| 1 |
On 10/31/2009 09:18 PM, Alan McKinnon wrote: |
| 2 |
> On Saturday 31 October 2009 20:09:37 Harry Putnam wrote: |
| 3 |
>> Nikos Chantziaras<realnc@×××××.de> writes: |
| 4 |
>>> The link is created only if you have the "symlink" USE flag enabled. |
| 5 |
>>> |
| 6 |
>>> Also, "Gentoo requires that the [...] symbolic link points to the |
| 7 |
>>> sources of the kernel you are running" is not entirely correct. It is |
| 8 |
>>> required only when you want to build something against that |
| 9 |
>>> kernel. |
| 10 |
>>> |
| 11 |
>>> . . . . Obviously, you need to create the symlink if you want to build |
| 12 |
>>> the newly installed kernel, even though the system is still running an |
| 13 |
>>> older one. |
| 14 |
>> |
| 15 |
>> Why is that obvious? That's what seemed confusing to me. |
| 16 |
>> |
| 17 |
>> Nothing about creating it with USE=symlin, eselect, or by hand is a |
| 18 |
>> problem. Or hard to follow, and I've always just done it by hand. |
| 19 |
>> |
| 20 |
> |
| 21 |
> Nikos is being kind to the document writers :-) |
| 22 |
> |
| 23 |
> In fact, the documentation is flat out wrong - there is no requirement for the |
| 24 |
> symlink to point to the currently running kernel. It must point to the kernel |
| 25 |
> sources you want to *configure* or use for an emerge that installs a kernel |
| 26 |
> driver. |
| 27 |
> |
| 28 |
> For instance, you might be running 2.6.31-r4 and also have 2.6.31-r3 |
| 29 |
> installed. To install nvidia-drivers, you must build it *twice* - against each |
| 30 |
> kernel you want to use it with (nvidia-drivers builds and installs a kernel |
| 31 |
> driver into /lib/modules/<kernel version>) |
| 32 |
|
| 33 |
It's a bit more obfuscated than that. Maybe nvidia-drivers work |
| 34 |
different, but ati-drivers will build against /usr/src/linux but install |
| 35 |
the actual modules in /lib/modules/running_kernel. If /usr/src/linux |
| 36 |
doesn't point to the running kernel, the modules will be installed in |
| 37 |
the wrong place. |
Archives