From: milov@uwlax.edu (Milo Velimirovic)
Subject: [TUHS] Whence 1st Edition Unix Kernel Assembly?
Date: Thu, 24 Apr 2008 13:44:37 -0500 [thread overview]
Message-ID: <DA785D14-150E-49E1-BB21-F7F42A6979A4@uwlax.edu> (raw)
In-Reply-To: <Pine.BSF.4.58.0804241314150.5475@mail.keck.cx>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1736 bytes --]
I'd vote against. The MO disks and drive in my NeXT no longer work.
(of course if anyone has advice for resuscitating MO devices, I'm all
ears.)
- Milo
On Apr 24, 2008, at 1:15 PM, ckeck at texoma.net wrote:
> What about magneto-optical disks? They are supposed to last 50 years.
> Problem is that one would have to not only hold on to the disks, but
> also
> the drives, as well as a system with a SCSI I/F.
>
> -Cornelius
>
> On Thu, 24 Apr 2008, Tim Newsham wrote:
>
>> Date: Thu, 24 Apr 2008 07:30:58 -1000 (HST)
>> From: Tim Newsham <newsham at lava.net>
>> To: Michael Kerpan <madcrow.maxwell at gmail.com>
>> Cc: tuhs at tuhs.org
>> Subject: Re: [TUHS] Whence 1st Edition Unix Kernel Assembly?
>>
>>> I guess we need to start archiving all software on acid-free
>>> archival
>>> paper, then. It's the only way it'll survive.
>>
>> And not necessarily in human readable form -- how about some format
>> that is very easy to ocr with minimal errors and error correcting
>> codes?
>>
>> ps: how many pages to archive a gigabyte of src code? ;-)
>>
>> Tim Newsham
>> http://www.thenewsh.com/~newsham/
>> _______________________________________________
>> TUHS mailing list
>> TUHS at minnie.tuhs.org
>> https://minnie.tuhs.org/mailman/listinfo/tuhs
>>
>
> --
> Cornelius Keck -----------------------------------------> ckeck at texoma.net
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
--
Milo Velimirović, Unix Computer Network Administrator
608-785-6618 Office - 608-386-2817 Cell
University of Wisconsin - La Crosse
La Crosse, Wisconsin 54601 USA 43 48 48 N 91 13 53 W
--
Unix: Where /etc/init is job #1.
next prev parent reply other threads:[~2008-04-24 18:44 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
2008-04-24 19:02 ` Larry McVoy
2008-04-24 18:44 ` Milo Velimirovic [this message]
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=DA785D14-150E-49E1-BB21-F7F42A6979A4@uwlax.edu \
--to=milov@uwlax.edu \
/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).