On Fri, Mar 28, 2003 at 05:24:43AM -0800, Burke, Thomas G. wrote: > Installed the latest kernel & (I think glibc) updates for 6.2. > Rebooted machine. Kernel starts to load: beepbeepbeepbeepbeep (ad > nauseum)... > > "well shit," I think. I'll just R^2 the kernel & glibc stuff & > reinstall the older versions. > > Reboot with boot disk (unfortunately it's an old kernel, as well)... > rpm -e --force kernel (and related) and glibc (and related).
Oops. The --force is there for people who only know what they're doing. rpm does lots of checking to make sure you don't shoot yourself in the foot. You told it to override those checks and hurt yourself... For kernels, you always install new ones. The old ones are available to boot from. You should have tested that first. Never, ever, remove glibc. Boy does that hurt! > Now many of the normal commands don't work (ls, more, and so on)... > Didn't realize they were somehow related to those packages. That's why rpm does the checking for you. ls is in the fileutils package: [EMAIL PROTECTED] ewilts]$ rpm -q --requires fileutils /sbin/install-info /bin/sh /bin/sh rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1) libc.so.6(GLIBC_2.1.3) libc.so.6(GLIBC_2.2) libc.so.6(GLIBC_2.2.3) libtermcap.so.2 This tells you that you can't remove glibc because fileutils requires it. > So, what the heck... Make sure I've got recent backups of /etc & > /root (don't want to lose those configs!). Reinstall 6.2 from CD, > tell it to format the appropriate patitions & go to bed. > > Get up this morning, apply all the updates (which I have on disk) > except the latest, which is what seems to have hosed my system. > > Copy my /etc directory back into /etc. Did you also get the subdirectories of /etc? That's where things like your network is (/etc/sysconfig). Did you double-check the lilo config to make sure it's pointing to the right kernel? Did you re-run lilo? > Reboot machine. > > Error - can't (write or find) /var/lib/<something related to modules> > - - sorry, it goes by too quickly to catch what it says (Didn't think > to hit the pause key), but it seems to be pointing to a file that has > an older set of numbers than my kernel. cat /var/log/messages dmesg You're hopefully not too far away from getting things going again... -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] Member #1, Red Hat Community Ambassador Program -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
