You are not logged in.
Pages: 1
Hi,
I am on an old dell inspiron 6000 laptop, and trying to make a custom minimal kernel tailored for it. I wonder how often should I update it, if I should update it at all. My point of view on this issue is that, since my hardware is old, newer kernels won't be adding anything that I would need, since anything that can be added about this hardware, would already be included in kernel 3.2. However, I am not sure if this argument is valid, because I am not an expert on this issue. Could someone please enlighten me a little?
Yo Dawg, I heard you likes patches, so I have created a patch for your patch, so you can patch your patches before you patch.
Offline
I run a custom kernel (via ABS) on my laptop. It works like this: in my pacman.conf, I specify
IgnorePkg = linux linux-docs linux-headersSo when I do
pacman -SyyuI receive a warning about the ignored packages whenever the kernel has been updated. That tells me to recompile my kernel from ABS. I don't necessarily do it straight away, but I try to make time for it within the next 24 hours.
Offline
My point of view on this issue is that, since my hardware is old, newer kernels won't be adding anything that I would need, since anything that can be added about this hardware, would already be included in kernel 3.2.
You're mistakenly assuming that new hardware support is the only difference between one release and the next.
Offline
I run a custom kernel (via ABS) on my laptop. It works like this: in my pacman.conf, I specify
IgnorePkg = linux linux-docs linux-headers
I assume you don't use your custom kernel side by side with ARCH kernel right?
You're mistakenly assuming that new hardware support is the only difference between one release and the next.
That, and bug fixes and improvements. I am imagining all bug fixes and improvements related to my hardware would be already made. I guess you are suggesting that updating kernel matters regardless of the age of the hardware?
Yo Dawg, I heard you likes patches, so I have created a patch for your patch, so you can patch your patches before you patch.
Offline
I assume you don't use your custom kernel side by side with ARCH kernel right?
Right. It didn't occur to me to do it any other way. Anyway, this keeps things simpler.
Offline
Pages: 1