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