>> a) Fully replace standard /dev, and run
>> in total compatibility mode. (And
>> it has persistence with devfsd, no
>> more bullshit from you people)
>> b) Allow for automatic population of
>> standard /dev
>> c) deconfigured.
> Again, the "don't use it" argument isn't valid if you're going to
>try and replace the system, so c is out.
You never just *replace* anything. It's introduced as an
experimental driver. You could write a perl script to emulate
a preprocessor to remove the patch if you wanted.
> In b, do you populate a filesystem /dev with actual files that have
>major,minor's?
Yes.
> a appears unacceptable to a number of people for a number of
reasons.
A in compatibility mode lets you have your major/minors.
No incompatibility. What are those reasons again?
-Shawn
-
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/