> Very true. The easiest way to solve _any_ problem is to have somebody else
> do the solving.
>
> Look, the problems with devfs are of two kinds:
> - It really can't solve the problems it is supposed to solve
> - The implementation might not be up to snuff
it solves my device naming and it is quite up to snuff. for the last X months,
the largest changes in the devfs patch are syncing it with the current source
code of the kernel.
> I really don't know about the second point, I'd assume that that is fixed
> by now (it has been more than a year, isn't it?). If not, they can be
> solved by the horde of devfs adicts. No need to involve the kernel hackers
> in this.
it's been two years in the works. and issues are really trivial. i've used
devfs in production for just shy of a year now and none of my production
machines has ever suffered from an issue related to devfs. i have a singular
machine that sits on the shelf that i had a problem with an IDE tape drive a
long time ago and haven't had time to dust it off and solve the problem ..if
the problem even exists today.
> The first one is the real stumbling block, IMO: devfs tries to solve the
> (addmitedly very hard) problem of managing devices (which in turn are just
> proxies for the _data_ they contain/convey, which is what you really want
> to manage) by placing an automated naming system in between. This just
> might be one of the minor building blocks for a solution to the real
> problem (assuming the solution goes through "devices" with "names" that
> look like "files").
and it's doing one heck of a great job, and as i've purported before, it is a
step in the right direction. i'd rather take that step than let moss grow.
-d
-- This is Linux Country. On a quiet night, you can hear Windows NT reboot! Do you remember how to -think- ? Do you remember how to experiment? Linux __ is an operating system that brings back the fun and adventure in computing. \/ for linux-kernel: please read linux/Documentation/* before posting problems
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/