Re: LILO and b*zImage?
Hans Lermen (lermen@elserv.ffm.fgan.de)
Fri, 26 Apr 1996 09:51:08 +0200 (MET DST)
- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Dan McLaughlin: "Re: Solved: 1.3.94: open () still slower than 1.2.13"
- Previous message: Paul Schmidt: "Re: Solved: 1.3.94: open () still slower than 1.2.13"
- In reply to: Alex Pikus: "LILO and b*zImage?"
- Next in thread: Linus Torvalds: "Re: signal(SIGFPE,SIG_IGN), possible solution?"
- Reply: Linus Torvalds: "Re: signal(SIGFPE,SIG_IGN), possible solution?"
- Reply: Linus Torvalds: "Re: signal(SIGFPE,SIG_IGN), possible solution?"
- Reply: Gerard Roudier: "Re: signal(SIGFPE,SIG_IGN), possible solution?"
- Reply: Kai Henningsen: "Re: signal(SIGFPE,SIG_IGN), possible solution?"
On Thu, 25 Apr 1996, Alex Pikus wrote:
>
> A while back someone posted about the new b*zImage format and the latest LILO that accepts it ...
>
> Could someone please elaborate on:
>
> What version of LILO?
LILO18dev3
LOADLIN-1.6pre11
(the final versions will be released soon)
SYSLINUX-3.0
> Is there a FAQ or HOWTO?
linux/Documentation/initrd.txt,
linux/Documentation/Configure.help (CONFIG_BLK_DEV_INITRD),
ftp://elserv.ffm.fgan.de/pub/linux/loadlin-1.6/ANNOUNCE-LILO+LOADLIN
> Does this apply only to large kernels or ALL kernels?
the new features are available for zImages as well as for bzImages,
though only bzImages gets loaded high.
> What are the benefits?
bzImages can be 1Meg compressed and will be loaded directly 'high',
an initial ramdisk can be loaded by the loader.
for more see the above mentioned docs.
Hans
<lermen@elserv.ffm.fgan.de>
- Next message: Dan McLaughlin: "Re: Solved: 1.3.94: open () still slower than 1.2.13"
- Previous message: Paul Schmidt: "Re: Solved: 1.3.94: open () still slower than 1.2.13"
- In reply to: Alex Pikus: "LILO and b*zImage?"
- Next in thread: Linus Torvalds: "Re: signal(SIGFPE,SIG_IGN), possible solution?"
- Reply: Linus Torvalds: "Re: signal(SIGFPE,SIG_IGN), possible solution?"
- Reply: Linus Torvalds: "Re: signal(SIGFPE,SIG_IGN), possible solution?"
- Reply: Gerard Roudier: "Re: signal(SIGFPE,SIG_IGN), possible solution?"
- Reply: Kai Henningsen: "Re: signal(SIGFPE,SIG_IGN), possible solution?"