Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA6738 ; Tue, 12 Jan 93 15:12:16 EST Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!hri.com!noc.near.net!uunet!ulowell!cs.ulowell.edu!vpham From: vpham@cs.ulowell.edu (vinh) Newsgroups: comp.unix.bsd Subject: Re: Difference between 3c501 & 3c503, drivers anyone? Message-ID: <C0vKCv.IAx@ulowell.ulowell.edu> Date: 15 Jan 93 03:00:31 GMT References: <1j34rfINNbvm@girtab.usc.edu> <1993Jan14.093801.4907@spcvxb.spc.edu> <TRI.93Jan15023010@zelda.hut.fi> Sender: usenet@ulowell.ulowell.edu (News manager - ulowell) Organization: University of Massachusetts at Lowell Computer Science Lines: 19 In article <TRI.93Jan15023010@zelda.hut.fi> Timo.Rinne@hut.fi writes: >terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.) writes: >> eddy@girtab.usc.edu (George Edmond Eddy) writes: >> > Does anyone have the 501 drivers? otherwise i'll get ahold of 3com >> > for the spec's and get to work 8-) >> I'd advise against it. The 501 can't walk and chew gum at the same >> time. Folks might say it has trouble doing either alone 8-). > >I agree that 501 is not a ethernet board for serious UNIX work, but I >cannot understand that how it would be harmful to have driver for it >available. The fact is that there is thousands of 501s and they cost >practically nothing. If I had two machines home I'd like to connect >them through ethernet via 501s rather than serial line. > >And still 501 is bad, but there's been worse ethernet connectors in >the past. So if someone makes the driver for 501 I suggest that it is >made public. > look at the ka9q package that has built-in support for this card.