[lkml]   [2003]   [Jan]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] don't create regular files in devfs (fwd)
    On Tue, 14 Jan 2003, Christoph Hellwig wrote:
    > On Tue, Jan 14, 2003 at 11:48:58AM +0000, Tigran Aivazian wrote:
    > > a) if devfs is available it provides a regular file whose size can be
    > > examined by applications and content read/written without much "fuss". In
    > > particular it is very convenient to say "vi microcode" and examine the
    > > content directly. If it was a device node then this would have been
    > > impossible.
    > What do you think about adding a sysvfs attribute for that instead in
    > 2.5? This seems to be the much more logical interface to me..

    Ok, that is a reasonable constructive suggestion. The only disadvantage I
    see is:

    sysfs is mounted under /sys and having two distinct paths (a device node
    /dev/cpu/microcode and a regular file somewhere in /sys) does not seem
    worthwhile. Not necessarily illogical, just not worth the hassle, imho.

    I think one filename is sufficient in this case. The fact that the same
    filename may sometimes refer to a device node and other times (if devfs is
    present) to a regular file may seem a little odd but it is not harmful and
    since it is useful then why remove it or change it?

    If you move it all the way to sysfs (i.e. no device node in /dev) then it
    seems a bit odd that a device driver entry point is found somewhere other
    than the usual /dev.


    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:32    [W:0.020 / U:29.760 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site