Return to BSD News archive
Xref: sserve comp.os.386bsd.misc:2767 comp.os.linux.misc:20024 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!ihnp4.ucsd.edu!usc!howland.reston.ans.net!vixen.cso.uiuc.edu!news.uoregon.edu!usenet.coe.montana.edu!bsd.coe.montana.edu!nate From: nate@bsd.coe.montana.edu (Nate Williams) Newsgroups: comp.os.386bsd.misc,comp.os.linux.misc Subject: Re: I hope this won't ignite a major flame war, but I've got to know! Date: 19 Jul 1994 19:13:33 GMT Organization: Montana State University, Bozeman Montana Lines: 29 Message-ID: <30h8kt$fcv@pdq.coe.montana.edu> References: <30drlt$7tc@news.u.washington.edu> <1994Jul18.093302.19670@wmichgw> <30fhpn$968@pdq.coe.montana.edu> <1994Jul19.143013.28119@cs.cornell.edu> NNTP-Posting-Host: 153.90.192.29 In article <1994Jul19.143013.28119@cs.cornell.edu>, Matt Welsh <mdw@cs.cornell.edu> wrote: >In article <30fhpn$968@pdq.coe.montana.edu> nate@bsd.coe.montana.edu (Nate Williams) writes: >>And Anyone and I MEAN ANYONE can work on FreeBSD development. >> >>[...] >>-- >>nate@bsd.coe.montana.edu | FreeBSD core member and all around tech. > ^^^^^^^^^^^^^^^^^^^ >Then why the cabal? For historical reasons. 386BSD had all of the 'integration' done by *one* person, and his decision weren't always met with approval. (As are some of the changes Linus makes, but he's a much easier guy to get along with than the 386BSD person) What happens when Linus decides to quit developing Linux? I've seen what happens, and I'd rather have a group of professionals that decide what goes in and what doesn't rather than one person. Someone needs to decide direction or else chaos will ensue. Linus is the one stabilizing factor in Linux, and in the *BSD groups we have a group of folks. Nate -- nate@bsd.coe.montana.edu | FreeBSD core member and all around tech. nate@cs.montana.edu | weenie. work #: (406) 994-4836 | home #: (406) 586-0579 | Available for contract/otherwise work.