James.Smart@xxxxxxxxxx wrote: > - There are some real challenges in supporting a udev-named boot > device. For the most part, it's a distro issue, which is becoming > better. PS: for $10, name a 2.6 distro that uses udev out > of the box for disk names and its installation. For $10 more, > can it install/boot from one? Hmm. You are correct in that appearently there _is_ a large education effort required. SLES9 uses udev for installation and booting per default, and this works with even the horribly old version we're having there. > - Some of these vendors come from large disk farms, and in several > cases, the disk farms change frequently. Thus, they must flush > and regenerate their udev configurations on each change. Not a > fun process. Not really. You normally shouldn't have to redo the udev configuration as your vendor/distributor will have provided you with one which works out of the box. Of course, you'll have to initiate a rescan of the SAN topology, but udev is the least of the problems you're facing then. > - Most could care less about, or don't understand, the technical > justifications for the new 2.6 behaviors. Thus, they push their > vendors for same-style behaviors as 2.4 regardless of the 2.6 > stance. Oh, how true. I heartily agree with you on this one. Cheers, Hannes -- Dr. Hannes Reinecke hare@xxxxxxx SuSE Linux Products GmbH S390 & zSeries Maxfeldstraße 5 +49 911 74053 688 90409 Nürnberg http://www.suse.de - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
