From: Mel (gormo at domain csn.ul.ie)
Date: Tue 04 May 1999 - 12:50:13 IST
Got it burned over the weekend and went to upgrade just to see if the CD
worked right. I thought my old install with the packages I'd upgraded was
fine and I didn't need 6.0 and I was bloody right. Loads of stuff is now
broken for no reason. It bollixed up keymaps, older packages, LILO, socks,
the lot and installed shite like RPC, nfs, webservers, stuff I never
wanted or needed or had an option to NOT install during the upgrade. I've
cleaned up a lot of it but there are still a number of problems.
1. LILO now won't install kernels unless they are much smaller than they
needed to be before. This can be solved using modular kernels but I would
like to know why a compiled zImage won't get installed by LILO if it's
2. runsocks no longer works. runsocks is a shell script to get programs
that use TCP/IP to run over a socks proxy. I used to get great milage out
of this program but now I can't even get telnet to work without a core
dump. I ran strace but it showed nothing more than it crashed while
looking at resolv.conf. Any ideas what could be broke? I recompiled socks
but to no avail.
3. It made a pure shite of gnome. It upgraded some packages and left
others alone making the whole lot of them inconsistent. What is the
easiest way to remove EVERYTHING gnome related both installed through RPM
and from source so I can put it on right again.
4. Keymapping is still screwed. I changed the revelant init scripts to
pipe the revelant keymap through loadkeys and although this works grand
from the console, it doesn't in a shell script. The line looks something
zcat /usr/lib/kbd/keymaps/i386/qwerty/uk.kmap.gz | loadkeys
What is wrong with that line that I have to type it in while in the
current directory of the keymap and at the console. More importantly, what
is the right way to load a keymap. The above works but wasn't even
remotely like what was in the initscripts originally.
I've a feeling redhat "updated" the wrong libraries but I've not way of
confirming this. Does anybody have a clue with what could have gone wrong
to cause *any* of the above?
This archive was generated by hypermail 2.1.6 : Thu 06 Feb 2003 - 13:04:10 GMT