1 |
The old way of doing things was to make the following two symlinks: |
2 |
|
3 |
/usr/include/linux -> /usr/src/linux/include/linux |
4 |
/usr/include/asm -> /usr/src/linux/include/asm |
5 |
|
6 |
Then the second would be linked to the correct set of asm headers for |
7 |
your architecture, etc, inside the linux kernel source tree. |
8 |
|
9 |
Somewhere along the lines, the symlinking idea became deprecated in |
10 |
favor of using a hard set of header files. I forget why this came to be |
11 |
but I agree that at some point, a newer kernel must render some portion |
12 |
of an old set of headers outdated. I think the linux-headers package is |
13 |
intended to be kept as up to date as possible to avoid interface |
14 |
changes/incompatibilities. Why it's not kept even and why the |
15 |
redundancy? Good questions. |
16 |
|
17 |
I would figure that if you wanted to manually maintain a hard set of |
18 |
headers and keep them installed in the correct places, you're free to do |
19 |
so but the linux-headers package has been properly maintained from my |
20 |
experience. |
21 |
|
22 |
My $0.02. |
23 |
|
24 |
On Mon, 2006-12-04 at 19:53 -0500, David Relson wrote: |
25 |
> Today when I ran "emerge -au world" I was surprised to see |
26 |
> |
27 |
> Calculating dependencies... done! |
28 |
> [ebuild U ] sys-kernel/linux-headers-2.6.17-r2 [2.6.17-r1] |
29 |
> |
30 |
> because I'm presently running a 2.6.19-gentoo-r2 kernel (built from |
31 |
> gentoo-sources-2.6.19-r1 using genkernel). |
32 |
> |
33 |
> When I run "emerge -C linux-headers" it warns me that |
34 |
> |
35 |
> !!! 'sys-kernel/linux-headers' is part of your system profile. |
36 |
> !!! Unmerging it may be damaging to your system. |
37 |
> |
38 |
> Common sense tells me that anything 2.6.19 renders all things |
39 |
> obsolete that relate to 2.6.17. Am I right? |
40 |
> |
41 |
> Also, where is it recorded that linux-headers 2.6.17-r2 is important? |
42 |
> I suspect I ought to delete that info as well. |
43 |
> |
44 |
> Thanks. |
45 |
> |
46 |
> David |
47 |
|
48 |
-- |
49 |
Statux <statux@×××××××××.net> |