Re: [PATCH][retry-2] init: Introduce rootdir bootparm to select which dir to sys_chroot

H. Peter Anvin wrote:
> a. For as long as we keep throwing more crap into the kernel, kinit will
> not get merged, because it "provides no new functionality."

I'm not really familiar with kinit, but it sounds unfair to hinder new 
features because it would reduce the usefulness of another project.

kinit should have nothing to fear, as its purpose would not be to add new 
features, but rather to modularize the boot process, by replacing the 
current init, and thus allow for more flexibility to add/modify features.


Thanks!

--
Al
-
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/

---

• References:
  • Re: [PATCH][retry-2] init: Introduce rootdir bootparm to select which dir to sys_chroot
    • From: Bodo Eggert <[email protected]>
  • Re: [PATCH][retry-2] init: Introduce rootdir bootparm to select which dir to sys_chroot
    • From: "H. Peter Anvin" <[email protected]>

• Prev by Date: SCSI breakage on non-cache coherent architectures
• Next by Date: Re: Need help with register_page_fault_notifier() replacement in 2.6.24
• Previous by thread: Re: [PATCH][retry-2] init: Introduce rootdir bootparm to select which dir to sys_chroot
• Next by thread: HP Pavilion DV6408nr timer/irq related? hard lockup
• Index(es):
  • Date
  • Thread

[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]