Because that's the way Redhat themselves said to do it in their documentation
(granted, it was their 5.1 manual) and it has always worked for me.  

I really don't see any advantage to doing it your way as far as the modules are
concerned (not much difference in doing a vi versus a mv) but it really would
help keep the images straight.  

Thanks for the tip...it's easy to just keep doing something that works even if
it's not the best way!!!


Gerry



On 28-Dec-99 Stefan Smietanowski wrote:
> Hi.
> 
>> Prior to running this you should go into the /lib/modules directory and:
>> 
>> mv 2.2.16 2.2.12.old
> 
> Why?
> 
> vi /usr/src/linux/Makefile
> 
> edit the EXTRAVERSION= to include something like -20_r1 where r1 stands
> for release 1, then next recompile change it to r2, etc.
> 
> Use that naming scheme for the kernel too, etc.
> 
> That's what RedHat themselves recommend to do.
> 
> Result is that all modules will go into their own directory in
> /lib/modules/2.2.12-20_r1.
> 
> // Stefan


----------------------------------
E-Mail: Gerry Doris <[EMAIL PROTECTED]>
Date: 28-Dec-99
Time: 18:47:40

"The lyf so short, the craft so long to learne"  Chaucer
----------------------------------


-- 
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.

Reply via email to