Slashdot Mirror
BSD For Linux Users
noackjr writes "Matt Fuller posted among his rants a great introduction and explanation of BSD For Linux Users: 'It's been my impression that the BSD communit{y,ies}, in general, understand Linux far better than the Linux communit{y,ies} understand BSD. I have a few theories on why that is, but that's not really relevant. I think a lot of Linux people get turned off BSD because they don't really understand how and why it's put together. Thus, this rant; as a BSD person, I want to try to explain how BSD works in a way that Linux people can absorb.'"
"BSD For Linux Users"
What, was "BSD For Dummies" already taken?
ouch.. my karma is going to burn over that one
Trolling is a art,
Thus, this rant; as a BSD person, I want to try to explain how BSD works in a way that Linux people can absorb.'"
duuuuuuuhhhh When your done telling me about BSD Georgeie, can you please tell me about da' rabbits? I wanna know how dey dance and frolick in da springtime! I really wanna know about da rabbits George...duuuuhhh....
Quod scripsi, scripsi.
What's this all about?
Is it good or is it not so good?
BSD is for those that love Unix. Linux is for those that hate Windows.
Do you even lift?
These aren't the 'roids you're looking for.
Looks like the server has gone "over yonder"...
Gentoo.
;) ) and as someone who has tried Linux (most major distros), Solaris, and BSDs (Free and Open), I keep coming back to Gentoo.
;)
Seriously.
I'm sure that the "Gentoo Zealot Translator" will follow this post (or at least another one
Why? Several reasons:
1) The community. It is *fun* to be part of the community. I am on IRC as much as I can be, and I like to help, and the community helps me back.
2) Documentation. It is extensive. Unbelievably so. Even the noobiest of noobs can follow the install documents, and the rest of the documentation just r0x0rs.
3) Portage. It combines the best of apt-get with the concept of Ports, and I have yet to find that something I need isn't in Portage. While I'm sure that not everything for everyone is in there, the vast majority of people will find what they need, and even lots they don't!
4) Ease of use. Some people might see this as a negative; ie, that which is easy can't be (or shouldn't be) good. However, Gentoo can be hard too - the choice is there. You can take advantage of all that they've done to make Virtual Hosting with Apache easier, or you can ignore it and do your own thing.
It all comes down to flexibility and power in your OS. I run minimal Gentoo installs as servers at work, but have a full fledged desktop at home. It makes work easier, and my home machine way more powerful and fun than it would ever be with any other OS, and that's what I'm looking for. It's the best of both worlds.
libertarianswag.com
Apparently, since the article is currently returning a 403 Forbidden, he thinks Linux users can't handle what he has to say.
What is this?
I run FreeBSD on my computers. A lot of my friends run Linux, or at least one of the distributions of it. Naturally, then, we agree that a Unix-style operating system is the right choice, but we disagree on which to use.
It's been my impression that the BSD communit{y,ies}, in general, understand Linux far better than the Linux communit{y,ies} understand BSD. I have a few theories on why that is, but that's not really relevant. I think a lot of Linux people get turned off BSD because they don't really understand how and why it's put together. Thus, this rant; as a BSD person, I want to try to explain how BSD works in a way that Linux people can absorb.
While there's overwhelming similarity between the operating systems in most cases, there are also a lot of differences. As you probe more into the differences, you find that they emerge from deep-seated disagreements. Some are disagreements over development methodology, some over deployment and usage, some about what's important, some about who's important, and some about which flavor of ice cream is superior. Just comparing the surface differences doesn't tell you anything; it's the deeper differences that both explain and justify why each group does things the way they do.
What isn't this?
This is not:
* A list of command correspondances; "'netstat -rnfinet' on BSD = 'netstat -rnAinet' on Linux" and such things.
* How to do all the things involved in adminning and running a BSD box.
* Why you should use BSD instead of Linux.
* Why you should use Linux instead of BSD.
* Why you should use this BSD instead of that BSD.
* Why you should use this Linux instead of that Linux.
* Why BSD is Right and Linux is Wrong.
* Why Linux is Right and BSD is Wrong.
* Why I am a god and you should worship me.
I, personally, for me, believe (obviously) that my OS choice is right. That's me. I'm not telling you that you should believe it. Learn the facts, and the origins behind the facts, and make up your own damn mind. That's why you have one.
Some preliminary thoughts
There're a lot of philosophical disparity between the Linux world and the BSD world. And there are a lot of expressions about it out there. One I particularly like goes something like:
BSD is what you get when a bunch of Unix hackers sit down to try to port a Unix system to the PC. Linux is what you get when a bunch of PC hackers sit down and try to write a Unix system for the PC.
Now, I like that quip, not because it's some sort of absolute revealed truth, but because it gives a very good feel for some of the differences. The BSDs, in general, are very much more like traditional Unices than Linux is. A lot of that is because they're direct-line descendants of the BSD from Berkeley, which was a direct-line descendant of the original AT&T Unix. Unix-the-trademark is a trademark of The Open Group, and Unix-the-code is owned by SCO, so one can't actually say that the BSDs are really Unix (that's the sort of statement that triggered the USL/UCB lawsuit extravaganza, in fact). But, in many ways, the BSDs are direct derivatives of traditional Unix.
That shows through in a lot of ways. It shows up in the design of the base system and the packaging of addons. It shows up in the partitioning of the mass storage. It shows up in a lot of details of the commands. And it shows up in the attitudes and reflexes and prejudices of the developers, which are reflected in the code and in the users.
BSD is designed. Linux is grown. Perhaps that's the only succinct way to describe it, and possibly the most correct.
Where to begin?
BSD or linux? Who cares what's running on it... The server screams in pain and agony when it's slashdotted out of existence.
It's better to burn out than to fade away
Forbidden /~fullermd/rants/bsd4linux/bsd4linux1.php on this server.
You don't have permission to access
At least BSD lets you log in and change file permissions whilst being slashdotted, impressive!
Beep beep.
He could have gotten across all of the ideas in that introduction with three sentences.
I want to try to explain how BSD works in a way that Linux people can absorb.
Just sprinkle your explanation with random anti-Microsoft rants and talk of your imminent death, and you'll do just fine.
BSD (server) is dying! (from being slashdotted)
...the rant says "Forbidden You don't have permission to access /~fullermd/rants/ on this server. Apache/1.3.27 Server at www.over-yonder.net Port 80" and the main link says "Warning: main(../../php_inc/styleswitch.php): failed to open stream: Too many open files in system in /home/fullermd/public_html/php_inc/main.php on line 16 Warning: main(): Failed opening '../../php_inc/styleswitch.php' for inclusion include_path='.:/usr/local/share/pear:/usr/local/s hare/smarty') in /home/fullermd/public_html/php_inc/main.php on line 16 Warning: main(../../php_inc/ahem.php): failed to open stream: Too many open files in system in /home/fullermd/public_html/php_inc/main.php on line 19 Warning: main(): Failed opening '../../php_inc/ahem.php' for inclusion (include_path='.:/usr/local/share/pear:/usr/local/ share/smarty') in /home/fullermd/public_html/php_inc/main.php on line 19 Fatal error: Call to undefined function: print_ahem() in /home/fullermd/public_html/TEMPLATE.php on line 94".
Could someone please be kind enough to post a mirror?
--
FreeNET user? Comfortable with the adverse selection?
Well, my suggestion would be to use a lot of pretty pictures interspersed with interludes on where Linus is, what Linus is doing, what Linus was wearing, what Linus said, what Linus' facial expression was as he said it, if Linus will be say something like that again, perhaps, in the future, and where Linus might be living or moving to, maybe, perhaps, possibly.
Then I'd lead all the Linux users out to a fertile field where they could graze for the day, protected by a couple of good dogs, herding them in, keeping them together, where I'd sit back and enjoy their gentle baying in the summer sun: Liiiiinnnnux, Liiiiiinux ...
Chr0m0Dr0m!C
We'll have rabbits and chickens and live off the fat of the LAN.
Appologies to Steinbeck
Perhaps for the same reasons that the Branch Davidians or the Ralieans knew more about the Cathloics than most Cathloics knew about the Branch Davidians or the Ralieans? Maybe Linux is just a much more widespread cult than BSD.
I'm an American. I love this country and the freedoms that we used to have.
How is it that all the top servers in uptime(NETCRAFT) run bsd? Some of thier servers have been up for years. What is it about bsds' design that facilitates not shutting down the server while fixing stuff? I'm guessing it must be modular and allow for you to just compile an updated module and then insert it into the kernel. Anyone care to enlighten me. Just curious.
I'm I the only one going cross eyed trying to read this??
This is not:
* A list of command correspondances; "'netstat -rnfinet' on BSD = 'netstat -rnAinet' on Linux" and such things.
* How to do all the things involved in adminning and running a BSD box.
* Why you should use BSD instead of Linux.
* Why you should use Linux instead of BSD.
* Why you should use this BSD instead of that BSD.
* Why you should use this Linux instead of that Linux.
* Why BSD is Right and Linux is Wrong.
* Why Linux is Right and BSD is Wrong.
* Why I am a god and you should worship me.
Steve
Candle burns its brightest in the dark
It's been my impression that the BSD communit{y,ies}, in general, understand Linux far better than the Linux communit{y,ies} understand BSD.
And my impression is that Ogg communit{y, ies}, in general, understand Mp3 far better than Mp3 communit{y,ies} understand Ogg
*ducks*
Free XBox, PS2
I think I'm gonna go put up an article on my Linux server called: Setting permissions and running a webserver 4 BSD users who preach to Linux Users.
Honestly though, whats the point here? You chose your OS, I chose mine. Do I really need an entire website dedicated to why you chose yours over mine?
I read enough of this stuff here
"why don't you just slip into something more comfortable...like a coma!"
Who are the characters?
Meet the players
I'll give here a quick introduction to and discussion of the systems I'll be talking about. Note that the histories presented are not comprehensive or authoritative, and no attempt has been made to make them that way. Deal.
Unix
Unix isn't (precisely) an operating system.
Well, it is, and it isn't.
In specific usage, Unix is an operating system originally developed in the late 60's at Bell Labs by Ken Thompson and Dennis Ritchie. Over the years since then it's been developed and distributed as a commercial operating system, and a research operating system, by Bell Labs and USG and USDL and ATTIS and USL and Novell and SCO and anybody else who could come up with an acronym.
It's probably not too much exaggeration to say that Unix is the single most influential operating system in modern computing. Every general-purpose computing device you'll find, and a lot of specific-purpose computing devices, will be using ideas and concepts and often code from something in the Unix family tree.
When we use the word 'Unix', then, we far more often mean the general form, than the specific OS that carries the name Unix(TM). The general form means "Any operating system which, in design and execution and interface and general taste, is substantially similar to the Unix system." That means all the BSDs, Linuxen, SunOS, Tru64, SCO, Irix, AIX, HP/UX, and a cast of hundreds or thousands of others.
I'm not interested in getting into semantic discussions about how many angels can dance on a head of split hair. Let it suffice that when I use phrases like "Unix systems", I mean exactly what you think of when I use the phrase. Pedantry City is ---> that way.
Linux
Linux also means several things. It's a kernel, originally written by Linus Torvalds when he was a student in Finland. Since then it's been beat up, punched around, tweaked, poked, prodded, manged, digested, spit out, stomped on, chewed up, tossed out, brought in, and otherwise manipulated (not necessarily in that order, of course) by more other people than you could easily count.
Linux is also the term for a family of operating systems. While there are fascinating metaphysical discussions taking place in dozens of places around the world at this very second (I guarantee it) about how "Linux isn't really an operating system, it's just a kernel", or "It should be called 'GNU/Linux'", or similar topics, I'm also going to neatly avoid that semantic cesspool. When I say "Linux", I mean Red Hat. I mean Slackware. I mean Mandrake. I mean Debian. I mean SuSe. I mean Gentoo. I mean every one of the 2 kadzillion distributions out there, based around a Linux kernel with substantially similar userlands, mostly based on GNU tools, that are floating around the ether.
BSD
BSD stands for "Berkeley Software Distribution". Originally, it was a set of patches and extra add-on utilities for the official Bell Unix system that were developed by the CSRG at the University of California, Berkeley. Over time, it evolved to change and/or replace more and more of the system, until at some undefined point it became basically its own OS that merely happened to share chunks of code with Bell's Unix system.
Of course, it still required that you have a Bell license to use the system, since a lot of it was still Bell's code. All of the code written by Berkeley, however, was released under what's come to be known as the BSD license, which basically translates to "Do whatever the hell you want with the code, just give us credit for writing it". And a lot of the BSD code ended up working its way back into the "official" Unix system too, in System III and System V. And, a lot of both strains worked their way into the various commercial forks of Unix.
After the CSRG (mostly) dissolved and stopped developing the BSD system, several groups went off different ways with the code. One of these was the 386BSD project, which took the BSD code and made it run on the Intel i386 platform.
Help Brendan pay off his student loans
What does the {y,ies} in the article mean? Anyone?
I might appreciate your opinion of linux better, if you could set up a BSD box that can withstand a slashdoting... :-)
/etc/(rc.d/)init.d, and ps -ef) rather than the BSD approach (as in /etc/rc.d/rc.local and ps -aux)
*BSD's have a different approach to *NIX than most linux'ers. Most of the linux distro's have gone with the SYSV approach as default (as in
It's kinda odd. The BSD's and SYSV's are different superficially (some command line arguments) and at the deep kernel level, but the mid-level abstractions are almost identical (similar syscalls, etc). It's all UNIX though.
Zapman
.. there is something in my eye. That's all.
It's hard to believe that's how Micronians are made. Why don't we see it right now by having you both kiss one another?
how does it's functionality compare to Linux? I've heard something about "ports" where Linux apps must be ported to *BSD.
Does this mean that Linux apps and source are not readily available to compile on *BSD machines?
BSD is designed. Linux is grown. Perhaps that's the only succinct way to describe it, and possibly the most correct.
/.er who posted the first page, but the author).
He jests (not kind
BSD has grown from each previous BSD and then from each previous UNIX. How he can say this is more "designed" than Linux I'm not sure.
Sam
blog.sam.liddicott.com
Here is a mirror of another page of it:
:: The Base System :: The Ports Tree :: Releases :: Upgrading :: Ports
System Upgrades
Building the world in less than 7 days
As a result of the fact that the BSD base system is developed as a single unit, you can easily get the entire source tree for the entire base system. And because of the way it's designed, you can execute a single command at the top level to compile everything. For most of us, that's the normal way to upgrade; you update your source tree to the absolute latest (with a few hours, of course) changes made by anybody, compile it, install the new binaries, and you're done. Miller time.
Of course, you might not necessarily want the latest. You could grab the sources from last week, say. And normally, you do the whole rebuild process in four steps. You start with a make buildworld which compiles all of userland, then a make buildkernel which compiles the kernel. Then you take a deep breath and make installkernel to install the new kernel, and make installworld to install the new userland. Each step is automated by a target in the Makefile.
Of course, I'm leaving out tons of detail here. Things like describing the kernel config, merging system config files, cleaning up includes... all those gritty details. If you want to read about that, check the FreeBSD handbook, specifically the sections on updating and building and configuring your kernel, or the various other forms of documentation available. But those sort of things become second nature after you do them a few times. Really, the process of updating your system boils down to those four commands. I find it a lot easier than having to resolve cross-dependencies and changed library versions and such across a zillion binary packages.
This information is mostly based on FreeBSD. NetBSD uses a different model for doing the system builds. OpenBSD tends to be much more in favor of reinstalls, at least for major version changes.
Addon software
Well, that sure was easy. But, what about all those add-on packages? How do we manage those? Let's talk about installing and upgrading ports.
1. Intro
2. Dramatis Personae
3. Design
4. Design
5. Technical
6. Technical
7. Technical
8. Philosophy
9. Myths
10. Conclusion
Comment removed based on user account deletion
The BSDs all keep the system under revision control; all the free BSDs use CVS. Revision control (in extremely brief) is a process by which editing a program means checking out a file or group of files, making the changes, then checking in the new versions, along with a message describing the change. A full history of all changes is kept in the revision control system, so you can view a history of the changes, check out an old version, look at the differences between arbitrary versions, etc.
All the BSDs provide public access to their CVS repositories in one way or another; generally through anonymous CVS, or CVSup checkout or mirroring, or often both. That means that, as a user, you can see exactly what changes happened when, who did them, and why they did them. You can also always get your hands on the latest changes (within a few hours, anyway, depending on mirroring strategies). All of the free BSDs have mailing lists that you can subscribe to and see the changes as they're made. In fact, they all have web frontends as well; you can poke around FreeBSD's entire source tree online at http://cvsweb.freebsd.org/src/, and see all the history of every file.
Linux, historically, hasn't used any version control for the kernel. I don't have exact data at my fingertips here, but I believe it was somewhere in mid-2.4 days that the kernel began being kept in a public BitKeeper repository. Many of the other utilities use revision control, but since they're all developed separately, there isn't any central place you can go to to look through the changes. So it's sometimes hard to get a historic picture of even any one part; to so do for a whole distribution is practically impossible.
This leads to a lot of differences. In a very real sense, BSD systems are constantly developed; I can always update my system to the absolute latest code, irrespective of "releases". In Linux, that doesn't really have as much meaning, because the release process is very different. I think the most appropriate verb for a Linux release is "assembled". A Linux release is assembled from version A.B of this program, plus version C.D of this program, plus version E.F of this program... all together with version X.Y.Z of the Linux kernel. In BSD, however, since the pieces are all developed together, the verb "cut" makes a lot more sense; a release is "cut" at a certain time.
Linux releases kernels in two parallel lines (well, often more than 2, but we're simplifying); a version with an odd minor release number, as a "development" version, and a version with an even minor release number, as a "production" version. The BSDs also have "development" and "production" tracks, but they're handled rather differently.
CVS, like most version control systems, has the concept of "branches". It's easy to understand, but somewhat difficult to explain. Basically, when you "branch" a file or a set of files (or a whole directory tree), you create a new version of the file which exists in parallel with the primary version. When you make changes to the primary version, it doesn't affect the branched version. And you can make changes to the branched version without affecting the primary.
In FreeBSD, there's usually 2 active development lines; one called "-CURRENT", which is the development version, and the other called "-STABLE", which is the production version. Both, of course, are under development, and both have some attempt to be made to keep them usable. -STABLE, as a rule, gets bug and security fixes, but only gets new features and such that are well tested, usually by a stint in -CURRENT first. -CURRENT gets new features, big architectural changes, and all those sorts of new development stuff. It should be noted that the naming of the branches doesn't necessarily mean what it seems to; while -STABLE usually is "stable" as in
It should be pointed out that if ever the Slashdot community believes that the editors of Slashdot are immune to pot-stirring tendencies, then this post should serve as proof that sometimes they get bored and message each other: "The servers are slooooowww today. What can we do to get a few hundred angry comments? Oh, I KNOW!!!"
Chr0m0Dr0m!C
You trying to tell me BSD isn't another Distro of Linux?
WTF?
OS X is for... anyone who can afford the hardware?
Condescending is just the right word for the style of this rant.
My favorite snippet:
and make up your own damn mind. That's why you have one.
Oh! That's what that thing is for! Thanks for letting me know.
It's hard to believe that's how Micronians are made. Why don't we see it right now by having you both kiss one another?
Design Philosophies
General
Ah, now this is the part I enjoy. Lots of soaring generalities, without a single hard fact in sight. Saves the trouble of having to do research. 8-)
What I'm going to discuss here is some of the real and imagined philosophical differences that both cause, and are caused by, some of the technical and organizational differences we've discussed. Like most such discussions, there's little that's hard-and-fast here; there's plenty of overlap in attitudes among people in the various camps. And there's certainly plenty of completely deserved flak for both sides to take, as well as undeserved flak they've been forced to. Still, I think it's important to examine some of these splits, without trying to presume that one is "correct" and the other is "incorrect".
Realize, I must emphasize, that a lot of this is very general. Practically every point is riddled with exceptions. And both systems often don't "follow the rules", or fail to meet their own expectations. It's more a question of inclination that of exceptionless implementation. I'm just saying this now, so I don't have to keep qualifying and re-qualifying every statement I make, until it's impossible to read.
Chaos vs Order
One common generality is that the Linux methodology is the living incarnation of chaos, whereas the BSD methodology is far more about control. To a large extent, it's true. Linux grew out of a spare-time hacking background, while BSD grew out of a controlled engineering background. Of course, there's plenty of weekend tinkers writing BSD code, and plenty of full-time professional programmers sloughing away at various parts of Linux. But the feel of the systems still does reflect that sort of schism.
We've already discussed the construction methodology; BSD builds up a core system which is uniform, whereas Linux distributions takes pre-existing pieces and pretty much puts them together helter-skelter. Naturally, the BSD method is far more amenable to keeping things ordered, while the Linux method practically necessitates utter chaos. That's not to say that chaos is inherently bad, or order inherently good. They're just different environments.
Linux will also generally chase new versions of other programs much more closely, adopting particularly more major changes like Apache 2 much sooner than BSD will move that way. Now, the stricter separation of "base" vs "ports" in BSD, as well as the structure of the ports tree itself, make it easier to have multiple parallel versions of packages in BSD. Sometimes, it's even possible and easy to have multiple versions installed at the same time. Linux, by not having that sort of separation, makes it very difficult to have parallel versions, and instead almost requires a single "blessed" one.
And the primacy of source-compiling in packages also makes it easier to handle multiple versions. For instance, PHP must be compiled differently depending on whether you're using Apache 1.3 or Apache 2. With from-source packages like ports, I can define an environmental variable when I compile and install PHP to tell it whether to use Apache 1.3 or Apache 2. With binary packages, you'd have to have 2 separate packages available, which will lead to confusion sooner or later.
Right vs Wrong
The difference can also be seen in the way core code is integrated. BSD tends to always shy away from hackish solutions when there's even a hint of a proper solution in the wings. The theory is that it's far easier to wait for the clean answer, than to integrate the dirty answer now, for several reasons. For one thing, if you integrate the dirty answer, that reduces the incentive to implement a better one. For another, once you dirty up the architecture to integrate something it'll never get cleaned up again. You know it as well as I do. Oh, sure, you'll say it's temporary. But you know there's nothing quite as permanent as a temporary stop-gap. And things grow. The only way to avoid giving a mile is to refuse to give the first inch. It's just lik
It this an arrogant statement or what ? This sort of moderate arrogance, of showing off some alleged superiority, together with the constant efforts to undermine Linux from some BSD enthusiasts, don't really help me get interested on BSD.
But the reason I use Linux rather than BSD is simple: I personally prefer the GPL rather than the BSD License. Let alone the argument of which is better, I heard both sides several times, and I prefer the FSF's philosophy. This doesn't imply that I don't like the BSD philosphy. If the Linux kernel didn't exist, I would definitely be running KDE on to of some flavour of BSD ...
Obviously it's not a scalability article.
/home/fullermd/public_html/php_inc/main.php on line 23
/ share/smarty') in /home/fullermd/public_html/php_inc/main.php on line 23
/home/fullermd/public_html/php_inc/main.php on line 24
/ share/smarty') in /home/fullermd/public_html/php_inc/main.php on line 24
/home/fullermd/public_html/TEMPLATE.php on line 15
/ share/smarty') in /home/fullermd/public_html/TEMPLATE.php on line 15
Warning: main(../../php_inc/navbar_rant.php): failed to open stream: Too many open files in system in
Warning: main(): Failed opening '../../php_inc/navbar_rant.php' for inclusion (include_path='.:/usr/local/share/pear:/usr/local
Warning: main(../../php_inc/navbar_sgml.php): failed to open stream: Too many open files in system in
Warning: main(): Failed opening '../../php_inc/navbar_sgml.php' for inclusion (include_path='.:/usr/local/share/pear:/usr/local
Warning: main(.data/bsd4linux1.vars): failed to open stream: No such file or directory in
Warning: main(): Failed opening '.data/bsd4linux1.vars' for inclusion (include_path='.:/usr/local/share/pear:/usr/local
int27
Why do I run BSD?
It Just Works. When I install the system, a set group of pieces are there. Period. When I go through the upgrade process, it works. When I install an addon package, it works.
It supports practically every piece of hardware I've thrown at it in close to a decade of use. And that support Just Works, it doesn't flake out or fail from one version to another.
I can choose whether to stick with tried and tested release versions, to track the -STABLE branch, to track the -CURRENT branch... however close to the edge I want to live. And even the bleedingest edge usually works just fine. I can take a system that hasn't been touched in 3 years, and bring it up to date with minimal pain.
When a problem comes up, whether it's security or stability or performance or even just aesthetics, it gets fixed. And because of the development methodology, I can get those fixes later that same evening. All the time. When a new feature gets added, I can grab it right now, not wait a week or a month or 6 months until the next release. I can see, whizzing by in my email, every change as it's made. Or, when something breaks, I can fix it myself, and be able to send the fix right off to somebody who can get it incorporated into the system right away. I've done it before, I'll do it again, and so have thousands of other people.
It's designed to all fit together. Not just munged after-the-fact to go together OK, but designed from the ground up to be a single coherent system. And when something doesn't fit, it's a bug to be fixed, not just "part of the game".
It's had quirks. It's had vagueries. It's had out-and-out bugs. It's had bizarreness. It's had inexplicable behavior. It's given me misleading error messages. Sometimes, it out-and-out breaks things that worked yesterday. And all those will happen again in the future. But, every time, somebody goes right ahead and notices, and discusses, and fixes it. I read the mailing lists, and I see these things go by. I see the problem brought up, I see the people who know the area discussing it, I see solutions proposed and discarded and tested and agreed upon, and I see them committed into the main repository. And usually by the time I see it happen, I can already get my hands on it.
It's just a level of consistency and transparency and usability lightyears beyond anything else I've seen. Its development path is aimed at technical merit and correct solutions, not just sexy features and workable hacks. And I think that's the only way to be sustainable long-term.
Why should you run BSD?
Well, I don't know. Does what you have now meet your needs? Then you probably don't have an urgent need to change anything.
There're plenty of essays and rants on there about why X works better than Y, for any values of X and Y. I don't want to write another one. If and when you do get time or inclination or resources to try BSD, I want this essay to help you understand why some of those differences are there, and what the result of those differences is.
More info
All the BSD's sites (FreeBSD, NetBSD, and OpenBSD) have extensive documentation available on their systems. Because the base system is integrated, all things dealing with it can be authoritatively documented in a single place. They describe the strengths and weaknesses of the individual systems, how to install them, how to upgrade them, how to admin them... Everything you need.
In the FreeBSD docs in particular, the article on Explaining BSD is similar to this essay, in that it describes BSD and its historical context. There's all kinds of documentation, from introductory documents describing the basics of FreeBSD and Unix-type systems, to detailed descriptions of the inner workings of the kernel, and everything in between. Scroll down the page.
And, of course, the FreeBSD Handbook, and the FreeBSD FAQ are both stuffed with information you never even knew you needed. Don't leave home without it.
The BSD's also all have mailing lists and news
1,2c1,4
,
The GNU General Public License (GPL)
> Version 2, June 1991
> Copyright (C) 1989, 1991 Free Software Foundation, Inc.
> 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
4c6,7
Everyone is permitted to copy and distribute verbatim copies
> of this license document, but changing it is not allowed.
6,9c9,125
nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
Preamble
>
> The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Library General Public License instead.) You can apply it to your programs, too.
>
> When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.
>
> To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.
>
> For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
>
> We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.
>
> Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.
>
> Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.
>
> The precise terms and conditions for copying, distribution and modification follow.
>
> TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
>
> 0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".
>
> Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if
vodka, straight up, thank you!
...uhh ... anyone wanna enlighten BSD users on bandwidth?
FLR
... in this context, community and/or communities.
...Linux isn't UNIX. It's an independent project, despite what SCO thinks.
I wonder how funny it would be to tell SCO that BSD is a direct derivative work from AT&T UNIX...
Do not look into laser with remaining eye.
Warning: Unknown(/home/fullermd/public_html/TEMPLATE.php): failed to open stream: Too many open files in system in Unknown on line 0
/ share/smarty') in Unknown on line 0
Warning: (null)(): Failed opening '/home/fullermd/public_html/TEMPLATE.php' for inclusion (include_path='.:/usr/local/share/pear:/usr/local
because I see any efforts amdcontributions I end up making to that system as a waste
What contributions have you made to Linux or other GNU project?
Well, being such an curious person, I wanted to see what is this BSD thing. And i got my hands on 5.2 REALEASE and gave it a shot. Well, i was surprised. It is very different from linux (not just another tool for the job, but the arhitectural thing is diferent). It seemed to me that it really runs faster, it's more responsive. While i compiled various applications from ports, the cpu was at 100%, but whenever i issued a command, it was executed instantly. I must say, that this does not happen in linux. Probablly i have used linux more, and I know its ups and downs, and in freebsd i have only seen the ups in such a short time, but man ... I love it.
I really do.
And how, exactly, does that make your efforts a "waste"? Does Microsoft using your contributions prevent anybody else from using them?
Only 31 comments so far and it is slashdotted.
Are Slashdot readers actually reading this story? What with Linux, BSD, and rant in the title it must be good. :)
I guess that is what I get for working on Friday afternoon instead of reading Slashdot. It is time for the afternoon sun to wash out my monitor anyway, so I have to take a break.
</worthless_post>the_crowbar
Have you read the Moderator Guidelines
ports in this case are completely not what you have described.
ports are what gentoo ebuild scripts are based on. you snag the source for whatever program you are installing and it's compiled on the spot.
there are apps that are linux-specific, and there are some that do not rely as much on linux in particular that will compile readily on other unices.
I think that most Linux people don't care about BSD because it sucks: it's hard to install and it's hardware support sucks and it doesn't do anything better than Linux anyway.
Reading the article, I got this error. Assuming the web server is running on BSD, I guess that is one difference between Linux and BSD. Seems a little severe to me, but I guess that is the vaunted BSD security for you.
/~fullermd/rants/bsd4linux/bsd4linux8.php on this server.
Forbidden
You don't have permission to access
Apache/1.3.27 Server at www.over-yonder.net Port 80
Give a man a fish and he will eat for a day.
Teach him to eat and he will fish forever.
Jon
God bless the slashdot fool who knows nothing of the subject matter they are discussing and yet perfectly willing to give an opinion based only in their own delusions.
Help Brendan pay off his student loans
BSD = Black Spiral Dancer
Slashdot = The Wyrm when Gehenna & the Apocalypse arrive!
"There is always some madness in love. But there is also always some reason in madness."- Friedrich Nietzsche
I agree. Who is a much more appropriate relative pronoun.
Both communities should remember that development for either tends to benefit both.
A lot of BSD code flows into Linux, and a lot of apps that are made worthwhile (in terms of size of userbase) by Linux are ported to BSD.
Every person using Linux OR BSD is an asset to the free software community, and helping things in the right direction. There is no need to get pissy over small things like licenses or religious wars until only Linux, BSD and other free OSes are left standing and all other non-free systems are long buried.
Beep beep.
It's just fine the the lin-ewbies stick with linux, I'm find being on of the only guys who knows how to fix bsd, we don't need the lin-ewbs doing it.
Plus, at the same time, I can fix linux!
And thus:
#1. Hold the brothers down!
#2. ???
#3. Fix their shit that they are ignorant about.
#4. ???
#5. Profit!!!!
In the December 2003 issue had an article "The other open source OS" on page 14. It looks like a case of lets split hairs.
FreeBSD is binary compatible with Linux, that's all you need to know about Linux to make things work. Of course native BSD applications are more likely to be more reliable. Part of the Linux emulation involves emulating bugs in the Linux kernel. How do you like that?
Well, that's kinda funny.
/usr/ports/www/apache13/
Because there's nothing on Linux that most Windows users think they need or want, yet how many people are standing on street corners praising Linux and all it's glory over Windows? More software is written for Windows, and there's alot more support available.
And, BTW, I run FreeBSD. And I don't have to know anything about linux to get any of the apps I want running. It's called the ports collection.
Want proof? Here's a sample apache 1.3.29 install.
cd
make install
BIND and sendmail were originally developed at Berkeley as part of BSD
Aha, so that's where the blame lies! ;)
"BSD is designed. Linux is grown. Perhaps that's the only succinct way to describe it, and possibly the most correct."
I'm wondering what he's smoking. Of course, if he's in Berkeley maybe he's using more LSD than BSD...
If the SCO lawsuit has done anything positive, it has caused a lot of research into the history of UNIX and its derivatives. And based on the continuous ripoffs between Berkeley and AT&T, BSD definitely didn't start out with a plan. Linux hasn't forked into eight or nine individual large projects, and is still spearheaded by its original creator, who ultimately decides what goes where or delegates the decisions. True he takes input from more and more people, and probably has less direct control than he used to, but the core of what is wanted for the next stable series is usually pretty clear once things are played with.
and other than Slackware, all of the distributions seem to be pretty tight too, not just falling completely where things end up.
Do not look into laser with remaining eye.
I'm one of those guys who used a lot of Linux, still like it on the server side and now I use OS X on the desktop side, but at the advice of some of the penetration testers I worked with, I decided to give OpenBSD a shot on my rebuilt home server.
/var/www and none else), but within hours someone posted a polite "Oh, try this".
It's one of those things where for a bit, I was a little confused on how things work. Granted, OpenBSD is not as "user friendly" on the install as, say, Red Hat 9, where you click the pretty buttons and things install. But thanks to a copy of "Absolute OpenBSD", I got it installed.
And I have to admit - for my server love, it's working pretty well. The ports system works like I'd always dreamed RPM's to work - tell it "install", and it gets the source, check it for dependancies, and go on.
The Flavor setting is another one I think I can live with, since you can specify there things like "Plaintext imap" versus default "secure imap" and the like.
And everything is right where I'd expect it. Ports installed files are in local, so now I can remember where everything is at once it's installed.
And it's pretty small - little "crufiness", and the community has been great. Like when I couldn't get Apache, PHP, and MySql to play. Turns out it was a socket issue (Apache on OpenBSD by default only wants to see things in
So far, as a server system, I'm beginning to groove on it. Perhaps if I wanted to run it as a desktop I might or might not have other issues, but since I've got a different OS for my desktop things, I'm pretty pleased with the BSD system.
Next up: learning how to upgrade. Not that I need to yet, but it's that "yet" that I'm anticipating. (Hey, there could always be another ssh exploit - you never know.)
52 Weeks, 52 Religions with John Hummel
[ed. note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]
When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.
Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.
FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.
It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.
So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.
Discussion
I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.
From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.
There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.
Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.
Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?
Shouts
To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.
To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real goals. It
Since I own dead tree versions, I have no idea if they're easily available or have been collected together.
One line blog. I hear that they're called Twitters now.
The concept of the "base system" is something that, I think, causes the most trouble for people used to the Linux methodology. Which is perfectly understandable, because the whole idea just doesn't even exist in the Linux world.
Linux, from the start, was just a kernel. Without getting into the eternal debate of what an "operating system" precisely consists of, it's easy to state that a kernel by itself isn't very useful. You need all the userland utilities to make it work. Linux has always been a conglomerate; a kernel from here, a ls from there, a ps from this other place, vim, perl, gzip, tar, and a bundle of others.
Linux has never had any sort of separation between what is the "base system" and what is "addon utilities". The entire system is "addon utilities". MySQL is no different from ls from KDE from whois from dc from GnuCash from ...
Every bit of the system is just one or another add-on package.
By contrast, BSD has always had a centralized development model. There's always been an entity that's "in charge" of the system. BSD doesn't use GNU ls or GNU libc, it uses BSD's ls and BSD's libc, which are direct descendents of the ls and libc that where in the CSRG-distributed BSD releases. They've never been developed or packaged independently. You can't go "download BSD libc" somewhere, because in the BSD world, libc by itself is meaningless. ls by itself is meaningless. The kernel by itself is meaningless. The system as a whole is one piece, not a bunch of little pieces.
Now, X isn't a part of the FreeBSD base system. It's an addon package. Since X isn't part of the base system, X apps like xterm and KDE and Gnome and Mozilla and gaim and xmms and such obviously can't be part of the base system either. They're add-on packages, which are treated and thought of differently. The primary difference is where they're developed.
NetBSD and OpenBSD do have an X implementation in the base, because of the way they integrate it with their console driver. They both use heavily modified, very custom versions, so it's not feasible to keep it as a separate package.
The entire base system is developed together. To be sure, there're parts of the base system like sendmail and BIND and tcpdump and ssh and such, which are in fact individual packages which are developed elsewhere. There are even some GNU packages like groff and gcc and gzip and such, which will be immediately recognizable to any Linux user. But these are treated specially, in that versions are imported into the tree, then molded to fit the rest of the system. In fact, many of them used to be BSD-only; BIND and sendmail were originally developed at Berkeley as part of BSD, and only later became available separately. My FreeBSD system claims to be running gcc version 3.2.2 at this moment. Technically, it's not really gcc 3.2.2; it's a FreeBSD compiler based on gcc 3.2.2. The version of tcpdump I've got here isn't technically 3.7.2, it's a FreeBSD tcpdump based on tcpdump 3.7.2.
In most cases, of course, the FreeBSD version is practically indistinguishable from the vendor version. There're usually some changes to the compiling setup (Makefiles and such) to let it build cleanly with the rest of the system, and occasionally some necessary patches to make it compile and run right. Some changes are more extensive, and some are massive. But, they're all maintained together, and forced to play nicely together. There's a basic assurance that the pieces in a BSD base system all fit together, by design.
The primary reason an externally-maintained package becomes imported into and tracked in the base system is that it is, in some way, basic enough to the functioning of the system that it's easiest to have it there by default. FreeBSD currently uses the OpenSSH ssh server and client, which are integrated into the base system because, in this day and age, a secure remot
CSS is great, when used correctly, especially for professionals and large sites.
Some advantages of css:
- sitewide changes by changing 1 file
- ability to play with changes, in real-time, by using one of the several css-switching/editing plugins, without affecting other users
- complete control over fonts, colors, spacing, etc
- seperation of data from presentation, which leads to:
- ability to change the presentation based on the output device (browser, printer, tele-type, etc)
- (MUCH) smaller pages which leads to:
- faster loading pages
Not every site should use CSS, but it is a nice technology to have, quirks and all.
I can see the conversation now...
"d00d, my server is b0rk3d!
"again?
"DSL pipe saturated too. think I got slashdotted?"
"d00d, get a _real_ hosting service...
(Just to prove to the Slashdot advertisers that some do read their pitches...:)
I was a linux fan from quite a while back and I decided to try FreeBSD to see the differences.
I installed it without much difficulty and poked around. I liked what I saw. I sorta shrugged my shoulders and said "Looks like a Unix system to me" and continued using Linux.
I was using Redhat for the longest time before RHAT forced me into migrating (Mandrake if you must know). I never really saw a reason to switch from this distro to that distro unless the features were significantly different.
I think it's all what you get used to and prefer. I never understood the BSD/Linux platform wars. To me, we're on the same open source team. As long as I can download the code, I don't see a big problem. If SCO got their wish and asked me for 699$, you can bet I'd be hopping straight over to FreeBSD. All the software I need is there anyhow.
After all, LinuxDistros/BSD aren't so different when they share the same features (KDE, openoffice, etc...)
"as a BSD person, I want to try to explain how BSD works in a way that Linux people can absorb."
One Word: POSIX
Okay, really that's four words.
What do you think? Linux users don't know BSD?
Why won't I use BSD? Because I believe in the GPL, not the Berkeley license, that's why.
If a software license was like the government:
1. BSD would be anarchy. You can do whatever you want with whatever you want, whenever you want to. Murder your own mother? Nobody cares, you're free to do so! It's anarchy baby!
2. Most of Microsoft's traditional licenses would be rampant fascism. We control everything, we are accountable for nothing, and we will not stop until there is nothing left. Hitler would be proud.
3. Just about any license agreement from any small company would be the equivalent to an Iraqi or Italian dictatorship (think Musolini, absolutely pathetic compared to Hitler, but still a complete control freak).
4. Shared source would be communism (you have the illusion of freedom, but really, we the collective control everything and you have no say even though we say you have say even though you don't but you do).
5 And finally, the GPL would be democracy. Democracies are hardly ideal, they are slow, they waste a lot of energy, they infight a lot, but in the end there is NOTHING better.
It's as simple as that.
Bryan
I jumped from RH62 to OpenBSD3.3 some time ago. I have to admit that I've applied a lot fewer patches, security is much better, and the firewall is very powerful. In all, I'm happier.
However, I don't like:
And let's not even get started on Mac OS X.
I'd like to shoot you in the face along with most of the other slashdot commys.
I am guessing you probably meant comm{y,ies}
Free XBox, PS2
Dictionary is your friend:
Joke, n. L. jocus. Cf Jeopardy, Jocular, Juggler.
- In joke, in jest; sportively; not meant seriously.
As you mentioned, Microsoft uses this code, too. The difference is that the motivation behind Microsoft's additions is based upon power and greed in a feverish attempt to maintain their monopoly.
If you work on BSD code, you could possibly be a contributor to OS X. Certainly there is a sense of pride in this.
However, as in Microsoft's case, your contributions can also be twisted in dark and selfish ways without your knowledge or control. In this case, one is not proud, but deeply saddened by the misappropriation of which you spoke.
...or divide and conquer. It's very strange that people seem to need to lash out so violently. From what I've read of the article (pages 1 and 2, since the rest is lost to slashdotting) the article seems to be relatively non-inflammatory.
Of course, this means we need to start attacking him for DARING to even SUGGEST that, yes there are things about BSD that Linux people could stand to understand. I'm personally a contended Gentoo Linux user, and I disagree with the idea in BSD of writing code that anyone can simply use without giving something back. Heck, I wouldn't work for Microsoft for money, I sure as heck won't do it for free! But that sort of brings up the issue that, for the most part, Linux people tend to care more about the political/ethical issues of code that BSDers, who seem to be more down-to-earth realists. Gross generalization - perhaps. Again, just my impression, just as the article is merely the author's impression.
So divide and conquer. Get the free unices to squabble amongst themselves as much as possible, and it's harder for them to threaten more entrenched OSes. Or at least, it seems that way to me. What I'm trying to say is: while the differences between BSD and Linux (and, indeed, between the different BSDs and linux distros) are what make us so strong (nobody likes monoculture), this excessive fighting really is useless. Moreover, I think the people who get all radical about these things tend to hurt the cause more (in terms of broad adoption) than helping. If you feel like preaching to convince people to try your OS - don't. The straightforward, YMMV, choose-what's-best-for-you explanation has helped me convince many people to try free software alternatives. A drop of honey catches more flies than a bucket of gall...
Some do, some don't. Get over it. Personally, I'd like to see more articles of this type. And maybe some more reconciliation between the free unices.
But then, if we didn't have flame wars, I guess it wouldn't be slashdot, eh?
One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.
FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes *BSD is dead.
Fact: *BSD is dying
i'll bite.
:
separate your content and presentation. always.
from http://www.w3.org/MarkUp
(in reference to color, font, margins, etc)
HTML is not designed to be used to control these aspects of document layout.
also, css can be used to easily make pages accessible to those with disabilities. also from http://www.w3.org/MarkUp:
The Web is a tremendously useful tool for the visually impaired or blind user, but bear in mind that these users rely on speech synthesizers or Braille readers to render the text. Sloppy mark-up, or mark-up which doesn't have the layout defined in a separate style sheet, is hard for such software to deal with. Wherever possible, use a style sheet for the presentational aspects of your pages, using HTML purely for structural mark-up.
basically, html wasn't designed to be carry information for both presentation and content -- it was designed for content only. css was designed for presentation.
-mike.
Actually, he's right. Every page should use CSS, and every browser should support it.
HTML 1.0 is worthless.
The "ports" collection of FreeBSD is merely a collection of source packages for easily compilation. Thousands of packages are available in the ports system.
The vast majority of Linux applications just compile on a BSD system. However, most "open source" and "free software" applications are written and have most of their testing done on Linux/x86. As a result, some x86 Linux-specific code gets in. Some example include: big-endianness (ppc and sparc processors are little-endian); the locations of certain include files; libraries required to link in certain functions; directory structure; structure of system init scripts.
autoconf can help solve many of these problems, but not everyone uses autoconf properly.
Very often, the amount of work required to fix a package isn't very great, though it varies. The ports system just keeps the patches required to make a package work properly.
OpenBSD also has a ports system, IIRC. NetBSD has a similar system, though it's called "pkgsrc".
...to be so clueless.
The Ports System
Then, there's the second category; those programs which are add-on packages. In the BSD world, this is usually called the "ports system". That name is chosen for a specific reason.
Traditionally, when you wanted to run a package on your system, the first thing you had to do was compile it. And often before you could compile it, you'd have to fiddle with it. Your system would require different header files. Sometimes, manifest constants would be different. Sometimes, you'd even need to rewrite parts of it from scratch, because of basic assumption that didn't hold on your system.
Or, in other words, you'd have to "port" it to your OS, and/or to your specific system. The basic intent of the ports system is to do all that "porting" stuff for you. That it also automates building and installing, and provides packaging services (for things like 'uninstall') isn't as well reflected in the name.
But as with many things, it grew past its name into the beast it is today. The current FreeBSD ports collection has close to 10,000 packages in it (this number will, of course, be outdated quickly, but that's the nature of development). The most obvious feature of ports is that it builds things from source all the time, rather than just install pre-built binaries. This, it seems, is another one of those blatant differences that trip people up when trying to look at BSD from a Linux perspective. That it builds from source is just a side effect, it's not the primary purpose or difference. Binary packages are also available; in fact, binary packages are built from the ports tree!
Now, it's true that most Linux users install binary packages, and most BSD users install by building from source. Partly, that's a result of the tools; the ports system is designed around the concept of building from source, with the ability to make and install binary packages being something of an afterthought, while Linux packaging like RPM and dpkg and such are designed around the concept of installing a binary package, with building from source as an afterthought. Some of this is historical; binary packaging historically isn't a predominant theme in Unix systems, as I mentioned earlier. For that matter, packaging itself is a more recent thing. Traditionally, you'd deal with uninstalling and such manually.
Gentoo is a Linux distribution gaining in prominence these days. One of its big selling points is its portage system, which is often considered very similar to BSD ports. Perhaps most visibly, in that it compiles from source. That avoids a lot of the problem of binary packages. I've never used it myself, but the impressions I've gotten from information I've seen on it, and people I know who have used it, is that it's taken some good ideas from everyone, and smooshed them together. It'll be very interesting to see how it progresses and matures over the next few years. It's still much more Linux than BSD, but it may well be the closest to the BSD style of the major Linux distributions.
Now, there are advantages to pre-compiled binaries; mostly time (as in much less), and usually it'll take a lot less space to install a pre-compiled package, than it would to compile the package. There are also advantages to building from source, like avoiding all sorts of library versioning ugliness (my personal pet peeve with binary packages). You can install binary packages on Linux or BSD; you can build from source on Linux or BSD. But the users seem to be biased differently, because the systems are biased differently, because the users are biased differently... it all dovetails.
I guess what's important here is to realize that the difference between ports and RPM's isn't just that ports compile and RPM's just install. Ports are designed to cover the full range of bits and pieces of installing stuff; encoding and tracking and installing dependencies, packaging, installing and deinstalling, local changes necessary to build on your system, compile-time configuration tweaks... all those things. An RP
#include "sig.h"
The Ports System
Then, there's the second category; those programs which are add-on packages. In the BSD world, this is usually called the "ports system". That name is chosen for a specific reason.
Traditionally, when you wanted to run a package on your system, the first thing you had to do was compile it. And often before you could compile it, you'd have to fiddle with it. Your system would require different header files. Sometimes, manifest constants would be different. Sometimes, you'd even need to rewrite parts of it from scratch, because of basic assumption that didn't hold on your system.
Or, in other words, you'd have to "port" it to your OS, and/or to your specific system. The basic intent of the ports system is to do all that "porting" stuff for you. That it also automates building and installing, and provides packaging services (for things like 'uninstall') isn't as well reflected in the name.
But as with many things, it grew past its name into the beast it is today. The current FreeBSD ports collection has close to 10,000 packages in it (this number will, of course, be outdated quickly, but that's the nature of development). The most obvious feature of ports is that it builds things from source all the time, rather than just install pre-build binaries. This, it seems, is another one of those blatant differences that trip people up when trying to look at BSD from a Linux perspective. That it builds from source is just a side effect, it's not the primary purpose or difference. Binary packages are also available; in fact, binary packages are built from the ports tree!
Now, it's true that most Linux users install binary packages, and most BSD users install by building from source. Partly, that's a result of the tools; the ports system is designed around the concept of building from source, with the ability to make and install binary packages being something of an afterthought, while Linux packaging like RPM and dpkg and such are designed around the concept of installing a binary package, with building from source as an afterthought. Some of this is historical; binary packaging historically isn't a predominant theme in Unix systems, as I mentioned earlier. For that matter, packaging itself is a more recent thing. Traditionally, you'd deal with uninstalling and such manually.
Now, there are advantages to pre-compiled binaries; mostly time (as in much less), and usually it'll take a lot less space to install a pre-compiled package, than it would to compile the package. There's also advantages to building from source, like avoiding all sorts of library versioning ugliness (my personal pet peeve with binary packages). You can install binary packages on Linux or BSD; you can build from source on Linux or BSD. But the users seem to be biased differently, because the systems are biased differently, because the users are biased differently... it all dovetails.
I guess what's important here is to realize that the difference between ports and RPM's isn't just that ports compile and RPM's just install. Ports are designed to cover the full range of bits and pieces of installing stuff; encoding and tracking and installing dependancies, packaging, installing and deinstalling, local changes necessary to build on your system, compile-time configuration tweaks... all those things. An RPM is just a binary package. If you want to auto-install dependancies, you have to have a higher-level tool like urpmi or apt-get to do it. And, since it's binary, you have to deal with library versioning conflicts, or missing compile options, or any of the other limitations you incur by not building it on your own system.
And further, ports, like the rest of the BSD systems, are centralized. The "ports tree" is really just a big directory tree with a bunch of categorized directories, each containing a Makefile with some variable definitions, a checksum file, a packing list, and various other possible things. Each of those directories represents a single program, which is described by th
Did you know that "FTW" ("for the win") is a direct translation of "Sieg Heil"?
The main thing I liked about it was that, IMO, the author took a completly non-antagonistic stance, unlike some other pro-*BSD stuff I've seen & read. Some previous posters her on /. seem to have the oposite opinion, but I really liked how he approached the discussion, saying that for him FreeBSD is the best choice, but that everyone is free to make their own decision.
Unfortunatly, a lot of the pro-*BSD stuff I've seen & read is entirely different, bashing on Linux almost exactly like Linux users bash on M$ (only Linux doesn't deserve it IMO). At least for me, this is the reason that "the BSD communit{y,ies}, in general, understand Linux far better than the Linux communit{y,ies} understand BSD." Because of the extremely antagonistic pro-*BSD stuff, I have little or no inclination to learn about *BSD. I'm glad this rant shows a better image of the *BSD communit{y,ies}.
Join moola.com, play games to earn money.
The first page stated that BSD is for those who like Unix and Linux is for those that hate microsoft, and that last statment is not going to win support for Linux.
Take the Wikipedia asking for donations last week, half the posts here at slashdot were, "Why don't they go salvage a few old PIII 600's and cluster them together. Should only cost about two grand". Hell, an worthwhile opensource project needs some help paying the bills and they get ripped apart here. Sorry geeks, but Econ 101: There is no free lunch. It costs someone something somewhere. (Yes I did donate $25. Not much, but all that I could afford at the moment.)
I do use Linux, but mostly I do use some kind of BSD, whether it be Mac OS X, OpenBSD, or FreeBSD.
I see the people trying to either be funny or karma whoring state: Well if he can show me a freeBSD server that can survive a /.ing...and I have to ask, "How many sites are taken down a week by slashdotting running Linux?" Hell I know our little 2.Ghz Xeon box with 1GB of Ram wouldn't survive no matter what OS we had on there, it is Linux btw.
Bottom line...the negativity needs to go out of OSS. Linux cannot have the banner, "Microsoft Sucks! and use us because...Microsoft Sucks!" and hope to really make it into the desktop arena. OSS and Linux needs a banner of, "Hey our system works, has fewer viruses, easy to use, and it will do any thing Windows will do, except play games."
And to the "any thing you can do, I can do for free" dot communist crowd: In order to make Linux viable, its going to need programs written for it like games, quickbooks, quicken, adobe products, that people are willing to spend money on and need before it will truely be accepted main stream.
"The problem with socialism is eventually you run out of other people's money" - Thatcher.
I'd like to see a relatively impartial comparison of the relative strengths and weaknesses of Linux and the various BSDs. I hear, for example, that FreeBSD has a more efficient TCP stack than Linux, and you can therefore get better performance with Apache under FreeBSD than under Linux. I have noticed that OpenBSD seems to be more responsive to user input under heavy load than Linux, but I haven't used OpenBSD enough to know if that subjective impression actually bears out consistently.
Dealing with these questions would be far more useful than taking saying
foreach("Amiga", "Mac", "OS/2", "*BSD", "WinXP") {
print "$_ is better than your OS.\n";
}
which is my impression of where these screeds come from.
Proud member of the Weirdo-American community.
How about NotePad for TextPad users? Same analogy.
$parent =~ s/{y,ies}/[y|ies]/g;
If you have to explain why something is useful to someone then you are probably targeting the wrong audience.
Happy Linux, Mac, Windows, etc. Users don't need to be told why BSD will make them happier. Frankly an author has to take a wild guess what bugs me about my Linux and Windows machine. They might get it formated like this but a general "What does BSD do well" FAQ is better. Mr Fuller might not know that some of the things he thinks are wrong in Linux I've hacked around or are in the end non-issues.
Free software is about enabling people. Linux and BSD and whatever can and should all exist because neither is "right". A Linux user can learn how to use BSD. A BSD can learn how to use Linux. How come? Its because both are open systems. The implication with "helpful documents" like this is that there is a right or wrong choice to be made which I believe is an idea rooted in bad faith.
I see any efforts and -contributions I end up making to [BSD] as a waste, since there's no one stopping M$ from apropriating my efforts.
So you're more concerned with hurting Microsoft than you are with helping anyone? That's a rather sad philosophy to have.
...how long does it take a BSD guy to turn a dynamic page (.php) into a static page once you've been slashdotted?
Oh wow, my above Anonymous Coward post makes it look like "Linux applications" are different from "free software" and "open source" applications, which is misleading. Most Linux applications are "free software" or "open source", and most "free software"/"open source" applications are Linux applications.
(There are some Linux applications which are binary only (think Adobe Acrobat), or have source available, but are licensed under a non-free/open source license (like djb's qmail). There are also some free/open source programs primarily for Windows or MacOSX).
> separate your content and presentation. always.
Well, I guess there is the difference in viewpoint. I mant my site to be taken as a whole. There is no difference between content and presentation, each page is an individual entity - a work of art, if you will. Even if some info (common links, logos, etc) is common between them, they are separate. This distinction is completely lost when you go to formats such as slashdot, where the information has to be presented dynamically (or else it would take weeks for a post to go up).
Basically, I still think the guy's a tool, because as SunBug pointed out, it is not for every site. The dude said that EVERY page should use CSS. I don't want my online man files, usenet stuff, whatever to be CSSed. It's overkill, and can cause problems with older, admittedly obsolete, browsers.
Yeah, CSS is great for a lot (probably most) of applications, but not all.
I'd be interested in such a project. Post more info on how we can contribute in future FPs.
Gracias.
So right at the top of the page I'm taunted with a message that "This page uses CSS for all styling, like every page should. Your browser doesn't support CSS, so this page will look pretty bland, but you'll still be able to read every word. Tough cookies."
Except that I'm running Galeon. Which supports CSS just fine.
So why should I listen to this guy?
(/.ed now anyway, so I only saw the first page.)
Tom Swiss | the infamous tms | my blog
You cannot wash away blood with blood
Most Open Source/FSF/GPL software is built for Linux
not quite, have u read where does the TCP/IP stack of linux comes from??? a lot of OSS/FS is built for any Unix, so they run smoothly on any, even Richard Stallman considers that all GNU software/GNUOS can run on a different kernel than linux, and it does.. when you have the basic OS copilant with others (BSD, Linux, HURD) porting becomes quite easy.
I switched to FreeBSD just a couple of months ago, I got pretty much everything running smoothly on BSD as it was on Linux b4, I even still have my home directory (linux partition) working, and the nice thing was that I could read/write on to it on BSD, while I can't do on Linux. I'm a big Linux fan, I've used it already for some years, and become a Linux zealot in these years, but when I try FreeBSD I found it to be a great OS, where I can do everything (and some more) I used to on Linux, and some things were incredible easier on FreeBSD, like burncd as opposed to cdrecord.
There are something I don't quite know yet because I haven't get a chance to work on, like personalizing correctly the kernel, and I think it would be nice if BSD could have something like make menuconfig on Linux. But as far as it goes, I think that linux users don't know about BSD just because they haven't use it, but a big part of the BSD comunity try linux sometime before or after using BSD
I was wondering....can we have a celebrity deathmatch between Linus Tovalds and Theo de Raad?
And who would win?
I do have a couple of promotional logos in mind though....
Cafeshops
Cafeshops, but check around you for [boss|superior|wife|kids]
Aw, hell, my carma's in the gutter anyway....
Then, there's the second category; those programs which are add-on packages. In the BSD world, this is usually called the "ports system". That name is chosen for a specific reason.
Traditionally, when you wanted to run a package on your system, the first thing you had to do was compile it. And often before you could compile it, you'd have to fiddle with it. Your system would require different header files. Sometimes, manifest constants would be different. Sometimes, you'd even need to rewrite parts of it from scratch, because of basic assumption that didn't hold on your system.
Or, in other words, you'd have to "port" it to your OS, and/or to your specific system. The basic intent of the ports system is to do all that "porting" stuff for you. That it also automates building and installing, and provides packaging services (for things like 'uninstall') isn't as well reflected in the name.
But as with many things, it grew past its name into the beast it is today. The current FreeBSD ports collection has close to 10,000 packages in it (this number will, of course, be outdated quickly, but that's the nature of development). The most obvious feature of ports is that it builds things from source all the time, rather than just install pre-built binaries. This, it seems, is another one of those blatant differences that trip people up when trying to look at BSD from a Linux perspective. That it builds from source is just a side effect, it's not the primary purpose or difference. Binary packages are also available; in fact, binary packages are built from the ports tree!
Now, it's true that most Linux users install binary packages, and most BSD users install by building from source. Partly, that's a result of the tools; the ports system is designed around the concept of building from source, with the ability to make and install binary packages being something of an afterthought, while Linux packaging like RPM and dpkg and such are designed around the concept of installing a binary package, with building from source as an afterthought. Some of this is historical; binary packaging historically isn't a predominant theme in Unix systems, as I mentioned earlier. For that matter, packaging itself is a more recent thing. Traditionally, you'd deal with uninstalling and such manually.
Gentoo is a Linux distribution gaining in prominence these days. One of its big selling points is its portage system, which is often considered very similar to BSD ports. Perhaps most visibly, in that it compiles from source. That avoids a lot of the problem of binary packages. I've never used it myself, but the impressions I've gotten from information I've seen on it, and people I know who have used it, is that it's taken some good ideas from everyone, and smooshed them together. It'll be very interesting to see how it progresses and matures over the next few years. It's still much more Linux than BSD, but it may well be the closest to the BSD style of the major Linux distributions.
Now, there are advantages to pre-compiled binaries; mostly time (as in much less), and usually it'll take a lot less space to install a pre-compiled package, than it would to compile the package. There are also advantages to building from source, like avoiding all sorts of library versioning ugliness (my personal pet peeve with binary packages). You can install binary packages on Linux or BSD; you can build from source on Linux or BSD. But the users seem to be biased differently, because the systems are biased differently, because the users are biased differently... it all dovetails.
I guess what's important here is to realize that the difference between ports and RPM's isn't just that ports compile and RPM's just install. Ports are designed to cover the full range of bits and pieces of installing stuff; encoding and tracking and installing depe
just get along?
I tried FreeBSD once, it seemed okay. I agree that the BSDs are probably a better, more reliable operating system than Linux. However, Linux was SO much better than Windows, that any improvements BSD could make seem minimal at best, especially since most of the server and end-user software is identical.
For example, someone once told me that BSD is much more stable than Linux. Assume that's true for a minute: I've NEVER had a Linux system crash, except for hardware failures, and I've been using Linux since 1998 or so. Okay, so maybe BSD is more stable than Linux, but the time spent learning BSD isn't worth the "extra" uptime I'd have, since the extra uptime is approximately zero.
As I mentioned, the end-user software is mostly the same, but I've heard Linux has more variety and more hardware support. My printer is supported under Linux (it's an HP USB printer), but I don't know whether HP is putting resources into BSD support. Same goes for my Palm Pilot. Since everything is working now, and I'm happy with how well everything works, why should I want to switch to BSD?
And why can't we have our own preferences anyway? Why do BSD users have to bash Linux and vice versa? The two are a lot more alike than different, at least compared to Linux vs Windows or BSD vs Windows. (It's almost like brothers fighting...)
--RJ "Firmly sitting on the fence"
"Because there's nothing on Linux that most Windows users think they need or want, yet how many people are standing on street corners praising Linux and all it's glory over Windows? More software is written for Windows, and there's alot more support available."
You're overlooking philosophical differences between Window and linux. Which is a lot more different the the philosophical differences between BSD and Linux.
Also momentum. Windows is loosing places to look for new users, Linux is still gaining them. Mean while BSD seems to be just kind of gliding along.
Could just be my impression, however I can't think of the last time I saw BSD mentioned in any trad mag. for any industry as an alternative to windows.
I want to make something perfectly clear:
This post is in no way anti BSD. I haven't used BSD in years.
The Kruger Dunning explains most post on
fsck {y,ies}ou all!
"Hardly used" will not fetch you a better price for your brain.
To make it short:
- Linux users don't know BSD because they don't need to know BSD, BSD having nothing that can interest them (how do they know?)
- BSD users know Linux because they absolutely need it to make something out of their systems, unusable without the software built for Linux
That said by somebody confessing he knows nothing about BSDFunny...
He's concerned with not helping Microsoft. I don't see how that's got anything to do with hurting Microsoft.
... then maybe applications wouldn't crash on it quite as often as they do.
General
Ah, now this is the part I enjoy. Lots of soaring generalities, without a single hard fact in sight. Saves the trouble of having to do research. 8-)
What I'm going to discuss here is some of the real and imagined philosophical differences that both cause, and are caused by, some of the technical and organizational differences we've discussed. Like most such discussions, there's little that's hard-and-fast here; there's plenty of overlap in attitudes among people in the various camps. And there's certainly plenty of completely deserved flak for both sides to take, as well as undeserved flak they've been forced to. Still, I think it's important to examine some of these splits, without trying to presume that one is "correct" and the other is "incorrect".
Realize, I must emphasize, that a lot of this is very general. Practically every point is riddled with exceptions. And both systems often don't "follow the rules", or fail to meet their own expectations. It's more a question of inclination that of exceptionless implementation. I'm just saying this now, so I don't have to keep qualifying and re-qualifying every statement I make, until it's impossible to read.
Chaos vs Order
One common generality is that the Linux methodology is the living incarnation of chaos, whereas the BSD methodology is far more about control. To a large extent, it's true. Linux grew out of a spare-time hacking background, while BSD grew out of a controlled engineering background. Of course, there's plenty of weekend tinkers writing BSD code, and plenty of full-time professional programmers sloughing away at various parts of Linux. But the feel of the systems still does reflect that sort of schism.
We've already discussed the construction methodology; BSD builds up a core system which is uniform, whereas Linux distributions takes pre-existing pieces and pretty much puts them together helter-skelter. Naturally, the BSD method is far more amenable to keeping things ordered, while the Linux method practically necessitates utter chaos. That's not to say that chaos is inherently bad, or order inherently good. They're just different environments.
Linux will also generally chase new versions of other programs much more closely, adopting particularly more major changes like Apache 2 much sooner than BSD will move that way. Now, the stricter separation of "base" vs "ports" in BSD, as well as the structure of the ports tree itself, make it easier to have multiple parallel versions of packages in BSD. Sometimes, it's even possible and easy to have multiple versions installed at the same time. Linux, by not having that sort of separation, makes it very difficult to have parallel versions, and instead almost requires a single "blessed" one.
And the primacy of source-compiling in packages also makes it easier to handle multiple versions. For instance, PHP must be compiled differently depending on whether you're using Apache 1.3 or Apache 2. With from-source packages like ports, I can define an environmental variable when I compile and install PHP to tell it whether to use Apache 1.3 or Apache 2. With binary packages, you'd have to have 2 separate packages available, which will lead to confusion sooner or later.
Right vs Wrong
The difference can also be seen in the way core code is integrated. BSD tends to always shy away from hackish solutions when there's even a hint of a proper solution in the wings. The theory is that it's far easier to wait for the clean answer, than to integrate the dirty answer now, for several reasons. For one thing, if you integrate the dirty answer, that reduces the incentive to implement a better one. For another, once you dirty up the architecture to integrate something it'll never get cleaned up again. You know it as well as I do. Oh, sure, you'll say it's temporary. But you know
BSD is for those that love Unix. Linux is for those that hate Windows.
:-).
Only a total moron would love Unix at times like this. Ever heard of this company called SCO?
Unix is dead, long live Posix!
And BTW, I used to play w/ various BSD's in the past. However, I would be hard pressed to try any of them again, I just don't like the people in the BSD community (well, NetBSD might be an exception, don't know about DragonFlyBSD...). I can't imagine myself being among them, badmouthing Linux at any given opportunity (especially as *BSD benefits immensely from success of Linux, which BSD people don't seem to realize).
Getting a "thumbs up" from Microsoft (which BSD community does, because MSFT can rip them off any time they want) doesn't help either. Enemy of my enemy is my friend, and apparently BSD is not an enemy of MSFT
Save your wrists today - switch to Dvorak
Below is from the SFU licenses you get with SFU 3.5
The utilities bc, ci, co, cpio, csplit, dc, diff, diff3, gawk, gzip, gunzip, ident, merge, nl, rcs, rcsdiff, rcsmerge and rlog are covered under the GNU General Public License, here reproduced. In accordance with section 3b of this license the source code to those utilities is available from the Services for UNIX World Wide Web site, http://www.microsoft.com/windows/sfu.
Help fight continental drift.
I see a lot of folks in both camps that use both, because both have their strengths and weaknesses.
The folks that will choose one or the other and be biased about it are either:
1) BSD folks that tried out linux in 1994, and still have the impression stuck in their mind. They seem to think that linux hasn't changed at all since then.
2) Linux folks that at some point of their complete n00bness went into a BSD channel in efnet and asked some lame question like "since linux is unix, where can i get the FreeBSD RPMS?" and got flamed so hard that they had to crawl out of a hole in the ground. Therefore, they think that BSD users are all crusty assholes that cling to a "little used" OS that is fading into obscurity like people that try to ride out hurricanes. Hence all the "BSD is dying" bullshit.
And it's really sad. Both have their merits. Both share many of the same goals. I wish they could get along and do great things together.
My $0.02USD + tax.
do() || do_not();
JavaScruft but not CSS? CSS = "simple flash"??? Wow, you are one seriously cl00less n00b.
I thought nobody cared about those... I know I don't ;)
General
There're all sorts of myths and objections and "common knowledge" and "conventional wisdom" and such floating around about BSD. I'm always a little surprised at how quick some Linux people are to latch onto such over-simplifications and long-dead statements about the BSDs, especially since they then spend so much effort screaming about people doing the same thing concerning Linux. Oh well. Let's rip up a few.
Hardware
"BSD doesn't support common hardware."
Does Linux support hardware that BSD doesn't? Probably. Does it matter? Only if you have that hardware.
I'll betcha Windows supports hardware Linux doesn't. For that matter, MacOS probably supports hardware that none of the rest do. BSD supports most common hardware you'd stick in a server, most common hardware you'd stick in a workstation, most common hardware you'd stick in a desktop... There are gaps, but the gaps change from release to release, just like every other system.
Video card support, for instance, is hardly ever claimed in any BSD documentation, while Linux documentation talks about it a lot. That seems weird, until you realize that in the BSD worldview, the OS isn't supporting any of those video cards; X is, which is a separate package. So you can use any video card under BSD that you can under Linux, since neither the BSD kernel nor the Linux kernel is supporting the video card. Now, that's not strictly true, particularly in some of the more esoteric reaches of 3D and DRI, which require more direct hardware ties and more grubbing in the kernel itself. Of course, I don't follow that, so I don't even know what the current state of the world is in FreeBSD, to say nothing of Linux. Maybe BSD doesn't have support on a par with Linux on that. Maybe it does. I dunno, and it'll probably change between the time I write this and the time you read it.
But most hardware is simple. Most common IDE and SCSI mass storage controllers work just fine. Even most RAID controllers are supported to some extent. Most network cards, wired and wireless, most sound cards, some crypto-assist cards...
But it is simple. You don't care what hardware the OS supports, as long as it supports what you have. Read the hardware support lists and/or just try booting it up. You might be surprised.
When in doubt, check the lists. Hardware support lists are available per-release, such as the lists for 5.2-RELEASE and for 4.9-RELEASE of FreeBSD.
Program Availability
"But Linux has more programs than BSD!"
How do you figure? Most of these "programs" you're so hot about are things that are open source or source-available anyway. If it's written reasonably portably, 95% or better of it will compile right off on any vaguely POSIX-compliant system. Heck, just look in the ports tree; there are over 10,000 programs and packages there.
Of course, there's a lot of software out there that won't compile on anything but Linux. Sometimes, that's because it really does require facilities that only Linux has, or does things that only matter on Linux. Sometimes, that means you need to pick up a 2x4 and go find the author, because they've put in something gratuitously imcompatible through malice or laziness. There are people who do the same with BSD, or with HP/UX, of course, but the rapidly growing Linux community, combined with the number of people writing programs who have with less experience in traditional software engineering, make it far more visible there.
Of course, there are some things that won't cross-build, particularly those that stick their fingers deep in implementation details. Some require only a little work to port, some major work, and some don't even have any meaning on other systems (When did anybody ever port Mic
I think this is a great example of mis use of dynamic web pages to store static data.
Ike
Most Linux users don't bother with BSD because of the license. At any time a corporation can come along, take the code, and use it in their closed source product. With the GPL the Microsofts of this world have a harder time stealing the code and reinforcing their monopoly.
If I worked at a large software corporation and was hellbent on shoring up my monopoly at least cost I would thank the lord that there are fools enough releasing software under the BSD license and prey that Linux and the GPL would just go away.
I don't mind contributing to Linux and GPL'd software for free but doing the same with BSD or closed source software is lunacy.
Release BSD under the GPL and I'll try it out, otherwise, forget it.
It's not technical. It's political.
Forbidden /~fullermd/rants/bsd4linux/bsd4linux1.php on this server.
:)
You don't have permission to access
Apache/1.3.27 Server at www.over-yonder.net Port 80
Ok, as a Linux user, I really understand why I should _not_ use BSD after reading this
{{.sig}}
And the problem with that is ... what? Here we have an MS implementation of OpenBSD .. that is compatible with OpenBSD. As opposed to an MS implementation of POSIX that wouldn't really be compatible with POSIX and cause all kinds of interoperability problems for everyone.
... or everybody using the same, tried, tested, and known-to-work implementation??
Which would you rather see: every proprietary software company making their own implementations of everything
The BSD license allows for this, and is why all low-level architectural-type stuff should be released under a BSD-type license. The GPL does not allow for this, and forces everybody to continuously rebuild every wheel, with who knows what kinds of bugs lurking underneath to bite us down the road.
But, the GPL is a good license for high-level applications, things you don't want other software companies to take, wrap under a different name, and sell as their own.
I read this article the other day and it is very enlightening actually. Pretty much his reason to use FreeBSD is the coherent, tightly integrated, and heavily tested base system. *it just works* Of course that is all a matter of preference. I run Linux because I value high configurability, choice, and bleeding edge software else I would be running *BSD. Of course I am running Gentoo, whose package management is based on *BSD ports, the other major plus for BSD.
Also momentum. Windows is loosing places to look for new users, Linux is still gaining them. Mean while BSD seems to be just kind of gliding along.
Don't worry, I'm sure they'll fix it by writting helpful documents to explain BSD in a way Windows users can understand.
*snort*
Check this article out!
/etc/format.dat file.
/etc/format.dat file, matching the geometry..." Uh-huh. After years of development and millions of dollars, Solaris still can't figure out how to label a disk drive. Give me, as they say, a break.
Title: Why I run FreeBSD - SunOS, Solaris, Linux? No, thanks!
Why I run FreeBSD
SunOS, Solaris, Linux? No, thanks!
Abstract
Rich explains why FreeBSD is the superior OS for him. (1,500 words)
Last month's column ("Serious FTP") discussed anindustrial-strength FTP site, based on a 200-MHz P6 ("Pentium Pro") and a pile of special-purpose
I/O hardware. Although my main server isn't trying to serve thousands of simultaneous FTP sessions, I still want it to be robust, easy to maintain, and convenient to enhance.
So, like Walnut Creek CDROM, I use FreeBSD. Specifically, I'm using FreeBSD 2.2.8; I'll switch over to FreeBSD 3.x in a while; for now, I'm just lurking on comp.unix.bsd.freebsd.*, watching the new development track's bug reports quiet down.
It's not that I haven't tried Sun's offerings; I have. In fact, I have both SunOS and Solaris running here, as well as a Power Mac (supporting the www.mklinux.org Web site).
However unwillingly, I have been initiated into the administrivia of a variety of Unixish systems. And, for a variety of reasons, I believe that FreeBSD is a clear winner over the others I have installed.
Why SunOS and Solaris lose I tried hard to retain the SunOS machine as my server. SunOS is a tidy (by current standards, at least) little BSDish operating system. Also, I am very familiar with its BSDish quirks, and it has been amazingly reliable, so I was strongly motivated to keep it going.
Unfortunately, SunOS has had no real support from Sun for several years. As a result, the system software is quite out of date. It has gaping security holes (e.g., ancient sendmail), annoying limitations (a "mere" 2 GB per filesystem), archaic development tools (no C++ or Perl), and some real oddities (no DNS without (yurggh!) NIS).
Patches and add-on packages could solve much of this, but there is no guarantee that they'll all play nicely together. In any case, I'm not into that degree of pain, so the SunOS box has been relegated to "experimental" use.
I have managed to avoid Solaris for several years, but I recently had reason to set up a Solaris system. I attached a CD-ROM drive and a pair of disk drives to the SCSI bus of a spare ELC and fired it up.
Everything went fine until Solaris looked at the disks. Then, because the disks didn't have Sun labels (well, duh!), the GUI installation procedure printed a nastygram and dropped me in front of a command-line prompt.
If this was a SunOS system, I would have known exactly what to do at that point: find a utility to get the exact size of the disks, fake up a plausible disk geometry to match the size(s), and edit the mess into the
You see, SunOS inherited the 4.2 BSD filesystem, which tries to employ disk geometry as a way to reduce head movement and rotational latency. Modern SCSI disks don't have fixed track sizes, however, so some parameter faking is required.
This, however, is Solaris 7, Sun's latest and greatest operating system. There must be a magic command to set things up on an "alien" disk drive. The fact that the GUI didn't call the appropriate routine is a bit annoying, but surely just an oversight.
So, I asked a friendly Sun support person for the answer. "Well, you have to find or create an entry in the
I won't even get into the issues of Solaris support tools, save to say that a Unixish system without a C/C++ compiler and Perl 5 isn't up to any standards I'd wish to set.
Why Linux loses (for me)
Part of my problem with Linux is subjective; As a long-term BSD administrator, I am simply more comfortable
Muchas Gracias, Señor Edward Snowden !
So, let me get this straight.
Apple uses BSD code to make a good operating system and its all sunshine and roses. Good for Apple. I commend them for wanting to make their operating system the best they can for their customers.
Microsoft uses BSD code to make their operating system a little better for their customers and they are the solely driven by greed and power in preservation of their "monopoly". I would think Microsoft has as much right to make their products a little better by using code in the same manner that Apple does without it being deemed an evil use of people's hard work.
Plus, *raises change of subject card* despite what everyone says, even the court system. By the mere fact that alternate operating systems exist, are sold, and are installed; Microsoft does not have a monopoly on the Operating System market. They just have a widely-used product.
--being modded down because I can see reality
"Wisdom is not a product of schooling but of the life-long attempt to acquire it." -Albert Einstein
I think with Linux's popularity, people often fail to understand that generally the same desktop environments, utilities, and such work exactly the same on the BSD's. Especially in the case of the ever-so-portable NetBSD, it allows one to have a Linux-like desktop on pretty any platform imaginable that's powerful enough.
Now, commercial/binary application support, and variety of device drivers available are the main areas were the BSD's are still playing catch-up.
Love many, trust a few, do harm to none.
Kinda makes you understand how windows users feel when we complain about windows and talk about how "linux users know more about windows than windows users know about linux". Just sounds like "whine, whine, wish I had real critical mass". Personally, I kind of regret my dalliances in NetBSD and FreeBSD - they took time away from Linux. Now I can't say I ran linux solid from the days of 0.12. And with the way Theo rants, there's a snowball's chance I'm going to try OpenBSD.
Granted, you have to pay them for their effort, but it is commonly agreed that OS X is worth paying for.
[...]
If you work on BSD code, you could possibly be a contributor to OS X. Certainly there is a sense of pride in this.
However, as in Microsoft's case, your contributions can also be twisted in dark and selfish ways without your knowledge or control.
Ok, so apple takes community code, uses it, arguably, for the bulk of their operating system, and then charges $130 per client per version for it. They don't release any changes. Microsoft takes community code and integrates it into an add-on product that they're now giving away. They don't release any changes. But since Steve Jobs is a lovable druggie and Bill Gates is a scary nerd, Microsoft is dark and selfish and Apple is warm and fuzzy. That makes perfect sense!
I don't quite understand this feeling that Apple is any better than microsoft. Both use fairly sleazy business practices, and I wouldn't expect either Steve nor Bill to take their foot off your head to keep you from drowning.
Unlike those generous darlings at apple who used the BSD code and mailed a $1000 check to every every BSD developer, right?
Oh, they didn't do that?
...no really, I did read it. Honest.
Although the writer does have a few good points, he also has some rather large gaps in his knowledge. He really only knows the FreeBSD system, but seems to assume the other BSDs do things exactly the same. Some of his arguments would apply to NetBSD and OpenBSD, but not all of them.
His personal bias really shows through in the writing, almost bordering on making it a flame or troll against Linux, even though he mentions over and over that this is not the intent.
I'd love to see the same article written by someone with less personal bias, and more actual knowledge of Linux and the BSDs.
better than the avg linuxer.
Replace Linux with Windows, and BSD with Linux, and much of the same could be said about the technical Windows crowd.
That said, Unix is Unix, even if it is a Unix-like OS.
I have plenty of machines to run *BSD on, and occasionally I do. The choice to use Linux every day over any of the other Unix/Unix-like operating systems is mostly based on familiarity, though the difference between a Linux-based system and a BSD-bases system is minor if the tools and apps are all there. With Windows, it is a major pain to get things Unix-like working as they do under a Unix/Unix-like system.
That said, for personal use I would not consider a Solaris or HPUX system. They are a pain to use when compared to a half decient Linux ditribution. I would not be in too much pain switching to one of the *BSDs.
A firewall can not protect you from yourself. Turn off what you do not need. Do not use the firewall to do your work.
Linux isn't UNIX
Then using the UNIX API's and the GNU toolset for UNIX makes GNU/Linux exactly what then?
Go ahead, earn your +3 insightful.
On the "advise" (really more like repeated nagging, which seems to be fairly common from BSD enthusiasts) of a friend, I went with OpenBSD when setting up a server a year or two ago. Even after getting over the culture-shock, I ended up not liking it very much. I've gone back to debian, which I'm confident is every bit as secure, and is easier to admin.
/etc. Having to go searching for httpd.conf in /usr/local/etc or maybe /var/www/conf *really* bugs me.
I found the installer to be utterly cryptic, filled with unexplained single letter commands. I should not need a $40 reference book to install the freaking OS. Once it was up and running I was fairly comfortable, except for the propensity to scatter config files/etc around the filesystem. Maybe debian has spoiled me, but I expect to find *all* config files under
Then of course there is their reputation for security. They would have people believe that there has never been a root exploit; in reality, that only actually applies to the "base" system. I do like that the secure by default thing; having to specifically enable services is a good idea(getting the choice while installing is better though).
Am I mistaken, or are you trying to tell this person that there is a linux that does things more like BSD, and therefore this linux is somehow better?
:)
Doesn't this kind of imply things you'd rather not be implying?
Slashdot. It's Not For Common Sense
since there's no one stopping M$ from apropriating my efforts.
And its a good thing you just don't like Microsoft 'misusing' your code. Because, boy, you'd have to be pissed about the Virgin WebPlayer and the GPL violation of the Linux OS there. And, given the LACK of action on the Virgin WebPlayer, I'd have to call you a hyprocrite.
All of the BSDs rely thoroughly on GPL tools for their development, as there are no equivalent tools available under non-copyleft terms.
For details on which GPL'ed tools are part of OpenBSD, for example, see the gnu portion of their cvsweb.
It includes GCC, the binutils (assember, linker and all commands dealing with object files, like nm, ar, etc), the debugger, and many other standard Unix tools such as diff, bc, grep, etc.
BSD developers would not be able to get any work done without GNU.
You are utterly retarded. A *BSD user needs only to know basic UNIX concepts to get stuff running. In fact, to use linux effectivly the same is also true.
"Most Open Source/FSF/GPL software is built for Linux."...And probably runs on *BSD as well. Check http://www.freshports.org for a list of the FreeBSD ports tree.
Let me get this straight:
Apple takes BSD code, incorporates it into a closed source, propretary operating system, and that's good.
Microsoft takes BSD code, incorporates it into a closed source, propretary operating system, and that's bad.
I'm not seeing a huge difference here...
It's official. Most of you are morons.
i saw this article yesterday posted on:
freebsdaddicts.org and the first thought that came to mind was, "boy I hope this doesn't get slashdotted, because the linux crowd will have another BSD flame-fest." its not as bad as i thought it would be. the guy who wrote the article was really not judgemental at all, he made points to say "not saying one is better, they are just different." so cut him some slack..
home of the original cupholder
System Upgrades
Building the world in less than 7 days
As a result of the fact that the BSD base system is developed as a single unit, you can easily get the entire source tree for the entire base system. And because of the way it's designed, you can execute a single command at the top level to compile everything. For most of us, that's the normal way to upgrade; you update your source tree to the absolute latest (with a few hours, of course) changes made by anybody, compile it, install the new binaries, and you're done. Miller time.
Of course, you might not necessarily want the latest. You could grab the sources from last week, say. And normally, you do the whole rebuild process in four steps. You start with a make buildworld which compiles all of userland, then a make buildkernel which compiles the kernel. Then you take a deep breath and make installkernel to install the new kernel, and make installworld to install the new userland. Each step is automated by a target in the Makefile.
Of course, I'm leaving out tons of detail here. Things like describing the kernel config, merging system config files, cleaning up includes... all those gritty details. If you want to read about that, check the FreeBSD handbook, specifically the sections on updating and building and configuring your kernel, or the various other forms of documentation available. But those sort of things become second nature after you do them a few times. Really, the process of updating your system boils down to those four commands. I find it a lot easier than having to resolve cross-dependancies and changed library versions and such across a zillion binary packages.
This information is mostly based on FreeBSD. NetBSD uses a different model for doing the system builds. OpenBSD tends to be much more in favor of reinstalls, at least for major version changes.
Addon software
Well, that sure was easy. But, what about all those add-on packages? How do we manage those? Let's talk about installing and upgrading ports.
microsoft also works perfectly with the rights of the license
bsdl = protects user
gpl = protects developer
vodka, straight up, thank you!
I am growing to dislike Slashdot more and more...
The average intelligence shown in the posts here have gone from good to horrible.
It has become a waste of time.
I guess Slashdot's 15 minutes of fame are up.
I only read the pages posted to /.
Ohhh, how enlighted of you!
licensing differences between BSD and Linux. Both are open source, one is free software.
And that would be FreeBSD.
As with any free software project,
The following licenses do qualify as free software licenses,....The modified BSD license.
As you can see, the FreeBSD project calls itself Free Software and the FSF says that is correct.
So therefore, Linux must not be free software, just Open Source or you are wrong about there being "one is free software."
This is the one thing that I have never quite understood and have always heard people in the BSD camps complain about.
I always hear complaints of how fractured the linux community is because of the umpteen different linux distributions. Now I have used about 5 different linux distributions over the years and I have to say that I have been able to sit down at everyone that I have tried and felt pretty much at home. The base operating system is always made from the same packages. I have yet to see a mainstream distribution that didn't use glibc, util-linux and the like. The only major difference you see between the distributions is the package managment.
On the other hand I currently use both Open and FreeBSD and while mostly similar I would have to say that there was a greater difference in the core OS between them then between different linux distributions. For example the disk partitioning program. Also since they use seperate kernels it can result in other incompatabilities. I know in the past filesystems were not quite compatible, or all features were not supported, such as UFS2 and soft updates.
Also when he talks about the installation from ports being snazy for install because they find dependancies and install them for you I am suprised he doesn't bring up any of the linux tools that do the exact same thing such as apt or emerge. He mentions the distributions that they are a part of so I think he knows about them. It is possible that he thinks that linux users know about them and therefore doesn't have to.
Either you're with us or you're against us!
Exactly. If Microsoft takes a copy of your BSD licensed code, compiles it, presses it onto a CD, drops it into a shiny box (so shiny!) and sells it for $100...
What is stopping anybody else from doing the same thing? What is stopping anybody else from doing the same thing but only charging $90? Or $110 but including a nice manual? Absolutely nothing.
People who use the "Microsoft will use my code in a product" argument against the BSD license forget that the original code will still be available for free. Whatever the marketplace can accept paying for Microsoft's additions to otherwise freely available software then that is what Microsoft's additions are worth, regardless of how insignificant those additions are.
Serve Gonk.
I'm quite happy for anyone to use the code I have released under BSD licenses. I'd love it if Microsoft included a port of OpenSSH with their operating system, just as I am happy that they are releasing some POSIXy tools (mostly based on BSD licensed code).
/bin/sh).
This has already happened - Sun's Solaris 9 SSH is based on portable OpenSSH. I'm happy that Solaris is a little less braindamaged out of the box these days (though I wish they would get a modern
Would I care if Microsoft were to make a few $$$ of my work? Not at all - I have lost nothing by their gain. The original, free code would still be out there for people to improve and every additional line of 3rd-party free code that these proprietary software companies have to track puts them closer to that pain threshold where they decide it is easier to contribute their changes back to the community than maintain their own forked version.
I hereby propose an addition to the HTTP status codes for the 418 Slashdotted response. This response code MAY also automatically request that the clients operator place a temporary mirror online for a 24 hour period.
Back when I started out with linux(less than 5 years ago!) there wasn't any considerable anomosity between linux/bsd. The only change that might have caused this is that linux has become simpler and more graphical in nature, and has increased in popularity. So is it that BSD users are jealous, or is it that more idiots can now work linux? Probably a combination of both judging by the mud being slung by both sides. Maybe the bsd based OSX release has created some tensions for both sides too.
True genius is grasping a situation like a peice of fruit, and peircing it just right so that it drains dry.
The comment at the top, in css class "ahem". Saying that my browser doesn't support css. What actually happened is your server couldn't serve the css page. With pretentions like these are you suprised people don't care about the facts of BSD?
Special Relativity: The person in the other queue thinks yours is moving faster.
I'm so sick and tired of seeing (certain) {geek(s),nerd(s)} speak in (a) way(s) that makes their language look like programming code and makes them look like (a) total neurotic (horse's) {ass(es),cock(s)}.
1. Linux, not BSD is run like an anarchy. The kernel is done by one group, Gnu, the utils, libs and applications are another, they're not even vaguely in sync with one another and like a sloppy carpenter they're leaving it to the plasterers and painters (Distributions) to make it look good.
2. pass (aside from noting a Goodwin)
3. Small companies obviously vary, I've had both extraordinary good luck with some(most) and less good luck with others. That's called a market, caveat emptor. Particularly smaller software firms I've worked with have been extraordinarily good at listenting to customer requirements and actually responding.
4. Shared Source ... ahh now that's an important license type. Didn't want to contrast Public Domain, Artistic, MIT ...?
5. As with (1) you've reversed it. The BSD's in fact operate considerably more slowly than Linux in developement pace, however they do so with far better coordination of the various parts. Kernel, Libc, utilities are released together, and probably benefit from the faact that the whole assemblage is tested.
I have *nothing* against any of these systems, some I use, some I don't. Linux works, BSD works and I'm fluent in the advantages and disadvantages of each and can make educated decisions about which is appropriate to a given task.
You've also demonstrated that you don't understand crap about governments. The world has many flavors of democracies, the Linux, BSD, Gnu, Perl communities are all vibrant forms of demorcracies in action (as, by the way are commercial / proprietary vendor - customer environments.)
It's as simple as that. Let me guess you use Debian? or is it Windows?
Linux is Linux, if One need clarify their dist: <Dist>/GNU Linux
bsds are of course just BSD
Who do you think will win the popularity contest. A cute little penguin or some red weirdo with a stick?
Even my wife likes Linux, because of that penguin. (Tux racer being one of her favorite games.. just because there is that penguin)
Since it isn't very often that there has been 2 BSD posts and 0 linux posts...
:D
This is just proof that Linux is Dying
Good ending to a fine Friday.
The problem with the BSD approach is that it doesn't see copyrights (the right to restrict what people copy) as a restriction on peoples freedoms. It's sorta like saying I believe I should have the freedom to restrict other peoples speech, but if you don't want to restrict other peoples speech - that's OK too. Where the GPL is more like saying, "I'll use my power to restrict your speech when you use your speech to restrict others" In fact, in the information age, we minus well be discussing free speech like this because in the eyes of the internet there is no difference between copyright content and free speech content. You either half to have the power controll all of it or none of it.
...have downloaded file one to three and six:
bsd4linux1.php:
BSD vs Linux
What is this?
I run FreeBSD on my computers. A lot of my friends run Linux, or at least one of the distributions of it. Naturally, then, we agree that a Unix-style operating system is the right choice, but we disagree on which to use.
It's been my impression that the BSD communit{y,ies}, in general, understand Linux far better than the Linux communit{y,ies} understand BSD. I have a few theories on why that is, but that's not really relevant. I think a lot of Linux people get turned off BSD because they don't really understand how and why it's put together. Thus, this rant; as a BSD person, I want to try to explain how BSD works in a way that Linux people can absorb.
While there's overwhelming similarity between the operating systems in most cases, there are also a lot of differences. As you probe more into the differences, you find that they emerge from deep-seated disagreements. Some are disagreements over development methodology, some over deployment and usage, some about what's important, some about who's important, and some about which flavor of ice cream is superior. Just comparing the surface differences doesn't tell you anything; it's the deeper differences that both explain and justify why each group does things the way they do.
What isn't this?
This is not:
* A list of command correspondances; "'netstat -rnfinet' on BSD = 'netstat -rnAinet' on Linux" and such things.
* How to do all the things involved in adminning and running a BSD box.
* Why you should use BSD instead of Linux.
* Why you should use Linux instead of BSD.
* Why you should use this BSD instead of that BSD.
* Why you should use this Linux instead of that Linux.
* Why BSD is Right and Linux is Wrong.
* Why Linux is Right and BSD is Wrong.
* Why I am a god and you should worship me.
I, personally, for me, believe (obviously) that my OS choice is right. That's me. I'm not telling you that you should believe it. Learn the facts, and the origins behind the facts, and make up your own damn mind. That's why you have one.
Some preliminary thoughts
There're a lot of philosophical disparity between the Linux world and the BSD world. And there are a lot of expressions about it out there. One I particularly like goes something like:
BSD is what you get when a bunch of Unix hackers sit down to try to port a Unix system to the PC. Linux is what you get when a bunch of PC hackers sit down and try to write a Unix system for the PC.
Now, I like that quip, not because it's some sort of absolute revealed truth, but because it gives a very good feel for some of the differences. The BSDs, in general, are very much more like traditional Unices than Linux is. A lot of that is because they're direct-line descendants of the BSD from Berkeley, which was a direct-line descendant of the original AT&T Unix. Unix-the-trademark is a trademark of The Open Group, and Unix-the-code is owned by SCO, so one can't actually say that the BSDs are really Unix (that's the sort of statement that triggered the USL/UCB lawsuit extravaganza, in fact). But, in many ways, the BSDs are direct derivatives of traditional Unix.
That shows through in a lot of ways. It shows up in the design of the base system and the packaging of addons. It shows up in the partitioning of the mass storage. It shows up in a lot of details of the commands. And it shows up in the attitudes and reflexes and prejudices of the developers, which are reflected in the code and in the users.
BSD is designed. Linux is grown. Perhaps that's the only succinct way to describe it, and possibly the most correct.
bds4linux2.php:
Who are the characters?
Meet the players
I'll give here a quick introduction to and discussion of the systems I'll be talking about. Note that the histories presented are not comprehensive or authoritative, and no attem
------- In the end there are no begining
Linux is not free as in speech, it's more like forced speech. Free speech involves the freedom to not speak.
Thus, this rant; as a BSD person, I want to try to explain how BSD works in a way that Linux people can absorb.'
The server is feeding back 403s, which seems to make some sort of statement...
May we never see th
Is how they insist that a community can or should behave as a monolith.
Linus, Gates, and Theo have no control over how their software communities behave. Their respective software communities have no control over how they themselves behave.
Yes, I realize my complaint has been voiced before. But all y'all jackasses are hard to drown out. Well. IHBT. IHL. HAND.
There are no trails. There are no trees out here.
The way his server is failing might have more to do with the fact that it's PHP. I don't think php holds up well to a heavy load. Which makes me think it might be able to serve more pages if it was JSP/servlet - which reminds me, isn't there sort of a cloud hanging over Java on BSD? It used to be just not available or available only via Linux emulation, but it's been a long time since I looked into it. Anybody using it?
I don't really get the schism between FreeBSD and Linux. I use both. The servers I have full control over usually get loaded with FreeBSD. The reasons for this are simple; I haven't found a Linux distribution with the ease of system upgrade and general maintenance that FreeBSD has. The ports system isn't perfect but using cvsup to get update patches for the core OS is simply wonderful. Combine this with the reputation for stability and it's a winning combination. A combination that makes me comfortable to upgrade the complete server remotely without worrying too much about the upgrade failing.
Gentoo is somewhat similar but they aren't aiming for ultra stability and they don't have a long term reputation like FreeBSD.
Debian is great for upgrades but the glacier pace of upgrades to the stable release is unacceptable.
Slackware is wonderful (I'm back to using it for my desktop OS) but upgrading the OS isn't as nice as FreeBSD. Third party tools like swaret are slick but not time tested.
I would love to have a tidy distributation of Linux and a small core of tools released in the same way as FreeBSD with a similar "make world" upgrade process.
So you're more concerned with hurting Microsoft than you are with helping anyone? That's a rather sad philosophy to have.
What do you expect? This is Slashdot.
Karma: It's all a bunch of tree-huggin' hippy crap!
BSD folks think they are the only ones to understand linux. Then why don't they use Linux instead of BSD.
As well why is Slashdot so hard up to publish articles on such a stupid topic. We have heard enough from the BSD folks. Lets move on. The facts are Linux is used more than BSD, that speaks for it's self..
Well, I think I can save a line command over BSD: ;)
;) ) don't fight each other when they exchange files, they're even pretty close and I always sleep without fearing a murder during night.
emerge apache
works juste fine
All in all, I think that this article and most of the posts here are pointless and this is only calling for flamewar.
Speaking from experience I can tell that (at least from user point-of-view) one should use whatever he fells comfortable with. I tried the three flavors of BSD I know (namely Free, Net and Open) and about a dozen of Linux distro based on at least 3 packages management system. Now I run Gentoo, not because it's faster/better/whatever but because I feel comfortable with it. If you have the time and resources, please try some and get yourself an idea.
That's fun to see people so closed-minded (although he pretends the contrary (not parent post, article author)), basicaly, he seems to never have run Linux but explains that BSD is better designed because a somewhat stronger relationship with "The True Unix(tm)". Hey, at least, try before ranting!
And on a final note, I think penguins and daemons can live together without any problems. My Gentoo server and my OS X box (YES! OS X is a BSD, I've seen it while installing... "BSD Subsystem" right in front of me
it's kinda like how brazillians know about americans but americans don't know much about brazillians.
you dig?
Dear Slashdot dimwit,
Thanks for idiot post on how BSD license doesn't see copyrights as a restriction on people's freedoms. I'm sure you won't like to hear this, but The GPL is COPYRIGHTED TOO!
Please READ the licenses before you act like a dumbass.
For example, (taken from:
http://www.gnu.org/licenses/gpl.txt)
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
There -are- licenses which disavow all copyright explicitly, perhaps you should go read up on them. kthx, bye.
Here're my impressions from the first 5 pages I managed to read.
0) It's just the East coast/West coast thing. Except for rap, everything else is better on the East coast.
1) The author constantly has to mention that he doesn't really have much familiarity with Debian/GNU/Linux/etc - but that doesn't stop him from making far-reaching conclusions and grand promises
2) If the BSD communitIES could get along first and form a BSD communitY - then I might be inclined to try them out.
The single most dangerous threat to the success of Linux, especially in the workplace, are the legions of fanboys
Are you sure, because "Linux" has other issues.
1) Over 200 seperate 'distros' (or forks) all calling themselves "Linux". Such creates market confusion.
2) Take this Eolas article. "Eolas Discussing Browser Patent With Linux Community" Errr, guys? Mozilla runs on Mac OS X, Windows, Solaris, FreeBSD. The Gnome and KDE browers run on FreeBSD, solaris, Mac OS X. When did "mozilla" become a stand in for "Linux Community". More market confusion when anything that touches Linux is then called "Linux".
Such mixed messages are what will keep GNU/Linux from going anywhere. Microsoft will bury it, just like they buried UNIX back in the 1990's when they called UNIX 'forked' and 'confusing' and offered Microsoft as a 'stable target'.
It really is about freedom. Either you have it, or you don't... and beer has nothing to do with it.
The problem is that Microsoft acts in ways that negatively impact the life of OSS folks (such as promoting .doc lockin). If you help Microsoft, you are helping someone who uses spare resources to repeatedly kick in you in the nuts.
May we never see th
You're off base with your comments.
Apple has released their changes when required, specifically KHTML, GCC, and others. They have also released their BSD codebase as Darwin, which is available at the following URL.
http://developer.apple.com/darwin/projects/
Feel free to look at all of the other code they have contributed. If you ask me, they're better than Microsoft simply because they participate. Microsoft doesn't do this, at all.
Maybe you're just writing flamebait and I'm a big sucker? Oh well.
I am not sure everyone understood what I meant. My intent was to echo a chord I felt in the message of the original comment: One does not take pride in work that one feels is used inappropriately.
I was not arguing good vs. bad so much as pointing out that even if your work is mis-used in your opinion, it is still valuable.
As for my own opinion, I dislike Microsoft's attitude of "embrace, extend, extinguish" because they embrace your work, extend it, then extinguish it. No one likes to see their work "extinguished", and this is what I felt the original poster was referring to.
I know that Jobs is no angel, but I am not aware of Apple using the same tactics. Please enlighten me if I am mistaken.
Well shit, what's this open-source Darwin thing with an OSI-approved license? You know, the one with modified BSD sources and their changes that also doubles as a fully-capable operating system on PPC and mostly-capable on x86? I guess a public CVS repository full of open-source code doesn't count as "releasing any changes." Strange world you live in.
How about all the work they've given back to KHTML's developers in producing Safari? Are they not releasing changes there, either?
I would also suggest reading up on monopolys in a capalist system.
then charges $130 per client per version for it. They don't release any changes.
I paid more like $40 per client and (at least in previous versions), have used the released source to work around bugs in things I'm doing.
-- The world is watching America, and America is watching TV.
...and call this flamebait, though i don't mean it as such.
....are the new hordes of OSX users that go around trumpeting "I AM A BSD POWERUSER" or "I HAVE A HIGH-END UNIX SERVER" "MY APPLE HAS PROTECTED MEMORY, PREEMPTIVE MULTITASKING AND UNIX, WHICH IS SOMETHING YOUR STUPID WINTEL PEECEE WILL NEVER HAVE" that have never seen the inside of a terminal window, init script or log file. Essentially lifelong Mac nuts.
What i think is a *real* issue for the BSD folks to consider if they are being misunderstood..
(and i mean this as informative, not scathing)
In other words, the BSD community just inherited a whole new legion of zealots, who will have the side effect of causing people (who probably also aren't very knowledgeable) to associate "BSD" with bad flamewars, etc. The difference is that some of these folks don't have a clue, and they spout a lot of dumb rhetoric.
Sure, there are zealots in *any* camp, and there are kind, knowledgeable, helpful folks in every camp too. I'm not saying that all OSX users are zealots, or clueless, or that all BSD users are assholes, or anything. Good and bad in all.
do() || do_not();
I use linux instead of *BSD for what I'll admit are pretty much subjective reasons - I spent a lot of time learning the various quirks, and FreeBSD just never fit right in my brain.
However, I think we're losing sight of the real fundamental dichotomy here, which, for lack of a better phrase, I'll call the 'Vendor/Community' spectrum. As it stands, Microsoft has power because they control the protocols that their users can access. Through 'embrace&extend', they try to ensure that you simply cannot interoperate with any other operating systems.
Apple would act this way if they could, I'm sure, but since they do not have the market share that MS does, they can't afford to have OS X be an island of its own. It's in their best interests to be a team player. For now.
These are the Large Evil Vendor and Small Brown-Nosing Vendor models, respectively.
Linux, *BSD, etc, all the (to whatever extent) open-source OSes are aware that they are part of a community. As such, it is the users, not business interests, that drive development. While there is value to a Vendor in lock-in, there is never value to a user in adding gratuitous incompatibilities. If Windows boxes can't talk nicely to Unix boxes, Bill Gates wins. If Linux boxes can't talk to OpenBSD boxes, nobody wins, and Linus and Theo will both want to figure out why, and fix it.
Every time I witness a debate between BSD and Linux fans, I reminded of the Star Trek episode where the Cheronians were a race of people who were black on one side and white on the other. One group claimed the other was inferior because they were black on the left side instead of the right.
It sort of puts us "holier than thou" Linux users in our places.
while true ; do echo this is my sig; done
...I could see the offtopic mod here, but why the troll?
"Could just be my impression, however I can't think of the last time I saw BSD mentioned in any trad mag. for any industry as an alternative to windows."
Well, that is partially the problem. Most people, myself included, tend to equate all the open source *nix's as one big thing. And then we just say linux because it's easier to explain.
Visiting colleague: "What server are you running?"
Me: "FreeBSD"
Visiting colleague: "Um...what's that?"
Me: "...linux"
Visiting colleague: "Oh, neat!"
Irregardless, I wasn't attempting to espouse the virtues of FreeBSD. Just countering some of the points the parent had made.
Does linux use any BSD code ? :)
MacOS X is largely OpenSource--under a vaild OpenSource license. AND Apple *has* released the source. The KHTML team has also been very pleased that Apple has contributed code to their project. You can even run MacOS X Core (Darwin) on your PC.
Hardly sounds like a proprietary OS to me.
People are divided into two camps on Gentoo: those who use it, and those who wish all the fucking Gentoo disciples would go jump off a fucking cliff.
-Looking for a job as a materials chemist or multivariat
Not exactly, the GPL in practice isn't copyright even if it technicaly is.
Just like a trojan or worms aren't really user applications even if they techicaly are.
The GPL is like a virus to the copyright system, it harms it, it looks like part of the (c)system, it is made of the same stuff that the rest of the (c)system, it works with the (c)system but it works to its destruction (at leat in the software department).
BSD isn't part of the (c)system, just like grass isn't part of cows, but cows eat grass. GPL has integrated itself into the (c)system but no one seriouly think it is about restrictions. When the only restriction is no restriction, you have to be very dim to call it restricted
But... the future refused to change.
cd /usr/ports/shells/bash
make install clean
Bash is now installed. What's the problem?
You want zsh? It's there. Plan9 shell? It's there.
The reason why (t)csh is still used is because of backwards compatibility. Something RH and many other distributions do not care about. You can still run FreeBSD 2.x binaries (circa 1995) on a FreeBSD 5.2 (released a couple of days ago). Try running a RH5/6 RPM on RH9 and see how far you get.
If you give out fish and loaves no strings attached, you will help out a lot of needy people -- but you may also end up giving a free meal to an agent of the enemy, who will use the money he saved on food to buy weapons to use against you.
If you give out fish and loaves but place conditions upon who you'll give to -- you only get a meal if you agree to attend church every week -- you may avoid helping the enemy, but you also won't help as many of the legitimately needy. Assuming the enemy doesn't just lie to you and promise to comne to church, then make off with the fishes.
Which of these did Jesus do? Which kind of behavior does the BSD license encourange? Which one is closer to the GPL model?
Or they use your code in order to create something that's compatible with your code, but your code is incompatible with.
Or they simply save resources on developing that code, and can put more resources into the Doc format lockin.
I'd rather OSS contributions were forced open so all could enjoy them. Those who want to create closed software can suffer from the same code duplication and inefficiencies that everyone else suffers of, due to the closed-software practices.
Well, when BSD switches to a new VM they think about it and test it in the development area and then leave it alone in the stable series.
When Linux switches to a new VM they switch in the middle of a "stable" series.
Which one do you think is best for a heavily loaded server?
It's free as in
freely included with the used computer I own.
free from annoying OS/License zealots.
The reason noone cares about BSD is because for 90% of us, anything we can do with one we can do with the other. So all other things being equal we go with the one that has more mindshare/software/hardware/support.
That's my reasoning, and I'll bet it's the majority opinion if you were to poll average linux users.
Sigs are awesome huh?
bsdl = protects user
gpl = protects developer
Huh? Please support this better.
GPL protects users by guaranteeing access to code, reducing the chance of abandonware should the original maintainers go out of business and quit, at least there is nothing preventing other maintainers from stepping up and continuing the torch. BSD doesn't necessarily help in this regard if a business takes BSD licened code, makes changes but does not release changes, so the users are SOL if they need a fix. Granted, Apple does release at least some changes, I don't track it so that isn't something I am qualified to say how much.
To be honest, CVS isn't all that hot as a VC system, compared to what could be done. The problem is that it's a pain in the ass to make a VC system, it's a pain in the ass to migrate from one to the other, and CVS has been there and free, so folks use it.
/proc out of box, this means that they can also do a fair amount of monitoring of what's going on.
Don't get me wrong -- using CVS is waaay better than no VC. CVS was the first VC system I used seriously (well, after a short stint with RCS). However, CVS is seriously hampered by trying to be highly compatible with RCS, which was never designed for the kinds of environments that CVS is used in.
Anyway, as to things that aren't that hot about CVS:
* CVS doesn't grok "text" files where the linefeed format matters. If you have a piece of software that uses a text file in CRLF format, you need to treat it as a binary format.
* CVS sucks -- badly -- from a security standpoint. The current feature branch is getting vaguely closer, fixing a huge number of symlink-related bugs present. Basically, something as simple as a repository where some folks have read access, some folks have read/write access, and some have no access to each module is a real pain to set up.
* CVS allows spoofing of version history. Bad, given that one reason folks like VC is that they treat it as auditable. CVS is *not* an auditing system that can be trusted for legal or security purposes.
* CVS does not grok the concept of files moving.
* CVS cannot version CVS metadata. This means that if you have a file checked in as text (accidentally), and at some point switch it to binary format, you must break all checkouts before the original date when you mark the file as binary.
* CVS understands things based on a file-by-file basis. While it's not too hard to write scripts to provide functionality like listing all tags used in a project, it's annoying that CVS can't handle this.
* CVS lacks some of the re-merging features that BitKeeper and more advanced VC systems have. I haven't needed to muck with this, but it's apparently one of the two big reasons that the Linux kernel folks don't use CVS.
* CVS can't do distributed, disconnected development. You have to have one server that everyone can talk to, full stop. This is the second major reason that the Linux kernel folks don't use CVS.
* CVS does not do atomic updates or checkouts across multiple files (as I said, CVS sees everything on a per-file basis). Frankly, our databases and filesystems all moved to transaction semantics long, long ago. A VC system has even less excuse not to have transaction support. CVS is way behind the times in terms of reliability -- theoretically, this can cause all kinds of nastiness.
* CVS makes it a real pain in the ass to delegate administrative access, and tends to not be particularly secure. For example, if I want to allow someone to add a module, and want some *subset* of the modules in a repository to generate commit notification messages, I need to give that person write access to CVSROOT/loginfo. Bad. (Again, you can write a program that provides this access, but it's not part of CVS.)
* The CVSWin GUI sucks, and hangs if CVS is processing anything. If you have anyone that doesn't use the CLI and uses Windows, life is annoying for them.
* Unless you want to do mucking about with secure shells, giving someone CVS write access means giving them shell access on the server. Because Linux (and, I suspect, most *IXes) don't support restricted
Really, to be honest, CVS was a cool system for when lots of people were using RCS. CVS's killer feature is RCS compatibility. Without this constraint, CVS would not have most of its drawbacks.
I haven't seriously checked out Subversion, but I'd like to see how well it stacks up. It certainly fixes at least some of the problems.
May we never see th
in my original post s/protects/saves ass of/
gpl is all about the developer's rights. user access to code is a by-product. bsdl is all about the user's rights to do whatever they please with it.
vodka, straight up, thank you!
Thanks. I don't mind the POV, it makes for more interesting reading anyway. Completely objective reviews/discussions are really quite boring.
I tinkered with BSD, and was trying to see if BSD could easily live in a Linux environment.
FreeBSD understands Linux extended partitions and ext2, but you cannot boot an ext2 fs.
NetBSD will boot ext2 fs, but cannot deal with extended partitions. You would need to edit the disk
label.
OpenBSD seemed worse, but I really never tried it.
This seems like something that the BSD people would want to encourage us Linux users to give it a try.
Except the developer choose to put their code under the BSD license.
I don't think it's because linux users don't understand BSD, I think it's because the loudest voices for BSD, like this guy, come off as arrogant elitists which is a terrible way to recruit.
Well, you've said nothing of substance.
bash, gcc, and other utilities (like, what, groff?) are installed on pretty much every BSD as part of the core system. The BSDs are, of course, compiled using gcc. There's no distinction between the "functionality" of Linux vs. BSD from that point of view.
No, the "traditional Unix" feel that the BSDs provide is in BSD interfaces. The BSD versions of ls, ps, and so on, behave in the tradition of their BSD 4.4 counterparts. The system APIs are in the style of BSD APIs, and so on. Init scripts, file system philosophy, user capabilities, &c., are BSDish.
These BSD interfaces are what enable "getting things done" in the BSD way . Some would argue that these interfaces are technical advantageous to "the Linux way" (read: mock Sys V), but, your implication that they're antiquated is most certainly incorrect. You lose nothing in robustness, flexibility, security, performance or interoperability in doing things the BSD way.
I've been using Linux since 1994, just so you know which camp I'm in. :)
Last few months or so, I've been using FreeBSD more and more. Why? No reason. Just for experience points.
IMHE (E for experience), the only substantive difference is, FreeBSD feels like Linux did about 7 years ago. You have to be *really picky* about what hardware you buy, and you have to acquire a certain elistist attitude to use on nonbelievers who scrunch up their faces at you. Other that that? Same.
On a snarky note, the author seems to make a big deal about chaos (Linux) v order (FreeBSD). My first thought was, "Wow, his toilet training must have been *intensive*!!!". But that's rude. Both of them have stable/development (STABLE/CURRENT) tracks, and they operate similarly. In one, Linus calls you an idiot; in the other, the Core Team ignores you. No big difference.
I will say, to other Linux lovers, check FreeBSD out. You'll be pleased by the massive similarities, and enlightened by the differences. Oh, and if you used Linux seven years ago, you can dust off and reuse your hardware-buying and heathen-dissing skills!
Ahh... so basically everyone who flamed me didn't even bother to read my entire post.
I'm not anti-BSD. I have no problems with BSD at all. I was speaking as a Linux user who's never tried BSD and I explained why.
I find it hilarious that the BSD zealots came out of the woodwork to flame me when I basically agree with everything they've said. If BSD people could be troubled to read, I guess they wouldn't look like such fools in this instance.
The bottom line is the fact that BSD has less support than Linux. I never said that you couldn't run GPL/GNU software on BSD. Linux has the mindshare, BSD does not. That's not an opinion, it's an established fact, for good or ill. Because of that, more people develop applications targeted at Linux. If it works with BSD, GREAT! But if not, most programmers aren't going to spend the time and effort to make it compatible with BSD (I know I don't... and I run one of the most popular O/S projects on Sourceforge) - I let the BSD people do that... because I simply have no interest in BSD.
Like I said, it's not that I think BSD is bad; I just know nothing about it and have absolutely no reason to know anything about it. I don't even know anyone that's run any of the BSD varients.
So all of your tools that felt the need to flame me over the quote about Linux users not needing to know BSD... I took that essentially from the article itself, that asked the question as to why most BSD users know Linux, but Linux users don't know BSD.
I answered the question of why... I didn't make the statement. One of your own BSD zealots made the statement, go flame him for asking a blindingly obvious question.
Popular OS's get the application support. BSD is not popular. That doesn't make it bad, it's just the way it is. Flaming me is not going to get me to try out BSD, that's for sure.
Well, you're even more incorrect if we judge what you say on actual outcomes. In actuality, the FreeBSD project has produced, and continues to produce, vibrant, technologically advanced, enterprise-grade operating systems, year after year, without 'assholes stepping on each others toes' due to the BSD license. The other BSDs do the same.
You've made sweeping generalizations that are utterly wrong, have no basis in reality, and whose articulation reinforces fallacious urban legends at the expense of free software developers and free software users.
You, sir, are a cad and my only hope is that the groupthink diminishes to the point where you're finally modded as such.
You say FBSD has no new hardware for new drivers, yet it installed and runs flawlessly on my laptop. Linux wouldn't work with the pcmcia slots (none of the distributions I tried played nicely). *BSD is far from dying, they just choose to create well writen drivers and take their time. BTW, it included USB support with autodetection of every device I've plugged in. USB hard drives worked. The USB cable modem I tried worked. Your information is old and outdated.
MS created some problems with the w2k conversion :/
Mycrosoft's use of BSD code is both legal, and ethical, in that it is a voluntary action, done with the informed consent of both the parties involved.
However, that alternatives exist at all is not a test for Monopoly. If it were, there could never be a true monopoly, ever. A monopoly exists wherever those alternatives face constraints other than those of the market in surviving, gaining a share, or making a profit. Now you know why "everyone, even the court system", disagrees with you. It's legal to have a widely used product, all the way to 100% share. It's not legal to engage in what the court calls anti- competitive practices to protect or augment that share.
Refusing to sell to hardware vendors unless they do not enter into other contracts with your competitors, for example. Given that the hardware vendors are publicly traded companies, they cannot legally refuse to take such a deal, as the short term penalties to their own stock would be a violation of existing laws protecting shareholders. Ergo, a monopoly exists, at least so long as the shareholder protection law exists.
Maybe in a world where there were not a lot of other laws, monopoly would be as impossible as you seem to think it is. So, let's get rid of the Sherman anti-trust law, RIGHT AFTER we repeal all the other laws that made it vitally necessary. Better yet, let's figure out how to change these laws, a few at a time and with the overall goal of moving smoothly from Mercantilism to a true free amrket.
Who is John Cabal?
First, you mischaracterize "anarchy" as disorder and chaos, which is an unfalling indication that you have no background in political science, understanding of political history, or grasp of the philosophies of governance (from all "wings") over the last 50 to 200 years.
Second, these licenses exist in a word where so-called "intellectual property" rights (such as the dubious Berne Convention Copyright) are the law. The GPL and the BSD licenses would not exist were it not for copyright laws. The GPL was founded to spite copyright law, and, if you ask Richard Stallman, he'll tell you he wouldn't have created it if the copyright for software did not exist. This means that in a copyrightless world, all software would be BSD licensed.
This means, of course, that both BSD and GPL ultimately mean anarchy in a society free of fallacious intellectual property rights. Of course, anarchy isn't disorder or chaos, as you've claimed, it means "no rulers" -- and that's exactly what we're after.
The goal of the GPL is to give all users freedom, not just the programmers who use the code ... but everyone down the chain too. The BSD is fine for what it is, public domain for the vain, but the GPL seeks to guarantuee freedom and not just give out free source code.
I have faith in capitalism, if I want repricosal behaviour from those who use my code I need to enforce it.
bsd = unix;
linux = ++unix;
You might not care, but a lot of the developers do ... and they aren't exactly unimportant either :)
I've never understood why people think that's significant.
For the source code pouring out of Uni's EE departments, GPL licensed software vastly outnumbers BSD licensed software :)
Now having use NetBSD, FreeBSD and Linux, in some ways I like Linux, but in some ways I like the BSD's. Figuring out why a service is started under BSD seems easier to me as they are all listed in rc.conf, but in RH Linux they have a whole directory of stuff. eep!
I use both. Linux cause its easier to install most programs (synaptic && atp-get rpm).
Only 'flamers' flame!
Does slashdot hate my posts?
...here you go...
:o)
I am NaN
Yeah, I think he used the commonly accepted English definition of the word "right" meaning "correct for my purposes."
What else was he supposed to mean? If I said to you, "I think my choice of refridgerator is the right one" would you jump to the conclusion that I meant "absolutely right in all circumstances" or "right for me"?
Fucking wanker.
more
Bogus
I think the tension between BSD/Linux camps is pretty funny really. I mean *GEEKY*. But I think its pretty easy to lay blame on the new/old schools of OS thought. I mean both are good and anyone serious about computers or programing knows that. They both do different things in slightly different ways and one (you'll have to guess) happens to be a little more old school then the other.
I'm all about the license, which is probably the SECOND biggest reasons for flame-wars but c'mon, they are both good here too. Simply depends on how you like to express your values.
Of course the best thing is that we have the ablility to flame eachother about this at all. I mean two (+/-) totally free operating systems just begging for you to muck around with!
Quack, quack.
Linux for the desktop, BSD for the servers/workstations... ;-P
Your point was something along the lines of, "I am one of Slashdots many Gentoo zealots. Don't forget about us!"
Because otherwise your point was, "The author forgot about a very tiny part of the linux community that happens to be doing something else similar for very different reasons."
You didn't say anything else in your original post. You just picked a nit. If you pick nits, prepare to have your nits picked. I was kind of being silly about it, but I guess that was totally lost.
In any event, the Ports system is a big advantage for many things. Not the least of which it is the same everywhere, and it makes life easy when you want to synchronize. This was the author's point. This is a distinct advantage over what the majority of linux users use. Yes, Gentoo and your homegrown linux might use something. Hell, even MacOSX has gotten in on the ports craze.
That doesn't invalidate the point the author was trying to make, as you tried to suggest it did.
Slashdot. It's Not For Common Sense
BSD is the concept album. Linux is a bunch of singles.
i used to have freebsd and linux on my pc, now linux is the only resident. there was a shared partition on /dev/hda2 or /dev/ad0s2 that wouldn't mount until i created the slice w/freebsd, rebooted, made the filesystem with linux, and recompiled the freebsd kernel with ext2fs support. that's not so bad, but every time the shared partition was mounted under freebsd, it couldn't clear the buffers on shutdown and failed to umount the partitions. then fsck_ext2fs didn't work on bootup...
after that i found that many ports were available for linux as well, and the added disk space won out over my desire to learn freebsd
Yes, and the GNU versions of ls, ps, more, etc. which are installed on nearly every Sun workstation I see nowadays as replacements for the official BSD versions.
/usr/ucb on SunOS 5.x. But, moreover, the FreeBSD versions of ls, ps, etc. aren't the ones from 4.4BSD nor from 386BSD... they're new versions, with improved functionality, but in the style of BSD. We're talking about continuing a tradition. Realistically, the GNU tools are tools in the style of System V (which is where the new Solaris/SunOS 5+ tools derive). GNU tools are as much "authentic, traditional" as BSD tools, in that sense, except that no real source was ever shared between Sys V and GNU. But, that's why I told you there's no real distiction there--both sets of tools are as capable, generally.
Well, look in
Yes, the systems *calling* themselves BSDs today have bash and gcc, but if you are going to be pulling the authenticity card, you should use csh and K&R cc.
One more time, for the ladies in the nosebleeds: nobody claims BSD tools are identical to 4.4BSD or earlier tools. Modern BSD tools are better than their 4.4BSD counterparts.
What BSD inherits is the BSD UNIX tradition -- for instance, BSD sockets, or, a BSD libc, or, the way BSD handles user capabilities... or how BSD has no System V runlevels... or the way BSD handles processes... or the way BSD organizes its filesystems... or the way BSD handles its kernel behaviours... and so on, and so on, and so on.
Those things are very much "BSDish" -- they are authentically BSD for a number of reasons: perhaps they derive from 4.4BSD source; perhaps they share the "BSD design philosophy"; perhaps they conform to published standards on the behaviour of BSD interfaces... or whatever.
The point you're missing is that there's no "authenticity card" to play, because, we're not in a pissing contest. The purpose of illustrating that BSD has roots in a tradition of UNIX founded at UC Berkeley is to make descriptive statements about the reasons, philosophies and mechanics of how things are done in the BSD world.
There are probably three great UNIX traditions: the BSD tradition, from UC Berkeley, the System V tradition (adopted in most commercial Unices and SunOS after version 4), and the GNU/Linux tradition (which is thoroughly rooted in System V, but, it is unique and has its own divergent philosophical roots).
So, no, the dichotomy is -- once more -- not about practicality vs. authenticity: it's about different design choices dictated by different philosophies, histories, and codebases. Both systems are clearly concerned with practicality, robustness, flexibility, efficiency, performance, security, and so on, above and beyond some blind nostalgia.
Why is this offtopic? I don't see it....
It is precisely because of the GNU software that comes with all Linux distributions as standard that I prefer Linux to the "real" Unixes (Solaris, Irix, etc.).
GNU software is really high quality. I now really begrudge every minute I spend working on old Unix machines where programs like sed have arbitrary line length limits. It's the GNU part of Linux that makes it great (sorry Linus). I really know sod all about the kernel, but the GNU/Linux combination works for me.
flossie
Write now. Defend liberty
To be specific about the apps, none of the traditional UNIX RDBMS run on *BSD -- Oracle, Sybase, etc. They all run on Linux. And that's just the tip of the iceburg -- you've got Oracle Apps, SAP, WebSphere, BEA, 100 other Java Servers, none of which run on BSD. And these are strategic, CIO-Sell-Level apps that matter.
Nearly every single one of those things runs perfectly well on FreeBSD. What was your point again?
Even without a "FreeBSD native" version, FreeBSD is capable of running Linux binaries through a kernel personality... API calls are automatically converted, and, what's more -- this results in execution as fast, if not faster (yes, it's true), than on a Linux kernel proper.
So, whatever, you're spreading lies.
is the fact that it has a stiffer feel to it compared to linux, which is a bit more flexible. and has a friendlier userbase, I havent been in one bsd chat where there are people who arent socially inept and fanatical.. I've seen lots of linux chats that are fanatical and socially inept, but I've also actually seen friendly linux chatrooms with people willing to help.
I'm sorry, but rtfm can only be an excuse for ignorance for so long before it becomes obvious that the people saying that and bitching a lot because you need help where a manual cant help are too afraid to admit they dont know either.
I tried bsd once, it's ok, openbsd is great for misc server work, small and stable, but I ran into various little issues that I didnt like. and the stiffness of bsd is annoying. I just feel more comfortable with linux as a daily operating system.
BSD is just better as a server operating system, it's not good for gaming, it's not good for most media, so, that's why linux is more popular. because of its flexibility and up to date functionality.
First of all, the claims of superiority of FreeBSD to Debian/GNU Linux are utterly bogus. Debian chooses to distribute its packages in ready binary form, while FreeBSD mostly prefers it if you compile everything from ports. So neither is superior as far as packages are concerned. However, keeping Debian current and secure is a single command that needs to be run occasionally (you know what it is). With FreeBSD it's more difficult and you have to spend considerable time compiling stuff regularly.
Another issue that FreeBSD advocates like to bring up is that there are many Linux distributions and only one FreeBSD. This argument is as popular as it is irrelevant. You don't have to run all the Linux distributions, just pick one (like Debian, for example)
I can't speak about the kernel quality, since I never use unstable kernels and all kernels that I used were very fine with me.
As to security, BSD advocates frequently claim that their system is more secure that Linux (which for me stands for Debian, since it's the only Linux I will use). This claim is wrong. To see for yourself, check SecurityFocus. OpenBSD, allegedly the more secure BSD brand claims to only have had 1 or 2 remote exploits in the past few years. Considering how minimalistic OpenBSD is, this is no big deed - you need to run services to have remote exploits.
Much has to be said about community. Debian has one of the best geek communities around. #debian IRC channel is much, much more helpful than #freebsd channel, in my experience. Most of the FreeBSD questions are answered with RTFM, which implies reading a 1000+ page FreeBSD manual. Quite often the RTFM answer is simply misplaced (there is no answer in the manual). But at least it makes the 31337 FreeBSD h4k0rs feel superior.
Last, but not least, the industry is consolidating behind Linux, and not BSD or Windows or OS X.
If you hear more anti-Linux and pro-BSD rants than anti-BSD and pro-Linux ones it's only because BSD is largely irrelevant to Linux users, while BSD users have to suffer in the shaddow of Linux, and port software from it (or try to run it in the compatibility mode - not always successfully)
BSD is. Linux is. If you look at the fundamentalities, they are different. If you look at the practicalities, BSD users use GNU tools and Linux users use BSD tools. That they are seperate is good because we have choice. It's like competition in the workplace, because we're all on the same team. I run BSD's and Linux's including Gentoo which is right in the middle.
-- I was raised on the command line, bitch
FreeBSD has binary patching as well here
Helevius
Posted from a FreeBSD 5.2 RELEASE laptop
The problems seem pretty cut and dry.
Due to the change from a.out to ELF binary format in OpenBSD 3.4, upgrades can be a complex, delicate process. The best solution, whenever possible, is to backup your data and reinstall from scratch... In all cases, once you start the upgrade you MUST complete it. If the upgrade process fails or is abandoned before it completes you will almost certainly be left with a non-functional system... Finally, you cannot use the bsd.rd kernel to upgrade the system. The existing bootblocks on your system cannot boot the 3.4 bsd.rd.
Pardon me for reading the instructions.
When I first started out with open-source I was very interested in trying out *BSD. It wasn't until I read a little into the differences between the BSD and GPL way of licensing software that I decided to support Linux.
For what it's worth, I think the BSD mascot is cooler than the Linux mascot.
I am speaking from the point of view of a Linux user.
The crux of what the gentleman has written about BSD and Linux's main difference seems to be stability vs. adaptability. There is one small point that is crucial to Linux's adoption over that of BSD. It's a point that I think the author knows, but did not focus on when he wrote his articles. If you have hardware, odds are Linux will get on it FIRST before BSD by a factor of months to years. And why is this.. because demand is met by Linux first. BSD values correctness or cleanliness over getting it to simply work. I admire that, but that's about it.
This is how technology works.. just like anything else. First come, first serve. The saturation point is reached sooner to whomever is first. If I'm hungry, I want something to eat. I don't care if it's a 5 course meal shipped from Paris, or a madcow burger from McDonald's. I'm fucking hungry- NOW! Anyhow, that's one lame example. Now to continue..
Linux is not as stable as BSD. Everyone knows this. Netcraft has documented it for web servers. Experience shows us this for ssh, ftp, and the like. But that doesn't matter- if this package isn't available, or this feature isn't available, or this hardware isn't available. If you cannot adapt rapidly to a changing environment, then you are left behind.
It is said that "intelligence", by definition, is the ability to adapt. Evolution is messy. The fact that most people have an appendix sitting there waiting to get infected and burst is tribute to how adaptation isn't clean and neat and orderly. Nature IS this. Scientific progress is no different.
I would like it to be different, but we aren't that smart. We have no foresight as human beings. We are bumbling idiots pretending to be aware. Achievement for us is gained by learning from failure- not by innately knowing what is right or wrong. This is how we got to where we are now.
I have great respect for BSD and it's users. Although, they seem to be upset by the lack of attention paid to them for some reason. That's a subjective observation on my part. Either way, I don't care if their feelings are hurt. This is reality. Linux works and does what I need it to. When BSD does the same, then I'm all over it. Until then, keep on doing your thing. BSD serves a great niche. I hope they survive. And I wish them the best. We will see if "adaptability" or "correctness" survives in time. Until then, I want to say I admire both camps.
Take care.
Thor
I can say that for me, the single worst thing about the *BSDs is the way the kernel is bound into the base system.
My FreeBSD experience went roughly thus:
Maybe I was unlucky. But the lesson I learned from this is that when monolithic `designed' systems go wrong, you're screwed. Modular systems, by contrast, give you the option of swapping out faulty components, even if the resulting system is slightly less slick than a monolithic system.
I now use Debian Stable for high-availability systems, and Gentoo for high-performance systems. Gentoo is, of course, the modular system par excellence, giving you total control over all aspects of the packages you use. Debian is less so, but gives you the security of knowing that your system has been thoroughly tested under all the conditions it is likely to encounter, and that with a modicum of judgement, updating whenever new packages appear will give superlative security without compromising stability.
And, of course, if the latest kernel screws up your system, you can downgrade to the previous version with absolute freedom. To me that's worth far more than whatever an integrated system can provide.
There are? You're kidding? Where?
Need Mercedes parts ?
case statement in /etc/rc to support this behavior, but pdksh does not currently support a case statement.
You, sir, are an idiot. See here.
Anyway, I consider myself somewhat of an advanced *nix user, even though I've only been doing it circa 2001. I started out with linux, of course, and liked it very much. I've seen the both the system and the open source community make tremendous leaps and bounds in just these few short years, and I must say that linux is absolutely a fine operating system.
Despite this, I was also compelled to try FreeBSD; I'm always interested in trying new things and tinkering around as much as I can with things I know little about, so naturally BSD was the perfect target for me. Being used to linux, I found the subtle differences in BSD very attractive; I wanted to get in on this because of the useful knowledge would provide as well as the rich history behind it. Also, a tiny bit of zealously may have played a part ("Wow, it's really unix!) ;)
I had a touch and go realtionship with BSD for the past several years, but it wasn't only until this one that I got a little more serious about it. Putting linux down for a while, I delved deeper into the use and maintanence of the system, gaining the kind of more intimate knowledge that the casual user probably doesn't have.
What happened was that I loved absolutely everything about it; it was very different than linux! Instead of groping around for strange tools and trying to fight a quirky system with which, due to constant mutation, there was always some uncertainty as to the correct way of doing things (are you running distribution X, Y, or Z? What version of software package A do you have, and are you using libraries B or C?).
With BSD, I found a system that was consistent, reliable, and very practical in its design. If you wanted to do something, there was a right way to do it, and this way always works (and works well, at that). Package management was top notch, and upgrading, maintaining, and generally managing the system was a quick, easy, and painless process. It is often said that BSD is not "user friendly", but I guess it's true when they say unix is "picky about who its friends are." To a moderately advanced user like me, BSD was more friendly and easy to use than linux! There aren't as many programs that will hold your wee-wee for you so you don't miss, but all of the information you need to know in order to do a certain thing is always readily available and right up front, beckoning for you to do it yourself and do it right. (some linux distributions are much better in this respect than others)
It must be said, however, that linux is a very fine system in its own right, and not to be looked down upon in any way! As Matthew says in his article, the big differences are mainly philosophical and cultural, and I have just found myself very much at home in this culture and very agreeable towards this philosophy.
What puzzles me is all of the rampant slandering of BSD that goes on by linux users (only a small percentage of this is meant to counteract the slandering made against linux by BSD users). Yes, there are common myths (like the ones Windows users hold towards linux, which make us all cringe), and yes, there are many misconceptions afloat.
Regardless of personal preference, the fact remains that BSD is also a very fine operating system, and does a few things a lot better than linux. Of course, linux does a few things a lot better than BSD, so when choosing between the two it's important to learn what those things are and how important they are to you.
I'm a Linux user, but I do consider trying FreeBSD. The only thing that turns me off is people like you.
Maybe I'm missing something here, but what do "people like [him]" have anything to do with you trying an operating system? Either try it because you're curious, or geeky, or bored, or interested in expanding your horizons. Or... don't try it because you're happy with what you have, or because you aren't interested, or because you don't have the time. Geez... do crappy drivers keep you from owning a car?
Not from the featured article, but from here:
4.4 What versions of BSD are available?
In contrast to the numerous Linux distributions, there are only three open source BSDs. Each BSD project maintains its own source tree and its own kernel. In practice, though, there appear to be fewer divergences between the userland code of the projects than there is in Linux.
It is difficult to categorize the goals of each project: the differences are very subjective. Basically,
*
FreeBSD aims for high performance and ease of use by end users, and is a favourite of web content providers. It runs on PCs and Compaq's Alpha processors. The FreeBSD project has significantly more users than the other projects.
*
NetBSD aims for maximum portability: ``of course it runs NetBSD''. It runs on machines from palmtops to large servers, and has even been used on NASA space missions. It is a particularly good choice for running on old non-Intel hardware.
*
OpenBSD aims for security and code purity: it uses a combination of the open source concept and rigorous code reviews to create a system which is demonstrably correct, making it the choice of security-conscious organizations such as banks, stock exchanges and US Government departments. Like NetBSD, it runs on a number of platforms.
There are also two additional BSD UNIX operating systems which are not open source, BSD/OS and Apple's Mac OS(R) X:
*
BSD/OS is the oldest of the 4.4BSD derivatives. It is not open source, though source code licenses are available at relatively low cost. It resembles FreeBSD in many ways.
*
Mac OS X is the latest version of the operating system for Apple Computer Inc.'s Macintosh(R) line. The BSD core of this operating system, Darwin, is available as a fully functional open source operating system for x86 and PPC computers. The Aqua/Quartz graphics system and many other proprietary aspects of Mac OS X remain closed-source, however. Several Darwin developers are also FreeBSD committers, and vice-versa.
The Greens have mastered the ability to conjure up a scare campaign about almost anything to such perfection, one almost forgets that they are a lying bunch whose past lies have harmed the timber industry, those engaged in ranching and agriculture, those who provide the chemical building blocks of everything we use every day, and those responsible for providing the energy this nation requires to function. The Greens, assisted by journalists with an agenda, create such a campaign.
After reading through all that I feel obligated to comment. It wasn't all drivel, but there are definately points where linux ingnorance comes through. When it comes to packages vs ports, both can work equally well. I tell RH users all the time, if your going to use an RPM based system, stick with vendor supplied RPMs and it works like a charm. It's very much a static product at that point. If you want something that is not in a vendor supplied RPM at least build the RPM from the SRPM and better yet, put in /usr/local or /opt. On the other hand, when I'm on a gentoo or BSD system, you run into a different problem. Version stability. If an end user customer pays some developer to build a spiffy web app they don't want it broken by upgrades. You see companies like this all the time. They outsource dev, and administration to two seperate parties then lose the developers business card. Anyway, when you don't have a lot of control or intimate knowledge of what code make a web app go, or better yet, no idea what it is, it's very nice to be able to apply security errata and maintain version stability. That's where the vender RPM dependancy is good. You just run up2date or yum and poof, You have exactly the same system with exactly the same version of everything, the only difference being the bug is patched, backported. Now Gentoo, and FreeBSD, both of which warm my heart, tend to force rolling upgrades. You can't just port security errata unless you manually fix the code yourself. Instead you upgrade to the secure release. This mean you may be including any number of changes that break any number of things in all that unknown code on the box. This really has gotchas when updating APIs like PHP and sudenly certain global variables no longer exist. Now if your the developer and the sysadmin, no problem right. Just fix it and stop being a wuss. If your joe outsource, your fucked. It will take you two hours to find your developer and sysadmins phone numbers in your rolladex and another 2 to convince them that your emergency is their emergency. Then you have to pay through for the nose while enduring an outage of unknown length for an unknown durration for reasons that you'll never understand while the hired guns poke around and scratch there heads. With version stability much of this scenario is mitigated.
Anyway, I think your view of linux is simplistic and misses all of the strengths and diversity of linux.
The differences between the licenses go quite deep. The BSD license comes from an academic tradition that software is a form of human knowledge. You do the work, write the peer-reviewed papers, pocket your grant-funded salary, talk about it in lecture and move on to the next project. Why worry about who uses it. It's knowledge! Spread it around! Share it! Endless supply!
It contrast, GPL-folk tend to think of things in terms of products competing for mindshare. From this perspective the worst thing that can happen is competing against yourself. As such they want to be altruistic, but they don't want to be so altruistic that their work is placed at a disadvantage. Horrors! Big Blue might steal my work!
am I missing something? who exactly is matt fuller and why do his opinions make frontpage slashdot?
I checked his homepage... the biggest thing he's done is create a patch for Postfix so it "logs (and displays) its version number when it's started up"
was this not just published on slashdot to incite a flame war??? ~700 comments into the story (~300 of which are modded -1) tells me yes...
Here's to finally giving Bush his exit strategy in November
I thought we all became Linux users to avoid the Blue Screen of Death!
What's that? Oh, that BSD?
Never mind, then.
This is by far the best line.....
:)
'So, I'm not saying you should dump your Solaris systems (let alone your Sun stock!)'
seems a little out of date to me
finse
Paranoid tinfoil hat crowd say Y here, everyone else say N.
Mod up!
/etc/csh.cshrc.
We have Bash in the ports and package collections that you can install anyway during installation.
I prefer the modern Tcsh that is based on the 4.4 version but is update. Its not the same one from the 80's at all. Same is true with make. BSD pmake are what most ports use to do a ftp for their ports. gmake is available as well which is called make under Linux. I find it easier to read and do system administration.
4.4csh is available via the ports as well but like the parent claims it has not been used since the 1.0 days of FreeBSD.
I can also have color xterms by just doing a alias ls gnuls --color in
I have supperior man pages and info pages too. For example I can type man tuning or man security, as well as the regular man pages. Again its not available in Linux.
The reason why FreeBSd feels old by default is its more possix compliant just like sun workstations. Bash does not equal the standard. This makes unix scripts run by default which would choke in Linux under bash.
I am sick of the old BSD is old, or BSD is dieing.
http://saveie6.com/
Yes, I know about the AT&T agreement. But my point is to a desktop user the differences are invisable. You would really have to look under the hood a bit to tell what you are running. So I don't think that the real issue lies here. On the server side of things, there is no doubt that BSD has been doing it longer and for a good while was doing it better than Linux. But the Open Source explosion we are seeing is centered around Linux and the GPL'ed applications, not BSD. I believe (as does Linus) that Open Development in the less structured (bazaar) method of Linux is superior to the structured (cathedral) methods of BSD. As a result Linux has done the real grabbing of market share in the enterprise. This is not because BSD is bad. BSD is very good and Linux owes a huge debt. But Linux is better. SCO's original claims centered on the idea that it could not have come so far so fast without stealing. What they failed to understand was the incredible power of its development model. I for one am glad that BSD exists and have used it for many purposes. Without the flexability of its license Apple would probably never have ventured into the Open Source waters. But I am much more grateful for Linux. For my servers, I will use Linux, because it now surpasses any of the BSD's for enterprise systems. I don't think we will see Microsoft sweating over TCO comparisons with BSD for a while.
After reading that I feel almost ashamed. But really the author and all those that think like that should feel shame. I like FreeBSD for it's licence and it's legacy. Maybe FreeBSD now is as the author discribes but there never would have been a FreeBSD without the origional BSD hackers fixing things and sharing patches. Not all the patches and programs origionated at Berkley. What the school did was organize a distribution amist all the chaos. In reality it was the first hacker rebirth of an OS. They took a flakey prototype and make something useful of it.
The only real part the author got right was the anology in comparing BSD/Linux to PC/Unix users. Mainframe verses PC; Client/Server verses decentralized P2P. But there is no reason it has to be that way. And in fact it can't because FreeBSD is just a fragmented in it's pieces as linux, many like him just won't admit it.
I like BSD for it's licence. I dislike Linux for it's licence. There is some truth to FreeBSD being a stronger distribution (which is another reason I like it) but it's still a distribution all the same as any Linux distribution. His statements to the contrary just don't stand up. Both sides pick and patch from what's useful.
FreeBSD is a distribution built around a core set of tools with relatively tight quality control. It is more focused that many Linux Distros. FreeBSD is also controled democraticly among the elite where Linux people have no problems forking code and competing against one another, with users and distributors judging the winners and hence is more democract.
The FreeBSD ruling class may have a bug up their ass about somethings but I'm still free to fork code. But it turns out it's not worth it. If you have good reasoning on your side and enough patience people learn, or else they die while you persist. In gerneral BSD is more about patience, who has it, and who doesn't.
Java on BSD isn't ready for production server use, according to the developers.
You have never run a real Oracle server on BSD, so you wouldn't know if it works or not (it doesn't really).
The machine actually didn't detect the networking device within Windows. Yet, it worked fine within FreeBSD, without any configuration at all from install.
My first exploration outside of Windows was with FreeBSD 4.5. I ran it in a virtual machine on my Windows box, played with it, read about it, and finally decided to switch over to it. I loaded it on all of my systems and made a go of using it. But there were too many problems with hardware incompatibilities, in fact, my RAID controller went nutz and actually damaged 2 out of the four hard drives. My printer was not supported, so on, and so forth.
After that I switched to Red Hat Linux, which still gave me a few learning curve problems, so I switched to Mandrake Linux and have been with it ever since. Just like in your case, I don't have system crashes on my servers, just on my workstation since that is the one I am always experimenting on ( different drivers, tweaks, etc ) but even then the crash is harmless, no data or hardware lost.
Sorry FreeBSD, you did your best, but sometimes your best just isn't good enough. I would say that if someone where migrating from Windows, they should move to Linux, not FreeBSD. If someone is already on FreeBSD, they should feel free to stay, as you probably have the kinks worked out for your particular environment.
I can't afford a sig!
If I understand the article correctly, BSD is even more monolithic than linux, and stuff like libc and ls are part of the BSD base itself. This sounds like no modularity at all.
If this is so, I will say: thanks but no thanks, I'll stick to my Debian GNU/Linux, and keep my eye out for a good microkernel OS.
Bram Stolk http://stolk.org/tlctc/
But it's not about including a port. Microsoft could include a port of OpenSSH even if used the GPL. In fact, that's basically what they're doing with SFU: it's bundled with software using both the GPL and the BSD licenses.
The danger of the BSD license is when Microsoft modifies OpenSSH in some manner that means MS-SSH clients can communicate with MS-SSH servers, but the standard OpenSSH client cannot communicate with MS-SSH servers. As the maintainer of OpenSSH you're now in a pickle. You can either leave OpenSSH without "MS-SSH server support", which means OpenSSH is inferior to MS-SSH. Or you can expend the effort to reverse-engineer the feature and independently implement it in OpenSSH. But that's a fairly inefficient use of your time that could be better spent on improving other aspects of OpenSSH.
So the BSD license leads to repeated work and redundant work. Or it leads to bifurcation and incompatibility. Either way, I don't like it. But it's your code so if you like the BSD license... shrug... go for it.
Simply by typing glxinfo and seeing the wonderfull mesa software renderer. Hardware support in the BSDS is a JOKE!
France is a fascinating country or that is what everybody says, but I have to admit, I could never get my head around this concept. Ok, so every time (more than 20 times over the past 10 odd years), I have been to France, something or other has gone wrong, so I am rather jaundiced towards that country. Plus a man growing up eating all varieties of Indian cuisine will not get excited about French cuisine at all. Yes, they are well decorated but tiny portions do not make a meal! Finally I am not a wine connoisseur, I think of it more like grape juice gone bad, so there is really nothing much to attract me to that country. I lie; the cognac is excellent. Ok, ok, so I finally found something that France does well. So how come a country which makes such excellent cognac managed to screw up its foreign policy this year so thoroughly? Obviously, 2003 was not a good year for the French foreign policy vintage.
gpl is all about the developer's rights. user access to code is a by-product.
I couldn't agree more. Lots of people here seem to confuse users and developers. I believe that I understand RMS's motivations for creating the GPL - to redress the perceived power imbalance between the technical elite (developers) and the technical 'underclass' (users). By allowing/enforcing free access to the source, everyone can make whatever changes they like.
All good in theory, but there's a snag - the vast majority of users can't make changes, even with the source. They neither know how to code, nor care, and in a lot of cases, quite possibly wouldn't be any good even if they were taught. That's not an insult - I'm a pretty good programmer, but, for example, can't sing, can't draw, and have very little "traditional" creative talent. I'll never be an artist, or a musician, or an athlete, and in the same way, most people will never be programmers.
That, I think, is something a lot of people forget - end-user access to the code is essentially irrelevant. It is just a byproduct of allowing developers access to it.
It's official. Most of you are morons.
You can still run Linux using a ports-like system, compiling everything from source: check out Gentoo Linux.
Phillip.
Property for sale in Nice, France
It's been my impression that the BSD communit{y,ies}, in general, understand Linux far better than the Linux communit{y,ies} understand BSD. I think a lot of Linux people get turned off BSD because they don't really understand how and why it's put together.
Linux users don't have an opinion about BSD, they just don't know any better. We on the other side know better and use BSD because it is so much more elite. Linux isn't geeky enough anymore and that's why we have to reeducate Linux users. It's only for their own good!
Thus, this rant; as a BSD person, I want to try to explain how BSD works in a way that Linux people can absorb.
Linux users wouldn't get it if you'd slap them over the head with a 12 lb BSD manual, so here's the absolute dummy's guide to BSD that even a totally brainless halfwit can understand.
If a train station is a place where a train stops, what's a workstation?
Companies like Microsoft don't need help to break standards, they are more than capable of doing it on their own. In fact the SFU example demonstrates the exact opposite: the code was available, it was adopted in a compatible manner, the license was followed and the result was good for everyone.
If anything, the existence of code in a incompatible license is going to increase the likelihood of deranged implementation. If they already have to reimplement it because they are unwilling to put up with GPL code in their product, then they are just as likely to implement all the features that they want while they are there (and standards be damned).
An interesting aside - someone from a company that offers commercial Windows interop tools has already has posted patches to build OpenSSH under Interix SFU. So please don't tell me that the BSD license equates to wasted effort and closed derivates.
This is BSD advocacy, poorly disguised. A demon in sheep's clothing.
What do you you expect radical egalitarianism where the banal philistines rule ?
NOT. That is what your inferior linux OS is for.
Linux is for bitches and stupid ones at that.
www.linuxisforbitches.com
I don't know about performance
There seems to be a lot more mainstream support for GNU/Linux and a lot more development of new things. Translation: more goodies coming for GNU/Linux.
Communities?
I have had a lot more exposure to the GNU/Linux community then the BSD community.
The BSD community seems to be more dominated by mature people( with the *possible* exception of the author of the site that inspired this thread).
If they don't want to answer a question, they will not answer a question. No flaming, no ROTFM, no googling. Very smart....why waste your time typing on an issue you don't care about. If you do get ROTFMed by a BSD person chances are you will get a very sober, mature, well written, *polite* note advising you to do your own researh with some pointers.
These people kinds of people are in the majority in the GNU/Linux community as well, but that community also has a voiceferous minority of grown men who have never quite finished maturing.
The last excuse for a difference between distros IMHO would be the license issue.
I still believe in the GPL and the Free(dom) Software Movement as opposed to the open source movement.
People who develop under the BSD license must be very unselfish.
I know if I spent my spare time codeing for free of charge I would want my contributions to be shared to everyone. I would be furious if a business with a payroll, resources etc gobbled up my code, incorporated it into a proprietary venture, burped, and did not give me compensation of any kind......at least recognition. Microsofts use of BSD sockets comes to mind.
Some people will rightfully point out that the BSD license encourages some contributions that the GPL does not.....my answer to that is the overwhelming support for GNU/Linux by IBM and several other companies.
I also have to wonder that if the BSD license became popular first if the open source movement( as opposed to the Free(dom) Software Movement) would have its emphasis on sharing.
I doubt it and I doubt that the open source movement would have gotten off the ground. Many businesses would have done an M$/BSD-Socket manuevar taking, and giving nothing back with the result of there being a very small library of open source code available to everyone.
Finally, a word about user friendliness, the bastard step child of both the Free(dom) Software Movement and the open source movement.
GNU/Linux got some of it first which encouraged me to dump windows at home. That encouraged me to get used to *nix, and venture into user
UN
friendly territory, which encouraged me to like *nix for itself.....again( I had that Solaris shell account everyone did in college ).So, because of GNU/Linux I might just try and/or migrate to BSD someday.....or use both.
The two communities gain much from each other.
Steve
I just finished reading the article, and it's amazing how wrong many of his statements were. For somebody claiming to understand Linux users and the differences between Linux and BSD, the author would do well to do a little research before wasting his time writing up an article such as this one.
/sys/blahblahblah.txt when upgrading, moron", but this was also missed by my boss, who'd been using FreeBSD since before they were widespread enough for CERT to mention them in security advisories. Also, coming from Debian I'd have expected a note about the change during the upgrade process.
As a Debian user, I wouldn't claim to understand Slackware, or Redhat, or even BSD, despite the fact that I cut my teeth on Slackware, used Redhat for a while, and used to admin at a data center using exclusively FreeBSD. Each Linux distro is based upon different assumptions and philosophies. This is something especially apparent to me when running Debian.
Under Slackware, everything used to be DIY. (I say used to be because my experience with Slackware was in the mid-to-late 90's). There was the base system, and there were a whole lot of packages. Package management was nonexistant beyond scripts that would maintain a list of files associated with each package. It was minimalist, but had very nice defaults, and a bare Slackware installation had a personality to it that I've not seen since.
When I later tried Redhat (5.something, I don't recall) I felt that it aimed a bit higher than Slackware in terms of program selection, but finding packages was sometimes difficult, and the defaults often had a less usable feel.
Under Debian, the common tasks one would ask of a distribution are automated. Upgrades between packages are generally seamless, and the work has been taken out of finding packages and satisfying dependencies. Defaults are generally functional, but sometimes have the if-you-want-more-configure-it-your-damned-self feel that I used to get from FreeBSD. Unlike what the author suggests, you aren't limited to using the "blessed" version of Apache, BIND, etc. with the operating system -- you can run their 'testing' distribution, but install Apache from the stable branch, and let the package management system know that you'd like to keep the version of Apache you're using, even if a newer version is available from the testing repository.
Which brings me to FreeBSD -- great documentation, decently nice operating system. Moving away from ReiserFS was painful, especially when creating a Squid cache, but the base system is very nice, and is designed to work together.
However, I felt that FreeBSD's commitment to easy upgrades stops where the ports collection begins. There was no easy way to upgrade a package -- it was "remove old, install new". I recall a minor version number difference in MySQL forcing a manual database reload, which is something that Debian's maintainers would have likely had happen automatically (following what I see as Debian's "automate the mundane" philosophy).
I also couldn't find an obvious way to choose something other than Sendmail, as it was part of the "base system". Debian's system may state that an MTA is required, but FreeBSD tries to force you into using a specific one.
I also recall an upgrade that changed a default setting in SSH, without making it obvious that it very well could break existing configurations and disable logins. Sure, the answer is "read
I suppose the point of this rambling is that each system has issues, and each system tries to make assumptions about the user's intent. While BSD may be "engineered", and supposedly all parts of the base system are meant to work together well, it also feels like BSD maintainers think that they have some divine right to tell you which MTA or DNS software to run. This is something that RedHat didn't try to pull in when I used it around 1999, and Debian definitely doesn't try to do today.
Somebody get that guy an ambulance!
Beyond all the hype and ego's about which OS is better, in reality there are benefits to both.
:p).
Linux, being the poster-child for the free-software idea, tends to have a lot more commercial vendor support. If I was a business looking to run Oracle on a free unix, I'd go with Linux. You can call Oracle and get support without the 'we don't support that configuration' comment. And if I were a gamer, I'd probably go with Linux for the better 3D video card support.
BSD, being a programmer at heart (if not by job at this point), has always seemed to me - looking at the code - to be far more cleanly designed and well though out. If you aren't a programmer, then bypass this comment.
People bash both sides, and comment on the 'eliteism' of BSD'ers. Now, personally, I use NetBSD for the most part at home.. from a management persepective, it maintains a consistency between my Sun's, Mac68K, PC, pmax, vax, and other machines. Yes, I have an E250 with Solaris, but it has an A1000 on it so I need the drivers. I have an Ultra-1 with Solaris to run my Aurora terminal server card (anonymous, I changed my hostID and have a license from my old job for the aurora control tower software). I have an HP735 running HPUX.
I've seen postings on Linux boards that were equally as nasty as ones I've seen on OpenBSD. I don't lurk on the FreeBSD lists much, so I can't comment. But I've *never* seen anything other than a calm/rational response to anything on the NetBSD lists. Perhaps its just me, but I find it very professional, even if its not the most popular OS in the world.
What pisses me off more than anything is the "my OS is the best" ranters. Y'know what, you can run whatever you want, go for it. I choose NetBSD because it meets my needs. I'm not saying its the best in the world, blah, blah, blah... I'm saying that it works. And if I have a problem and post a message up, I don't get bashed or RTFM'd (I usually have RTFM anyways), I get a decent intelligent reply. Thats far more valuable to me than having whats 'popular'.
I don't run games on unix (thats for my windoze box), so I don't need flashy 3D video cards, I just serve files (NFS & Samba), run a webserver, and write code (personal). And play. X runs fine, I have KDE but debating GNOME... no, I don't need you to tell me which is better, I'll play around with Gnome for a few weeks (used it before, but I'll give it another shot), and use my own mind to decide.
Its about choice. I like what I like, you can like what you like. Sure, you can speak your mind, but the price of freedom is that we need to respect differing viewpoints. Bigotry is bigotry, be it about race, religion, or your OS (debatedly another form of religion
ksh93 supports the ";&" syntax for case fallthroughs - it is this functionality that pdksh lacks. I added it as a feature request some time ago.
I've gone linux for the same reason I've shunned Solaris for the desktop: it doesn't have the tools and desktop diversions I need at work. I've run BSD and, at the time, it was a lot nicer and better than linux. When I need a production server it'll be Solaris. When I need a co-lo, it will be BSD. When I need a desktop, it's Slackware.
say in whole album there is maybe one great song. but bunch of singles makes best of the best compilation :-)
I find it interesting that the guy who trolls about the BSD license gets modded up, and the guy that calls him on his shit gets modded down.
And bad for me.
It is for these reasons that I think helping Microsoft is immoral. Hence, I reject the BSD license as immoral since it has been and will be easily used to benefit Microsoft.
I don't make the rules. I just make fun of them.
Take the Wikipedia asking for donations last week, half the posts here at slashdot were, "Why don't they go salvage a few old PIII 600's and cluster them together. Should only cost about two grand".
Sweeping statements like these do not help. You and I both know that you didn't measure and come up with "half".
Bottom line...the negativity needs to go out of OSS.
Why limit that to OSS? I think that "negativity" needs to go out of humanity.
Linux cannot have the banner, "Microsoft Sucks! and use us because...Microsoft Sucks!"
I think it's more true that this is what BSDers think Linux's banner is than it is true that this is what Linux's banner is.
OSS and Linux needs a banner of, "Hey our system works, has fewer viruses, easy to use, and it will do any thing Windows will do, except play games."
The many companies that use Linux have found their own reasons for using Linux. They don't need what you think Linux's banner should be.
And to the "any thing you can do, I can do for free" dot communist crowd:
And why do you call this "communist"? Explanations as to why Linux and GNU are not communist have occurred many, many times. Did you judge them invalid?
In order to make Linux viable, its going to need programs written for it like games, quickbooks, quicken, adobe products, that people are willing to spend money on and need before it will truely be accepted main stream.
And how will you determine that Linux will "truly be accepted main stream"? What does that even mean? If it happens to be equivalent to "having programins writen for it like games, quickbooks, qucken, and adobe products" then it has no additional meaning. Many companies and individuals are already using it despite it not being "truly accepted main stream".
I don't make the rules. I just make fun of them.
On the one had the BSD license is bad and the GPL far superior. I certainly don't want to give Microsoft a leg up, anywhere!
/slightjy/ differently.
On the other hand, I'm extremely glad Microsoft copied BSD networking code, rather than try to write their own.
Can you imagine it? It would be called TCP/IP, but it would be buggy as hell, and half of it would work just
But because they didn't ahve to spend time making their own, they didn't bother to make their own moderately incompatible with everything else. Thus interoperability reigns.
That's about the only good argument I've ever heard for the BSD license (as opposed to the GPL).
I want my Cowboyneal
This is just not true. Linux kernel was being kept in CVS for a long time, if not from the beginning.
I wonder how ignorant a sysadmin one needs to be to use Linux and not know about source RPMS. This guy's experience with Linux apparerntly isn't much more than a simple home install.
The number of Windows installations that will use SFU will be measured in the 1/10ths of a percent of the total Windows installation base. I really don't think it's a very good example of results being "good for everyone". It would have been better if SFU had been properly integrated into the Windows core, so that all Windows users received the benefits of secure connections and powerful scripting languages. But I cynically think that SFU is nothing more than a tickmark in their feature list so Microsoft can say: "Look! We do UNIX too, so why would you want to use that nasty Linux?".
This is a good point, and I don't have an answer. The alternative is to give them a BSD license and cross your fingers that they don't do as I describe in my previous post. I'm even less comfortable with that scenario! So there is no perfect solution here. Companies are anti-social and untrustworthy. If they can copy source code with impunity, they will. The GPL tries to force them into cooperation with copyright law. The BSD license ignores the problem. Some BSD people justify the apathy as being intentional. Other BSD people say "the companies will contribute! I know they will!" but I'm not convinced. I see more examples of companies using without contributing, than I see examples of cooperation.
One example of a company being gracious does not refute what I said. I'm not saying every company will purposefully fork the code into a closed derivative. I'm saying that the license permits a company to create a closed derivative. There's no disputing that point because it's one of the touted benefits of the BSD license!
What I then described was one possible outcome if the closed-fork becomes popular (ie, incompatibility, wasted effort, redundant work). And you and I both know what I described has already happened in the Real World(tm). I wasn't describing a theoretical possibility. I was describing in general terms the fact that closed derivatives have already occured. So please don't tell me that it's not true.
tightly bound to government enforcement (as practiced by those outside a hippie commune).
gewg_
But Linux is better.
Why then did RedHat CD-ROM install not work, whereas FreeBSD CD-ROM install DID work on a box. RedHat would install once FTP based install was done?
Why is it the GNU/Linux boxes fail under a load when FreeBSD slows up, but keeps running?
Why does the leading GNU/Linux fork ship with code that bombs on install when missing a file? FreeBSD's code issues an error, then lets you return to the install process.
Or is your use of the word 'better' like how Microsoft uses the word 'better' to describe thier software?
No, microsoft doesn't have an incompatible TCP/IP implementation because they don't hold a monopoly in networking infrastructure.
I've had much worse support from paid contracts and major vendors.
Someday I'll get around to trying this newfangled Linux thing out, but for now, the employer I'm looking at back home wants familiarity with BSD, and so my spare time is allocated.
Aside from what goes to the wife and kid, that is.
I've been reading the many comments of my fellow slashdotters about whether Linux or BSD is a superior OS. My personal feeling is that both of them have merit, as well as their own strengths and weaknesses. I just wanted to remind everyone that there was/is another alternative OS that was created before Linus Torvalds made the first linux kernel: OS/2. I have OS/2 Warp 4.0 on one of my boxen and it is really an impressive piece of work. I only wish that people would have switched to OS/2 warp instead of windows 95, because it is far superior. Anyways, just my two cents on the subject.
Here is the deal. It was a picture of a male stretching his sphincter. You wrote (or pasted) an eight paragraph essay defending a man stretching his asshole. The CIIA did the world a favor, IMHO.
I hate sigs.
Appearently you're rich!
I get turned off BSD (in spite of its more "secure" reputation) because I see any efforts amdcontributions I end up making to that system as a waste, since there's no one stopping M$ from apropriating my efforts. In fact, "Microsoft" services for linux is just that, as you saw in the /. story less than 24 hours ago.
I guess it depends on your mindset. If you are thing "us versus them", then yeah, you'll have a problem if competition is your goal. If you are thinking adoption, then you won't have a problem.
IE, lets assume you wanted standards-based HTML engines to be the du jour, to be adopted by everyone and anyone. Chances are you'd want to look at a BSD-based license, as it'll have a better chance of getting faster adoption. Hell, if MS would embed Moz instead of IE I'd be a happier camper.
BSD is dead, Linux too, use Windows Server 2003!
can be found here: here.
Unix-the-trademark is a trademark of The Open Group, and Unix-the-code is owned by SCO, so one can't actually say that the BSDs are really Unix (that's the sort of statement that triggered the USL/UCB lawsuit extravaganza, in fact).
No he doesn't. This means one of two things. /.ed.
1) He pulled the page because it was getting
2) His site got hit really bad, and Apache crapped out.
Either scenario is entirely possible.
I hate sigs.
it's dead Jim
...join us.... (in a really deep zomby voice)