RE: Rebuilding the Kernel Mini HOW TO
No wonder none of the documentation around is exactly right or up to date!
For me this needs to be translated into Window-speak. In windows, a link is
like a file that when it is clicked, opens another file. I do not know what
is needed here, but what worked, and the only thing that worked was a "link"
in /usr/src/linux/ (in Windows there could not be such a thing as a link
that was /usr/src/linux) that was named kernel-source-2.4.18 and to "make
xconfig" you needed to cd to /usr/src/linux/kernel-source-2.4.18
I am not sure either that this is necessary, and it sure looks useless, but
I was following the instructions in one of those references...the one that
used the xconfig GUI.
And doing it as it is written here worked (I was able to rebuild and use my
kernel this way).
Alternatively, I think cd to usr/src/kernel-source-2.4.18/ (not a link)
would also work for xconfig, but that would not follow the suggestion from
elsewhere that one should not build the package in usr/src the way I read
Madness! All I can say is that it seems this effort to get this straight
will be worth it in the end for other Windows converts.
Mike Olds www.buddhadust.org
From: Russell [mailto:firstname.lastname@example.org]
Sent: Monday, October 14, 2002 6:09 PM
Subject: Re: Rebuilding the Kernel Mini HOW TO
Michael Olds wrote:
> Thank you,
> I am still in a fog in terms of simple things like symlinks. What you want
> is to end up with a link in the linux directory called
> that links to /usr/src/kernel-source-2.4.18. So how should that be said?
> [ ]1.d create a symbolic link to kernel-source-2.4.18 from /usr/src/linux
> $ ln -s /usr/src/kernel-source-2.4.18 /usr/src/linux
No. I don't know if you even *need* the linux symlink. But if you
do, the symlink is /usr/src/linux and it points to
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact