Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!news.dacom.co.kr!usenet.seri.re.kr!usenet.hana.nm.kr!usenet.kornet.nm.kr!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,comp.unix.misc
Subject: Re: Linux vs FreeBSD
Date: 2 Dec 1995 06:48:13 GMT
Organization: TRW Financial Systems, Oakland, CA
Lines: 94
Message-ID: <49osrd$ptg@times.tfs.com>
References: <489kuu$rbo@pelican.cs.ucla.edu> <30BD2617.23585C28@mcs.net> <49k0dd$pfg@nntp5.u.washington.edu> <49o2n2$t4e@daffy.anetsrvcs.uwrf.edu>
NNTP-Posting-Host: mailhub.tfs.com
Xref: euryale.cc.adfa.oz.au comp.os.linux.advocacy:29565 comp.unix.bsd.freebsd.misc:9964 comp.unix.advocacy:11852 comp.unix.misc:19904
In article <49o2n2$t4e@daffy.anetsrvcs.uwrf.edu>,
BENJAMIN A LINDSTROM <bl03@uwrf.edu> wrote:
:
:Where in the BSD world, I would either have to patch it myself, or get
:my way into the "Developer's guild".=)
Whoops, can't let you get away with that one I'm afraid..
The entire FreeBSD system are available on a DAILY basis
(or should I say CONTINUAL basis) The releases are just the time
when we make an EXTRA effort to snapsot it and we
'freeze development' for a while to get that snapshot
'right'.
To understand how this works you need to understand how The FreeBSD
System is worked on...
Firstly the ENTIRE SYSTEM (kernel, utilities etc)
is under CVS. there is ONE CVS repository that represents "THE TRUTH"
as to what happens to be FreeBSD at any instant.
We have a tool called SUP, that will duplicate the CVS (logfile) tree
on your machine if you are Well connected TCP-wise, and another
called CTM that does the same for people only connected by email.
Both CTM and SUP only update those files in your tree that have CHANGED.
The result of this is that Here I have My own CVS tree, from which I check out
sources that are guarenteed to be up-to date. I make patches which
are relative to that, and check those patches back into the Central tree.
That's too much work for most people, who get the sources updated but
don't keep their own CVS tree on it.
Anyone can get the resulting source tree copied to their machine..
they need only ask SUP to give it to them (or subscribe to the CTM service.)
The source tree for FreeBSD that is available generally lags behind
what is the 'TRUTH' by, on average 2 hours.. Can you do THAT with Linux..?
That's EVERYTHING on my machine here is on average about 2 hours
behind freebsd.org. kernel sources, utility sources, games, docs, the lot.
if I go to /usr/src and type "make all install", It'll recompile anything
that may have been affected by any changed files, AND istall them into
the running system.. (it won't make and install a new kernel..
I have to ask for that.. (duh))
It's all guaranteed to work together, because it all comes from the
same place..
You do NOT have to be in "The Guild" (hey nice term.. like it..)
to get upto date stuff. I personally tend to follow the 'Truth'
by a couple of hours.. when I'm working on FreeBSD. :)
When I'm ready to commit my patches, I ask Sup and CVS to bring my tree RIGHT
up to date (to the second), and merge any changes that might have happenned
in the last few hours (amazing how often that happens), draw off
a large 'patch file' and send it in to the TRUTH where it's checked, and
committed to the tree.
the kernel is only one program (though the largest (hmm X?))
it's exactly the same if I'm working on 'ls'
:Yes, Linux's method of kernel development is different, but you have to
:admint that 1.2.13 is rock stable...And I'm sure 2.0.lastX or 1.4.lastX
:will be rock stable.
FreeBSD 'Releases' are pretty stable.. we don't stop the process
for releases, however, we BRANCH everything, and one BRANCH
stops development and get's fixed up for release, while the main
branch plows on.. (You have to know RCS/CVS etc. to know what I'm
saying here but hopefully you do).. The moment we Branch a release it's
effectively left behind....
:
:Does BSD release a major change per year for kernels and packages?
:Linux kernel has a major revision change every year.
Our Aim was a FULL (CDROM and all) release 3 or 4 times a year,
but practicallity looks like being every 6 months..
but between those times there are usually several 'half releases'
Not quite as much QC as a full release, but a new boot-floppy, and
stuff.. No cdrom though.(well we could but people would get upset about the
reduced QC if they had bought something, so we don't
for self preservation reasons)
Usually you grab the latest half or full release, (one every couple
of months), install that, and then use SUP or CVS to catch up
to where things are now....
+----------------------------------+ ______ _ __
| __--_|\ 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