I think there might be more to it than the release file. I had the same
problem Before upgrading. I had upgraded some libraries under 5.0 and
Linuxconf lost the ability to call the network. I don't remember what files
did it but there are some apps that require some 5.1 style libraries (like
the latest KDE) to work on 5.0. I had two boxes do this. Removing
Linuxconf allowed the normal startup to work fine. They were better after
going to 5.2.
However, one 5.0 to 5.2 upgrade has this problem:
Linuxconf won't call the firewall (module is active and the menus allow the
setup). Manually calling ipfwadm is o.k. A fresh 5.2 install was fine.
All my other 5.0 to 5.2 upgrades: (maybe not Linuxconf related).
Error on startup about mounting /proc which then refuses to mount any
additional drives in fstab. Manually calling mount with options works.
PPPD complains that IPX is not compiled in the kernel (it is). Other
mounting problems all seem related to /proc.
Again, a fresh 5.2 install has none of these problems. I don't know if the
upgrade process missed something (can't find anything wrong under glint) or
if Linuxconf confused the process (I removed Linuxconf beore the upgrade
just to be sure).
Any easy procedures to verify the correct files? I found an errata on KDE
that said to --force install one app a second time if upgrading as the
uninstall process was flawed. Residue?
"[EMAIL PROTECTED]" wrote:
> I've seen some notes regarding the above problem but haven't found the
> emails in my box.
>
> I started out with RH 5.0 and Linuxconf 1.10r5. I upgraded the OS to 5.1
> and Linuxconf to 1.13r8. On boot up none of my network services start - I
> must manually run /etc/sysconfig/network-scripts/ifup-eth0. I noticed a
> fix to ifup-aliases, pulled it down, but must run it maually as well.
>
> The only thing I can think of is Linuxconf thinks the system is still
> running at the earlier OS, which obviously started its daemons in
> a completly different manner.
>
> How can I get Linuxconf to 'see' that I am now running RH 5.1 - I'm
> itching to move to 5.2 but will wait till I can fix this.
---
You are currently subscribed to linuxconf as: [[email protected]]
To unsubscribe, forward this message to [EMAIL PROTECTED]
