Linked by Corey Holcomb-Hockin on Wed 5th Nov 2003 19:48 UTC
FreeBSD I've been using computers since I was quite young and have been using Unixlike OSes for about two years. Most of my life I've used Macs and only started using Windows and Unixlike OSes recently for programming. I'm good at learning OSes as long as they are documented. I've been using FreeBSD for about a year and a half.
Permalink for comment
To read all comments associated with this story, please click here.
Names for CVS Tags
by Jud on Thu 6th Nov 2003 17:52 UTC

Good and fair article. RE: "a long time" to compile during FreeBSD's 'make world' updating process, with my 1.533Ghz Athlon XP1800+ it takes me about 25 minutes to build world, 5 minutes to build the new kernel, a few seconds to install the kernel, and about a minute and a half to install world. To update an entire OS and kernel, that ain't bad. Do it while you're having breakfast on a weekend morning (afternoon?;).

The following are, from my reading of the Handbook and FreeBSD mailing lists, generally accepted terms for the following CVSup tags:

Tag=. Term=-CURRENT

(This is the up-to-the-minute development version.)

Tag=RELENG_x Term=-STABLE

(This is a more stable version backporting those items from the development branch that appear to be stable after testing by developers and users running -CURRENT. Though the author was somewhat reluctant to try this branch, I haven't had a problem with it in several years of use.)

Next is what seems to me to be the most often used term for the following CVSup tag:

Tag=RELENG_x_y_0 Term=x.y-RELEASE

(That's the same source as appears on the release isos, no changes. It has been extensively tested through preview and release candidate stages.)

Next is a branch for which there is less consensus about what to call it, but the term I've seen most often (a good one IMO, since it doesn't duplicate the names of other branches) is as follows:

Tag=RELENG_x_y Term="Security branch"

(This is the source that went into the release updated to fix security bugs and perhaps a limited number of non-security bugs deemed to be especially critical.)