-----BEGIN PGP SIGNED MESSAGE----- dman <[EMAIL PROTECTED]> writes:
> The benefit is for Herbert and people with out-of-the-ordinary > setups. By using an initrd Herbert can make one kernel package for > the repository and it will be able to boot my system regardless of my > disk controller and root fs type since those can be loaded as modules. > > If you build your own kernel just for your system, I don't see any > real advantage. I'm not using it for my homemade kernels. One case where you are required to have an initrd is if you have your root (/) in an LVM. You need the initrd to run the userspace tools necesarry to initialize the LVM. A real pain though since the lvm tools require a writable filesystem (they create files in /etc). Debian uses cramfs for initrd which is read-only. The debian initrd config scripts are great, but can't use with LVM. lvm_createinitrd creates a working initrd but is *not* extensible (not even a script -- it is an ugly compiled piece of code) easily. <sigh> I've almost got the debian mkinitrd working with LVM, but not quite and I don't have a test box to keep "playing around" -- at least for a while. - -- - -rupa -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: noconv Comment: Processed by Mailcrypt 3.5.6, an Emacs/PGP interface iQEVAwUBPE+al3HDM4ucEopdAQGaZgf/eqBeNAVjQywKdyf6ZbES4reHgBKcSmxG zvGLU0bJ71dxg8EdrTT0fJn1RTLBbVtCY+nDbPdT1XcY4kJM2WZnlmEJK2PkKbpa +/1NeInQzPbEIoLo2bypSlUVhUOzXn+P5beHfrS8DFd1LCETHvM+pCS9Gz2oJvZR 1pszQg/Zpq3ODLASOdQCGa01neKKJ5KpPwc9CtGP3Nh8RndwqZI10u8A4Iike+lg Oun8CzcGM5XzrT5qv0NIZFerYeCeN3xKdRcX3dGlGbDkBw4pr89wJs3y6rGEayab rvs+uYmHzSgXRufbhcZXh5S4IdZK1KJWviqthUNQ/Dr3NsWfOMCV6Q== =zwWh -----END PGP SIGNATURE-----
