On Thu, 09 Sep 1999, you wrote:
> Is this because of the symlink?
I believe so. At least it's my (limited) experience that this
behavior occurs.
> Can I remove the symlink so it wont
> overwrite the 2.2.9-27?
I don't know.
> If this does work do I need to make a new one to
> the sources I want to compile?
Probably, but I don't know. :-)
>Why is the link there?
>
I'm afraid my knowledge is based on unpacking a "tarball" kernel
source this past holiday weekend (for us in the United States it was
a holiday weekend <G>) and being surprised that it overwrote the
source for my previous kernel. I "moved" the directory to a new name
(2.2.12) to reflect the contents of the kernel.
I would strongly suggest you try making a directory FOR the contents
of the tarball and making the symlink point to that directory.
Probably have to do an "ln -s --force" to get it to work.
John
