On Tue, 30 Oct 2001, John Desmond wrote: > --- Charles Steinkuehler <[EMAIL PROTECTED]> > wrote: > > > > Continuing, the reason you need ramdisk.lrp (or > > ramlog.lrp) is because > > otherwise there is no provision for creating and > > formatting additional > > ramdisks. You could put mount entries in fstab, but > > without formatting them > > first, the ramdisks are pretty much useless. There > > I hate to appear to be perserverating on this, but I'm > having trouble understanding how ram0 gets created and > formatted, but an add-on package is required to format > the ram1.
"perserverating"? whew! /dev/ram0 is the root filesystem under LRP. You should first understand what it means to be the root filesystem, and a rough idea how it gets designated as such. Then the complications introduced by initrd and the LRP approach should make a little more sense. It is definitely treated differently than any other file volumes, because of its special status. You probably ought to read http://www.linuxdoc.org/HOWTO/Bootdisk-HOWTO/index.html, and "man initrd". LRP uses a kernel patch that was developed by Dave Cinege to adapt initrd to use a tar.gz file instead of a preformatted filesystem image to initialize /dev/ram0 as root. (http://www.uwsg.iu.edu/hypermail/linux/kernel/9905.1/0771.html) In summary: /dev/ram0 is initialized by the patched kernel, unlike any other filesystems. --------------------------------------------------------------------------- Jeff Newmiller The ..... ..... Go Live... DCN:<[EMAIL PROTECTED]> Basics: ##.#. ##.#. Live Go... Live: OO#.. Dead: OO#.. Playing Research Engineer (Solar/Batteries O.O#. #.O#. with /Software/Embedded Controllers) .OO#. .OO#. rocks...2k --------------------------------------------------------------------------- _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
