Slashdot Mirror
FreeBSD 5.2 RC2 Now Available
Dan writes "FreeBSD Release Engineering Team's Scott Long announces the availability of FreeBSD 5.2 RC2 which fixes a number of bugs, specifically the one in which users experienced system panics during install and dynamic library problems in the 'fixit' environment. Scott is asking everyone to test this release over the holidays. You can download it from one of your preferred mirror sites." Update: 12/24 23:01 GMT by T : Dan writes with more info: "Scott Long has also laid out a roadmap for future FreeBSD 5.3 releases now that FreeBSD 5.2-RC2 is getting close to release quality."
Hey who is the OSDN hottie in red? question mark question mark question mark
I have always loved open source projects.. this has a unique opportunity of researching on your own and learning what others have done on the research.. like simple scalar tool available on University of Texas austin that allows you to research on microprocessor design I consider this one is a nice research tool in OS. Crossing my fingers for this release.
OK, this one goes out to all of you BSD trolls out there:
;-)
It's dying!
It's dying!
It's dying!
It's dying!
There... feeling better, little trolls? I know you would!
This being out of the way, kudos to all the FreeBSD developers for all the good work -- it's a nice Christmas present!
The right to offend is far more important than the right not to be offended. (Rowan Atkinson)
That means that the next two releases on the 5 branch are going to be last times new features are added to the branch before -current forks, so it's going to require a lot of testing to ensure stability.
Why do you care?
Well, if you don't ever plan on using FreeBSD, you don't. If you do use FreeBSD, tossing this release on your hardware and making sure things like ACPI function with your motherboard are really important as NOW is the time to fix them so that they can be tuned and maintained prior to the 5.3 Release when the code is marked stable.
The major changes in FreeBSD 5 are significant. There's new locking throughout the tree, which should improve SMP performance everywhere. There's also finer grained locking in the Network stacks (thanks Sam), better ACPI (thanks John), support for AMD64 (coming slowly, thanks Peter), and the GEOM disk abstraction layer (nice work PHK), which has already been shown to be useful for things like GEOM-gate (a la nbd in Linux), is getting more mature with every release.
Performance and stability
--
Use Vobbo for Video Blogs
An HP ProLiant DL140 server, apparently.
Oh wait, you've probably got a different ad...
Perhaps this "bais" is due to the fact that Linux kernel panics are not news. However, kernel panics in BSD are so rare that when they occur they are indeed news.
And yes, before the Linux hordes flames me to death, yes I know that Linux kernel does have Opteron support and has been more or less 64-bit compatible since the DEC Alpha days.
I'm talking about the distribution. I am considering buying a dual Opteron in January but all the Linux distros seem to be betas. A quick search on Google reveals that the distros have serious problems. In particular, X doesn't work and compilers fail completely.
FreeBSD reports Opteron as tier-1 hardware, so how is it?
Anybody who hasn't tried 5.2 RC2 yet is really in for a treat...
Wasn't 5.2RC2 just released?
> bugs, specifically the one in which users
> experienced system panics during install
I wonder how they expect anyone to actually use an operating system whose installation procedure makes experienced users panic... Oh, yeah; I forgot. It's open source.
/. just cannot resist the chance to take a shot at FreeBSD over a kernel panic in the story, can it? One stability issue in FreeBSD in what, 5 years?
Calm down. We are talking about the release candidate of a development branch. FreeBSD 5.x isn't stable yet. The first stable FreeBSD 5.x release will be 5.3. Nobody says that there are major problems with the stable branch of FreeBSD.
Yet, the myriad of kernel panic issues in Linux go conveniently ignored.
This is hardly on topic in a FreeBSD release announcement.
Didn't you get the memo?? Slashdot is now an Apple fan site. Since OS X is related to BSD, in the fifth cousin twice removed sort of way, you would think there would be more BSD stories.
Shhhh, you'll awaken the "16 year old in BSD daemon latex" troll with all his pictures of the only woman he's ever seen in his life besides his mom.
What's the status of pf on FreeBSD? And what's the preferred packet filtering/firewall setup these days?
The last I checked, circa 4.8, you had to recompile the kernel just to get a NAT "router."
Has NAT-ing and filtering drawn any attention in the 5.x series?
I ask because FreeBSD has about the best host adapter/hard drive support in the business [possibly better even than NetWare] - if you've got an old hba and an old hd, FreeBSD will load the drivers and do the LBA translations to perfection. I've seen countless motherboard/HBA/HD combinations where e.g. Windows 2000 just can't get the LBA translation right. Or OpenBSD, for that matter.
Which brings me to the question of Theo. Since I'm interested in NATing/PFing/SSHing, most people would say, "Then you want OpenBSD," to which I say, Yeah, some of Theo's goals are laudable, but, quite frankly, the guy's a kook, and guts of his operating system don't work all that well.
I'd rather use something designed by grown-ups.
"NOW is the time to fix them so that they can be tuned and maintained prior to the 5.3 Release when the code is marked stable..
Shouldn't this read something like:
NOW is the time to fix them so that they can be tuned and maintained so that the 5.3 Release can be marrked stable.
In other words, the code should be marked stable when it IS, rather than at some arbitrary release level.
I want to delete my account but Slashdot doesn't allow it.
that's the best part IMGO: "Scott is asking everyone to test this release over the holidays". What a scary geeks you are !
I re-iterate. -STABLE is *NOT* the most stable branch. It is not comparable to 2.4 in Linux. For more information, please see http://www.freebsd.org/handbook/current-stable.htm l (which explains the -CURRENT and -STABLE branches as well as a bit about releng.)
;))
But yes, thanks to the developers who have been working on this. And thank heavens that it's the holiday season; now I'll finally have time to work on locks in the IPv6 stack (thanks Sam and Robert
www.sitetronics.com/wordpress
It's dying!
OK, It's so much that it's dying .... it's that all these companies like SCO are able to keep living by forking off endless proprietaty code for themselves because the FreeBSD license allows it. Do a "strings" command on any SCO binary and you'd be amazed how much similar stuff they have to the FreeBSD equivalents. (what's even more amazing is that for all that copying you'd think they'd be able to make SCO stable)
Scott is asking everyone to test this release over the holidays.
Is this an example of copying the Microsoft practice of having the customers perform the actual testing?
BSD itself died, back at v4.4 when UCB stopped doing development itself. The body parts have been transplanted into computer systems all over, almost every system has some BSD code.
The current BSD's are like the children of the original, taking on the family business.
BSD is like the late, great, patriarch, whose portrait hangs on the wall, in the living room of the family mansion.
With *BSD proving to be especially resilient, *BSD trolls are facing the reality that *BSD is, indeed, not dying after all. The particularly outspoken troll known only as "Anonymous Coward" recently said, "*BSD trolls will never die, like *BSD soon will! We will never give up! Face the death of *BSD and switch to a different OS and section!" but the numbers tell a different tale. In fact, in the month of December alone, *BSD trolling is down by 14%, continuing a pattern from earlier months. *BSD may not be dying after all, but it seems to be only a matter of time before the *BSD trolls' days of trolling the BSD section are over.
Fact: *BSD trolls are dying.
An HP ProLiant DL140 server, apparently.
Oh wait, you've probably got a different ad...
For sex appeal, pretty much anything beats the geek I'm staring at. Apparantly he's using his UNIX experience to administer Windows Server 2003.
For those of you that have been neglected by the gods or ad rotation, look here. (Do you think the red ad was designed to match the /.-BSD theme?)
Whoever she is, I can tell she's into BSD.
What I really wish for is private Sys V IPC and multiple IP's for jails to be available as standard features. Currently, there are some patches out there, but they seem outdated.
Allowing freedom includes allowing people to do things you don't necessarily agree with. I used to defend the GPL consistently, but I'm starting to feel like "Free as in Speech" should also include unpopular speech, and that's what the BSD license protects that the GPL does not.
...software which OpenBSD uses and redistributes must be free to all (be they people or companies), for any purpose they wish to use it, including modification, use, peeing on, or even integration into baby mulching machines or atomic bombs to be dropped on Australia.
In the words of Theo de Raadt:
As opposed to the the GPL, which exists as Stallman's attempt to redefine "Free Software" as any software that suits his political ideology.
The GPL as a strategy is fine, but to call it "freedom" is less than honest. Whose freedom is being protected by the GPL? The developers? Not really. The developers are only allowed to use the source as long as they conform to the RMS ideology that the work they do should benefit the collective and not necessarily just the individual who wrote the software. As for the users, what freedom do they gain by using GPL software over BSD licensed software? The freedom to use software that does not co-exist peacefully with others? The freedom to view the source code they don't understand or care to understand? Besides, the original BSD software always remains free as in speech and beer, even if the Hated Proprietary Software Vendor of the Week exercises their right to protect their own interests.
I'm certain that I'll be moderated as a troll, but this something that I've been pondering quite a bit lately, and I'm certainly willing to be proven wrong.
Are you listening, Neo? or were you looking at the lady in the red dress. And speaking of red, I'm glad the OS in the red devil(er... daemon) suit is getting opteron support.
read my blog
musings on politics and technol
I agree with this post
How much longer will 5.x wear the "New Technology Release" label?
--Brian
Puhleeze.
I had three BSD servers that would crash (sometimes often, sometimes sporadically) quite often that I had to switch over to Linux and NT.
BSD users outright lie about the OS.
I'm looking forward to trying this release out; I've been using FreeBSD 5.1 for a few months and have been very pleased with both the startup time and the relatively little difference between it and Linux. I mean that from a user's standpoint of course, I know the internals are drastically different, but quite a lot of source compiles on FreeBSD pretty easily with little or no patching, and there's always ports to handle that, which, digressing, is an extremely great feature that I know other OSes have. Anyway, it's worth a try if you're looking for something new, and I don't think you'll be entirely disappointed.
OK, I just need to ask how this is a "shot" at FreeBSD when the developers themselves acknowledged the bugs that are mentioned in the /. story - In fact the release anouncement for the new RC uses the exact same wording.
Am I the ONLY fscking BSD user on slashdot without a persecution complex?
/~mikeg
I personally feel that ipfw/natd are a terrible combination, and are confusing and frustrating to use, to boot. I have been able to do everything I need to ipfw/natd, however. My major complaints were:
1. Cannot dynamically reload rules of ipfw (your connection can be broken after a flush, and before new rules).
2. Poor (really no) integration of natd/ipfw.
3. Weaker rules/macros than pf.
The FreeBSD pf port is coming along nicely. I am currently using it with a kernel loadable module and a startup script, both of which are installed by the port. You do still have to recompile the kernel:
You need these options:
"device bpf" and "options PFIL_HOOKS"
The port will tell you to do this when you install it. My transition was very easy, and immediately I was happier with pf. I had never used it before, and I prefer it immensely. I use it to do firewalling and NAT, and they are integrated, of course.
So, I'd say the status is...good! I'd prefer not to have to rebuild the kernel, but I'm used to that by now.
-Dan
I had a problem with 5.2-RC1 where by on boot the kernel would detect the HDD and say [MPSAFE] and then pause for a while, this struck me as odd, mostly because i interperated MP to be Multi-Processor, and i was on a Uniprocessor machine (and thats an AMD, not an Intel P4 w/ HyperThreading, which i know is set up as a virtual CPU in the kernel for scheduling)
If anyone knows if this has been resolved, I'll probably update my box from 5.1 to 5.2-RC2 tonight.
As a side note, I'm curious as to what ports are broken, I've yet to encounter one that I can't compile under 5.x, including all the things I used to run under 4.x/3.x/2.2.x (yes i've had the same FreeBSD box that long)
Music is everybody's possession.
It's only publishers who think that people own it.
Fuck Beta
~John Lenno
> Mastery of mspaint does not qualify you as an experienced user.
Perhaps not, but remembering that mspaint still exists might be a qualification in itself. That program seems as ancient as dosshell these days.
There are so many things in these new technology releases that I am so lookiing forward to implementing on my own machines once this branch becomes stable. GEOM Based Disk Encryption and LOMAC are among them.
The background fsck saved me a couple of times before I got UPSs for them, and the new GENERIC SMP kernel will be great once I get my new dual Opteron.
All in all FreeBSD is doing great, and I'll never go back to Linux; there's no incentive, nor need.
it's that all these companies like SCO are able to keep living by forking off endless proprietaty code for themselves because the FreeBSD license allows it.
Now this would be the company that took stock market IPO money from its GNU/Linux offering and bought the USL code. The same USL that had chunks of BSD copywritten code in the USL tree where the USL people removed the BSD license and copyright and put on USL copyrights?
Your 'statement' ignores the past. But if it helps you feel better about yourself, keep thinking BSD licensed code is somehow evil, ok?
Well, I have to say, having just installed a FreeBSD (5.1) server in my house, I am blown away at the stability and easy configurability of this thing. I built the computer it is running on for $160.00 with (obviously) cheap parts and it is perfrominig like I had really spent some money on it. This was much easier to install software for and configure than any of the Linux distros I have used in the past, including the vaunted RedHat. Stable and fast. That's what I like, and this isn't even the current fork. :-)
On a more serious note - I'd recommend any Linux fan to give FreeBSD a shot. It took me a while to get my head around the whole philosphy behind the way things are done (just as I had to get used to Linux - its just "different" to most linux distros), but once you get used to it, its far more logical and consistant. Faster, in my experience, as well.
Even if you decide to go back to Linux, knowing BSD will put you in a better position to understand the way other Unices work, as Linux is far less similar to them than BSD.
My 2c.
smash.
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
In a startling turn of events today, a previously little-known fact came into the public eye: "*BSD Sux0rs". This came as a complete surprise to the BUWLA, or BSD Users With Large Assholes, as they previously thought that *BSD 0wned.
"You see, even though I have never contributed code to any BSD project, I thought it was my duty to be a big asshole to others which don't use the OS I do, because it just 0wnz.", said one FreeBSD user. "Now that I know it sux0rs, though, I have to go find something else to be an asshole about."
One notorious OpenBSD fanatic known as WideOpen, told reporters, "I have to kill myself. This isn't how it was supposed to happen. My BSD has always been the best, and shouting that opinion in other people's faces at every chance I got has been my only hobby. It was all I ever did. It was what got me out of bed in the morning. Now I have to die. I will jam my bedpost up my ass until I hit my brain. It is the only way to go: BSD style."
In the volatile world of operating systems anything can happen. "At least we don't sux0r as much as Windows users", BigAzz, a relatively well-known NetBSD user said. "Screaming things in people's faces is my calling. Now I need to scream that BSD sux0rs. What a sad world. At least I won't kill myself like those uber-asshole OpenBSD guys. They are just way over the top. Or were, at least."
Nobody knows for sure what the future holds for the state of operating systems, but with Netcraft confirming the sux0r status, *BSD users all over the world will have to stick something else up their asses from now on or risk looking even more gay than they used to.
Why was a post detaling problems with BSD modded down, but a post that praised BSD and made unfounded cheapshots at Linux modded up?
And you guys wonder why you get trolled so much? Maybe if you folks weren't so uptight about your operating system and could have an honest discussion of the facts, you wouldn't be in this situation. But hey, you brought it upon yourselves.
Is this how you treat anyone who has anythind bad to say about *BSD? You call them names and say "its your fault!". Thats not a very professional way to keep people using your software, isn't it?
All Linux distro's do NOT share the same code! You idiot, if you're going to post nonsense about Linux stuff that you don't know, go back to windows 95 you fuck face! We don't need you with Linux you fucking retard!
Go back to windows you loser and stay out of our Linux community! Linux ownz you bitch and windows sucks as much ass as you do! Now fuck off!
HAND
The record is clear on one thing: no operating system has ever come back from the grave. Efforts to resuscitate *BSD are one step away from spiritualists wishing to communicate with the dead. As the situation grows more desperate for the adherents of this doomed OS, the sorrow takes hold. An unremitting gloom hangs like a death shroud over a once hopeful *BSD community. The hope is gone; a mournful nostalgia has settled in. Now is the end time for *BSD.
I've recently switched from Debian Linux to FreeBSD 5.2. I was running a pair of RAID-1 arrays off a Highpoint HPT372 RocketRAID 133 controller using Highpoint's rather lackluster, "open source" driver. Of course, contacting them about FreeBSD support greater than 5.0 has yielded nothing useful, so now I am on the hunt for other solutions.
I've come across offerings from 3ware, notably the 7006-2. What caught my eye about this card (well, all of them from 3ware) was that it's actually a hardware-based ATA RAID adapter (where as RAID functionality is implemented in software for most ATA controllers out there). Does this mean that I can use this card without any driver hell? Will a RAID-whatever array simply appear as another /dev/a[dr]* device or is it not that simple? (By the way, I care little about CLI tools for rebuilding the array. I am content to use the card's BIOS to do management.)
Of course, if I can solve the problem with my Highpoint, that'd be useful too. Currently, if I create a RAID-1 array, the two real disks appear as /dev/ad4 and /dev/ad5 but I also get a /dev/ar0 device. However, if I simulate a disk failure, none of the devices appear. It appears to me like FreeBSD indeed supports the RAID functionality of this card out of the box, but a bit of minor tweaking is required.
The bottom line however is I wouldn't mind buying a a RAID adapter with functionality implemented in hardware. That'd be better overall. I just want to make sure it'll work with flying colors in whatever OS I choose to use.
Join Tor today!
notice how all the moronic posts saying BSD is dead come from anonymous posters, in other words people who don't have a pair and don't have any real arguement. take a look at netcraft you bozos and see if bsd is dieing. I use bsd, it's got a much more coherent design then linux and it's documentation is much much better. It's multimedia isn't quiet as good as linux yet but that hasn't been as much of a focus as for linux. In short if you think BSD is old hat and dieing your an idiot, nuff said.
If you mod me down, I will become more powerful than you can imagine....
FOAD
http://slashdot.org/comments.pl?sid=90450&cid=7806 876
However, USB 2.0 (EHCI) is still not supported (to try it, add "device ehci" to your kernel configuration). This makes using portable hard drive enclosures under FreeBSD less than optimal, as transfers go at the slow 1Mbps of USB 1.1 instead of the much faster USB 2. No one seems to be working on ehci.c at the moment; Firewire portable drives currently seem to be a better option for support under FreeBSD.
Tired of free ipod spam sigs? Opt ou
- deal with the inevitable.
- grieve for your loss.
- move on.
Never let your emotions get tangled up with something as silly as a computeroperating system. It isn't healthy. So BSD fails. Big whoop. Deal with it and move on.
I posted the response in case some less clueful people out there actually took it as the truth.
Which was a hell of a lot more relevant than your post.
smash.
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
R.I.P. FreeBSD.
"Don't moderate just answer the fookin' question."
It hurts 'n' stuff.