http://qa.mandrakesoft.com/show_bug.cgi?id=3614
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEEDINFO
Ever Confirmed| |1
------- Additional Comments From [EMAIL PROTECTED] 2003-04-01 17:11 -------
argh :(. we're exposed to these problems because mkinitrd does not handle
dependencies (as you noted).
i'll add dependencies in next mkinitrd package.
FYI we didn't notice this problem because very few people are still using this
style of root partition (performance is not so good - and I'm not sure you won't
expect any booting problem?).
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: NEEDINFO
creation_date:
description:
When a loopback file is used as the root "partition," mkinitrd includes loop.o
but not aes.o in the initrd. Any attempt to use this initrd to boot the system
results in the initrd being unable to mount the root filesystem and, hence, the
system being unbootable.
I first encountered this problem during a fresh 9.1 install (I used a Knoppix
rescue CD to manually modify the initrd so I could boot after the install). It's
100% reproducible with mkinitrd from the command line after installation, too.
In any case, this bug makes Mandrake 9.1 loopback installs *totally unusable*
unless you manually hack the initrd.
I'm taking a look at the mkinitrd source code now, and I'll see if I can put
together a patch (or maybe a few patches which use different approaches) to fix
this.
