Re: [Plug] Ok, attempt number two..+ CORRECTIONS

["LeRoy D. Cressy" <ldc@netaxs.com>]

make mrproper 	deletes and cleans everything, so if
		you call this after either 
			make config
			make menuconfig
			make xconfig
		you just hosed you new config files.

The proper order for compiling a kernel is:
	make config | make menuconfig | make xconfig
	make dep
	make bzImage
	make modules
	make modules_install

	The final bzImage is put in arch/???/boot/
	cp arch/???/boot/bzImage /boot/bzImage_02.xx.xx

	I like to attach the version of the kernel to the
	filename in /boot :-)

	I also make symbolic links in the / directory pointing
	to the kernels in /boot

	vmlinuz -> boot/bzImage_xx.xx.xx
	vmlinuz.old -> boot/bzImage_xx.xx.xx
	vmlinuz.dist -> boot/distribution kernel filename

	Thisway, after I make lilo pointing to the symbolic
	links in the root directory, I never have to hand edit
	/etc/lilo.conf again.  When I do a kernel compile I
	just change the symbolic links in the root directory
	and rerun lilo.



Vale_Kenny@vanguard.com wrote:
> 
> I;m trying to keep this simple as possible..
> RH 6.0
> Kernel 2.2.5 u/g to 2.2.10, no patches, whole kit-n-kaboodle
> is this the correct order..
> make menuconfig
> make mrproper
> make dep
> make bzImage
> make modules
> make modules-install
> copy bzImage to /boot
> edit lilo.conf
> run lilo
> 
> is there something I'm missing?
> 
> Peace , Vale
> 
> _______________________________________________
> Plug maillist  -  Plug@lists.nothinbut.net
> http://lists.nothinbut.net/mail/listinfo/plug

-- 
          0 0      L & R Associates
           "       Home Page:    http://www.netaxs.com/~ldc/
_______ooO ~ Ooo_______________________________________________

LeRoy D. Cressy     	 /\_/\		ldc@netaxs.com
Computer Consulting 	( o.o )		Phone (215) 535-4037
		 	 > ^ <		Fax   (215) 535-4285



_______________________________________________
Plug maillist  -  Plug@lists.nothinbut.net
http://lists.nothinbut.net/mail/listinfo/plug