Re: [PATCH] delete devfs

Mike Snitzer
2004-07-22T01:48:59Z

Maintaining device registration and persistence all from userspace is
wonderful. Try it, you'll like it. Not to mention that for the
developers udev is much more easily maintained than kernel code
(devfs). Your concern about something else ripping off udev a year
from now is misplaced; the beauty of free software is the best
solution generally wins out. That "something else" will have to be
pretty damn amazing to upstage udev.

Mike

On Thu, 22 Jul 2004 03:08:00 +0200, Grzegorz Jaśkiewicz
<gj@pointblue.com.pl> wrote:
> Jesse Stockall wrote:
>
> >On Wed, 2004-07-21 at 17:27, Greg KH wrote:
> >
> >
> >>It fixes an obviously broken chunk of code that is not maintained by
> >>_anyone_. And it will clean up all device drivers a _lot_ to have this
> >>gone, which will benifit everyone in the long run.
> >>
> >>
> >>
> >
> >Agreed, but this 'broken' chunk of code is 'working' for a lot of people
> >(whether or not this is due to pure luck is not the point)
> >
> >
> >
> Personaly as many of my friends (those who use and care about kernel) we
> think that devfs is (was) the only resonable solution for /dev tree, and
> should be only one maintained. Requirement of userspace software for
> /dev is just a one big mistake. IMO in year time someone will have
> another brilliant idea, and will rip udev off. I don't think that's a
> good solution. IMO (and that was my humble opinion) devfs should be
> maintained instead of rewriting thing again, and creating problems (udev
> is not present unless userspace is up, etc).
> so for me, and many others devfs should stay as only solution :-)
> I am pretty shocked that there is no expierenced developer to maintain
> devfs. I would be delighted to do it, but I guess it's over my schledue.
> I don't have time enough to maintain my KDE stuff atm, not to mention
> kernel bits...
>
> (no flames please, just giving my opinion).
>
> --
> GJ
>
>
>
> -
> 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/
>