https://bugzilla.novell.com/show_bug.cgi?id=330705#c17
--- Comment #17 from andreas bittner 2007-10-15 09:51:56 MST ---
hi again,
you cant be serious about this, right?
this is how i see this bug from an enduser point of view:
your upgrade mechanism doesnt ask/handle the partitions found in fstab
properly.
why on earth would your installer ask for usr and opt just fine and mount them,
and simply disregard the partition for /var... it never asks for /var...
and besides: how hard cand it be to analyze fstab and if you have found
partitions on a physical drive and mapped them from oldname /dev/hdaX to
/dev/sdaX already, then simply map all the partitions that are listed in
fstab....
why does yast installer ask for /opt and /usr just fine, but never asks to
point to the proper location from old /dev/hda6 = /var to /dev/sda6...
why not simply exchanging/offering all the device rootnames once a device has
been identified and corrected from an oldname to newname?
so if i have given yast the information that my / (root) parition is on
/dev/sda3 now which was listed in my old fstab as /dev/hda3, then yast knows
that what was once /dev/hda is now /dev/sda....
and everything that exists in /dev/hda now is on /dev/sda...
this is the most logical and basic thing there is.
as sda and hda are physical disk names, and the numbers after the rootname of
the physical disks are parititon numbers...
how in earth could this be a problem for the installer/upgrade mechanis, and
how can suse lower the importance of this bug to "enhancement"
this is simply crazy and to freak out. i dont get it why i still am buying suse
retail releases on and on....
i am really freaking out about this i am sorry, but i have to write this down,
cos i still think i am only dreaming all this mess: you people mess up a simple
upgrade process from a clean and simple installation of your very previous
version of opensuse and dont support an upgrade just because customers use
partitions for mountpoints your installer/tools offer?
you gotta be kidding me. there is nothing so special or magic about a /var
partition, but nevertheless suse messes up handling it properly, just because
if who knows why some of the devs decided to switch naming convention just all
of a sudden for classical hardware.
and while thinking about this "problem" i have explained why i fail to see the
"big problem" with finding the partitions.... if you found just one of the new
names (on a physical disk/device), then you have found them all... simply
replace all of the fstab entries with the old device name to the new devicename
the customer/user once has identified/supplied, or the installer has properly
found. this cant be that hard. or am i missing a point or is there more to this
whole confusion with the naming convention change?
why not asking the user just to point to all of the partitions that are listed
in the customers fstab file, instead of omitting the var partition just because
of who knows why.
i really really dont get it. i really think i do gotta change to some other
distribution for sure and advise others to do so too if this is the real
philosophy of suse/novell.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.