Peter Ruskin wrote:
ebegin Checking that /usr/src/linux is linked to booted kernel...
if [ /usr/src/linux-$(uname -r) != $(ls -l /usr/src/linux|cut -f2
-d\|cut -f2,3,4 -d' ') ]
This looks more complicated than it really should be. Just run ln on reboot
(stolen from your post):
rm -f
Norberto Bensa schreef:
Peter Ruskin wrote:
ebegin Checking that /usr/src/linux is linked to booted kernel...
if [ /usr/src/linux-$(uname -r) != $(ls -l /usr/src/linux|cut
-f2 -d\|cut -f2,3,4 -d' ') ]
This looks more complicated than it really should be. Just run ln
on reboot
051109 Holly Bostick wrote:
Can someone tell me on what basis this *needs* to be done
as a standard operation? Not getting it at all.
How many kernels does one keep in a bootable state, anyway
-- and use commonly, without needed external modules, no less --
that this would be necessary?
On Wed, Nov 09, 2005 at 10:28:04AM -0500, Philip Webb wrote:
051109 Holly Bostick wrote:
Can someone tell me on what basis this *needs* to be done
as a standard operation? Not getting it at all.
How many kernels does one keep in a bootable state, anyway
-- and use commonly, without
On Thu, 10 Nov 2005 04:54, Holly Bostick wrote:
Secondly, you're *using* 2.6.14, and you're keeping 2.6.12 around as a
fallback. It's very unlikely you're going to actually boot into 2.6.9,
and while you may boot into 2.6.12, you are not in fact doing so
(because 2.6.14 is working OK).
So
On Wed, Nov 09, 2005 at 03:35:42PM +0100, Holly Bostick wrote:
Norberto Bensa schreef:
Peter Ruskin wrote:
ebegin Checking that /usr/src/linux is linked to booted kernel...
if [ /usr/src/linux-$(uname -r) != $(ls -l /usr/src/linux|cut
-f2 -d\|cut -f2,3,4 -d' ') ]
This looks
Rumen Yotov wrote:
On Tue, 2005-11-08 at 17:18 +, Digby Tarvin wrote:
Something which I havn't found any explicit elaboration of in the
documentation...
The convention in the Linux/gentoo filesystem seems to be to have a unique
directory for each installed kernel in /usr/src, with a
On Wed, 9 Nov 2005 16:34:03 +, Digby Tarvin wrote:
Norbertos suggestion and Peters refinement were useful to me
as examples of one plausible interpretation of what /usr/src/linux
symlink should be - a shorthand way of finding the source for the
running kernel.
But it is not. As soon as
Digby Tarvin schreef:
On Wed, Nov 09, 2005 at 03:35:42PM +0100, Holly Bostick wrote:
-- If you have some external module that compiles against the
kernel source, you most likely need it against *all* kernel
sources, not just the running one (so redirecting the link is only
of limited
- Original Message -
From: Philip Webb [EMAIL PROTECTED]
To: gentoo-user@lists.gentoo.org
Sent: Wednesday, November 09, 2005 10:28 AM
Subject: Re: [gentoo-user] use of /usr/src/linux symlink
051109 Holly Bostick wrote:
Can someone tell me on what basis this *needs* to be done
On Wed, Nov 09, 2005 at 11:59:43AM -0500, Chris Fairles wrote:
Changed my symlink to point to 2.6.12-gentoo-r10, compiling ndiswrapper
1.5 is using running kernel 2.6.13
..
make[2]: Entering directory `/usr/src/linux-2.6.13-gentoo-r3'
Building modules, stage 2.
MODPOST
Oops - seems like
On 11/9/05, Robert Crawford [EMAIL PROTECTED] wrote:
I use to not worry about making the linux symlink in /usr/src point to my
currently running kernel every time, but lately I've taken to redoing it
each time I compile a new kernel, as I've found more and more that emerging
programs look for
051109 Holly Bostick wrote:
Philip Webb schreef:
I have 2.6.14 working ok (still ~x86), but am keeping 2.6.12
2.6.9 around in case something unexpected happens with 2.6.14 .
However, if I want to use 2.6.12 , I will have to recompile Nvidia.
Why?
Yes (pink face): as I now realise after
On Tue, 08 Nov 2005 19:40:59 +0200
Rumen Yotov wrote:
Hi,
There seems to exist at least two current kernels - one is the kernel to
which /usr/src/linux points, this one is used by most (all ?)
kernel-module programs (i have 3 of them: nvidia, arpstar, loop-aes; had
also alsa-driver). When
On Thu, 10 Nov 2005 06:37, Robert Crawford wrote:
I guess it depends on how much updating and compiling you do as too how
aggrevating this would become, but since it's no big deal to change it, I'd
recommend doing it as a matter of course, so you don't have to stop and do
it during an emerge
Digby Tarvin schreef:
Something which I havn't found any explicit elaboration of in the
documentation...
The convention in the Linux/gentoo filesystem seems to be to have a
unique directory for each installed kernel in /usr/src, with a
symbolic link to the 'current' kernel directory
16 matches
Mail list logo
