You are not logged in.
I used to testing for a while to install the 2.6.32 kernel and I installed the kernel26-headers package.
Today I upgraded (testing repo off) only to find that there's a kernel-headers package which installs to /usr/include/
as opposed to the kernel26-headers (from testing (and previous kernel-headers)) which install to /usr/src/linux-*
Furthermore the kernel-headers package from core comes with version 2.6.32!? But the kernel in core is only 2.6.31
?!?
My victim you are meant to be
No, you cannot hide nor flee
You know what I'm looking for
Pleasure your torture, I will endure...
Offline
kernel-headers are the sanitised userspace headers that are part of the toolchain (glibc, gcc, binutils).
kernel26-headers are for building kernel modules. They were split from the kernel26 package. You of course know this given you subscribe to arch-dev-public for the important announcements for [testing] packages...
Offline
I've seen that last sentence many times now, and wonder whether anyone actually uses [testing] without subscribing there. It would be insane, like deciding to upgrade your sedan to a monster truck and sliming the entire windscreen with egg.
Oh, and with the windows wound up and stuck closed.
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.
Offline
I used testing a approximately 2 weeks ago and back then the packages weren't split (At least I didn't have two different kernel-headers packages on my system).
And regarding the kernel-headers 2.6.32 package in core while the kernel itself is 2.6.31? Why's that?
My victim you are meant to be
No, you cannot hide nor flee
You know what I'm looking for
Pleasure your torture, I will endure...
Offline
And regarding the kernel-headers 2.6.32 package in core while the kernel itself is 2.6.31? Why's that?
because of what allan said and doesn't need to follow your kernel version.
Last edited by wonder (2009-12-22 12:34:40)
Give what you have. To someone, it may be better than you dare to think.
Offline
@ Dheart: A somewhat related thread: http://bbs.archlinux.org/viewtopic.php?id=49105
Evil #archlinux@libera.chat channel op and general support dude.
. files on github, Screenshots, Random pics and the rest
Offline
I know that they don't need to match by version, just that usually the kernel is the first thing upgraded and after that come the headers, not the other way around...
My victim you are meant to be
No, you cannot hide nor flee
You know what I'm looking for
Pleasure your torture, I will endure...
Offline
I know that they don't need to match by version, just that usually the kernel is the first thing upgraded and after that come the headers, not the other way around...
usually is like that but now there are a few bugs concerning kernel 2.6.32 kernel and can't be moved from testing until those are fixed.
Give what you have. To someone, it may be better than you dare to think.
Offline
I've seen that last sentence many times now, and wonder whether anyone actually uses [testing] without subscribing there. It would be insane, like deciding to upgrade your sedan to a monster truck and sliming the entire windscreen with egg.
I'm guilty of using [testing] without being suscribed to ML for over 5 years (dev ML hasn't been public for that long, IIRC). I'm alive.
Offline
ngoonee wrote:I've seen that last sentence many times now, and wonder whether anyone actually uses [testing] without subscribing there. It would be insane, like deciding to upgrade your sedan to a monster truck and sliming the entire windscreen with egg.
I'm guilty of using [testing] without being suscribed to ML for over 5 years (dev ML hasn't been public for that long, IIRC). I'm alive.
Well, lets call that luck... I frequently post a message saying "now is probably not a good time to update" message during big rebuilds.
Offline