lkml.org 
[lkml]   [2006]   [Jul]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [klibc] klibc and what's the next step?
    Olaf Hering wrote:
    > On Tue, Jul 11, Jeff Garzik wrote:
    >
    >> Two are IMO fairly plain:
    >>
    >> * Makes sure you can boot the kernel you just built.
    >
    > There is always some sort of prereq when new features get added.
    > Documentation/Changes has a long list. Some setup need more updates,
    > some need fewer updates. No idea what your experience is.
    > Old klibc was trivial to build (modulo that kernel header mess), and I
    > expect that kinit handles old kernels.
    >

    "Old klibc" still exists and is the same code out of the same source tree.

    >> * Makes it easier to move stuff between kernel and userspace.
    >
    > What do you have in mind here?
    > Once prepare_namespace is gone, there is no userspace code left.

    Things that have been bandied about, for example:

    - suspend/resume
    - partition discovery

    I'm sure there is more.

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

    \
     
     \ /
      Last update: 2006-07-11 19:27    [W:4.391 / U:0.144 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site