From: d_smith@eggs.uwe.ac.uk (Dylan Smith) Subject: Re: Why is TCP/IP treated like it isn't really part of Linux sometimes? Date: 18 Oct 1992 12:30:08 GMT
In article <Qer299_00Vo9IXakoY@andrew.cmu.edu>, fl0p+@andrew.cmu.edu (Frank T Lofaro) writes:
|> Excerpts from comp.os.linux: 14-Oct-92 Re: Why is TCP/IP treated l..
|> Daniel AMP Carosone@mull (453)
|>
|> >Besides, if you want to beta-test the networking code, you don't need
|> >it to be in a distribution kernel - unlike, for instance, the scsi
|> >driver patches where some people couldn't install linux on their scsi
|> >drives to test it.
|>
|> would be standard UN*X practice. As for beta test, the support code for
|> EFS (which is still alpha test) is in the kernel by default, but not
|> tcp/ip. (By the way, after having used the EFS for a couple of months, I
There is a good reason, I suspect. The machine won't boot with the TCP/IP
kernel if you don't have an ethernet card (well, that's what it does to me,
perhaps a new driver sorts this.)
This brings me to a point - is anyone working on a kernel SL/IP driver, so
us mere mortals without an Ethernet card can use the same TCP/IP utils (and
AF_INET sockets) as an ethernet owner? I know ka9q exists, but it's not the
same, is it? (I'd gladly do it, but I'm a bit of a beginner at C)
--
Email : JANET dylan@uwe.hal | Everywhere else : dylan@hal.uwe.ac.uk
d_smith@uwe.csd | d_smith@csd.uwe.ac.uk