Well you are right, John I did unzip before I removed
the symlink and so I overwrote the 2.0.36 source
files.
Will this affect any of my devices after a reboot?
This morning when I rebooted it did not start
up my eth0 card, and I was wondering if this had
anything
to do with it. But I also upgraded my kerneld
from 2.1.85 to 2.1.121.
Maybe this is what is causing the initialisation of
eth0 at startup.
It will not even start when I go into X-Win and
click on activate from the Kernel Config menu.
Any ideas?
Shane
--- intalt <[EMAIL PROTECTED]> wrote:
> When you installed linux, it made a directory for
> your old (current)
> kernel, i.e. linux-2.0.36, and made a symbolic link
> to it called "linux".
> You have to make a directory called linux-2.2.2
> (well, you can call
> it whatever you want, but it's a little easier to
> keep up with this way,
> and it's how almost everyone does it, so don't try
> to be special =] )
> Anyway, after you make the new directory (mkdir
> linux-2.2.2) and
> remove the old symlink (rm linux), you make a new
> symlink to your
> new kernel directory (ln -s linux-2.2.2 linux). When
> you decompress/
> untar the kernel source (tar -xvzf
> linux-2.2.2.tar.gz), it goes to ./linux,
> that is why you make the symlink.
>
> If you did not remove the old symlink before you
> unarchived the source,
> you overwrote you old source. If you removed the
> symlink, but didn't make
> a new symlink/directory pair, then the archive made
> a directory called
> "linux"
> and put the source in there.
>
> Hope that clears it up, if not, feel free to ask
> again.
>
>
>
> After I run the command tar xvzf linux-2.2.2.tar.gz
> what should I be left with?
> It does not seem to have extracted the files to a
> new
> directory of linux-2.2.2. Is this not what is
> supposed
> to happen?
>
> Shane
>
>
>
>
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
