Arch Linux

dk

Member

Registered: 2004-04-20

Posts: 106

Removing a custom kernel

I compiled a custom kernel ( definitely an E-ticket for a noob.)
It all worked an booted up nice, but it didn't solve my
(minor)problem. I don't need the custom kernel since it
does nothing different from my *perfect*arch kernel. I would like
to get rid of it. I'm assuming I can just remove the necessary
lines from Grub and the following:

/boot/Kconfig-2.6.6-custom
/boot/vmlinuz-2.6.6-custom
I made a symlink
ln -s /boot/System.map-2.6.6-custom /boot/System.map
Do I just delete /boot/System.map-2.6.6-custom ??

Next in /lib/modules can I remove everthing *-2.6.6-custom
and finally remove the source tree in my home directory?

Am I missing anything.

wdemoss

Member

From: WV - USA

Registered: 2004-01-18

Posts: 222

Re: Removing a custom kernel

I compiled a custom kernel ( definitely an E-ticket for a noob.)
It all worked an booted up nice, but it didn't solve my
(minor)problem. I don't need the custom kernel since it
does nothing different from my *perfect*arch kernel. I would like
to get rid of it. I'm assuming I can just remove the necessary
lines from Grub and the following:

/boot/Kconfig-2.6.6-custom
/boot/vmlinuz-2.6.6-custom
I made a symlink
ln -s /boot/System.map-2.6.6-custom /boot/System.map
Do I just delete /boot/System.map-2.6.6-custom ??

Next in /lib/modules can I remove everthing *-2.6.6-custom
and finally remove the source tree in my home directory?

Am I missing anything.

Looks like you got it all, except be sure to relink System.map to System.map26.

One thing for the future, when you compile your own kernel, if you name your system map file to System.map-`uname -r` (where uname -r is your kernel version, in your case 2.6.6-custom) then you don't have to link it to System.map becuase the kernel / ps looks for System.map-`uname -r` before System.map.

-wd

---

Hobbes : Shouldn't we read the instructions?
Calvin : Do I look like a sissy?

dk

Member

Registered: 2004-04-20

Posts: 106

Re: Removing a custom kernel

Looks like you got it all, except be sure to relink System.map to System.map26.

Don't kill me wd

==> ln -s /boot/System.map /boot/System.map26

or

==> ln -s /boot/System.map26 /boot/System.map

wdemoss

Member

From: WV - USA

Registered: 2004-01-18

Posts: 222

Re: Removing a custom kernel

ln -s <actual file> <alias> so its ln -s /boot/System.map26 /boot/System.map
np, no murders today

---

Hobbes : Shouldn't we read the instructions?
Calvin : Do I look like a sissy?