From: "boyd, rounin" <boyd@insultant.net>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Don't know much about history
Date: Wed, 30 Jun 2004 23:22:59 +0200 [thread overview]
Message-ID: <030e01c45ee8$6bd2b090$18587d50@SOMA> (raw)
In-Reply-To: <f78e33ac6ab2511fcb04443727e4406a@collyer.net>
> ... and no fsck.
one time an ex-colleague screwed up and used the
wrong [new] kernel with an old [not upt to date]
RM03 [80mB; our root f/s].
the standalone tools worked-ish, but it took tape,
a screwdriver, a 9 track, adb and standalone fsdb.
we wasted a lotta 132x60 fanfold paper that night.
next prev parent reply other threads:[~2004-06-30 21:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 5:20 Jack Johnson
2004-06-30 7:12 ` Skip Tavakkolian
2004-06-30 7:26 ` Richard Miller
2004-06-30 21:34 ` boyd, rounin
2004-07-01 3:57 ` Geoff Collyer
2004-06-30 7:48 ` Richard Miller
2004-06-30 21:16 ` boyd, rounin
2004-06-30 7:57 ` Richard Miller
2004-06-30 7:58 ` Geoff Collyer
2004-06-30 8:35 ` George Michaelson
2004-06-30 21:29 ` boyd, rounin
2004-06-30 21:22 ` boyd, rounin [this message]
2004-06-30 21:15 ` boyd, rounin
2004-06-30 8:46 ` Steve Simon
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='030e01c45ee8$6bd2b090$18587d50@SOMA' \
--to=boyd@insultant.net \
--cc=9fans@cse.psu.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).