| 1 |
On 11/28/05, Scott Stoddard <scott@×××××××××××.ca> wrote: |
| 2 |
> Neil Bothwick wrote: |
| 3 |
> > |
| 4 |
> > This thread is all about compiling kernel modules, which must be specific |
| 5 |
> > to either the running kernel or the intended kernel. Most packages take |
| 6 |
> > the latter option, using the symlink, which causes problems if the |
| 7 |
> > symlink is updated during an emerge -u world. |
| 8 |
> > |
| 9 |
> |
| 10 |
> IMO exactly why no one should ever really use the symlink USE flag... |
| 11 |
> |
| 12 |
> (Haven't read the whole thread either...long since deleted from my |
| 13 |
> mailserver.) |
| 14 |
> |
| 15 |
> Depending on the output of uname -r is foolish, as witnessed by the |
| 16 |
|
| 17 |
I don't think anybody was advocating _depending_ upon the output of |
| 18 |
uname -r, but using that to find the sources for the currently running |
| 19 |
kernel. As in: |
| 20 |
|
| 21 |
ls -l /lib/modules/`uname -r`/build |
| 22 |
|
| 23 |
Using uname -r in this context is unlikely to ever break, as then |
| 24 |
module loading would be broken. |
| 25 |
|
| 26 |
-Richard |
| 27 |
|
| 28 |
-- |
| 29 |
gentoo-user@g.o mailing list |
Archives