The devs already know exactly how to fix it - the title of the bug report is the answer. In fact they knew how to fix it before Dapper was released. They simply didn't think it was worth fixing in Dapper - which was the worst mistake the Ubuntu devs ever made. It's not a mystery that needs to be solved - it's a fix that they knew but didn't want to put in at the last moment because they were afraid the fix might break other things. (It turns out that the fix doesn't break anything else, but that was their decision.)
The least bad workaround is to use UUIDs for the boot identifier in grub, as explained on that bug report. But that's not really good enough for all situations. The only real fix is not to install Dapper and instead wait for Edgy, which reportedly had the fix built-in from day 1. I'm not bothering with Dapper because, to me, it's definitely not worth the hassle. Best, Edward On 4 Jul 2006, at 10:34 AM, GIZMO wrote: > I have written a HOW TO for people suffering from this problem > while the > bug is ammended. It's titled "Fix 'ALERT! : dev/XYZ does not exist' > after upgrade to Dapper Drake". I hope it may be able to help the > developers with fixing it, perhaps? > > http://www.ubuntuforums.org/showthread.php?t=197956 > > Thanks > > Ted > > -- > udev enumeration should use /sys/bus not /sys/devices > https://launchpad.net/bugs/6367 -- udev enumeration should use /sys/bus not /sys/devices https://launchpad.net/bugs/6367 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
