lkml.org 
[lkml]   [2002]   [Jan]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [RFC] klibc requirements
    From
    Date
    >>>>> "felix" == Felix von Leitner <felix-dietlibc@fefe.de> writes:

    Hi

    >> Comments from the various libc authors? Comments from other kernel
    >> developers about requirements and goals they would like to see from such
    >> a libc?

    felix> I think you need to ask initrd users.
    felix> My understanding was that people want to use the IP autoconfiguration
    felix> stuff from the kernel to initrd. Is that still so? What other programs
    felix> are needed?

    I can think of that in a fast thought:

    - if fsck.* can be there, it will make fs nice, just now they have to
    be able to fsck a ro root fs.
    - I suppose that you can put here also the raid autodetect code and
    things like that.
    - you also need a very small minishell, something like nash (that
    cames with mkinitrd will suffice).
    Basic utility here is that you want to have several small programs
    and have a small shell script to configure them (a distribution
    dont' want to recompile all its boot programs for each target
    configuration).
    - as I suppose that you have supposed insmod is essential :)
    - you already put there IP autoconfiguration.

    Later, Juan.



    --
    In theory, practice and theory are the same, but in practice they
    are different -- Larry McVoy
    -
    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: 2005-03-22 13:15    [W:0.032 / U:1.744 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site