On 2014-01-12 12:27 (GMT-0300) Cristian Rodríguez composed:
Felix Miata composed in English:
> Once upon a time, OS installed to sole HD as sda
would stay sda even
> when PCI eSATA was both added and powered on at boot time. Not any more:
Maybe, but nowadays things are slightly more
complicated than that.
Meaning since when?
Since dracut replaced mkinitrd?
Since after 12.3 was released?
Since Grub2 became openSUSE default?
Since libata became smart enough to find all partitions that ide drivers
Since GUID support started appearing in PC BIOS?
All my systems were manufactured before any of those events took place, yet
only now has this new annoyance surfaced.
> Is there some kernel config option or cmdline
option or anything else in
> latest distro releases that can ensure an internal (aka non-removable)
> HD attached to a motherboard SATA port gets its device name assigned
> prior to any (removable) USB device and prior to any (removable) (e)SATA
> device attached to a PCI slot device port, like it used to do
You have to write your fstab referencing filesystems
Wrong. UUIDs are for computers and eidetics, not the other 99.99999% of
humans. My fstabs (and boot menus) refer to native filesystems via LABEL=
syntax, not by device name, nor any of the newer device aliases among which
UUID. UUIDs are fine for losing in binary files, not fine for plain text
config files humans ever care to edit or evaluate.
When one boots one system to each installed openSUSE release in turn with no
change other than boot menu selection, and redirects fdisk -l output to a
file, one should reasonably expect diffing any two of those files would
produce null output (not counting differences attributable exclusively to the
fdisk change in each reported disk's descriptive data head that began in
13.1's fdisk binary - newer added a disk label type line, and added a sector
count to the # of bytes line). That isn't happening here when the sata_sil
driver is being availed by a storage device.
remember to rebuild your initrd afterwards.
Why? Yet another new misfeature? Once an initrd has been written for a
particular installation and kernel and confirmed working as designed and/or
desired, it should not need to be rewritten just because some package with a
component that an initrd might contain has been updated, especially not 5
times per update run. https://bugzilla.novell.com/show_bug.cgi?id=786318
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org