From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: monsgrapius@my-deja.com, 9fans@cse.psu.edu
Subject: Re: [9fans] HOW TO INSTALL?
Date: Tue, 6 Feb 2001 16:04:31 -0500 [thread overview]
Message-ID: <20010206210444.AD093199E8@mail.cse.psu.edu> (raw)
I don't know what the install process is doing there.
Two others have seen this behavior too, but I have
yet to see it myself so I haven't found it.
Type the Delete key while it is churning and
it should come back with the list and let you
proceed.
If anyone who has seen this wants to help debug
the problem, drop me a note once you're set up
and gotten the hang of rio.
Thanks.
Russ
next reply other threads:[~2001-02-06 21:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-06 21:04 Russ Cox [this message]
2001-02-07 23:41 ` [9fans] So, once I've got the OS up how do I Jim Choate
-- strict thread matches above, loose matches on Subject: below --
2001-02-08 21:11 [9fans] HOW TO INSTALL? Russ Cox
2001-02-08 10:00 Becker, Peter Dr.
2001-02-06 16:41 nemo
2001-02-06 9:49 Mons Grapius
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=20010206210444.AD093199E8@mail.cse.psu.edu \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
--cc=monsgrapius@my-deja.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).