🚀 go-pugleaf

In article <mi34HD1w165w@electech.dialix.oz.au>, owen@electech.dialix.oz.au (Owen Crocker) writes:
|> 
|> Yahoooo!!!! I finally managed to compile a kernel.......
|> 
|> Too bloody bad it was the wrong one :-(
|> 
|> "make zImage" worked finally, after I discovered mkswap and swapon.
|> 
|> What's this about my Slackware distribution using vmlinuz instead
|> of zImage ???
|> 
|> /etc/lilo.conf has a line "image=/vmlinuz" and I guess that is what is
|> currently booting, but "make vmlinuz" doesn't do me any good.
|> I don't seem to have a vmlinuz.c or anything close.
|> 
|> Am I asking the right question ?
|> 

No,
the kernel can have any name, Slackware defaults to vmlinuz,
source code defaults to zImage, you could call it OwenCracker.
The only thing that matters is the name in lilo.conf.
So far you have done everything right. 
Most of the info you need is contained in the README
file in /usr/src/linux, along with the kernel source.
In brief; you can use the zImage file that
you created as your kernel as follows
- move zImage to /zImage
- edit lilo.conf -> image=/zImage
- run liloconfig to reconfigure lilo
- reboot

Read the README.
Make sure that you have a floppy you can boot from.

Martin

-- 
The world is sacred.  You cannot improve it.	| Martin Hofmann
If you try to change it, you will ruin it.	| Centre for Visual Sciences
If you try to hold it, you will lose it.	| ANU, Canberra
	Lao Tsu, "Tao Te Ching"			| Martin.Hofmann@anu.edu.au