No it wasn't.
What about other stuff: net-utils and plenty other friends?
> If a useful thing goes into the kernel and the developers of userland
> tools abandon the old-style interfaces in favor of the new interface,
> I'm not going to blame the kernel when I take that new interface out
> and the tools go belly-up.
What about just this: Think TWICE before inventing ANY new interface?
> (And thats one of the nice things about devfs instead of some
> hypothetical ``do devfs, but break the interface so that it's not
> usable without some large expensive daemon'' alternative; it may
> be a new interface, but it's backwards-compatable with the
> previous interface so I can disable it without stomping all over
> userland.)
>
> ____
> david parsons \bi/ The only use for a "break the interface" replacement
> \/ is that it would get the devices registry into the
> kernel so a devfs patch could be done against that.
>
> -
> 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/
-
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/