http://qa.mandrakesoft.com/show_bug.cgi?id=3614
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |UNCONFIRMED
------- Additional Comments From [EMAIL PROTECTED] 2003-04-02 03:30 -------
mkinitrd 3.4.43-1mdk still doesn't see that loop needs aes. It's no worse than
the previous mkinitrd package though. I'll take a look at the new dependency
code and see if I can figure out what's wrong.
BTW: I know not many people do this and the performance isn't that good, but the
performance is still sufficient for this machine's uses. I've learned over the
last few years to expect booting problems with loopback ;) but I still like to
fix them when possible.
------- 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: UNCONFIRMED
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.
