Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!news.kei.com!newsfeed.internetmci.com!uwm.edu!newsspool.doit.wisc.edu!koala.uwec.edu!daffy.anetsrvcs.uwrf.edu!cakerwood!not-for-mail From: bl03@uwrf.edu (BENJAMIN A LINDSTROM) Newsgroups: comp.os.linux.advocacy,comp.unix.bsd.freebsd.misc,comp.unix.advocacy Subject: Re: Linux vs FreeBSD Followup-To: comp.os.linux.advocacy,comp.unix.bsd.freebsd.misc,comp.unix.advocacy Date: 6 Dec 1995 00:36:34 GMT Lines: 48 Message-ID: <4a2oii$m7h@daffy.anetsrvcs.uwrf.edu> References: <489kuu$rbo@pelican.cs.ucla.edu> <49smvs$8gd@josie.abo.fi> <DJ2JEp.7Ky@nntpa.cb.att.com> NNTP-Posting-Host: cakerwood.acc.uwrf.edu X-Newsreader: TIN [UNIX 1.3 950726BETA PL0] Xref: euryale.cc.adfa.oz.au comp.os.linux.advocacy:30164 comp.unix.bsd.freebsd.misc:10353 comp.unix.advocacy:12137 John S. Dyson (dyson@inuxs.inh.att.com) wrote: : In article <49smvs$8gd@josie.abo.fi>, Mats Andtbacka <mandtbac@abo.fi> wrote: : >Robert Sanders, in <87rayn8ion.fsf@interbev.mindspring.com>: : >>On 2 Dec 1995 10:52:32 GMT, nickkral@parker.EECS.Berkeley.EDU (Nick Kralevich) said: : >Actually, if I wanted to nitpick, not _every_ Linux kernel change : >should go to Linus; for example, the ext2fs is maintained by Remy : >Card, so patches to it should be sent to him. But yes, you're : >essentially right. : > : That means that he has full and exclusive control, perhaps like a benevolent : king. Sure hope that he stays that way. Note that on FreeBSD, someone who : would have developed such an important part of the OS, would more than : likely have direct CVS commit access. : Hmm..Where do you get "King" and "Exclusive" access from that statement? Are you saying that if I fixed person A's XYZ driver that I could submit the patch to FreeBSD and avoid person A?? If this is the case then I can for-see many arguements and problems. Remy Card maintians the EXT2FS file system...You can submit patches to him..which in-turn get submitted to Linus..If Remy looks at your patch and feels that you are on the right track, but you missed a few things (Since he more then likely knows the source code like the back of his hand.=). He might rewrite to make sure it works the way it should. : >Out of interest, what happens if I develop something completely new : >for FreeBSD, some driver never seen before; with Linux, I could just : >proclaim myself its developer/maintainer, send it to Linus and hope : >it gets into the kernel. Who approves new stuff into FreeBSD? : > : It is a complicated question, but rather than having to convince 1 out of 1 : person on Linux -- on FreeBSD you have to convice 1 out of 10 or so kernel : people to champion your kernel change. It is almost always reviewed, and : usually it is accepted. You see, FreeBSD is not meant to be 'owned' by anyone : in particular, and the FreeBSD maintainers (including core team) are : developers AND caretakers. We do have much open discussion on the mailing : lists when conflicts arise -- I think that one of the reasons that there : have been comments about the adversity on *BSD, because we are so open. : Acutally.=) Linus is moving Linux to a Module system..So unless the driver/addition is not fit to be an Add-on module, then you have to 'convince' Linus to include it. : Bottom line, I think in this thread we have shown that FreeBSD is at least : as open as Linux, and I essentially agree that it is folly to beg the : question any farther. : I agree it's pointless to argue more.=)