Slashdot Mirror
FreeBSD 4.1.1 vs. Linux 2.4
A reader writes: "This byte.com
article finds byte.com's Linux guru wondering why he isn't running
FreeBSD. 'Linux 2.4.0 is available for no money. So is FreeBSD. Linux uses
advanced hardware, so does FreeBSD. FreeBSD is more stable and
faster than Linux, in my opinion. We penguinistas sometimes believe
we are having more fun than anybody. But then I lean over the fence
and discover the FreeBSD folks are having a hell of a party, too. And
their OS is as fast as I have seen.
I have to ask myself why I don't just switch my server to FreeBSD.'"
If FreeBSD is a server-only OS why did it get USB support before Linux did?
If FreeBSD is a server-only OS, what is PicoBSD all about?
Fact of the matter is FreeBSD serves multiple intrests as well. And it does them all reasonably well.
I've had plenty of people ask me if they should switch from MS Windows over to Linux. For some the answer is yes. But only if they're ready for the headaches that come with breaking from the pack. For others, I realise early on that they're going to be much more productive on a machine with an operating system that they're pretty much guarenteed to be able to be fixed by the local Best Buy.
It really isn't about which OS is the holy grail, perfect for all situations and godsend to all who use it. That's because such a beast doesn't exist. It's about finding the right tool for the job, and the right tool means not only the proper amount of control and features, but support and comfort for the person using it.
Despite what we geeks tell ourselves, an operating system is just a tool, not a lifestyle. Right? Right? Guys? Hello?
It's not really a matter of which is technologically superior, and I suspect that FreeBSD may in fact be so. However, in the particular style of searching for information on how to accomplish a particular task, I've always found the Linux information quicker and easier than for the FreeBSD way of doing things. Again, this doesn't mean that Linux is better, far from it. It's just easier for me to run thanks to the types of online resources I come across.
Your mileage, as always, may vary. Offer void in most major cities. Not to be taken internally, while pregnant, or running for Congress.
This, however, caught my eye:
long y;
y = 28.2839281;
x = 339829;
y = x / y;
Notice how I included some simple floating point arithmetic in the C program to make things just a tad tougher.
He admits he's no benchmark specialist, but any compiler worth its salt (and many that aren't) will optimize the floating point operations away. Also, since the result of the divide is never used, that will be optimized out, too.
I don't know what the real story is, and I do know a lot of knowledgeable people split on the Linux vs. FreeBSD issue. However, such a blatant error in benchmarking methodology gives me large doubts about this guy's credibility as a competent judge.
Popularity is really not a good reason to choose something. Windows is a lot more popular than Linux. It has more users, more commercial programs, more programmers, certifications, and possibly books, training courses, and any number of other things. It doesn't make it any better, really, now does it? Yes, there are more Linux users than FreeBSD users. It doesn't really make that much of a difference.
And besides that, FreeBSD out of the box isn't as friendly as most Linux distributions.
Care to justify that statement? Easier to learn, again, is questionable. It's easy to learn something if you have, say, a friend next door that runs the same thing. At my university, FreeBSD became very popular (much more so than Linux) because the people who took the time to help out and organize things knew FreeBSD best, and suggested people try it. Those same people who used Linux before considered FreeBSD much easier to learn. The same may apply the other way around in your area. It isn't a matter of ease, but your surroundings. If you go it alone, like I pretty much did, it ends up being a personal matter (discussed below). As for documentation, I'd say it depends on the person. The FreeBSD Handbook helped me through most of my trials, but some find it too complicated, and some find it too abstract. Greg Lehey's book is good. There're FreeBSD courses offered by BSDi, amongst others. The NetBSD documentation is technically great and complete.
Maybe when my hardware needs change, I'll run FreeBSD. If FreeBSD NFS and Linux NFS start talking to each other faster,...
The problem there is Linux NFSv3 implementation. Quite honestly it sucks.
They love BSD for this reason. They have told their developers to not even look at GPL code while on the job.
If anything BSD is doomed by their license(trying hard not to troll here). Most open source developers would rather not have their code end up in Windows. Hence, eventually the popularity of Linux and the GPL with developers will mean that Linux will likely overtake the BSDs in performance in the not-too-distant future.
No, Thursday's out. How about never - is never good for you?
You mean besides the benefits of standard protocols?
[In case you fail to fail to miss the point, like most mindless GNU drones, answer this question: How many successful protocols have their reference implementations licensed under the GPL?]
Well, I look at it this way. I can walk into any bookstore and get an O'Reilly book detailing how to write drivers for Linux, another explaining Linux internals in detail, yet more describing for newbies how to install same. There are wonderful distributions like Debian and (well, at least when they can make a release that allows you to get the kernel to compile) RedHat, etc etc etc.
On the daemon front, I've seen books available by mail, none in the bookstores. There's certainly a lot less in terms of choice. And you can forget finding sound drivers, or the like. What you do get is the suggestion to take the drivers from the Linux people and port them yourself. Of course you can do that, because you're a g0d l337 ha>0r d00d, right? Otherwise you'd be running Windows.
--- Jump!! Fire!! Bullet time!! - Lego version of the Matrix
FreeBSD is a pure server OS. Nobody has to worry about the other possible applications, it is designed purely for one purpose, and one purpose alone. It does it well.
If I were running a server alone, I would use FreeBSD. For any other purpose, I would use Linux. Each have their strengths.
They fuck you up, your mum and dad.
--Anticipation of a New Lover's Arrival, The
Most open source developers would rather not have their code end up in Windows.
Being an open-source developer myself, I would personally never release any of my code under the GPL. And I encourage all the coders I talk with to do the same. And once they see the reasoning behind why, most will switch. They honestly want to give their code away for others to use as they see fit. You are not giving your code away if you are requiring something back.
I tried to use the BSD license in a class where the teacher was pro-GPL and he refused to agree. Although we discussed it at great length. It turns out that at my college any professor has the right to determine the license for all code his class produces. But, even if the school had not been on his side the GPL would have allowed him to win. All he had to do was require that a GPL'd base class be included in all assignments, and everything would be forced under the GPL! He told me he was going to do this, no matter what verdict he school returned. This is just one of the reasons I hate the GPL.
I am sorry, but your little disclaimer about trying not to troll is not going to change what you said into anything less offensive to those who have been forced into submission by that filthy beast of a license! If the cost of giving my code away means it goes to Windows. Great! This again proves my favorite saying, "Those who hate Windows use Linux; those who love Unix use FreeBSD."
If the GPL becomes as prominent as you think it will be, there will be a lot of excellent coders who will take up other hobbies where freedom is maintained. But it won't happen. Communism failed in use with politics it will fail in use with code developing as well. FreeBSD will remain 'Free' and so will all the code I, and those who know the truth about giving, produce.
</rant>
---
"Do not meddle in the affairs of sysadmins,
---
"Do not meddle in the affairs of sysadmins,
for they are subtle and quick to anger."