Slashdot Log In
FreeBSD 5.4 Released
Posted by
timothy
on Mon May 09, 2005 07:36 PM
from the still-free-too dept.
from the still-free-too dept.
FreeBSD 5.4 is out. Reader KFW excerpts from the announcement: "The Release Engineering Team is happy to announce the availability of FreeBSD 5.4-RELEASE, the latest release of the FreeBSD Stable development branch. Since FreeBSD 5.3-RELEASE in November 2004 we have made many improvements in functionality, stability, performance, and device driver support for some hardware, as well as dealt with known security issues and made many bugfixes." Here are the release notes.
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
how... (Score:5, Funny)
Fifty Dollars. (Score:2, Funny)
Re:how... (Score:2, Funny)
Re:how... (Score:4, Funny)
Parent
congrats (Score:5, Interesting)
I have one (uneducated) question though: they mention a number of security fixes. How long does it generally take for a fix/patch to come out on freebsd compared to linux (or the other bsd variants)? I'm considering experimenting with it, but the relative comfort of packaging systems I'm familiar with makes it sort of hard.
Re:congrats (Score:4, Informative)
Parent
Commercial flavours of unix maybe. (Score:3, Informative)
Re:congrats (Score:5, Informative)
In all honesty... 24 hours is very unusual for us. I can think of one case where it happened recently, but that was when we rushed an advisory out in order to fit into the 5.4 release schedule.
A more typical time is 3 days, since we want to test carefully to make certain that a "security fix" never ends up breaking something else.
Parent
Re:congrats (Score:3, Interesting)
openbsd
Re:congrats (Score:5, Informative)
As fast as they are fixed, which in reality ends up being comparable to Linux, just listen on the appropriate mailing lists and follow the step-by step instructions. There are also some automated utilities in the ports collection that ease security updates. The BSD ports system will take care of most of your packaging concerns as well since it is an actively updated collection, although most require compilation from source there is the binary alternative, package, which should be easy enough for most RPM folk I would imagine.
Check out this link [freebsd.org] regarding packages and ports.
Parent
Re:congrats (Score:2, Interesting)
Re:congrats (Score:4, Informative)
Security fixes are backported to earlier versions. Those versions still officially maintained have fixes backported by the security officers. Older versions tend to also get fixes but merely by the work of interested committers. Thus it isn't usual to see fixes being backported to releases as far back as 4.3.
What do I mean by backported? Users can update their
Thus there is for example 5.3-RELEASE, and 5.3-p5.
Generally speaking, there is no need to wait for new releases to get fixes. Fixes are painlessly and automatically available almost overnight.
All of this applies to the software officially maintained by the FreeBSD system--i.e., anything in the "base system" Other software generally gets fixes in ports soon after the upstream version has a fix... but backing this is the port-audit database. port-audit is maintained by the security team and lists all the known vulnerabilities against third-party software. A cron job mails you warnings about vulnerable third-party software. The ports system warns you about vulnerable software and libraries when you attempt to install (even when a new install depends on an already installed but vulernable library.
Parent
Remember, cvsup is your friend! (Score:4, Informative)
Re:Avoid CVSUP on a server (Score:3, Informative)
1) The stable branch does include security fixes
2) The ports collection is not branched, so there's no possibility for "several ports downgraded" in the "4.x series". The only situation in which ports are downgraded is if there are serious problems with the newer version, and a reversion to the previous version is a net gain.
The end is near. (Score:5, Funny)
FreeBSD has risen from the grave.
It's hailing here in northern California in may.
The end is near, put on your glasses and anti-radiation suits boys, we're in for a ride.
Re:The end is near. (Score:2)
Torrents are your friends: (Score:5, Informative)
##### Disk One [freebsd.org] #####
##### Disk Two [freebsd.org] #####
Of course, in their infinate wisdom, the coders of slashdot have decided to make my life difficult with their damn lameness filters
Bloody Thieves!!! (Score:5, Funny)
What is it with you people???
You make me sick.
Parent
Re:Bloody Thieves!!! (Score:4, Funny)
Parent
Re:Torrents are your friends: (Score:5, Informative)
Parent
VIA CLE266/VT8235 USB support (Score:3, Interesting)
Re:VIA CLE266/VT8235 USB support (Score:3, Informative)
Re:VIA CLE266/VT8235 USB support (Score:2, Flamebait)
I never had a problem with my KT333 board.
Of course, it was running Windows.
Help promote their new torrent option, (Score:2, Informative)
http://people.freebsd.org/~kensmith/5.4-torrent/ [freebsd.org]
if you can, join the all seeds ; )
Free BSD (Score:5, Interesting)
Re:Free BSD (Score:5, Insightful)
Just plain marketing for one. *BSD can and probably is better by any number of measures. "Better" doesn't always equate to "sexier".
The other reason is that GPL can be more business friendly than the BSD license. The trick here is that the GPL is picky about which businesses it is friends with. For strategic reasons, a company like IBM can open something up but place the contribution under the GPL. It is perfectly free from an end user point of view but will require re-implementation on the part of a competitor who wishes to use knowledge from the code in question. This takes nothing away from scenarios where the BSD license is more "business friendly". Personally, I find the "moral" arguments around all of this induce finger drumming. If the choices were BSD or nothing or GPL or nothing then I expect we'd see much less funding of interesting projects by business.
Parent
Re:Free BSD (Score:4, Informative)
I'll also point out that the BSD's tend to be more predictable in their quality from release to release. There have been some real brown paper bag kernel releases and distros like RedHat and Mandrake have pulled boners on their own.
I'll bet a real BSD fanboy could probably think of a few more.
Parent
Re:Free BSD (Score:2)
I couldn't have said better! Mod me offtopic if you will, but please stop saying MacOS X == BSD!
tail -f *log (Score:4, Funny)
"The -f option of tail(1) utility now supports more than one file at a time."
That enhancement alone is worthy of upgrading!
Re:tail -f *log (Score:3, Informative)
That enhancement alone is worthy of upgrading!
Never heard of xtail [unicom.com]? It was released in 1989 and does exactly that.
5.4 Dedication (Score:5, Informative)
http://www.freebsd.org/releases/5.4R/announce.htm
stable development? (Score:2)
Re:Better SMP support? Better MySQL performance? (Score:3, Informative)
Re:Better SMP support? Better MySQL performance? (Score:2)
I doubt, many benchmarkers will bother turning these off on their systems and recompiling libthr/libc_r ...
Re:Sorry guys (Score:5, Funny)
Parent
Re:good stuff (Score:5, Interesting)
It would be hard for them to talk their way out of the rhetorical position they're in, where (it is claimed) Unix is inferior/dead/too expensive.
It's too bad, because I think they would be in a stronger position had they gone the Apple route. Can you imagine how different things would be if they had released a Unix-based OS a couple of years ago? Unthinkable.
Parent
Re:good stuff (Score:2, Insightful)
Re:good stuff (Score:3, Insightful)
Re:good stuff (Score:2)
Re:good stuff (Score:3, Funny)
l
*pop*
Clippy on Unix:
It looks like you're trying to write a cross-platform, intelligent forking, self-sustained, multi-thread application. Do you need help with that?
User: Fuck off clippy. I just wanted ls!
Re:good stuff (Score:2)
I've always wanted the same thing, sadly however the majority of
I'm also waiting to see how receptive
Re:I hope it's better than 5.3 (Score:2)
Please enlighten me, how is FreeBSD 5.x flaky?
The ports system works almost perfectly for me (FreeBSD is my main desktop and it is on one of my test servers). Keeping curent is simply a matter of make update && portupgrade -a every morning (I don't even run cvsup manually), with the occasional hiccup that is easily solvable by yourself or with a little help from TFM, freebsd-questions@lists.freebsd.org, or freebsd-ports@lists.freebsd.org.
Re:I hope it's better than 5.3 (Score:4, Informative)
Not true. Device drivers are usually backported unless they depend on some system difference between 4.x and 5.x. I've never noticed any hardware incompatibilities between versions and i've used both extensively.
The next one is a doosy...
The FreeBSD ports system is not all it's cracked up to be. Stuff is constantly breaking.
I honestly have not encounted a break in any major apps in ports in the past 3 years. It's evolved a lot since you last used it, i guess.
The desktop apps just aren't maintained carefully enough (not surprising, since FreeBSD is not a major desktop OS). After a cvsup, you get left wit a system in a state where you can't upgrade one piece of software without breaking a lot of other software. Portupgrade is a disaster -- I've never seen a better way to bork a system than to unleash portupgrade on it.
No, no no. Not true. I had a production system with apache, php, postgresql, gnome, KDE, etc installed (it was a workstation/light-use webserver for a lab i was working in). I installed it at 4.5, last time i touched it it was at 4.11, all ports upgraded (using cvsup and portupgrade), only one install point. After being a FreeBSD user for about a year. If I can do it, in a production environment, without any break in's or security issues, anyone can. My webserver here at home has been running 5 since 5.2.1, same deal - all things installed from ports, only one point of install, all upgraded by cvsup and portupgrade. No problems. Then there's my workstation, it runs Gentoo, Windows, Solaris and FreeBSD 5.3. FBSD has been installed since 5.3 first made -RELEASE, runs gnome 2.10 (which hit ports before it hit portage, ~1 week after official release). Only one install point, constantly updated using cvsup and portupgrade. Gentoo? Great little distro, but i've installed it at least 3 or 4 separate times due to major breakages or just aggrivation with portage. I don't hold it against portage, it's just still maturing.
Your report couldn't be further from my experience. Ever since i started running freebsd back four years ago i've been able to keep an up-to-date, stable system without much difficulty.
Parent
Re:I hope it's better than 5.3 (Score:3, Informative)
Re:Might be a stupid question, but... (Score:4, Informative)
*default host=cvsup2.FreeBSD.org
*default base=/usr
*default prefix=/usr
*default release=cvs tag=RELENG_5_4
*default delete use-rel-suffix
*default compress
src-all
(I like to put it under
cvsup -g -L 2
Go make some coffee while your sources are synchronized, then read the Handbook to learn how to build the beast.
Parent
making your own world (Score:3, Informative)
make buildworld
make buildkernel
make installkernel
reboot
boot in single user mode, then
mergemaster -p
make installworld
mergemaster
reboot
Voila, you should be running 5.4-RELEASE at this point
Re:Might be a stupid question, but... (Score:2)
pkg_add -rv cvsup-without-gui, then take a look at the example supfiles in
Once you've brought the system up-to-date (if you just want to go to 5.4, set the release tag to RELENG_5_4), follow the instructions in the Handbook [freebsd.org] on building the world.
That handbook section covers all the stuff I've mentioned above. The Handbook is your friend.
Re:GUI to desktop (Score:2, Insightful)
Re:So what's 5.4 like for 4.x users? (Score:3, Informative)
Re:So what's 5.4 like for 4.x users? (Score:3, Interesting)
There are worse problems than that though. I recall having mysterious behavior (also seen on mailing lists) when trying to forward things to a local FTP proxy, which is the only way to have transparent FTP NATting with PF (and IPFW/natd just didn't work at all, but I might have just missed something: it's been years since I last used it). So it has some caveats as