[lkml]   [2002]   [Nov]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [BK PATCHES] initramfs merge, part 1 of N
    Jeff Garzik wrote:
    > Aaron Lehmann wrote:
    >> On Sat, Nov 02, 2002 at 03:13:45AM -0500, Jeff Garzik wrote:
    >>> The Future.
    >>> Early userspace is going to be merged in a series of evolutionary
    >>> changes, following what I call "The Al Viro model." NO KERNEL
    >>> BEHAVIOR SHOULD CHANGE. [that's for the lkml listeners, not you
    >>> <g>] "make" will continue to simply Do The Right Thing(tm) on all
    >>> platforms, while the kernel image continues to get progressively
    >>> smaller.
    >> Won't the initial userspace be linked into the kernel? If so, why will
    >> the kernel image get smaller?
    > Yes and no ;-)
    > Ignoring for a moment initramfses loaded from your bootloader (a la
    > initrd)... The amount of code that runs in kernel space shrinks, which
    > is the main point of early userspace. If you are talking in terms of
    > overall kernel image size, yes, but the initramfs cpio archive is
    > ditching along with the rest of __init code, so you're really only
    > talking about wasting a couple of additional pages in vmlinux -- a
    > slight increase in disk space usage, and that's it.
    > So runtime memory usage certainly does not increase...

    By the way, the final initramfs should typically be a union of whatever
    sources there are; with the ones linked into the kernel image unpacked
    first (so they can be overwritten if so specified to the bootloader.)


    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:30    [W:0.022 / U:1.060 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site