Excerpts from netnews.comp.os.linux: 9-Aug-92 Stabilizing Linux Russell
Nelson@crynwr.co (3313)

quoted text
>I write a lot of Ethernet drivers.  I'd like to write some for Linux.
>But that means becoming a kernel hacker.  I'd be much happer with a
>Linux that had runtime loadable device drivers.  You see?  I just
>want to be a user as far as the kernel is concerned.

        I agree that something has to be done about device drivers! I've found
a token ring device driver, but I have to see how to get it to interface
with the kernel. But the source code and its includes are kinda of big
and would have to be packaged before I can send them to the person who
is doing the tcpip. Btw, the /ALPHA directory on tsx-11.mit.edu wasn't
there last time I checked, luckily I already got the tcpip stuff from
there. I also have to figure out just what parts I need. It was
originally from a freely distributable MS-DOS router, luckily it seems
not too hard to port. I still gotta look at it some more.

        I don't know if *runtime* drivers are needed, although it does indeed
sound like it could be a good idea. A kernel config utility that would
allow easy selection and installation of device drivers and other
configuration info and parameters would be good too. That way one just
sets the options in a config file or uses a program to do it, makes the
kernel, installs it, and reboots. Also having a standard for interfacing
to the kernel at the driver level would be helpful (sort of like VFS for
filesystems, I think).