| 1 |
Rumen Yotov wrote: |
| 2 |
|
| 3 |
>On Tue, 2005-11-08 at 17:18 +0000, Digby Tarvin wrote: |
| 4 |
> |
| 5 |
> |
| 6 |
>>Something which I havn't found any explicit elaboration of in the |
| 7 |
>>documentation... |
| 8 |
>> |
| 9 |
>>The convention in the Linux/gentoo filesystem seems to be to have a unique |
| 10 |
>>directory for each installed kernel in /usr/src, with a symbolic link to |
| 11 |
>>the 'current' kernel directory named /usr/src/linux.. |
| 12 |
>> |
| 13 |
>>The question is - is this just a user convenience, or will parts of |
| 14 |
>>the system break if it is not maintained correctly? |
| 15 |
>> |
| 16 |
>>The reason I ask is that if I have several kernels which I have configured |
| 17 |
>>grub to allow me to select from at boot time, where should this symlink |
| 18 |
>>point? The newest kernel? An experimental one being worked on? The one most |
| 19 |
>>recently booted from. If the latter case then it is likely to be wrong for |
| 20 |
>>a finite period following boot until the system has come up far enough to |
| 21 |
>>allow me to update it. |
| 22 |
>> |
| 23 |
>>Anyone know what is likely to break (if anything) if I boot from a kernel |
| 24 |
>>other than the one which corresponds to the directory /usr/src/linux points |
| 25 |
>>to, and neglect to update the link? Does it direct (for instance) the target |
| 26 |
>>directory for an emerge of new kernel components? Or does it perhaps have to |
| 27 |
>>point to the kernel being built during any recompile? |
| 28 |
>> |
| 29 |
>>Regards, |
| 30 |
>>DigbyT |
| 31 |
>>-- |
| 32 |
>>Digby R. S. Tarvin digbyt@××××××.com |
| 33 |
>>http://www.digbyt.com |
| 34 |
>> |
| 35 |
>> |
| 36 |
>Hi, |
| 37 |
>There seems to exist at least two current kernels - one is the kernel to |
| 38 |
>which /usr/src/linux points, this one is used by most (all ?) |
| 39 |
>kernel-module programs (i have 3 of them: nvidia, arpstar, loop-aes; had |
| 40 |
>also alsa-driver). When you compile/recompile any one of them they use |
| 41 |
>the kernel sources pointed by /usr/src/linux. Patch kernel sources too |
| 42 |
>(e.g. "l7-filter"). |
| 43 |
>The second kernel is your running kernel (available by "uname -r") this |
| 44 |
>one is the one actually running at any givenn time. Don't have any |
| 45 |
>examples of something using this one. Anybody here? |
| 46 |
>HTH.Rumen |
| 47 |
> |
| 48 |
> |
| 49 |
Changed my symlink to point to 2.6.12-gentoo-r10, compiling ndiswrapper |
| 50 |
1.5 is using running kernel 2.6.13 |
| 51 |
|
| 52 |
#ls -al |
| 53 |
lrwxrwxrwx 1 root root 24 Nov 8 12:57 linux -> linux-2.6.12-gentoo-r10/ |
| 54 |
|
| 55 |
#make |
| 56 |
make -C driver |
| 57 |
make[1]: Entering directory `/root/ndiswrapper-1.5/driver' |
| 58 |
make -C /lib/modules/2.6.13-gentoo-r3/build |
| 59 |
SUBDIRS=/root/ndiswrapper-1.5/driver \ |
| 60 |
DRIVER_VERSION=1.5 |
| 61 |
make[2]: Entering directory `/usr/src/linux-2.6.13-gentoo-r3' |
| 62 |
Building modules, stage 2. |
| 63 |
MODPOST |
| 64 |
|
| 65 |
Chris |
| 66 |
-- |
| 67 |
gentoo-user@g.o mailing list |
Archives