Re: Kernel setup() and initrd problems

[Chris Friesen]

H. Peter Anvin wrote:
> Chris Friesen wrote:

>>Maybe I'm just confused.

> I think so.
>
> The way to get around the historical baggage is to tell the kernel that
> the initrd is a "permanent" initrd by using the "root=/dev/ram0"
> command-line option.  This has the side effect of bypassing all the
> initrd historical crap and instead spawning /sbin/init using PID 1, like
> any other system would do.  Now you can just pivot and "exec /sbin/init"
> like you should be.

Thanks for that excellent explanation.

Chris

-- 
Chris Friesen                    | MailStop: 043/33/F10
Nortel Networks                  | work: [phone]
3500 Carling Avenue              | fax:  [phone]
Nepean, ON K2H 8E9 Canada        | email: [e-mail]