From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
Subject: Re: [9fans] pccpu kernel: how to get #S/sdC0/nvram recognized?
In-Reply-To: Your message of "Tue, 04 Nov 2003 21:33:47 MST."
             <Pine.LNX.4.44.0311042120520.4387-100000@maxroach.lanl.gov>
From: "Russ Cox" <rsc@swtch.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <33733.1067988243.1@t40.swtch.com>
Message-Id: <E1AHAWr-0008m7-LE@t40.swtch.com>
Date: Tue,  4 Nov 2003 18:24:03 -0500
Topicbox-Message-UUID: 7f972a12-eacc-11e9-9e20-41e7f4b1d025

> 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