| 1 |
Ben Munat wrote: |
| 2 |
> So, you are saying that it is fine to go ahead and emerge |
| 3 |
> "linux-headers-2.6.8.1-r2" even though I'm running an old 2.4 kernel |
| 4 |
> (with gss sources, no less)? |
| 5 |
> |
| 6 |
|
| 7 |
Definitely not. It is safe to build applications against 2.4 headers and |
| 8 |
to run those applications with a 2.6 kernel. The reverse is not the |
| 9 |
case. There is no specific requirement for you to switch your |
| 10 |
make.profile at this time. But, in order to protected yourself against |
| 11 |
future developments, I'd suggest that you do something like this |
| 12 |
(assuming x86 arch): |
| 13 |
|
| 14 |
# cd /etc |
| 15 |
# rm make.profile |
| 16 |
# ln -s ../usr/portage/profiles/default-linux/x86/2005.0/2.4 make.profile |
| 17 |
|
| 18 |
That should solve the problem (judging by the amount of misguided |
| 19 |
questions I've seen on IRC, I'm surprised that this hasn't been made |
| 20 |
clearer). If you need to make any futher customisations to the profile |
| 21 |
then you should either override it or augment it with a further |
| 22 |
"cascade" in a PORTDIR_OVERLAY. |
| 23 |
|
| 24 |
Aside from all of this, when you change your system headers then it is |
| 25 |
probably not a bad idea to rebuild any packages that you have installed |
| 26 |
which are affected by the headers. glibc is by far the most important, |
| 27 |
but this one-liner will handle the lot (it won't upgrade anthing though): |
| 28 |
|
| 29 |
# ls /var/db/pkg/*/*/*.ebuild | xargs grep -l virtual/os-headers | cut |
| 30 |
-d "/" -f 5,6 | egrep -v "linux(26)?\-headers" | sed -e "s/\(.*\)/=\1/" |
| 31 |
| xargs emerge --oneshot |
| 32 |
|
| 33 |
Regards, |
| 34 |
|
| 35 |
--Kerin Francis Millar |
| 36 |
-- |
| 37 |
gentoo-server@g.o mailing list |
Archives