Bug 13447

Summary: Several problems with upgrade from 6.1 to 6.2
Product: [Retired] Red Hat Linux Reporter: hugues.talbot
Component: gdmAssignee: Havoc Pennington <hp>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-07-13 19:13:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description hugues.talbot 2000-07-04 05:54:36 UTC 
Dear Sirs,

The 6.2 upgrade procedure has some terribly annoying features:

1- if a /etc/auto.master is NOT present before  the upgrade it
puts one there. In our case the auto.master information comes from 
an NIS map. The upgrade should not invent files when not needed.

2- The upgrade procedure changed the layout of /etc/rc.d/rc?.d/ 
files without notice. In particular it created a K20nfs in lieu
of a pre-existing S60nfs in rc3.d and  rc5.d. It also removed
a S95sshd there. 

3- Gdm reacts badly to unknown situations. It tries to restart
several times when some data is missing before settling down. 
A couple of times should be enough. The end results is that the
monitor tries to sync to a high frequency for the X stuff, then
something goes wrong (no way to tell what), then it syncs down to
text mode for a few milliseconds, and then tries again a number of
times. During that time the computer is unusable and looks about
to blow up. Fortunately GDM gives up after a while. Why not immediately? 
presently this is a surefire way to destroy monitors.

These are minor points but it made the difference between a smooth
15 minutes procedure and an annoying 2 hours one when trying to find
out what is happening.
Comment 1 Bill Nottingham 2000-07-04 19:34:30 UTC 
The NFS thing was an intentional change in that it not be started by
default, although settings shouldn't be changed on upgrade; most likely
this is because the script moved packages, and it can't really be helped.

The auto.master confusion should be fixed in the latest autofs in rawhide.

Assigning the rest of the bug to gdm.
Comment 2 Havoc Pennington 2000-07-13 19:13:05 UTC 

*** This bug has been marked as a duplicate of 13786 ***
Comment 3 Glen Foster 2000-07-18 13:22:08 UTC 
This defect is closed (since it's a duplicate)