I just want to be sure I understand how pacman handles custom kernels

Allamgir · 2009-10-10 15:51:53

If I compile my own custom kernel and set pacman to "IgnorePkg = kernel26 kernel26-firmware", will pacman automatically hold off all updates that require a later kernel version and just let me know? Should I ignore kernel-headers (or kernel26-headers; I can't remember the exact name now) as well, or are the other two sufficient? I was thinking of just managing kernel updates myself once pacman updates start accumulating, but I didn't want pacman to start writing all over my custom kernel with a new one as soon as an update comes out. The wiki pages tell me plenty about the actual compiling of the kernel, but not much about what to do afterwards. Is this what the other custom kernel compilers around here do?

ngoonee · 2009-10-10 16:33:02

Its recommended you compile your custom kernel to have a different package name (anything other than kernel26). Take a look at kernel26-parallel in the AUR, just add your own config/patches to it. Then you'll always have to stock kernel to fall back on. I normally have about 3 kernels installed, the stock one and 2 custom ones I'm playing with. This is better than trying to use IgnorePkg to circumvent pacman's updates.

Allamgir · 2009-10-10 16:37:02

Thanks for the help! I didn't find a kernel26-parallel in the AUR, though.

So if I understand correctly, I should compile my kernel with a new name of my choosing, tell GRUB to load that up in my Arch Linux entry, but keep my Arch Linux Fallback entry with the stock kernel? Then pacman will just do its thing correctly and I'll get to use my custom kernel, correct?

ngoonee · 2009-10-10 16:38:08

Yep, pacman will update kernel26 as updates comes along, but your own kernel will not show as being in the repos, so it won't even attempt to update it. It will still track files, dependencies, and the like though.

Allamgir · 2009-10-10 16:40:52

Awesome! So what about packages that require later kernel versions? Is it recommended that I just keep fetching the latest kernel from kernel.org and customize it? That sounds like a lot more work than its worth. I guess what I'm asking is, is it OK for me to stay back a few kernel versions despite Arch's bleeding-edge rolling nature? I would think with this system, pacman will think I'm using the latest kernel and will update all packages that require it, thus causing breakage.

loafer · 2009-10-10 19:13:38

Finally you don't need to add the kernel headers to IgnorePkg.

ngoonee · 2009-10-10 23:08:28

Allamgir wrote:

Awesome! So what about packages that require later kernel versions? Is it recommended that I just keep fetching the latest kernel from kernel.org and customize it? That sounds like a lot more work than its worth. I guess what I'm asking is, is it OK for me to stay back a few kernel versions despite Arch's bleeding-edge rolling nature? I would think with this system, pacman will think I'm using the latest kernel and will update all packages that require it, thus causing breakage.

The only packages which directly rely on kernel version would be udev and the like. I trust the devs on this one, if they say you need a certain version, you'd better make sure your kernel complies with it.

Out of curiosity, what modifications are you doing to your kernel that is so hard to keep updated? If its just your config, save it and reapply it with make oldconfig....

Allamgir · 2009-10-10 23:44:45

Wow, I didn't know that would work! I just do some slimming of unnecessary hardware, &c. but thought I would have to muck about in the config file or menuconfig each time.

ngoonee · 2009-10-11 05:14:31

I'm not sure if menuconfig has the option for it, but I use gconfig (Gnome user here) and just save my config file once I've got it nicely, then reload it the next time I compile a kernel.

In fact, the custom kernel I use (kernel26-ice) even has an option to use the config file from the currently running kernel, which is handy while updating.

theapodan · 2009-10-11 16:20:54

I don't know how advisable this is, but I've removed the kernel26 packages so that pacman isn't tempted to update them, and compiled and installed my kernel in the "old-fashioned" way.

I haven't experienced any problems thus far with this setup.

Arch Linux

#1 2009-10-10 15:51:53

I just want to be sure I understand how pacman handles custom kernels

#2 2009-10-10 16:33:02

Re: I just want to be sure I understand how pacman handles custom kernels

#3 2009-10-10 16:37:02

Re: I just want to be sure I understand how pacman handles custom kernels

#4 2009-10-10 16:38:08

Re: I just want to be sure I understand how pacman handles custom kernels

#5 2009-10-10 16:40:52

Re: I just want to be sure I understand how pacman handles custom kernels

#6 2009-10-10 19:13:38

Re: I just want to be sure I understand how pacman handles custom kernels

#7 2009-10-10 23:08:28

Re: I just want to be sure I understand how pacman handles custom kernels

#8 2009-10-10 23:44:45

Re: I just want to be sure I understand how pacman handles custom kernels

#9 2009-10-11 05:14:31

Re: I just want to be sure I understand how pacman handles custom kernels

#10 2009-10-11 16:20:54

Re: I just want to be sure I understand how pacman handles custom kernels

Board footer