Jesper Juhl wrote:
Well, it wouldn't have to be initrd specifically. Generally what's needed is *some* way to tell the kernel "please read more options from location <foo>". The interresting bit is what <foo>'s supposed to be.
This is what initramfs (as opposed to initrd) does quite well. -hpa - 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: Alon Bar-Lev <[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
- 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: THE LINUX/I386 BOOT PROTOCOL - Breaking the 256 limit
- Next by Date: Re: [PATCH] Fix kprobes handling of simultaneous probe hit/unregister
- 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):
