Return to BSD News archive
Xref: sserve comp.os.386bsd.misc:2744 comp.os.linux.misc:19872 Newsgroups: comp.os.386bsd.misc,comp.os.linux.misc Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!gatech!newsxfer.itd.umich.edu!zip.eecs.umich.edu!yeshua.marcam.com!news.kei.com!travelers.mail.cornell.edu!cornell!mdw From: mdw@cs.cornell.edu (Matt Welsh) Subject: Re: I hope this won't ignite a major flame war, but I've got to know! Message-ID: <1994Jul20.150208.23766@cs.cornell.edu> Organization: Cornell CS Robotics and Vision Laboratory, Ithaca, NY 14850 References: <30h8kt$fcv@pdq.coe.montana.edu> <1994Jul20.040243.5860@cs.cornell.edu> <SJA.94Jul20171747@gamma.hut.fi> Distribution: inet Date: Wed, 20 Jul 1994 15:02:08 GMT Lines: 21 In article <SJA.94Jul20171747@gamma.hut.fi> sja@snakemail.hut.fi (Sakari Jalovaara) writes: >> Can J. Random User really _directly_ contribute to the [*BSD] >> project? How much red tape does it require, if so? > >My experience in contributing fixes to *BSD: > >I found a bug in a program. >I fixed it. What about adding new code, features, or applications? >NetBSD and FreeBSD are BSD and Posix compatible. Most stuff out there >that runs under UNIX (SunOS, AIX, whatnot) runs fine under *BSD. >If you write Linux code that is portable (and why not?!), that should >work under *BSD as well. Certainly. I'm less concerned about the work that the Core Team does (which is wonderful, I'm sure), but to what degree the user community can contribute. M. Welsh