Re: [proaudio] emerge rt-sources && ln -s linux -> rt-sources |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/proaudio Archives
]
- To: proaudio@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [proaudio] emerge rt-sources && ln -s linux -> rt-sources
- From: "Mark Knecht" <markknecht@xxxxxxxxx>
- Date: Fri, 26 May 2006 20:55:28 -0700
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=L8w4ZAPGIl+EhCrdLQe9E+8QfHYJoyoIAvVRhxX1f3zMUcHL2YGpuNeIwOQNcu8tnq0AnvslhSGGTPVMsTbaAxdXKqEc+M6HAP/Q/kG4CiqUG185gSZIMsD/yJY7ypCIXnRzNUT/thtUrPB6yiQb+MC1fUy/NJLErbJMXDuN1ic=
On 5/26/06, Colin Shapiro <cmshapiro@xxxxxxxxx> wrote:
Supposedly the "symlink" USE flag is supposed to control this behavior, but
for quite a while now, I have noticed that even with USE="-symlink", the
/usr/src/linux symlink is created anyway. This occurs even with
gentoo-sources.
Other than the minor inconvenience of having to issue a "ln -sf" command, I
fail to see how this is a big problem. How often do you really emerge a new
kernel?
Quite often. Probably 5-10 times per month...
Also, keep in mind that every time you emerge additional kernel sources, you
need to remerge any packages that build kernel modules so that these modules
are built for the new kernel. Take nvidia-glx for example; if you have
gentoo-sources and rt-sources installed, you will have to emerge nvidia-glx
once for each kernel. As such, changing the /usr/src/linux symlink around
isn't necessarily a bad thing.
I agree. However, if I am running 2.6.16-gentoo-r2 and emerge
rt-sources, I am not running rt-sources. rt-sources cannot run until I
configure it, build it, install it, change grub and reboot. In the
meantime I proceed to do work on my machine and later find out
mistakes are being made because the symlink is pointing to the wrong
kernel.
Further, I think that creating this link is not the Gentoo way. This
link is neither created, changed or destroyed when emerging
gentoo-sources or any of the other kernels. I think it should really
not be done here.
Cheers,
Mark
- Colin
On 5/26/06, Mark Knecht <markknecht@xxxxxxxxx> wrote:
> Hi,
> After emerging rt-sources this evening as a test of the new -rt
> patches I found there was a new link in /usr/src point at
> linux-2.6.16-rt25.
>
> 1) Was this created by emerge rt-sources? IT seems ot be based on
> dates and times:
>
> lrwxrwxrwx 1 root root 17 May 26 17:26 linux -> linux-2.6.16-rt25
> drwxr-xr-x 19 root root 4096 May 26 17:26 linux-2.6.16-rt25
>
> 2) Do others agree with me that if it was created by emerge rt-sources
> that it should NOT be?
>
> Just because I emerge a new kernel source tree does not mean I want
> it to become the default kernel source for the system. Since other
> emerges reference this link to tell it what code to build for
> different modules, such as realtime-lsm or video adapters, I want to
> make sure I control this link and not emerge.
>
> Long term this will cause problems if the kernel pointed to doesn't
> match the default kernel that's booted by grub after a cold boot.
>
> Comments?
>
> Thanks,
> Mark
>
>