[lkml]   [1999]   [Oct]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Subjectdevfs again (was RE: [linux-usb] Re: USB device allocation)
    > userspace, though, and I hope most people would agree with me.  Why
    > don't we try to design that interface first, and I suspect
    > the rest will
    > follow relatively easily.

    what about the current devfs, but without the filesystem code?

    ie a central kernel devfs layer to handle accept driver registrations and
    communicate with daemon.

    daemon to handle updating the already existing /dev on filesystem?

    Would such a solution be acceptable? It seems a decent compromise between
    Richards full-blown devfs, and the minimal user-space daemon/scripting
    approach favoured by others. Plus we can retain some of the existing devfs
    code, and the API it has established.


    Paul Jakma.

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

     \ /
      Last update: 2005-03-22 13:54    [W:0.056 / U:7.640 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site