On Thu, Mar 02, 2006 at 04:25:50PM +0100, Arjan van de Ven wrote: > but so does the new one! For example on one of my test boxes, it depends > on if I have a USB stick inserted.. if it is at boot, sda is my usb > stick and sdb is my sata disk, and sdc my cd writer. > if it's not, sda is my disk and sdb my cd writer. > Now add USB cd writers to the mix and it's clear that such device names > are not persistent at all and utterly useless for identification. Certainly this increases the problem because now it matters if different types of devices are initialized in a different order, not just the same type. But if you only have one device of the type attached, the default "generic" device name independent /dev/cdrom, etc. devices are still created. So it doesn't make anything any worse for people who only have one device of a type attached, and it makes things better for people who have two devices of the same type attached, since it at least creates a unique symlink for each device, allowing the permissions to be set correctly, while still creating at least one device name independent device. But the problem was brought to his attention the day before yesterday, and he whipped up a quick hack yesterday that at least sets the console permissions correctly. I'm not sure that anyone's suggesting that this is really a solution, or even one that should be sufficient for FC5-- he left the bug open as MODIFIED rather than closing it, and it is a FC5 blocker. John Thacker
Attachment:
pgpRCcliIV9TY.pgp
Description: PGP signature
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
