On 12/26/01 at 9:24 PM, Jacques Nilo <[EMAIL PROTECTED]>
wrote:

> From: "David Douthitt" <[EMAIL PROTECTED]>
> 
> > I've begun working on the next generation... and have
> > Oxygen booting with an initial RAM disk - in preparation
> > for running without the linuxrc patch.

> In a non-patched kernel the only parameter you need are
> linux initrd=initrd.gz root=/dev/ram1 init=/linuxrc (see
> my 2.4.14 distro)

My impression was your distro never "let go" but rather set the system
up as desired and then you ran init yourself.

In the case of Oxygen, it is entirely standard: /linuxrc is run
automatically since the root volume is actually /dev/ram1.  Thus the
linuxrc-always patch is unnecessary since the root volume is not
/dev/ram0.  Once /dev/ram1 is configured, all appropriate filesystems
are unmounted and the kernel does a pivot_root and starts init.

> root=/dev/ram1 will load initrd fs in /dev/ram1. But after
> that you can do whatever you want. In by 2.4.14 version of
> LEAF (see previous post) initrd is loaded in /dev/ram0 and
> after that everything is moved over tmpfs which is much
> nicer. But you have to be under 2.4.x  :-)

My impression was that the initrd fs will be loaded into /dev/ram0 no
matter what, and that root=/dev/ram1 means that the real root system
is /dev/ram1.  It's the fact that the real root is NOT /dev/ram0 that
makes /linuxrc run.

I'd like to go to 2.4 - but right now it appears that it is quite big. 
I've been working with 2.4.16 with GR Security patch installed - last
compile (without module support) was 700-800k uncompressed.  I DID
strip out everything I could - but I noticed a few things:

1. PPP Compression conflicts with something else in the kernel.
2. Can't pick and choose from iptables/ipchains/ipfwadm simultaneously
unless using modules.

So back to module support....
--
David Douthitt
UNIX Systems Administrator
HP-UX, Unixware, Linux
[EMAIL PROTECTED]

_______________________________________________
Leaf-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to