*BSD News Article 55974


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!howland.reston.ans.net!agate!tfs.com!mailhub.tfs.com!julian
From: julian@mailhub.tfs.com (Julian Elischer)
Newsgroups: comp.os.linux.advocacy,comp.unix.bsd.freebsd.misc,comp.unix.advocacy
Subject: Re: Linux vs FreeBSD
Date: 3 Dec 1995 23:19:51 GMT
Organization: TRW Financial Systems, Oakland, CA
Lines: 49
Distribution: comp
Message-ID: <49tban$978@times.tfs.com>
References: <489kuu$rbo@pelican.cs.ucla.edu> <49smvs$8gd@josie.abo.fi>
NNTP-Posting-Host: mailhub.tfs.com
Xref: euryale.cc.adfa.oz.au comp.os.linux.advocacy:29041 comp.unix.bsd.freebsd.misc:9727 comp.unix.advocacy:11669

In article <49smvs$8gd@josie.abo.fi>, Mats Andtbacka <mandtbac@abo.fi> wrote:
>on ftp://ftp.funet.fi/pub/OS/Linux/PEOPLE/Linus/v1.$VERSION
>where $VERSION is in [0-3]; 3, at the moment. New patches come out
>whenever Linus releases them, which can be daily to biweekly.
>
[...]
>
>Am I correct to think that the FreeBSD "equivalent", this CVS or
>whatever you called it, can't be _read_ except by a small core team?
>Whatever for? Keeping people from making their own changes and writing
>to it I can see, but...?
no the FreeBSD equivalent is 
ftp://ftp.freebsd.org/pub/FreeBSD/....
(or one of it's mirrors).. It get's updated every (4?) hours or so..
In ADDITION to this you can subscribe using either the 
CTM or SUP (two updating protocols) and have any changes to the tree
deliverd to you (via tcp or email) on a daily basis.


CVS is a source-code revision tracking system, and simply
represents the way that the revisions of code are archived within
the FreeBSD group.


>
>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?

You do exactly the same.
you sent it to core@freebsd.org, or "the patches  alias that I forget the
name of right now"@freebsd.org (patches?)
and declare youself it's developer/maintainer..

If you ACTIVELY maintain it
i.e. a patch every few days.. you'll probably get given commit
privs on the source tree so that you don't have to
bug people to commit the latest "foo" patch..

>

+----------------------------------+       ______ _  __
|   __--_|\  Julian Elischer       |       \     U \/ / On assignment
|  /       \ julian@tfs.com        +------>x   USA    \ in a very strange
| (   OZ    ) 300 lakeside Dr. oakland CA. \___   ___ | country !
+- X_.---._/  USA+(510) 645-3137(wk)           \_/   \\          ><DARWIN>
          v                                                        LL  LL