Hi, we just had a discussion on IRC:
14:41 < pusling> Md: I haven't seen any comments from you on 392623 (I would actually consider the side effects critical) 14:43 < Md> pusling: because it's not a bug in udev and I do not know enough dm to comment on the issues in other packages 14:43 < Md> I think there is a consensus that lilo is broken 14:43 < aba> Md: does it only affect lilo-based installs? 14:44 < Md> grub works fine, if this is what you are asking 14:44 < pusling> aba: it affects root/boot on lvm (which the installer sets up easily with udev 100, but upgrading to udev 103 makes it not work) 14:44 < pusling> grub won't boot on root on lvm 14:44 < Md> check the message from lool 14:45 < aba> hm, ok. That sounds like an RC-bug "somewhere", wherever that somewhere is 14:45 < pusling> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401393 14:45 < pusling> is the lilo bug 14:45 < pusling> but the bug is not in lilo according to vorlon 14:46 < Md> the problem is that 100 broke other things... I think we can safely agree that all programs confused by the existence or non-existence of /dev/dm-* devices are broken, and as a matter of personal taste I'd rather not have the dm-* devices, but fixing lilo looks (?) easier 14:46 < Md> I can do either way, but I am not going to decide this myself 14:47 < Md> one argument in favour of the change is that it is what other distributions do 14:47 < Md> so it may be worth investigating how rhel and suse cope with lilo and root on lvm 14:47 < Md> or else lilo could install a rules file to stop creating the devices :-) 14:49 < pusling> mv lilo lilo.real ; echo -e #! /bin/sh\nrm -f /dev/dm-*\nlilo.real > /sbin/lilo 14:49 < pusling> ;) 14:50 < Md> I can't see why it should be hard to teach lilo to ignore /dev/dm-* anyway... 14:55 < aba> Md: well, that should be easy enough, yes ... Summary is that it's probably easiest if lilo would just ignore /dev/dm-* - is that ok from "it does not have other side-effects" as well? Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
