On Sat, 2013-09-28 at 08:59 -0400, Stephen Powell wrote: > On Fri, 27 Sep 2013 23:17:40 -0400 (EDT), Ralf Mardorf wrote: > > On Fri, 2013-09-27 at 19:41 -0400, Stephen Powell wrote: > >> But the correspondence between these Linux device names and the > >> hardware device numbers varies widely from boot to boot. I can assure > >> you of that from personal experience. > > > > So my question, if somebody experienced it already is answered. > > The s390x hardware platform is more susceptible to device name variations > because of the extra "online/offline" layer. The kernel does not assign a > major > or minor device number to a DASD, nor does it assign it a user-space device > name (/dev/dasda, /dev/dasdb, etc.) until the device is brought "online". > Under Debian, a DASD device is brought online by the sysconfig-hardware > package, which in turn is invoked by udev. IDE and SCSI drives on the i386 > or amd64 hardware platform do not have this extra layer of processing. > But device name changes can happen on i386 and amd64 too. It's just less > likely.
As Joel mentioned "If, for some reason, they spin up out of order, your naming changes". I consider to edit /dev/sd* entries in fstab to use the label or UUID instead and will take a look at grub.cfg too. Regards, Ralf PS: Perhaps someday I'll switch to UTC for the clock too ;) or stop using MBRs. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1380374333.6343.31.camel@archlinux
