At least explain when and where this behaviour in ordering changed within udev and why shouldn't be a bug. Or, are you telling me that at the SAME TIME, udev changed its behavior in ordering and grub guys introduced a new bug that inadvertently broke the ordering?
Tryed running grub (would be more correct to say the grub shell frontend, that's the component run when you are running linux) with --device-map option. This force grub to produce this device.map file: (fd0) /dev/fd0 (hd0) /dev/sda <-- This ISN'T the hd bios want to boot (hd1) /dev/sdb That is the wrong ordering, as said before. I'm sorry, but it's simpler to me to think that the grub shell frontend is just assuming the default LANANA device ordering to map devices, looking for the hd that hopefully will be booted by bios. So, for example, hd0 in grub is just the first /dev/hdX in alphabetical order (excluding cd-roms) if you use the old linux ATA driver, or /dev/sdX in alphabetical order (excluding cd-roms and usb mass storages) if you are using LIBATA or SCSI. In this case, you MAY think that changing the device ordering in udev is not a bug, but you would be inadvertently breaking other applications. Let's hope to hear a word from Grub devs soon. In the mean time, please, stay tuned. -- S-ATA Hard drives swapped https://bugs.launchpad.net/bugs/225175 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
