FreeBSD 5.2.1 RC Ready For Getting
MobyTurbo writes "FreeBSD 5.2.1 RC is now available, and now can be downloaded from the FreeBSD site and mirrors, or if you are currently running FreeBSD 5.2 (or for that matter some earlier versions) you can simply cvsup to it. The upcoming 5.2.1 release should fix a number of outstanding bugs in the 5.2 release, and this is a chance to make sure those bugs get fixed!"
FreeBSD certainly does support CD writing and has for some time. Maybe you last used it before CD burners were produced :-P
Even your favourite K3b is available.
Following the rules doesn't get the job done.
of what has been reported broken in 5.2 and MFC'd to 5.2.1 can be found here
I just hope I can use my USB mouse with out needing a PS/2 mouse plugged in and my sound works again!
Music is everybody's possession.
It's only publishers who think that people own it.
Fuck Beta
~John Lenno
... is a FreeBSD-based liveCD. You can find it at www.freesbie.org. I downloaded it awhile ago but haven't yet checked it out, must get onto that. So many distros, so little time. L
Well stereotypes don't just start by themselves.
Remember though that just like any stereotype what you actually see from a group doesn't necessarily paint the whole picture. For linux OR FreeBSD.
Ignoring the fact that the parent post was a joke for a moment, BSD has been around since the 1970s.
The original Windows (not NT, which is a different OS) was released in 1985 (Windows 1.0), and the last version was released in 2000 (Windows Me).
Linux and NT are about the same age: Linux 1.0 was released in 1994; Windows NT 3.1, (which was really NT 1.0, but called 3.1 to match the version number of Windows 3.1) was released in 1993.
Also:
Windows 2000 = NT 5.0 (really 3.0, since NT started with version 3.x)
Windows XP = NT 5.1
Windows 2003 = NT 5.2
The 5.x branch is expected to go -STABLE with FreeBSD 5.3, which should be out some time this spring. There is a list of outstanding issues at http://www.freebsd.org/releases/5.3R/todo.html.
OK, that's actually 2 words. But they're important words describing a feature CVS lacks. Basically it means that when I commit a bunch of files, they either all are committed or none of them are. No partial commits that break the build. No chance of getting latest during what happens to be the midst of someone else's multi-file commit.
See the Subversion site to try it out.
In the last 10 years, I've worked on projects with RCS, CVS, Sourcesafe, Perforce, and Subversion. Once you get used to atomic commits in Perforce and Subversion, you'll wonder why any source control software is still used that doesn't do it this way.
-_-_-
There are 0x40000000 types of people: those who understand 32-bit IEEE 754 floating point, and those who don't.