From: jmk@plan9.att.com jmk@plan9.att.com
Subject: installing plan9 demo on a PC
Date: Tue, 15 Aug 1995 08:59:37 -0400 [thread overview]
Message-ID: <19950815125937.gSzYidI4-mRska5hb7qvvZZDkkMMfJdPSUjX6uI_sag@z> (raw)
I also thought it was peculiar that sd!1 was not picked up as a
boot device but then I have no idea what criterion is being applied nor
by whom.
For that matter, I don't have a clear idea of what plan9/B
*exactly* what `B' is trying to do.
man b.com. man pages are available at http://plan9.att.com/plan9/mansearch.html.
Also, just now I noticed something about my plan9.init that
strikes me as suspicious, namely, the `rootdir' specification.
this name is within the boot device so does not require a 'device!ctrlno' prefix.
next reply other threads:[~1995-08-15 12:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-08-15 12:59 jmk [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-08-15 17:36 jmk
1995-08-15 16:09 Bill
1995-08-15 14:18 Bill
1995-08-15 2:02 jmk
1995-08-14 19:19 Bill
1995-08-13 4:49 Bill
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=19950815125937.gSzYidI4-mRska5hb7qvvZZDkkMMfJdPSUjX6uI_sag@z \
--to=jmk@plan9.att.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).