Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.sprintlink.net!uunet!in1.uu.net!mozz.unh.edu!toto.plymouth.edu!oz.plymouth.edu!not-for-mail From: ted@oz.plymouth.edu (Ted Wisniewski) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: The Future of FreeBSD... Date: 31 Jul 1995 08:29:46 -0400 Organization: Plymouth State College - Plymouth, NH. Lines: 33 Message-ID: <3viibq$npn@oz.plymouth.edu> References: <3v40u3$qmb@nntpd.lkg.dec.com> <3v7g53$qag@bonnie.tcd-dresden.de> <3vc897$u2h@nntpd.lkg.dec.com> NNTP-Posting-Host: oz.plymouth.edu In article <3vc897$u2h@nntpd.lkg.dec.com> Jon Jenkins <jenkinsj@ozy.dec.com> writes: >j@bonnie.heep.sax.de (J Wunsch) wrote: >>Jon Jenkins <jenkinsj@ozy.dec.com> wrote: >>Interesting. Matt Thomas doesn't seem to have this kind of troubles, >>he's been contributing the 100 MBit ethernet and FDDI drivers, and >>he's also a DEC employee. > >You will have to ask Matt about this. I wrote most of >the ISDN code. I asked if I could contribute to an ISDN >driver for FreeBSD and was told no!. The decision >is quite understandable on Digitals part. Why should >they let me use expertise I have gained while in their >employ (and still so) on a potential competitors product. I think the difference here is: I think a driver for a piece of DEC hardware would get a blessing because it will boost sales of such hardware. Where ISDN is not a piece of DEC hardware and thus DEC has nothing to gain and just would lose. It is just good business practice to encourage sales of your product by providing drivers. (If we could only get printer manufacturers to do the same we would be all set). | Ted Wisniewski INET: ted@oz.plymouth.edu | | Computer Services ted@wiz.plymouth.edu | | Plymouth State College tedw@psc.plymouth.edu | | Plymouth NH, 03264 HTTP: http://oz.plymouth.edu/~ted/ |