On Thu, Sep 01, 2005 at 12:12:00AM +0200, Jesper Juhl wrote: > b) add a new boot option telling the kernel the name of some file in > initrd or similar from which to load additional options. a file in initrd isn't a good choice; as the initrd is generally a fix image the point is some bootloaders might want to pass quite a bit of state to the kernel at times (i actually have this for a mip32 target where i construct a table and pass a pointer to that in, a tad icky but for lack of options) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: THE LINUX/I386 BOOT PROTOCOL - Breaking the 256 limit
- From: Jesper Juhl <[email protected]>
- Re: THE LINUX/I386 BOOT PROTOCOL - Breaking the 256 limit
- From: "H. Peter Anvin" <[email protected]>
- Re: THE LINUX/I386 BOOT PROTOCOL - Breaking the 256 limit
- References:
- Re: THE LINUX/I386 BOOT PROTOCOL - Breaking the 256 limit
- From: "H. Peter Anvin" <[email protected]>
- Re: THE LINUX/I386 BOOT PROTOCOL - Breaking the 256 limit
- From: Chris Wedgwood <[email protected]>
- Re: THE LINUX/I386 BOOT PROTOCOL - Breaking the 256 limit
- From: "H. Peter Anvin" <[email protected]>
- Re: THE LINUX/I386 BOOT PROTOCOL - Breaking the 256 limit
- From: Chris Wedgwood <[email protected]>
- Re: THE LINUX/I386 BOOT PROTOCOL - Breaking the 256 limit
- From: Jesper Juhl <[email protected]>
- Re: THE LINUX/I386 BOOT PROTOCOL - Breaking the 256 limit
- Prev by Date: RE: FW: [RFC] A more general timeout specification
- Next by Date: Re: THE LINUX/I386 BOOT PROTOCOL - Breaking the 256 limit
- Previous by thread: Re: THE LINUX/I386 BOOT PROTOCOL - Breaking the 256 limit
- Next by thread: Re: THE LINUX/I386 BOOT PROTOCOL - Breaking the 256 limit
- Index(es):