From: imp@bsdimp.com (M. Warner Losh)
Subject: [TUHS] Whence 1st Edition Unix Kernel Assembly?
Date: Thu, 24 Apr 2008 12:57:12 -0600 (MDT) [thread overview]
Message-ID: <20080424.125712.756919467.imp@bsdimp.com> (raw)
In-Reply-To: <4810D417.8040005@bitsavers.org>
In message: <4810D417.8040005 at bitsavers.org>
Al Kossow <aek at bitsavers.org> writes:
: The critical point to add to this is that the data integrity needs to be
: constantly verified, even on presumed stable storage, and it is migrated
: to what at that time is easily to deal with storage, so you CAN easily
: verify it.
I keep my archives on a series of disks. There's always at least 2
copies, often times more, and the underlying disks get swapped out on
a round-robin basis. Helps limit my exposure to one or two
failures... I've had horrible luck with all other methods...
Warner
next prev parent reply other threads:[~2008-04-24 18:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 6:03 Warren Toomey
2008-04-23 6:07 ` Warren Toomey
2008-04-23 18:27 ` Tim Newsham
2008-04-24 0:07 ` Warren Toomey
2008-04-24 1:57 ` Tim Newsham
2008-04-24 6:04 ` Tim Newsham
2008-04-24 16:34 ` Al Kossow
2008-04-24 16:44 ` Tim Newsham
2008-04-24 17:07 ` Tim Bradshaw
2008-04-24 17:16 ` Al Kossow
2008-04-24 17:27 ` Michael Kerpan
2008-04-24 17:30 ` Tim Newsham
2008-04-24 17:35 ` lyricalnanoha
2008-04-24 18:15 ` ckeck
2008-04-24 18:40 ` Al Kossow
2008-04-24 18:57 ` M. Warner Losh [this message]
2008-04-24 19:02 ` Larry McVoy
2008-04-24 18:44 ` Milo Velimirovic
2008-04-24 21:39 ` Peter Jeremy
2008-04-25 6:27 ` Wilko Bulte
2008-04-24 17:38 ` Wilko Bulte
2008-04-24 18:39 ` Milo Velimirovic
2008-04-24 19:35 ` John Foust
2008-04-24 17:45 ` Al Kossow
2008-04-24 18:07 ` John Cowan
[not found] <200804241753.KAA02899@mist.magic.com>
2008-04-28 10:48 ` Warren Toomey
2008-04-28 16:52 ` Tim Newsham
2008-04-28 14:15 James A. Markevitch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080424.125712.756919467.imp@bsdimp.com \
--to=imp@bsdimp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).