A workaround for this is to make sure the driver modules are loaded in the desired order by putting them in /etc/initramfs-tools/modules.
The "use udev" comment rather misses the point. All reasonably current installations use udevd, but nothing uses the "stable" /dev/disk symlink tree by default, most notably - the installer does not use it. In fact it parses the legacy device name to determine the type of device. - consequently it isn't used in a default fstab - all documentation out there talks of /dev/sda, /dev/hda, etc... - sysfs uses the legacy names - the kernel outputs the legacy names - grub uses BIOS drive numbers and mapping those to /dev/?d* is difficult enough What is stable, anyway? Naturally the admin can use whatever scheme they like, but what should be the default scheme of a new Debian install? Should it "survive" the exchange of a disk controller (because the old one died)? Should it "survive" two disks being re-connected in the wrong order? What if a disk died and the root fs had to be restored from backup? Maybe the question "reference this partition primarily by [ ] uuid [ ] partition number on physical disk [ ] partition number of disk on port# of named controller [ ] partition number of disk on port# controller# [ ] partition number of BIOS disk #" should be added to partman, which would possibly change udev config to make the chosen path the real dev node and symlink the rest. I'll cherish the day when all device names in Linux are "stable" and optionally arbitrary but we aren't there yet. As it is I'd much rather the kernel had a constant idea about what it considers "the n-th disk on the m-th controller" C. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
