From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] building 9load
Date: Wed, 9 Apr 2003 19:50:16 -0400 [thread overview]
Message-ID: <615ce13f2a1b1eb2d3cd1e7e246d984b@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0304091741270.25963-100000@maxroach.lanl.gov>
cd /sys/src/boot/pc; mk
will build 9load.
to build a boot floppy,
cd /sys/lib/dist/pc; mk ndisk
i'm not 100% sure a fresh 9pcflop
kernel works. you definitely
need to change the
nobootprompt=local!/bzroot
in the usual plan9.ini to
nobootprompt=local!/boot/bzroot
due to the great /boot restructuring.
a fresh 9pccd kernel is known to work.
next prev parent reply other threads:[~2003-04-09 23:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-09 23:42 ron minnich
2003-04-09 23:50 ` Russ Cox [this message]
2003-04-10 15:14 ` ron minnich
2003-04-10 15:30 ` andrey mirtchovski
2003-04-10 15:31 ` rsc
2003-04-11 13:19 ` paurea
2003-04-11 13:27 ` Russ Cox
2003-04-11 13:33 ` paurea
[not found] <1427712808@snellwilcox.com>
2003-04-10 15:29 ` 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=615ce13f2a1b1eb2d3cd1e7e246d984b@plan9.bell-labs.com \
--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).