FreeBSD 5.0 Developer Preview #2 343
noackjr writes "'The FreeBSD Project is proud to announce the availability of the second Developer Preview snapshot of FreeBSD 5.0 (5.0-DP2). This
snapshot, intended for widespread testing purposes, is the latest milestone towards the eventual release of FreeBSD 5.0-RELEASE, currently scheduled for mid-December 2002.' See the announcement, early adopter's guide, and the release notes."
Smp (Score:5, Interesting)
Someone explain this about BSD/Linux to me. (Score:3, Interesting)
So on to my question (with a possible coda). I read in a BSD guide that "most" apps written for Linux will run under any of the BSDs. Is this true, or was this dude just plain misinformed? Only reason is I ask this is that most of the info I've seen regarding the Unix variants is that BSD is superior over Linux. If that's the case, why use Linux? Anyway, if anyone can answer this 2 part question in a quick, general way, it would be appreciated.
Re:Someone explain this about BSD/Linux to me. (Score:5, Interesting)
As for which is superior, that's certaintly a matter of taste. My first Linux experience was with Slackware way back, and then RedHat starting with version 4 and then 5. Then I gave FreeBSD a try. I actually find it easier to get setup and in many ways more consistent in terms of design and organization (given at least beginner level *nix knowledge). It's really a matter of personal taste though.
Re:Someone explain this about BSD/Linux to me. (Score:3, Interesting)
Sorry if I sound like a troll (I'm just adding my two cents), but Gentoo seems to have the best of both the FreeBSD and GNU/Linux worlds. I get the increased app compatibility of GNU/Linux with a great ports system.
Re:Someone explain this about BSD/Linux to me. (Score:5, Interesting)
The only thing Gentoo's portage has over *BSD's ports is the better updating mechanism. Portupgrade under freebsd just blows chunks, and not just because yet another script interpreter (ruby) needs to be installed. It croaks a lot when dependancies somehow shift (because you compiled new versions of something). Which lieves you with the dreaded pkgdb -F which sometimes leaves you guessing. I think the FreeBSD ports system could learn something from the NetBSD port system which has a make update target.
But that's just my personal opinion on both systems. They are both nice, but the FreeBSD ports system comes out on top wrt flexibility.
Re:Someone explain this about BSD/Linux to me. (Score:5, Informative)
Funny, I have quite the opposite judgement. I'm a huge FreeBSD fan, am typing this on my FreeBSD laptop in fact, but it now dual-boots Gentoo. One of the big selling points of FreeBSD, for me, was the ports system -- RPM is just so much of a headache -- but that was until I met gentoo. It has really gotten rid of many of the headaches associated with FreeBSD's ports: in particular, if you have a port A installed, and then port B pulls in a newer version of port A, the old version can be uninstalled automatically and safely in Gentoo without touching any of the new files. (In fact Gentoo now does it automatically.) And that's just one aspect: I like the fact that gentoo portage supports multiple versions of ports, that it generates the CONTENTS file automatically, and if your favourite port hasn't been updated to the latest version, you can often trivially do it yourself (you can also do that in FreeBSD but it's more complicated to get the CONTENTS right, and if you don't it won't uninstall cleanly). Now that I've used Gentoo for some time, FreeBSD's ports system is clearly showing its rough edges and deficiencies.
So why am I sticking with FreeBSD? Because it performs better (especially under load), and a lot of things just work better -- eg, I occasionally have problems with ppp or dhcp/cable modem in linux, never in FreeBSD. But gentoo has huge potential, in fact it's already a pretty spiffy system, I think. If I had multiple machines, I'd install FreeBSD on the "mission critical" ones and gentoo on the "play" ones (bleeding-edge software, multimedia, etc).
portupgrade and convenience (Score:5, Informative)
Re:portupgrade and convenience (Score:2)
Re:Someone explain this about BSD/Linux to me. (Score:2, Insightful)
Yes, ports is older, and has some rough spots. Its also mature and has a good deal of stability. gentoo is infantile, and they are already having trouble keeping up with changes; Look at the massive number of updates each day in freebsd, via freshports [freshports.org]. Gentoo doesn't even come close, and they want to scale this up to something the size of the FreeBSD ports system with 4-5 times the number of applications? As for the rough spots, FreeBSD is adressing each of them, and in truely creative and powerful ways. They already checksum each file as it is installed (autogenerating the CONTENTS file), and refuse in the future to modify, delete, etc files that have been modified, therefore protecting you from customizations or packages that overwrote files). In my experience gentoo only handles A overwrites B in the specific case where it is told ahead of time by the port maintainer that this is true, and how to handle it. That's nice when you're at the size you are now; and FreeBSD could certainly do the same but it doesn't scale at the level FreeBSD operates on, and therefore they are coming up with new ways, automatic ways of handling it. I've also seen the gentoo system screw up royally and delete files its not supposed to because it didn't understand that something else had installed a package (or a different version of a package), and wind up trashing all the custom work the user did. This is very unlikely given the way the FreeBSD ports system works... by assuming if key files are there (regardless if the user chose to use package management) that the requirements are fulfilled. Then if the prereqs were installed through package management it will register the dependancies. This gives users and administrators the best of both worlds. Using ports when it gives them what they need, and letting the admin/user do it themselves when it doesn't. Give gentoo's limitations they really need this.
Re:Someone explain this about BSD/Linux to me. (Score:2)
Re:Someone explain this about BSD/Linux to me. (Score:4, Insightful)
For me as an old FreeBSD user, Slackware feels much much more "at home". Yes, Gentoo has ports (I prefer FreeBSD's though) but a big drawback is that, in contrast to FreeBSD, the whole base system is also made up of ports.
In FreeBSD the 'core' system is the same everywhere, not maintained by ports but having all source code in
Gentoo, with its web of port dependencies and infinite number of configurations, is unstable because of this. Also a small change often requires recompilation and reinstallation of 'everything'. Just read the Gentoo boards/mailing lists to see how often some configuration (combination of ports) breaks.
FreeBSD ports also break occasionally, but at least the don't affect the base system.
Apart from that, Slackware is like FreeBSD w.r.t. simplicity for file layouts, rc startup files etc. Gentoo feels more like other Linuces. This is a matter of taste and of what you're used to. I am convinced that most FreeBSD users prefer Slackware if they have to use a Linux distribution.
Re:Someone explain this about BSD/Linux to me. (Score:3, Informative)
I suggest you lok into the '-r' and '-R' options of portupgrade, it automatically handles the dependencies for you.
--Jon
http://www.witchspace.com
Re:Someone explain this about BSD/Linux to me. (Score:2)
Re:Someone explain this about BSD/Linux to me. (Score:2)
It's certainly more featureful out of the box, but Portage requires its own toolchain to manage, which defeats the purpose of ports in a few ways. Ports uses make, a familiar well-worn tool to most system administrators. That said, if I install Linux again, it'd probably be Gentoo.
Besides, BSD will run any linux app that doesn't have kernel dependencies (though most of
Re:Someone explain this about BSD/Linux to me. (Score:5, Informative)
I'm a FreeBSD user since three months, and I think FreeBSD is an excellent beginner's unix.
My unix adventures started with downloading Redhat and installing it. It took 30 minutes and I learned nothing. Then I sat there with a system that I had no idea how to configure to my taste. I disliked it and went back to Windows.
My next try was FreeBSD. Installing it took a couple of tries and it took at least a day or two before I was satisfied. But I learned a lot, mainly because of the excellent online documentation [freebsd.org]. Now I run FreeBSD on all my computers and I am not going back.
That being said, expect Linux to have better support for the latest and greatest hardware. (And expect Windows to have even better hardware support than Linux!) But I'm happy since the recent release of FreeBSD drivers for my NVidia card.
5000 ports?!? (Score:4, Funny)
Re:Someone explain this about BSD/Linux to me. (Score:5, Informative)
Linux is beginning to hit so big in corporate America that the software development effort to develop new applications and port existing applications to Linux is amazing.
This of course is just my opinion, but I would have to say that the development effort for Linux is outpacing that of the FreeBSD community.
I suppose the bottom line though is what works best for you? I would recommend that you take a look at both and decide for yourself which one works best for you.
Re:Someone explain this about BSD/Linux to me. (Score:5, Insightful)
Just because Linux is gaining share doesn't necessarily mean that BSD is losing. It does mean that UNIX is gaining though. :)
Re:Someone explain this about BSD/Linux to me. (Score:5, Insightful)
Don't forget that when you say development for linux is outpacing bsd what does that mean? The servers apps most people run has nothing to do with the OS. Samba, Bind, Netatalk, Squid, Apache, IP NAT+firewall etc, ssh, ftp, sendmail and variants of these programs--these are what most people run, and these have absolutely no connection to linux.
Re:Someone explain this about BSD/Linux to me. (Score:2, Troll)
Maybe at some ISPs. From of what I've seen at corporate environments, BSD is only used unwittingly in appliances. Linux is making some inroads against commercial Unix and Windows.
That's certainly the kind of view that would validate BSD. If you asked an IT director what important apps are running on his servers, he wouldn't mention any of those. He might mention PeopleSoft, SAP, Oracle, Oracle Financials, Microsoft Exchange, ClearCase, Siebel CRM. The programs you mentioned are more like minor supporting utilities - you choose a platform for SAP, and just assume that ftp is available for it.
A lot of this key software is becoming available for Linux. You might be able to get it to run on FreeBSD. But would you want to? Would you seriously put Oracle on a platform Oracle doesn't support? In fact, most companies are scared to move these key apps to Linux, even when the vendor supports it 100%.
So it's not accurate to say the server room is running bsd. Maybe at a few pure-internet companies, or running a little utility DNS/cache/whatever box, but not running the key apps in the corporate world.
Re:Someone explain this about BSD/Linux to me. (Score:5, Interesting)
If you had to look at all the linux servers running on the internet today (and discounting personal boxes) I would bet you the VAST majority are running none of those applications you mention. That's one of the reasons that MS and the commercial unixes still hold a sway--running those apps. You do raise a good point--oracle on FreeBSD (for example) is not a viable solution. But I'm not at all convinced that Linux is beating out the BSD's the way you think.
I would be REALLY curious to see how many linux and bsd boxes are running what you call a little "utility" box (and I'll throw in fileservers too). I would bet that that is the big domain of linux and bsd alike.
Re:Someone explain this about BSD/Linux to me. (Score:4, Interesting)
So I reckon that early adopters of FreeBSD would have had to struggle to persuade management that it was worth using, and that it wasn't a dead-end platform.
BTW, I use FreeBSD in all my servers at our small place of work (except where I have to use OS X server). Personally, I love it. But maybe that's because we *do* use all of the ftp/sendmail/apache stuff the above poster mentioned, and none of the crap the next one mentioned
* Someone correct me if I'm spouting BS.
Re:Someone explain this about BSD/Linux to me. (Score:2)
AFAIK, IPfilter is available for all the BSD and also Linux.
I'm not sure about sendmail..I'm certaintly not a sendmail expert, but what's special about the FreeBSD version of sendmail? I thought it was in synch with the real version (config file differences only imho). There is also a sendmail port.
Dunno about gnome, I'm all about KDE myself
I personally am looking forward to when I can upgrade to FreeBSD 5.0 for ACL support, though to be be honest it hasn't mattered for our company at all. (small company)
Re:Someone explain this about BSD/Linux to me. (Score:2)
Never had a problem configuring lists under STABLE. Exactly what functionality can't you get?
IP NAT+firewall tend to be very OS specific pf only available for OpenBSD at the moment (AFAIK) and ip tables are only available for Linux
Yeah, that's kinda like saying IPFW isn't available for Linux. It's a different methodology to a similar end.
FreeBSD has it's own version of Sendmail that is carefully tuned and fully integrated into the OS. If you are going to use sendmail instead of postfix qmail or exim this my be important.
I recently configured Postfix on a FreeBSD box. Took about 10 minutes following the compile to disable Sendmail entirely. There are dozens of tutorials that cover replacing Sendmail with either Postfix or QMail. In short, this is by no means a deciding factor as to which OS to use.
Gnome is much easier to upgrade with Debian. Many people resort to uninstall all of Gnome and all of it's libraries in order to do an upgrade of Gnome on FreeBSD.
That's just plain silly. Gnome is installed as a "meta" port. In other words, it calls out to the variety of other ports that make up the over all system. One can just as easily upgrade only those libraries that need it, while leaving the rest intact. The very same thing is true of KDE.
but if you need MACL you have to use Linux
Sorry, not familiar with the term MACL. What exactly are you referring to here?
Re:Someone explain this about BSD/Linux to me. (Score:5, Insightful)
Well, a new kernel every couple of weeks is fine if you're running Linux on a PC in your bedroom, but in the real world, it takes time to deploy software. It has to be tested, downtime scheduled, documentation updated, staff trained, etc. The big advantage of FreeBSD (and Debian for that matter) is that it gets much more thoroughly tested before it's declared "STABLE". Although it may lag behind the cutting edge a little, that's a far, far happier place to be if you are relying on your systems to run your business. Not only that, but there is one FreeBSD, maintained in a consistent way by a single organization. If you are writing or deploying software that requires certain versions of certain things to be in certain places, then you have to only support a subset of the possible Linux distributions, or choose something like FreeBSD which is far more consistent. FreeBSD does not need to make compromises for portability to other platforms (like NetBSD and Linux), it is wholly developed for x86.
In short, my position is that Linux is better if you want to experiment, FreeBSD is better if you want to run crucial applications or infrastructure.
Its all about intentions (Score:2)
BSD is more entrenched in the backrooms of corporate America for this reason.
Now on the DESKTOP i agree, it lagged behind until recently. But now that you can run 99% of proprietary Linux binaries, and there is good desktop hardware support, even that point becomes moot and it becomes more of a matter of preference then 'better'.
Re:Someone explain this about BSD/Linux to me. (Score:5, Informative)
A lot of other Open Source software are BSD styled. Others are GPL.
It's a matter of which philosophy you subscribe to.
Re:Someone explain this about BSD/Linux to me. (Score:5, Interesting)
99% of Linux executables can be run after a simple 'brandelf -t Linux executable', although I have found a couple of very sloppily coded sh scripts that ran on Linux and didn't work as-is on FreeBSD (most notibly the UT2003 install script mentioned above).
As someone who switched from Slackware to FreeBSD, I don't forsee ever moving to anything else. Not to disrespect Linux, but it is relatively a mess.
Someone else here described FreeBSD kernel as being a "borg cube", and that it is - in a structured and nicely organised way. And this philosophy extends to the entire distro.
If you're happy with Linux, fine - enjoy. You're only going to be able to run mostly the same software anyway. But I would recommend checking out FreeBSD if you're stuck with anything else.
Re:Someone explain this about BSD/Linux to me. (Score:4, Insightful)
2. It's a matter of personal choice to run one or the other on a desktop workstation. I run Linux because it's just more fun. Better 3D games support, newer drivers for everything and much more rapid development full of new ideas, little bits of GNU humor or cleverness all over the place and a lot of variety. It feels right. Of course, a lot of FreeBSD users would say that 3D gaming is for gamer weenies, newer drivers equal more unstable drivers, GNU humor and cleverness are really just lack of professionalism and variety is really the same thing as inconsistency. It's all a matter of personal taste if it's your personal system.
For non-personal systems, I'd say it's more a matter of whatever your vendor is pushing. In more and more cases these days, that will be Linux, but there are still some large firms that are outfitting people with *BSD.
Re:Someone explain this about BSD/Linux to me. (Score:2)
I can think of three reasons:
a) Linux hardware support is often better, and drivers appear more quickly
b) You may prefer a specific Linux package-management system, like apt, or gentoo's thingy
c) There are some applications that don't run, or need a lot of massaging to run under FreeBSD - used to be the case with CrossOver (might still be), and last time I checked Ximian didn't work
Re:Smp (Score:2)
I'm glad to see Sun Blade 100's supported, currently only linux(suse) would work on my blades. (with kde/gnome support even) I wonder if some tested these ports on sparc64 machines.
Re:Smp (Score:3, Informative)
Re:Smp (Score:4, Informative)
Yaaay team! (Score:5, Interesting)
Now that DP2 is here, I might as well jump in the CURRENT water again and give it a go again. The time that CURRENT _did_ work for me, it worked great and I considered it stable. I have been following/lurking the current@ mailinglist for quite a while, and it's been fun seeing al these cool new things appear.
Great work. I'm definately going to give this a spin.
Wait, I thought FreeBSD *was* dead?! (Score:2, Interesting)
I thought I remembered hearing some time ago about some politics within the FreeBSD camp or the FreeBSD trademark being sold or something of that nature that gave me the impression that development of FreeBSD would probably slowly grind to a halt, while the other *BSD's would become the new BSD banner-wavers.
Anyone want to clue me in on what exactly went on in the FreeBSD camp over the last year or so? Are they back on track and humming along as usual? Was anything ever wrong, or am I totally nuts?
Re:Wait, I thought FreeBSD *was* dead?! (Score:4, Informative)
As far as I know, the trademark is in no danger. FreeBSD has been going strong since 1993 and I don't see a letup in sight. If anything, with the release of the 5.X series, FreeBSD will be able to give alot of systems a good run for their money with all of the New Generation stuff going in (SMP, networking, disks, threads, etc, etc).
BWP
Re:Wait, I thought FreeBSD *was* dead?! (Score:5, Informative)
Interestingly enough, I have had the same subscription from 4.0 to 4.7, with the same address on the all the CDs. This despite four different companies running the subscription. Someday I need to drive over to Concord and see that address that's just as stable as the FreeBSD kernel...
Re:Wait, I thought FreeBSD *was* dead?! (Score:3, Funny)
Supported Applications (Score:2, Insightful)
Re:Supported Applications (Score:2, Informative)
Re:Supported Applications (Score:3, Informative)
Re:Supported Applications (Score:2, Interesting)
I mean, have they decided to concentrate on making the best server OS, period, they can make -- or have they decided to create a "one size fits all" OS that can be a pretty darn desktop *and* a pretty darn server OS?
Have they decided to make it a goal to make the project's output more "desktop friendly", like what has happened generally with Linux?
This is not a troll. I was using FreeBSD way back when as my "desktop" *nix until I needed something that was just available for Linux at the time and switched horses (around RH 5.0). At the time, the installers of the various Linux distros were not that different from 'BSD (ok, maybe except Debian, IIRC) and Linux was as much "desktop friendly" as 'BSD was. But things have changed (Caldera Open Linux 2.2 in '99, etc.) since. Even though I had a bit louch touch/contact with FreeBSD since my switch, I still had a soft spot for it. I've been wondering recently how they were considering The Desktop these days and if they made (substantial (sp?)) changes to their installer.
Anyone care to light up my lantern? Thanks.
The Perl Situation... (Score:4, Informative)
Just after compiling the perl port, do:
use.perl port <enter>
and you STABLE system will always use the perl from the ports. This will probably save you a headache or two when upgrading to CURRENT
Re:Supported Applications (Score:2)
Lots of information there, and access to pre-built KDE-CVS snapshots (that is, if they built correctly). They have a handy script that gets the latest built snapshot and installs it for you. Bless pkg_add(1)'s little heart. :)
Re:Supported Applications (Score:2)
Re:Supported Applications (Score:3, Insightful)
KDE and GNOME are third party software. You can find them in the ports system, along with 7000+ more third party packages. I would hate to see the size of the release notes if they had to document every change to every port and package!
p.s. Microsoft, GNU, and the Linux distributions have done an admirable job in obfuscating the definition of "operating system". Just because it comes with the OS does not make it a part of the OS.
Know what I'd love to see? (Score:5, Interesting)
I know BSD is a more thought of as a server OS, but I've heard plently of BSD users claim its makes a fine desktop as well. If that's every going to happen they definitely need to start working on making it more user friendly.
Re:Know what I'd love to see? (Score:5, Insightful)
It's an installer that doesn't get in your way. The partitioning/labelling is pretty easy (and has reasonable auto-defaults). And finishing up after (enabling ssh, nfs et al) is a doddle.
I don't see why FreeBSD needs graphical cruft in it's installer. The simple ncurses based one lets me install a fully working FreeBSD base system + ports tree in under 30 minutes. If I want something extra after that, pkg_add -r isn't far away.
I mean, come on... It's an installation, not something you have to work in for more than 8 hours. Yeah sure, GUI installers look nice, but what's the USE?
Re:Know what I'd love to see? (Score:2, Informative)
The history is here [freebsd.org], for further reading.
Re:Know what I'd love to see? (Score:2)
Thank you for this post. This clears up a LOT of confusion on my part as to why things were done the way they were.
Being that this thing was dated over 2 years ago, I don't suppose there's much point in holding our breath for libh's completion. *sigh*.
Re:Know what I'd love to see? (Score:3, Interesting)
No, it's not hard. It's not exactly intuitive either.
A decision was made to use sysinstall as both the installer, and post installation utility. In short, it's not really adequate for either.
It's not whether it's text based or GUI. The real problem is that it doesn't follow a linear path to complete the installation. Even after a number of installations it's not entirely obvious what step happens in which order. For a first timer at it, it is quite confusing.
What should happen is to have a step by step process that walks a user through the process without allowing for deviations. Aside from the GUI, this is what makes the Linux installers so much easier for someone who hasn't seen them before.
The one advantage to a GUI installer is to provide a little more screen space to describe exactly what is going on. Full descriptions of packages that can be installed, things like that.
Lastly, a GUI would provide a bit more professionalism to what the user perceives. Text based installers are just too closely associated with the 80's. It's harmful to FreeBSD's image essentially.
Re:Know what I'd love to see? (Score:2, Insightful)
It's not. FreeBSD is for computer geeks and IT professionals, not the ordinary fool that would fall for BillG's latest marketing troll. User friendly means the user gets to do what the user want in the way the user expects, and a GUI does not really help, since it might behave in unexpected ways on unexpected hardware.
I must admit I haven't done many installations by the latest and greatest GUI installers, but I tried both SuSE 6.3 and Progeny some time ago, and none of them worked on the specific hardware, so I had to use text mode installers. My point isn't that GUI's are inherently wrong for installing, but that an installer has to be robust.
The FreeBSD installer isn't very good, but it's not because it's text mode. Cramming the same thing into a GUI would suck even worse - the user wouldn't know where to click.
Re:Know what I'd love to see? (Score:2)
FreeBSD's partitioning and labeling system blows chunks. If you accept the defaults and you don't do anything interesting with the box, you'll get by. The default sizes for / and
And then there's the whole confusing issue of partitioning, labeling and which means what relative to a lot of other OS environments.
And while I'm on it, there's the crummy sysinstall tool for doing it to new disks added to a system, if you're not brave enough to deal with fdisk and disklabel from the command line (I figured 'em out once, as a forced exercise, and I was happy to be done with it).
I have no grip with sysinstall for getting a base system installed, but it'd be great if someone re-examined the disk partitioning schemes and tools.
Re:Know what I'd love to see? (Score:3, Insightful)
What's this animosity against text-mode installs? They work. What makes you think that the FreeBSD sysinstall scares away "lusers"? Because it hasn't got a crash-prone fluffy GUI which is a pain in the butt to recover from when it falls on it's ass?
FreeBSD's text mode installation is perfectly okay for that odd half an hour (depending on hardware and network speeds of course) of installing the base system.
Re:Know what I'd love to see? (Score:2, Interesting)
The first part is text-based my dear AC. I don't know how you made it to +2, Insightfull but an installation should be a one-time activity and whatever you say: GUI doesn't cut it, because frankly, if you give a Windows 2000 CD to your little sister she won't figure it out either.
Because for installing a computer correctly you need at least some basic computer knowledge. The other 99% you talk about get their computers installed by "us" (meaning, people who know what they do). It's normal... I don't start drilling in my teeth when I've got toothache, I go to a dentist: a specialist. There is no difference with computers.
Re:Know what I'd love to see? (Score:2, Interesting)
Well, somebody got up on the wrong side of bed this morning. If we can't act stupid on Slashdot, where can we :-)
I see this attitude a great deal on slashdot (and more elsewhere I suppose) that something cannot possibly be "user friendly" without being graphical.
Unless "user friendly" is defined as "conforms to the expectations of Windows users" I don't see this statement as being at all obvious. Being "Windows-like" is a possible design goal, but maybe not the top priority.
One can look at this debate from two sides:
Re:Know what I'd love to see? (Score:2)
FreeBSD is too good to keep away from the desktop. Heck, the MacPPC folks have OS X...why deny x86 computers this BSD-driven goodness? A FreeBSD-based graphical desktop will run acceptably on older machines (think walk, not crawl) and is a true speed daemon on fast machines. This has been a long time coming, but it is going to happen.
Re:Know what I'd love to see? (Score:4, Insightful)
What do you mean, "if that's ever going to happen"? It already has! It's my desktop system right now! It may not be the desktop system for your grandma, but then again, I'm not your grandma.
And FreeBSD *IS* user friendly. Do not mistake pretty pictures for usability. The FreeBSD installer is straight forward and sensible. The documentation is complete and thorough. Configuration is simple. The only drawback is that it expects you to educate yourself on system administration. But actually, that's a Good Thing(tm).
A Parable that applies... (Score:5, Funny)
Once in the land of Karjakistan, there was a great sultan who had no heir, his wisemen dispaired and decreed that the queen should be put to death that the king might marry another. In her desperation she called on the wisest guru of the land, Bobi-Son-Denobi (BSD), telling him he was her only hope. So BSD arrived at the palace and met Queen Needs-a-Leia and she told him of the problem:
"Oh BSD, you must help me, for my husband has not produced an heir for he will not take me into his bed!"
BSD was confused, what man would refuse a woman with such a large set of erm... kernals? So he searched for the answer high and low until he came to the master handler, Linux. Linux told him of a dark secret, how King Mesa Sofi (King MS) would sneak down into the animals cages and have wild escapades with the camels. BSD was shocked, the world knew MS was cursed but not so defiled, but still an heir needed to be produced, so he went back to the Queen and asked her to disrobe (hey, she did it for Jaba, right?). He gazed at her nubile figure, which seemed as if it were petrified, like Natalie Portman.
The answer was as obvious as steaming hot grits, of course he thought! I HAS THE SOLUTION!
And so BSD appeared before King MS, with Linux and the two approached the throne. "Your monopoliness," BSD began, "If you will view the naked body of your wife."
Need-a-Leia disrobed again her nude form shining forth, "You will notice her... um TCP/IP socket... looks a bit like the toe of a beast of burdan, a camel's toe if you will."
The King looked on and was pleased, and so the Queen bore him a son and was spared, BSD and Linux had saved the day.
The moral of the story is, Microsoft is a bunch of sick bastards who need to listen to open source and stop fucking livestock.
Re:A Parable that applies... (Score:2)
will OS X be updated with this? (Score:5, Interesting)
Probably too soon for 10.3 to be based on this, but maybe 10.4?
Re:will OS X be updated with this? (Score:4, Informative)
Re:will OS X be updated with this? (Score:2)
Java? (Score:2, Interesting)
FreeBSD Sells Itself (Score:4, Interesting)
Just ask ... yahoo ... netcraft ... and slew of other servers that rely on BSD. If you want a server and you want the best bang for the buck, freebsd is the best price out there. (free)
For all the trolls who say BSD isn't GPL, well duh, BSD is in itself a license. Sometimes you just gotta wonder. If linux was so wonderful then why would apple choose BSD for OS X and not linux? It's more than just the license, BSD is a very nice OS that is wonderfully stable.
Rule of Thumb, if it works in linux it will more than likely work in freebsd, and vice versa, well that is until you try to compile a kernel not of that OS :-) ... try it before you bash it.
Don't fret about the BSD dying trolls... (Score:3, Interesting)
I use BSD everywhere. I sneak it into places where I work and impress the locals with it. And then it ends up in the server room. FreeBSD world domination! muhahahaha
Oh, and I never got fired for installing BSD somewhere :)
Re:FreeBSD Sells Itself (Score:2)
Because for the most part, the GPL ensures the code stays truly free and out in the open, something Apple didn't want to have to worry about for parts of their OS. It's not because BSD is somehow more advanced or better than linux. Mach sure as hell doesn't hold a candle to the linux kernel if that's what you were implying. And finally, it MIGHT just have something to do with Next which was based on BSD, which OSX is based on.
Honestly you troll and then ask people not to bash it, what gives?
Re:FreeBSD Sells Itself (Score:2)
BTW, Apple (and NeXT before) does use and modify GPL code (GCC, for example), and they don't seem to have a problem with playing after the GPL rules, so maybe the license wasn't the only reason for not choosing Linux after all.
Re:FreeBSD Sells Itself (Score:4, Informative)
Umm, they didn't. Choose, that is. The decision was made by NeXT, years before, after Jobs had left Apple and started hanging out with Avi Tenevian (sp?). NeXT chose BSD over Mach, which was state-of-the-art for Unix at the time, and is still very good (I personally am ambivalent on the subject of microkernels, but some people have very strong feelings about them).
Apple's next-generation OS (Copland, Pink, whatever) was in fairly dire straits, they had been working on it for years and had gotten precisely nowhere. So Apple bought NeXT, but NeXT people wound up in charge, and they made the decision that MacOS X would be the next (no pun intended) iteration of the NeXT OS.
Even without this, Apple would never have chosen Linux - if they had to release their modifications to it under the GPL, people would just have run it on cheaper PCs, and Apple make almost all their money on hardware. The BSD license allowed them to compromise.
Re:FreeBSD Sells Itself (Score:2)
Yes, MkLinux, which was Linux on top of the Mach microkernel. But it was never intended to be a commercial product, more a laboratory for Apple engineers to familiarize themselves with Mach.
10 things you might want to check out in DP2 (Score:5, Informative)
1) Filesystem Snapshots/Background fsck - On filesystems with softupdates enabled, fsck will be performed on the mounted filesystem (well, actually a snapshot) after the disk is mounted. This allows fsck to be run without affecting uptime along with the other obvious benefits of having snapshot support (dump comes to mind).
2) ACLs - Filesystem ACLs are included with FreeBSD now and can be set using the standard setfacl/getfacl methods
3) LOMAC - The LOMAC with DP2 is apparently old and seems intrusive. A recommendation from the author was to try the version of LOMAC from trustedbsd CVS. It is said to contain "99% less ASS"
4) MAC - I personally haven't tried it yet, however I plan to. Recommended you use UFS2 for full extended attribute support. This could/should rock
5) GEOM - A modular framework for disk I/O. This allows modules to be placed along the I/O request path in order to do nifty things such as filesystem encryption easily. There is an encryption module already written for this as well
6) UFS2 - UFS with extended attributes support and various code cleanup afaik. sysinstall will use UFS1 by default
7) SMPng - Have at it.. Last I heard, the speed increases weren't as significant as people seem to think they'll be. The groundwork is laid out though for future speed improvements. A lot of code has been moved out from under Giant (Big Giant Lock). That could have definitely changed though, as the last time I heard an SMPng update was at the kernel summit in SF. There are quite a few debugging options enabled in GENERIC, so you might want to take note of that.
8) sparc64/Itan{ic|ium} - If you have a supported hardware config.. Itanium is under
9) gcc3 - Nothing more to really put here.
10) New and improved rc system in
# PROVIDE: sshd
# REQUIRE: LOGIN
# KEYWORD: FreeBSD NetBSD
Ports, unfortunately, does not use this dependency system yet. However, last I heard, there will be a cutoff date at which time they should support it.
Some information may be outdated, but most of it should be correct.
Enjoy,
-JD-
Re:10 things you might want to check out in DP2 (Score:3, Informative)
perl out of base system (Score:3, Interesting)
Now if they could only do the same for Sendmail, BIND, and other junk.
Maybe I'm just more comfortable with systems like Red Hat where *everything* is in a package, but it seems silly to have this 3rd-party stuff in the base, especially if many people use the ports version anyway.
Re:perl out of base system (Score:2, Informative)
Re:perl out of base system (Score:3, Informative)
Compared to Debian? (Score:2, Interesting)
Re:Compared to Debian? (Score:3, Informative)
Kernel Threads! (Score:5, Interesting)
SMP Cooling HLT's (Score:2)
Thanks
Re:dead? (Score:2, Informative)
(note to troll: the story about FreeBSD's latest release is hardly the place to try the ol' 'BSD is dying' ploy)
Re:Why not Linux? (Score:5, Funny)
1.Ports
2.Packages
3.easy update (make buildworld etc..)
4.The Devil not that fat fucking penguin
MySQL on FreeBSD (Score:5, Informative)
Re:MySQL on FreeBSD (Score:2, Informative)
I read some more blog articles on that site, and it seems that he did find a solution to the FreeBSD/LinuxThreads problem; see this [zawodny.com] link.
Re:MySQL on FreeBSD (Score:2)
As the previous poster said, hopefully 5.0 will help.
Re:Gentoo gentoo gentoo (Score:5, Interesting)
On to easy updates... A whole bunch of tarballs with patchfiles works for a ports system, but not the base system. FreeBSD keeps the entire base system in CVS. FreeBSD actually has a base system. FreeBSD has multiple branches of development. Maybe gentoo will mature to the point where they make a real base system and do real release engineering, but it currently isnt the OS of choice for me.
Also, because the development cycle of FreeBSD is significantly more sane than that of the Linux kernel and the base system/toolchain which never has and never will exist in one master repository, nVidia's drivers work on the -CURRENT development branch of FreeBSD from which this developers preview was taken. Change one line in one file, and they build flawlessly (or at least they can, hopefully on this developer's preview too). The drivers even register properly with devfs.
Do yourself a favor and try FreeBSD, then you can check the FreeBSD mailling list archive if something is broken, instead of searching for a fix with google. It'll save you hours.
Re:Gentoo gentoo gentoo (Score:3, Informative)
Re:No obligation to use the fat penguin (Score:2)
Re:Why not Linux? (Score:5, Insightful)
Re:Why not Linux? (Score:2)
Re:Why not Linux? (Score:2, Insightful)
I'm not saying freebsd isn't a fast OS, but it can't do the impossible. Yes I realise you're exaggerating to an extent, but you're over exaggerating here.
Lets see some benchmarks too.
FreeBSD vs Linux (Score:5, Informative)
When my company was just starting out in late 1998, we deployed Linux for our custom S.E.D.D solution. It worked reasonably, aside from the occassional ext2 filesystem crash or kernel panic, which wasn't a big deal then since we had redundancy and weren't under heavy load. Unfortunately, when the load started increasing, so did the crashes and panics. The systems needed to be reinstalled every week. After messing around trying to get the 2.3.x series of kernels to work, I eventually had a cutting edge test server to see if the latest Linux offering could match up. It didn't.
I read about FreeBSD and downloaded the 3.2-RELEASE version. Since then I've tracked both STABLE and CURRENT, and I can say with conviction that any FreeBSD system is more stable, can take higher load, and is far easier to configure for hard-core use than is any Linux dsitribution, in my experience. The FreeBSD servers slowed (but even then, not as much as the Linux servers had), but didn't crash, even when far higher load was placed on them than was placed on the Linux servers we used to run. As a S.E.D.D company, we send millions of secure documents out per day, and also thousands at once. Since this IS Slashdot, and people here are Linux fanatics, I am not logged in with my username or password, since (a) I don't want to lose all of my karma and (b) I don't want childish Linuxbrats sending flames to me.
Linux may be ok for some, but for people who are trying to run their own companies, still have some sort of life, have other hobbies, like horse riding, and have girlfriends, Linux is not the ideal solution.
Close, but... (Score:5, Informative)
Of course, for controlled quantities like vendor-supplied hardware, all three can be very stable, though I'd still suggest that FreeBSD and Linux are at least an order of magnitude more stable than Windows.
And just to inject some of my own anecodtal evidence, on a volunteer basis I administrate several SMP x86 file and Web servers for NGO's/NPO's that 1) run Slackware Linux, 2) have uptimes >700 days and 3) have significant load a good percentage of the time with load spikes at times that can reach into the stratosphere.
Re:*BSD is dying (Score:5, Interesting)
http://uptime.netcraft.com/up/graph/?mode_u=on&
Zeus.com, makers of Zeus a powerful http server, use openbsd:
http://uptime.netcraft.com/up/graph/?mode_u=on&
To add to OpenBSD's clout, they have had 1 remote hole in 6 years, and are well known for their attention to security. NetBSD is still young but it is picking up speed, with ports to more hardware platforms than any other operating system. The Sparc64 port for FreeBSD is getting closer to production quality, too. Try joining their mailing list, there are many active users for sparc64. Try any of the BSD mailing lists, they are certainly not dead. And, might I add, FreeBSD was just given NVidia drivers.
Some one mod that moron a troll.
I'm going to dl FreeBSD 5.0-DP2 right now. I've already tried DP1 with much pleasure. Give it a try people, you won't be disappointed!
Re:*BSD is dying (Score:5, Informative)
Re:*BSD is dying (Score:3, Informative)
To then go and say NetBSD is still young, having mentioned OpenBSD (which forked from it after some drama) just makes you look uninformed, and kind of scuttles any credibility. Mod parent down.
Re:Oh please (Score:2, Insightful)
Yet here you are, sampling the koolaid like the sap you are, putting the kidies in their place like some kind of venerable rutting stag who is pissed that the younger ones get all the young females and you're left with the withered old ones that can't escape your feeble approach.
Maybe you should hang out on some windows support board where you can talk about how every worthwhile program ever made can be run under DOS ??
Re:Native jdk 1.4 hopefully (Score:3, Interesting)
Re:Wait a second... (Score:2)
Re:Wait a second... (Score:3, Informative)
The "standard" NetBSD iso image contains everything you need to install for a basic desktop machine. It includes compilers, X Window system, etc. What it doesn't include is third party stuff like KDE, GNOME or Apache. That can be installed from the packages collection (akin to the FreeBSD ports collection, only a port is a different architecture in NetBSD terminology). If you can't or wont install packages from the FTP sites, then there are supplemental iso images for the i386 architecture that contain a massive amount of precompiled packages.
Chris
Re:Installer (Score:2)