From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] pccpu kernel: how to get #S/sdC0/nvram recognized?
Date: Tue, 4 Nov 2003 18:24:03 -0500 [thread overview]
Message-ID: <E1AHAWr-0008m7-LE@t40.swtch.com> (raw)
In-Reply-To: Your message of "Tue, 04 Nov 2003 21:33:47 MST." <Pine.LNX.4.44.0311042120520.4387-100000@maxroach.lanl.gov>
> Now I'm finding I'm not sure how the bit of magic happens that gets things
> set up so that factotum can find #S/sdC0/nvram. The system comes up and
> sdC0 is there all right, I can 'fdisk -p /dev/sdC0/data > /dev/sdC0/ctl'
> dance and the 'prep -p blah blah' dance and make the nvram partition
> visible -- after it has booted. But while it is booting, factotum has no
> luck in getting to that partition.
9load parses a minimal partition table and leaves it for the kernel.
you need to leave a sdC0part= entry. i think it's of the form
part name start end / part name start end / ..., but i forget.
russ
prev parent reply other threads:[~2003-11-04 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 4:33 ron minnich
2003-11-04 23:24 ` Russ Cox [this message]
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=E1AHAWr-0008m7-LE@t40.swtch.com \
--to=rsc@swtch.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).