| View previous topic :: View next topic |
| Author |
Message |
thom_raindog
Guru
Joined: 16 May 2008
Posts: 400
|
 Posted: Mon Jul 28, 2008 7:05 am Post subject: Kernel symlink question |
 |
|
Hi there,
assuming I have /usr/src/linux pointing at the sources of Kernel A, but I use (very slightly older) Kernel B.
Will that pose a problem?
More specifically, will a
| Code: |
emerge --update --newuse --deep --empty world
|
mess things up? Do I understand correctly that some/all packages are compiled against the kernel sources (heresay only, I am no expert by any means  ) and therefore I could get in trouble in the above szenario? |
|
| Back to top |
|
 |
zyko
l33t
Joined: 01 Jun 2008
Posts: 620
Location: Munich, Germany
|
| Posted: Mon Jul 28, 2008 8:14 am Post subject: |
|
|
| Quote: | assuming I have /usr/src/linux pointing at the sources of Kernel A, but I use (very slightly older) Kernel B.
Will that pose a problem? |
Generally no. When emerging stuff, it may be a problem.
| Quote: | | Do I understand correctly that some/all packages are compiled against the kernel sources (heresay only, I am no expert by any means ) and therefore I could get in trouble in the above szenario? |
A few packages need information from the kernel configuration/sources. For example, the proprietary nvidia drivers read some stuff from /usr/src/linux and they will only work with the kernel they were built against.
If you don't want to point the symlink to the kernel you actually use, for whatever reason, I suggest you delete the symlink altogether in order to not emerge anything against the wrong kernel. Packages that need a kernel will fail and that will in turn give you valuable information on how to proceed. |
|
| Back to top |
|
|
thom_raindog
Guru
Joined: 16 May 2008
Posts: 400
|
| Posted: Mon Jul 28, 2008 9:34 am Post subject: |
|
|
Aha.. thanks.
Now, to get to the core of my "problem":
After some fiddling with a new kernel source and not getting my newest kernel to work I went back to the older one that worked fine.
I forgot, however, to change the symlink back.
At some point then I did the abovementioned update including --empty which built (pretty much?) all my system new since I changed some major stuff.
This morning I DID get the latest source to compile and produce a working kernel, so the whole thing is probably obsolete by now. But, understanding you correctly, as long as everything works fine, I need not worry?
(As said, by this morning I am fine anyway, since I built that latest kernel and the update was done with the symlink pointing to the very same source..) |
|
| Back to top |
|
|
zyko
l33t
Joined: 01 Jun 2008
Posts: 620
Location: Munich, Germany
|
| Posted: Mon Jul 28, 2008 9:52 am Post subject: |
|
|
| Quote: | | long as everything works fine, I need not worry? |
Yupp. If it ain't b0rked, don't recompile it 
AFAIK there are very few packages that need the kernel. There seem to be none in system -- those are the important ones anyway, so you know you will at least be able to boot properly. |
|
| Back to top |
|
|
cyrillic
Watchman
Joined: 19 Feb 2003
Posts: 7313
Location: Groton, Massachusetts USA
|
| Posted: Mon Jul 28, 2008 5:16 pm Post subject: |
|
|
If you have gentoolkit installed, you can check which packages would benefit from rebuilding against the new kernel sources.
| Code: | # equery depends virtual/linux-sources
[ Searching for packages depending on virtual/linux-sources... ]
net-firewall/iptables-1.4.1.1 (kernel_linux? virtual/linux-sources)
sys-apps/hal-0.5.11-r1 (kernel_linux? virtual/linux-sources)
sys-apps/lm_sensors-2.10.4 (kernel_linux? virtual/linux-sources)
(amd64? >=virtual/linux-sources-2.5)
(ppc? >=virtual/linux-sources-2.5)
(x86? >=virtual/linux-sources-2.5) |
In my case, there are only 3 out of 900+ packages that I should rebuild. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
