According to Adrian Bolzan: While burning my CPU.
>
>
> At 15:00 22/11/98 -0300, Joaquin wrote:
> >Hi to all:
> >
> > I want to upgrade kernel's RedHat 5.1. I have 2.0.34 and I have
> >downloaded linux-2.0.35.tar.gz. The matter is I don't now how I have to
> >install it.
> >
>
> Firstly, the 2.0.36 kernel is out now so if you have the time you might
> want to get that one instead of 2.0.35. There is also a HOWTO on compiling
> the kernel. It is in /usr/src/HOWTO/kernel.html and if you had RH it is
> probably in html format, but gzipped up. So just run gunzip kernel.html.gz
> and you can look at the HOWTO.
>
>
> > First one, I am not sure if I have to install the kernel source 2.0.34
> >or if it is just installed when I intalled the first CD of RedHat. I have
> >the source in the second CD. Do I have to install it too?
> >
>
> In a normal RH install i don't think the source is installed. No problem
> because you have the new kernel source linux-2.0.35.tar.gz
>
> So, the first thing to do is check if you have the 2.0.34 source installed.
> Go to /usr/src and type 'ls -l' (withought the '). Do you have a
> directory called linux-2.0.34? that is the src directory. If you do, see
> if anything is in it. If not then you can delete it. If there is i
> suggest you tar.gz it.
>
> To do that, get into the /usr/src directory and type:
> tar zcvf linux-2.0.34 old_tree.tar.gz
tar czf linux-2.0.34.tar.gz linux/ or
tar czf linux-2.0.34.tar.gz linux-2.0.34/
Considering the name above is the same name as an "origanal" source archive,
i would use linux-2.0.35.pa3gcu.tar.gz just in case the contents are
different to the "origanal". Using your machine name for this sort of thing
is a good idea.
>
> check if the linux-2.0.34 and the old_tree.tar.gz should go the other way
> using 'man tar' or 'info tar'.
>
> ok, once that is done you may also have a symlinked file called linux which
> in your ls -l will appear like: linux -> linux-2.0.35
> If you do, delete the file 'linux'.
>
> No copy your linux-2.0.35.tar.gz source file into the /usr/src directory.
> Type:
> tar ztvf linux-2.0.35
No need, ALL linux-kernel archives have the same format each and every time,
the archive will look for a directory called linux be it a symbolic link or
a hard directory, if none is found a directory called linux will be created.
>
> This command will let you see if the tar file makes it's own directory. It
> will list a lot of files quickly, all starting with 'linux/', which means
> that a directory called linux will be made.
>
> no problem now. Just type:
> tar zxvf linux-2.0.35
> and let it go. when it is finished you should change the name from linux
> to linux-2.0.35, so just go:
> mv linux linux-2.0.35
> then make a symlink from a new file called 'linux' to 'linux-2.0.35' using:
> ln -s linux-2.0.35 linux
It should realy be;
cd /usr/src
rm linux # Remove the old symlink.
OR if "linux" is a hard directory;
mv linux linux-2.0.34
mkdir linux-2.0.35 # Create the new source dir.
ln -s linux-2.0.35 linux # Link the 2 together.
tar xzf /path/to_location_of/linux-2.0.35.tar.gz
The archive does not need to be in /usr/src and drop the -v(erbose) folks
get dizzy when the screen scrools so fast, (i do)..
No further need to "rename" any directory like you suggest.
>
> check with the manual 'man ln' or 'man symlink' to make sure the order of
> the two names is correct, that is the new symlinked file linux is the last
> argument. If the command should be: 'ln -s linux linux-2.0.35' then you
> will just have to delete the file linux and the linux-2.0.35 directory and
> untar the source file again. then just use the right symlink command.
> sorry i can't be a bit more specific- i can never remember the order. i
> always check myself.
When createing symlinks its 'ln -s hard_dir_name linux' in this case;
ln -s linux-2.0.35 linux
the symlink name is the last name. You will now see;
lrwxrwxrwx 1 root root 12 Nov 22 13:52 linux -> linux-2.0.35
drwxr-xr-x 15 root root 1024 Aug 6 14:35 linux-2.0.35
I have commented on this mail as there have been so many mails about this
particular subject, most of then seem to be related to a wrong directory
structure resulting in things like patch and make failing, hence this mail.
>
> And that is it!
>
> then you can just:
> cd linux
> and then say:
> make xconfig
> (assuming you are using Xwindows)
> and start to configure your kernel!
>
> check the HOWTO first though, as it goes through all this and more. ;-)
>
> Hope that helps
>
> adrian b.
>
>
>
> -------------------------------------------------------
> Some oxygen molecules help fires burn while others help
> make water, so sometimes it's brother against brother.
>
>
--
Regards Richard.
[EMAIL PROTECTED]
