Strange module load behaviour
-----BEGIN PGP SIGNED MESSAGE-----
I have installed Debian sarge (from a custom made CD with kernel 2.6.18)
in a Sun Fire X4100 M2 server with a hardware RAID1.
When Debian boots, the disc name is either sda or sdb (in the
installation is all ways sdb though), this obviously makes Debian
unbootable when the fstab doesn't match the disc device name.
It seems that is related to the module load order, when it loads
usb_storage before the disc module, the disc is sdb, but the other way
around is sda. Adding usb_storage to blacklist partially solves the
problem, it seems like in single user mode blacklist is not red
Any hint on this? can I decide de module load order?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v18.104.22.168 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----