On Tuesday 04 December 2007 02:02:46 am Carlos E. R. wrote:
The Monday 2007-12-03 at 21:53 -1000, kanenas@hawaii.rr.com wrote:
after re-reading the release notes i can see that libata can be disabled, thanks:)
Only for 10.3, in version 11 this workaround might disappear. That's their intention :-(
That would imply that all fake sdx references would have to be changed to hdx , no? But what comes next? I can manually change the grub and fstab entries, also some samba and nfs shares in yast, perhaps a few more configs, but there are many other references in many many other files, how can that be dealt with after the fact? would a symlink or three do it?
No, a symlink would not work.
You should change all the references to device independent ones, like label, id, or uuid (not sure if all are valid). Nowhere should you have references like "hda" or "sda".
well, i looked at menu.lst and fstab in my 10.3 for the first time and saw a bunch of brave new things...I guess entropy *must* increase... i will try the "hwprobe=-modules.pata" in a day or two, but i somehow doubt it will solve my problem and then i will have to decide if i will live w. it or revert to 10.2 . btw, how does grub know about libata before the kernel is loaded and how/does it get modified?
In vmware... no idea.
vmware has had this scsi/sata problem, now it became an ide/scsi/sata one! maybe they will adapt the disk/by-id thing, who knows?
in 10.2 we had usbfs and smbfs as sources of similar anguish. is SuSe/linux big enough to dictate changes like that almost arbitrarily? Please note, i am not talking about technical merits...
Unfortunately, it's not suse alone, it's all of them (developers).
are we being asked to operate in a vacuum? is new stuff coming out just for the sake of newness?
-- Cheers, Carlos E. R.
thanks for the insight. now i know more than i wanted! d. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org