Slashdot Mirror


In Favor of FreeBSD On the Desktop

snydeq writes "Deep End's Paul Venezia wonders why more folks aren't using FreeBSD on the desktop. 'There used to be a saying — at least I've said it many times — that my workstations run Linux, my servers run FreeBSD. Sure, it's quicker to build a Linux box, do a "yum install x y z" and toss it out into the wild as a fully functional server, but the extra time required to really get a FreeBSD box tuned will come back in spades through performance and stability metrics. You'll get more out of the hardware, be that virtual or physical, than you will on a generic Linux binary installation.'"

487 comments

  1. Shouldn't Apples count? by elrous0 · · Score: 1, Insightful

    I'm sure I'm opening myself up for an onslaught here, but I thought all their OSX-based stuff was basically just a very elaborate FreeBSD distro. And you get the benefit of one of the best GUI's in the desktop world, to boot.

    --
    SJW: Someone who has run out of real oppression, and has to fake it.
    1. Re:Shouldn't Apples count? by sirdude · · Score: 3, Funny

      Seeing as to how you haven't RTFA, you deserve to be on-slaughtered :)

    2. Re:Shouldn't Apples count? by elrous0 · · Score: 4, Funny

      Sir, this is /. I have NEVER read an article.

      --
      SJW: Someone who has run out of real oppression, and has to fake it.
    3. Re:Shouldn't Apples count? by Threni · · Score: 2, Funny

      Damn - you're right. I wondered what all that text was above the comments. I assumed it was an ad, or a Terminal session or something....

    4. Re:Shouldn't Apples count? by Anonymous Coward · · Score: 0

      No. But you could just call them all Unix.

      Similar to the author, I run OSX on my desktops and BSD on my servers. OSX is too many steps removed from all of the other distros to rightly call it BSD and that its kernel is based on bits from some of them isn't a strong enough tie. Certainly a derivative though.

    5. Re:Shouldn't Apples count? by Anonymous Coward · · Score: 2, Funny

      And you get the benefit of one of the best GUI's in the desktop world, to boot.

      The desktop looks like AOL's client software from the late 90's. Best GUI is debatable.

    6. Re:Shouldn't Apples count? by Nursie · · Score: 2

      Yeah.... not quite.

      There are BSD user-space tools. The kernel is a combination of the BSD kernel, Mach and various other bits.

      It's BSD-flavoured, but it's not BSD. Look up Darwin for more info.

    7. Re:Shouldn't Apples count? by Bill,+Shooter+of+Bul · · Score: 1

      No, It shouldn't. If they had a freeBSD kernel, then yes. They have a Mach microkernel based one with elements of FreeBSD 4 something ( Free BSD is currently on 8.2 going on 9 soon). Yes, the common BSD tools and environment are there, but not used in anyway by the fancy Gui. And try upgrading or replacing those. DarwinPorts and Fink both elect to create separate repositories of the same tools. Just as you can call OpenBSD OpenBSD instead of NetBSD, OSX is Sufficiently diverged from FreeBSD to be something completely different: OSX

      --
      Well.. maybe. Or Maybe not. But Definitely not sort of.
    8. Re:Shouldn't Apples count? by peppepz · · Score: 1

      I think OSX is a very elaborate NeXTSTEP, not FreeBSD, installation.

    9. Re:Shouldn't Apples count? by Anonymous Coward · · Score: 0

      Mac OS X uses >some FreeBSD userland tools and services (like IP stack, firewall, etc), but it is by no means a FreeBSD distro.
      The Darwin Kernel is based on XNU and only partly on the FreeBSD kernel. The Cocoa application framework is completely proprietary, as is the GUI.

      OS X is basically a massively enhanced version of NeXTStep.

    10. Re:Shouldn't Apples count? by jiteo · · Score: 1

      And you get the benefit of one of the best GUI's in the desktop world

      No.

    11. Re:Shouldn't Apples count? by Sarten-X · · Score: 3, Informative

      TFA only makes a passing mention of OS X, and doesn't acknowledge its presence on servers at all. TFA is really little more than an advertisement for FreeBSD over Linux, saying "Look! It's more stable and has better features!" while completely missing the point that Linux is stable enough for use and also has ample useful features of its own.

      Linux is used more than BSD because there are more available distros, meeting diverse needs without any configuration necessary. Professional support is more readily available, and in my limited experience, even hardware support is somewhat better.

      Personally, I think Apple servers don't have much market share because they're so damned expensive, and there's not much in the way of specialization.

      --
      You do not have a moral or legal right to do absolutely anything you want.
    12. Re:Shouldn't Apples count? by ByOhTek · · Score: 2

      MacOS X is a skyscraper in the same way a house is a skyscraper. Yes, they use some of the same parts, and use similar (sometimes the same) stuff for similar functionality, but the similarities end there.

      MacOS (or as I call it) Frankenstein's OS, is a hodgepodge of at least three distinct operating systems, plus Apples own work.
      Unlike Frankenstein's monster, however, Frankenstein's OS, doesn't lurch around, it's actually rather good and functional, especially after the X.2 or X.3 update when they put threading into the kernel.

      As for the best GUI... that is a matter of opinion, which I disagree with. The GUI is way to distracting and lacks certain pieces of functionality, customisability and accessibility that I would prefer.

      Windows 2K ~= KDE > XP > XFCE > Window Maker > Gnome > Vista/7 > Any version of OSX > TWM

      at least, IMO.
      Yes, there's no real one trend in that list, each one is a combination of things that works for me.

      --
      Self proclaimed typo king, and inventor of the bear destroying coffee table (patent not pending).
    13. Re:Shouldn't Apples count? by Yvan256 · · Score: 3, Funny

      Wait, since when does Slashdot link to articles?

    14. Re:Shouldn't Apples count? by Anonymous Coward · · Score: 0

      No, it's not the microkernel; it's the CMU Mach monolithic kernel.

      At one time I believed that Digital's first releases of OSF/1 on AXP (1.x) used microkernels but in a cursory search of the intarwebs I can find nothing to support that recollection.

    15. Re:Shouldn't Apples count? by TheRaven64 · · Score: 5, Interesting

      I read TFA when it was on OSNews, and it's a waste of space. I was expecting some actual points, but it seemed to boil down to 'I haven't rebooted this machine for three years! FreeBSD is therefore awesome!' When someone talks about uptime, it's a clear sign that they are an idiot: uptime is irrelevant, downtime is important. You can achieve good uptime by failing to install security updates, but it's far better to spend a minute rebooting than to spend a day cleaning up and reinstalling after a machine is compromised.

      I have these reasons for using FreeBSD on the desktop:

      I don't want to have to spend ages configuring stuff, or learning how to configure stuff. With FreeBSD, the stuff I learned ten years ago is still relevant. I only need to learn new things when there is new functionality. Contrast this with Linux where userspace tools change more often than Paris fashions. Just as you've learned one, it's deprecated, and then replaced by something else.

      APIs are well designed and stable. A couple of years ago, I wrote some code for getting the battery status on a variety of platforms. On NetBSD, OpenBSD, and FreeBSD it was a few sysctls and worked on every architecture. On Linux, the interfaces were subtly different on every architecture, but there was a 300KB library that abstracted this for you. The code to invoke this library was more complex than the entire *BSD implementations combined.

      Sound Just Works. FreeBSD has low-latency sound mixing in the kernel and has a really amazing implementation of the OSS 4 APIs. Multiple applications can just open /dev/dsp, issue a couple of ioctls() to select the sample rate and so on, and away it goes. I installed FreeBSD on a NAS / Media Center box a few weeks ago. 5.1 sound output in VLC just worked[1], and I can ssh into the machine and run another music player with the display exported to my laptop without needing to close the VLC that has the sound device open to play audio from DVDs, or configure some userspace sound daemon. The kernel just does what a kernel is supposed to do: abstract the details of the underlying system (including the fact that multiple unrelated processes are running) from userspace apps. This was what made me switch from Linux to FreeBSD in the 4.x days - multiple apps playing sound at once was easy. Apparently, three sound daemons later, it's almost easy in Linux, in a hacky kind of way, as long as PulseAudio doesn't hate you as much as it apparently hates most people...

      ZFS. Seriously, if you haven't used it then you don't know how awesome it is. Creating new filesystems is as easy as creating new directories. Transparent compression, deduplication, and free snapshots are amazing. Even better is the integration with the ezjail tool, which clones a base system install and creates a jail. This is great if you want to run some untrusted code, or just set up a test environment - it takes a few seconds to create a new, isolated environment where you can test things, break things, and then destroy it when you're done. I've only used it on the most recent FreeBSD machine I've installed, and after a day I started missing it on systems where I wasn't using it. There are some places where it could be better integrated, for example apt-clone on Nexenta took a snapshot, installed a bunch of packages, and then reverted the filesystem if any of them failed - I don't know of any FreeBSD equivalent yet, but hopefully pkg-ng will introduce one.

      Capsicum. The first security framework I've seen that is actually well designed. It's in -CURRENT, not sure if it will make it into 9.0, but should into 9.1 if it doesn't. Most of the standard userland tools are being modified to use it, and things like Chromium have already had Capsicum integrated - a tiny diff to do fine-grained sandboxing. An increasing number of ports are getting Capsicum support too, so expect to see your favourite desktop applications start to run with the absolute minimum required privilege soon.

      [1] I spent a couple of hours looking for documentation on how to configure it. Then I decided to actually test it, found that it worked already, and felt quite silly.

      --
      I am TheRaven on Soylent News
    16. Re:Shouldn't Apples count? by Anonymous Coward · · Score: 1

      But, at the very least, you got first post; your name is out there, and you didn't have to say frost piss, or frist post, or whatever. You've posted something just as useless, but achieved your goal of getting your name out there, once again.

      You are the greatest. All hail the mighty elrous0, king of useless fisty pasts.

    17. Re:Shouldn't Apples count? by Anonymous Coward · · Score: 0

      TIL nextstep spawned Openstep which is what Mac OSx is based on.

      http://en.wikipedia.org/wiki/NeXTSTEP

    18. Re:Shouldn't Apples count? by TheRaven64 · · Score: 2

      OS X is the only one you can call UNIX. The others are UNIX-like or UNIX-derived (in the BSD case). To be called UNIX (a trademark owned by The Open Group), you must be certified as implementing the whole of the Single UNIX Specification.

      --
      I am TheRaven on Soylent News
    19. Re:Shouldn't Apples count? by goarilla · · Score: 1

      Well I do think so, it's also pretty consistent in my opinion.
      What really annoys me is the mixed BSD/GNU userland though.

    20. Re:Shouldn't Apples count? by wrencherd · · Score: 2

      With MacPorts, OSX is like FreeBSD, but frankly there's nothing like the real thing.

      I often get modded down for posting this (probably partly b/c I post it too often), but . . .

      Apple's hardware is tops, but OSX is a lesser-BSD and it would be the best of all possible worlds if a user could replace it (easily and completely) with a real one (FreeBSD, PC-BSD, or Desktop BSD).

    21. Re:Shouldn't Apples count? by fuzzyfuzzyfungus · · Score: 4, Informative

      The fact that Apple has largely abandoned the server market, and is the only source of hardware on which OSX is blessed to run probably doesn't help.

      Yeah, you can get the "Mac Pro Server"(Oh Boy! you can by a rack shelf and then put two of them on it, for up to 4 whole sockets in 12Us! The bitchin' Radeon HD 5770(whose mini displayport and DVI outputs aren't compatible with my KVM gear) totally takes my mind off the fact that xserves would have done 24 sockets in the same space. Dual PSUs aren't an option; but does your shitbox dell server have bluetooth or S/P-DIF audio? Thought not...) or a "Mac Mini Server"(a server that supports up to 8GB of RAM, fuck yeah! Wait, you mean that "apple remote control" is the name of an attractive IR remote, not a LoM card? Shit, no wonder is seemed so cheap.)

      For many people's desktop requirements, the fact that Apple refuses to make a sucky-but-wildly-inexpensive tower isn't actually a huge deal. The server market is a whole lot less forgiving of deviations from reasonable form factors and common redundancy and management features...

    22. Re:Shouldn't Apples count? by onefriedrice · · Score: 1

      MacOS X is a skyscraper in the same way a house is a skyscraper.

      Perhaps you haven't had your coffee yet.

      --
      This author takes full ownership and responsibility for the unpopular opinions outlined above.
    23. Re:Shouldn't Apples count? by Anonymous Coward · · Score: 0

      Darwin is a BSD distro every bit as much as FreeBSD is... it's not like the kernel was never replaced before.

    24. Re:Shouldn't Apples count? by Bill,+Shooter+of+Bul · · Score: 1

      No, actually Unix certification only applies to OsX 10.5 (leopard) and OsX 10.6 (snow leopard). The certification applies to each version of an operating system. http://www.opengroup.org/csq/public/search.mhtml?t=&w=apple&sort=bycomponent&display=short&pid=2958 So you cannot call OsX 10.7 (Lion ) Unix. At least not yet.

      --
      Well.. maybe. Or Maybe not. But Definitely not sort of.
    25. Re:Shouldn't Apples count? by EsbenMoseHansen · · Score: 1

      A few points:

      The locking of /dev/dsp is mostly ancient history at this point, even on Linux, where sound (finally) got the attention it needs. And now it actually handles multiple sounds cards (moving the sound around and stuff like that), which is nice if you are using an usb-headset and speakers, depending on the situation.

      I use schroot for the usecase you use ezjail for, and from your short note it looks mostly equivalent. I tend to use either a btrfs or lvm backend.

      As for creating new filesystems, I find that mostly a bother; what I want is just one filesystem to handle it all. Currently, I find I need 2 to handle my needs, which is annoying (one encrypted, one not). Snapshots are useful though (and supported by LVM and btrfs).

      --
      Religion is regarded by the common people as true, by the wise as false, and by rulers as useful.
    26. Re:Shouldn't Apples count? by tomhudson · · Score: 2, Insightful

      BSD was unix before the open group ever existed. Any sane person would consider it "grandfathered in."

    27. Re:Shouldn't Apples count? by Anonymous Coward · · Score: 0

      A BSD distro never consists of only the kernel.
      No, Darwin is NOT a BSD distro, as Darwin is neither BSD nor a complete OS.

    28. Re:Shouldn't Apples count? by cashman73 · · Score: 1

      Windows 2K ~= KDE > XP > XFCE > Window Maker > Gnome > Vista/7 > Any version of OSX > TWM

      Or your meds. Seriously, you put OS X behind Windows Vista?!?! Really?

    29. Re:Shouldn't Apples count? by ByOhTek · · Score: 1

      Would you have preferred a car analogy?

      --
      Self proclaimed typo king, and inventor of the bear destroying coffee table (patent not pending).
    30. Re:Shouldn't Apples count? by TheRaven64 · · Score: 5, Informative

      No, BSD was UNIX when it contained AT&T UNIX code and AT&T owned the trademark. After the UCB vs AT&T lawsuit, BSD removed the last remaining traces of UNIX code and was not UNIX.

      --
      I am TheRaven on Soylent News
    31. Re:Shouldn't Apples count? by Canazza · · Score: 1

      He also Equated Vista and 7 despite them being as different from each other as Vista was from XP.

      --
      It pays to be obvious, especially if you have a reputation for being subtle.
    32. Re:Shouldn't Apples count? by Anonymous Coward · · Score: 0

      Depends on what you mean by "complete OS." Are you aware of how little the first Linux distros included? Less than Darwin.

    33. Re:Shouldn't Apples count? by DarwinSurvivor · · Score: 1

      Hey, he put XP ahead of XFCE... Seriously, XP didn't even have proper multiple-desktop support! (powertools sucked btw).

    34. Re:Shouldn't Apples count? by wagnerrp · · Score: 3, Interesting

      I use schroot for the usecase you use ezjail for, and from your short note it looks mostly equivalent. I tend to use either a btrfs or lvm backend.

      Chroot is just filesystem isolation. It was never intended for security purposes, and can be trivially breached. Jails provide real OS and memory isolation, dedicated addresses, and even dedicated network devices and stacks. It's more analogous to Solaris Containers and Linux LXC.

      Having an integrated filesystem and volume manager affords certain capabilities that LVM cannot do. Without looking deeply at the implemented capabilities, BtrFS should be comparable to ZFS. The reason for multiple filesystems is to allow independent management of each. One with primarily text files could have compression enabled. One with important data could specify multiple duplicates, which makes sure those files are stored on multiple zvols in case one fails. If nothing else, it allows you to maintain independent snapshot strategies for different directories.

    35. Re:Shouldn't Apples count? by toadlife · · Score: 1

      Linux is stable enough for use and also has ample useful features of its own.

      You've just stumbled upon the reason why companies choose Windows over Linux.

      --
      I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
    36. Re:Shouldn't Apples count? by A12m0v · · Score: 1

      How does FreeBSD compare to Darwin? How much did Darwin divert from FreeBSD? A lot of technologies in OS X like GCD have been ported to FreeBSD and vice versa.

      --
      GENERATION 25: The first time you see this, copy it into your sig on any forum and add 1 to the generation.
    37. Re:Shouldn't Apples count? by Gilmoure · · Score: 1

      *golf clap*

      --
      I drank what? -- Socrates
    38. Re:Shouldn't Apples count? by Guspaz · · Score: 3, Interesting

      ZFS. Seriously, if you haven't used it then you [...]

      The problem is that FreeBSD's implementation of ZFS in stable builds is extremely out of date. FreeBSD currently supports ZFS v15 (current closed-source is v33), which means you're missing a lot of the features. No triple-parity RAID, no deduplication, no encryption, no snapshot diffs, etc.

      The good news is that FreeBSD 9.0 will bring this up to v28, the version used in the last release of OpenSolaris. My home file server is running OpenSolaris with a ZFS v28 storage pool, and I'm planning on trying to migrate to FreeBSD 9.0 as soon as it's out (RC2 should be out any day now, so close...)

      Of course, the downside to all this is that ZFS is now effectively closed-source, and I'm not sure if we'll ever get anything newer than v28, unless it forks...

    39. Re:Shouldn't Apples count? by Kjella · · Score: 1

      For many people's desktop requirements, the fact that Apple refuses to make a sucky-but-wildly-inexpensive tower isn't actually a huge deal. The server market is a whole lot less forgiving of deviations from reasonable form factors and common redundancy and management features...

      Actually for people's desktop requirements I think they are, but most people now use laptops and the MacBook, MacBook Air and MacBook Pro are pretty much "normal". With Thunderbird I guess I could get what I want with an iMac + external RAID, but it sure is pricey. Plus updating my graphics card isn't that easy anymore. In short their desktop lineup sucks almost as bad as the server lineup, but we're also no longer a very important market segment.

      --
      Live today, because you never know what tomorrow brings
    40. Re:Shouldn't Apples count? by Grishnakh · · Score: 1

      He's talking about the UI, not the other parts of the OS (all the crappiness that made Vista so slow, for instance). However, I thought Vista was more like XP in that regard than like 7.

    41. Re:Shouldn't Apples count? by TheRaven64 · · Score: 3, Interesting

      The locking of /dev/dsp is mostly ancient history at this point, even on Linux, where sound (finally) got the attention it needs

      And yet I still regularly hear complaints from Linux users about sound-related problems.

      I use schroot for the usecase you use ezjail for, and from your short note it looks mostly equivalent. I tend to use either a btrfs or lvm backend.

      schroot uses chroot. Jail does a lot more than chroot - each jail contains an independent set of users, so things can run as root inside a jail without being able to escape.

      As for creating new filesystems, I find that mostly a bother; what I want is just one filesystem to handle it all

      I want my backups to be compressed and deduplicated. I want my hone directory to have some extra redundancy. I want my ports tree to be compressed but not deduplicated. I don't want setuid or execute flags to work on every part of the hierarchy.

      The reason you want one filesystem is because you use a system where creating a new one that does what you want is expensive. Adding a new zfs filesystem is a single command and takes a few seconds (99% of which is the time taken to type the command, not the time for it to execute). Before using ZFS, I was in the same situation - I'd given up creating different filesystems for different parts of the tree. With the system I've set up to use ZFS, I currently have 24 ZFS filesystems mounted. There is no reason not to create more, and (since snapshots happen on a filesystem granularity) some very good reasons for creating new ones.

      Snapshots are useful though (and supported by LVM and btrfs).

      LVM snapshots are much more heavyweight than ZFS ones (which cost about as much as creating a hard link to create). I doubt you'd set up a cron job to take daily or hourly snapshots with LVM, but I wouldn't even think twice about doing that with the ZFS filesystem I use for storing backups.

      Not sure about btrfs, but last I heard it wasn't even close to being production ready and, because it still uses the old SunOS-derived layering, doesn't fix the RAID-5 write hole or address half of the other things that ZFS does. Like many other Linux things, it's a superficial copy of something else, missing the parts that made the original interesting.

      --
      I am TheRaven on Soylent News
    42. Re:Shouldn't Apples count? by ByOhTek · · Score: 1

      Yes. There is a lot of suck in the OSX UI. Vista has a lot of suck too, but it doesn't try to drag my attention away from work quite like OS X does.

      OS X's UI has always seemed like a little kid, jumping and screaming for attention. I don't use my computer because it looks pretty, I use it because it does a job. It shouldn't draw attention (either by looking ugly or by trying to get my attention when my attention isn't required).

      --
      Self proclaimed typo king, and inventor of the bear destroying coffee table (patent not pending).
    43. Re:Shouldn't Apples count? by bonch · · Score: 1, Informative

      OS X runs on its own XNU kernel and driver model but incorporates various components of FreeBSD and NetBSD, such as the network stack. That layer of the operating system is referred to as Darwin.

    44. Re:Shouldn't Apples count? by SuricouRaven · · Score: 1

      Thunderbolt. The high-end mac pros still make nice workstation machines (Dual Xeon and a ton of RAM, and will happily run six screens), but other than that their desktops arn't anything special performance-wise. I had to get a third-party PCIe card on mine just to get eSATA support though. I notice that even the very newest macbooks don't have USB3, probably because that would ruin the only reason anyone has for using a Thunderbolt port. Why pay £600 for a thunderbolt accessory when you can get the USB3 equivilent for a tenth the price and no significent difference in performance?

    45. Re:Shouldn't Apples count? by SuricouRaven · · Score: 1

      The best GUI in the world is always the one you use. Familiarity is the key to GUI useability - that's why any change to GUIs is always met with an immediate backlash.
      Except Vista. The more you use that, the more you hate it.

    46. Re:Shouldn't Apples count? by TheRaven64 · · Score: 2

      The problem is that FreeBSD's implementation of ZFS in stable builds is extremely out of date. FreeBSD currently supports ZFS v15 (current closed-source is v33), which means you're missing a lot of the features. No triple-parity RAID, no deduplication, no encryption, no snapshot diffs, etc.

      As you say, FreeBSD 9 (currently in release candidate phase) supports ZFS v28. I'm using the RC now, and deduplication seems to work pretty nicely. I've got a compressed deduplicated volume that I use for Time Machine backups from a couple of Macs. Compression is saving about 25% of the space, and deduplication another 10% (I expect this to increase, because Time Machine creates a new copy of every file even if only one block changes).

      Of course, the downside to all this is that ZFS is now effectively closed-source, and I'm not sure if we'll ever get anything newer than v28, unless it forks...

      iXSystems sells ZFS-based storage appliances running FreeBSD. They've recently taken over development of FreeNAS and have publicly committed to continuing to develop ZFS on FreeBSD - they've already been responsible for fixing a few bugs that haven't get been fixed on Solaris. Whether the new versions will be compatible with Oracle's version depends on whether Oracle releases documentation, but either way ZFS in FreeBSD is not going to orphaned.

      --
      I am TheRaven on Soylent News
    47. Re:Shouldn't Apples count? by greg1104 · · Score: 5, Interesting

      The important part isn't how FreeBSD's ZFS compares with Solaris's; it's how it compares to available Linux filesystems. You're not getting triple parity or dedup support there either. The ZFS v15 is still miles ahead of any stable Linux FS for many applications. Block checksums is the feature I miss most on Linux, with good snapshot support being a close second. v15 may not have the latest snapshot diffs, but it's still better than how Linux's snapshots require LVM to work, and even then are very hackish to use.

    48. Re:Shouldn't Apples count? by unixisc · · Score: 1

      Is it based on Mach 2.5 or 3.0? 2.5 was monolithic, 3.0 was microkernel. But OS-X is not a microkernel OS.

    49. Re:Shouldn't Apples count? by Anonymous Coward · · Score: 0

      XNU operating system (what follows Server-Client architecture) what OS X and iOS use is combination Mach microkernel, FreeBSD's networking and filesystem functions as servers and I/O Kit and so on.

      XNU ain't BSD-flavoured but own operating system. That the networking and filesystems have from FreeBSD to run as own servers on XNU does not make it anything.

      Darwin is XNU + development tools and configs. With specific Darwin version you know that what version of XNU you have and with what configurations it has been compiled. Darwin ain't operating system, it is development platform.

    50. Re:Shouldn't Apples count? by Anonymous Coward · · Score: 0

      Linux is a kernel and no OS.

      GNU/Linux is the name of the operating system you probably meant.
      There was less necessary to include, as less functions, less drivers, no GUI, etc were included.
      The complexity was simply on a different (much lower) level.

    51. Re:Shouldn't Apples count? by Anonymous Coward · · Score: 0

      > No, Darwin is NOT a BSD distro, as Darwin is neither BSD nor a complete OS.

      Quit splitting hairs, it doesn't matter what you call it. Mac OS X is a BSD variant. It's a certified Unix, and it sure isn't the proprietary parts that make it one.

      There's no technical reason to say it's not a BSD, only elitist dismissiveness.

    52. Re:Shouldn't Apples count? by nurb432 · · Score: 1

      Linux is used more than BSD because there are more available distros, meeting diverse needs without any configuration necessary. Professional support is more readily available, and in my limited experience, even hardware support is somewhat better.

      And BSD is more usable than Linux due to this same fact. More organized and predictable.

      --
      ---- Booth was a patriot ----
    53. Re:Shouldn't Apples count? by Anonymous Coward · · Score: 0

      Mach is microkernel and used in many different server-client architecture OS's.

      XNU is Server-Client OS like NT, Minix and HURD are as well (moving servers from kernel space to user space or vice versa does not make OS any different from Server-Client architecture. The OS is Server-Client or then it is Monolithic. Now there is even newer architecture, a multi-microkernel OS)

      You can even download Mach separated XNU from Apple's Open Source page. As whole XNU operating system is 100% open source (and free software) licensed with license what OSI and FSF have accepted.

      It is just news to many who does not know that OS X or iOS ain't operating systems but software systems, using same open source XNU operating system.

    54. Re:Shouldn't Apples count? by Dog-Cow · · Score: 0

      In a reasonably-sized company (100+ workstations), the management features and software compatibility are the primary reasons for choosing Windows. Linux doesn't even come close.

    55. Re:Shouldn't Apples count? by datavirtue · · Score: 0

      That is funny as hell. Because it is true.

      --
      I object to power without constructive purpose. --Spock
    56. Re:Shouldn't Apples count? by datavirtue · · Score: 1

      What OS do you run? AOL.

      --
      I object to power without constructive purpose. --Spock
    57. Re:Shouldn't Apples count? by EsbenMoseHansen · · Score: 1

      I seem to have touched a nerve :)

      You will always hear more complaints from Linux users. That is a price for having easy installers. But aside from unsupported hardware, I haven't had a problem with sound since the debacle around pulseaudio (which got enabled a bit prematurely imho. But works fine now.)

      As for running root as chroot: That is not a usecase I saw, nor one I have ever missed. From wikipedia jails falls in somewhere between a virtualized server and a chroot. *shrug* Certainly not a game changer, and a short google search reveals some linux alternatives.

      The reason I prefer to not have multiple filesystem is so that my backups can use hardlinks, I can move files between say /tmp and my /home without actually moving the data, and so that I don't have to bother thinking about it. I cannot get that today, because there is no way to encrypt part of a file system (or deduplicate etc, though I just use hardlinks for that. Easier to understand, less error-prone.) Creating a new filesystem takes me about a minute: I waste a lot more time (order of magnitudes) waiting for just moves between filessystems (even if I only use 2) than I ever did for creating filesystems. Sure, it is cool, and I think it is fun doing it with btrfs, but it's not really very useful.

      As for btrfs... I use it for snapshots. Why? Because I can. LVM would likely serve me just as well, but I like to play with new things. The data being snapshots, I don't care how stable it is, but it seems to work :) The remaining feature ZFS has are not compelling enough for me to bother installing even a test of it (with fuser, I think it is on linux).

      P.S: Why don't you deduplicate everything? That sounds like there is a significant downside?

      --
      Religion is regarded by the common people as true, by the wise as false, and by rulers as useful.
    58. Re:Shouldn't Apples count? by EsbenMoseHansen · · Score: 1

      Sure, but several file systems have drawbacks too. I'd prefer file systems that let me specify such features at the directory level instead.

      Breaking chroot for non-root users are not exactly trivial, though I don't personally use chroot for that.. .I use it (as the GP suggested) for scratch areas, especially for building and testing applications under different environments.

      --
      Religion is regarded by the common people as true, by the wise as false, and by rulers as useful.
    59. Re:Shouldn't Apples count? by Anonymous Coward · · Score: 0

      XNU ain't kernel but operating system. Mach is the microkernel what XNU use. And XNU is Server-Client by architecture instead Monolithic like Linux and FreeBSD, so it is like NT (what ain't "hybrid" what is just marketing propaganda what not even Microsoft use anymore).

      The Darwin is XNU + compiler and configs. It is same thing as GNU/Linux where Linux is a monolithic OS and GNU part is the compiler and configs.
      The Darwin and the GNU/Linux ain't operating systems but development platforms. GNU has own operating system HURD what is like XNU, it as well used Mach microkernel (now it use again something else or have they rolled back to Mach?) and own servers.

        http://www.topology.org/linux/lingl.html

      It is really very simple thing when first forgetting everything and then starting from scrating thinking what person needs to get simple program like INIT or shell (or compiler or any text editor) running.

    60. Re:Shouldn't Apples count? by Tarlus · · Score: 1

      MacOS X is a race car in the same way a sedan is a race car?

      --
      /* No Comment */
    61. Re:Shouldn't Apples count? by wagnerrp · · Score: 1

      There are only two drawbacks of multiple filesystems. Moving files between filesystems means you have to read and write back out the file, rather than simply altering an index. Use of things like NFS that are aware of filesystem levels for security purposes become more complicated. Do understand that filesystems in ZFS draw from a shared storage pool. It's not like a traditional partition where you are restricting access to disk space.

    62. Re:Shouldn't Apples count? by ByOhTek · · Score: 1

      OH. I see the point now. Coffee. Yes.

      MacOS is a BSD OS in the same way a house is a skyscraper.

      --
      Self proclaimed typo king, and inventor of the bear destroying coffee table (patent not pending).
    63. Re:Shouldn't Apples count? by TheRaven64 · · Score: 1

      Why don't you deduplicate everything? That sounds like there is a significant downside?

      Deduplication comes with a fairly hefty memory cost and requries every disk write to be checked against a hash table of existing blocks. This cost is worth paying for things that are likely to contain a reasonable amount of duplication, but not for other things. The combination of compression and deduplication on my backup volume is saving about a third - the disk space used is about the same as if I were using JBOD instead of RAID-Z, but if one of my disks fails the filesystem will still be fine. On the filesystem where I rip my DVDs, enabling compression and deduplication would be unlikely to save even 1%, but would slow the entire system down. The ports tree has a compression ratio of 1.67x at the moment, and it contains a lot of small files so the overhead of decompression is likely to be lost in the noise of disk seek times. For other filesystems, it wouldn't make sense.

      I also have an 8GB USB flash drive set up as L2ARC for that machine, which gets about a 40% hit rate and avoids the need to go to the disk at all for a lot of things.

      Oh, and I'd take issue with the assertion that hard links are easier to understand than deduplication. Deduplication lets you just make copies, with hard links you have no copy on write, so you have to remember that modifying one copy will modify all of the others.

      --
      I am TheRaven on Soylent News
    64. Re:Shouldn't Apples count? by painandgreed · · Score: 1

      Would you have preferred a car analogy?

      MacOS is sort of like a kit car made by a custom shop. They take a couple of fairly common cars, cut them up, and weld them back together with a lot of custom work. Then add a custom exterior and interior that makes it look great and a pleasure to sit in (unless you are used to BMWs and all their extra features such as the remote control seat warmers). It drives well, but there are things that it might not do as well as one of the individual cars it was original made from. Meanwhile, there are all the custom work and parts that can only be gotten from the shop that built it, and they will repair and replace, but won't sell just the parts.

      How's that?

    65. Re:Shouldn't Apples count? by jbolden · · Score: 1

      You've been around a while. You know the management features in a Unix are arguably better than what exists in Windows. They are just very different, because things like license management aren't a focus; there is no need for something like Citrix...

    66. Re:Shouldn't Apples count? by Guy+Harris · · Score: 2

      I'm sure I'm opening myself up for an onslaught here, but I thought all their OSX-based stuff was basically just a very elaborate FreeBSD distro.

      You were mistaken. OS X's kernel is a combination of some Mach-derived code modified by Apple, some BSD-derived code modified by Apple, some Sun-written code modified by Apple, and some Apple-written code. Its libc (or libSystem) is a combination of some mostly-FreeBSD-derived code modified to varying degrees by Apple and some Apple-written code. The rest of the UN*X userland is a combination of BSD-derived code, GNU code, other upstream code, and Apple-written code. (In some places it goes with GNU code rather than BSD code, e.g. using Bash rather than the Almquist shell as its Bourne shell and GNU Make rather than BSD make as its make.)

      I used "BSD-derived" deliberately; most of the BSD-derived code might have come from FreeBSD, but at least some of it came from other BSDs.

      It's best thought of as its own BSD-flavored UN*X, related to but not the same as other BSD-flavored UN*Xes.

    67. Re:Shouldn't Apples count? by Anonymous Coward · · Score: 0

      Linux is a kernel and no OS. GNU/Linux is the name of the operating system you probably meant.

      There are Linux distros that don't include any GNU, were you aware of that?

    68. Re:Shouldn't Apples count? by Guy+Harris · · Score: 1

      XNU operating system (what follows Server-Client architecture) what OS X and iOS use is combination Mach microkernel, FreeBSD's networking and filesystem functions as servers

      No, they don't. They function as built-in parts of XNU or as loadable kernel modules, invoked through procedure calls.

      And the networking code, VFS layer, and some of the file systems that plug into it may be BSD-derived but they ain't just lightly-breated-on FreeBSD code.

    69. Re:Shouldn't Apples count? by Guy+Harris · · Score: 1

      Mach is microkernel and used in many different server-client architecture OS's.

      XNU is Server-Client OS like NT

      If by "is" you mean "not really", that statement is true of both Darwin and NT. :-)

      NT is a bit more microkernelish than Darwin (with the client-server whatever whatever whatever process, csrss, doing, as I understand it, functions such as mapping Windows paths to NT paths and CreateProcess), but it's not as if file system and networking functions run in server processes in either OS (not even kernel-mode server processes). Yes, there are kernel threads that handle some of those functions, but they're not exactly server threads.

    70. Re:Shouldn't Apples count? by EsbenMoseHansen · · Score: 1

      Thanks for the explanation about deduplication. Not as cool as I had hoped, but suppose real life is often that way

      As for hardlinks, I was thinking specifically about backups, which are managed by a backup system. I never write to files in the backup (that would not make sense), so that is a non-issue, and that makes the system very, very simple and very effective. In the general case, deduplication is of course easier, but as I get from you, seldom worth the effort. With modern disk drives being so big, size tends to take 2nd place to speed or reliability in most cases.

      --
      Religion is regarded by the common people as true, by the wise as false, and by rulers as useful.
    71. Re:Shouldn't Apples count? by EsbenMoseHansen · · Score: 1

      I understand how it works, I use btrfs for fun to make disposable chroots, which is useful (though LVM would give me nearly identical results). Besides moving, there is also the hardlink problem... hardlinks cannot cross fs boundaries. Important for e.g. backups and git repositories.

      Not having to worry about the pool is cool, and certainly a step up from LVM, but IMHO not nearly compelling enough, especially considering that btrfs is on the way to fix that feature.

      --
      Religion is regarded by the common people as true, by the wise as false, and by rulers as useful.
    72. Re:Shouldn't Apples count? by Anonymous Coward · · Score: 0

      No, Darwin is NOT a BSD distro, as Darwin is neither BSD nor a complete OS.

      It is indeed a BSD, and it is a complete OS... though maybe not with all the features you want in an OS.

      I'd be interested in hearing what you think disqualifies it.

      ...On second thought, I don't think it would be very interesting or enlightening. Just pedantic.

    73. Re:Shouldn't Apples count? by TheRaven64 · · Score: 1

      To put some numbers on it, with my 1.6GHz AMD fusion CPU, I can only write at about 20MB/s to a three disk RAID-Z array with compression and deduplication enabled. For backups over WiFi, that's no limitation at all - it;s still ten times faster than the network. For local use, it's not ideal. That said, it's going to be a lot faster on a better CPU. It may also be possible in future versions to speed up the search for duplicate blocks by using a multiple threads.

      --
      I am TheRaven on Soylent News
    74. Re:Shouldn't Apples count? by synthespian · · Score: 4, Interesting

      So true...For me, FreeBSD adoption went like this: Debian eventually became huge stagnant swamp. To get out of it, you had to run unstable. A big mess ensued. Enter Ubuntu, the revenge, the promise. Poor documentation. Installation breakage. 6 months later, upgrade wreckage. Fsck this, I thought.

      I have installed FreeBSD once. Ports may take longer, but they are much more current then Debian ever was, and than the current Linux I use, Mandriva. You have to wait for the Package Masters...Also, with ports I have a much more fine-grained control. But let's get this out of the way: you can install packages in FreeBSD, and you do binary upgrades. There are lots of tools to handle ports. With today's speeds and RAMs, it's no big deal compiling ports. Only huge software, such as Java may take many hours (use the weekend or get the binaries and that's that..) FreeBSD takes some tweaking - because all you get is a Unix with no assumptions about what color the user favors, or which icons... -, but it's not a problem for the advanced Linux user (if you're a n00b, then there's PC-BSD, which actually should be the first approach to BSDs for the user workstation these days).

      I look at today's Linux and I don't regret my choice. What's the sane choice? Fedora is an experimental platform for Red Hat. That means, from time to time, they'll make you their guinea pigs...Debian can't even be considered secure (no less than twice they had their servers hacked), and who cares about dinossaurs, anyway? Ubuntu's the new Debian. Ubuntu shoves their choices down your throat and continues the Debian tradition of delivering broken software (the new GUI, etc.) and infighting. And Ubuntu is a fantasy. The only reason it exists is because there's a money-loosing millionaire backing it up. The fantasy island one day will blow up in the fanboys' face. Mandriva I find agreeable, but they don't offer many packages, and they have too few commercial partners (so why pay?) Other distros aren't even worth mentioning.

      I've used expensive proprietary mathematical software for Linux on FreeBSD, using their Linux binary layer, after the Linux upgrade destroyed library compatibility (they pride themselves in having unstable ABIs).

      Linux are a mess. Each one is different, full of stupid little quirks. Libraries differ in place, version, even names. FreeBSD is just as good for the desktop. The system is sane, advances by increments, has documentation, and man pages that are actually worth reading. It's a system where decisions are not made on political bases, but technical. The noise level is much lower. One of the reasons Linux makes much more headlines (besides the PR department from Big Iron, that is) is the constant noise and turmoil. BSDs are not like that...6 months later, you learn they added a cool feature. "Thou shall not fight about bikesheds."

      Linux development might get more resources. But, of course it does! Linux was part of a strategy to kill Sun Microsystems and Solaris.

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
    75. Re:Shouldn't Apples count? by RocketRabbit · · Score: 2

      You're missing the difference between a server and a component of a datacenter.

      Apple's server offerings, going all the way back, have been targeted at offering a smaller organization looking for something easy to use and familiar for their small to mid sized operation. We're talking schools here with maybe several hundred students, small to medium businesses with less than say, 100 employees, that sort of thing. These types of customers typically don't even own an equipment rack, and if they do it's populated entirely by commodity-grade D-Link switches and wifi routers. There's literally no need there for out of band management, SANs, or anything else that you seem to be thinking about. These organizations typically don't want to employ a full-time system administrator - they have an IT guy who runs the servers, fixes desktops, and offers user support, and does any and everything else the organization needs done. This guy doesn't want to fuck around with getting a "proper" environment going - he just wants to plug something in that will handle storage, mail, blogs, jabber, and a wiki. You know, the stuff that is so easy on OS X server that all you need to know how to do is slam your forehead into the space bar.

      Contrary to what you may have heard, Apple isn't interested in the low margin, high support cost market that Dell and HP are fighting for. The profit per unit is just too small for them to bother with. They are going where their customers are - graphics design shops, small schools and offices, etc.

      With the amount of computing ability that you get with a newer model Mac Pro, or hell even a Mac Mini, you can run one of these operations with one box tucked in a closet, sitting on top of a UPS, and it will just sit there happily plugging away doing everything they need to do without any need for somebody like yourself.

    76. Re:Shouldn't Apples count? by AHuxley · · Score: 1

      Re: Apples server market in full colour:
      Thar's BSD in Them That Apples
      http://www.apple.com/server/

      --
      Domestic spying is now "Benign Information Gathering"
    77. Re:Shouldn't Apples count? by cpghost · · Score: 1

      The good news is that FreeBSD 9.0 will bring this up to v28

      ZFS v28 was merged from current into 8-stable many, many months already. Runs very stable here on my FreeBSD/amd64 boxes.

      --
      cpghost at Cordula's Web.
    78. Re:Shouldn't Apples count? by Niomosy · · Score: 1

      Wasn't there also an AT&T lawsuit which took *BSD out of the picture temporarily, allowing Linux to jump into a niche that was left open?

    79. Re:Shouldn't Apples count? by Anonymous Coward · · Score: 0

      Lies. FreeBSD abandons and replaces tech like everyone else. I'd know, I had to reformat a server because the mirroring used was killed off.

    80. Re:Shouldn't Apples count? by Guspaz · · Score: 1

      Uh, no, how it compares to available Linux filesystems is not at all relevant to me, because my file server's ZFS v28 filesystem won't run on a version of FreeBSD that only supports v15. I've got to wait until FreeBSD 9.0 to migrate.

    81. Re:Shouldn't Apples count? by Guspaz · · Score: 1

      And looking into it in more depth, it looks like Delphix and others are actively working on non-Oracle ZFS. They've switched from using version numbers to using named feature flags to differentiate, so that there are no version number collisions, and so that different groups can introduce different features. Of course, there's still the concern about fragmentation, and the loss of compatibility with Oracle isn't going to be fun.

    82. Re:Shouldn't Apples count? by Guspaz · · Score: 1

      The development branch of 8-stable, sure. But it's never going to make it into an actual release of 8.x. However, since FreeBSD 9.0 should be out within a few weeks, it's not that big a deal. Just means I have to wait.

    83. Re:Shouldn't Apples count? by deek · · Score: 1

      Very passionate post. Very inaccurate, at least about Debian.

      I run both FreeBSD and Debian servers in my workplace. Been running them for the last 6 years. I also have Debian running as my primary OS on my workstation. Debian is not a "stagnant swamp" as you say it is. If you really want the absolutely latest software, then you can install testing or unstable packages on an otherwise stable system. If you're running servers, though, you really don't want to be running the latest stuff.

      Debian can't be considered secure? That's a strange thing to say. Our Debian systems have never had a problem, and security patches are always prompt and timely. Funnily enough, it's been one of our FreeBSD systems that has been hacked into, but granted, it was a PHP software security issue.

      Interestingly, I've found that Debian is more sane and better documented than the FreeBSD system. I guess it's just one of those subjective things.

      FreeBSD makes for a very good server. No questions there. I'd argue that Debian is better though, because it is more manageable than FreeBSD. As for desktops, Ubuntu is better than both, though.

    84. Re:Shouldn't Apples count? by Dwonis · · Score: 1

      Debian can't even be considered secure (no less than twice they had their servers hacked)

      You realize that the whole Debian archive is signed, and those signatures are checked by apt-get, right? When did malicious code ever make it into the (signed) archive?

    85. Re:Shouldn't Apples count? by dave87656 · · Score: 1

      I RTFA'd and I still find his comment apropos.

      Anyway, as I understand it, the big difference between OSX and FreeBSD is that OSX doesn't use X. Is that correct?

    86. Re:Shouldn't Apples count? by snowshell · · Score: 1

      oh sure ext4 is way behind the Zune Filing System, because we all want roll back features on a file system like the LvM2 with Advanced Encryption Support...

    87. Re:Shouldn't Apples count? by snowshell · · Score: 1

      Lol at people bashing debian saying it's the distro's fault that the end user can not take the time to fix libraries or patch applications that are unstable by downloading the latest stable branch and compiling it themselves be that out of the debian archives or direct from the source. As an example I was using Uncomplicated Firewall (ufw) and the GUI in the current debian stable build is broken, try using it to delete a rule from the firewall.. So the fix, well lets see, go directly to the maintainer on launchpad for ufw version 3.0 and then compile it and then go directly to the 11.04 gui (gufw) launchpad and my god look at that now it works without a hitch!

    88. Re:Shouldn't Apples count? by TheRaven64 · · Score: 1

      There are three branches to FreeBSD. -CURRENT is where the active development goes on. Stuff in here shouldn't break, but it may only have been tested on one person's machine so there's a good chance that it will. After something has been tested, it moves into the -STABLE branch. Most users track stable by just running csup and then doing a make world. This gives them new features as soon as possible without compromising stability. The third category is the release branches. Releases are made by a code freeze and a few weeks of bug fixing in -STABLE. Then they are branched. After that, the release branch will only ever get bug fixes, never new features. If you run 8.2, you can keep tracking the 8.2 branch until it's no longer supported and you won't see any changes, you'll just get security updates. Or you can jump from 8.2 to 8.3 when it's released, or you can periodically grab the latest from -STABLE.

      You're very unlikely to see any serious bugs in -STABLE, and people who can afford to see occasional ones are encouraged to use it and report any issues they find so that they can be fixed before the release (which is for 'stability at all costs' users). You are not encouraged to use -CURRENT unless you are a developer.

      But it's never going to make it into an actual release of 8.x.

      Absolutely untrue. It is in 8-STABLE, which means that it will be included in the next 8.x series release, which will be 8.3. If you're running 8.2 now, upgrading to 8-STABLE is easy and if you did it any time after June this year you'll already have found yourself with ZFS v28.

      --
      I am TheRaven on Soylent News
    89. Re:Shouldn't Apples count? by Tarlus · · Score: 1

      Gotcha. =)

      --
      /* No Comment */
  2. Performance gets eaten by old software by gentryx · · Score: 4, Interesting

    At least it's that way for us in HPC. Sure, FreeBSD is rock stable and all, but if you run stable, you'll be trailing behind and won't get to use the latest packages. This may be fine for ordinary HTTP server, but when you need an updated NUMA aware scheduler for your 48 core/4 socket machine or the latest drivers for your InfiniBand hardware, then you'll happily give up some alleged increase in stability in favor of real performance. Same is true for Debian stable.

    --
    Computer simulation made easy -- LibGeoDecomp
    1. Re:Performance gets eaten by old software by DrgnDancer · · Score: 1

      And, those are the real situations where you need the performance you allegedly get by using BSD. Honestly, for most day to day purposes eeking a few extra performance percentages out of a box is not all that big of a deal. Most computers are more than powerful enough to do most of what we want them too most of the time. This is true even in server class installs except at the most cutting edge.

      When I really need the most performance out of a box (HPC, high end servers, etc) I'm going to spend the money on the latest and greatest hardware. The latest and greatest is usually a driver nightmare on the *BSD OSes, so I tend to use Linux. If performance isn't a huge issue, then I'm not going to go to all the effort of tweaking a *BSD box. So I tend to use Linux. Of course in the first case I'll spend a ton of time tweaking, and even recompiling parts of the Linux stack for performance, in the second I'll "'yum install x y z' and toss it out into the wild".

      --
      I don't need a million points of light, just two points of multi-mode fiber and a 10 Gig-E router.
    2. Re:Performance gets eaten by old software by hedwards · · Score: 1

      If you're concerned with being up to date, you use ports which are rarely much out of date. Except maybe for some of the less popular ones.

      And really, you should be rolling your own as you can optimize them for use with more modern processors.

    3. Re:Performance gets eaten by old software by gentryx · · Score: 1

      And this is why I run Gentoo Linux. I don't have to roll my own, but still get optimized (and customized) builds, mostly free of effort.

      --
      Computer simulation made easy -- LibGeoDecomp
    4. Re:Performance gets eaten by old software by overlordofmu · · Score: 3, Informative

      Don't you know other people mock Gentoo?

      Sure, it works well for chumps like Facebook and the the NY Stock Exchange, but no one is using it for serious . . . um, wait . . . nevermind.

    5. Re:Performance gets eaten by old software by rev0lt · · Score: 1

      Ports are upgradeable at anytime, and freebsd has somewhat frequent releases. If you really need a scheduler for those 48 core, you probably would be better with solaris than with linux. But yes, often server-grade hardware lacks freebsd drivers, and most vendors don't correct defects on drivers not supplied by them. Some vendors don't correct them at all, but it is somewhat easier to fill a problem report when using a supported operating system.

    6. Re:Performance gets eaten by old software by johnthorensen · · Score: 1

      Most of the Gentoo mocking comes from the fact that it's liked by the same people who have transparent windows in their computers with UV-reactive liquid coolant, but it does have its place. I gave an employee an assignment to build a Gentoo system because it was a good way for them to get hands-on experience with the internals of Linux and the command line. Not something you get from installing the latest Ubuntu distro.

    7. Re:Performance gets eaten by old software by Anonymous Coward · · Score: 0

      "And, those are the real situations where you need the performance you allegedly get by using BSD. Honestly, for most day to day purposes eeking a few extra performance percentages out of a box is not all that big of a deal. Most computers are more than powerful enough to do most of what we want them too most of the time. This is true even in server class installs except at the most cutting edge."

                True, except it directly contradicts the "time required to really get a FreeBSD box tuned will come back in spades through performance and stability metrics", if the performance is LOWER due to older software.

                (Side bar -- this also amuses me, because you can talk to any Windows user, they take it as gospel that newer software (almost) always gets bigger and slower like it's some law of nature. Us Linux and BSD users tend to see the opposite. I sure have, I've only needed to upgrade my hardware when I actually expect it to do more significantly work, not to do the same stuff with a newer distro.)

                Anyway... last time I messed with a FreeBSD box, it reminded me of a late-1990s era Linux distro -- modern desktop but some extra fiddling to get it all working. Honestly, I used Linux back then, and the BSD users are not lying when they say this fiddling is not that bad. But, Ubuntu will either "just work" or hold your hand the whole way in similar circustances. (One exception -- wireless. Instead of just recently deciding mac80211 was "it", with SoftMAC, and atheros and intel drivers having their own MACs, and so on, FreeBSD standardized on a single 802.11 implementation like 10 or more years ago, and may still be ahead in terms of wireless device support.)

    8. Re:Performance gets eaten by old software by TheRaven64 · · Score: 1

      Few people mock Gentoo. A lot of people mock Gentoo users. I've not heard much from the distro for a while, but when it first came out its users were always telling you how much faster everything went if you added -funroll-loops to your CFLAGS. Now, most people who use Gentoo care more about the fact source builds make it easier to customise the software you install and use portage just like FreeBSD ports, so they aren't mocked as much.

      --
      I am TheRaven on Soylent News
    9. Re:Performance gets eaten by old software by reasterling · · Score: 1

      I've only needed to upgrade my hardware when I actually expect it to do more significantly work, not to do the same stuff with a newer distro.

      You haven't tried gnome 3 yet have you.

      --
      "For I desired mercy, and not sacrifice" -- God
    10. Re:Performance gets eaten by old software by jasno · · Score: 1

      Good point - using Gentoo brings a familiarity with the totality of the Linux experience that is second only to following the Linux from Scratch guide. It's been a few years, but I was never as sharp on my Linux internals, and the current state of important packages, as when I was using Gentoo.

      Shit.. that does it.. I'm switching back!

      --

      http://www.masturbateforpeace.com/
    11. Re:Performance gets eaten by old software by Jorl17 · · Score: 1

      I use Gentoo in 6 machines and I don't fit that description ;)

      --
      Have you heard about SoylentNews?
    12. Re:Performance gets eaten by old software by Rich0 · · Score: 1

      Well, don't completely discount being able to set -march to something other than i686 and use -ftree-parallelize-loops or whatever.

      Sure, this will break the odd package, but it is easy enough to just fall back to simple flags for a few of them.

    13. Re:Performance gets eaten by old software by synthespian · · Score: 1

      What about Linux binary emulation?
      I remember sometime ago, there was a story about a certain Linux software running faster in FreeBSD with the emulation layer than in Linux (don't remember what it was...)

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
    14. Re:Performance gets eaten by old software by utkonos · · Score: 1

      I beg to differ about your order of who is second and first. Building linux from scratch is first, and second place must go to Slackware. Gentoo's portage actually thinks about package conflicts and dependencies. Slackware, you have lots of well built tarballs and your wits.

    15. Re:Performance gets eaten by old software by rev0lt · · Score: 1

      I think you are talking about java and eclipse development tools that reportedly run faster using Linux ABI in FreeBSD than in native linux. If I recall correctly, at the time, the mainstream linux kernel was the 2.4 line, that had several design issues that impacted performance on many applications. 2.6 is a whole different beast. The Linux ABI is a nice FreeBSD feature (and currently is 2.6 compatible), but there is no support for 64 bit binaries. Also, some syscalls are not implemented, as well as some exotic functions such as LDT manipulation and virtual 86 mode. The biggest gripe I get with the Linux ABI are the userland environments available on the ports tree - some are old, some are deprecated and/or forbidden. It would be awesome to fire up a jail running a linux userland to use linux-only software, even if limited to 32 bit - Zend Encoder comes to mind.

    16. Re:Performance gets eaten by old software by SiliconViper · · Score: 1

      You've accurately described Debian Stable, but your argument doesn't hold for *BSD, where the "packages" (ports) you refer to do not differ between -STABLE and -CURRENT. So if you're running 7.4-RELEASE, any ports you have will be just as "updated" as those you'd have running 9.0-RC1.

      --
      "It is through collaboration that we achieve our greatest works." -- Chris Olstrom
    17. Re:Performance gets eaten by old software by MSG · · Score: 1

      Sure, it works well for chumps like Facebook and the the NY Stock Exchange, but no one is using it for serious . . . um, wait . . . nevermind.

      I don't know about Facebook, but NYSE is using Red Hat Enterprise Linux, not Gentoo. Actually, I'm not aware of anyone who is using Gentoo for anything serious.

  3. Sorry, but it's not worth the time by kriston · · Score: 4, Informative

    Are you really suggesting that the time I spend will "come back in spades?"

    Sorry, but as a longtime FreeBSD user and having wasted days of my life getting the graphics card to work and then tuning every last parameter, I'll take Ubuntu or Fedora on my desktop, thanks.

    Sorry, but it's not worth the time and whatever "spades" you're getting paid pack in are 99% emotional, not physical.

    --

    Kriston

    1. Re:Sorry, but it's not worth the time by Col.+Klink+(retired) · · Score: 3, Funny

      Oblig xkcd.

      --

      -- Don't Tase me, bro!

    2. Re:Sorry, but it's not worth the time by Entrope · · Score: 2

      It is one thing to look at somebody else's work product and be impressed. It's an entirely different thing to look at your own and decide that, yea verily, that was a nearly optimal way to spend your time. (The major difference is that you usually have a much better idea of how much time and frustration you spent than what someone else spent.) Unless your objective is making computers run fast or maintaining the OS, time spent tweaking things at a low level -- which FreeBSD requires -- is probably not worth it.

    3. Re:Sorry, but it's not worth the time by FunkyELF · · Score: 0

      Oblig xkcd.

    4. Re:Sorry, but it's not worth the time by Anonymous Coward · · Score: 1

      Are you sure you weren't thinking of this one? https://www.xkcd.com/349/

    5. Re:Sorry, but it's not worth the time by Anonymous Coward · · Score: 1

      Are you really suggesting that the time I spend will "come back in spades?"

      Have you seen PC-BSD ?

    6. Re:Sorry, but it's not worth the time by hedwards · · Score: 1

      You must not have been very good if you had that much trouble. I started using FreeBSD over a decade ago and I never had that much trouble getting my graphics cards to work. Some of them weren't supported at all, so I just used the VESA, but once I started buying with FreeBSD in mind I never had that kind of trouble either.

      If you're taking that much time and effort to tune a video card you're never going to get the time back, and it doesn't matter what OS you use, in my experience FreeBSD doesn't take any more time in that respect that Linux does.

      Where you do save a crapload of time is things like the integrated revision system, so when you edit a system file you can simply check it out and check it back in when you're finished. Or compiling everything with appropriate use of processor extensions. Not to mention the much easier process of eliminating unneeded modules from the kernel.

    7. Re:Sorry, but it's not worth the time by IICV · · Score: 1

      Sorry, but it's not worth the time and whatever "spades" you're getting paid pack in are 99% emotional, not physical.

      Yeah, that's exactly what I was wondering. I actually RTFA'd to see if the author had any sort of real statistics, but he really doesn't; the one thing that's presented as any sort of evidence is Netcraft's list of most reliable hosting companies for February, which is pretty meaningless. Sure, the top three are running FreeBSD, but every other company on the list is running Linux (besides number 9, which is running Windows Server 2003).

      Furthermore, if you look at the historical monthly data for "best datacenter", it's pretty obvious that the whole thing is hugely variable. Sure, in Feb 2011 the top three were FreeBSD sites; in April 2011, the top three were Rackspace (which runs something I've never heard of), Linux and Windows. You would imagine that if this were really a measurement of the operating system's reliability, the top ten lists would be fairly consistent; after all, it's not like the OS is changing significantly month to month. Instead, because it varies so much, this is probably mostly measuring how good the providers are at making sure data flows to and from their data center, instead of how good they are at responding to it.

      And finally, the server admins who choose FreeBSD are pretty self-selecting. Someone who really knows how to tune and administer Linux is probably going to have just as stable a system as someone who really knows FreeBSD.

    8. Re:Sorry, but it's not worth the time by Chemisor · · Score: 0

      Where you do save a crapload of time is things like the integrated revision system, so when you edit a system file you can simply check it out and check it back in when you're finished.

      If you want version control on system [config] files, it is equally easy to put /etc in a git repository. Same benefits, but without relying on an obsucre file system. Oh, and I can push the same config files and their full mod history to every computer on the network. Can your fancy ZFS do that? I thought not.

      Or compiling everything with appropriate use of processor extensions.

      Ever heard of Gentoo? It's quite a bit easier to use than your BSD ports system.

      Not to mention the much easier process of eliminating unneeded modules from the kernel.

      I don't know what you're talking about. Linux always supported module unloading, and will usually do it automatically with no user intervention required.

    9. Re:Sorry, but it's not worth the time by goarilla · · Score: 1

      Where you do save a crapload of time is things like the integrated revision system.

      Any advantage of this over say RCS ( which I still use ) or svn,git,hg ?

    10. Re:Sorry, but it's not worth the time by Anonymous Coward · · Score: 0

      You should have had no problem whatsoever getting your graphics card working, as most of the Xorg drivers are common between Linux and FreeBSD. The binary blob drivers for cards Xorg doesn't support out of box fail almost as often for Linux as they do for FreeBSD---and in fact, the nVidia driver for FreeBSD is largely identical to the Linux driver, and unlike the Linux driver, contains more parts that can be tweaked to get a reluctant card working. If you have that much trouble getting the almost identical to Linux driver system working, you should have been using Desktop BSD or PC-BSD, which have done the legwork for you already, have been well-received, and as a long-time FreeBSD user you undoubtedly would know about.

      Furthermore, the vast majority of system tuning is either automatic, occurs during one-time compilation of applications/kernel, and yields tangible performance benefits. A simple exercise with DTrace, as an experienced FreeBSD user like yourself should have done, will often show improvements up to and beyond 15% between untuned generic binaries and customized binaries.

      Of course, as an experienced FreeBSD user, it's not likely you would have made this post in the first place. How long have you actually been running FreeBSD anyway?

    11. Re:Sorry, but it's not worth the time by Joce640k · · Score: 2

      I was expecting this one: https://www.xkcd.com/963/

      --
      No sig today...
    12. Re:Sorry, but it's not worth the time by Bill_the_Engineer · · Score: 1

      And finally, the server admins who choose FreeBSD are pretty self-selecting. Someone who really knows how to tune and administer Linux is probably going to have just as stable a system as someone who really knows FreeBSD.

      Unless the Linux admin needs PPS or ZFS. Speaking as someone who had to implement PPS in Linux, there have been many times where I wished I could just use FreeBSD. I couldn't because there were board support packages for Linux that weren't close to being available for any of the BSDs.

      --
      These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
    13. Re:Sorry, but it's not worth the time by justin12345 · · Score: 3, Insightful

      Paul's question, "why more folks aren't using FreeBSD on the desktop?" can be answered in two words: hardware support. My business partner is a huge proponent of BSD, and so am I... but the only on the servers.

      One time we installed NetBSD on an old laptop. It ran ok so long as you kept the power supply in the office freezer. Otherwise it would start to smoke. No graphics card or wifi, but that's to be expected. And USB devices were pretty hit and miss.

      I'm sure BSD (in general) has probably come a long way since then, but I really don't care to find out. Installing a strange new OS doesn't give me satisfaction anymore. I haven't even booted into Linux for a couple years. And I've gotten too lazy to bother with Windows and their crazy DRM schemes. At the risk of sounding like an fanboy, Apple really did something right when they bought NeXTStep. OS X is perfectly positioned at the intersection of power vs convenience. It would be very hard to give up. I'm not exactly thrilled with iOS creeping in, but I suppose if they screw OS X up I can always just install an old version.

      --
      Cool art gallery, if you're into that sort of thing.
    14. Re:Sorry, but it's not worth the time by ksd1337 · · Score: 1

      Meh, PC-BSD uses KDE by default. Other DEs don't even work as well, as they're using a customized version of KDE at that.

    15. Re:Sorry, but it's not worth the time by Anonymous Coward · · Score: 0

      Actually, our fancy ZFS can do that, and can replicate the filesystem to multiple systems as well as provide full versioning, storage pooling, and a host of other nifty features that even make the stagnant, still-born BTRFS look pretty pathetic.

      Easier to use than BSD ports? That's pretty funny. It doesn't get much easier than:
      cd /usr/ports/x11/kde4 && make install clean for a source based install and
      pkg_add -rv kde4 for a package based install and
      portmaster -a for a complete port upgrade. And while this is totally anecdotal, ports break much less often than most competing packaging systems, and often receive updates faster.

      As for the module unloading, that tells me that you don't know what you are talking about. FreeBSD systems make it very easy to compile custom kernels, whereas Linux systems often struggle. It has nothing to do with module loading/unloading, a feature FreeBSD has had for years.

    16. Re:Sorry, but it's not worth the time by fnj · · Score: 1

      Ever heard of Gentoo [gentoo.org]? It's quite a bit easier to use than your BSD ports system.

      That's bull. Ports are turnkey, dead simple to use.

    17. Re:Sorry, but it's not worth the time by Anonymous Coward · · Score: 0

      "Stagnant, still-born BTRFS"?

      If you don't know anything about a system, how can you so confidently critique it? I'm flabbergasted.

    18. Re:Sorry, but it's not worth the time by Anonymous Coward · · Score: 0

      On the contrary, I know much about the mess that is BTRFS. For example, it remains experimental, still has yet to produce an fsck tool that doesn't just tell you that your filesystem well and truly IS fscked, has major internal fragmentation problems, and has yet to even become the default filesystem in the more experimental distributions after more than 4 years of development. On top of that, it remains slow in a number of situations (to which BTRFS defenders will cry that it's still in development, but then insist that it's ready for production use.)

      I know plenty about BTRFS, once being one of those people who championed it. For any serious use, it's a pain in the ass compared to the far more mature, far more stable, and far more forgiving ZFS while offering comparable features at best.

    19. Re:Sorry, but it's not worth the time by Anonymous Coward · · Score: 0

      Note the beautiful comparison of apples with oranges too. A carefully tweaked BSD may perform better than a non-tweaked "generic" Linux, but for that to be an argument to install BSD he would need to compare it with a carefully tweaked Linux.

    20. Re:Sorry, but it's not worth the time by Anonymous Coward · · Score: 0

      Btrfs is crap because it has no fsck, says the ZFS supporter, when ZFS doesn't even have an fsck tool because it is supposed to be too reliable!

    21. Re:Sorry, but it's not worth the time by finarfinjge · · Score: 0

      You must not have been very good if you had that much trouble. I started using FreeBSD over a decade ago and I never had that much trouble getting my graphics cards to work.

      Wow! Thanks for providing an excellent example of the "support" one can expect on a FreeBSD mailing list.

      I've used debian and freebsd. I now use Windows 7. Works with everything, I never have to R an FM, I never have to compile anything. My security updates come in without any effort on my part. And I NEVER have to ask for help from nice folk like you.

    22. Re:Sorry, but it's not worth the time by finarfinjge · · Score: 4, Insightful

      Of course, as an experienced FreeBSD user, it's not likely you would have made this post in the first place. How long have you actually been running FreeBSD anyway?

      Yet another example of the helpful attitude of the FreeBSD community.

    23. Re:Sorry, but it's not worth the time by JasterBobaMereel · · Score: 1

      Used Free/Net/BSD Linux in more flavours than I care to name including Gentoo and LFS, OS/2, DOS (MS and Non-MS) , And Every version of windows from 3.0 up ..

      Linux still rates as the easiest to install, FreeBSD the most stable (once setup ..), and Windows 7 still rates as the most annoying in it's defaults, most inflexible in it's allowed changes, most likely to break existing apps, most likely to not let me install a random application and want several million updates before it will work

      Linux may have it's faults, and so does BSD, but the software in repo's/Ports just work, which they should do since someone somewhere has tested them to work with your distro...and they update themselves (that's everything you have installed) automatically

      Whereas the vast majority of Windows software assumes you are on a particular version with a particular setup and does not bother to mention this until after the fact ... and updates are done by the seemingly huge number of tooltray apps and background tasks from each manufacturer that are run along with Windows update, rather than one update system for everything ...

      --
      Puteulanus fenestra mortis
    24. Re:Sorry, but it's not worth the time by Anonymous Coward · · Score: 0

      If you want a dumbed-down UI, then just buy a Mac.

    25. Re:Sorry, but it's not worth the time by ogdenk · · Score: 2

      At least it's not Unity or GNOME Shell. Like any other *NIX multiple DE's can be installed as well. I keep a lightweight WindowMaker session configured.

    26. Re:Sorry, but it's not worth the time by Anonymous Coward · · Score: 0

      And...this. It's people like you who are the reason this article exists in the first place, the real reason no one wants FreeBSD on their desktop -- the community is full of a bunch of arrogant, self-serving pricks.

      By all means, stick to the BSD's. We wouldn't want you among us anyway.

    27. Re:Sorry, but it's not worth the time by rtm1 · · Score: 1

      That's funny, because I had exactly the opposite experience. After spending hours getting wifi to work under ubuntu (atheros chipset, no less - spent endless hours trying to get either madwifi or ath5k to work) and having to fiddle with their little gui tool thing to select a network, I finally got it working for precisely one day before the endless barrage of daily 'system updates' broke it again. After the third time discovering that something broke my wireless I wiped the machine and installed FreeBSD. Wireless configuration was exactly one line in rc.conf, and it's been rock solid ever since. I've even updated the kernel, entire system toolchain and the whole ports tree without breakage. It Just Works. This was back in 2009, so maybe things have gotten better on ubuntu since then, but once bitten, twice shy..

      --
      "Belief means not wanting to know what is true." [Nietzche, The Anti-Christ, 1889]
    28. Re:Sorry, but it's not worth the time by Multiplicity · · Score: 1

      So unless you code, where do you get your computer fun then? The feeling of boredom that avalanched over me as I read your post nearly kills my willing to live :(

    29. Re:Sorry, but it's not worth the time by sarkeizen · · Score: 1

      Sorry, but it's not worth the time and whatever "spades" you're getting paid pack in are 99% emotional, not physical.

      Yeah, that's exactly what I was wondering. I actually RTFA'd to see if the author had any sort of real statistics, but he really doesn't; the one thing that's presented as any sort of evidence is Netcraft's list of most reliable hosting companies for February, which is pretty meaningless. Sure, the top three are running FreeBSD, but every other company on the list is running Linux (besides number 9, which is running Windows Server 2003).

      Just to let you know I'm not disagreeing with you but I do think what you are saying needs to be highlighted given the number of times I have to deal with "BSD is X" nonsense from people who have absolutely abysmal math skills. Not only are you correct about the variability of the data but the netcraft chart is a weighted ranking of a number of metrics and while these may be perfectly reasonable for evaluating a hosting provider. None of them are intrinsically OS related and only two have to do with reliability. One of those two is the same for every system down to #30 (on the Feb 2011 data)! For example in Feb 2011 # 6 serverbeach (a Linux based provider) outperforms BSD (and everyone above it) in connect latency, first byte, total and kb/s. The only reason this is in #6 is because it's failed requests differs by 0.008%. While someone might argue that this difference is important in some context as we can see from the two samples you gave it's not entirely clear how much each one of these OS's vary. While I wouldn't necessarily expect the "best" os to always be in the top. I would expect that - over time - the variance in the data to be smaller. Without this, it's impossible to derive anything about the OS from the "failed req %" (assuming it isn't simply a function of completely irrelevant things like their upstream ISP's)

    30. Re:Sorry, but it's not worth the time by sarkeizen · · Score: 1

      Depends on what you need from ZFS. I've been using it under Linux for two years now. I don't have to use PPS for anything so I can't comment on that but considering that the context of the OP was "on the desktop" I'd think this is out of scope. Anyway Linux while doing a good job of being most things to most people. It's unlikely that anyone here is claiming it's everything to everyone.

    31. Re:Sorry, but it's not worth the time by Stewie241 · · Score: 1

      I thought he was going for this one: http://xkcd.com/974/

      Ian

    32. Re:Sorry, but it's not worth the time by Rogerborg · · Score: 1, Insightful

      You should give a modern Linux distro a try, they Just Work. I mean, obviously not the graphics drivers if you have anything even remotely non-mainstream, and for WiFi you should of course just use Windows drivers though ndiswrapper rather than wasting your time with native ones, plus "support" just means "that version is unlikely to get any more broken", and every time you click "allow update" you run the risk of breaking everything and ending up with a retard-o-interface, but other than that...

      --
      If you were blocking sigs, you wouldn't have to read this.
    33. Re:Sorry, but it's not worth the time by TheRaven64 · · Score: 2

      ZFS has a fsck tool, it's called zpool scrub. It verifies the entire filesystem - including the contents of the files, by validating the checksums - and repairs it. The grandparent's complaint was not about the lack of fsck, it was about the lack of a fsck tool 'that doesn't just tell you that your filesystem well and truly IS fscked'. Being told that your filesystem is damaged is no use, you want the fsck tool to fix it. ZFS usually doesn't need fsck because it does background repair and recovery automatically on a live filesystem, but you can force it to verify and repair the entire filesystem if you want to.

      --
      I am TheRaven on Soylent News
    34. Re:Sorry, but it's not worth the time by Bertrand+Wilmot · · Score: 1

      I'm currently responding to you from a FreeBSD installation, utilizing my 460 WHDI on my TV in another room. I used the default Xorg file + nvidia-settings. I had been playing lots of Minecraft on it... Anywho, it all took about one hour of actual interactive time to setup my FBSD box, so I really don't know what you're going on about. What exactly about FreeBSD is "harder?" The documentation is great and the configuration files are simple. Plus, ZFS! I've sometimes spent less time setting up FBSD or OBSD servers than some Linux installations. It's all about context.

    35. Re:Sorry, but it's not worth the time by Anonymous Coward · · Score: 0

      I call bull....

      ndiswrapper? How old is this advice?

      Non-mainstream? What, your homemade video card? NVIDIA, AMD, VIA and Intel out of the box, pal.

    36. Re:Sorry, but it's not worth the time by Anonymous Coward · · Score: 0

      Did you even RTFA? Venezia's only talking about FreeBSD on servers, not desktops. He even says, "Linux on desktops, FreeBSD on servers."

    37. Re:Sorry, but it's not worth the time by finarfinjge · · Score: 1

      So unless you code, where do you get your computer fun then? The feeling of boredom that avalanched over me as I read your post nearly kills my willing to live :(

      I'm assuming your were replying to me. What computer fun? My computer is a tool I use to work. When I feel the desire to procrastinate I post here. If computers are your source of fun . . . Sorry about that young fella. Also sorry about your 'willing'.

    38. Re:Sorry, but it's not worth the time by Anonymous Coward · · Score: 0

      Everything you just said proves his point. Linux doesn't 'Just Work' because it has to support so much.

      I'm not sure I completely understand your comment about support, but telling your system not to update in case it might break as a general rule is not a solution.

    39. Re:Sorry, but it's not worth the time by Vyse+of+Arcadia · · Score: 1

      and every time you click "allow update" you run the risk of breaking everything and ending up with a retard-o-interface

      Slackware, my friend.

    40. Re:Sorry, but it's not worth the time by Lawrence_Bird · · Score: 1

      I managed to get Xmonad working on an ancient nvidia car on two monitors without too much trouble. The initial config took minutes. I did not like the out of the box way the virtual screens would switch between the monitors and that did take some research but I would say hours, not days. Ultimately I could have lived with the default but it was nice to get it work exactly as I wanted it. While TFA was really just about bsd on a server (and I have one of those too) it is just as functional on the desktop as linux, at least for my needs. And I do agree that the small amount of time one spends getting the config down as you want it is worth it over the long run.

    41. Re:Sorry, but it's not worth the time by Anonymous Coward · · Score: 0

      Aw look at this. Somebody got their feelings hurt when bullshit was called. It made me feel bad too....wait that was just lunch.

    42. Re:Sorry, but it's not worth the time by m50d · · Score: 1

      I find I spend less time making freebsd work, because it doesn't keep changing how everything works. Gone is the linux experience of spending days of my life getting my sound working after the switch to alsa, and then getting my sound working again after the switch to pulseaudio (freebsd still uses OSS, and it works just fine thank you). Or spending days making my system work with devfs (it's the future, static /dev nodes are old and will be unsupported soon) and then whoops, devfs isn't even included in the kernel any more, got to spend more days making udev work. Or spending days to migrate my xorg configuration into hal, and then more days when hal gets removed. In all seriousness, I don't know how to set the keyboard layout for when X starts up any more, and I can't find out (I even asked matthew garret, and he told me to use GDM).

      --
      I am trolling
    43. Re:Sorry, but it's not worth the time by GeodesicGnome · · Score: 1

      I'm a big fan of Linux (heck, I'm one of the authors of Linux Appliance Design) but if you are looking for "Just Works", I think you have to give the nod to Apple. But they do this by limiting you. They control the hardware and restrict what can go into the App Store. And they pay a lot of attention to the "cool factor". Lots of eye candy. But the biggest benefit of going Apple is that everything pretty much works together out of the box. Phone, tablet, laptop and desktop cooperate nicely, as long as you are doing things the way Apple wants (such as, everything must be registered under one Apple Id if you want certain types of sharing to work right). I have multiple Linux boxes in my house, but do most of my work on my iMac desktop (where I have multiple Linux distributions available in virtualized environments.
      I do Linux software all day as my full time job. I find I'm just too lazy (and pressed for time) to struggle with Linux to get my VPN connection to work (this broke when I upgraded to a new Ubuntu release last year) and other things like this. I want the day to day stuff to just work so I can be free to concentrate on my latest Linux-based project. Apple lets me do this. Seems funny, but using Apple gives me more time for my pet Linux projects.

    44. Re:Sorry, but it's not worth the time by Jorl17 · · Score: 1

      I tried PC-BSD right before I tried Gentoo. Believe it or not, my first ever Gentoo was better than PC-BSD. Drivers for everything. Good guides. Decent configuration. No insane lock-ups. No ugly KDE. It just looked better, felt better and was better. God, I hate KDE, can't even look at it enough to get an alternative. (I don't run Gnome or XFCE or anything else either, btw).

      --
      Have you heard about SoylentNews?
    45. Re:Sorry, but it's not worth the time by Jorl17 · · Score: 1

      That's because you kept updating and recompiling your machine! Seriously, I'm a Gentoo user, so I do it very often, but I don't get why so many people need to pointlessly update their systems. When I used Ubuntu, I used LTS and when I needed a more up to date package I'd just build it myself. No full-system updates. No more "oh-noes-Pulseaudio-fucked-me".

      --
      Have you heard about SoylentNews?
    46. Re:Sorry, but it's not worth the time by prezkennedy.org · · Score: 1

      You're complaining about DRM schemes while at the same time running an Apple product? Does not compute.

      --
      It started back in Team Fortress Classic
    47. Re:Sorry, but it's not worth the time by synthespian · · Score: 1

      If you want version control on system [config] files, it is equally easy to put /etc in a git repository. Same benefits, but without relying on an obsucre file system.

      You planning on branching much your config files, are you? Heh.

      Oh, and I can push the same config files and their full mod history to every computer on the network. Can your fancy ZFS do that? I thought not.

      I don't think you need git for that...Your idea of what ZFS is for is not even worth commenting.

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
    48. Re:Sorry, but it's not worth the time by synthespian · · Score: 1

      Do you realize you're not actually very good on your Linux selling points? Basically, you've just said that things break all - the - time in Linux upgrades. And it's true.

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
    49. Re:Sorry, but it's not worth the time by mobby_6kl · · Score: 1

      The best part is that now Linux fanboys are using the same "arguments" that were used against their baby to attack BSD. "But why should I use BSD if Linux is almost as good", or "but my graphics card!". I'm glad my Android phone is my only point of exposure to Linux, wish it could be moved to NetBSD or something though.

    50. Re:Sorry, but it's not worth the time by Anonymous Coward · · Score: 0

      If you've got any real experience (like a week of use...) with FreeBSD, you know that FreeBSD is dead simple to use, has amazing documentation, and a very helpful user community. However, you literally can't install your first port without discovering that system tuning is automatic/done at compile time. Xorg is also the same between Linux and FreeBSD, again something that any real experience would teach.

      No longtime BSD user would have made any mistakes as the thread starter did with wasting hours tweaking the graphics card or the system. In fact, not even a week old newbie would make those mistakes. The thread starter poster revealed himself as a clueless, FUD-spreading troll.

    51. Re:Sorry, but it's not worth the time by Anonymous Coward · · Score: 0

      Paul's question, "why more folks aren't using FreeBSD on the desktop?" can be answered in two words: hardware support. My business partner is a huge proponent of BSD, and so am I... but the only on the servers.

      Unfortunately, syndeq (the submitter) is mistaken (perhaps deliberately so, who knows). Paul never asked that question. He was promoting BSD on the server.

    52. Re:Sorry, but it's not worth the time by Jorl17 · · Score: 1

      I'm not selling Linux. I'm selling my way of running and maintaining my desktop-based Linux OS. I really was agreeing that many distros (and even kernel patches) consistently break some feature or package that previously worked. What I don't get is why people keep doing these distro upgrades (or even radical package upgrades) and kernel recompiles. While I said that "I do it very often", I meant that I upgrade/rebuild (some of) my packages very often (not necessarily the kernel, I should've pointed that out). Now, when we get to a distro upgrade, most things just get changed -- massively -- and, indeed, many times it's worth reinstalling from scratch. I remember the last distro upgrade I watched was that of an Ubuntu 8.04 to 10.10. Not pretty at all. Let's just say nothing worked.

      --
      Have you heard about SoylentNews?
    53. Re:Sorry, but it's not worth the time by finarfinjge · · Score: 1

      Aw look at this. Somebody got their feelings hurt when bullshit was called. It made me feel bad too....wait that was just lunch.

      Earlier on in this thread someone made the claim that the people in the FreeBSD community were a bunch of arrogant arseholes (he was more polite than that). I was pointing out instances here of this attitude. Thanks for providing another prime example. You should read up on "irony". And posting as an AC to boot.

    54. Re:Sorry, but it's not worth the time by finarfinjge · · Score: 1

      The best part is that now Linux fanboys are using the same "arguments" that were used against their baby to attack BSD. "But why should I use BSD if Linux is almost as good", or "but my graphics card!". I'm glad my Android phone is my only point of exposure to Linux, wish it could be moved to NetBSD or something though.

      From what I've read on this thread, it is more "why should I use BSD when Linux is far superior". Nice attempt at redirection though. In case you are wondering, I dumped debian in favour of FreeBSD in 2001. I dumped FreeBSD completely in 2010. I use professionally produced (i.e. for pay) software now. These amatuer things were nice as a hobby but I have kids and a life now.

    55. Re:Sorry, but it's not worth the time by finarfinjge · · Score: 2

      If you've got any real experience (like a week of use...) with FreeBSD, you know that FreeBSD is dead simple to use, has amazing documentation, and a very helpful user community. However, you literally can't install your first port without discovering that system tuning is automatic/done at compile time. Xorg is also the same between Linux and FreeBSD, again something that any real experience would teach.

      No longtime BSD user would have made any mistakes as the thread starter did with wasting hours tweaking the graphics card or the system. In fact, not even a week old newbie would make those mistakes. The thread starter poster revealed himself as a clueless, FUD-spreading troll.

      I've got nine years experience with FreeBSD. I started at 4.7 and I stopped at 8.0. Maybe something radical has changed, but last time I looked, dead simple would be an outright lie. Documentation may be amazing, once you understand it. The handbook is ok. The rest, not so much. As for the user community. Have you read the posts from that community on this thread? Read your own post. If you are an example of a helpful community, I'd hate to see what you consider rude and obnoxious.

    56. Re:Sorry, but it's not worth the time by Anonymous Coward · · Score: 0

      I'll bite. What's "dumbed-down" about the Mac UI? What do other GUIs have that makes them "smarter"?

    57. Re:Sorry, but it's not worth the time by justin12345 · · Score: 1

      I was specifically talking about Window's Genuine Advantage, I should have been more clear. Apple is certainly guilty of some nasty DRM schemes, but they don't really effect me because I don't use the iTunes store, and I deleted the App Store as soon as I noticed it on the doc. I'm only talking about the fact that OS X doesn't hassle me upon installation like Windows does.

      --
      Cool art gallery, if you're into that sort of thing.
    58. Re:Sorry, but it's not worth the time by Anonymous Coward · · Score: 0

      You championed and tried to use it "for serious use", when you knew it was in development and unstable? Well you're a moron then.

      I did not claim btrfs is stable right now, idiot; I refuted the incorrect assertion that it is stagnant and "still born" (whatever that means??).

      Btrfs is being very actively developed, is looking set to become default filesystem for several of the next round of distros, and is looking promising. It is slower than ZFS in a number of situations, and it is faster in another number of situations. Btrfs has features that ZFS does not (shrinking still not implemented, is it??), and ZFS has some that btrfs does not. That does not make one or the other "stillborn" or "stagnant"!

      Back when btrfs was first being announced, all the naysayers were moaning about what's the point of starting a new filesystem when ZFS has everything, everybody will be migrating to solaris anyway, it's going to take way too long, blah blah blah. And now it's close to becoming stable and generally usable, and people are still complaining. So you obviously do not know about btrfs.

    59. Re:Sorry, but it's not worth the time by Anonymous Coward · · Score: 0

      Scrubbing is not fsck. If you don't know that, you shouldn't be commenting here.

      fsck is a tool to verify the consistency of, and repair the filesystem's data structures (its metadata).

      Scrub is a tool which detects checksum errors in blocks and attempts to correct them with available redundancy.

      Two completely different things.

    60. Re:Sorry, but it's not worth the time by TheRaven64 · · Score: 1

      Fsck is a subset of scrub. Scrub checks and repairs the metadata and the data. It doesn't just verify at the block level, it verifies all of the data structures. Fsck checks and repairs the metadata. Well, normally it does, fsck for btrfs just checks it and then says 'sorry, your filesytem is broken. Sucks to be you.'

      --
      I am TheRaven on Soylent News
    61. Re:Sorry, but it's not worth the time by Anonymous Coward · · Score: 0

      Congratulations, you start your whole comment with a failure of reading comprehension. I didn't say that I personally used BTRFS for serious use, I said that it was unsuitable for serious use. When I first got involved with BTRFS, my own tests revealed gaping flaws in the filesystem that absolutely had to be fixed before serious use could even be contemplated. Several of these flaws have already been announced as flaws that will not be fixed, such as the enormous amount of in-system fragmentation that BTRFS accumulates, and four years in, there is still no working fsck that can actually FIX a broken BTRFS file system.

      I don't doubt that BTRFS is still being developed, as I still track their project commit logs. Too bad the progress is postively glacial, and a favorite hobby of BTRFS devs appears to be rejecting patches that would help the project move forwards. So I feel that stillborn and stagnant are excellent descriptions.

      And as for the whole nonsense about becoming default in the future, if you do some reading, you'll discover that enterprise users won't even touch it without FSCK. The feature set is also smaller than ZFS and less compelling. I will concede a point with the fact that zfs has not implemented pool shrinkage as a direct, single use command. However, a number of simple documents have been written that simply describe both ZFS send and zpool modification resize methods. Personally, in this age of expanding disk drives, I find the ZFS shrink problem a total red herring compared to BTRFS's fragmentation (fragmentation?! In 2011?! WTF!?) issues, total lack of fsck, slow performance, hostile developers, glacial progress and overall suckage.

      I stand by my posts with confidence. Yes, I do know quite a bit about both ZFS and BTRFS. You, on the other hand, appear to have major reading comprehension problems. Try reading and understanding my post next time, mmmkay?

    62. Re:Sorry, but it's not worth the time by Anonymous Coward · · Score: 0

      I remain enormously skeptical that you spent even remotely anywhere near that amount of time running FreeBSD, unless if, of course, your definition of 'dead simple' is that it works exactly like Windows or OS X, where everything has been set up and done for you ahead of time. Furthermore, I remain shocked at how it would even be possible for you to use FreeBSD so long and to not know that system tuning is largely automatic.

      As for user community, it's great for people who actually want to learn. I'm bringing facts to the table, facts any 10 year FreeBSD user would know enormously well. You're spreading FUD and trolling. I don't tolerate trolls.

  4. Gnome 2 and KDE 3 by water-and-sewer · · Score: 2

    I dual boot my Linux desktop, and spend a lot of time in FreeBSD (I used PC-BSD, which installs pretty easily). These days, one of its advantages is that you can still have a KDE3 or Gnome2 desktop - worth it indeed!

    --
    If this were Usenet, I'd killfile the lot of you.
    1. Re:Gnome 2 and KDE 3 by couchslug · · Score: 1

      "These days, one of its advantages is that you can still have a KDE3 or Gnome2 desktop - worth it indeed!"

      There are plenty of other desktop options which are lighter and faster than either of those. Not worth it to me.

      --
      "This post is an artistic work of fiction and falsehood. Only a fool would take anything posted here as fact."
    2. Re:Gnome 2 and KDE 3 by Chris+Mattern · · Score: 1

      These days, one of its advantages is that you can still have a KDE3 or Gnome2 desktop - worth it indeed!

      Because having desktop software that's been superceded and will lose all support is so much fun! Bah. Give me Xfce--which not only runs perfectly well on Linux but has an Ubuntu variant devoted to it.

    3. Re:Gnome 2 and KDE 3 by Bertrand+Wilmot · · Score: 1

      Wait, I'm confused; FBSD also has support for KDE3 and Gnome2. I haven't used Gnome or KDE in years, but I know these are "legacy/classic" versions, before they turned to shit. Praytell, are you suggesting that Linux or FreeBSD can't use KDE3 & Gnome2, but PC-BSD can?

    4. Re:Gnome 2 and KDE 3 by synthespian · · Score: 1

      People looking for a leaner desktop should rally, really check out enlightenment.

      It is really decent, it's not like the rest (half-ass geek jobs) and it's robust (if it crashes for whatever reason, it recovers). /usr/ports/x11-wm/enlightenment

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
    5. Re:Gnome 2 and KDE 3 by DCFusor · · Score: 1
      That's a big one. I don't care about the resource usage - I just like Gnome2 customized the way I like it, and have habituated to it to where it's effortless and takes no fishing around to get every job I have done, fast. I'm still on U10.04, and have been looking where to go next, since Canonical obviously has their head up their ass. I DO NOT NEED OR WANT a tablet for my quad 24" screen desktop. I'm a market trader looking at slowly changing plots, and about 200 tickers, trade by trade, all day - when I'm not programming for my physics hobby. I do not approach the computer not knowing what I want to do with it, ever - that hard to discover but suggestive new interface is in my way, not helpful one bit, and non configurable in every way I care about.

      I do not need or want all this fancy bling wasting pixels I paid to use. I do need reasonable hardware support, and rock solidity - which I now get from ubuntu 10.04, though the kernel doesn't support the trim command for my SSD (and don't tell me to backport the newer one - it breaks a bunch of other apps here). And as time goes on, less and less new stuff will be supported on it, so I can't just stick in the mud and keep this version forever. Guess what? Linux has lockin too! This sucks, Canonical!

      I finally got a machine just the way I want it. I don't really want to change anything, just use it and write more useful software for it. The apple guy above who says he can just drop back a version - he's going to find out quicker than I that a lot of things he depends on will stop working if he tries that in his walled garden - even more walled than mine or microsoft's. He'll get that "please upgrade to a newer version to support this feature (which he may have paid for or for media on) because the older version makes it too easy to escape the garden, so we won't support what you want on it anymore. Count on it.

      --
      Why guess when you can know? Measure!
    6. Re:Gnome 2 and KDE 3 by epine · · Score: 1

      I second the motion, but with half the pixels. That's why I'm crawling this thread in detail, because I'm looking for a way out of 10.04. I'm sure it will end up being OpenCL that's the FreeBSD deal breaker.

    7. Re:Gnome 2 and KDE 3 by Anonymous Coward · · Score: 0

      No, he is saying he is too stupid to find a way to install the forked and maintained version of KDE3 (you can find an Ubuntu PPA for Trinity quite easily with Google) and for some reason can't use a slightly old, but still supported Linux distro for GNOME 2 until the Mate project (a for of GNOME 2) makes a release.

    8. Re:Gnome 2 and KDE 3 by Anonymous Coward · · Score: 0

      There is a fork of GNOME 2 that is in development, I expect they'll have a release with an Ubuntu PPA in time for the next LTS. Otherwise XFCE is a good alternative.

  5. How?? by tetrahedrassface · · Score: 0

    How can you run it if it's dead?

    1. Re:How?? by tomhudson · · Score: 1

      How can you run it if it's dead?

      Zombies. Oh wait, that would infringe Microsoft IP ...

  6. m-( by Lazy+Jones · · Score: 3, Insightful

    tl;dr - guy uses 10 years old hardware and wonders why an OS that works fine for him doesn't appeal to everyone else...

    We switched our last servers from FreeBSD to Linux about 10 years ago because FreeBSD had crappy SMP support. Seriously, why does something like this get posted to /.?

    --
    "I love my job, but I hate talking to people like you" (Freddie Mercury)
    1. Re:m-( by kriston · · Score: 0

      +1 on the SMP support.
      Even the deader-than-dead NetBSD runs circles around FreeBSD when it comes to SMP support.

      --

      Kriston

    2. Re:m-( by Entrope · · Score: 1, Offtopic

      These stories get posted so that people have threads where they can say "Netcraft confirms: FreeBSD is dead" ... and have it be remotely on topic.

    3. Re:m-( by gentryx · · Score: 1

      I'd mod this post "+1 informative" if I had resisted posting prior to reading this.

      --
      Computer simulation made easy -- LibGeoDecomp
    4. Re:m-( by Anonymous Coward · · Score: 0

      Because it was posted earlier on OSNews

    5. Re:m-( by Entropius · · Score: 1

      Wow -- not a BSD user, but isn't basically every non-netbook computer (and some of those) sold these days multiprocessor?

    6. Re:m-( by hedwards · · Score: 2

      I'd mark you troll if I hadn't already posted in this particular thread. It's been 10 years, there has been substantial work on SMP in the interim. I did take a quick look to see if there were any comparisons of the two and couldn't find any that were even remotely recent. The most recent being FreeBSD 5 and 6 against a Linux kernel 2.6+, which is hardly recent enough to consider current.

    7. Re:m-( by LWATCDR · · Score: 1

      Not to be mean but I do have wonder about this statement. "Sure, it's quicker to build a Linux box, do a "yum install x y z" and toss it out into the wild as a fully functional server, but the extra time required to really get a FreeBSD box tuned will come back in spades through performance and stability metrics."

      What if you spend that extra time to also tune the Linux box. I am not a BSD hater but last time I checked Linux had better support for SMP and in my experience it has been very stable and performs very well.
      Not to say that BSD is a bad choice. FreeNAS runs on it and FreeBSD also supports ZFS which are both pluses IMHO but I just don't know if one can say that it is a "Better" choice than Linux for the desktop or server.
      And no I really do not want to start a flame war but I do have to wonder.
      Frankly a good reason to use FreeBSD over Linux is that "It is secure, it works, and I know it." The same is true for OpenBSD, and Linux IMHO.

      Oh and DragonFly BSD is supposed to be fixing SMP. I have a bit of fondness for Matt Dillion. He was involved in the Amiga community at the same time I was.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    8. Re:m-( by TheRaven64 · · Score: 3, Informative

      It's also nonsense. The ULE2 scheduler in FreeBSD has very good SMP support. Up to 8 cores, it gives a pretty linear speedup on the MySQL benchmarks I saw. Allegedly it should continue to scale well up to at least 64 cores, but I've not seen any real tests on bigger machines. This has been true since FreeBSD 7, although SMP performance improved a lot in the 8-9 window.

      --
      I am TheRaven on Soylent News
    9. Re:m-( by the_humeister · · Score: 4, Informative

      Could you elaborate?

      I have an AMD 1090T (6 cores @ 3.2 GHz) that I've run FreeBSD 8.2 and Debian 7 on. I run Povray 3.7, which is multi-threaded (compared to the prior version which was not), on this machine and was testing out OSes. Using the latest gcc version for each OS (4.6), it turns out running on FreeBSD is about 15% faster than on Debian running the standard benchmark:

      FreeBSD 8.2, gcc 4.6, -march=barcelona

      Render Time:
          Photon Time: 0 hours 0 minutes 2 seconds (2.390 seconds)
                                  using 9 thread(s) with 2.763 CPU-seconds total
          Radiosity Time: No radiosity
          Trace Time: 0 hours 3 minutes 10 seconds (190.466 seconds)
                                  using 6 thread(s) with 1113.568 CPU-seconds total

      Debian 7.0, gcc 4.6.1, -march=barcelona

      Render Time:
          Photon Time: 0 hours 0 minutes 2 seconds (2.277 seconds)
                                  using 9 thread(s) with 2.648 CPU-seconds total
          Radiosity Time: No radiosity
          Trace Time: 0 hours 3 minutes 38 seconds (218.326 seconds)
                                  using 6 thread(s) with 1277.363 CPU-seconds total

    10. Re:m-( by TheRaven64 · · Score: 2

      There are some benchmarks of FreeBSD 7 against Linux of the same era (that graph includes the version of Linux that was specifically released after the previous set of benchmarks showed FreeBSD beating Linux by even more). Both Linux and FreeBSD have improved in SMP support since then, so I don't know how they compare anymore. I suspect that both are in the state where the kernel is not likely to be the cause of any scalability issues that you encounter.

      --
      I am TheRaven on Soylent News
    11. Re:m-( by SirDice · · Score: 1

      You do realize SMP support had been significantly reworked in 5.0 (released in 2003)? And it has seen some impressive improvements since.

    12. Re:m-( by rev0lt · · Score: 1

      Opinions may vary. About a year ago, I benchmarked postgresql on a quad-core xeon, with freebsd 8.1, freebsd-zfs, centos 5.4 and netbsd 5.0. Netbsd performance was less than 1/4 of freebsd, and centos 5.4 was the clear winner. I never run all the tests on netbsd, because the battery of tests that had taken around 12h in freebsd would take about a week on netbsd.

    13. Re:m-( by tomhudson · · Score: 1

      What if you spend that extra time to also tune the Linux box.

      Since the article is about running FreeBSD on a desktop, here's the situation under linux. Your patch will break the next update. Or the next update will break your patch. Or the next update will break even if you don't patch.

      It's getting to the point that you have to do a clean install instead, because updates don't play nice with your existing wifi, video, or sound configuration, but a fresh install will still work ... mostly.

    14. Re:m-( by Anonymous Coward · · Score: 0

      No, it's not nonsense: for a long time, FreeBSD's SMP support was horribly sub par for servers.

      FreeBSD still is barely getting some support for NUMA memory allocation, which is pretty important even for medium servers these days (eg. 4/8 socket).

    15. Re:m-( by LWATCDR · · Score: 1

      That has never happened to my systems. Now it is a small sample but maybe you should try a modern stable distro and not one that is cutting edge. i will admit that I do not understand why anyone runs a server on Fedroa when Centos, Ubuntu Server, and Deban are available.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    16. Re:m-( by Anonymous Coward · · Score: 0

      PC-BSD is a quite nice desktop OS. The problem is the same old story though. Hardware support just isn't there. If Linux is a second rate citizen in hardware support, BSD is fifth or sixth.
      I use laptops for computing. Here's my BSD experience on each: My newest Samsung hangs on booting. My newer EEE PC doesn't support WiFi. My older EEE PC crashes on suspend (yes, I can't even SSH in, because networking is disabled on suspend). My original EEE PC doesn't have enough space (4GB ain't much!). However, I am running in the order mentioned: Debian, Linux Mint, Ubuntu, and a hand-tuned SUSE (took an afternoon on susestudio). No hardware problems (save for low power graphics on the Samsung) and all the soft keys just work. SUSE is the only thing I invested any time on and that was purely for consideration of space.

      Sure, I could spend weeks sorting out the hardware problems on BSD, hacking together scripts, but I bet I'd still be making compromises such as shutting down instead of suspending. Any performance gain would be so negligible it wouldn't be worth the time I would lose with my family.

    17. Re:m-( by Anonymous Coward · · Score: 0

      Are these results published online anywhere?

    18. Re:m-( by rev0lt · · Score: 1

      I am a FreebSD user, and most of my work envolves BSD setups.
      For most of what I've benchmarked, CentOS 5.4 is faster out-of-the-box than a tuned FreeBSD install. Upon resurce starvation, I find FreeBSD much more stable and easier to recover to a running state. Also, tools like zfs and jails allow me to be able to do more with the machine, and even improve the maintainability of the system. The ports infrastructure is not perfect, but does a good job at it, and I often get less garbage when upgrading packages in freebsd than on linux.
      The stability argument is moot nowadays, as I find a CentOS or Debian install as stable as FreeBSD (and forgeting the crappy unstable mess that were the 5.x releases. Most of the arguments against linux or freebsd used in the past arent valid today -as an example, linux has a ton of crappy drivers, freebsd still has a ton of unsupported hardware. Regarding 3D acceleration linux is somewhat far ahead, but behind other operating systems.
      I don't play around much with DragonFly, but I think the direction they're heading is grid computing, and not necessarily SMP. The project implements some interesting concepts, and are one of the few operating systems actually trying something "new", and for that they deserve all the merit they can get.

    19. Re:m-( by kriston · · Score: 1

      No, it's not nonsense: for a long time, FreeBSD's SMP support was horribly sub par for servers.

      FreeBSD still is barely getting some support for NUMA memory allocation, which is pretty important even for medium servers these days (eg. 4/8 socket).

      QFT.

      --

      Kriston

    20. Re:m-( by Anonymous Coward · · Score: 0

      That benchmark will have basically zero kernel interaction, so it is not a test of kernel SMP scalability.

    21. Re:m-( by LWATCDR · · Score: 1

      I actually just downloaded DragonFly to try it out.
      For me the answer would be Ubuntu Server or Centos. Both have worked well for me and the big thing is I know Linux much better than I know BSD.
      For the most part I would say that both are good choices depending on the user. Of course ZFS is really interesting and I have heard about Jails but have never used them.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    22. Re:m-( by jasno · · Score: 1

      You'd mark him a troll for saying something incorrect that you disagree with? Can we get an admin to take this guy's mod points away? He's not a troll. Please learn the difference before you moderate again.

      --

      http://www.masturbateforpeace.com/
    23. Re:m-( by Galactic+Dominator · · Score: 1

      He'd mark the OP troll for lying. Please learn to read before you comment again.

      --
      brandelf -t FreeBSD /brain
    24. Re:m-( by synthespian · · Score: 1

      Search for academic papers of package management. You'll find evidence that's not anecdote - actually registered and tracked - of a Debian system that uninstalled kernel packages when asked to update something else, because apt went haywire on dependency hell.

      I really don't have a reference for you, it was years ago.

      Anyway, bsd make does a topological sort on dependencies. My guess on why things seem to break much less than when I used Debian, is because, since the graph can have many topological sorts, and I am not tool-bound to do things a certain way, I can fix stuff if things go awry attempting another approach. If in Debian there's apt, in FreeBSD there are more tools. The package database is just a package database. It's not a Central Dogma. People are free to design and create what they feel are better tools - and a few have done so - and that's why we have more choice in FreeBSD. Another aspect I like is language diversity. It seems FreeBSD developers are much more open to accept other programming languages, as long as the tool works. Nobody says, for example, you can't use Ruby because a central committee disapproves of it (OpenBSD, in this respect, I don't like - they seem much to stuck on C).

      If nothing else works, then it boils down to Makefiles (which is what ports are about, anyway). There's none of that Package Wall...In Linux distros with package management, the only way not to break things is sometimes not having the latest and greatest software.

      But today's FreeBSD port tools are so good that the corner-cases are rare (I have never had stuff that absolutely refused to work, like in Debian).

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
    25. Re:m-( by synthespian · · Score: 1

      Sure, the hardware/laptop situation is worse in FreeBSD, but can't you do a bit of cherry-picking when you are shopping for a new laptop? Or is it really a fact that no-one uses FreeBSD on a laptop?

      Notebooks are tricky, they have lots of brand new hardware and even Linux is a liability if your not careful. Most of them are made to work with Windows, you know that...

      My laptop 3D acceleration is buggy sucks and the system uses less bits for color than Windows 7 would use. Should I conclude that Linux sucks? If that is the criterion, then the only decent Unix for laptops is Mac OS X.

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
    26. Re:m-( by synthespian · · Score: 1

      s/your/you're/ goddamn English phonetics...

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
  7. because costs by Anonymous Coward · · Score: 1

    The maintenance involved easily costs $50/hr.
    An i7 costs $300.

    Why finetune and keep maintaining a software system for thousans of dollars when you can just dish out a few hundreds and get a faster CPU?
    I was all for finetuning, Gentoo, LFS, even played with BSD. But when I run the math on how much it costs me (from a time/lost profits perspective), I quickly reverted to Debian and bought me a beefier PC.

    Sure, playing around with an OS and finding out more about it as fun, but let's just keep it in perspective. For low/mid systems (like the ones we all use at work/play), the effort is not worth the gains.
    The scales tip when we're referring to systems that cost significantly more (10's of thousands of dollars), and most of us would rather snuggle with such them rather than maintain it.

  8. Hardware Failure Mitigates OS Stability by bengoerz · · Score: 3

    The author himself gives the reason: "Right up until last week, this FreeBSD box had an uptime of 1,057 days, or nearly three years. This streak was broken only due to a UPS failure during a brief power outage... And this box has been rock-solid stable the entire 10 years, with only a disk failure or two in the middle." Considering hardware failure will eventually bring down the machine anyway, there's little to no difference in uptime between a "rock solid" BSD install versus a "also-solid" Linux install.

    1. Re:Hardware Failure Mitigates OS Stability by dreemernj · · Score: 2

      And individual stories like his three year uptime server are worthless. I have a server in a closet running Windows 2000 Server. It is in constant use by hundreds of employees and its uptime is over a thousand days right now. It too has only really had issues with a UPS failure at a bad time. And it hasn't had any drives die since it was installed in 2001.

      Does that mean Windows 2000 Server is better than Linux or FreeBSD? No! It means that anecdotes like these aren't helpful at all.

      --
      1 (short ton / firkin) = 89.1432354 slugs / keg
    2. Re:Hardware Failure Mitigates OS Stability by Archangel+Michael · · Score: 3, Insightful

      1) Three Year Old Server, is time to retire the hardware, and replace it with new equipment.

      2) Same box for 10 years, sounds like disaster waiting to happen (Hardware wise), and I surely wouldn't want anything mission critical on it.

      3) Ten year old box is a PIV era machine, with perhaps 3.6 GB ram, my current laptop has more power and ram and could run that machine in the background in a VM.

      4) A single UPS failure shouldn't break mission critical server, as they would have dual power supplies and run on independent Power circuits, with generator backup.

      However after reading #1 and #2 you realize that this is a theme that is building. THAT is why people don't believe these types of trolls.

      --
      Agent K: A *person* is smart. People are dumb, stupid, panicky animals, and you know it.
    3. Re:Hardware Failure Mitigates OS Stability by FoolishOwl · · Score: 1

      Three years of uptime is good for a server, but bad for a desktop. Unless that desktop is also functioning as a server, it really ought to be shut down when not in use for more than a few hours, or at least be put in sleep or hibernation mode. It's irresponsible to burn energy to keep a computer running when it's not actually being used, and a fetish for long uptimes is not a good justification.

    4. Re:Hardware Failure Mitigates OS Stability by Anonymous Coward · · Score: 0

      "Right up until last week, this FreeBSD box had an uptime of 1,057 days, or nearly three years.

      I wonder if American days are shorter than elsewhere or are there just more of them crammed into a single year?

    5. Re:Hardware Failure Mitigates OS Stability by sciencewhiz · · Score: 1

      3 year uptime on a Windows server means your server is 0wned.

    6. Re:Hardware Failure Mitigates OS Stability by Anonymous Coward · · Score: 0

      A thousand days? Do you never patch that box?

    7. Re:Hardware Failure Mitigates OS Stability by Anonymous Coward · · Score: 0

      5. If you're running a box for over 6 months without rebooting the kernel to patch security issues, you're probably either running a cool-but-dodgy live kernel patching setup, or you're not taking security seriously enough.

  9. Not-that-useful info by Anonymous Coward · · Score: 0

    I'm not saying I wish to argue with the article's position, but saying "You'll get better performance out a finely-tuned install of X than a generic install of Y" isn't really all that useful; with enough effort for X=Windows Server and enough sloppiness for Y=Some-Flavor-Linux Server, this still is true; that doesn't mean I'm saying Windows Server is the best choice.

  10. It's the software by Hatta · · Score: 1

    FreeBSD ports just aren't as comprehensive as Debian's repository.

    --
    Give me Classic Slashdot or give me death!
    1. Re:It's the software by Anonymous Coward · · Score: 0

      Not only that but stuff like virtualization software just isn't available for the *BSD's. Virtualization is critical for any desktop these days.

    2. Re:It's the software by Anonymous Coward · · Score: 0

      Sure, because git 1.5.6 on my debian box is a +1 to the debian package count.

      Personally I'd prefer a smaller list of maintained packages than a large list of abandonware.

    3. Re:It's the software by rev0lt · · Score: 1

      There is desktop virtualization - VirtualBox. Also, some versions of vmware workstation used to run on it, don't know if it still is an option. For unix-stuff prototyping and development, I find jails far more versatile and fast than some VM running on a desktop. Granted, I don't need X (though you can install it on a jail with some tweaks), but works for me.

    4. Re:It's the software by Hatta · · Score: 1

      $ git --version
      git version 1.7.7.2

      If you want current software, run unstable.

      --
      Give me Classic Slashdot or give me death!
    5. Re:It's the software by koinu · · Score: 1

      I am not sure, if this is really true. FreeBSD ports collection is the number one argument for me to stay on this platform. I've got over 20,000 ports and can compile them with a huge amount of settings.

      You cannot even compare Debian packages with FreeBSD Ports.

    6. Re:It's the software by TheRaven64 · · Score: 1
      Really? I replaced my colocated server with a FreeBSD Xen DomU. Virtualisation is working there. On the FreeBSD-hosted side, I have several options:
      • For lightweight virtualisation, there are jails, which can be created with a ZFS clone in about 2 seconds, and let you create a new root account and do anything you could in a real FreeBSD system except modify the kernel.
      • For real virtualisation there's BHyVe, roughly similar to KVM on the Linux side.
      • For desktop virtualisation there's VirtualBox.

      What's missing? We have lightweight containers, paravirtualised instances, and full system virtualisation. About the only thing I can think of is Xen dom0 support, and that's hardly a requirement for most desktops (and is coming soon)...

      --
      I am TheRaven on Soylent News
    7. Re:It's the software by TheRaven64 · · Score: 1

      FreeBSD doesn't tend to split things up as much as Debian. For example, on Debian I have to install two packages for every library - one for the library and one for the headers. Often the documentation is another package. A GCC version is about a dozen packages on Debian, but only one on FreeBSD. Debian also has a habit of giving packages stupid names (e.g. libobjc2 is not libobjc2, it's an old version of gcc libobjc, the new llvm-gcc packages are not llvm-gcc at all, they're DragonEgg, which is a completely different project).

      --
      I am TheRaven on Soylent News
    8. Re:It's the software by wagnerrp · · Score: 1

      Virtualization is critical? Unless you want to run applications on a different operating system, or want to sandbox machines for development, what purpose could a desktop user possibly have for virtualizing anything?

    9. Re:It's the software by synthespian · · Score: 1

      Before VirtualBox, there used to be 2 virtualization softwares for desktop FreeBSD. One was Win4BSD, from Virtual Bridges. They have redone their product line, and that product is no more, I think. And there was another product too, but I forget.

      Anyways, VMWare works with FreeBSD too: http://www.vmware.com/support/ws55/doc/new_guest_tools_ws.html

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
    10. Re:It's the software by synthespian · · Score: 1

      If you want current software, run unstable.

      If you want current software on a stable system, trash that Debian unstable and run FreeBSD.

      (over 20,000 ports frequently updated)

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
    11. Re:It's the software by synthespian · · Score: 1

      Not to speak of tiny useless packages that were the rite of passage of many Debian "developers".

      At least, on FreeBSD, the ports count is honest and not just jive...

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
    12. Re:It's the software by Anonymous Coward · · Score: 0

      Except that it is. Ports just doesn't inflate numbers by separating libraries into foo and foo-devel (both would be one port, as opposed to being counted as two different packages as in Debian), and iirc Debian's package count includes all three branches (stable, unstable and testing), whereas a port is only counted once, regardless of how many branches are supported.

    13. Re:It's the software by arose · · Score: 1

      Better, Debian has actual security upgrades instead of just pulling the latest version, incompatible changes and all.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    14. Re:It's the software by koinu · · Score: 1

      Don't know if you are lying (trolling) or simply have not read the manual (stupid).

    15. Re:It's the software by arose · · Score: 0

      Well, enlighten me, how do ports not pull new versions of software. Where does one specify to use security backports? Oh, hell, just post something besides accusations!

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    16. Re:It's the software by arose · · Score: 1

      And if you want to run a stable, full featured, system that doesn't upgrade half of the system then... and so on.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    17. Re:It's the software by Hatta · · Score: 1

      Unstable refers to the repository; it's always changing. The system itself is rock solid.

      --
      Give me Classic Slashdot or give me death!
  11. FreeBSD is not virtualiztion aware. by Anonymous Coward · · Score: 0

    Linux does better in a virtualized environment that FreeBSD does, especially in file access, because Linux's kernel is visualization aware and FreeBSD's is not.

    1. Re:FreeBSD is not virtualiztion aware. by TheRaven64 · · Score: 2

      What kind of nonsense are you spouting? FreeBSD has paravirtualised disk and network drivers for Xen and runs very well as DomU. Dom0 support is a bit less good, but if you want to run FreeBSD guests on a FreeBSD host there is BHyVe.

      --
      I am TheRaven on Soylent News
    2. Re:FreeBSD is not virtualiztion aware. by synthespian · · Score: 1

      I think you're framing things the wrong way... "A has this tools, and I can do X with it. Do you have X? Than you can't do X. Therefore, I conclude you suck." No, can't do X, but can do Y, which is equivalent to X, except it relies on B, which you never admitted in your premise.

      I'm not a sysadmin, but I guess that If a FreeBSD admin wanted lots of "images" he would create lots of "jails".

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
  12. 12 years with freebsd on the desktop... by Anonymous Coward · · Score: 1

    Been using FBSD for past 12 years on my desktop... recently switched to CentOS 6 because of stability problems with the nvidia driver.

    What you have to understand about fbsd is that it is a server operating system. They put NO effort into it working on the desktop.

    The installer is text-based. If you installed X during the install, it is out of date. You will configure X from the terminal. If you install KDE or GNOME, you should know FBSD did no work on fixing any bugs (and there are a TON of bugs).

    You will never see a desktop feature as part of the improvements in a release.

    The community is hostile to new users.

    If you really wonder why people don't use FBSD on the desktop, try it. You'll figure it out within an hour.

    1. Re:12 years with freebsd on the desktop... by Jorl17 · · Score: 1

      Yeah, I figured within an hour too, but with PC-BSD. Strangely enough, spent the following week installing my first-ever Gentoo. Even more strange: I've never looked back; now my installs take around 1-2 days, and that's if I really want it to look and work MY WAY.

      --
      Have you heard about SoylentNews?
  13. Numbers? by Anonymous Coward · · Score: 1

    I've been hearing continually for years about how BSD performs so much better and is superior to linux in every way--but i have yet to see anyone actually post some hard data to back this up. It'd be nice for someone to actually find some way of quantifying this--or to just admit it's a philosophical difference and be done with it (yes, i know, that'll happen about the time that the universe suffers heat death)

  14. Hostile community by hessian · · Score: 1, Interesting

    The FreeBSD community takes a "blame the user" stance that is going to alienate most desktop users, who want to use the machine to get something done and don't want to be held up by snafus that may take days to fix.

    Much of BSD's documentation is wrong or vague, many things are still broken within the OS and especially in the parts a desktop user would use, and when there is a problem, there's nowhere to go for a clear, quick solution.

    A friend of mine installed FreeBSD on some older hardware and couldn't get the mouse to work. After two weeks of back-and-forth on the mailing list, someone else chimed in that they had the same problem... and then another... and another. It turned out that for the previous for years the FreeBSD community had been screaming "RTFM" at people, when the error was actually in the FreeBSD code.

    Most desktop users are going to prefer Linux or Windows, despite the decreased efficiency, because they work and when you have a problem, there are multiple resources so that you can resolve it quickly. With FreeBSD, a broken driver may require 30 minutes to fix, or 48 hours of solid hacking. If you're trying to use your computer to do something unrelated to the operating system, that's too painful of a loss of time.

    1. Re:Hostile community by Anonymous Coward · · Score: 0

      The FreeBSD community takes a "blame the user" stance that is going to alienate most desktop users, who want to use the machine to get something done and don't want to be held up by snafus that may take days to fix.

      Can you be more specific ? I have a subscription on several mailing lists and I see people asking questions and being helped all the time. Same on the FreeBSD forum.

      Much of BSD's documentation is wrong or vague, many things are still broken within the OS and especially in the parts a desktop user would use, and when there is a problem, there's nowhere to go for a clear, quick solution.

      Can you give an example of broken things and bad documentation ? I find the documentation rather thorough and easy to understand. Maybe a bit to technical, but neither wrong, nor vague.

      And you know, sometimes it's actually a RTFM problem after all.

    2. Re:Hostile community by Danzigism · · Score: 1

      after using FreeBSD for over 10 years, I've never once seen "FreeBSD code" cause problems with a mouse not working.

      --
      *plays the Apogee theme song music*
    3. Re:Hostile community by finarfinjge · · Score: 1

      The FreeBSD community takes a "blame the user" stance that is going to alienate most desktop users, who want to use the machine to get something done and don't want to be held up by snafus that may take days to fix.

      Can you be more specific ? I have a subscription on several mailing lists and I see people asking questions and being helped all the time. Same on the FreeBSD forum.

      Much of BSD's documentation is wrong or vague, many things are still broken within the OS and especially in the parts a desktop user would use, and when there is a problem, there's nowhere to go for a clear, quick solution.

      Can you give an example of broken things and bad documentation ? I find the documentation rather thorough and easy to understand. Maybe a bit to technical, but neither wrong, nor vague.

      And you know, sometimes it's actually a RTFM problem after all.

      I dumped FreeBSD for a number of reasons. Required to upgrade due to some security thing, Oh wait, some obscure library has also updated and now the entire OS needs to upgrade. And KDE too. WTF? When did Gnome get installed? Ah well, I wasn't going to use the computer this week anyway. One week later, nothing works, so I go to the mailing lists. First responses are usually "It's in UPDATING, come back when you've read that." If you haven't seen the snide, arrogant crap that happens on the mailing lists you are not paying attention. (mailing lists? are your reading what you are typing? mailing lists? This isn't 1988.) And yes, there are a large number of parts of the base OS (not the ports) that have crap documentation. And RTFM? If you need to RTFM to install software and keep a system running, the system is crap. I've switched to a Mac and Windows 7. Haven't had to R any FM since. No. FreeBSD is not a desktop system. If you want it to do useful things, don't install a gui and try to limit yourself to the base OS. Do everything from the command line. Aint that quaint. Otherwise, run away.

    4. Re:Hostile community by Sancho · · Score: 1

      Though there have been times where the keyboard didn't work. USB keyboard, FreeBSD 6ish (two releases iirc), on the installer disk. You had to toggle something in the boot menu, or else the keyboard wouldn't work once you got into the installer.

    5. Re:Hostile community by Anonymous Coward · · Score: 0

      Congratulations on running FreeBSD for over 10 years with keyboard commands. Come out of your mother's basement and have some cake.

    6. Re:Hostile community by nurb432 · · Score: 1

      The FreeBSD community takes a "blame the user" stance that is going to alienate most desktop users, who want to use the machine to get something done and don't want to be held up by snafus that may take days to fix.

      Funny, that is one of the reasons i personally left the Linux camp long long ago and i was there from the beginning ( and I'm mean the VERY beginning, when it was still incapable of self-hosting ). A bunch of elitist jerks slowly appeared destroying the community, and fragmentation due to all the upcoming distributions made it a technical nightmare. Over at the BSD camps, people were less tolerant of misbehaving children but they were far more helpful as a community, and actually knew what they hell they were talking about as they were not just a bunch of kids shouting 'linux is cool.. windows sux.. i'm elite'.. that wouldn't know what a scheduler was if it bit them in the ass.

      --
      ---- Booth was a patriot ----
    7. Re:Hostile community by Anonymous Coward · · Score: 1

      I take it you haven't read UPDATING after all. Honestly, if you don't know about /usr/ports/UPDATING you shouldn't even play with FreeBSD. I assume you haven't spent any time on reading about Ports system before using it. So basically this breaks down to a RTFM case.

      There are rare occasions when some libraries are upgraded to a more recent release, time when you need to recompile/upgrade applications that depend on it too. It *does* make sense, isn't it ? Otherwise you may end up with broken applications due to changes in those libraries they depend on.

      Another situation is when some app/library has a security update. Usually few people provide patches for older versions, so if you want the patch you upgrade to the most recent version. Kind of natural if you think about it. FreeBSD is not RedHat and doesn't have the same financial support to spend time on backporting patches for instance.

      I take it you don't like this system. You are free to stick with Windows or Fedora then, but there are people that prefer systems such as FreeBSD and Gentoo (yes, amazing, Gentoo Linux functions in a similar fashion, so it's not even a FreeBSD vs Linux issue here, it's a matter of packaging philosophy).

      I don't claim FreeBSD is better then Linux or vice-verse, but your comments show an amount of ignorance that I generally disregard.

    8. Re:Hostile community by Danzigism · · Score: 1

      no. i like it down here. it's moist. and i like feeling closed in. bring cake down here. along with hot pockets.

      --
      *plays the Apogee theme song music*
    9. Re:Hostile community by Galactic+Dominator · · Score: 1

      I dumped FreeBSD for a number of reasons. Required to upgrade due to some security thing, Oh wait, some obscure library has also updated and now the entire OS needs to upgrade. And KDE too. WTF? When did Gnome get installed? Ah well, I wasn't going to use the computer this week anyway. One week later, nothing works, so I go to the mailing lists. First responses are usually "It's in UPDATING, come back when you've read that." If you haven't seen the snide, arrogant crap that happens on the mailing lists you are not paying attention. (mailing lists? are your reading what you are typing? mailing lists? This isn't 1988.) And yes, there are a large number of parts of the base OS (not the ports) that have crap documentation. And RTFM? If you need to RTFM to install software and keep a system running, the system is crap. I've switched to a Mac and Windows 7. Haven't had to R any FM since. No. FreeBSD is not a desktop system. If you want it to do useful things, don't install a gui and try to limit yourself to the base OS. Do everything from the command line. Aint that quaint. Otherwise, run away.

      Well there is one thing to be learned here. Don't install FreeBSD if you're incapable of following instructions.

      This is the biggest pile of whining drivel I've seen in awhile. This is what you get when you try to cover up incompetence by blaming it on something else.

      --
      brandelf -t FreeBSD /brain
    10. Re:Hostile community by theArtificial · · Score: 1
      Greetings! The snarkiness from your posts is not needed especially when you imply that the "FreeBSD community" (which you replied to an AC on Slashdot!) is not friendly. From your posts it doesn't seem like you have a solid understanding of FreeBSD which is essential if you're going to administer it effectively.

      Required to upgrade due to some security thing, Oh wait, some obscure library has also updated and now the entire OS needs to upgrade

      Do you upgrade a foundation of a house without expecting to touch anything built upon it? When a dependency is upgraded software which depends upon it is rebuilt to make use of the new library (ports and whatnot are built with compile time flags which tell it what libraries to use). You can work with binary packages to reduce the compile time, but as soon as you start manually upgrading things you need to be aware of what you're doing since you now have a "custom" configuration.

      First responses are usually "It's in UPDATING, come back when you've read that." If you haven't seen the snide, arrogant crap that happens on the mailing lists you are not paying attention.

      Each operating system has it's own quirks and FreeBSD is no exception. When upgrading your FreeBSD system you would be wise to consult UPDATING file located in the ports directory. This file contains the most recent notes and issues to be aware of before beginning any updates to minimize conflicts and redundant questions. Pretty obscure eh? It wouldn't be if you began here. You may be shocked to discover people being snide or arrogant are not limited to FreeBSD mailing lists... have you heard xbox live?

      And KDE too. WTF? When did Gnome get installed? Ah well, I wasn't going to use the computer this week anyway. One week later, nothing works, so I go to the mailing lists.

      You install oodles of software and are shocked (SHOCKED!) there are oodles of dependencies. It doesn't take a week to update a system but i'm not familiar with your configuration or the hardware this machine has, or your abilities. Back in the day bsdforums.org was a great place to turn to help, you might consider the "official" forums.

      (mailing lists? are your reading what you are typing? mailing lists? This isn't 1988.)

      Google makes navigating these pretty easy if you don't want to configure a client. We're still using wheels and those predate mailing lists! People still use SSH, FTP and VI and those aren't exactly new either but I digress.

      And RTFM? If you need to RTFM to install software and keep a system running, the system is crap.

      Perhaps this is the reason you're experiencing the issues you've encountered. Disregarding the advice and best practices of the developers and maintainers who have created the system you're "administering" through your own ignorance is telling and a recipe for disaster. Luckily FreeBSD has a nice handbook which covers everything from upgrading a system on the fly to common administration tasks should you need assistance. Honestly, do you just dump fluids into your engine and when something strange happens lament the vehicle?

      I've switched to a Mac and Windows 7. Haven't had to R any FM since. No. FreeBSD is not a desktop system. If you want it to do useful things, don't install a gui and try to limit yourself to the base OS. Do everything from the command line. Aint that quaint.

      I'm glad you've found something you can get work done with little hassle, which is ideally what computers are there for - getting work done. Each of these OS have different ways of getting these things done, and typically I prefer the *nix side of things. Windows/OSX Philosophy: "I don't think you shoul

      --
      Man blir trött av att gå och göra ingenting.
    11. Re:Hostile community by cpghost · · Score: 1

      Required to upgrade due to some security thing, Oh wait, some obscure library has also updated and now the entire OS needs to upgrade.

      Event tough I'm using FreeBSD almost exclusively nowadays and have been using it since even before 2.0, this is one of my favorite gripes. Really! devel/icu updated, and poof, nearly your whole /usr/local has to be rebuilt. WTF?! And that's when you learn to put ZFS snapshots and rollbacks to good use, emulating OpenSolaris' beadm alternate boot environment pardigm to quickly recover production machines.

      --
      cpghost at Cordula's Web.
    12. Re:Hostile community by synthespian · · Score: 1

      (mailing lists? are your reading what you are typing? mailing lists? This isn't 1988.)

      I suppose the *really* **smart** thing to do is to wade through countless and dispersed PHP forums, googling non-stop, instead of going to *one* central place, right?

      Because, like newsgroups, if a technology is old, it's bad, right? (Just like the hp 12c calculator, I guess - so bad...why is it still around?).

      We *need* forums in which we can put avatars and smileys, right dude? Otherwise, it's not optimal, right?

      I mean, text, WTF, that's so 90s...

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
    13. Re:Hostile community by finarfinjge · · Score: 1

      I take it you haven't read UPDATING after all. Honestly, if you don't know about /usr/ports/UPDATING you shouldn't even play with FreeBSD. I assume you haven't spent any time on reading about Ports system before using it. So basically this breaks down to a RTFM case.

      There are rare occasions when some libraries are upgraded to a more recent release, time when you need to recompile/upgrade applications that depend on it too. It *does* make sense, isn't it ? Otherwise you may end up with broken applications due to changes in those libraries they depend on.

      Another situation is when some app/library has a security update. Usually few people provide patches for older versions, so if you want the patch you upgrade to the most recent version. Kind of natural if you think about it. FreeBSD is not RedHat and doesn't have the same financial support to spend time on backporting patches for instance.

      I take it you don't like this system. You are free to stick with Windows or Fedora then, but there are people that prefer systems such as FreeBSD and Gentoo (yes, amazing, Gentoo Linux functions in a similar fashion, so it's not even a FreeBSD vs Linux issue here, it's a matter of packaging philosophy).

      I don't claim FreeBSD is better then Linux or vice-verse, but your comments show an amount of ignorance that I generally disregard.

      I stopped reading UPDATING more than a year ago when I gave up entirely on this POS operating system and the people in the community. Before then, I spent WAY too much time reading UPDATING. Based on my hourly billing rate I could have purchased a full version of Win7 Professional a month. So now I run Windows. I haven't had to read UPDATING in a very long time. I spent a lot of time on the mailing lists. I was able to help a lot of people over the years. The problem isn't just the system. The problem is the community. It is elitist, obnoxious and rude. FreeBSD is a nice hobby. Fewer and fewer people who have to do real work are using it. Anonymous Cowards, such as yourself, who epitomize that community, are assuring that the trend will continue.

    14. Re:Hostile community by nnull · · Score: 1

      but there are people that prefer systems such as FreeBSD and Gentoo (yes, amazing, Gentoo Linux functions in a similar fashion, so it's not even a FreeBSD vs Linux issue here, it's a matter of packaging philosophy).

      Ever been on the Gentoo forums? Notice how less hostile people are on the forums compared to the freeBSD forum and mailing list? People will reply to anyone with problems without getting hostile on gentoo. There's quite a huge difference.

      I've been using freebsd as a desktop for the last 3 years and I do enjoy it, but getting help from the forum or mailing list is next to impossible. My last problem with a freebsd port was with gnome trying to install evolution and forcing install heimdal. Of course after installing heimdal, it broke every port I had installed on my system and I was unable to ever upgrade again until I removed it (removing also evolution and gnome along with it). When I asked on the freebsd forum and mailing list about this, I was met with hostility and absolutely no solutions to this. After searching the mailing lists for about a couple weeks, I finally ran into someone with the same problem and we discovered this was a problem because krb is installed in the base system so either replacing it or removing whatever Kerberos port I had installed was the only solution. That's all it was, I could have saved a ton of time if I knew this before hand or if someone was kind enough to tell me this instead of calling me to dumb to use freebsd (because apparently none of them use a GUI or gnome and everyone knows how to fix these nuances except me).

      As much as I try to love freeBSD, this kind of hostile community isn't really helping freeBSD get anywhere or any support.

    15. Re:Hostile community by Anonymous Coward · · Score: 0

      When you bring the charming and endearing personality you've demonstrated over and over again here, I can't say I would blame "the community" for treating you like an asshole. Asshole is as asshole does. Did you start out all your post on the mailing lists like you do here: "I'm very important, I have a high billing rate, I love my Win7, and everything around here blows. If you don't answer all my questions, then you are a bunch of arrogant bastards."?

    16. Re:Hostile community by BlackCreek · · Score: 1

      I think that the "know nothing, aggressive abrasive kids" shouting 'XYZ is cool... ABC sux... i'm elite' is a consequence of the popularity of the platform. Its is a bit like saying that the LaTeX dev groups is one of the most civil that there is (from what I heard, no direct experience). I tend to think that _part_ of the reason for it, is that LaTeX development is not the most exciting piece of software tech around.

      The distros brought fragmentation to some extent, but it was mostly because of the problems (packaging) that they were tackling to solve. At the same time the BSD family had fragmentation at the kernel level, which Linux doesn't actually have.

    17. Re:Hostile community by Anonymous Coward · · Score: 0

      WOAH. The FreeBSD Handbook is about the best OS documentation out there, and the man pages are way better than any linux I've ever used. OpenBSD still has better man pages than FreeBSD, but FreeBSD is definitely better than any linux in terms of documentation.

  15. Who has the time? by whistl · · Score: 2

    When I have a list of 200+ servers and VMs that I'm responsible for, as well as the applications that run on them, who has time to tune each server? While a nice idea, it's simply not practical at the scale most large businesses run at.

    We used to use FreeBSD on some servers, but they all quickly became dead ends, as OS patches and upgrades were painful and time consuming. Now we're a SLES house.

    1. Re:Who has the time? by Anonymous Coward · · Score: 0

      When I have a list of 200+ servers and VMs that I'm responsible for, as well as the applications that run on them, who has time to tune each server?

      If you have 200+ servers that are so different that they need different tuning then I can do your job better than you. If most of them are the same then I can write more relevant and insightful posts than you.

    2. Re:Who has the time? by Anonymous Coward · · Score: 0

      It's called configuration management. If you aren't using Puppet or something similar, you are not going to scale well.

    3. Re:Who has the time? by wagnerrp · · Score: 1

      If the servers all run the same hardware, then you only have to tune one server. If the servers are all independent, then the problem is that you grew several hundred servers organically, rather than planning out ahead of time.

  16. Cite by Anonymous Coward · · Score: 0

    [T]he extra time required to really get a FreeBSD box tuned will come back in spades through performance and stability metrics. You'll get more out of the hardware, be that virtual or physical, than you will on a generic Linux binary installation.

    So taking the time to tune a FreeBSD box allows you to beat a generic Linux binary installation. Seems an unfair comparison, don't you think?

    If you are making the (generally unfounded) argument that building from source gets you vastly better performance, then you can still use Linux, with something like Gentoo. Even if you're using a purely binary distribution, there are ways to tune it (e.g. choosing a different scheduler, etc). Compare apples to apples, or at least apples to Malus sieversii.

    The real question is: is a "tuned" FreeBSD box both faster and more stable than a "tuned" Linux box? Answers should include (non-anecdotal) evidence.

    I'm more of a BSD fan than most Linux users, but there are many more people claiming that the BSDs are superior than there are people providing evidence of this.

  17. Works great by SirDice · · Score: 1

    I've been using FreeBSD as a desktop for at least 10 years now. You pretty much have everything a Linux box has, KDE, Gnome, XFCE, Openbox, Windowmaker, whatever you want. Only lately things aren't going too good. Mainly because Gnome and XFCE have decided to solely depend on Linux' udev which FreeBSD doesn't have. Sure we could 'add' udev to FreeBSD but why would we want to do that when we have a perfectly working devfs that's better and older then the latest Linux fad.

    1. Re:Works great by Mysticalfruit · · Score: 2

      And by fad, you mean... in the kernel since 2003.

      --
      Yes Francis, the world has gone crazy.
    2. Re:Works great by SirDice · · Score: 1

      But used HAL for hotplugging. It now seems to use udev, uevent, udisks, upower. What other uthings will they come up with?

    3. Re:Works great by ThePhilips · · Score: 1

      I've been using FreeBSD as a desktop for at least 10 years now. You pretty much have everything a Linux box has, KDE, Gnome, XFCE, Openbox, Windowmaker, whatever you want.

      What is the state of hardware accelerated video playback? Last time I was looking into it, it wasn't even experimental yet.

      --
      All hope abandon ye who enter here.
    4. Re:Works great by Anonymous Coward · · Score: 0

      Hardware accelerated video playback works well on Nvidia hardware. As a former ArchLinux user and actual FreeBSD user, I can say that.

  18. Use Gentoo by doconnor · · Score: 4, Informative

    If you want your Operating System tuned and customized to your hardware can't you just use Gentoo Linux? Then you won't lose the benefits of the better support that Linux has.

    1. Re:Use Gentoo by Scaba · · Score: 1

      Gentoo is for sissies who like having their hands held and bottoms wiped. Real men - you know, the kind with beards and repulsive body odor - use Linux From Scratch.

    2. Re:Use Gentoo by koinu · · Score: 1

      I'm FreeBSD user since 10 years. I try Gentoo about every year, but I always have come back to FreeBSD because of the Ports Collection. I need working software and I don't want to be bothered with some inconsistencies like Gentoo often has in their Portage.

      I try Linux again and again, because it has the potential to be a mainstream system. But all Linux distributions get awful with time when it comes to details and suddenly I want my FreeBSD back.

    3. Re:Use Gentoo by Anonymous Coward · · Score: 0

      My thought exactly. And for new ones, the Linux communities are much more helpful than those for the BSD-Unix distros, based on my experience.

    4. Re:Use Gentoo by colsandurz45 · · Score: 1

      I don't want to be bothered with some inconsistencies like Gentoo often has in their Portage.

      Like what?

    5. Re:Use Gentoo by TemporalBeing · · Score: 1

      Gentoo is for sissies who like having their hands held and bottoms wiped. Real men - you know, the kind with beards and repulsive body odor - use Linux From Scratch.

      LFS has only one use - teaching you how to build a distribution should you want to be the next Red Hat, SuSe, Gentoo, etc. It does not belong any where near a real Linux installation - server OR desktop.

      If you won't want to use Gentoo, then use Slackware and install everything from source yourself. That's the only thing better than using Gentoo. And even LFS is sissified in comparison.

      --
      Truth is like the sun. You can shut it out for a time, but it ain't goin' away. - Elvis Presley (source: imdb.com)
    6. Re:Use Gentoo by Anonymous Coward · · Score: 0

      Add to that, that if you want stability, there is Gentoo Hardened, even with SELinux, PaX, and all that. Of course not using unstable (~arch).

      I haven't seen anything crash on it since 2002, which is when I installed it. ^^
      Mind you, that is while going through 3 different mainboard/CPU combinations, 2 architectures, and 4 hard disk replacements.
      And the system still feels lean and clean like on the first day. (Actually even more, since I managed to fix the newbie mess from the unexperienced early days.)

      But hey, I'm using unstable bleeding-edge Gentoo on my workstation for a couple of years now, and yes it's more work, but it's like more work with your self-built car: It's something you look forward to, since messing with the system and learning new stuff, my hobby, is why I installed Gentoo in the first place. (Otherwise I'd go with Debian and not waste the time.)

    7. Re:Use Gentoo by hetfield · · Score: 1

      Yes. I use Gentoo and absolutely love it. That is, until an emerge of a package hoses my system and I spend the next six hours troubleshooting it. The Gentoo forums are sometimes helpful, but not always depending on the root cause of the problem. If I didn't read a news item after syncing my portage tree I can usually find the answer along with a proper scolding for not RTFM. If the problem is a Gentoo ebuild issue or an upstream bug, finding an answer is usually more difficult.

      Because Gentoo is geared more towards a seasoned, savvy Linux user, I never would recommend it to someone switching from Windows, and hardly would recommend it to someone who's been using Ubuntu for the last year. I've been using Linux since 1998 and Gentoo since about 2003, and I struggle at times (see previous paragraph). I think that disqualifies Gentoo as a general-purpose desktop Linux distribution.

      Also, remember that the Gentoo portage system is a direct kin of FreeBSD's ports. I guess you don't *need* FreeBSD around since it's the concept and not the code that makes portage, but what a slap in the face.

    8. Re:Use Gentoo by Scaba · · Score: 1

      Whoosh!

    9. Re:Use Gentoo by Rich0 · · Score: 1

      Well, I'd say that system-hosing updates used to be more common in the past than they are now, but occasionally they still come up (usually with more warning these days, but not always).

      I think that Gentoo (and everything else) will be much better off when btrfs becomes stable. With btrfs you can just snapshot everything inexpensively, run your update, and if you're hosed you can just switch back to your snapshot. I know when I update Gentoo VMs I make liberal use of snapshots.

    10. Re:Use Gentoo by Sepultura · · Score: 1

      More users =/= better support.

      In my experience, FreeBSD's support is bar none.

    11. Re:Use Gentoo by Anonymous Coward · · Score: 0

      Agreed, Gentoo Linux has a lot more hardware compatibility, and has all the bleeding edge packages, but you still can tune the system for whatever you want.

      I heard that Gentoo's "portage" package manager looks just like FreeBSD's ports, but improved, so I'd say why not use Gentoo/FreeBSD instead of just FreeBSD then?
      And it looks like the Linux kernel has just more features than the FreeBSD one in general, and more hardware support, so Gentoo Linux it is.

      PS: I never understood why it was mandatory to have a primary partition and a slice in it to be able to boot FreeBSD, linux is able to boot from virtually anything.

    12. Re:Use Gentoo by Anonymous Coward · · Score: 0

      ..and you can enjoy a similar packaging system (if you want to use it)..

    13. Re:Use Gentoo by thehodapp · · Score: 1

      LFS has only one use - teaching you how to build a distribution should you want to be the next Red Hat, SuSe, Gentoo, etc. It does not belong any where near a real Linux installation - server OR desktop.

      Do you have any reasons why "it does not belong any where near a real Linux installation"? Gentoo is, perhaps, even worse than an Ubuntu distribution in many circumstances. Unless you really know what you are doing, you're very likely to break things on a Gentoo distro.

      If you won't want to use Gentoo, then use Slackware and install everything from source yourself. That's the only thing better than using Gentoo. And even LFS is sissified in comparison.

      Also I'm betting you've never installed LFS. If you know what you are doing, you have almost ultimate control over your system with LFS. I'm betting the reason most people don't run it as a server is because it would be way too much effort to learn how to build an entire operating system just to run a server. Oh and let me know if you can think of a reason why it's "sissified".

    14. Re:Use Gentoo by TemporalBeing · · Score: 1

      LFS has only one use - teaching you how to build a distribution should you want to be the next Red Hat, SuSe, Gentoo, etc. It does not belong any where near a real Linux installation - server OR desktop.

      Do you have any reasons why "it does not belong any where near a real Linux installation"? Gentoo is, perhaps, even worse than an Ubuntu distribution in many circumstances. Unless you really know what you are doing, you're very likely to break things on a Gentoo distro.

      To start with, LFS's goal is NOT to be a real Linux installation. It's stated goal is to teach you how to build a distribution so that you may then go off and do so (http://wiki.linuxfromscratch.org/lfs/); even if you derive it from LFS. However, please note how few distributions are derived from LFS.

      If you won't want to use Gentoo, then use Slackware and install everything from source yourself. That's the only thing better than using Gentoo. And even LFS is sissified in comparison.

      Also I'm betting you've never installed LFS. If you know what you are doing, you have almost ultimate control over your system with LFS. I'm betting the reason most people don't run it as a server is because it would be way too much effort to learn how to build an entire operating system just to run a server. Oh and let me know if you can think of a reason why it's "sissified".

      I've gone through LFS before, and it's rather cumbersome. You also don't need most of their patches, which at least at the time I did they claimed were required to make a distribution system, but really you didn't - I used vanilla sources just fine.

      People don't use LFS for a server or desktop because there is no real process for keeping it up to date, getting security fixes, etc. It's entirely up to you to do the work. And every now and again they release a new copy of the documentation for building the whole thing over with new patches, updated software, etc - but no migration from an older build. You're on your own.

      So really, you're no better off than doing Slackware and then building all your own software from source - at least then, you have the advantage of using PkgTool when you want to install something from Slackware instead of rolling your own. (Though you could do that under LFS too, but it's much quicker to just start with Slackware instead of LFS.)

      But honestly, if you really want to get 100% out of your system configuration and run a system built from source, then there is nothing like Gentoo which makes it extremely easy to do, complete with updates, security patches, and a full set of methods to keep a consistent system build going as well as a lot larger community to help out in the rare instances you do actually run into trouble. And yes, Gentoo is used on many servers too - even allowing you to build on a non-production system to make rolling out to production systems very easy (emerge package && quickpkg package, transfer to the other computer, and emerge the prebuilt package).

      --
      Truth is like the sun. You can shut it out for a time, but it ain't goin' away. - Elvis Presley (source: imdb.com)
  19. more stability? by james_van · · Score: 3, Interesting

    all the linux fanbois i know are always raving about "OMGZ teh linux is uber stable, i only have to reboot every 6.1 years!" and looking down their noses at me as a poor, foolish windows user. youre saying theres something even more stable? those guys must be insufferable

    1. Re:more stability? by daid303 · · Score: 1

      Every OS is as stable as the user.

      Also, if you apply updates you need to restart those services. If X.org gets updated then you might as well restart you computer. (FYI: X.org runs below all the GUI stuff). I think Windows and Linux are about as stable as an OS. I run windows at home, Linux at work. So I do experience both. All crashes and reboots I had so far I could relate to: "updates on critical parts" or "hardware problems".

      I do have to say that hardware problems are usually easier to diagnose in Linux. But I have to give windows credit for detecting that my video drivers crashed (and then continue at 640x480 256 colors VGA mode) that at least allowed me to save my work.

    2. Re:more stability? by SirDice · · Score: 1

      The stability of FreeBSD also referrers to it's API/ABI. Something both Windows and Linux seem to be seriously lacking.

    3. Re:more stability? by Attila+Dimedici · · Score: 3, Funny

      Every OS is as stable as the user.

      So, you are saying that Free BSD is not very stable? Because every FreeBSD user I have ever met has been among the most unstable people I know.

      --
      The truth is that all men having power ought to be mistrusted. James Madison
    4. Re:more stability? by udippel · · Score: 1

      Firstly, the article is on desktop, not on server and neither on development. So your argument is moot.
      Secondly, the only stable API I ever experienced was and is on Solaris. Exactly on the contrary: In BSD userland goes pretty much together with a kernel.

      What was your argument again?

    5. Re:more stability? by e3m4n · · Score: 1

      if i had mod points I'd give you a few for that funny retort. That was pretty clever.

    6. Re:more stability? by Anonymous Coward · · Score: 0

      Every OS is as stable as the user.

      Not Windows 95: the infamous "Get_System_Time" service bug made it impossible to have an uptime above 49.7 days.

    7. Re:more stability? by clarkn0va · · Score: 1

      Every OS is as stable as the user.

      So would you say that Windows makes people unstable, or that unstable people tend to choose Windows?

      --
      I am literally 3000 tokens away from the chaotic crossbow --Stephen
    8. Re:more stability? by Anonymous Coward · · Score: 0

      Why yes , they are.

    9. Re:more stability? by inhuman_4 · · Score: 1

      Every OS is as stable as the user.

      Amen. I was forced to use windows at my work, and do you know what its uptime was? 370 days. If you are smart about not installing a billions useless things, and not open every email attachment WinXP is more than stable enough for most people. I still greatly prefer linux to windows, but I'm fully aware that windows is often good enough.

    10. Re:more stability? by inhuman_4 · · Score: 1

      So would you say that Windows makes people unstable, or that unstable people tend to choose Windows?

      I would say that Windows is unstable because of the people who use it. I've had 370 days of uptime on WinXP. Windows is less stable than Linux, but a large part of the difference is the users. Linux people tend to be techie and smart about how they use the computer. While many Windows are clueless and do stupid things that make machine fail. Things like installing cracks, email attachments, and do hard power offs.

    11. Re:more stability? by clarkn0va · · Score: 1

      I'll agree that those factors could be part of it, but certainly not the whole story. A developer friend of mine runs both Linux and Windows at home (personal and work computers, as he works from home), and he says he is lucky to get through a day without rebooting or resetting his Windows machine. This is not not from installing cracks or other questionable software, but from merely doing the normal types of things a software developer does in a day. He says he can go longer without rebooting since upgrading from xp, but it's still generally several times per week.

      Contrast this with his Linux machines, which generally reboot when the kernel gets updated. Granted, these are two different usage patterns, but he's not doing anything far-out risky by any stretch.

      And let us not forget the story that graced /. roughly three years ago, featuring a video interview with the microsoft.com devs admitting that until their web servers went 64-bit they had them on a 5-minute rotating reboot cycle thanks to memory leaks. I wish I could find the link to that story, but it's not turning up.

      --
      I am literally 3000 tokens away from the chaotic crossbow --Stephen
    12. Re:more stability? by synthespian · · Score: 1

      Every OS is as stable as the user.

      Yeah, my mom's OS is stable as hell. Last I visited her, she was running Windows XP unpatched!

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
  20. 2012 by tetrahedrassface · · Score: 1

    2012: The year of the FreeBSD desktop? Hurry while we still have time before the Mayan calender and the asteroids and Nibiru hit!

  21. A tale of three tries by sirdude · · Score: 1

    Frankly, I've tried using FreeBSD three times in my life and gave up each time. It's just too bleeding involved to get it up and running to your expectations especially when there's a Debian installation that I can have up and running to perfection in about an hour.

    From memory, the stumbling block was inevitably drivers, and often when you couldn't get your NIC working, it decidedly becomes a chore. I refuse to even try to recollect the veritable nightmares that I experienced trying to get my graphics card going the first time.

    I suppose I should give it another shot using virtualbox.

    P.S. even the "post options" popup on bsd.slashdot.org fails to open right. Poetry.

  22. What about drivers? by peppepz · · Score: 1

    Especially for "multimedia" hardware such as GPUs? Linux is already a bit behind in this field, but FreeBSD is even worse.

  23. Hurr durr? by L4t3r4lu5 · · Score: 1

    Not once did I read any phrase relating to *BSD on the desktop. He specifically says "Linux on the desktop, BSD on the server".

    Very well done, editors.

    --
    Finally had enough. Come see us over at https://soylentnews.org/
    1. Re:Hurr durr? by MimeticLie · · Score: 1
      Yeah. His conclusion at the end of the article is specifically about servers:

      Once you've ridden the learning curve and spent some time actually getting to know the innards, you may decide you'd be better off running FreeBSD on the next set of Web servers, SMTP relays, or application servers you build.

      I guess even the submitters don't RTFA.

    2. Re:Hurr durr? by ohcrapitssteve · · Score: 1

      You would have found it if you read the title: "In Favor of FreeBSD On the Desktop" :-D

    3. Re:Hurr durr? by pz · · Score: 1

      In fact, at the end of the article, in the concluding paragraph, the last line of serious content is:

      Once you've ridden the learning curve and spent some time actually getting to know the innards, you may decide you'd be better off running FreeBSD on the next set of Web servers, SMTP relays, or application servers you build

      Not in a single place does the article advocate that any variant of BSD is appropriate for the desktop, save Apple's.

      --

      Put my fist through my alarm clock with its ding-dong death inside my ear. - The Blackjacks.
    4. Re:Hurr durr? by L4t3r4lu5 · · Score: 1

      You would have found it if you read the title: "In Favor of FreeBSD On the Desktop" :-D

      You mean the title of the stub? That's not the title of TFA:

      "Why aren't you using FreeBSD?
      FreeBSD is a free, fast, stable, feature-rich operating system. If you've never looked into it before, you should."

      Granted you have to read the first paragraph to see that he's writing about servers, but surely that's not too much to ask for a story submission. At no point through the entire article does the author mention BSD on a desktop computer. Only servers.

      --
      Finally had enough. Come see us over at https://soylentnews.org/
    5. Re:Hurr durr? by L4t3r4lu5 · · Score: 1

      Not in a single place does the article advocate that any variant of BSD is appropriate for the desktop, even Apple's.

      FTFY. The article does not comment on desktop OS's at all, save that the author uses Linux on the desktop.

      I'm going to be generous and assume that this was a genuine mistake.

      --
      Finally had enough. Come see us over at https://soylentnews.org/
    6. Re:Hurr durr? by Anonymous Coward · · Score: 0

      Also, nowhere in the article does it purport any particular advantages that FreeBSD has over Linux except a completely hollow assurance that it is more "stable" based on some stupid server he hasn't bothered rebooting in 3 years and some lame insistence that the benefits will be "returned in spades". Whatever.

  24. Re:Flash by somersault · · Score: 1

    If you use Chrome then it presumably would, as Flash is built in to Chrome.

    --
    which is totally what she said
  25. x y z? by Anonymous Coward · · Score: 0

    I tried yum install x y z, but nothing hapenned.. I'm running debian.. Should I be concerned?

    1. Re:x y z? by ksd1337 · · Score: 1

      sudo apt-get install yum
      That should take care of it!

  26. apt-get install freebsd by sgt+scrub · · Score: 1

    I thought it was pretty easy to install both server and desktop. http://noone.org/talks/kfreebsd/kfreebsd-fosdem.html

    --
    Having to work for a living is the root of all evil.
  27. Re:Flash by Anonymous Coward · · Score: 0

    You are dead wrong. Wake up call. Flash works. Since years....

  28. Why even run it on servers? by jtseng · · Score: 1

    In every professional environment I've worked in we choose the best tools for the job; it was usually Windows, Solaris or some form of Linux. I've only seen one instance of using FreeBSD and even then we were migrating to CentOS. Why? It's the maintainability and time-savings, stupid! Not only are the tools you need widely available for those platforms, the updates are easily accessible as well, they're generally configured to work out of the box (granted it may not be optimized but you can "spend the extra time to tune it"), and far more people know how to use those platforms vs FreeBSD.

    --

    Sanity.html - Error 404 not found

    1. Re:Why even run it on servers? by rev0lt · · Score: 2

      I actually use mostly FreeBSD on servers because the maintainability and time-savings. I've never had a problem with updates not being accessible (cannot say the same for Solaris), and most of my installations work out-of-the-box. They do not have some fancy half-assed X wizard to tune some config file (or some xml that will later be translated to some config file), and requires that the administrator has an idea of what he's doing. The problem is, is cheaper to hire average administrators that can run a linux configuration script or a windows wizard, than one that actually knows what he's doing. And while companies probably don't need a wizard running the servers, a competent unix sysadmin will be competent and productive on freebsd, linux or solaris. The problem with modern operating systems isn't stability anymore, but how they allow the sysadmin to diagnose, troubleshoot and recover software and hardware errors. On that field, both solaris and freebsd are much more advanced than linux or windows.

    2. Re:Why even run it on servers? by synthespian · · Score: 1

      These days in FreeBSD you do binary system upgrades, you know?
      If you're running servers, than you don't have a gazillion ports installed...do ya?
      It sounds like a bunch of people here played with FreeBSD for 2 days than said "reading the handbook is too hard - let's go install Leenoox!"

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
  29. I know it, I know it, I know it! by Anonymous Coward · · Score: 0

    - It is because we don't want to have to compile basic applications.
    - It because we don't want to use a system with a lack of QA.

  30. Re:Flash by Anonymous Coward · · Score: 2, Informative

    I assume they still don't have it. Wake me up when that happens and I will use FreeBSD on the desktop.

    Your assumption is wrong. A simple search on the internet would have shown you that Flash works on FreeBSD, and it works for a while now (both 32 and 64bit). I've used it with Firefox and with Opera.

    See the handbook.

    So, um... wake up lazy!

  31. Re:Flash by hedwards · · Score: 2

    They've had it for years, there's at least two different ways of doing it. The easiest way is just using Wine and the Windows version of Firefox. The other way is to just use the Linux version of Flash. And really, it's only necessary because of incompetent web developers anyways.

    These sorts of FUD posts about a largely unimportant feature that isn't native, is really not conducive to a decent discussion.

  32. People don't want to watch kernel compiling by daveewart · · Score: 1

    "Here I sit, watching a freshly installed FreeBSD box run through cvsup on all ports, to be closely followed by a new kernel compilation. As the output flies by in the xterm, I find myself wondering why I don't run into more FreeBSD in the world."

    There's your answer right there. Perhaps people want more from their OS than to sit watching a kernel compilation."

    --
    "If you think the problem is bad now, just wait until we've solved it." --- Arthur Kasspe
    1. Re:People don't want to watch kernel compiling by SirDice · · Score: 1
    2. Re:People don't want to watch kernel compiling by geminidomino · · Score: 1

      Pretty much. I used to love FreeBSD. I really did. I built a server into an old Dell full-tower back before the turn of the century and ran a (admittedly useless) server off of my mindspring dial-up to learn it.

      Now, though, I work for a small company wearing way too many hats, including being responsible for maintaining (but not purchasing) a few dozen rag-tag machines running the gamut of age and architecture. 'make buildworld' et al are just too damned involved and time-consuming nowadays.

      I hate ubuntu with a passion, but that decision predated me, and at least the server LTS versions don't inflict Unity upon me, so that's not a battle I picked.

    3. Re:People don't want to watch kernel compiling by joib · · Score: 1

      Haven't you understood; Watching gcc output scroll by for hours on end will make you l33t! That's why Gentoo and FreeBSD users are so hardcore.

  33. FreeBSD vs Linux -- 1994 edition by Kurt+Granroth · · Score: 1

    I remember the first time I looked into FreeBSD. It was back in 1994 and I needed to run some Unix variant on my 386 and it came down to FreeBSD or Linux. At the time, FreeBSD seemed to be significantly farther along than Linux... but in a completely unusable way, to me. I was a rank newbie to Unix that had just learned how to exit 'vi' without powering down the computer. FreeBSD had almost no documentation and certainly none for somebody like me.

    Linux, on the other hand, had the Linux Documentation Project (LDP). The docs there were incredible! I hogged the computer lab's laser printer printing off the SAG and the NAG and, most importantly, Matt Welsh's 'Installation and Getting Started Guide'.

    It was no contest. FreeBSD was an impenetrable mystery but 60 something floppies of Slackware later and I was hooked on Linux for life.

    1. Re:FreeBSD vs Linux -- 1994 edition by toadlife · · Score: 2

      Funny - it was the complete opposite when I started with the BSDs. I learned UNIX on FreeBSD using the handbook as my primary guide. Before discovering it, Linux was always an exercise in frustration due to slightly incorrect, or missing documentation. When you are starting from a position of having large pre-requisite knowledge gaps, slightly incorrect documentation is a killer.

      FreeBSD's handbook allowed a noob like me to get by and make it while the knowledge gaps were filled in with experience.

      --
      I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
  34. Time equals money by bigogre · · Score: 2

    I've installed BSD systems a number of times. They've always required more effort than a Linux box to get configured for what I want.

    Sure BSD is a cool thing. To some people MS-DOS 6.11 was a great thing, too. You'd be surprised how many systems in the world are still running MS-DOS (a lot of point of sale systems). Just because something is cool or can be made to work doesn't mean it's the best for any particular use.

    You could use a Porsche 911 as a dump truck, but why? You could make a pickup truck into a limousine, but why? Wise use of tools is a sign of maturity.

  35. Theory vs Reality by ChrisKnight · · Score: 1

    In theory, I prefer FreeBSD. I have been running it as my primary server OS for 16 years. I have 30+ VMs running it right now. At the time they were easy to spin up an configure for my friends for whom I provide hosting.

    In reality, the nearly constant state of screwed up dependencies in the ports tree makes it pretty much impossible to keep those 30 systems up to date without serious amounts of manual prodding. Keeping PHP up to date alone has drained my will to keep running FreeBSD.

    At my job I maintain several thousand CentOS boxes, via puppet. The ease of keeping these systems patched is like night and day compared to my mere 30 FreeBSD VMs.

    The only things keeping me running FreeBSD are nostalgia and inertia. The next time I need to do major updates I plan on swapping them out for CentOS.

    --
    -- This sig is only a test. If this were a real sig it would say something witty. --
    1. Re:Theory vs Reality by rev0lt · · Score: 1

      Can't you install freebsd packages via puppet? The upgrade path should be the same. The dependency problem is transversal to most unix so's, including linux (desktopbsd has a workaround for it when using .pbi). I usually update php using make deinstall/reinstall, and have my database instances on another jail. also, usually the php instalations are jailed, so a zero-day exploit might access or wipe the jail data, but won't expose the whole server. If you're running 32 bit VMs, you could probably even install the linux php binaries and run them (though at that point, you may be better served running centos or some other linux distro).

    2. Re:Theory vs Reality by Chris+Mattern · · Score: 1

      Can't you install freebsd packages via puppet? The upgrade path should be the same.

      In reality, the nearly constant state of screwed up dependencies in the ports tree makes it pretty much impossible to keep those 30 systems up to date without serious amounts of manual prodding.

      Puppet's not going to do him much good if he has to keep manually fixing broken depencies to make the upgrade work.

    3. Re:Theory vs Reality by rev0lt · · Score: 1

      He can build the package on a separate machine, with the fixed dependencies, and then install it on the VMs via puppet. Package building on FreeBSD isn't as simple as it should be (I prefer the simplicity of the OpenBSD ports in this regard, but I don't recall any broken dependency incident when building PHP. It is not a task I do everyday - once a month or so, but never had any issues as described.

    4. Re:Theory vs Reality by Anonymous Coward · · Score: 0

      There are a couple of php extensions that have had circular dependencies. Not saying it is that way all the time, but it is a pain in the ass.

      As for building the packages on another machine, and then installing via puppet... Yeah, loads of fun.

      I am not interested in creating work for myself; and sadly, sticking with FreeBSD has become more work than I want to put into my hobby box.

    5. Re:Theory vs Reality by synthespian · · Score: 1

      I have a question: have you used portmanager for upgrading ports? portmanager will update all the port's dependencies *before* upgrading the ports. It's really good.

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
  36. Linux isn't untweakable by r00t · · Score: 1

    It's even easier and faster, since you can just tweak the stuff that matters. Install something sane, perhaps debian-testing, ditch the background daemons you don't need, compile your own kernel (way easier than with FreeBSD), and compile any app that you really really care about. Done, easy, and you still get fast/easy access to the gigantic Debian software collection.

    1. Re:Linux isn't untweakable by Lord_Naikon · · Score: 1

      How is kernel compiling easier in Linux than in FreeBSD?
      cd /usr/src
      make kernel
      How hard can it be?

    2. Re:Linux isn't untweakable by udippel · · Score: 1

      Oh dear! Had you not written the sequence about compiling the kernel, we might have considered you a philosopher ... .
      But you fail it. Compiling a BSD kernel is actually most simple, and much more simple than compiling a Linux kernel. That doesn't mean I wanted to defend FreeBSD. But surely truth needs to be defended.

    3. Re:Linux isn't untweakable by r00t · · Score: 1

      It is implied that you want to do more than just run your CPU to replicate a binary that you already have. In other words, the goal is to tweak. The goal isn't to waste electricity.

      On the Linux side, "make menuconfig" is pretty darn good. It nicely deals with prerequisites, provides you with allowable values, and even gives you help. FreeBSD has you editing a makefile with minimal documentation.

    4. Re:Linux isn't untweakable by r00t · · Score: 1

      see response to comment above

    5. Re:Linux isn't untweakable by colsandurz45 · · Score: 1

      Compiling a BSD kernel is actually most simple, and much more simple than compiling a Linux kernel.

      go on....

    6. Re:Linux isn't untweakable by TheRaven64 · · Score: 2

      FreeBSD has you editing a makefile with minimal documentation.

      No, it has you editing the kernel description file with lots of documentation. Here is the GENERIC kernel config for x86-64. If you want to compile a custom kernel, copy that file and modify it. You'll find a comment on every single line explaining what it does, and a longer comment above every section. Linux's menuconfig requires more keystrokes to remove options than editing that file in a text editor.

      --
      I am TheRaven on Soylent News
    7. Re:Linux isn't untweakable by theArtificial · · Score: 1
      For starters it's a .conf and Linux has these things too. After editing this file you then build the kernel. Typically you're commenting out devices you know you won't need to support and compiling in modules you'll load frequently. If you're adding new stuff you hopefully have done your homework and have the device specifics handy. Minimal documentation, really?

      It is implied that you want to do more than just run your CPU to replicate a binary that you already have. In other words, the goal is to tweak. The goal isn't to waste electricity.

      Is it also implied that on the Linux side of things that one needs to run a script to generate a kernel configuration file since it's apparently too complicated to do so directly?

      --
      Man blir trött av att gå och göra ingenting.
    8. Re:Linux isn't untweakable by theArtificial · · Score: 1

      Since you haven't selected any specific distributions I've googled for guides and selected OpenSUSE, Ubuntu, Fedora. Seems like there are typically more steps involved in both building the kernel and installing it for these systems compared to FreeBSD. I didn't spend a lot of time googling examples, I searched for "%distro% installing custom kernel guide" and selected the most relevant results returned from the first page.

      FreeBSD:
      Pre-requisites is having the source installed. The easiest way to install the full source tree is to run sysinstall as root, and then choosing Configure, then Distributions, then src, and finally All. sysinstall is FreeBSD's terminal based installer.

      Already have a kernel configured? Skip to step 4.
      1 # cd /usr/src/sys/i386/conf
      2 # cp GENERIC CUSTOMKERNEL //duplicate default generic kernel as a starting point
      3 # ee CUSTOMKERNEL // load kernel file into easyedit (you could use vi, pico etc.) and modify kernel
      4 # cd /usr/src
      5 # make buildkernel KERNCONF=CUSTOMKERNEL
      6 # make installkernel KERNCONF=CUSTOMKERNEL

      --
      Man blir trött av att gå och göra ingenting.
  37. I basically agree (and I am still using it) by Conley+Index · · Score: 1

    I am currently using FreeBSD as my main OS, even on a recent (2010) laptop. It works great, for me. I have great control what is going on on my computer and I love the combination of a stable (as in "API/ABI stable" _and_ as in "upgrades do not break basic functionality") base system and very recent applications from ports.

    Anyhow, I still have to agree with you that for most people, it is just not worse the time. For anyone else, I usually install Ubuntu. Ports are very powerful, but just not suitable for everyone.

    If there were just stable ports (ports that come with a release and get only security fixes until the next release), one might come to the conclusion as the original article, but currently, you can either use release ports and live with the security holes (not a good idea to have an outdated browser and Flash plugin on the desktop), or you upgrade all ports very frequently.

    PC-BSD might be a different story, I have not tried it in some time. Even though it brought me to FreeBSD, there were some good reasons not to use it anymore: How can you suggest users to use FreeBSD ports, if there is no PC-BSD PBI, and then wipe them at an upgrade? Probably not an issue anymore, but for me, that stuck.

  38. Um, Debian? by Anonymous Coward · · Score: 0

    Hey submitter, you are forgetting about the Debian/kFreeBSD project! http://www.debian.org/ports/kfreebsd-gnu/ Complete with apt and everything. I've been running it on a laptop with pretty decent success for almost a year now.

  39. The upgrade cycle is too steep for the desktop by Anonymous Coward · · Score: 0

    I've been using Linux (Ubuntu LTS) professionally on the desktop for a few years to support my company. It wasn't a full time job when this started so I also had plenty of time to spent on administrating it.

    But now that I am working full time one of the first things I discovered was that Linux may be free of charge to get it up & running. Support is a totally different aspect! For example trying to get Ubuntu 8 LTS upgraded to Ubuntu 10 LTS. I tried, hard, with several years worth of experience. From a direct upgrade to upgrading from one version to the other until 10 was reached. It failed, horribly. The only way I would have succeeded was to do a clean installation and then try to figure out how I could manually restore my configuration (thus also hoping that it wouldn't break things).

    Long story shorter; I moved the desktop to Windows 7 & Office 2010. Sure; it costs money. But now I can also rest assured that I'll be able to continue to use this environment until 2018 or so (- 7 - years) before any upgrade might be required.

    Now; lets take a look at the FreeBSD Support cycle. Release 8.2; Feb. 24 2011 released and expected EOL is Feb. 29 2011. That is one year.

    If you use a desktop professionally then one year is totally out of the question. Quite frankly, with such a short lifespan I wouldn't even consider it for personal use either.

    Mr. Venezia doesn't seem to understand the basis of desktop usage: Most desktop users want to use their computers (desktop) instead of tinkering with it.

    There is a very good reason why Microsoft continues to support their OS's for so long.

    1. Re:The upgrade cycle is too steep for the desktop by Mr+Thinly+Sliced · · Score: 1

      Release 8.2; Feb. 24 2011 released and expected EOL is Feb. 29 2011. That is one year.

      It's 5 days.

      You haven't heard? They're trying to beat Ubuntu for release early release often.

      Best of luck to them I say!

  40. Since when... by Danzigism · · Score: 2

    did Slashdot get taken over by ADD/OCD redditors? FreeBSD is not hard to install, use, and configure. It has the best documentation out of any *NIX I've seen. It can easily utilize resources, great for server daemons, clusters, DB, and can run Xorg. There's so many damn distros to choose from nowadays, people see it for 30 seconds, download a new ISO of something completely different, install it, get bored, try another, etc. Maybe if you actually put some time in to making the system just the way you want, and RTFM, then you might be happy with the results you get from FreeBSD, or any other OS for that matter. Just tired of the ADD. Pay attention!

    --
    *plays the Apogee theme song music*
    1. Re:Since when... by daid303 · · Score: 1

      Maybe some people don't want to spend hours tweaking their system so it works. If I cannot install your OS, and run youtube movies out of the box, then it's no good on the desktop.

      Also, most complains above here are in the "hardware/driver support" section.

    2. Re:Since when... by Anonymous Coward · · Score: 0

      Last time I checked, there was a lot more factors to consider something a desktop OS than just being able to watch YouTube videos. Hardware/Drivers support? Oh I forgot that FreeBSD can be installed on almost every architecture known to man. Maybe if more people used it, tried it, saw its potential like Apple did, then they'd focus their resources on developing drivers and enhancements for graphics cards, audio, etc. I recall Linux being this difficult to get setup just a few years ago, and it is still far from perfect minus the people that make the OS for a specific device, like Android phones and tablets. The truth of the matter is, it is a much powerful OS that people give it credit for.

    3. Re:Since when... by rivaldufus · · Score: 1

      This is the "Ubuntu" vs "Mac" site. If you're not running one of the approved religions - I mean OSes, you need not comment. Sure, there are "protestants" here who run Debian, Fedora, or some other linux, but they're still running linux. There used to be Windows people, too, but they were eventually purged. Not too too long ago, there was a large group of slashdot ubuntists who converted and became die hard Macolytes. The great irony is that several people here are complaining that FreeBSD users are too "religious." Apparently, if you're not running linux or OS X, you're a religious zealot.

    4. Re:Since when... by jedidiah · · Score: 1

      The fact that you can install something on MIPS or 680x0 won't win you any brownie points with desktop users. Little things like "hardware/driver" support will be a bit more important. This includes vendor blob drivers that allow you to actually use your relic to watch videos with any acceptable level of performance.

      How quick you an be browsing YouTube is a pretty good metric actually. It covers what the target demographic is actually likely to be interested in.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    5. Re:Since when... by christurkel · · Score: 1

      I think OpenBSD has better documentation, but it's small degrees better. The FreeBSD docs do a very good job.

      --

      CDE open sourced! https://sourceforge.net/projects/cdesktopenv/
    6. Re:Since when... by Anonymous Coward · · Score: 0

      For a desktop system, that's only true if everything Just Works(tm). (Just Works is a trademark owned by someone else.) I just installed it, and truly, it does boot. However, it does not do much else, as it supports neither my USB networking card nor my phone's USB tethering. There's a driver for the former, of course, it just Does Not Work(tm). (Does Not Work is a technology used by FreeBSD under license from PEBKAC Industries: all problems with Does Not Work technology is referred to PEBKAC.)

      Personally, I find it's not worth the bother. At least my current system actually works at all.

    7. Re:Since when... by archen · · Score: 2

      It's been this way for years. Slashdot isn't about the joy of tinkering, or science. It's an endless string of rants about people complaining about absolutely everything. As the saying goes, BSD is for people that love Unix, Linux is for people that hate windows. I think some of the negativity has seeped into the minds of people where they can no longer comprehend liking a system that is well organized and fun (in a nerd kind of way) to use.

    8. Re:Since when... by myrdos2 · · Score: 1

      I've never had a problem with the stability or performance of a Linux system. I've had significant problems with BSD systems with poor hardware support. Why should I "actually put some time in to making the system just the way you want, and RTFM" for a negligible gain?

    9. Re:Since when... by Anonymous Coward · · Score: 0

      Hard to do that when I can't get the damn thing to boot without crashing! I could spend days reading the manual or I could just download an ISO and be done in a matter of minutes. Hardware support's better too!

    10. Re:Since when... by hetfield · · Score: 1

      FreeBSD is not hard to install, use, and configure. It has the best documentation out of any *NIX I've seen. It can easily utilize resources, great for server daemons, clusters, DB, and can run Xorg. There's so many damn distros to choose from nowadays, people see it for 30 seconds, download a new ISO of something completely different, install it, get bored, try another, etc. Maybe if you actually put some time in to making the system just the way you want, and RTFM, then you might be happy with the results you get from FreeBSD, or any other OS for that matter. Just tired of the ADD. Pay attention!

      You might be right. I'll be honest and say I've never really given FreeBSD much attention beyond the pretty wrapping paper of things like pfsense and FreeNAS. However, on my local LUG mailing list there used to be a guy who made no attempt to hide his love of FreeBSD and marginal disdain of Linux. I think he participated on the listserv just because our LUG was the closest thing to an open-source form/community in our area. He constantly referred to Linux distributions as 'forks' and when the topic of FreeBSD was discussed, it was made to be superior to Linux. Looking back, I don't think he was really trying to anger anyone, but after a while he did. Eventually he was shunned to the point of leaving the listserv. My conversations about FreeBSD and its user base almost always ended up with people saying "I tried it, but got tired of the condescending tone when I tried to get help."

      I really try hard not to stereotype or generalize people, but the tone of your post falls right in line with this. Also, you say FreeBSD is "great for server daemons, clusters, DB, and can run Xorg." I'd like to point out that the first three things are exactly NOT what this article is about. Instead of bashing people, talk about how FreeBSD can run desktop environments just like Linux can, and talk about the virtues of portage. I know you're probably just venting so what I'm saying isn't exactly fair, but sadly perception is reality.

    11. Re:Since when... by Anonymous Coward · · Score: 0

      From my limited experience of installing FreeBSD, I'd agree with you about the quality of the documentation -- it is good. But it has to be, because the install is not at all intuitive. Installing FreeBSD reminded me of my first Linux experiences installing Slackware in the mid-90s. That really wasn't hard either. You just had to be patient and be willing to read network docs, graphics docs etc. The payoff was that you really learned how the system works, what each config file does, what firewall rules look likes. I like OS stuff, so I dig that. But it did sometimes mean hours of searching through mailing lists for the right option for a piece of hardware, and on occasion finding yourself out of luck.

      If you're on a server, especially a high-visibility server, it's beneficial to have that level of intimacy with the configuration. But for my development laptop, there's no way I would choose a BSD. Ubuntu installs are almost trivial, work on commodity hardware and come with a huge selection of packages and up-to-date drivers. If I want to get down to the config file/iptables level, I still can, and the documentation is also good in addition to having a large and generally supportive user community. The FreeBSD ports system is a step up from "download tarball and compile," but it's in no way comparable to synaptic or even yum, and based on my experience, I can't rely on ports compiling and working, especially for "user" stuff like KDE apps. I think the current use of *BSD mostly on servers is about right. I really can't see these OSes becoming more mainstream.

    12. Re:Since when... by Danzigism · · Score: 1

      Honestly, have you ever asked for help in a #linux IRC channel? If the level of support you receive from the community is why you chose to use a specific system, then why in the hell did you chose Linux? There's so many inconsistencies, and package nightmares among the various distros I can't even begin to describe it. Regardless, the flame war is stupid. FreeBSD has never sought out to be a Desktop OS. It can certainly make one, but there's nothing to base your experience on besides having the tools necessary to create what it is you want. Preference is preference. I could scream all day about why I think it makes a good desktop OS, however I don't even use it as a desktop OS. I'm just posting because I'm tired of seeing this same argument brought up all the freakin time. Use whatever the hell you want for whatever reasons you want and stop trying to be zealots.

      --
      *plays the Apogee theme song music*
    13. Re:Since when... by CAIMLAS · · Score: 1

      Of the subsystems I've run into which have bad or simply wrong documentation in the past year, the list includes (geom, jails, zpool/zfs, and ports), they're not exactly 'small components' of freebsd.

      Jails simply don't work as described, and what's described is inconsistent. ZFS is still highly, highly experimental (in terms of stability and performance, at least), yet has had teh green light for some time now (7.3 and 8.0? seriously?). What's more, there are some pretty horrible drivers, or hardware support: hardware which works fine in centos or debian crashes repeatedly under FreeBSD (things like Intel storage controllers.)

      And don't even get me started about Ports. No, I realize its' not FreeBSD, but if you want software, you either build it yourself from an official repository for that package (I highly recommend it) or you use ports. Using ports works great, unless it doesn't: the package may be ancient, or the maintainer may have (probably did) munge the fuck out of it so that it doesn't work.

      Sorry. FBSD is about as awesome as a bag of dead mice.

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    14. Re:Since when... by utkonos · · Score: 2

      I have to say that if you enter FreeBSD from an ignorant perspective (= didn't read the Handbook) then you will get pretty terse answers on the freebsd-questions mailing list, bordering on condescending. This is because it is expected to RTFM. However, if you do basic community support due dilligence (read the Handbook, and if your answer is not there, search the mailing lists), and then post your question to one of their mailing lists (must be the appropriate list), you will get your question answered quickly and by extremely knowledgeable people. Often you will have your question answered by the committer who either wrote or is currently maintaining the part of the OS that you are asking about. Bugs in the core OS get addressed fairly quickly, and they are good about triage. I can't say the same about *buntus, KDE, Libre, and many other free software projects. In many cases it seems like you are reporting a bug to an empty room when it comes to other software projects, especially *buntu.

    15. Re:Since when... by Anonymous Coward · · Score: 0

      "Jails simply don't work as described, and what's described is inconsistent. ZFS is still highly, highly experimental (in terms of stability and performance, at least), yet has had teh green light for some time now (7.3 and 8.0? seriously?). What's more, there are some pretty horrible drivers, or hardware support: hardware which works fine in centos or debian crashes repeatedly under FreeBSD (things like Intel storage controllers.)"

      Jails are one of the strongest features of FreeBSD. A lot of people use jails _all_the_time_ , they're just not that visible. If you haven't figured out how they work then you haven't really dug deeper. Inconsistent you say? Evar since jails appeared in 4.x, the syntax are about the same, with just newer features (chroot, multiple IPs, IPv6) added over the newer releases.

    16. Re:Since when... by Danzigism · · Score: 1

      I read a lot of people talking about PC-BSD on here, so I decided to give it a shot in a VM. They have have release 9 coming out which you can download to try out. Installation was graphical, and ridiculously easy. You can use whatever window manager or environment you want. I went with KDE4 which looks like the default. It comes with a fantastic program called the AppCafe which uses PC-BSD's very own installer packages called .PBI files. They contain everything you need to install a program without any hiccups. Not to mention once you install a program via the AppCafe, it remains up-to-date. First thing I did was install FireFox. Required two clicks of the mouse, and I was watching YouTube videos in a matter of seconds. No bullshit required. I've used PC-BSD in the past and was never too impressed. But holy hell they have come quite a long way over the past couple years. This is an AMAZING desktop OS that I think everyone should try just for shits. I'm so surprised at how well this works. If there's something that's going to make *BSD a good desktop OS, this is what's going to make it happen. Fantastic job.

      --
      *plays the Apogee theme song music*
    17. Re:Since when... by swalve · · Score: 1

      [insert political rant here]

    18. Re:Since when... by Anonymous Coward · · Score: 0

      Mod parent up or down!

    19. Re:Since when... by iggymanz · · Score: 1

      you didn't get the memo, as of a few months ago we all hate Ubuntu; and Arch, Mint, and Debian are the approved GNU/Linux as long as you're not running GNOME 3 (though with mods to make it more user friendly like Mint 12 it's then sanctified)

    20. Re:Since when... by iggymanz · · Score: 1

      "can run Xorg", doesn't mean that someone took the time to integrate a good user desktop, usually the GNU-linux centric desktops and utilities leave many loose ends when ported to other OS. The FreeBSD documentation isn't as polished as say OpenBSDs, the freebsd developers aren't forced to keep it current as the OBSD are (code will be thrown out of release if docs not updated). Most people want their computer to be tool to do work, don't want to spend time grinding blades out of rods for screwdrivers, so to speak. Man-days of work to get usable system might get a hardcore gentoo user excited, but not most of us.

    21. Re:Since when... by iggymanz · · Score: 1

      I can't tinker if I have to spend man-days of time to get a useful desktop so I can tinker with *my* projects. Getting an OS usable is tinkering with someone else's stuff. A server justifies that kind of thing, but not a desktop, I want to be up and at it in less than an hour. FreeBSD desktop takes away too much tinkering time.

    22. Re:Since when... by rivaldufus · · Score: 1

      Ah, I was on sabbatical. Slashdot should keep a running chart to clarify things. I think there's a massive plot underway by windows fans (there are some, right?) to get the zealots from linux and mac to kill each other off.

  41. Benchmarks by Chemisor · · Score: 3, Informative

    Sorry, but it's not worth the time and whatever "spades" you're getting paid pack in are 99% emotional, not physical.

    These benchmarks say that Linux is usually faster than any BSD flavor.

    As for stability, I can't find any definite stats on this. Personally, haven't seen a Linux crash since 1997, and that's a pretty damn long time.

    1. Re:Benchmarks by bonch · · Score: 0

      Ah, yes, Phoronix, the company that Slashdotters dismiss when they release benchmarks that put Linux in a disparaging light but happily cite when they put Linux in a positive light.

    2. Re:Benchmarks by TheRaven64 · · Score: 1

      GCC 4.2 on FreeBSD produces slower code than GCC 4.4 on Linux? Shocking! And clear evidence of the superiority of Linux!

      --
      I am TheRaven on Soylent News
    3. Re:Benchmarks by jmusits · · Score: 1

      As for stability, I can't find any definite stats on this. Personally, haven't seen a Linux crash since 1997, and that's a pretty damn long time.

      You're doin it wrong. :^)

      --
      -- 42 --
    4. Re:Benchmarks by fahrbot-bot · · Score: 1

      These benchmarks [phoronix.com] say that Linux is usually faster than any BSD flavor.

      From that site:

      ...the spin of Debian that replaces the Linux kernel with the FreeBSD kernel while retaining most of the same GNU user-land and it uses the GNU C library. With those original tests comparing Debian GNU/Linux to Debian GNU/kFreeBSD, the Linux version ended up winning in 18 of the 27 tests.

      I'm not convinced that running "Debian GNU/kFreeBSD" is the same as native FreeBSD, especially for a performance benchmark.

      --
      It must have been something you assimilated. . . .
    5. Re:Benchmarks by heson · · Score: 1

      If you have ever tried to do serious benchmarks.
      Most of the Phoronix benchmarks will feel like benchmarking cars by measuring highest rpm possible (higher is better). Or measuring acceleration down to micro seconds, but some cars tested in light rain and some in snow.
      I do never feel that they are doing it on purpose, only by incompetence or carelessness. (i.e there are no deceptive scales like in ads)

    6. Re:Benchmarks by Sipper · · Score: 1

      These benchmarks say that Linux is usually faster than any BSD flavor.

      I don't think that's the conclusion to come to from those benchmarks. Only two benchmarks occurred where Linux was significantly faster than FreeBSD; onewas the Himeno Benchmark test doing a "Poisson Pressure Solver" -- and only one of the two systems tested had this issue, not the other. The other benchmark where Debian Linux was faster than BSD was the Threaded I/O tester. For all the other tests the differences were minor, and in several cases BSD was faster. I don't think there's any clear conclusion to draw from these tests.

      I don't personally run FreeBSD (thusfar) so I don't have personal experience to draw on for comparing BSD vs Linux speed. However I will say that speed is not the reason I run Linux rather than BSD.

    7. Re:Benchmarks by Anonymous Coward · · Score: 0

      Name one person who has done what you describe.

    8. Re:Benchmarks by koinu · · Score: 1

      Hi!

      http://slashdot.org/submission/1780750/linux-3d-games-run-faster-on-pc-bsd

      The discussion has been archived... but a lot of Linux users criticized Phoronix for publishing bad benchmarks.

    9. Re:Benchmarks by Anonymous Coward · · Score: 0

      Not only that, but to heck with BSD. There is gentoo! I wanna compile my own stuff and customize like there is no tomorrow - there you go, gentoo. Linux kernel, BSD style package system where EVERYTHING(apart from a few packages) is compiled. Also, you can use binaries if you like. And from Phoronix tests, it seems that performance wise, linux is better!

      No wonder, i doubt BSD can be compared to Linux based on performance(photonix confirms it in every test). By all accounts customized linux beats any BSD any time of the day. And when i say linux, I don't mean Ubuntu(which is great for anyone looking for alternative to windows)

      it would be stupid to ask windows user to use BSD anyway. Smart people, not technical ones, may not be able to simply install some BSD falvours. Sad mother fckn fact of life.

    10. Re:Benchmarks by Anonymous Coward · · Score: 0

      So who's the Slashdotter who praised Phoronix when its benchmarks favored Linux and criticized it when its benchmarks favored Windows? Because I'm not seeing that in your link.

    11. Re:Benchmarks by Anonymous Coward · · Score: 0

      Oops. I should have said "disparaged Linux" rather than "favored Windows".

    12. Re:Benchmarks by Anonymous Coward · · Score: 0

      Can't do it, huh?

  42. Same reason as Gentoo is not as popular.. by GrumpyOldMan · · Score: 1

    .... Because a rolling release, build-it-yourself based software package model is too big of a hassle (ports tree, I'm looking at you).

    I've been a FreeBSD committer for over 10 years. I ran FreeBSD on the desktop for many years, but I switched to running Ubuntu Linux 4 years ago on my desktop because "apt-get install foo" and "apt-get update" are about 10x simpler and faster than doing the same things using the FreeBSD ports tree, and I don't have time to deal with broken dependancies, unfetchable files, etc.

    For those who don't know, FreeBSD base system is maintained directly by the FreeBSD "src" team, and is what constitutes a FreeBSD release. This is the "basic" stuff like the kernel, a few shells, fs utilities, ls, cron, a customized system compiler, etc. This stuff is rock solid, and security updates fix bugs.

    The "interesting" stuff (X server, web browser, most shells, perl, python, IDEs, etc) are provided by a rolling-release based "ports tree". The big problem is that the FreeBSD ports tree is a "rolling" release. If you need to update your X server due to a bug, you risk breaking some totally unrelated piece of software which has had a version update. Worse, you have to compile all ports yourself when you update, so updates are unnecessarily time consuming and complex.

    Compare this to say, an Ubuntu/Debian/Mint or RHEL/Centos/Fedora release where there are no huge surprises when updating. Every apt-get update or (or yum equivalent) fixes bugs, and you don't have to worry about an update to fix program "A" totally hosing program "B"

    This is the same reason why Debian or Red Hat based distros are so much more popular than "rolling release" distros like Arch or Gentoo.

    I have hope that the new PC-BSD might be as easy to deal with as Linux. I love their "PBI" concept, where every every package contains all of its dependencies. I'm planning to replace an older Fedora on my laptop with PC-BSD 9.

    1. Re:Same reason as Gentoo is not as popular.. by koinu · · Score: 1

      As a ports tree committer you should know that FreeBSD also has got packages for people who prefer time over customizability.

    2. Re:Same reason as Gentoo is not as popular.. by Xenophon+Fenderson, · · Score: 1

      Seconded, as a FreeBSD user since 3.x. I would never recommend it as a desktop operating system, and I have a really difficult time selling it as a server operating system, too, solely because of the ports tree. As an example, install FreeBSD 8.1 (the latest stable release) and add the binary GNOME packages during the installation. Then compare updating the base system (two built-in commands, a short download, plus a reboot) with updating GNOME (a built-in command to update the ports tree, one command to install a different package management tool from the ports tree, followed by a very long time waiting for GNOME and its dependencies to download and compile). That's the best possible case - where no package customization has been done and the various build- and run-time dependencies don't conflict. Unfortunately, the ports tree's dependency graph isn't consistent between FreeBSD releases, so there are plenty of degenerate cases, where for example the latest GNOME depends on a Samba 4.x executable and a Samba 3.x library that conflict with one another.

      FreeBSD has plenty of selling points: a solid base system, fantastic documentation, great performance. With the right tools and discipline, the ports tree gives system admins a great deal of flexibility over how third-party software packages get configured and installed. But this ability to be highly customized costs administrator time and effort, and for many it just isn't worth it.

      --
      I'm proud of my Northern Tibetian Heritage
    3. Re:Same reason as Gentoo is not as popular.. by GrumpyOldMan · · Score: 1

      I'm not a ports tree committer. I maintain a few device drivers in the src tree. I'm much less active than I was 10-12 years ago.

      And yes, I do know that there are packages. The problem with packages is that the packages are generally updated infrequently (like every point release), and when they are updated, they have new versions & dependencies, and not just bugfixes. So even if you (try to) do a binary update, you run into the same sort of unintended consequence where picking up a bugfix for package A hoses some unrelated package B.

      Back when I ran FreeBSD on the desktop, I used linux versions of web browsers, just so I could go outside the ports tree to get something I needed the latest version of & not have to worry about the newer dependancies for a browser causing me to have to update ports & possibly break something.

      IMHO, ports are the single biggest problem with FreeBSD.

    4. Re:Same reason as Gentoo is not as popular.. by synthespian · · Score: 1

      As an example, install FreeBSD 8.1 (the latest stable release) and add the binary GNOME packages during the installation. Then compare updating the base system (two built-in commands, a short download, plus a reboot) with updating GNOME

      Wait, dude, if you have any experience on BSD you know GNOME software is a major offender. Dependencies ahoy!, and no attempt to write portable Unix software. In fact, they've stated they plan to be Linux-only. In fact, wasn't Ulrich a certain Gnome guy who told everybody to fuck off on lists?

      All this self-centric brokenware linuxisms in FreeBSD will probably go away Real Soon Now as the systems moves further and further away from GNU stuff, such as moving to llvm, etc.

      Man, stuff in linux breaks so much, they couldn't get any standardization project going (Linux Standard Base or whatever). And congrats to Debian: the system relies on literally a thousand packaging ant-army that then feeds the result of its labor to the termite-army of Ubuntu, that feeds on the ant-army and then, with luck, upgrades won't break. Sure, standard, do-like-everyone-else installs are monitored by a legion of packagers (what they call "developers"), but walk toward the edge...Many have reported here - stuff breaks in Ubuntu (Debian is not much mentioned anymore). Problem is, you are dependent upon the Holy Packager and you are tool-bound. If apt pukes, you haven't a chance.

      Care to try a smarter package manager? Then try SuSE's or Mandriva's SMART -they use SAT solvers. If Debian is so advanced, why isn't it using a SAT solver, because that is what the theory demmands. Mandriva will warn you, though, that your dependency tree might come out looking like a little non-orthodox after using the installer with the SAT solver. No wonder no-one uses it, and it lies relegated to some obscure corner of the Known Intertubes. No, the reason apt sort-of-works is not because it's so well-designed. It's really the reason pyramids were built: they were made possible through slave-working. At least, with FreeBSD, I know what I'm buying: there it is, it's just a system to make makefiles easier on the user. So it means I get whatever (solid) dependency-tracking bsd make has (or don't "makes" have one? then why are we using them?).

      Today, there more than one tool in FreeBSD to handle port dependency tracking. Like I said in another post, if make's topological sorting produces another graph, then I can probably try a fix from another angle, because your solution is not tool-bound, like apt. Has anyone read apt's source code? I tried some years ago...very helpful comments, such as "Oh! Shit!"...Although, today portmanager is so good, that the only real trouble I recently had was a Java circular dependency issue, that I solved with a binary install (portmanager will install all of a ports dependencies before the port is installed - makes can have you walking up a branch to a dependency, fix, then back to reinstall - there's method to the madness (infrequent), if you want to do it like a Real Unix Dude).

      Separation from userland third-party software to base system is a plus. Much harder to end up in a dead end street. At least your kernel isn't screwed (I mentioned in another posts - search for academic papers on package managers - you'll find non-anecdotal reports of major breakage with apt/dpkg based systems - as in Oh, we fucked up the kernel kinda-of-breakage. Don't take my word for it, please.

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
    5. Re:Same reason as Gentoo is not as popular.. by synthespian · · Score: 2

      I'd like to add that some facets of FreeBSD's problem are really Unix problems (that includes Linux).

      For instance, is ports building relied on some sort of modern exception-handling mechanism, then we could have a system that automagically transversed upwards the edges of the graph starting from where the build tool threw the exception, instead of a system that simply signals that it borked.

      Anyway, for me I think FreeBSD, since it separates the package database from the potential tools, offers a much better future perspective for creating dependency-tracking installation software than the hard-coded ones of dpkg and rpm. These systems are nothing but another layer of complexity - if it weren't for that millionaire that created the Ubuntu team that piggybacks on Debian's legion of packagers, that approach would be long gone by now. Does anyone remember the pathetic situation Debian was in, which was the major reason Ubuntu even came into existence?...At the time, someone here on /. even produced a graph tracking number-of-packages versus time-to-deliver, and it showed clearly that Debian's assembly line was stalling in an exponential fashion, IIRC, as more software was being brought into the distro (Woody, was it?)

      So, to sum it up, I remain non-plus'd. I see no real good arguments, except anecdotes (some of them betraying lacking system-administration skills. In fact, I wish people would come out and just admit the real reason they perceive the purported superiority of Linux package management systems is because of the impatient and the childish "immediatism", because, frankly adults can't wait 5 or 10 minutes for a port to install (no, do not multiply 20,000 ports x 10 minutes, that is not how FreeBSD installation and upgrading works - not *all* your ports phase of of sync with upstream at the same time, do not be a moron).

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
  43. For Performance and Stability for a desktop... by jellomizer · · Score: 0

    Who cares.
    Linux/FreeBSD/OS X/Windows are all about the same.
    The Unix Based OS's (Linux/FreeBDS/OSx) have the advantage that for the most part they are immune to most viruses and spy where that slows your PC down.
    The Windows desktop when clean can run just as fast as those Unix Based OS's sometimes faster because they are better drivers for it. But it really comes down to how you use it. For you x is important so one OS does x better then the other. So you found your OS. But for the most part the OS is becoming more and more irrelevant due to more Web Based Software that actually follows the standards.

    --
    If something is so important that you feel the need to post it on the internet... It probably isn't that important.
  44. Performance? Really? by bmo · · Score: 1

    Let's take a look at the Top500.

    Both FreeBSD and Linux are free in all senses of the word. Licensing and costs are not barriers to using either one or swapping one for the other. One does not spend over a hundred million dollars on a system and chuck any old OS on it. One wants to squeeze the highest amount of performance (number crunching and data flinging over the interconnects) as one can. All things being equal, one selects for speed. One could argue that if Windows had an edge, it would have more of a toehold in the Top500 than it does now because of extra deep pockets or Microsoft giving a deep discount on licenses for bragging rights.

    Over 90 percent of the Top500 is Linux based. You would think that if FreeBSD had an edge, however slight, over Linux, you'd see the Top500 dominated by FreeBSD, or any BSD for that matter. Indeed, Microsoft has 6 times as many supercomputers running their OS than BSD. Before the Windows people get up to brag, the number of BSD systems is 1.

    Linux has been dominating and pushing out the standard Unices like BSD for years and for good reason.

    BSD is dying. The bad news rolls in like a river of tears.

    --
    BMO

  45. PC-BSD by fa2k · · Score: 1

    PC-BSD is built on FreeBSD, and does a great job of packaging up common desktop functionality. It comes with out of the box support for webcams , flash, sound, and a preconfigured desktop environment. It also has many common applications available as binary packages using its own package manager (including Skype, for example). When you need more applications you can turn to the ports tree, which is somewhat behind the common linux distros, because there is a long UPDATING file with manual tweaks necessary for updating. If you refrain from installing from ports, there are automatic binary updates in PC-BSD. Version 9 also supports automatic in-place upgrades of major versions. On the bad side, the support for sleep and hibernation is entirely reliant on the BIOS, meaning that it doesn't work (I've asked on the forum for a motherboard that supports ACPI S3 sleep, but I got no reply). There is no 3D acceleration with AMD graphics cards, so no dekstop effects are available (I've seen on the IRC that someone may be working on this). NVidia cards are supported using a binary driver, and comes with PC-BSD of course. The installer is very easy for any setup that's less complicated than ZFS mirroring + full disk encryption.

  46. observations don't match claims by DdJ · · Score: 1

    I've been running my home servers (web, mail, dialup, other) on Debian since before Debian got to version 1.0. I've run it on single processors and with SMP. I've run it on x86 and on Alpha.

    I've never had stability or performance problems due to the software.

    Is it possible that FreeBSD is more stable? I'll grant that it's possible, but... "the extra time required to really get a FreeBSD box tuned will come back in spades through performance and stability metrics"? Really? No, I cannot see how. I do not need more than five nines of uptime.

  47. Obvious flaw by dkleinsc · · Score: 1

    FTFS:

    Sure, it's quicker to build a Linux box, do a "yum install x y z" and toss it out into the wild as a fully functional server, but the extra time required to really get a FreeBSD box tuned will come back in spades through performance and stability metrics.

    Big deal. Yes, your machine might run slightly faster, but the simple fact is that computers spend a lot of their time idling these days (as they should). The whole point of computers is to value people time over machine time, and that means it's probably not worth the time to really tune your OS.

    Same story on stability: For desktops, stability is nice, but you aren't generally trying for really long uptimes.

    --
    I am officially gone from /. Long live http://www.soylentnews.com/
  48. The title is inaccurate by Narishma · · Score: 1

    The article talks about servers, not desktops.

    --
    Mada mada dane.
  49. IE 6-8 and Edge by tepples · · Score: 1

    And really, [Adobe Flash is] only necessary because of incompetent web developers anyways.

    Is it that, or is it because of the existing IE 6-8 user base whose browsers don't even support a lot of HTML5 features needed to make user interfaces comparable to those possible in Flex? Or is it because Adobe Edge (HTML5 counterpart to Flash CS) is still in preview?

    1. Re:IE 6-8 and Edge by hedwards · · Score: 1

      The sites where you have to have Flash tend to use it as a navigation element without an alternative. The sites that are using it for video mostly work with gnash. So, incompetence seems to be the most reasonable explanation for it. Even on Windows where Flash is "well" supported, it still sucks.

  50. No, I was talking about servers by Anonymous Coward · · Score: 1

    Not sure how this got marked as a desktop story. I am talking exclusively about servers in this piece.

    -Paul

  51. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  52. Too much religion with BSD by Nelson · · Score: 1, Informative

    Ubuntu (and it's variants) and OpenSuse are pretty damned good, it's literally minutes and you've got an integrated, modern KDE, or Unity or GNOME up and running. You want more software of security patches? It's just a couple clicks and you're there. Now if you had some concrete numbers on instability or performance numbers then you could talk about something, real numbers, not just hearsay.

    Thing is, I don't think you can find and interesting performance difference between Linux and FreeBSD, excluding the possibility that there might be a few pathological cases where one really out performs the other, and the Linux community is such that if you could produce a real benchmark, they'd invalidate it before too long and fix the performance problem. And from my own experience shipping products and running businesses on it, I don't think you could show a substantial difference in reliability. Now one thing I know you could measure the difference on is the amount of time managing them and I think Linux has a gigantic lead here.

    I'm not a BSD hater exactly, but they need a better story than they've had and they need a different sort of community. If you like oldskool like UNIX, real UNIX, then BSD is just the thing. If you want UNIXy like stuff with some more contemporary things (think upstart, systemd, I don't know a full desktop UI) then Linux is pretty clearly the choice. Now that newer stuff may not be what you want, I'm personally sort of surprised how well Linux does in the embedded world where a BSD might be far better suited in a multitude of ways. PCBSD is getting nice, it's still nowhere near the level of polish that Ubuntu is though. LLVM and Clang have finally provided them with a non-GCC build chain option, there has been a ton of cycles spent on GPL vs. BSD licenses and in this particular case, I don't see how BSD has benefited in those discussions, at the end of the day the difference fundamentally lets businesses do stuff and just not contribute it back. Maybe I'm wrong but while BSD was worrying about a build chain, Linux platforms were building GNOME and KDE and remarkably simple graphical installers and easy to use automatic patch systems and support for tons of hardware and the list goes on.

    1. Re:Too much religion with BSD by Anonymous Coward · · Score: 0

      Maybe I'm wrong but while BSD was worrying about a build chain, Linux platforms were building GNOME and KDE and remarkably simple graphical installers and easy to use automatic patch systems and support for tons of hardware and the list goes on.

      In a way, I think you are - KDE and Gnome have worked fine on at least FreeBSD (no idea about the others) for most of their lives, so both the Linux distros and FreeBSD have benefited almost equally from the work of the partially independent groups of people building those desktop environments.

    2. Re:Too much religion with BSD by Anonymous Coward · · Score: 0

      "Linux platforms were building GNOME and KDE and remarkably simple graphical installers and easy to use automatic patch systems and support for tons of hardware and the list goes on."

      Gnome and KDE are independent of linux and are irrelevant since the bsd's use them too.

      Freebsd has zfs, dtrace, nfs4, a new installer, support for tons of hardware, patch support, list goes on and on.

      What operating system you get just depends on what your requirements are.

      Oh and graphical installer and updating:
      http://pcbsd.org/

      The truth is it's becoming more a taste battle than anything as FreeBSD/PCBSD and Linux are getting on par with each other. Linux has a larger ecosystem and FreeBSD has a stronger software paradigm. In the end it's virtually a wash for most things.

      By the way, has linux gotten nfs working yet? And if yes, did it work after the next update?

      Oh, apt-get x,y,z == pkg_add x,y,z.

      If you want the truth, there is to much religion BSD(programmer/server os), Linux(kill microsoft), and Windows(fuck everybody). Apple religion is just a whole other world of too much not even on the same par with the others(just status symbolism does even come close).

      Sorry for the windows wording but I don't like beating around the bush and microsoft lost the privilege of a nice description long ago.

      Licenses by code availability (make/keep knowledge available to enhance society -- purpose of copyrights/patents)
      BSD -- short sighted
      GPL -- long term/permanent
      Apple/Microsoft/etc -- closed

    3. Re:Too much religion with BSD by synthespian · · Score: 1

      FreeBSD will have a graphical installers, IIRC what I read recently.

      And then, that would suffice?

      Linux has lot of PR. IBM wanted to beat Sun and it did, using Linux. Sun's dead. Good for IBM. IMHO, I would have like to have a world with more Solaris. Sun Microsystems was the principal providers of a Unix system that was used for serious commercial stuff, like CT scanners. I can't imagine the horror it would be if someone installed a piece of crap like Ubuntu on a critical device like that. The only Linux that will give that kind of commercial support Sun had, I guess, is Red Hat (but I'm not saying they are as trustworthy as Solaris...). Lo and behold, Red Hat sells per-seat licenses, and I've never heard that Stallman, the FSF, the GPL church goers complain.

      The part I don't really understand is, if Linux is so fucking good, how come it's one security breach after another? How come Debian's servers got hacked twice? So, you see, the criteria for "good" is a flexible one...

      --
      Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
    4. Re:Too much religion with BSD by iggymanz · · Score: 1

      The security breaches I saw would have worked on *any* OS, FreeBSD included.

      Do you have hard evidence that an Ubuntu server is crap? Not my favorite server os, I do like BSD better for servers, but we've a couple internet facing Ubuntu boxes at our company that have been running for years with no problems and doing millions of dollars of e-commerce per year.

      Sun support was for running on Sun hardware, with Linux (and more than just Red Hat), you can get support for wider variety of hardware.

      Solaris was closed source for most of its life. Sun even provided funds for the "new SCO" while it was attacked Linux, and even spread FUD of its own against LInux. So Sun and Solaris deserved to die. OpenSolaris was too little too late, and now its dead too. Just as well, who want Oracle running things?

  53. Did anyone bother to read the author's own comment by musial · · Score: 4, Informative

    "Note to all: Despite what you might read on Slashdot or other aggregators, this piece is about servers, not desktop FreeBSD use. Not sure how that got misconstrued, but I'm talking exclusively about server use. I haven't run *BSD on the desktop since 1998, hence my comment about Linux on the desktop and FreeBSD on the servers. "

  54. Re:Flash by Anonymous Coward · · Score: 0

    I assume they still don't have it.
    Wake me up when that happens and I will use FreeBSD on the desktop.

    Admittedly, the only reason I really use flash tbh is because of youtube, and now that there's minitube in the ports tree there's really no need for flash support technically.

  55. SMP performance by Larry_Dillon · · Score: 1

    Maybe there's a reason that over 80% of the Top 500 Supercomputers run Linux. I couldn't find FreeBSD on the list....

    --
    Competition Good, Monopoly Bad.
    1. Re:SMP performance by rev0lt · · Score: 1

      AFAIK most of the top 500 supercomputers run a heavily modified and customized version of linux, not your run-to-the-mill distro. Given that most BSDs were late to the "SMP race" and that Linux already supports a set of architectures at least as vast as netbsd, it is the ideal candidate to be tewaked and installed on those supercomputers. If by supercomputers you ment clusters, yes, there is a strong tradition of using linux for it because of projects like openmosix, and many proprietary scientific software is usually linux-compatible. That desn't mean you can't run it on freebsd, or create MPI applications, or use BSD nodes on your sun gid engine cluster.

    2. Re:SMP performance by TheRaven64 · · Score: 2

      Totally irrelevant. A typical supercomputer uses Linux as a glorified I/O controller. SMP performance in the kernel is irrelevant - jobs get given 100% control over the CPU for the time that they run. The kernel is there (often in a coprocessor) to handle I/O requests issued by the code running on the real hardware. They certainly aren't scheduling jobs on a supercomputer in the same way that they are on your desktop. If they were, it would be a pretty compelling reason to not use Linux on the desktop: supercomputers are all about throughput, and if a job has to wait a few minutes to get CPU time then that's fine as long as it gets a huge amount of CPU when it runs. Desktops are all about latency: if your code is using 20% of your CPU instead of 10%, you probably don't care, but you do care if you have to wait a user-noticeable amount of time (more than a few tens of ms) for a response to an interface action.

      --
      I am TheRaven on Soylent News
  56. Where's the BSD Love? by Anonymous Coward · · Score: 0

    I've used FreeBSD on the desktop since 2.1.5. A couple years back I gave Debian a whirl. I grew to dislike apt compared to pkg_*. Dependency management is a pain no matter what you run, but with linux the glibc dependencies drove me crazy. No such problem with FreeBSD. I also grew to dislike the levels of indirection for things like startup and configuration. I can remember doing a Debian upgrade and having my network interface fail to start. That's not insurmountable, but it is annoying. The interface was found and configured automagically the first time. (nice) I had to try a couple different edits before I got to the _actual_ place where network configuration was stored. (not so nice)

    I've been running FreeBSD with XFCE on version 7.0 and on for the last couple years. It works great. Oh, and it doesn't take any more time to install FreeBSD than Debian.

    Regards,
    Jason C. Wells

  57. FreeBSD is a step backward by sl4shd0rk · · Score: 1

    Linux does everything I need my comp to do except play games, but don't get me wrong; I think BSD is great. It's a great option. I'm glad the alternative exists. It has just got a loooonng way to go to catch-up with Linux. Consider all the legal wrangling in it's past. Libraries have had to be hacked up, cut up, forked and fondled. You can't just download/untar/compile (Ports ain't all that either). It's a whole new kind of dependency hell. If I wanted the experience of heating my living room via CPU I'd run Gentoo first.

    From a desktop perspective, It's taken over 20 years for OpenGL and the underlying X libraries on Linux to evolve far enough to be able to play Unreal Tournament or Quake 3 Arena, edit an MPEG, do a screencast, or even get a desktop screenshot. Yet, after 20 years things are still buggy and slow and difficult. I still can't pull down the OS Options menu on amazon and pick a Linux option when I buy the latest game (and Wine is just pathetic for gaming).

    If the unix desktop was all that great these days we'd see lots of mainstream inroads being made across the *nix platforms in general. Switching to BSD would be easy but it's not.It's too difficult. Yeah, Macintosh is BSD but what you get is another highly polished proprietary, paid-for, hacked up OS that nobody is quite sure what hell is going on with. Nothing compiles on it unless you write in objective C or succumb to the Apple kool-aid-kult. I'd still run Gentoo.

    --
    Join the Slashcott! Feb 10 thru Feb 17!
    1. Re:FreeBSD is a step backward by SchMoops · · Score: 1

      Good points. One minor objection: the objective-C/kool-aid thing is true for iOS, but not really for OSX (yet, at least).

  58. Striking a balance by Larry_Dillon · · Score: 1

    There's nothing wrong with FreeBSD, it just that for most of the companies I've worked for, Linux strikes a better balance between ease-of-use, features and stability. You might know how to install, configure, update, etc FreeBSD, but the guy that replaces you might not.

      Of course, it also has better vendor support the the *BSD's.

    --
    Competition Good, Monopoly Bad.
  59. Re:Flash by finarfinjge · · Score: 1

    They've had it for years, there's at least two different ways of doing it. The easiest way is just using Wine and the Windows version of Firefox. The other way is to just use the Linux version of Flash. And really, it's only necessary because of incompetent web developers anyways.

    These sorts of FUD posts about a largely unimportant feature that isn't native, is really not conducive to a decent discussion.

    Are you serious? Flash is an unimportant feature? What year did you fall asleep? It's 2011 now.

  60. Stable = Inert by NicknamesAreStupid · · Score: 1

    The best things in life are free, and that is why people don't buy the best. It is better to live on the edge of life and run Windows. Those who cannot bear such excitement use MacOS, which has its roots in BSD. I, on the other hand, run OS/VS2 and submitted this comment using JES job. Browsing the web is so much more exciting using a deck of Hollerith cards and a TTY terminal.

  61. Video drivers? by Anonymous Coward · · Score: 0

    Every Linux box that I've ever had, the main and usually only cause of instability (other than dodgy hardware) is closed source graphics card drivers. If FreeBSD have fixed that, I'm sold. Or is their stability of the so-long-as-you-don't-want-decent-performance-in-X variety?

  62. Lacking Hardware Vendor Support by burning-toast · · Score: 1

    More or less, FreeBSD is not commonly supported by the same hardware vendors which do provide Linux support and drivers. RedHat / Fedora / CentOS is most commonly supported by the hardware vendors. Debian/Ubuntu is a close second. If I want full support of the features in my new Core-i7, NVidia graphics card, SSD hard disk, InkJet printers, or WIFI cards I am much more likely to get traction in the Linux space (and even that has been a long and hard road and is still sketchy coverage at best).

    And for the server space, when you start getting into various RAID controllers, out of band management drivers (and SNMP MIBS), 10Gb networking, and fiber channel cards; the picture looks pretty much the same as in the desktop space.

    So yeah, if all I want is a web, FTP, ssh, or similar server on standard (commodity) hardware then FreeBSD and variants are a perfectly valid option... until I want to start using SAN, 10Gb networking, fiber channel or centralized lights-out administration technologies (hardware out of band monitoring) where Linux support is common, but BSD support is not so much.

    I work in an industry which requires extremely low latency (quasi-realtime server response times) which FreeBSD would be OK for, however the hardware we must use to achieve those results is NOT supported on FreeBSD by the vendors which make the drivers, nor are the 3rd-party libraries we use for communication with other data vendors.

    Switching the OS to something more well supported is MUCH easier than trying to get all of the rest of the applications, drivers, and vendors to switch without some sort of tangible reason for it.

    - Toast

  63. Gnome..KDE...yuck by Anonymous Coward · · Score: 0

    FreeBSD rules, Linux sucks. Ubuntu might as well be Windows...all noob friendly.

  64. its broken by Anonymous Coward · · Score: 0

    Drivers. Good luck getting a modern amd/ati card working. On a server, that might be fine. On a desktop, good use convincing someone to run an os without their gpu, sound card, or trackpad. And yes, all of those are devices on my new toshiba laptop which freebsd lacks support for.

    1. Re:its broken by koinu · · Score: 1

      In my opinion... you bought this hardware, so it's YOU who made a mistake.

      That means for me that your hardware does not support FreeBSD. I select my hardware more carefully, because FreeBSD is the top priority.

      Do you also buy a Playstation game and complain that it does not run on your Wii?

  65. ROI Baby by chimerafun · · Score: 1

    Computers and redundancy are relatively cheap these days the engineers to set them up and maintain them are really expensive. Perfection isn't needed when you can afford redundancy and automation.

  66. Post moded Flaim Bait by Anonymous Coward · · Score: 0

    On the other hand, where is all the BSD hate from the old days on Slashdot?

    1. Re:Post moded Flaim Bait by Anonymous Coward · · Score: 0

      Linux is the new cult with radical acolytes and extremists.

      It's members chant "You shall have no OS besides me. Everything else Sux and is a toy. Only Linux users are 1337. Linux, Linux over all."

  67. Re:Flash by clarkn0va · · Score: 1

    I can't speak for FreeBSD, but Flash is not built into Chrome in Linux. I had to install the plugin separately. Not so for my Windows desk, of course.

    --
    I am literally 3000 tokens away from the chaotic crossbow --Stephen
  68. Re:Performance? Really? by Anonymous Coward · · Score: 0

    Youre an idiot

  69. I switched my FBSD laptop to Linux by damn_registrars · · Score: 1

    FreeBSD has some great features, but most of them are lost on the desktop/laptop. Even more so, a lot of software that is important to a lot of users doesn't care about FreeBSD (wine comes to mind in particular on this one) and FreeBSD doesn't tend to care about those ports / packages because they aren't important to the mission of "the power to serve".

    --
    Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
  70. BSDs on Desktops by unixisc · · Score: 2

    Isn't the FreeBSD that Apple uses a variant that sits on top of Mach 3.0? Whereas IIRC, FreeBSD itself doesn't use Mach.

    One thing I didn't get - did the article focus on just FreeBSD, or was it a generic question about BSDs? In other words, was the author wondering why people don't use any of the BSD distros out there - FreeBSD, NetBSD, OpenBSD or TrustedBSD? (And yeah, I did read the full article, but didn't get which of the above questions it was!)

  71. spam processing by Onymous+Coward · · Score: 1

    this box generally deals with 250,000 to 300,000 emails a day (mostly spam, which produces a heavier load than actual mail delivery)

    Huh. Half my incoming spam is nixed at HELO.

    And, arguably, the load for spam analysis is undertaken whether the message is spam or ham.

    I've seen Paul Venezia articles linked before. I can't remember if it had a similar level of dubiousness, but I'm wondering now.

    1. Re:spam processing by Anonymous Coward · · Score: 0

      I've seen situations where there are only a handful of actual user mail accounts and the domain is getting hammered by dictionary spam attacks. In that case, the ratio of spam:ham can be 5000:1 or even higher. Thus, it's a significantly heavier load than actual mail delivery.

    2. Re:spam processing by Onymous+Coward · · Score: 1

      Oh, I see. It's not that the spam is harder to process than the ham, it's just that there's more of it.

      That wasn't how I read Venezia's blog. I took him as saying that spam is harder per unit than regular mail to process.

  72. Here is why... by fhuglegads · · Score: 1

    I put Ubuntu on my girlfriends laptop and she loves it. I downloaded the latest iso. Easily had it partition the drive, set up the boot loader, install the os and the video, network and audio drivers were all installed. Since she wants to watch tv shows online and check email and facebook she has a great environment (I did put in Gnome and let her pick between that and Unity and she picked Gnome) to mess around in and the effort level on a scale of 1 to 10 was a 2. What would BSD have done for me that U11.10 didn't?

  73. Pah by Anonymous Coward · · Score: 0

    Just repurposed a G4 Powerbook. Was planning to use FreeBSD... It took longer to just build X on FreeBSD (which, of course, failed the first three times and never did get more than 8-bit color before I shitcanned the idea) than it took to install, configure and customize MintPPC as a fully usable system.

  74. I only have 1042 days of uptime by Anonymous Coward · · Score: 0

    My Suse Enterprise Linux Server has only been up for 1042 days. Paul's FreeBSD box really has me on system stability. The bottom line is I don't see any advantage to using FreeBSD for what I do. If other people do, then more power to them.

  75. I just want it to work by ThinkDifferently · · Score: 1

    Most people, perhaps geeks included (myself certainly) just want their desktop to work. I'll worry about what OS to choose for my server, but my desktop just needs to be (a) compatible with all of the latest hardware, (b) able to run loads of great software for pictures, videos, games, desktop publishing, etc. and (c) just work when I want it to. I have enough to worry about. Building my OS from scratch and compiling the software for it just isn't on my to do list.

    My personal experience with FreeBSD has been 2 motherboards that wouldn't work, because nobody in the community could figure out the drivers for them, no hardware RAID support for the card I wanted, and several days of my life getting it all loaded and configured the way I needed. No thank you, not again!

  76. Hardware and apps by Anonymous Coward · · Score: 0

    I like FreeBSD, especially the PC-BSD spin-off, but neither works on my hardware. Nor are all the applications I use on Linux available in the ports collection. Put another way, I don't run FreeBSD on my desktop/laptop because it won't run on my hardware and can't run the programs I want. That makes the OS pretty useless in my case.

  77. yeah right by wasabii · · Score: 1

    "but the extra time required to really get a FreeBSD box tuned will come back in spades through performance and stability metrics. You'll get more out of the hardware, be that virtual or physical, than you will on a generic Linux binary installation.'"

    Prove it.

  78. BTX halted by sveni · · Score: 1

    I just tried to install FreeBSD-8.2 on my laptop, but I wasn't even able to boot the installation CD or DVD or USB stick image.
    All i get to see is a list of registers and finaly the line

    BTX halted

    Same with PC-BSD.

    After searching the net for this, I found the advise to turn off AHCI in the BIOS, which isn't possible, because the bios setup of my laptop is pretty minimal. So now I'm stuck.

    So if anyone wonders why more folks aren't using FreeBSD on the desktop, this is the reason.
    At least for me.

    Sven

  79. Re:Flash by somersault · · Score: 1

    How long ago was that? I see news stories from 2009 saying Chrome for Linux ships with a built in flash plug in.

    --
    which is totally what she said
  80. Re:Flash by clarkn0va · · Score: 1

    Clean install of Ubuntu six months ago, updated less than a week ago. Chrome is installed via Google's .deb installer, which adds their repo's to apt.

    I am running 64-bit though. Possibly the 32-bit version of Chrome on Linux comes with Flash preinstalled, but I wouldn't know.

    --
    I am literally 3000 tokens away from the chaotic crossbow --Stephen
  81. kFreeBSD by unixisc · · Score: 1

    Since a lot of people have mentioned how they switched from FreeBSD to Debian Linux, wouldn't they be getting the best of both worlds if they switched from FreeBSD to Debian's kFreeBSD? I.e not have utilities change b/w versions, but still be able to use Debian packages and other such features?

    1. Re:kFreeBSD by m50d · · Score: 1

      GNU/kFreeBSD still has no native threading - you have to use libpthread like in the early days of linux 2.4. Meaning multithreaded performance will be poor, which is a big deal on today's multicore machines. I would like a better package management system on freebsd, but I've got more faith in the gentoo-on-freebsd project to deliver it.

      --
      I am trolling
    2. Re:kFreeBSD by koinu · · Score: 1

      You don't need to "switch" you can run Debian in a FreeBSD Jail, if you want.... but I always prefer FreeBSD Jails over Debian Jails.

  82. Too much weird behavior in FreeBSD by Anonymous Coward · · Score: 0

    We develop authentication software for Aix, HPUX, Solaris, FreeBSD, Mac OS X, and Linux. We have quite a few issues getting the FreeBSD desktop to work out of the box before we even try integrating our software. Some of the issues we've come across are non-standard PAM (configuration files can be located in multiple places, generates console messages for odd reasons), getting Gnome set up properly can be a real pain, login names limited to 15 characters by default (a huge number of corporations use LDAP or first.last name or something that violates that limit (and the limit is done wrong and can lead to a simple root exploit)). Now some of these could just be errors because I didn't read the docs right, but I have read a lot of FreeBSD docs.

    After having messed with FreeBSD at work for a few years, I would never install it for the desktop and the bugs I've seen would make me reconsider it as suitable for the server.

  83. List of advantages by jbolden · · Score: 1

    I think the list of advantages pretty much explains why: DTrace, ZFS, pf firewall, and more standard TCP stack. Even Linux/Unix desktop users don't generally care too much about that (ZFS possibly exempted). The advantages of FreeBSD aren't solving problems desktop users face. The problem with Linux in general is that it is too annoying to configure apps. FreeBSD is no worse than say Debian but much worse than the popular Linuxes: Ubuntu, Mint, Mandriva... when it comes to configured apps.

    And as for the other BSDs, they are even worse choices for the desktop. As a niche, sure. If it is a BSD shop (and I've worked in those) sure. But otherwise?

  84. Why I don't use FreeBSD on the desktop.... by MrNthDegree · · Score: 1

    FreeBSD variants of most features are inferior to Linux variants. Excluding ZFS, Grand Central Dispatch (and of course the friendly developers very willing to help end-users without flaming on official lists)... allow me to explain why I find FreeBSD completely inferior on the desktop:

    Linux: Kernel Namespaces (with cgroups)
    FBSD: Jails

    Kernel namespaces are more flexible and are designed for individual apps as well as full containers. One can isolate in many different ways and on many more different levels with kernel namespaces. In addition, cgroups provide better granularity over scheduling and RAM use in a jailed environment, as well as for individual apps and such granularity may be nested ;-)

    Example 1: I want a separate network namespace but not filesystem isolation
    Example 2: I want to have a restricted /dev tree and my app to only see it's own PID (as PID 1) and have restricted CPU/RAM use but no filesystem isolation
    Example 3: I just want a separate set of virtual terminals, so I can run truly unprivileged SSH that can only login as one user, without screwing over permissions on my desktop VTs...
    Example 4: I want a jail with limited RAM, CPU, allow IPC safely, allow access to only a specific graphics card and per-user /tmp namespaces for added safety between users

    None of this stuff can be done in a non-convoluted way with jails, when compared to the Linux equivalent.

    Linux: CFS Scheduler
    FBSD: ULE Scheduler

    Both are designed with desktop interactivity in mind on one level or another. But CFS supports cgroups, providing far more granular control over process priority than that of ULE, making it inferior on the desktop. Nesting of CPU limitations makes it possible for desktop applications to never lock-up the Xorg server via CPU usage, while on ULE, it is possible in my experience to lock-up the desktop with five or more unresponsive applications hogging CPU time.

    Linux: CFQ
    FBSD: C-LOCK (elevator)

    Welcome to I/O hell people. 2 apps using the HDD will lock up the desktop totally on FreeBSD, because the I/O scheduler is crap for desktop use. While on Linux, CFQ handles I/O far more gracefully, without totally locking up the desktop (until 8 or more apps hog the HDD with random write patterns). Ironically, Windows in my experience handles constant random write patterns the best... but I suspect some proprietary hackery in Windows elevates the priority of core system components to avoid lockups from being as noticeable.

    Linux: ASLR
    FBSD: No ASLR

    Address Space Layout Randomisation. Even Windows supports this for its wonderful protection against address-specific exploits when combined with No eXecute (NX).

    Linux: KMS and/or UMS
    FBSD: Only UMS

    Kernel Mode Setting is used by almost all modern 3D-supporting F/LOSS Xorg drivers. Without it FreeBSD can't run the latest graphics card drivers.

    Linux: ext4
    FBSD: UFS

    Until recently (-CURRENT) background fsck would run, gobbling up tons of resources in the background post-crash (in -CURRENT, UFS cleans up any issues via journal, in addition to Soft Updates). As much as I like Soft Updates, ext4 is just so much better when it comes to overall I/O performance in my (admittedly, non-scientific) experience.

    Linux: ALSA
    FBSD: OSS

    On Linux, every onboard sound card i've come across has been way better supported than on FreeBSD. In addition, devices like my USB webcams have also always been way better supported. ALSA is also far more stable and with PulseAudio sitting on top, provides better per-app volume controls.

  85. Re:Flash by hedwards · · Score: 1

    Yes, it's an unimportant feature. The most common use of Flash is those annoying ads, and for things like YouTube, you have the option of gnash. YouTube itself is getting out of Flash and migrating to HTML5.

    I'm sure there are still some incompetently designed sites that require Flash, but it's not like it used to be several years back, I rarely encounter sites where a lack of Flash is a deal breaker.

  86. Linux on the server, FreeBSD if it installs. by Murdoch5 · · Score: 1

    After reading the article I have only two major things to point out against FreeBSD which I feel is why it's losing out. First of all the installer is a mess, I've only ever been able to boot the installer in safe mode and I've never been able to finish a full install of the system, I've tried about 10 times. Now I've been in the IRC channel and they keep telling my drives have a faulty IDE controllers and etc.... but seriously if Linux can install perfectly fine then there is no reason FreeBSD shouldn't be able to.

    The second thing I want to point is the learning curve is incredible. They say the learning the curve for Gentoo Linux is big but it doesn't hold a candle to FreeBSD, not even close. If they made the FreeBSD system operate more like a Linux system then I think this could also help.

    In closing I think if they just cleaned up the installer and the base system to be more Linux like, doesn't have to be GUI based, they could probably convert a lot of Linux users over. .

  87. New users don't stick around by Anonymous Coward · · Score: 0

    As a user that's been attempting to put together a functional linux/bsd box since the late 90's I've got one comment - lack of support. I've built and installed several flavors of linux, with a friend's help I manage a BSD router/ftp server, and I'm putting together an ubuntu box running xbmc for video at home. Am I capable of making the OS work for 90% of my needs? Yes I am. It's that othr 10% that usually gets me moving back to microsoft. I get on forums to ask questions, and the moment it becomes obvious I'm a newbie the forum respones dry right up. The community wants to see the operating system flourish, but the majority of users either point a newbie to a section of the manual or simply don't respond. The new user base can't possibly learn to properly edit conf files or recompile kernels without a bit of help, and when veteran users feel that providing this help is beneath them you have your answer.

  88. Re:Flash by koinu · · Score: 1

    They have, but who wants to install any browser plugins? We aren't in the 90s anymore.

  89. All could be unix by Anonymous Coward · · Score: 0

    Chances are, if all the distros out there of both BSD and Linux (as well as Hurd & Minix in future) were subjected to the Open Group's certification tests, they'd all pass. The only reason to not call them Unix is that nobody has thought of subjecting any of them to such tests.

  90. lack of Real Time kernel by ffflala · · Score: 1

    Multi-track audio recording is something I always want on my desktop. For multitrack recording, latency is key. Real time access is what makes it possible on Linux (I think Ingo Molnar did most of the work on that.) Anything around 6ms or higher is too much. Maybe it's possible to have single-digit latency w/out an RT kernel, but I've never seen it.

    I believe that real time kernel is simply theoretically incompatible w/ BSD's security model. Unless they can get the latency down to usable levels, it'll never work for my desktop.

  91. Re:Did anyone bother to read the author's own comm by sootman · · Score: 1

    Welcome to Slashdot, where even the submitters don't RTFA.

    --
    Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
  92. Finally!!!! by batistuta · · Score: 1

    Yes!! Yes!!! After this post, this might finally be the year of the FreeBSD Desktop!!!

  93. Article was about servers, not desktop by daffmeister · · Score: 1

    Did the submitter (or editor, ha ha) even read the article? Or even read the article headline: "Why aren't you using FreeBSD?".

    Nowhere does he mention the desktop except to say "There used to be a saying -- at least I've said it many times -- that my workstations run Linux, my servers run FreeBSD", and he finishes with "you may decide you'd be better off running FreeBSD on the next set of Web servers, SMTP relays, or application servers you build".

    Staggering lack of reading comprehension.

  94. How Much Uptime is Needed for a PC? by Anonymous Coward · · Score: 0

    Why is uptime so important for a PC? Most of the PC's are rebooted daily, or at least weekly, thus there is no need to be able to run 5000 days w/o reboot. A few days uptime is good enough for me. Even if it crashes once in a while, it's not the end of the world, I let my 2 yr old play on the computer anyways.

  95. Has the OP ever worked in an enterprise? by Anonymous Coward · · Score: 0

    When your server-to-admin ratio is in excess of 60-to-1 and your server counts is in the thousands, a "generic X binary distribution" scales a bit more effectively than a shitload of one-off custom-tuned Y installations.

    True for any X and Y.

    Not all of us are hobbyists with unlimited time to tune and tweak. From the time the installation media finishes, I'm lucky to have 10 minutes hands-on a given installation to configure networking, get any SAN/filesystem space up, set password policy and create a handful of user accounts before it gets turned over to the users.

    An analogy would be that of a fleet-vehicle maintenance crew versus a shade-tree hobby mechanic. The STHM may be able to tune and tweak their single Crown Vic to be the hottest thing on 4 wheels. The fleet maintenance team can't give that kind of attention to one car, we've got hundreds to keep running.

  96. Works for me since 1995 or so... by Anonymous Coward · · Score: 0

    FreeBSD on the desktop, this works for me, thank you very much.

    The last time I rebooted was for the upgrade to 8.1-REL.

    After a few months I've to restart firefox, but otherwise: It just works.

  97. FreeNAS by HuguesT · · Score: 1

    FreeNAS is the project that got me finally using FreeBSD. I have it in my 2004-era single core Athlon64 box full of (new) disks. Everything is supported included the newer SATA controller and the Gigabit ethernet NIC. It runs ZFS well in spite of only having 2GB of RAM, and it is hosting my backup. It is easily controllable via its web interface.

    No way I'm using this on the desktop though.

  98. Absolutely great - unless: by DF5JT · · Score: 1

    * you want Suspend2RAM work on a notebook. Even an old T60p doesn't wake up after suspend

    * you want DVB - There used to be a driver, but with the USB-stack rewrite this doesn't work anymore

    * you actually want to use Flash

    * you want to use your ext2/3/4 filesystem, say from your old /home

    I like FreeBSD, in fact I started my *ix experience with 2.2.6, but for regular desktop use, the above are true show stoppers, at least for me.

    1. Re:Absolutely great - unless: by hhw · · Score: 1

      Flash has worked pretty well on FreeBSD for years now, using nspluginwrapper. ext2 has pretty much always been supported, and ext3 can be mounted as ext2.

      --
      http://astutehosting.com/
  99. Re:Flash by synthespian · · Score: 1

    What's minitube? Enlighten us.

    --
    Main difference between the BSD license and the GPL license: one is from California and the other is from Massachusetts
  100. Linux configuration is convoluted by Anonymous Coward · · Score: 0

    Compared to FreeBSD, configuring a linux box is quite a hair pulling experience. Why must syntax change for all of the simplest commands? Because somebody wanted to urinate on their own corner of the OS? NO! BAD LINUX USER!!!

    Tell me, if linux is so great, why did I spend 5+ years trying various linux versions only to leave dissatisfied and angry? It took me less than a year to get hooked on FreeBSD.

  101. 1. Hardware. 2. Software. by David+Gerard · · Score: 1

    I used to run FreeBSD on the desktop and liked it a whole lot. It's a really nice Unix and I deeply approve of it.

    The secondary reason for giving it up was that Linux supports more hardware, specifically the laptop I had at the time.

    The primary reason was that the ports system sucks ass, and when I tried synaptic on Ubuntu that converted me.

    YMMV, of course.

    --
    http://rocknerd.co.uk
  102. Stability by QuasiRob · · Score: 1

    rob> uname -a
    FreeBSD 4.11-RELEASE FreeBSD 4.11-RELEASE #0: Mon Oct 10 15:43:12 BST 2005
    rob> date
    Tue Nov 8 22:26:49 GMT 2011
    rob> uptime
    10:26PM up 2084 days, 7:27, 1 user, load averages: 0.29, 0.32, 0.26

    --
    If you try to fail and succeed, which have you done?
  103. Re:Did anyone bother to read the author's own comm by ghmh · · Score: 1

    Indeed. Did anyone bother to even read the article first?

    I clicked the article because the Slashdot headline mentioned FreeBSD on the desktop. The article doesn't even _contain_ the word desktop, and there's only a passing reference to 'workstations' made by the author "that my workstations run Linux, my servers run FreeBSD".

    I've come to the conclusion that Slashdot's primary reason for existence now is for simply testing your powers of observation.

  104. Submitter is an idiot. by drolli · · Score: 1

    Not the time will not come back in spades.

    I was unhappy enough to use a server at work where somebody believed he is better in getting a freebsd system with a kernel configured by him stable and running as a server than a dedicated linux configured and supported for a specific hardware (e.g. HP servers which are certified for Redhat). I can say: no, he was not....

    It may seem to you that you can do all the testing and problem solving easily and that the idiots just put in too much features, but in a real use case you may have a tricky locking issue between samba and multiple clients. You may have some configuration which creates data corruption under highly specific circumstances. You may even have weird performance bumps which you never figure out.

    Yes. You could do it. If you know the kernel well. If you invest time. And if you have the resources and skills to reproduce the test cases well enough.

    Users will be pissed if they loose Data once to a weird locking problem and they will be more pissed if that happens twice. If you cant figure it out then the server is completely useless until you figure it out.

    Unless you have that, please use yum or apt-get to install preconfigured software. Your creative freedom should be the one to choose the right (linux) distribution (Remark: If you need it running and fixed, the buy support). There is at least one for everybody nowadays.

  105. As a FreeBSD desktop user by ZorkZero · · Score: 1

    I moved from Linux to FreeBSD on the desktop something like 10 years ago. The same arguments apply as used to apply in the Linux vs. Windows debate. FreeBSD is more secure than Linux (but is that because it's less of a target?) Linux has better Flash support (with its attendant security holes.) FreeBSD has the ports system and ZFS though, and the system is cleaner, better integrated, easier to maintain, and I simply like it better. Use whatever OS you want for whatever you use it for. For me FreeBSD beats Linux any day.

  106. Virtualisation by FerretallicA · · Score: 1

    I'd love to use PC-BSD as my main host/desktop OS but for me it boils down to: 1) No Vmware support 2) Very patchy Virtualbox support Vmware adamantly refuse to ever support BSD, and the drive for thorough Virtualbox is half-hearted enough that I'm not expecting any noteworthy progress in the foreseeable future.

    --
    Smoke my peg.
  107. But ... but ... if you don't use GPL software ... by harryjohnston · · Score: 1

    ... people will steal your code!

  108. A major flaw in Linux Distros by Anonymous Coward · · Score: 0

    Having just spent a couple of weeks performance tuning RHEL servers and workstations for maximum 10GbE throughput (incl disk and NFS tuning) it strikes me that this is a massive hole in the capabilities of Linux. When I install linux why can't I check a box that says: optimise for single user or multi user; and another for maximum throughput vs balanced or redundancy. If you want linux to make inroads into uninformed userland rather than propellorheadland then you need to make config a bugger of a lot easier. Oh, and by the way, Yum is a total abortion of a package manager. Joe average user does not want dependency hell when trying to install skype... why does it only seem to be Debian (that I know of) that will handle all of that elegantly for you?

  109. BSD is not a desktop OS by Cherubim1 · · Score: 1

    One would have to be a masochist to run FreeBSD On the desktop. It's way too cryptic and limited in functionality for dssktop use. Hardware support is not as extensive as Linux and it lacks simple things like a native flash player. Nope. BSD should stick to servers.

  110. it is of limited use by smash · · Score: 1

    ... and i say that as a current freebsd user, who has dealt with it on the desktop on a fairly regular basis up to 7.1.

    The benefits you get from it are of limited importance to a desktop user, and if i need to test something on BSD before deploying it to servers, its small enough to run in a VM under Windows or OS X in any case. The drawbacks (3d hardware support, commercial software support, etc) outweigh the benefits for a desktop user. Most desktops are turning into laptops these days also, and this is not a focus of freebsd development.

    If you want freebsd on the desktop with support for things like flash, hardware support, etc what you probably really want, is to let go of your bias and just get a mac.

    This is what I did, and couldn't be happier. Most things "just work". If i want the unix shell, it is there. If i want GCC (or clang), it is there. Plus there is neat stuff like applescript and automator to boot.

    Unfortunately, some people think that one OS should be capable of fulfilling all tasks, and unfortunately (or fortunately) that just isn't the case. But when all you have is a hammer, everything looks like a nail....

    Figure out what apps you want to run, determine what operating systems support those apps, and make your choice. For me, that works out to be FreeBSD for internet facing devices, Windows 2008R2 for stuff at work, and OS X at home. Yes, you can make choices outside of that and make it work, but the number of IT staff who are savvy enough to make things work, and support them when you go against the grain are a lot fewer. And personally i like the ability to take a holiday if i want and leave work behind to someone else.

    --
    I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    1. Re:it is of limited use by Cherubim1 · · Score: 1

      MacOS X is not BSD Unix - it's a bastardised fork of BSD (Darwin) which borrows some FreeBSD/NetBSD and Mach components. It's a pity Apple left out most the security enhancements from FreeBSD.

    2. Re:it is of limited use by Anonymous Coward · · Score: 0

      MacOS X is not BSD Unix

      Yes it is.

      I'm not sure what you think Apple would need to do to make it "real BSD," but if it looks like a duck and walks like a duck and quacks like a duck...

    3. Re:it is of limited use by smash · · Score: 1

      Whether it is by your definition or not, it works the same as far as desktop use goes. Care to cite what security enhancements have been left out that matter for desktop use (which is what we're talking about here)?

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
  111. vices of decentralisation still are lesser evils by Predatory+QQmber · · Score: 1

    You have to wait for the Package Masters...Also, with ports I have a much more fine-grained control. But let's get this out of the way: you can install packages in FreeBSD, and you do binary upgrades. There are lots of tools to handle ports. With today's speeds and RAMs, it's no big deal compiling ports.

    I look at today's Linux and I don't regret my choice. What's the sane choice? Fedora is an experimental platform for Red Hat. That means, from time to time, they'll make you their guinea pigs...Debian can't even be considered secure (no less than twice they had their servers hacked), and who cares about dinossaurs, anyway? Ubuntu's the new Debian. Ubuntu shoves their choices down your throat and continues the Debian tradition of delivering broken software (the new GUI, etc.) and infighting. And Ubuntu is a fantasy. The only reason it exists is because there's a money-loosing millionaire backing it up. The fantasy island one day will blow up in the fanboys' face. Mandriva I find agreeable, but they don't offer many packages, and they have too few commercial partners (so why pay?) Other distros aren't even worth mentioning.

    and this is why i use Gentoo (source-based distro with binary installation support; pretty much FreeBSD of GNU/Linux) and my girlfriend uses Sabayon (binary-based Gentoo-derivative with source-based installation support).

    I've used expensive proprietary mathematical software for Linux on FreeBSD, using their Linux binary layer, after the Linux upgrade destroyed library compatibility (they pride themselves in having unstable ABIs).

    no, "they" take pride in doing their thing with disregard to proprietary requirements (which mostly are in not changing architectural design as long as proprietary authors are unwilling to make changes in the basis of their software which relies on that design. and they mostly always indefinitely are).

    Linux are a mess. Each one is different, full of stupid little quirks.

    well, you can't please everyone by the same thing.

    Libraries differ in place, version, even names.

    which is an inevitable consequence of things rapidly happening. 'stable' branches are made exactly to counterpart that but you said it yourself - they are stagnate.
    though i too believe that there is a problem with this: there is no distinction between feature-complete "stable" and on-the-way "development" branches because there are no proper roadmaps in most GNU/Linux-centric software . BUT distro maintainers can't do much about that.

    FreeBSD is just as good for the desktop.

    sorry, but i, like most people, prefer to, at least, have useful video output on my desktop's monitor :) and for that working video drivers are needed, but i haven't heard anything good about those in *BSD.

    FreeBSD maybe is a perfectly good server OS for some instances but i still would generally prefer CentOS/RH or OpenSUSE and specific distros for specific purposes

    --
    who dares wins
  112. Re:Did anyone bother to read the author's own comm by Anonymous Coward · · Score: 0

    Sad part is for most here the desktop is their server...

  113. Re:Did anyone bother to read the author's own comm by Anonymous Coward · · Score: 0

    Your post wins musial! I've never bothered to figure out the mod point system but if I had I would mod you 1000000!!! (Yes, with the exclamation mark)

    There's a reason for acronyms like RTFA and TL;DR. The reason is being a know-it-all-computer-nerd. If we had to RTFM before we posted... well we wouldn't already know the answer before we started and then what kind of a know-it-all would we be? Not very knowing. That's some strange off topic idea like listening.

  114. Java Support by dave87656 · · Score: 1

    How is java support these days?

    We have an internal application and I could chose which OS I wanted back in 2001. I really wanted FreeBSD -- it just seemed faster and more coherent. Configuring the system and various userland settings worked similarly whereas Linux was all over the place. But, I was writing the application in Java and FreeBSD didn't support it natively then.

    Is there native support for JDK 6 or ... dare I ask ... 7?

  115. why bother by Anonymous Coward · · Score: 0

    I used to install and play with most of the linux and *nix flavors out there, loved Debian, FreeBSD, OpenBSD etc. Still prefer OpenBSD on firewalls. Running linux/*nix on my desktop frankly costed me too must time at work, struggle to work with the exchange server, struggle to do smbmount's etc. the whole time when developers dump code on fileservers that I need to deploy, etc. yes...I could and have automated alot of it. FreeBSD and Debian is just too far behind, our developers code break on them. Frankly I am geeked out, lost too much of my live tinkering with linux, *nix, got a macbook pro, and run ubuntu server and could not be happier.

  116. Re:Did anyone bother to read the author's own comm by koinu · · Score: 1

    I haven't run *BSD on the desktop since 1998

    I'm running FreeBSD on desktop since 2001.

  117. Misleading title by ReeceTarbert · · Score: 1

    Paul Venezia is not wondering why more folks aren't using FreeBSD on the desktop: on the first page he tells us about the uptime of his server (which runs FreeBSD) and whatever he has to say about other uses of FreeBSD is on page two -- and quoted in full in the summary. In other words, he's not making a strong case in favor of FreeBSD on the desktop, except for a generic reference to "performance and stability" which, let's be honest, could be said just about any recent OS.

    That said, my desktop of choice is FreeBSD and not because I dislike Linux, but because I like FreeBSD better and, assuming you have the right hardware, it makes for a more than viable desktop. And no, I don't think that hardware support is as limited as it used to be: for instance my little ZOTAC HD-AD01 is fully supported (video, audio, wired and wireless network all work with a plain FreeBSD 8.2-RELEASE).

    Anyway, since Paul Venezia also mentions virtualization, I'll go ahead and leave with a shameless plug about VirtualBSD which, as the name implies, offers a virtualized (but desktop oriented) FreeBSD that can be used with VMware or, after a few tweaks, VirtualBox.

    Oh, and version 9.0 will be out as soon as FreeBSD 9.0 is ready! ;-)

    RT.

  118. FreeBSD: Not yet rasy for prime time by Pigskin-Referee · · Score: 1

    FreeBSD is a joke. It has no support for wireless "N" devices and poor support for the remaining ones. Getting a simple sound card up and running in FreeBSD can be a serious PIA. In fact, the number of modern devices that don't work or don't work correctly in FreeBSD far exceeds those that do. FreeBSD is dedicated to finding the hardest way to do things and then doing it. It spends way to much time trying to reinvent the wheel rather than taking advantage of it. When you add in that the FreeBSD "INSTALLER" is straight out of the dinosaur age, I can not fathom why anyone other than a true masochist would bother with the OS. Even KDE and Gnome work poorly under FreeBSD. Not surprising when you consider that they have to extensively patch those desktops just to get them running all. Applications like LibreOffice work poorly under a FreeBSD environment.

    It has been my experience that the best way to turn a prospective user away from OpenSource software is to let them spend 30 days attempting to install and configure a FreeBSD system and desktop. They soon come running back to Microsoft at light speed. When you then consider that FreeBSD offers no support other than its poorly maintained and often highly abusive "mail forum", I can see why it is easier to find a virgin in a whore house than finding a satisfied FreeBSD user.

    --
    Pigskin-Referee
    Linux: Yesterday's technology, tomorrow ...
  119. Using FreeBSD developing java applications. by jm2dev · · Score: 1

    I use FreeBSD as my desktop workstation and an old thinkpad laptop, and the only thing I miss is flash support, although it helps me to stay focus on work :)
    Personally I don't see great differences compared with other linux (slackware, gentoo, debian, fedora), but every person is different. I use it for near two years developing java/scala/groovy applications. I agree you need to invest time reading the documentation, as unfortunately sometimes we want to force the operating system to do stuff the way we want instead of the way it was designed to be.
    It is also true that I was a competent linux user before I moved to FreeBSD.
    Despite the lack of support for some hardware, it is important to remember that it is supported by a community, not a company, and you can always help them to improve it: it is open source.

  120. i've been advocating this idea for awhile by Anonymous Coward · · Score: 0

    but GAWD! desktop bsd is EPIC FAIL!
    someone take a few hours and TWEAK THE HELL OUT OF IT!