[arch-dev-public] [signoff] initscripts 2010.01-1, udev 150-1, device-mapper/lvm2 2.02.60, cryptsetup 1.1.0

Eric Bélanger snowmaniscool at gmail.com
Mon Jan 25 17:39:39 EST 2010


On Sun, Jan 24, 2010 at 5:39 PM, Eric Bélanger <snowmaniscool at gmail.com> wrote:
> On Sun, Jan 24, 2010 at 9:42 AM, Thomas Bächler <thomas at archlinux.org> wrote:
>> Okay, here are the changes:
>>
>> initscripts:
>> - hwclock improvements by Dan
>> - some minor crypto fix on shutdown
>> - moved the prekillall hook so it can be used better with splash
>> Necessary for device-mapper/udev, as dm-device detection on startup has
>> needs options introduced in 2009.11-1 (still in testing)
>>
>> udev:
>> - upstream update
>> - remove resolve-modalias, replace with modprobe --resolve-alias
>>
>> device-mapper/lvm2:
>> - cleaned PKGBUILD, hopefully fix the dmeventd path mess
>> - upstream update
>>
>> cryptsetup:
>> - upstream update, hopefully fixes lots of bugs
>>
>> These have to be moved together (and with mkinitcpio) so that
>> device-mapper still works fine with udev. This should solve FS#16735
>> finally - it has to be moved in any case, because this is better than
>> the situation in core, even if some people will still have problems.
>>
>> I want to move these 5 and mkinitcpio out of testing before I push the
>> kill-klibc mkinitcpio in - the latter will also require changes in lvm2
>> and cryptsetup.
>>
>>
>
> You'll also need to move the lilo-22.8-4 in testing with the new device-mapper.
>
> My i686 system using lilo and lvm2 booted fine.
>

I just noticed an error message when booting that i686 system. When
activating the LVM2 groups, I get this error message:
File-based locking initialisation failed.

The system still boots and there doesn't seem to be any problems.


More information about the arch-dev-public mailing list