On Sun, 4 Nov 2001, Harry Putnam wrote: > > Setup: > RH 7.1 stock on a rarely used partition of dual boot Solaris/Redhat > machine. This install is pretty bare bones.. no X and is there as > a safeguard for that day when I trash the solaris install and can't > get into the machine or something. > > (Don't tell anybody on comp.unix.solaris though.... he he) > > This RH install boots from floppy. Since its rarely used, it didn't > seem worth while to get into and figure out the mbr stuff when solaris > is concerned. > > I've updated to the newest update kernel, and done the same stupid > thing I did last time. Tried rpm -ivh on the new kenel and got a boat > load of dependancy messages, conflicting with old kernel files.
Were you trying to install just the kernel rpm or the kernel, kernel src, kernel headers.... I have never had a problem doing an ivh on just the kernel. Trying to install multiple copies of the kernel headers etc gets the dependancy problems. > So thinks I to myself. I'll just rpm -Uvh and then `mkbootdisk <newkernel>' > > After doing so... (bad move) then running `mkbootdisk newkernel' > thats when I remembered why this was a bad thing. > > mkbootdisk 2.4.9-12 > mount: fs type msdos not supported by kernel > mount: fs type vfat not supported by kernel The Uvh upgraded and removed the old modules. > I remembered then that this happened before. I imagine it is because > the old modules have been deleted or something related to removing old > kernel files. > > At any rate it means that I can't make a boot disk with the new kernel > image. At least not easily. Until the new kernel is booted and of > course I can't boot the new kernel without a floppy. It sounds like you kinda have a chicken and egg problem. > OK .. maybe there is a way to invoke the modules that handle the > filesystem stuff. But I doubt it since they would not agree with the > running old kernel. > > Maybe there is some other easy solution...? > > But it all reminds me that I don't really know how to save the old > kernel when installing a new one. I've seen the recipes that say > rpm -ivh instead of rpm -Uvh but what about all the dependacy stuff > do you jsut --force or --nodep .. That seems kind of rash too. Redhat has a nice writeup about in the documentation (i forget exactly where sorry) I saw a pointer to it this morning while reading the 7.2 errata for the upgraded kernel. I have used this proceedure many times it works well for me. The key is to only install multiple copies of the kernel rpm (rpm -i kernel-2.4.new_one). Do not try to install multiple copies of the headers, src, etc. You will get dependancy problems. > Last time I ended up booting with `toms' rescue thingy and it wasn't a > big deal. I sure I can do the same now. But since the machine is > still running maybe someone can tell me how to get past the this > point. And more importantly how one safely installs a new kernel but > keeps the old one on tap in case of problems. I would suggest reinstalling the old kernel (rpm -i --oldpackage kernel-2.4.old_one should do it.) HTH, -- ......Tom Dysfunction The Only Consistent Feature of All [EMAIL PROTECTED] of Your Dissatisfying Relationships is You. _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
