Messages in this thread | | | From | (david parsons) | Subject | Re: My $0.02 on devd and devfs | Date | 13 Oct 1999 12:15:37 -0700 |
| |
In article <linux.kernel.m3g0zftj78.fsf@sscnet.com>, Benny Amorsen <bamorsen@netvision.dk> wrote: >>>>>> "dp" == david parsons <orc@pell.portland.or.us> writes: > >dp> ``Modern'' is not the word I'd use for the standard >dp> PC-style ports on an IBM PC clone. > >Then let us not redesign device handling in order to support a bus >that is going away in a few years.
I think there may be a bit of confusion here. The PC-style ports already exist, and Linux already handles them. If I build a modular kernel (which I do), the current version of Linux will already do the fbm needed to load the drivers and give me access. If I use a devfs, current 2.3.x's will do the fbm needed to load the drivers and give me access without any changes to userland. But if I use devd as described in recent email on the kernel list, I either have to have the device nodes already installed or I have to bloat my kernel with the detection parts of the drivers or I have to build the drivers into the kernel.
____ david parsons \bi/ ... to say nothing of the additional userspace daemon \/ and the conversion table to convert from the new guaranteed to be unusable without userspace massaging kernel namespace to a namespace I can use. Shoot, Redmond couldn't do better than 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/
| |