On Wed, 28 Jul 1999, Tony Nugent wrote:
==>My advice is simple: DON'T upgrade. NEVER upgrade. Re-install
==>instead. Why do I say this? Let me explain...
This morning I wrote a different letter but didn't send it. At that point
I thopught I could still bang my system into shape. Not so. I concede
that it is not possible to upgrade from 5.0 to 6.0, not without WAY too
much work. SO I don;t advise anyone to do it! I will resolve some of the
problems I had.
==>Don't do this. The 2.2.x kernels DO NOT NEED kerneld! This daemon is
==>now a standard part of the kernel is isn't needed.
As mentioned below, I was still using my 2.0.36 kernel... so kerneld _was_
needed by it. Unfotunately, as you will note, 2.0.36 doesn't work well
with RH6.0...
==>Two reasons that this may be happening. The version of Accel-X that
==>are using could be binary incompatable with the RH6 shared libraries.
==>It's not actually segfaulting (not that you've mentioned), so it's
==>less likely the cause.
What turned out to be at issue is that Xaccel didn't accept gzipped fonts,
and choked on them at startup (not being able to find the default font).
Tihs could probablty be fixed with a new version of Xaccel but I am cheap
so I just unzipped them. it works fine now.
==>RedHat 6.0 now has /usr/X11R6/bin/startx exec xinit with the --auth
==>flag to make it more secure. It also creates the X authority for you,
==>a new one each time it is run.
This was a problem as well. Running xdm once set everything straight.
==>Not sure what's going on here, but mount is one of the packages that
==>needed upgrading if you wanted to use a 2.2 kernel on a RH5.2 system.
==>Makes me suspicious that something's gone wrong here.
Works now that I upgraded to kernel 2.2.5
==>Hey, I have a very strong suspicion that you're booting up with your
==>old 2.0.36 kernel, which wouldn't know about the new functionality
==>that is expected of it by your new utilities! This might also explain
==>some of the weirdness with modprobe.
Boy, you were right. Actually I compiled the 2.2.5 kernel, using make
zlilo, but lilo complained that the kernel was too large! I didn't notice
this so my /vmlinuz was updated, but lilo was not run. Hence, huge module
problems.
==>There's very likely to be more grues lurking about the place than the
==>ones you've mentioned here.
Boy stuff was screwed up... many other devs had incorrect major/minor
numbers, libraries were a mess... module loading didn't work the way it
was supposed too (still) although not as bad as before. As we speak I
ambacking up my /usr/local and /home and my source, etc, etc... Preparing
for a brand new install. On the plus side, I do like many of the features
of 6.0.
Thanks for the advice!
