[Top] [All Lists]

Re: [patch] cmdline.c rewrite

To: Guido Guenther <>,
Subject: Re: [patch] cmdline.c rewrite
From: Andrew Clausen <>
Date: Wed, 5 Feb 2003 10:55:43 +1100
In-reply-to: <20030204234529.GZ16674@bogon.ms20.nix>
Original-recipient: rfc822;
References: <> <20030204092417.GR16674@bogon.ms20.nix> <> <20030204231203.GY16674@bogon.ms20.nix> <> <20030204234529.GZ16674@bogon.ms20.nix>
User-agent: Mutt/1.4i
On Wed, Feb 05, 2003 at 12:45:29AM +0100, Guido Guenther wrote:
> On Wed, Feb 05, 2003 at 10:19:09AM +1100, Andrew Clausen wrote:
> > Huh?  The firmware uses something looking like OSLoadPartition=dksc(0,1,2),
> > not /dev/sda1.
> Sure. But what we do on IP22 is to let the kernel look at OSLoadPartition and 
> use that as the root device - so we're actually interested in
> linux device names. This is basically done since we can't store the root
> device in OSLoadOptions due to limited space.

Limited space?  Ah.  I understand now.

> > >  If you have a
> > > bootloader (which is only true for IP22 [1]) it sets up the kernels
> > > commandline properly anyway - so where's the problem? nfsroot?
> > 
> > The problem is the firmware (on my IP27, anyway) uses a different
> > form to Linux for OSLoadPartition.  OSLoadPartition tells the
> > firmware / bootloader (sash here) where to find the kernel.
> Again: we don't care what the firmware wants here,

I do.

> Why do you need sash for booting anyways? Can't
> you let the PROM boot the kernel directly?

No.  I can't figure out why.  In any case, the PROM uses OSLoadPartition
to find the kernel.

> Anyways, I won't object to change OSLoadPartition, we have a bootloader
> on IP22 so this isn't actually needed anymore.

It is on IP27.

So, we should obviously support OSLoadPartition=/dev/sda1 (=> root=/dev/sda1),
but it would also be nice to support OSLoadPartition=dksc(0,1,3).


<Prev in Thread] Current Thread [Next in Thread>