Re: [SLE] installation support!! - a comment (even longer)
Anders Johansson wrote:
On Sunday 23 September 2001 21.22, you wrote:
I don't think you've eliminated the most plausible explanation. I can't see why the fstab file needs to be touched at all during the upgrade. There is no difference in format between 7.1 and 7.2, and the upgrade only looks at specific rpms and config files when it determines what to upgrade. At no time can I see a complete find / or whatever that runs through your entire file system.
I think it's far more likely that the upgrade simply re-created your fstab using the code from the 'clean install' version of yast. Of course, if this happened, the only way to check this without the source of the installer (which I have, but it would take too long to get acquainted with it), is if you had other customizations in fstab that also disappeared.
I don't see that as a plausible explanation. It is not plausible that with a "clean install" you have fstab entries that look like this: /dev/hda4 swap swap defaults 0 2 /dev/hda3 / ext2 defaults 1 1 /dev/sda1 /usr ext2 defaults 1 2 /dev/hdb5 /home ext2 defaults 1 2 /dev/hdb6 /opt ext2 defaults 1 2 /dev/hda1 /windows/C vfat auto,user,uid=jimmo 0 0 /dev/hda5 /windows/E vfat auto,user,uid=jimmo 0 0 /dev/hdc5 /windows/F vfat auto,user,uid=jimmo 0 0 /dev/hdc6 /usr/vmware/ ext2 defaults 1 2 I seriously doubt that /usr/vmware exists on most systems. However, this was still in fstab after the upgrade. Furthermore, /usr/vmware was mounted sometime during the install as I switched VCs and saw that it was mounted. /opt was not, so after the install I had to copy everything from the /opt directory into the /dev/hdb6 filesystem. Plus there is no real commonality in regard to which filesystem / or swap is mounted on. (not to mention the other filesystems) Therefore, the upgrade would need to have a lot of extra logic in it to "create" a new fstab. (IMHO) That's how it looked before the upgrade. Afterwards "auto" was changed to "noauto". Granted fstab might have been "re-created" as opposed to "changed", but the result is that I had a different fstab than when I started and the original was not backed-up. That's a bug. The upgrade also changed my httpd.conf. In that case there was a backup, but not with the fstab. regards, jimmo
I have installed Suse 7.2 on 3 of the PC's in my network. One was an upgrade, the other 2 fresh installations. The upgrade was a nightmare, breaking many things and need a lot of post-install repair work on my part. The fresh installations went fine. The only exception being that the X11 installation setup took no notice of what my monitor told it about it's refresh rates and let me adjust the screen to an out of range frequency..fortunately my monitor moaned about this Now, being a former UN*X system manager I can vouch for you all that upgrades are always more of problem than fresh installs. It stands to reason I suppose, they are much more complicated than virgin installs for the installation program to handle. Having said that, I no longer trust that SuSE upgrades can do the business except in the most straightforward of situations. -- Regards Cliff
Hi Cliff! Unfortunately, it shouldn't be that way. The changes I saw being made could have easily been changed to get it right. Maybe their is a magic log file that says what was changed, which would be a help, and I missed it. I keep hoping that one day upgrades will be just as easy as fresh installs. Regards, jimmo Cliff Sarginson wrote:
I have installed Suse 7.2 on 3 of the PC's in my network. One was an upgrade, the other 2 fresh installations.
The upgrade was a nightmare, breaking many things and need a lot of post-install repair work on my part.
The fresh installations went fine. The only exception being that the X11 installation setup took no notice of what my monitor told it about it's refresh rates and let me adjust the screen to an out of range frequency..fortunately my monitor moaned about this
Now, being a former UN*X system manager I can vouch for you all that upgrades are always more of problem than fresh installs. It stands to reason I suppose, they are much more complicated than virgin installs for the installation program to handle.
Having said that, I no longer trust that SuSE upgrades can do the business except in the most straightforward of situations.
participants (2)
-
Cliff Sarginson
-
James Mohr