From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] hardware acceleration
Date: Wed, 14 Feb 2001 02:01:57 -0500 [thread overview]
Message-ID: <20010214070202.33F78199D5@mail.cse.psu.edu> (raw)
Just curious. What are you using to compose your
thesis if you don't have a working Plan 9 terminal? If you
did, I would presume you would use troff with
Acme or SAM.
I'm using troff, acme, and a staggering amount
of chewing gum and twine. I'll have a working
Plan 9 terminal again in a couple hours, I hope.
Something in an experimental kernel did some bad
things to my kfs file system. I can still read
it, just not boot from it. (It's very odd.)
I'm setting up a cached fake worm file server
(using Eric's IDE patches) at the moment, so that
such damage will be easier to undo in the future.
I should have done this a long time ago.
Russ
next reply other threads:[~2001-02-14 7:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-14 7:01 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-14 12:42 William Staniewicz
2001-02-14 10:24 forsyth
2001-02-14 7:44 nigel
2001-02-14 2:28 Russ Cox
2001-02-14 1:40 Russ Cox
2001-02-14 1:56 ` George Michaelson
2001-02-14 9:41 ` Douglas A. Gwyn
2001-02-14 0:45 Russ Cox
2001-02-14 1:08 ` George Michaelson
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=20010214070202.33F78199D5@mail.cse.psu.edu \
--to=rsc@plan9.bell-labs.com \
--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).