FreeBSD 6.0 Released 289
Reyad Attiyat writes FreeBSD 6.0 is ready for release! New features, and there are lots, can be reviewed at the official site. One of the biggest and most anticipated features (mentioned before on Slashdot) is wireless support, which has been greatly improved upon. This includes support for a lot more cards, WAP support, and integration into the dhcpd client. This release comes only mere days off NetBSD's release and an OpenBSD release. Version 6.0 was intended to be released way back in August but due to a number of factors it had to be delayed till now. Aside from this major release the FreeBSD project has also had some major changes, including most recently a new logo and also a brand new website."
Shit... (Score:2)
Re:Shit... (Score:2)
Doesn't that have a bunch of security bugs? 4.11 is pretty nice.
Re:Shit... (Score:3, Interesting)
I am looking into NetBSD after the fallout with FBSD 5.x but I am willing to try again with 6.x. Pkg's are also available for FreeBSD users from www.netbsd.org and you can compile them from source as well. It takes care of alot of dependancy problems.
Re:Shit... (Score:2, Informative)
Live-CD? (Score:2)
Re:Live-CD? (Score:2)
Re:Live-CD? (Score:3, Informative)
Alright, can't you google for your own info?
http://www.freesbie.org/ [freesbie.org] - Latest release is based on FreeBSD 5.3.
It's harder to find LiveCDs of Open/NetBSD, but you can create your own -
http://ezunix.org/modules.php?op=modload&name=Sect ions&file=index&req=viewarticle&artid=88&page=1 [ezunix.org]
http://www.onlamp.com/pub/a/bsd/2005/07/14/openbsd _live.html [onlamp.com]
Gee golly, and all of that was on the first results page after searching for "Open/Net/FreeBSD LiveCD".. Whooda thunkit?
Re:Live-CD? (Score:2)
I'm still amazed by the number of people whose first reaction is to ask, rather than search. Christ, I'd be embarrassed to ask a question whose answer was on the first page of a simple search...
Re:Live-CD? (Score:5, Insightful)
Unless, of course, you've never run a unix-like system before. Then by all means, try Freesbie.
-matthew
Re:Live-CD? (Score:3, Interesting)
Now if I had a livecd, I'd use that instead to get full CPU on my side.
Now before you call me a newbie, search my name on google, and maybe visit me sometimes. I have stacks of sparc, hp, rs6000 and alpha machines in my room to play wit
BSD is dead? (Score:4, Funny)
Variants. (Score:4, Funny)
Re:Variants. (Score:2)
Torrent? (Score:2)
Re:Torrent? (Score:5, Informative)
Re:Torrent? (Score:5, Informative)
Yes. The official release announcement [freebsd.org] (which for some reason wasn't linked in the story) has a link to the torrent files [freebsd.org].
Real improvement over 5.x (Score:5, Insightful)
Congratulations, Release Engineering team! You've turned out a great product.
And as a side note, we've seen big releases from each of the major BSDs within the last week. Dying, my foot.
Re:Real improvement over 5.x (Score:4, Insightful)
Of course BSD isn't dying. Either that, or it's the longest death in history. Some Linux-based asswads -- and please understand that I'm not equating Linux usage with being an asswad, heck, I use Linux every day and I wouldn't want to incriminate myself; no, I'm just specifying asswads who somehow have found Linux -- just can't shut up. They're like the annoying nerd in the back of the room who has found an expert mix of geekness and insufferable rudeness that, for some reason, he mistakes for wit. Think "Malvin" in WarGames, and you get the idea. They're the guys who think they're experts because they've managed to install Debian and, oh, Gnome maybe, but they only use Synaptic for package management and they're afraid of cron even though they talk about how they use it all the time, even for personal tasks(!).
God.
They're *dying* to appear knowledgable, so they perpetuate this dying joke without ever really knowing what situations the BSDs are best suited for or the philosophies behind them. I mean, the BSD Web sites, have you seen them? That have all that *text*, I mean, God, you have to read and stuff.
FreeBSD has its issues, I'm aware of them. But I've used it for many, many moons now, and honestly, it rocks my world as a server system. I might use something else, but I'd have to have a really, really good reason. My mail servers run on fairly close-to-stock OpenBSD systems, and they're rock solid. Package management and upgrades are a breeze.
Bottom line, the BSDs make my job easy.
Re:Real improvement over 5.x (Score:2)
I have a 5.4 server that I recently installed and I want to upgrade to 6.0. It isn't in production yet, but it does have some custom configuration and many ports installed (as well as a system disk mirrored with geom). I've never really run FreeBSD before. Do I need to recompile all the ports I installed against the 6.0 system? How do I go about doing that? I'm concerned about running ports built against old libraries. I'm used to running Debian where everything get
Re:Real improvement over 5.x (Score:3, Informative)
You probably don't need to, but it's a good idea. Here's how I do it:
Use "find" to find and delete all files in /bin, /sbin, /usr/bin, /usr/sbin, /lib, /usr/lib, /usr/libexec, and /usr/include that are older than the day I upgraded the machine. At this point, I have a 99% "pure" base system, but almost all ports on the machine are temporarily broken. Note that FreeBSD 7 has this feature built-in.
Is portupgrade installed?
- If
Re:Real improvement over 5.x (Score:2)
Could be problematic (Score:2)
Also remember the compat5x port actually installs a binary package of the libraries - it doesn't build them from source. That means that you only get the debugging or optimization flags that the package was built with, not the
Re:Real improvement over 5.x (Score:3, Informative)
You are also correct that the ports tree is unrelated to the release version. The base system in 6.x comes with a new utility, "portsnap", that you can use instead of cvsup to update your
Re:Real improvement over 5.x (Score:3, Interesting)
So far I've had a great experience with FreeBSD. Before that my only experience was GNU/Linux (mostly on Debian).
Any useful resources you have would be nice too. I'm still relatively new to FreeBSD, and I'm not familiar with everything about it. If it's not in the handbook, I don't know it.
Re:Real improvement over 5.x (Score:2)
As far as resources, I highly recommend joining one of the official FreeBSD mailing lists ("-questions" and "-stable" would be appropriate for this). The people on there are really friendly and helpful. That's the first place I t
SCO is DYING (Score:2)
Re:SCO is DYING (Score:2)
Re:Real improvement over 5.x (Score:2)
I wouldn't have done it if I thought it was a risk. It seems like the real risk in this case was in not upgrading.
Comment removed (Score:4, Interesting)
WAP? oh yeah... (Score:3, Informative)
most probably the article means this sentence:
"In addition to architectural changes, it includes completed 802.11g, WPA [...]"
WPA = security standard (stay back from WEP, guys!)
Re:WAP? oh yeah... (Score:2)
No mention of WPA in the handbook, however (Score:2)
So, is WPA supported or not?
Java on BSD (Score:2)
FreeBSD Java(TM) Project (Score:5, Informative)
There are several ports, one of them being native. Google!
Re:Java on BSD (Score:2)
http://www.freebsd.org/java/dists/15.html [freebsd.org]
Are you sure about that? (Score:3, Informative)
I recently set up several servers running FreeBSD 5.4, the native JDK 1.5, and Tomcat 5.5.12. They work perfectly, each handling upwards of 9 to 10 million hits per day.
Re:Are you sure about that? (Score:2)
Re:Java on BSD (Score:3, Informative)
Gcj is becoming more and more capable, however. I believe it's now possible to build OOo with gcj as your compiler for the java bit
Re:Java on BSD (Score:2)
Then again, in previous discussion it was stated that Java caused a lot of the startup performance problems noted with OpenOffice.org. So a better idea may to be avoid the use of Java with OO.o.
Re:Java on BSD (Score:2)
Jeremy
Re:Java on BSD (Score:2)
Re:Java on BSD (Score:2, Interesting)
Re:Java on BSD (Score:2)
That's much the same reason why the *BSD projects use GCC: it would take far too long and would consume far too many resources to produce a quality C and C++ compiler suite.
Oh man .... (Score:5, Funny)
Bah.
Re:Oh man .... (Score:2)
Re:Oh man .... (Score:2)
Actually, I wasn't trying to be funny. I really just did get around to burning them the other day. The fact that I've not felt compelled indicates that, for my needs, 4.8 has always just worked.
And it is also factually innacurate that I would need to upgrade to 5.3 before upgrading to 6.0 from a 4.8 system.
Due to the lovely way that FreeBSD does partitions and slices, the way I
Re:Oh man .... (Score:2)
The filesystems marked with (*) get newfs'd when I do an upgrade. The other ones get left alone and re-mounted. ad0s1 used to be my Windows partition before I got a dedicated XP box, hence the wi
FreeBSD 6.0 = good (Score:2)
Re:FreeBSD 6.0 = good (Score:2)
Re:FreeBSD 6.0 = good (Score:3, Informative)
I haven't had any problems with this setup for months on pre-6.0, so I don't think it's an i
A new release of DFBSD. (Score:4, Informative)
http://leaf.dragonflybsd.org/mailarchive/kernel/2
For those who are unaware, DragonFly BSD is a heavily modified continuation of FreeBSD 4.x. It is done by Matt Dillon and many others who are/were prime FreeBSD developers in the past, but disagreed with the current FreeBSD development path.
Re:A new release of DFBSD. (Score:4, Informative)
http://en.wikipedia.org/wiki/DragonflyBSD [wikipedia.org]
Put simply, Matt Dillon was a FreeBSD contributor for many years. He was responsible for some of the most important and beneficial work, such as the virtual memory subsystem rewrite.
He did not feel that the direction of FreeBSD 5.x was a good one, and thus did the open source thing and forked his own kernel from FreeBSD 4.8.
DragonFly BSD is incorporating many features useful for multiprocessor systems. It includes a vastly improved kernel memory allocator and improved threading and messaging constructs, for instance.
While it is still under development now, it is poised to become the leading general-purpose desktop/workstation/server BSD of the future. It's partaking in the innovations that will be needed with the advent of multicore and multiprocessor systems.
memory management and scheduler? (Score:2)
<IIRC>
The 4.x->5.x transition made some major changes in the scheduler and memory management. It was a rough transition, and personally I had some problems with some of the early 5.x releases (e.g., processes hogging 100% of cpu when they shouldn't have). There were complaints that only a couple of the kernel developers actually understood the new code, there were doubts about whether bugs could actually be fixed, and the 5.x seri
Re:memory management and scheduler? (Score:2, Insightful)
New logo on web site? (Score:3, Insightful)
I386 Support Removed? (Score:5, Informative)
I sorta find that astounding (not that I have a 386 around myself). Oh well, the world has moved on.
Re:I386 Support Removed? (Score:2)
Out of curiosity, why? This version's big features are increased performance on big systems (where big means "expensive new desktop and above"). I have a hard time imagining an intersection between 386 systems and the new target audience.
>386BSD (Score:3, Insightful)
Re:I386 Support Removed? (Score:2)
I think this represents a true break with past where they are going for "modern" and fast versus the historical roots of the OS (now if only we could get rid of csh on bsd systems.
Re:I386 Support Removed? (Score:2)
I'll setup a sourceforge webpage including full toolchains and a weblog on how I did it.
And of course, I'll sell the mandatory T-shirts.
Re:I386 Support Removed? (Score:2)
Do you have proof of that? I was under the impression that the 386-specific parts of the kernel had been ripped out altogether. You might be right, but that wasn't my understanding.
Vast performance improvements. (Score:5, Interesting)
We found that the server was able to process about 60% more mail when running FreeBSD 6.0, as compared to OpenBSD. That's not to suggest that OpenBSD is bad, but performance wise, FreeBSD has taken the lead. And that was without significant tuning, and running a GENERIC kernel.
I'm not certain yet if it is improvements in the network stack, the filesystem subsystem, or in the scheduling. It may be a combination of all three. Some more time will be needed to determine exactly where the benefits are coming from.
Re:Vast performance improvements. (Score:5, Insightful)
Erm, has OpenBSD ever had the lead in performance? I really doubt it; that's not what it was designed for. All of those little niceties like ultra-paranoid memory protection, cryptographically random process IDs, etc. take resources. Basically, it's tuned for security and correctness with a nod toward performance, while FreeBSD emphasizes raw performance over watertight security.
That doesn't mean that FreeBSD has bad security, or that OpenBSD doesn't incorporate performance enhancements when they can safely do so. All of the BSDs are heavily cross-pollinated, and the best ideas tend to get broad support from all of them.
Still, it's pretty reasonable to say that OpenBSD is more secure and FreeBSD is faster. I wouldn't be the least surprised that FreeBSD can process more email or web hits, especially when you through SMP or HTT systems into the mix.
Re:Vast performance improvements. (Score:2)
What astounded me most was the massive performance boost over OpenBSD. 60% isn't a small amount, by any means. That's nearly getting the capabilities of another physical server, without actually having to get any new hardware.
Re:Vast performance improvements. (Score:2)
You judge stability after half a day?
Re:Vast performance improvements. (Score:2)
Re:Vast performance improvements. (Score:2)
Measured how? What were the bottlenecks?
ULE scheduler? (Score:2)
Could anyone explain the benefits of the ULE vs. 4BSD schedulers?
Are there real performance benefits?
Thanks.
m0n0wall (Score:2)
Re:m0n0wall (Score:2)
Digging up grandma? (Score:3, Funny)
For the humor impaired, this was a joke!
Glad to hear that BSD keeps on chugging along...Linux has a reputation for taking some excellent ideas and even implementation from the BSD guys....BSD improvements often translate into Linux improvements too.
Good job guys!
Holy Quick (Score:2)
Still broken on Supermicro 5013C-MT (Score:2)
Re:how does this affect OS X? (Score:3, Informative)
Re:how does this affect OS X? (Score:2)
I know that under the terms of the license they don't have to do anything but it's always nice to share... and all that.
Re:how does this affect OS X? (Score:3, Informative)
http://developer.apple.com/darwin/ [apple.com]
Re:how does this affect OS X? (Score:2)
Re:how does this affect OS X? (Score:5, Interesting)
Re:how does this affect OS X? (Score:3, Informative)
Re:how does this affect OS X? (Score:5, Informative)
Re:how does this affect OS X? (Score:3, Informative)
Or, at least, kernel code based on BSD - but developed independently; it's not just FreeBSD lifted up and modified to plug into Mach. In Tiger, for example, the MP locking, and VFS layer, are significantly different from FreeBSD.
As for userland, the system library (called libSystem on Darwin/OS X, unlike the libc on most other UN*Xes) is based on BSD, but not identical to FreeBSD's - for example, a lot
Re:how does this affect OS X? (Score:2)
No intention of slighting the FreeBSD developers and the extent to which
Re:how does this affect OS X? (Score:3, Informative)
The major one being the insane filesystem layout. A number of links to more orthodox locations helps but it still is pretty weird and finding something isn't easy. Expecially since the included search system only looks in $HOME, so enabling locate is a good first move...
For most users who will never see the system anyway, this
Re:how does this affect OS X? (Score:5, Interesting)
Wrong. The page you linked to mentions all 3 BSDs exactly once, never specifying which one in particular the userland was primarily derived from.
I'm more inclined to believe the following, straight from news articles and Apple's own documentation:
"Going forward, [Darwin] will track a stable version of FreeBSD, which is the more popular and traditionally x86-only version that claims about a million users worldwide..." (source [zdnet.com])
"The Darwin kernel is based on FreeBSD and Mach 3.0 technologies..." (source [apple.com])
"...the BSD portion of Mac OS X is primarily derived from FreeBSD..." source [apple.com])
"Above the Mach layer, the BSD layer provides "OS personality" APIs and services. The BSD layer is based on the BSD kernel, primarily FreeBSD." (source [apple.com])
"We should note, however, that apart from a few architectural differences (such as our use of the Mach kernel), we try to keep Darwin as compatible as possible with FreeBSD (our BSD reference platform)." (source [apple.com])
"Integrated with Mach is a customized version of the BSD operating system (currently FreeBSD 5)." (source [apple.com])
In fact, practically the only references I can find to NetBSD in Apple's Developer Connection are to the HISTORY sections in some of the man pages. Apple may have borrowed some from NetBSD, but the main BSD player in OS X is clearly FreeBSD.
Re:6-STABLE? (Score:5, Informative)
From what I've seen, 6.0-RELEASE is more stable than 5.3 or 5.4.
Re:6-STABLE? (Score:2, Insightful)
Re:6-STABLE? (Score:5, Informative)
Not at all. I (and many other people) have been running 6.0-BETAs since mid-July, and 6.0-RC1 since early October. This isn't just a random snapshot of HEAD; the code which became 6.0-RELEASE was frozen apart from patches approved by the release engineering team for months leading up to the release.
Re:6-STABLE? (Score:2)
Re:6-STABLE? (Score:2)
RELEASE and STABLE are mutually exclusive. Please read up on FreeBSD release naming.
I'm pretty sure you're confusing RELEASE and CURRENT. STABLE is a CVS branch (as CURRENT is) while a RELEASE is a CVS snapshot, no matter what branch it comes from. So you can have, say, the 5.4-RELEASE snapshot from the 5-STABLE branch.
Re:6-STABLE? (Score:2)
So, for FreeBSD 6-RELEASE you'd cvsup to RELENG_6_0.
See FreeBSD's releng page [freebsd.org] for details.
Re:no offense, but give it a rest (Score:3, Informative)
Good grief. BSD was once the great, now its like a garage hobby, albeit at an expensive elite univeristy.
Impossible.
1. A beta of OSX wasn't even released until 1999.
2. Although FreeBSD can trace its roots to the 4.4BSD from Berkley, the univeristy has nothing to do with active FreeBSD developemnt today (unless students & profs do work on their own).
Re:BSD/OpenDarwin Questions (Score:2)
When it comes to running a server, it's probably best to just stick with FreeBSD or Solaris if you want performance, or OpenBSD if you want security. The hardware support is far better, bugfixes are quicker, and support is easier to obtain.
Re:But are the ports ready? (Score:2)
Re:But are the ports ready? (Score:2, Informative)
I have migrated 6 machines from 5.4-RELEASE to 6.0-RC1 without any problems with recompiling ports (including: Postfix, Perl, SpamAssassin, Python, Apache 2.0, PHP 5, PostgreSQL). You may want to go with the stock GENERIC kernel configuration file that comes with 6.0-RELEASE and trim it back down as some of the options have changed.
Also, che
Re:But are the ports ready? (Score:2)
What is the status of SMP support? Should I run FreeBSD on a multi-proc system?
What about threading? What about Java?
I'm also a little curious about virtualization (like with Xen), but that's not my top priority right now.
Re:Cisco VPN Client (Score:2, Informative)
Re:From what I have heard of FreeBSD (Score:4, Informative)
In addition, the ports system makes installing software a snap, and the online FreeBSD Handbook and FreeBSD FAQ are very well-written and kept up to date if you have any questions.
Re:From what I have heard of FreeBSD (Score:5, Informative)
Rubbish. It's BSD, which means it's a Unix derivative. If you're familiar with one, you're familiar with them all. There are some differences, of course, but a skilled administrator or gifted hacker could bring themselves up to speed in an afternoon. If by "hard to use", you mean "there's no pointy-clicky administrative interface" then perhaps. However, most system administrators who have to deal with production systems all day long (FreeBSD's target audience) don't want any of that anyway.
I'm not sure what kind of environment FreeBSD is deisgned for (servers, desktops?)
FreeBSD is almost entirely geared toward servers. There are various movements and projects underway to help bring FreeBSD closer to the desktop, but it's nowhere near as strong as Linux in that arena. Linux is a good general-purpose Unix-like OS, but FreeBSD is typically regarded as a more solid server.
but the fact that I don't even know that says a lot
Forgive me for being blunt, but it only says that you didn't even bother looking into it. All of what I've stated here is fairly common knowledge to those who care enough to find out for themselves. We live in the age of the Internet. If you're curious about FreeBSD or any other operating system, go read up on it, don't just sit around to hear about it.
Re:Good choice for a *AMP stack? (Score:2)
And maybe you also have in mind to put that experience on your resume. It might be better to use FreeBSD if you work in the ISP business and for general IT, Linux might be better.
All things considered, Linux is more
Re:So many BSD... (Score:2)
Not OpenBSD, though. The development model of OpenBSD entails two releases each year (1th May and 1th November), while until recently NetBSD and FreeBSD had a different model with years between each major release. Very loosly speaking, the OpenBSD model is time driven while the other *BSD is feature driven.
It's a bit funny that NetBSD and FreeBSD is released at the same time as OpenBSD traditionally has been.