Mailinglist Archive: opensuse (3261 mails)
| < Previous | Next > |
Re: [SLE] Kernel too big error
- From: Philipp Thomas <pthomas@xxxxxxx>
- Date: Mon, 2 Apr 2001 08:00:38 +0200
- Message-id: <20010402080038.C11704@xxxxxxxxxxxxxxxx>
* Rick Green (rtg@xxxxxxxx) [20010402 07:28]:
> 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='?
Look back in the thread and you'll find everything. By default, it'll not
give it a unique name. But I posted my changed zlilo rule for
arch/i386/boot/Makefile that'll append the kernel release to vmlinuz and
System.map, thus making them unique. The only thing you have to do manually
is to create a new entry in /etc/lilo.conf.
> 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?
Search our support database for the keyword initrd and you'll find an
article I wrote that explains what initrd is all about, which would lead too
far here.
Philipp
--
Philipp Thomas <pthomas@xxxxxxx>
Development, SuSE GmbH, Schanzaecker Str. 10, D-90443 Nuremberg, Germany
Penguins shall save the dinosaurs
-- Handelsblatt about Linux on S/390
> 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='?
Look back in the thread and you'll find everything. By default, it'll not
give it a unique name. But I posted my changed zlilo rule for
arch/i386/boot/Makefile that'll append the kernel release to vmlinuz and
System.map, thus making them unique. The only thing you have to do manually
is to create a new entry in /etc/lilo.conf.
> 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?
Search our support database for the keyword initrd and you'll find an
article I wrote that explains what initrd is all about, which would lead too
far here.
Philipp
--
Philipp Thomas <pthomas@xxxxxxx>
Development, SuSE GmbH, Schanzaecker Str. 10, D-90443 Nuremberg, Germany
Penguins shall save the dinosaurs
-- Handelsblatt about Linux on S/390
| < Previous | Next > |