[6864] in testers
Re: RHEL 4 X upgrade issue
daemon@ATHENA.MIT.EDU (William Cattey)
Mon Mar 28 10:22:38 2005
In-Reply-To: <1111958034.9732.11.camel@egyptian-gods.mit.edu>
Mime-Version: 1.0 (Apple Message framework v619.2)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <1978c43c990f42985795bb33c1ba7c12@mit.edu>
Content-Transfer-Encoding: 7bit
Cc: rhe-release@mit.edu, testers@mit.edu
From: William Cattey <wdc@MIT.EDU>
Date: Mon, 28 Mar 2005 10:22:25 -0500
To: Greg Hudson <ghudson@mit.edu>
Ok.
Thanks very much for the clear and detailed analysis.
The course of action you propose sounds like the right one.
It's VERY reassuring to know that stand-alone Linux will be OK.
-wdc
"Like my father before me, I shall remain 5 years old till the day I
die!"
On Mar 27, 2005, at 4:13 PM, Greg Hudson wrote:
> On Sat, 2005-03-26 at 14:57, William Cattey wrote:
>> Is this X configuration bumpiness something we should report as a bug
>> to Red Hat?
>> It might affect stand-alone RHEL3 users at MIT who upgrade.
>
> Red Hat takes care of this as part of the upgrade process (as I
> discovered after a few hours of poking around), by invoking
> /usr/sbin/fix-mouse-psaux from anaconda. We can have Athena do the
> same
> thing, probably at boot time. So, while it would have been cleaner for
> Red Hat to take care of this in the xorg-x11 RPM (where they take care
> of renaming XF86Config and a few other things), we don't really have a
> bug to report on that front.
>
> I don't know if it's worth reporting the failure to shut down the X
> server properly. If it only happens on a bad mouse configuration, then
> it's probably not very worthwhile since mouse configuration is simpler
> (everything is supposed to use /dev/input/mice). If it only happens on
> rare hardware like the old Thinkpad I'm testing on, then it may not be
> worthwhile. If it is worthwhile, it may be better to pursue it through
> X.org, which means first checking if the problem has already been fixed
> in the mainline, which means figuring out how to build an X server. My
> guess is that we want to put this on the back burner until we see it in
> another situation.
>
