http://bugzilla.novell.com/show_bug.cgi?id=591700 http://bugzilla.novell.com/show_bug.cgi?id=591700#c20 Kay Sievers <kasievers@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|kasievers@novell.com | --- Comment #20 from Kay Sievers <kasievers@novell.com> 2010-04-19 11:28:17 UTC --- A version upgrade of udev might not convert all the information in the udev database. As a result, during the upgrade, some dynamic information will no longer be available when the new udev binaries are installed along with the old database. The values need to be re-evaluated, by rebooting the system, or "udevadm trigger" needs to be run for the devices in question. I don't know how to solve this from the udev side, running "udevadm trigger" when updating udev is known to cause problems in some cases. It should not in theory, but especially things like device-mapper may break their udev setup, if we emit additional events. I guess, we need to make sure, that a bootloader update happens before the udev update, if the bootloader depends on non-core/non-kernel properties from the udev database. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.