On Sep 25, 2007, at 1:37 PM, Federico Sevilla III wrote:
What you need an initrd for are:
1. Encrypted (using dm-crypt) root filesystem with unencrypted /boot.
2. Root filesystem inside LVM (or an encrypted LVM with root inside
it).
3. Kernel that needs a loadable module to access root filesystem
because
the necessary support wasn't compiled-in statically.
though i've always made sure not to use initrd. always compiled only
what the machine only needs to have. like do you really need to
compile in a yamaha sound card when you only have a creative and will
never use anything else or its a server that doesn't have a sound
card or have ipv6 features, when you know you'll never use 'em or
have no plans to in the life span of the box to use ipv6. though
point taken that sometimes, what's the point? a couple of megs here
and there of compiled modules and at the power of our current boxes,
a minute or two longer to compile the kernel really means so little.
aesthetically, it's kinda good not to have bloat.
thanks for the info on initrd. it might be useful, someday. there's
always something to learn!
cheers!
------------
Cocoy Dayao
"People who are really serious about software should make their own
hardware." --Alan Kay
_________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
[email protected] (#PLUG @ irc.free.net.ph)
Read the Guidelines: http://linux.org.ph/lists
Searchable Archives: http://archives.free.net.ph
