Ole G. Kinney

Ole G. Kinney (June 1, 1858 – December 26, 1922) was an American politician and businessman.

Born in Dane County, Wisconsin, Kinney moved to Crawford County, Wisconsin in 1860 and then to Dunn County, Wisconsin in 1863. He was educated in the public schools. He was a merchant and grain trader. Kinney was president of the Community Savings Bank in Superior, Wisconsin. Kinney served as the Colfax Town clerk and also served as chairman of the Colfax Town Board. From 1903 to 1907, Kinney served in the Wisconsin State Assembly and was a Republican. In 1922, Kinney was elected to the Wisconsin State Senate from Superior, Wisconsin and the Wisconsin 11th Senate District; he died from a stroke in Superior, Wisconsin before he took the oath of office. Kinney had the stroke on October 31, 1922 and was near death.[1][2][3][4]

Notes
  1. 'Wisconsin Blue Book 1905,' Biographical Sketch of Ole G. Kinney, pg. 1096
  2. 'Wisconsin Blue Book 1923,' Biographical Sketch of Marcus A. Kemp, pg. 609 (Notation was made that Kemp was elected in a February 17, 1922 special election to fill the vacancy cause by the death of Senator-elect O. G. Kinney)
  3. 'Ole G. Kinney, Wisconsin State Senator Elect Dies,' Creston Daily Advertiser (Iowa), December 27, 1922, pg. 1
  4. 'Senator-Elect Near Death,' La Crosse Tribune, November 17, 1922, pg. 11
gollark: Oh, so you mean this `hdr` goes at the start and the `dofs` thing tells you where the bit appended to the end is?
gollark: Perhaps the headers should also store the location of the last header, in case of [DATA EXPUNGED].
gollark: There are some important considerations here: it should be able to deal with damaged/partial files, encryption would be nice to have (it would probably work to just run it through authenticated AES-whatever when writing), adding new files shouldn't require tons of seeking, and it might be necessary to store backups on FAT32 disks so maybe it needs to be able of using multiple files somehow.
gollark: Hmm, so, designoidal idea:- files have the following metadata: filename, last modified time, maybe permissions (I may not actually need this), size, checksum, flags (in case I need this later; probably just compression format?)- each version of a file in an archive has this metadata in front of it- when all the files in some set of data are archived, a header gets written to the end with all the file metadata plus positions- when backup is rerun, the system™ just checks the last modified time of everything and sees if its local copies are newer, and if so appends them to the end; when it is done a new header is added containing all the files- when a backup needs to be extracted, it just reads the end and decompresses stuff at the right offset
gollark: I don't know what you mean "dofs", data offsets?


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.