[arch-dev-public] [signoff] mkinitcpio 0.5.25, cryptsetup 1.0.6-3

[Eric Bélanger]

On Sun, Jun 7, 2009 at 9:41 AM, Thomas Bächler <thomas at archlinux.org> wrote:
> Going into testing in a few minutes:
>
> mkinitcpio changes:
> - Finally fix a bug where required HID modules were missing
> - Add a new COMPRESSION option that accepts gzip, lzma and bzip2 parameters
> (gzip is the default, the others are only supported on 2.6.30 and later)
> - Add a new poll_device function that waits for a block device to appear.
> This is used in the init function and the resume hook, with rootdelay as a
> maximum timeout (default to 10 seconds)
> - Remove the unmaintained and untested modload hook
> - Remove the runtime filesystems hook
> - Rework the code that checks whether a root device has been found, don't
> reboot when exiting the emergency shell, but try to continue.
> - Due to the new poll_device behaviour, the usb and fw runtime hooks are no
> longer required, remove them
> - Parse arguments to init properly, using the "$@" parameter from the
> commandline the kernel generated - also needs the new fix in the latest
> kinit from testing (this allows us to use init=/bin/sh again)
> - Adjust for the latest filesystem/module-init-tools changes
> - Fix an autodetection bug that would sometimes omit some filesystems
>
> cryptsetup changes:
> - Use poll_device when waiting for the encrypted device and the (optional)
> key container device (default to rootdelay), added
> conflicts=(mkinitcpio<0.5.25)
> - Add a warning if the deprecated root= syntax is used on the commandline
>
>

I'm experience a small problem (it might be due to the changes you made.).

On my i686 system with lvm, after the lvm group has been activated, I get a:
"Waiting 10 seconds for device fe00" message. After the timeout, it says that
"root device fe00 doesn't exits attempting to create it
/bin/mknod /dev/root b 254 0"

The booting continues successfully and everything seems to be working
fine except I've noticed that I have a /dev/root symlink that points
to a non-existing fe00 device. I don't know if this is expected
because of the new poll_device function or if there's another problem
elsewhere. BTW, this system use lilo in case it's related.