[lkml]   [2004]   [Jun]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH] PPC64 iSeries viodasd proc file
    On Sun, Jun 20, 2004 at 03:52:33PM -0400, Jeremy wrote:
    > > Agreed. And the old viodasd reason was rejected exactly because it was
    > > such a f***ing mess.
    > The argument could be made that sysfs is similarly a f***ing mess and
    > that instead of solving problems, it creates more.

    It does? Have you brought this up to the sysfs / kobject / driver model
    authors? I think they would be open to any critiques of the current
    code, especially if such critique contains patches.

    > The mess of symlinks present there is a disaster and disgusting for
    > anyone who wants to actually write clean probing code.

    What do you mean by this. Any examples?

    > Also, things in sysfs aren't exactly stable enough to count on as a
    > dependable interface, but that's something the kernel has never
    > reliably exported to userspace.

    Why isn't sysfs stable enough? You can find any driver instantly. And
    any device bound to that driver in a stable and repeatable manner.

    So, give me specific examples, or stop ranting for no reason.

    greg k-h
    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 14:03    [W:0.019 / U:2.744 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site