kernel rpm help

[elite_syntax]

I did a rpm kernel 2.4.20-13.It this this


kernel ***********************************100%
*******************************************100%



I did that but i not sure what to do next?I never install a kernel with rpm.:confused:

[serz]

I think that now, you have to edit your grub.conf and make a new section to boot with y our new kernel. You have to make something similar to what your Grub system settings are but changing the kernel images.

[MB[DK]]

... And reboot.

[elite_syntax]

Whatt about add your own hardware?Is that all in the rpm?:confused:

[elite_syntax]

I lost



What do i need to edit in/etc/grub.conf?I shutdown the red hat linux and when i came back to home the new kernel work.But now when i re install red hat linux and download it again and re boot it didn't work.:confused:

[elite_syntax]

Anyone want to help a newbie??

[dysharmonic]

To edit :

# pico /etc/grub.conf

Ctrl+X to exit and save

Dont ask me but I dont know anyhintg abt grub.conf :D

[wrc1944]

Most rpm distros will automatically edit the lilo or grub file when you do a kernel rpm install- I know Mandrake does.

All you do is download the new kernel rpm (and rpm source if you like) to its own directory in /home.

Then go to a console, su to root, and cd to that directory. Then issue:

rpm -ivh *.rpm

After it installs, go and check your lilo or grub file and make sure the new kernel image is really there. You should also have a new modules directory for the new kernel in /usr/lib/modules.

It's good to check these files beforehand, so you know what you had originally- in fact, just make a backup of /etc to be safe. Then you can reboot, and you'll have an option to boot either the new kernel, or the old one (assuming all went well with the install). Even if the install fails, you will still have the old kernel intact.

wrc1944

[irishred]

I take it that it is not a good thing to delete a rpm after you install it. I would think it would insert itself into the kernal and be happy. I deleted one of the kernel updates after installing it. My box shutdown and came up to the GRUB prompt. I can't type anything. I put in an old boot disk but that's not a whole lot of help. I can admisistrate it but keeping the OS happy is tough. I am running RH9. Any suggestions?

[wrc1944]

Deleting an rpm after you install it should have no effect at all- it's just a repository package of the source files for the program, or kernel. The kernel image is actually extracted from the rpm, compiled,and placed in /boot. Same for the modules- they are placed in /lib/modules.

If you deleted the kernel image file in boot, that would be different. We'd need more info about what you actually did in sequence, and then what happened on your box to deduce what your problem is.

For example:
Is your old kernel still there in /boot? What exactly did you delete? Did it boot OK the first time after installing a new kernel, or this happened only after you deleted your "kernel update"? Were the options for which kernel to boot from there? And, what exactly does "kernel update" refer to- the rpm, or the image file?

Maybe RH9 doesn't edit the grub/lilo file when you install a kernel, or you needed to manually run grub/lilo after editing? I don't use grub, so am not up on the details of grub.

wrc1944

[dysharmonic]

Originally posted by wrc1944
Deleting an rpm after you install it should have no effect at all- it's just a repository package of the source files for the program, or kernel.



Yup, it's just like installing from the CD. You dont have to copy the rpm file onto the h/disk, you just give it the install command, once everything is in place the rpm file itself is of course still on the CD.

I remember compiling my kernel when I had RHL 7.1, it needed to update/edit lilo.conf and then manually run it by /sbin/lilo -v.

Not sure w/ RHL 9 tho.

[elite_syntax]

I got it working now i shutdown the pc and started it back up and got my new 2.4.20-13 kernel to work and i delated the rpm so if i got hacked.They can't mess with the kernel:)




Now i got to find more updates.I not sure if i should update my lib on red hat linux 7.1 just to upgrade to the 2.4.20


Because i think of sell my laptop to get a new one.:)

[irishred]

In theory I agree with everyone, deleting the rpm should not matter.

I d/l'd the rpm's into my /home/<user>/update dir.

I tried a new trick of rpm -Fvh *.rpm (there were two kernels and two kernel boot rpms to add)

It installed everything and appeared happy. When it was complete, I started deleting rpm's rm -r xxx.rpm. This went well, then I decided to try rm -r *.rpm (as the user not root and in the /home/<user>/updates dir. My terminal went back to prompt after a few seconds of deleting, my screen went blank, my machine shut down, rebooted then when it got to GRUB it stops.

[elite_syntax]

I just happy my 2.4.20 works.:D

[wrc1944]

irishred,

If your old boot disk won't work, maybe the RH9 cd 1 install disk has a rescue mode like Mandrake does, and you can get to a console, and open grub with a text editor and see what's going on.

If you have a seperate /home partition, you could simply reinstall RH9, and not format or resize /home when you get to partitioning section- just keep things as the are, and reformat the other partitions, and reinstall the entire OS. If you are somewhat of a newbie, and there is nothing you would mind losing on the hard drive, this might be the simplest solution.

Anyway, If you do it right, /home will be left untouched, so there is little danger of losing any data on /home, assuming it is a separate partition NOT /home on your root partition.

Another option is to get a knoppix cd (or another type of rescue cd) , and boot from it to the knoppix linux OS with kde and utilities, and access your RH9 install from there to figure out what grub is doing. BTW, how are you posting to the forum- on another machine?

Chalk it up to experience, and next time, read more and understand what the procedures are before you make a move. In any case, always create a seperate /home partition when you install any linux OS, and keep your data there, so if disaster strikes and you can't get out of it, a reinstall is very simple. And always make a working rescue boot floppy right when you do the OS install.

wrc1944