Messages in this thread | | | Date | Tue, 11 Jul 2006 13:05:59 -0400 | From | Jeff Garzik <> | Subject | Re: [klibc] klibc and what's the next step? |
| |
Olaf Hering wrote: > On Tue, Jul 11, H. Peter Anvin wrote: > >> When you say "loop mount code" I presume you mean legacy initrd support >> (which doesn't use loop mounting.) Legacy initrd support is provided to >> be as compatible as possible, obviously. > > Yes. > To create the initrd you needed a loop file, at least for ext2, minix etc. > > But so far, the arguments are not convincing that kinit has to be in the > kernel tree.
Two are IMO fairly plain:
* Makes sure you can boot the kernel you just built.
* Makes it easier to move stuff between kernel and userspace.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |