SCIENTIFIC-LINUX-USERS Archives

November 2014

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Konstantin Olchanski <[log in to unmask]>
Reply To:
Konstantin Olchanski <[log in to unmask]>
Date:
Fri, 7 Nov 2014 19:11:07 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (26 lines)
On Fri, Nov 07, 2014 at 07:00:17PM -0800, ToddAndMargo wrote:
> 
> I got bit by it too.  I had to restore my /etc/X11 directory.
> 
> Do you know if it is safe yet to let any xorg update go through?
> 

Best I can tell, you are okey if all packages are up to date from SL and ELREPO repositories.

Only the transition across the incompatible X11 API change was rough.

I had ELREPO updates turned off, got broken until manually updates.

If I had them turned on, would have been broken by the ELREPO update because of the problem with unloading the old kernel module.

Regarding the unloading of the kernel module, it looks like the whole X11/Xorg mess of scripts
has no hook or place where I can run my own command *before* Xorg is fired up (I could install
a fake /usr/bin/Xorg, but that would not survive rpm/yum update). Plenty of scriptable places *after* Xorg starts,
none *before*.

-- 
Konstantin Olchanski
Data Acquisition Systems: The Bytes Must Flow!
Email: olchansk-at-triumf-dot-ca
Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada

ATOM RSS1 RSS2