http://bugzilla.novell.com/show_bug.cgi?id=613873
http://bugzilla.novell.com/show_bug.cgi?id=613873#c4
Alex Müller changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
InfoProvider|bugzilla@go4more.de |
--- Comment #4 from Alex Müller 2010-06-21 14:09:12 UTC ---
yast2-bootloader talks about "master boot record" without informing me whether
the SATA or the PATA harddisk is supposed to be the one containing this master
boot record. And, as you said, because the SATA/PATA mix is problematic, in
different situations the master boot record can be interpreted to be on SATA or
on PATA, without the user knowing about that?!
So IMHO:
- If YaST itself cannot discern the correct harddisk by itseld, it should give
me enough information to do the right config myself (e.g. by adding the
"/dev/disk-by-id" or, maybe more human-readable, the capacity information
and/or the filesystem used on this disk).
- YaST should at least warn during an installation that the SATA/PATA mix can
cause problems and the proposed config should therefore be thoroughly checked.
- YaST could warn about a valid Windows bootsector being overwritten by grub.
Especially during updates, as it is extremely unlikely that on a running
system grub will have to overwrite a Windows bootsector in this scenario!
- YaST could have an option to leave certain drives untouched.
Don't know if these are good and/or feasible workarounds :-/-
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.