[TriLUG] my latest kernel attempt

[Roy Vestal]

Agreed. IIRC, the depndencies set themselves to the EXTRAVERSION in the 
Makefile, so the way you are running it I think is causing the 
dependencies to go to one dir in the /lib/modules directory, and when 
you create the kernel, it looks in another.

Here's my way. This is on RedHat Linux ( I think Jeremy and I do the 
same thing):

cd /usr/src/linux

make mrproper

vi Makefile - edit EXTRAVERSION info

cp ../.config .config  (copy my .config file from previous kernel if I 
have one for the machine)

make oldconfig ( may no longer be needed, but old habits...)

make xconfig (or menuconfig if X is not present) and set kernel parameters

make dep clean bzImage modules modules_install (yes, I run these all as 
one command)

go get snack, go get coffee, watch tv <g!>

cp arch/i386/boot/bzImage /boot/vmlinuz-#.#.##-EXTRAVERSION (kernel 
version plus EXTRAVERSION line in Makefile)

cp System.map /boot/System.map-#.#.##-EXTRAVERSION(kernel version plus 
EXTRAVERSION line in Makefile)

mkinitrd /boot/initrd.img-#.#.##-EXTRAVERSION (kernel version plus 
EXTRAVERSION line in Makefile)

edit /etc/grub.conf (I don't use lilo anymore) and add lines for newest 
kernel

reboot and test

HTH.

Just my $0.02 ... Change requested


Jeremy Portzer wrote:

>On Wed, 2002-11-27 at 16:10, Greg Brown wrote:
>  
>
>>My latest kernel custom attempted ended, yet again, in failure.  
>>Bummer.  Here's a step-by-step of what I did and what I (didn't) manage 
>>to accomplish.
>>
>>all steps as root
>>
>>cd /usr/src/linux-2.4
>>
>>make mrproper (returns lots of STDOUT)
>>
>>make xconfig
>>	(make changes)
>>	Save and Exit
>>
>>make dep	
>>
>>make clean
>>
>>vi Makefile
>>	change EXTRAVERSION to -3custom-greg
>>	save and exit
>>    
>>
>
>Hi Greg,
>
>As we've said before, you need to run "make dep" (and then make clean)
>*after* changing the EXTRAVERSION, not before.  I normally make this
>change (if I'm going to) as the first step (after make mrproper).  I
>don't know if this is your actual problem, but I would strongly
>recommend this change in procedure.
>
>--Jeremy
>
>_______________________________________________
>TriLUG mailing list
>    http://www.trilug.org/mailman/listinfo/trilug
>TriLUG Organizational FAQ:
>    http://www.trilug.org/~lovelace/faq/TriLUG-faq.html
>
>  
>