Hi,
On Fri, 9 Jun 2006, Michael Tokarev wrote:
> But I see a reason for kinit *now*, in its current form - it's
> compatibility. Later on, maybe the whole stuff can be removed entirely,
> to rely on external tools for booting.
The compatibility code is already in the kernel, just don't call it if
e.g. there's a /kinit in initramfs. We can add the hooks to the kernel to
pull whatever you want into the initramfs and with time we can remove
the old code.
Why create new (temporary?) compatibility code, if the current code is
working just fine?
bye, Roman
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
