D&C GLug - Home Page

[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]

Re: [LUG] Compiling the Kernel

 

Thomas Arrow wrote:
>
> So I remember reading
> somewhere you could install 2 kernels and the boot into the test one
> and if I it messed up I could just boot in to the old one (I'm using
> GRUB). 

You can do this.

Debian's kernel-package does it all for you, so I forget the specifics ;)

But a kernel is just a program GRUB runs, so you can have several. And
/lib/modules keeps things in nicely version numbered directories so you
can have several different kernel versions available for booting. I've
had over 6 on some boxes when debugging driver issues (Debian inserts
two grub entries for each kernel so that gets cluttered fast).

You are unlikely to make a system completely unbootable, and should be
able to "undo" changes with a Live CD even if you did. Backing up
"/boot", and convincing yourself you could recover it with a LiveCD if
needed, might be a shrewd move if you are unsure.

> Now
> secondly I was thinking that if I did managed to make it all go right
> can I overwrite my original kernel with the new one. 

They ain't that big. Just make sure it defaults to the right one in the
GRUB menu.lst file, and leave the old one till you are sure you don't
need it.

> Lastly I use SuSE
> and really enjoy having it kept up to date and secure does anyone know
> if the yast online update will still work with it.

No idea.

Debian has a few packages that depend on kernel versions, and this
affects patching of Debian. As such I prefer to stick with stock kernels
(I make exceptions for hardware not yet supported for the stock 2.6
kernels - more than I'd like).

As such I'd be surprised if you didn't have to stay within supported
packages for 100% functionality of YAST, especially as regards patching.
You'd probably also want to base a bespoke kernel on a SUSe kernel, so
check if they supply a ".config" (probably done these days by supporting
one of methods of exposing ".config" content in one of the files in /proc).

But then presumably you have a reason for wanting a bespoke kernel?

--
The Mailing List for the Devon & Cornwall LUG
Mail majordomo@xxxxxxxxxxxxx with "unsubscribe list" in the
message body to unsubscribe. FAQ: www.dcglug.org.uk/linux_adm/list-faq.html