HMS Kinross
HMS Kinross was a Hunt-class minesweeper of the Royal Navy. Kinross was a member of the Admiralty's modified design of Hunt-class minesweepers, which are known variously as the Aberdare class or Aberdare group.
 Sister ship to HMS Kinross, HMS Aberdare in 1919 | |
| History | |
|---|---|
 | |
| Name: | Kinross |
| Builder: | Fairfield Shipbuilding and Engineering Company |
| Yard number: | 576 |
| Launched: | 4 July 1918 |
| Out of service: | 16 June 1919 |
| Fate: | Sunk by mine 16 June 1919 in the Aegean Sea[1] |
| General characteristics | |
| Class and type: | Hunt-class minesweeper, Aberdare sub-class |
| Displacement: | 710 tons |
| Length: | 231 ft (70 m) |
| Beam: | 28 ft (9 m) |
| Draught: | 8 ft (2 m) |
| Propulsion: |
|
| Speed: | 16 knots (30 km/h; 18 mph) |
| Range: | 140 tons coal |
| Complement: | 73 |
| Armament: |
|
Loss
At the time of her loss HMS Kinross' was serving with the Mediterranean Fast Minesweeper Flotilla.
Casualties
12 members of the ships company were lost, with most casualties incurred in the ships engine & boiler rooms.[2]
- On 16 June 11 men were lost in the sinking.
- BEAMES, John, Cook, M 7573
- BRACEWELL, Robinson, Chief Engine Room Artificer 1c, 270477
- BROOKS, Albert H, Stoker 1c, K 23341
- FLOOD, Arthur, Stoker Petty Officer, 292870
- JOYCE, Ralph, Stoker 1c, SS 118607
- LETHBRIDGE, James A, Stoker 1c, K 14459
- MONTE, Emilio, Officer's Steward 2c, 122493
- OLIVER, William S, Able Seaman, J 11034
- RICHARDS, Edward A, Stoker 1c, K 14474
- STONE, Henry T, Stoker 1c, K 17232
- WEBBER, Samuel C, Leading Stoker, 183706
- On 17 June 1 man died of wounds.
- MCCORQUODALE, Duncan, Engine Room Artificer 4c, M 33412
gollark: ... no.
gollark: Thus bad.
gollark: It does NOT allow random access.
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, finds the latest versions and decompresses stuff at the right offsetThere 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: I have been pondering an osmarksarchiveformat™ because I dislike the existing ones somewhat. Specifically for backups and append-only-ish access. Thusly, thoughts on the design (crossposted from old esolangs)?
References
- Colledge, J. J.; Warlow, Ben (2006) [1969]. Ships of the Royal Navy: The Complete Record of all Fighting Ships of the Royal Navy (Rev. ed.). London: Chatham Publishing. ISBN 978-1-86176-281-8.
- Admiralty Estimates for 1919 (appendix) accessed 25 October 2016
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.