There is a reason for the simlink aproach. make zlilo or make bzlilo will copy a kernel to /vmlinuz and automatically run lilo. This means if the default kernel is vmlinuz in the root, thinks will just go. Many people however only create a 10-20 megabyte partition for /boot keeping the intire contents below cylinder 1024. The simlink keeps /vmlinuz below this magic cylinder. Now that most bioses and lilo support lba32 adressing, this problem should go away in the long term. The simlink aproach also means you have 1 simlink cluttering up the root directory and can put the rest of the kernels in /boot/* and referr to them as /boot/blah Most comercial unixes stored the kernel image (not images) in the root of the tree hence the historic convention. REgards, Kerry On Tue, Jan 09, 2001 at 07:40:27AM -0600, Kirk Wood wrote: > Janina, > > One thing that comes to mind here for me. I know that slackware puts the > kernel image in the root directory with a softlink in the /boot > directory. This can cause confusion as far as I can see. What I have found > is that you can put the image in the /root directory (which I go ahead and > put on the first available partition) and skip the softlink altogether. I > name the kernel something that will help me remember when I compiled it > and any special features. I can find nothing sacred about vmlinuz other > then that it is the common name scheme. But I have seen the same (or a > similar) problem where someone continued following the slackware original > setup. > > ======= > Kirk Wood > Cpt.Kirk at 1tree.net > > Cluelessness > There are no stupid questions, but there are a lot of > inquisitive idiots > > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > -- -- Kerry Hoath: kerry at gotss.eu.org Alternates: kerry at emusys.com.au kerry at gotss.spice.net.au or khoath at lis.net.au ICQ UIN: 62823451
