On Sun, 1 Apr 2001, Philipp Thomas wrote:
* cll muzh [Tue, 27 Mar 2001 22:00:11 +1200]:
Have a look in /usr/src/linux/arch/i386/boot. You will find your bzImage there. Copy it to /boot, and add configuration to lilo, and you are away!
Why don't you people just use 'make bzlilo'? That'll do all that's needed including calling LILO.
Well, I didn't know that target existed! Tell me more... 1) What does it call the resulting kernel? Does it choose a new, unique name, or will it overwrite /boot/vmlinuz or some other standard name? 2) Does it give me a new, unique 'label='? I must admit I'm leery of anything automatic, until I understand what's going on under the covers. ESPECIALLY with kernel re-compiles, I want to make absolutely sure that my old kernel won't be over-written, and the new kernel will selectable, but not default, in the lilo config. I'm tired of pulling the rug out from under myself! I haven't attempted a compile on a 7.1 system yet. One look at lilo.conf, where I saw initrd= instead of image=, and I knew I had some reading to do before I attempted it. Can you point me to a good starting point? What's in an initrd, and how do I build one? I've heard it allows one to boot systems with module-supported root filesystems, so I'm assuming it's a ramdisk filesystem which includes the /boot files as well as the necessary modules and module-loading utilities. Can I mount one using the loopback device to see what's included? What fstype? -- Rick Green "I have the heart of a little child, and the brain of a genius. ... and I keep them in a jar under my bed"