Slashdot Mirror


Happy 20th Birthday, FreeBSD

mbadolato writes "FreeBSD celebrates its 20th birthday this week. On 19 June 1993, David Greenman, Jordan Hubbard and Rod Grimes announced the creation of their new fork of the BSD 4.3 operating system, and its new name: FreeBSD." And in the time since then, FreeBSD hasn't exactly stood still; it's spawned numerous other projects (like DragonFly BSD and PC-BSD), as well as served as the basis for much of Mac OS X; there's even a Raspberry Pi build.

220 comments

  1. Well... by grub · · Score: 5, Funny


    Given enough time, Netcraft will confirm...

    --
    Trolling is a art,
    1. Re:Well... by Freshly+Exhumed · · Score: 2, Informative

      If it is not in `cat /usr/share/calendar/calendar.history` on a FreeBSD box then I refuse to believe it happened.

      --
      I deny that I have not avoided attaining the opposite of that which I do not want.
    2. Re:Well... by UltraZelda64 · · Score: 2

      You have to check that file on a Xenix/SCO UNIX system. It will probably have Netcraft credits at the bottom with the copyright.

    3. Re:Well... by SnarfQuest · · Score: 0

      NetBSD was found dead in his bathroom, adter overclocking himself once to often. Never able to keep up with his more famous brothers,netBSD freeBSD and BSD386, he locked himself in his mothers basement and hadn't been seen in years.

      --
      Who would win this election: Andrew Weiner vs Andrew Weiner's weiner.
    4. Re:Well... by Anonymous Coward · · Score: 0

      Honest question, who uses NetBSD?

      + FreeBSD is used in certain hardware appliances, and some ISPs use it for shared hosting etc.

      + OpenBSD seems to be the security nerd's choice when they're setting up a really, really secure router. Or so they say.

      + NetBSD? Ummmm. I guess you can install it on some 1990s RISC hardware and brag to slashdot about it? (Except you have to go back to your x86 to run a browser.)

      Seriously, after 25 years in the business I've never seen or heard about anyone using NetBSD in production ever. Is this a real legit OS, or is Netcraft just being lazy?

    5. Re:Well... by Plunky · · Score: 5, Interesting

      Honest question, who uses NetBSD?

      Well I do, and moreover I personally have written ~30 thousand lines of code for NetBSD which has been used in other OS projects (the other BSDs, and OpenSolaris at least - see Bluetooth code) in varying amounts, and I am certainly not the only one to have had code re-used. The NetBSD libc is being used for Android now, I believe.

      Also, many companies do use it, though they don't always advertise that fact.

      Seriously, after 25 years in the business I've never seen or heard about anyone using NetBSD in production ever.

      The licence is liberal, and companies are not obligated to mention their usage.

    6. Re:Well... by kthreadd · · Score: 2

      Well it's a regular UNIX-like distribution so anyone can use it on their desktop or server if they want, and some do. It's also used in some embedded systems, Apple's networking equipment uses it for example.

    7. Re:Well... by ShanghaiBill · · Score: 1

      Seriously, after 25 years in the business I've never seen or heard about anyone using NetBSD in production ever.

      Either you are in the wrong business or you aren't looking very hard. NetBSD runs on almost anything, and is widely used in embedded systems. It is likely that some little black gizmo in your own home or office is quietly humming away with NetBSD inside.

    8. Re:Well... by Anonymous Coward · · Score: 1

      Apple's networking equipment uses it for example.

      Apple makes networking equipment? That runs NetBSD?

    9. Re:Well... by jones_supa · · Score: 1

      They make the AirPort gear, but that's pretty much it. I haven't seen mention of BSD, but the AirPort Extreme is known to run VxWorks.

    10. Re:Well... by jones_supa · · Score: 1

      Honest question, who uses NetBSD?

      + FreeBSD is used in certain hardware appliances, and some ISPs use it for shared hosting etc.

      + OpenBSD seems to be the security nerd's choice when they're setting up a really, really secure router. Or so they say.

      + NetBSD? Ummmm. I guess you can install it on some 1990s RISC hardware and brag to slashdot about it? (Except you have to go back to your x86 to run a browser.)

      Seriously, after 25 years in the business I've never seen or heard about anyone using NetBSD in production ever. Is this a real legit OS, or is Netcraft just being lazy?

      The most important area is probably providing the base for the Darwin kernel. It's good for other commercial products too as the BSD license doesn't require the source to be redistributed and thus you can better protect your intellectual property. But on the other hand, for many BSD setups, Linux would do the job just as fine. It's nice to have variety though.

    11. Re:Well... by jbolden · · Score: 1

      I'll give you an example Danger, who made the HipTop (T-Mobile's version was the sidekick) one of the earliest innovators for smart / feature phones was based on NetBSD server software. So there you go

    12. Re:Well... by Anonymous Coward · · Score: 0

      The base for Darwin is FreeBSD...

    13. Re:Well... by jones_supa · · Score: 1

      Well, I was talking about BSDs in general. But on the other hand, I today saw the official Products based on NetBSD list to mention Darwin. Maybe Darwin pulls from various BSDs?

    14. Re:Well... by unixisc · · Score: 2

      Add Minix to the list - they've adapted NetBSD userland, and are an excellent alternative to NetBSD for embedded apps. Only issue - they are currently x86 only, but once they add ARM support and proliferate it across the leading implementations, if not all, they'll be good to go.

    15. Re:Well... by unixisc · · Score: 1

      The Apple project that uses NetBSD is the Airport router. Aside from that, both OS-X and iOS are derived from FreeBSD as far as userland goes

    16. Re:Well... by jones_supa · · Score: 1

      At least the Wikipedia page for Airport Extreme states that it runs VxWorks.

    17. Re:Well... by ButchDeLoria · · Score: 1

      NetBSD is the premier operating system for smarttoasters.

  2. It just works by approachingZero+ · · Score: 5, Insightful

    I've been using it since about 1998 to serve web pages. Solid product, thanks for all the hard work people.

    --
    'I don't know what it's called. I just know the sound it makes, when it takes a man's life.' ~ Four Leaf Tayback
    1. Re:It just works by eksith · · Score: 2, Interesting

      This is exactly the reason I was using it for such a long time. I've used it along with Linux and OpenBSD, while these days, I use the latter for my home server. FreeBSD was my first honest attempt at building a home server.

      --
      If computers were people, I'd be a misanthrope.
    2. Re:It just works by mlts · · Score: 3, Insightful

      It works without issue. I've used a BSD on and off since the days of Jolitz's 386BSD which came with a compressed image with a number of utilities on a 1.44MB floppy disk. Before this, if a person wanted source code to look at, they would have to pay a good mint to BSDI or a company like that... and of course, if you wanted SVR4 source... good luck with that.

      Ahh... memories.

    3. Re:It just works by houstonbofh · · Score: 3, Interesting

      It is also the core of several appliances like m0n0wall, pfSense, FreeNAS, Nas4free, and Askozia. (even if Askizia ported to Linux later) Not bad for a little OS no one uses... ;)

    4. Re:It just works by Anonymous Coward · · Score: 0

      Back around 1990, we had a 486 system running "US Army BSD". (Whatever that really was.) Apparently our University paid AT&T enough money that this was free to use, at least on-campus.

      I never tried 386BSD, but the general perception was that it was junk and there was this other *nix called Linux you should use instead.

      Apparentlyt Net/Open spilt off as new projects (you know, Theo) and FreeBSD took over the old 386BSD project from Bill Jolitz.

    5. Re:It just works by Anonymous Coward · · Score: 1

      Back then, there were so many UNIX flavors, it was a totally different world. Even Dell had a SVR4 UNIX that installed from QIC tape.

    6. Re:It just works by Anonymous Coward · · Score: 0

      Don't forget Python. It also came from an obscure (now mostly dead) OS, Tanenbaum's Amoeba OS.

    7. Re:It just works by Anonymous Coward · · Score: 0

      Yep, remember that. "Dell Unix" was just a brandname for UnixWare from AT&T/Univell/Novell/SCO.

      Still, I've never found any google references to "US Army BSD". Someone DOD-related produced an x68 port, but apparently history has ignored them completely.

    8. Re:It just works by LordLimecat · · Score: 2

      It works without issue.

      Lets not wax TOO poetic about it. Wasnt there an issue in 8.1 which caused reboot loops if u had a USB keyboard plugged in?

    9. Re:It just works by steg0 · · Score: 4, Informative

      I recall frequent kernel panics while booting that were related to the Intel Ethernet chipset on a SuperMicro H8SGL-F board (not exactly the least common hardware) in a released version (I think it was 8.2 or 8.3), which was probably this. Rather annoying.

      There have been other problems, too (off the top of my head), like

      • the mediocre PAE support,
      • and the in my eyes rather ungracefully handled transition to Xorg 7.2 in the 6.x releases, which for me didn't work at all like the documentation said, although this was not a problem of the base system, but the ports collection.
      • Then there's stuff like some guys arbitrarily deciding to reimplement the system installer and on top of that, to remove the old one in the time window between 9.0 RC 3 and 9.0-RELEASE, see (along with some elitist Linux bashing going on:) here and here
      • or the transition to Clang at a time when it wasn't even ready for the non-x86 architectures!

      So sometimes I ask myself whether this OS is really ready for prime time

      But enough of the rant. I've been sticking to it since 2000 and for most of the time it just runs and does its job. It's got some nice coherent documentation too.

    10. Re:It just works by drinkypoo · · Score: 1

      Back around 1990, we had a 486 system running "US Army BSD". (Whatever that really was.) Apparently our University paid AT&T enough money that this was free to use, at least on-campus.

      There are (were) a million-billion variants of Unix. For a while, everyone and their mom was writing [a bad] one or doing [usually a mediocre and never-updated] BSD port. The original RISC machine (IBM RT PC, with the ROMP architecture) had a BSD4.3 port called AOS and later got a 4.4-lite port. A friend had a SAGE machine which ran a Unix called IDRIX. Etc etc.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    11. Re:It just works by ulzeraj · · Score: 1

      My first contact was while working for an online gaming community that served some korean MMOs who ran on top of FreeBSD. Their firewall was handled by OpenBSD. I might say that pf is incredible from the point of view of someone who has to deal with iptables and iproute2 from time to time.

      Today I use it as my home server providing ZFS storage management AFP through netatalk and CIFS, Kerberos, DNS and LDAP through SAMBA4. I'm very proud of my FreeBSD box.

    12. Re:It just works by LordLimecat · · Score: 1

      So sometimes I ask myself whether this OS is really ready for prime time,

      Of course it is and that wasnt my point.

      It just bugs me whenever people gush about how X is the perfect OS with no flaws. That doesnt exist, and never will.

    13. Re: It just works by Anonymous Coward · · Score: 0

      Someone from the third world might point at the US and say we we gush about how perfect our country is.

      The truth is we have lots to complain about, you know, first world problems like slow Internet, who owns twitter posts, and a gallon of gas costing less than a McValue meal. It's not in our best interests to complain about these to our less fortunate friends.

      Anyways, when I see someone write "Mac users think their systems are perfect", all I can say is you have it tough buddy, I wish the world was different, I won't complain about my Mac around you. You can have my old one when I'm done with it ok, peace?

    14. Re:It just works by Xtifr · · Score: 1

      Doesn't change the fact that you can type rm /etc/issue without any negative impact on system performance!

    15. Re:It just works by unixisc · · Score: 1

      On the x86 platform, honestly, there were too many. There was SCO ODT/OSE for starters, UnixWare, Interactive Unix, Consensys, Dynix, and a few others, aside from Solaris itself, which was ported to x86. I had no idea that Dell Unix was rebranded UnixWare - I thought that they spun their own Unix distro. But that was very short lived - within Dell, they referred to it as 'del Unix'.

      Speaking of which, did FBSD and NBSD come out at the same time, or was there a significant gap b/w their debuts? Also, when did PC-BSD first surface?

    16. Re:It just works by Anonymous Coward · · Score: 0

      There have been other problems, too (off the top of my head), like

      • Then there's stuff like some guys arbitrarily deciding to reimplement the system installer and on top of that, to remove the old one in the time window between 9.0 RC 3 and 9.0-RELEASE, see (along with some elitist Linux bashing going on:) here and here

      Arbitrary? Retiring sysinstall has been discussed for about 15 years. After complaints from everybody that tried to maintain it (including me - I did a couple of fixes, including the "restart" dialog box and ISTR some parameter checking) I was talking to the Lizard guys at Qt about replacing sysinstall back in 1999, and at that point the complains were by no means new. There has been an ongoing wish to retire it (with the codebase considered more or less unmaintainable by everybody) since, with no substantial architectural fixes/refactoring happening because the environment for developing and testing the installer sucks.

      I seem to also remember a couple of attempts at rewriting it in the meantime (including hiring somebody to write a replacement), with this one being the only one that actually managed to pull through. Though I've not been involved for a while, I can say that when I last participated in the discussion, the project was ready to lose features in the short term in order to get a reasonable installer in place. From the discussion that you're referring, that seems to have happened. It is by no means arbitrary, though losing features of course is annoying.

  3. HAS THIS BEEN CONFIRMED BY NETCRAFT ?? by Anonymous Coward · · Score: 2, Funny

    Well has it !!

    1. Re:HAS THIS BEEN CONFIRMED BY NETCRAFT ?? by Anonymous Coward · · Score: 0

      In Soviet Russia, *BSD confirms Netcraft.

    2. Re:HAS THIS BEEN CONFIRMED BY NETCRAFT ?? by VanessaE · · Score: 1

      Nonono, in Soviet Russia, *BSD confirms Nyetcraft. Jeez, get it right.

    3. Re:HAS THIS BEEN CONFIRMED BY NETCRAFT ?? by Anonymous Coward · · Score: 0

      *golf clap*

  4. BSD confirms by Anonymous Coward · · Score: 0

    Netcraft is dead!

  5. Re:DEd by Anonymous Coward · · Score: 1

    your sega cd is malfunctioning..

  6. Still dead after all these years by Anonymous Coward · · Score: 0

    Kind of like Generalisimo Francisco Franco.

  7. Don't forget OpenBSD by twocows · · Score: 1, Troll

    OpenBSD was a fork made by the founder of FreeBSD and it's arguably better than FreeBSD in several major ways.

    1. Re:Don't forget OpenBSD by twocows · · Score: 2

      Sorry, my mistake. He was not the founder of FreeBSD. I don't know where I got that idea.

    2. Re:Don't forget OpenBSD by Anonymous Coward · · Score: 2, Informative

      OpenBSD is a fork of NetBSD, and historically was never really involved in FreeBSD. Of course, all 3 share code under the friendly license.

    3. Re:Don't forget OpenBSD by hedwards · · Score: 1

      It's arguably better in one very specific way, they find a bug in the base system about once every decade.

      But, that's their focus. FreeBSD has a different focus and does quite well in its own area of focus.

    4. Re:Don't forget OpenBSD by Anonymous Coward · · Score: 0

      Probably dragonfly BSD. That founder was a fairly significant developer on FreeBSD, and he forked it. I believe it had to do with scheduler or SMP support or something.

    5. Re:Don't forget OpenBSD by Anonymous Coward · · Score: 0

      Sounds like YOU need to fork ClosedBSD.

      Do it, you arrogant SOB.

    6. Re: Don't forget OpenBSD by Aethedor · · Score: 1

      With OpenBSD and specially it's main developer, nothing is arguably...

      --
      It doesn't have to be like this. All we need to do is make sure we keep talking.
    7. Re:Don't forget OpenBSD by Anonymous Coward · · Score: 0

      Sorry, my mistake. He was not the founder of FreeBSD. I don't know where I got that idea.

      For some reason your original message got modded "Troll" even if it is not troll but simply contains wrong information. Good job again, mods... *facepalm*

    8. Re:Don't forget OpenBSD by SteveFoerster · · Score: 1

      Since mods use Troll as a substitute for "I think you're wrong" about opinions, perhaps they're just also using it that way now for facts.

      --
      Space game using normal deck of cards: http://BattleCards.org
  8. Congrats FreeBSD by laffer1 · · Score: 5, Insightful

    FreeBSD is a great example of open source working. Not only has it been successful, but it has spawned a lot of other open source projects such as GhostBSD, PC-BSD, DesktopBSD, DragonFly, pfsense, freenas, nanobsd, and my own MidnightBSD.

    There are a lot of people who have donated a lot of time to FreeBSD. This wouldn't have happened without all the committers and folks offering patches to the project. FreeBSD and all the other projects I mentioned wouldn't be here without the. Thanks!

    1. Re:Congrats FreeBSD by adolf · · Score: 2, Insightful

      And a lot of closed-source things: FreeBSD != GPL, so one is free to bottle up a bunch of their compiled stuff and sell it without interference.

      I, personally, am quite OK with this. (I once owned a TV that I strongly suspect ran FreeBSD; it worked well.)

    2. Re:Congrats FreeBSD by Daniel_Staal · · Score: 0

      IIRC, Windows for a long time used a FreeBSD-derived networking stack for TCP/IP...

      --
      'Sensible' is a curse word.
    3. Re:Congrats FreeBSD by cold+fjord · · Score: 1, Troll

      I will second that. And beyond just the fact that FreeBSD is a great OS and has spawned a number of derivative systems is the fact that it participates in the *BSD ecosystem in which useful ideas and developments are shared among the many BSD based distributions. (FreeBSD, NetBSD, OpenBSD.....n) That makes for a lot of innovation and experimentation that benefits much of Unixland, and beyond.

      --
      much of left-wing thought is a kind of playing with fire by people who don't even know that fire is hot - George Orwell
    4. Re:Congrats FreeBSD by ArchieBunker · · Score: 2

      I think ftp.exe from NT 3.51 or even 4.0 was BSD based and that was about all. For something as mature and tested as a simple FTP client why bother re-inventing the wheel? It was legally licensed as well.

      --
      Only the State obtains its revenue by coercion. - Murray Rothbard
    5. Re:Congrats FreeBSD by Anonymous Coward · · Score: 1

      In addition, it is the basis of many commercial products, including: TrueNAS, Netscaler, some F5 products, IronPort, Juniper Routers, NetFlix OpenConnect boxes, NetAPP OnTAP, Panasas and Isilon products, Playstation 3 and 4, Sophos's Email Appliance, and a bunch of TVs and other devices.

    6. Re:Congrats FreeBSD by smash · · Score: 4, Insightful

      It is also the basis of JunOS, Netapps Data OnTap, and various other commercial products. FreeBSD is really under-rated and works very very well.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    7. Re:Congrats FreeBSD by smash · · Score: 1, Insightful

      It was "BSD" derived, not FreeBSD. BSD is often the birth place of many reference implementations of new standards, due to the truly open nature of the license. Develop a "standard" under the GPL and it won't become standard at all, as no commercial OS will be able to use a starting reference implementation as a base.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    8. Re:Congrats FreeBSD by Anonymous Coward · · Score: 0, Funny

      Typical Linux user behavior.

    9. Re:Congrats FreeBSD by jbolden · · Score: 1

      Let's not forget OSX which got some of its code from FreeBSD as well.

    10. Re:Congrats FreeBSD by Anonymous Coward · · Score: 0

      If most or all GNU distributions use it then it pretty much is a standard.

    11. Re:Congrats FreeBSD by jbolden · · Score: 4, Insightful

      Develop a "standard" under the GPL and it won't become standard at all, as no commercial OS will be able to use a starting reference implementation as a base.

      Absolutely. And you can see that by noting that:

      gcc compatibility C++ source
      gnu make's -o extension
      Qt API's as a standard for mobility cross platform
      Linux kernel API as a standard for emulation (mainframe, supercomputing, mini...)
      Wordpress as a blogging standard
      Sword standard for bibles
      Guile as a standard Scheme
      Blender API for 3D modeling
      etc...

      aren't standards. Oh wait.

    12. Re:Congrats FreeBSD by nmb3000 · · Score: 2

      Absolutely. And you can see that by noting that:

      List of completely unrelated things

      aren't standards. Oh wait.

      If you'd bother to think a second before posting, what the OP meant was that you won't see the code of a GPL project being used as a general implementation reference standard. It wasn't a slam against the GPL, simply pointing out that the BSD license allows anyone to read and use the ideas in the code without much in the way of limitation or requirements. For example, a Microsoft engineer could read over the code for the BSD TCP/IP stack and then implement one for Windows using those ideas as a reference. That would never happen with GPL'd code because the license is more restrictive (again, not necessarily a bad thing).

      (PS: Wordpress is a "blogging standard"? WTF does that even mean? That blogging software is by definition a mess of security holes?)

      --
      "What do you despise? By this are you truly known." --Princess Irulan, Manual of Muad'Dib
      /)
    13. Re:Congrats FreeBSD by Anonymous Coward · · Score: 0

      What does Microsoft has to do with anything? That's just one operating system. If a 1000 Linux distributions use the same GPL source code then that is by sheer numbers more of a standard that anything Microsoft has ever done. GPL by its nature enables software to become a standard, because it is more restrictive. BSD just adds to fragmentation.

    14. Re:Congrats FreeBSD by Anonymous Coward · · Score: 0

      Let's not forget OSX which got some of its code from FreeBSD as well.

      And let's not read the summary where it says exactly that...

    15. Re:Congrats FreeBSD by Anonymous Coward · · Score: 0

      gcc compatibility C++ source

      gcc is not a standard and most c++ compilers are not GPL.

      gnu make's -o extension

      Never seen it, never used it, thought most gnu manpages tend to include warnings for incompatible flags -> this is most likely an exception to the rule.

      Qt API's as a standard for mobility cross platform

      Qt is dual licensed, everyone who wants can get a GPL free version of it.

      Linux kernel API as a standard for emulation (mainframe, supercomputing, mini...)

      You could not write a proprietary linux application if the API was GPL and the kernel internal stuff is unstable as hell.

      etc...

    16. Re:Congrats FreeBSD by Anonymous Coward · · Score: 0

      Pretty much all GNU/Linux distributions uses gcc. Last time I checked neither Windows or Mac OS X came with a compiler.

    17. Re:Congrats FreeBSD by Arker · · Score: 4, Informative

      There is a little bit of truth hiding behind your words but your statement is still very misleading.

      GPL is much more 'truly open' precisely because no 'proprietary' implementation of a standard with a GPL reference implementation will be able to simply lift the code (legally.) *Proprietary* being the keyword here - you said commercial, and that is simply false. You can make a commercial implementation of a standard with a GPL reference implementation, and furthermore you can simply copy that reference implementation to do it!

      Proprietary != commercial. Slackware, RedHat, Ubuntu, etc. are all commercial. GPL is perfectly fine with commercial. It's only proprietary that it objects to (and for good reason!)

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    18. Re:Congrats FreeBSD by Arker · · Score: 1

      "For example, a Microsoft engineer could read over the code for the BSD TCP/IP stack and then implement one for Windows using those ideas as a reference. That would never happen with GPL'd code because the license is more restrictive (again, not necessarily a bad thing)."

      You are wrong. Anyone that wants to is free to read any GPL code they want and then implement those ideas themselves, using that code as reference. The GPL very explicitly limits itself to copyright law here (which does not prohibit anyone from reading, adapting and applying ideas using a document as a reference.) That is not restricted in any way.

      What is restricted, for *proprietary* implementations (not as others have claimed 'commercial' implemenations) is simply copying the code outright. That is prohibited by copyright law when not allowed by license, and the GPL will only allow it if the resulting code is free. Unfree code must be written rather than simply copied. Either free or unfree code may be and is used commercially.

      P.S. Agree with you on Wordpress. The interesting side of the BSDs for me is entirely technical. There were several forks in the road where the BSDs took the path I would prefer, and Linux did not. However licensing is not one of them. If you can be against the GPL without being simply wrong about what it does and requires, then fine, but you would be a first.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    19. Re:Congrats FreeBSD by Anonymous Coward · · Score: 0

      "some"... try almost ALL other than applications. Really it is ALL of which they then changed some of the code to truly fuck up everything. Now each successive version is a kludge of mangled code to fix shit they fucked up in the original OSX. Have you looked at their directory tree lately? It's like the Windows registry except in file form. Shit here, shit there, better make a few more copies of it all over the place just to be sure. OSX is FreeBSD's druggie son who can't control can't control his bowel movements anymore and just shits all over himself.

    20. Re:Congrats FreeBSD by Anonymous Coward · · Score: 0

      gcc is not a standard

      You might be surprised at how many "non-standard" GCC extensions for C & C++ make their way into the official standards.

    21. Re:Congrats FreeBSD by Anonymous Coward · · Score: 0

      Guile as a standard Scheme

      So a Scheme implementation that is widely ignored is somehow a standard? If there somehow was such a "standard" it would be Chicken or Racket. None of the people writing the actual Scheme standards even use Guile and there are probably 4 or 5 Scheme implementations that are significantly more popular.

    22. Re:Congrats FreeBSD by nogginthenog · · Score: 1

      I think it still does in Win7:

      C:\Windows\system32>strings ftp.exe | grep -i regent
      @(#) Copyright (c) 1983 The Regents of the University of California.

    23. Re:Congrats FreeBSD by jbolden · · Score: 1

      If you'd bother to think a second before posting, what the OP meant was that you won't see the code of a GPL project being used as a general implementation reference standard.

      That's a much more specific statement. I don't think it is my job to read his mind if he meant something that narrow he should have said it. Certainly that narrow statements is true.

      (PS: Wordpress is a "blogging standard"? WTF does that even mean? That blogging software is by definition a mess of security holes?)

      Wordpress is used pretty freely on 3rd party hosted websites to roll out blogs. It is how people add blogging functionality to the overwhelming majority of sites that have blogging. Because it is so heavily used as an API is allows thousands of people to create templates, functionality, plugins.... for WordPress blogs. It has become the Internet's standard blog. As far as security holes, I don't know if it is good or bad but that's irrelevant to the question of standard.

    24. Re:Congrats FreeBSD by jbolden · · Score: 1

      You are wrong. Anyone that wants to is free to read any GPL code they want and then implement those ideas themselves, using that code as reference. The GPL very explicitly limits itself to copyright law here (which does not prohibit anyone from reading, adapting and applying ideas using a document as a reference.) That is not restricted in any way.

      That's not true. Copyright extends to the expression of an idea. Studying code to apply the ideas, that is the expression is covered by copyright. That's why when companies want to reimplement around an idea they have to use the blackbox approaches. Anyone who has seen the original code is basically tainted for life.

    25. Re: Congrats FreeBSD by Anonymous Coward · · Score: 0

      Apple lets you download Xcode, clang/llvm for free on OS X.

    26. Re:Congrats FreeBSD by drinkypoo · · Score: 1

      I think ftp.exe from NT 3.51 or even 4.0 was BSD based and that was about all.

      There is substantial evidence that the entire TCP stack in win2k was lifted from FreeBSD based on its behavior. One of the RCs would even fingerprint as FreeBSD.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    27. Re:Congrats FreeBSD by Anonymous Coward · · Score: 0

      BSD runs in areas that GPL cannot. BSD runs in routers and infrastructure, you know, important things; GPL runs in TVs and cell phones, you know, stuff that is "fun".

    28. Re:Congrats FreeBSD by Antique+Geekmeister · · Score: 0

      Please go and review the actual licenses. "Ideas" is a very vague standard for what can, or cannot, be copied, and the history of copyright has many competing decisions on what copying is of "ideas", which are not copyrightable, and what is of "content", which is copyrightable. The idea that the GPL somehow locks down ideas where Apache or the variety of BSD licenses do not is not well founded, because copyright does not cover "ideas". To lock down "ideas", you need something much more comprehensive like an End User License Agreement or an actual contract.

      A key difference between GPL and BSD licenses are the _patent_ rules. GPLv3 covers _patents_ very carefully, and for sound historical reasons. The "TIVO" set topo bax used GPL code, but locked it down with patents so customers could duplicate the very "ideas" you mention, even if they were allowed to read the modified code under the GPL. Patents were used to lock down the box and make it difficult, even dangerous, to duplicate or modify.

      The various BSD rules _do not cover patents_. Thus, you are far more in danger of being in intellectual property violation, and at the risk of patent troll lawsuits, by using BSD licenses. The Apache license is even worse, by the way. If you sue anyone over their patent abuse, _even if you're suing them for fraudulently claimin gyour patent is theirs_, you lose your license to use all patents in that particular code. It's a dangerous license.

    29. Re:Congrats FreeBSD by Arker · · Score: 1

      That's not copyright law, that's a confused and perverted reading of "IP" instead.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    30. Re:Congrats FreeBSD by jbengt · · Score: 1

      I think you misunderstand 'expression of an idea'.
      'Studying code to apply the ideas' is not 'the expression covered by copyright'.
      Ideas are not covered by copyright. Functionality is not covered by copyright. Only the creative, original expression is covered. Using the black box approach is a way to avoid the argument about what is functional, what is expressive, what is copied, what is original, etc. Trial lawyers love to argue, but clients want corporate lawyers to help them avoid the trial.

    31. Re: Congrats FreeBSD by Anonymous Coward · · Score: 0

      My Sony BluRay player runs FreeBSD

    32. Re:Congrats FreeBSD by dbIII · · Score: 1

      Just about all? How about just about the entire TCP/IP stack? I'm still quite amused that MS later put a whole lot of copyright text in etc/hosts as if it hadn't come from elsewhere.

    33. Re:Congrats FreeBSD by dbIII · · Score: 1

      Everyone's getting this mixed up. The BSD stuff went in as a cut and paste with later modifications and there was nothing wrong with that so long as the attributions were kept. So "copied outright" was OK for that licence.

    34. Re:Congrats FreeBSD by smash · · Score: 1

      No.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    35. Re:Congrats FreeBSD by smash · · Score: 1

      Point: missed. With BSD code, a closed source vendor can lift the code verbatim and use it as a starting point in their code. This is a FEATURE (not a bug) as it enables us to have well tested code in all our apps, be they open source or closed.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    36. Re:Congrats FreeBSD by smash · · Score: 1

      More to the point, the MS engineer could cut and paste the code into his project and modify to suit. In fact, if i'm not mistaken, the original version of the Linux TCP/IP stack was heavily based on the BSD stack if I am not mistaken, but am unable to find confirmation with a quick google search and my memory from back in the early 90s of such things is hazy.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    37. Re:Congrats FreeBSD by smash · · Score: 2

      And this is the point. BSD allows (by design) cut/paste code reuse. Rather than promoting wheel invention with new and undiscovered bugs.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    38. Re:Congrats FreeBSD by jbolden · · Score: 1

      Most infrastructure runs Cisco IOS neither BSD nor Linux.

    39. Re:Congrats FreeBSD by jbolden · · Score: 1

      Expression and ideas is right in Chapter 1 and goes through the entire copyright act: http://www.copyright.gov/title17/92chap1.pdf

      Yes it is copyright law. You make not like copyright law but that doesn't change how broad the law is.

    40. Re:Congrats FreeBSD by jbolden · · Score: 1

      I understand that in theory one can study code and avoid expression. In practice though it is complex and people far too easily end up copying expression without realizing it. Expression is a bit broader than line for line copying. See The Wind Done Gone case.

    41. Re:Congrats FreeBSD by jbolden · · Score: 1

      Mac OSX comes with a compiler. For years it was gcc. Now it is gcc and LLVM, they are transitioning.

    42. Re:Congrats FreeBSD by jbolden · · Score: 1

      Like I said above. That's fine. That's a standard code base. I would agree BSD allows for a standard codebase. But that's a different claim then saying the GPL apps don't allow for standards. That's a different claim.

      ____

      Now addressing that much weaker claim, I also don't happen to agree with you that the BSD license does this. Because there is no sharing the proprietary vendors end up creating non standard extensions of the BSD codebase rendering the free one more or less worthless. The history of X being the most classic example. The GPL conversely requires the closed source vendor to keep the open stuff open. They can extend but they can only extend things far removed from the core and they need to share their core back with the community. GCC being a terrific example of this.

      The net result is that GPL code ends up being far more standard.

    43. Re:Congrats FreeBSD by Anonymous Coward · · Score: 0

      It is used in every single one of the 2WIRE triple play DSL modems deployed by ATT that everyone uses. Read the license, it's there.
      Too bad ATT chooses not to support the FreeBSD project with donations. Then again, now you know how to support ATT in return.

    44. Re:Congrats FreeBSD by Artifakt · · Score: 1

      We're currently in an era where lawyers have fought to extend copyright law into some sort of generic Intellectual Property law, and then make that ambiguous enough that their company could win two cases back to back on exactly opposite claims. The GPL can easily be abused in this way, as can all the alternatives. Blaming the GPL, or any other license, is a mistake, when the real problem is widespread legal abuse by powerful corporations.

      --
      Who is John Cabal?
    45. Re:Congrats FreeBSD by Antique+Geekmeister · · Score: 0

      > The GPL can easily be abused in this way, as can all the alternatives.

      Please do re-read the licenses yourself. The GPL has been much more careful about the consequences of its claims, and more recently about patents, than the other licenses. GPL learned the lessons about casually written, or "vendor friendly" software licenses that allow encumbering of commercial or patent licenses _on top of_ the the originally free or open source software. Such encumbering occurs today: take a deep look at the various firewall appliances and storage appliances that are BSD based, and just try to get source code for their components. GPL has been very helpful to get access to that software, and has been much more robust for work I do.

    46. Re:Congrats FreeBSD by unixisc · · Score: 1

      In Windows 7, it's IPv6 that's used for the networking stack, and Teredo that's the native mechanism to connect IPv6 externally. So from Vista onwards, Microsoft couldn't have been using the BSD TCP/IP stack.

    47. Re:Congrats FreeBSD by unixisc · · Score: 1

      A 1000 Linux distros put together have less than 5% of the user base of Windows, so calling that as an example of more standardization misses the point. Especially when most of the distros are just cosmetic combinations of certain DEs, software, kernels and the like.

    48. Re:Congrats FreeBSD by dbIII · · Score: 1

      There's two - it's a fucking enormous mess and a credit to those that finished it off that it works at all. The underlying problems surface every now and again with firewalls not acting as expected, or network problems vanishing entirely for no explicable reason when IPv6 is turned off and it falls back onto the older TCP/IP stack. I believe there's even been an article about it here some time ago.

    49. Re:Congrats FreeBSD by readingaccount · · Score: 1

      OK, this trolling wasn't really as fun as I was expecting. Not sure why people keep trolling if it's no fun.

    50. Re:Congrats FreeBSD by Anonymous Coward · · Score: 0

      And we can find FreeBSD on many commercial software/appliance like Citrix Netscaler, or the operating system "layer" under JunOS on Juniper SRX/EX ecc.
      Great software, imho

      regards

    51. Re:Congrats FreeBSD by tlhIngan · · Score: 1

      A key difference between GPL and BSD licenses are the _patent_ rules. GPLv3 covers _patents_ very carefully, and for sound historical reasons. The "TIVO" set topo bax used GPL code, but locked it down with patents so customers could duplicate the very "ideas" you mention, even if they were allowed to read the modified code under the GPL. Patents were used to lock down the box and make it difficult, even dangerous, to duplicate or modify.

      Bzzt. Incorrect. The TiVoization rules are NOT because of patents. In fact, GPLv2 had patent rules as well - basically by agreeing to release code under GPLv2, any patents covering said code are licensed for that code only.

      TiVoization referred to "look but don't touch" - TiVo released the OS code per the GPLv2. However, because of various hacks bricking systems and in generally messing things up horribly, their Series 2 boxes included signature checks. The end result was yes, you had all the modified source code, but you could not run it because you couldn't sign the kernel nor filesystem, so any changes you made got blown away by the official build.

      It wasn't patents. It was look but don't touch. It's why GPLv3 is now considered toxic to most companies wanting to use open-source code - they don't want to accidentally reveal their signing keys and what not (which is now a requirement - that the entire build system used must be available).

      OTOH, GPLv3 has at least brought open-source licensing to the same scrutiny that commercial code licenses have gotten at the same companies, so inadvertent violations should be reduced and more open-source usage policies get developed.

    52. Re:Congrats FreeBSD by Plumpaquatsch · · Score: 1

      Most infrastructure runs Cisco IOS neither BSD nor Linux.

      Sure. But looking at the history of IOS it's not unreasonable to assume that it originally used BSD licensed code, but certainly not GPL licensed code.

      Cisco's Router and IOS were based on Stanford's Blue Box and Networking OS, and the Blue Box was basically nothing but the original SUN 1 (Standford University Network) - which ran BSD.

      I'll admit that this is just speculation, but it's not baseless.

      --
      Of course news about a fake are Fake News.
    53. Re:Congrats FreeBSD by jbolden · · Score: 1

      I think they completely (or almost completely) replaced that old code base twice. Once when they stripped it down to make it faster and then 2004 when they switched to the IOS-XR. The layers are just stuff that would never exist in a generic Unix. So for example QoS (Quality of Service) is a kernel level module.

  9. FreeBSD managed to lose control of its own name by jphamlore · · Score: 1

    There is an organization that is supposed to be enforcing the FreeBSD trademark: http://www.freebsdfoundation.org/documents/guidelines Supposedly. Except there is a project, http://www.debian.org/ports/kfreebsd-gnu/ that is only using parts of FreeBSD, that is nonetheless calling itself FreeBSD. Actually, for something like grub 2, FreeBSD no longer exists, it's kFreeBSD. Either you own the trademark or you don't. Which is it? And since when is it such a big deal to require someone to rename their project?

    1. Re:FreeBSD managed to lose control of its own name by Trepidity · · Score: 2

      Considering pretty much nobody uses Debian GNU/kFreeBSD, is it really a problem for FreeBSD's name recognition or brand confusion?

    2. Re:FreeBSD managed to lose control of its own name by smash · · Score: 1

      Erm. GRUB is garbage. Nobody uses it on FreeBSD.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    3. Re:FreeBSD managed to lose control of its own name by grub · · Score: 2

      I take offens... oh, you mean the bootloader!

      --
      Trolling is a art,
    4. Re:FreeBSD managed to lose control of its own name by TheRaven64 · · Score: 1

      Debian/kFreeBSD users the kernel from FreeBSD. It is perfectly acceptable for it to use a word similar to the trademark.

      --
      I am TheRaven on Soylent News
    5. Re:FreeBSD managed to lose control of its own name by Anonymous Coward · · Score: 0

      " GRUB is garbage. Nobody uses it on FreeBSD."

            Actually Kris Moore plans on using grub as the bootloader for pcbsd.

            http://lists.pcbsd.org/pipermail/dev/2013-June/000777.html

      celle

    6. Re:FreeBSD managed to lose control of its own name by cpghost · · Score: 1

      With UEFI-PCs being locked down to Microsoft's bootloader soon, FreeBSD will very likely move to one of the Microsoft-signed Linux bootloaders... and that will basically be shim/grub2 or something like that.

      --
      cpghost at Cordula's Web.
    7. Re:FreeBSD managed to lose control of its own name by D1G1T · · Score: 1

      not true. I've used grub to boot freebsd for some projects. it has quite good serial-console multi-boot flexibility.

  10. Had AT&T not sued BSDi by stox · · Score: 3, Interesting

    We might be talking about FreeBSD as we do Linux these days.

    --
    "To those who are overly cautious, everything is impossible. "
    1. Re:Had AT&T not sued BSDi by jbolden · · Score: 1

      The BSD people keep telling themselves that but no. The BSDs never made an attempt to appeal to Windows Power users and Unix users who didn't do administration. They focused on providing a classic Unix admin experience. They were harder to install, harder to configure, less tolerant of various hardware.... BSD failed because it never made an attempt to appeal to the group of end users that became the Linux desktop users of the 1990s and the Linux admins of the 2000s.

      They lost a few months due to the lawsuit no question but that's not why they failed. There have been multiple markets that have opened since then where Linux has failed to be able to enter and the BSD haven't entered successfully. Were it nothing more than those few crucial months the BSDs could have exploited those holes.

    2. Re:Had AT&T not sued BSDi by drinkypoo · · Score: 1

      We might be talking about FreeBSD as we do Linux these days.

      Well no. The difference is that I could get a stack of floppies and simple install instructions and actually install Slackware and get it running within one day. Whereas with BSD, asking for install help was pretty much guaranteed to leave you with the mark of the idiot for the remainder of time.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    3. Re:Had AT&T not sued BSDi by Anonymous Coward · · Score: 0

      appeal to the group of end users that became the Linux desktop users

      Kind of like appealing to the average USA voter. It only lowers the standard. Do we have a lot of Linux admins now? Yes, but how many write, use, and sonfiure insecure and buggy systems.

      PHP is a poster-child of what is wrong with the "Linux Community". Horrible horrible language that people brag about.

    4. Re:Had AT&T not sued BSDi by jbolden · · Score: 1

      Kind of like appealing to the average USA voter. It only lowers the standard. Do we have a lot of Linux admins now? Yes, but how many write, use, and sonfiure insecure and buggy systems.

      That's true. There are huge advantages in avoiding popularity. But that desire to not lower standards by educating or working with people with lower skills is what killed BSD not those missed months.

      PHP is a poster-child of what is wrong with the "Linux Community". Horrible horrible language that people brag about.

      I don't agree it is a horrible language. I think at the time of PHP there was a strong desire for a way for people who knew HTML to program variable web content with easy database access. PHP accomplished its objective.

      Part of being a good language for the masses is being something the masses want to use.

  11. Cheers! by bidule · · Score: 1

    Here's to the other kind of free, and another 20 years for both!

    --
    ID: the nose did not occur naturally, how would we wear glasses otherwise? (apologies to Voltaire)
  12. FreeBSD's developers CHOSE to not be popular by jphamlore · · Score: 5, Interesting

    Let's explode that myth. Here's what actually happened. Linux distributions such as Slackware back then supported booting from a floppy into the OS so that one could run the rest of the userland from a hard drive. That meant one could preserve Microsoft Windows booting yet run Linux at the same time with no risk. I cannot stress how important a feature that was back then to someone like me, back when PCs were very expensive and had to be shared among family members. The FreeBSD developers took a different tack. Their OS was for grown-ups, for servers. They openly mocked on their mailing lists the feature of being able to boot into the OS from a floppy drive. (Note this is different from being able to INSTALL from floppy, everyone back then could do that.) The FreeBSD developers CHOSE to not be popular.

    1. Re:FreeBSD's developers CHOSE to not be popular by jphamlore · · Score: 2

      And Linux back then supported booting the OS from an extended partition, a feature FreeBSD didn't have until many years later.

    2. Re:FreeBSD's developers CHOSE to not be popular by camperdave · · Score: 5, Funny

      They openly mocked on their mailing lists the feature of being able to boot into the OS from a floppy drive... The FreeBSD developers CHOSE to not be popular.

      ... and here it is umpteen years later and NOBODY boots from a floppy. Sounds to me like they were just ahead of their time.

      --
      When our name is on the back of your car, we're behind you all the way!
    3. Re:FreeBSD's developers CHOSE to not be popular by stox · · Score: 4, Insightful

      I disagree, as far as real adoption goes. Yes, booting Linux from a floppy using a MSDOS filesystem did enable a lot of people to get exposed, but the race was lost before those people made a difference. Had BSD development not stalled for two years, many of the early commercial and big site adoptions would have gone to BSD instead. Many started with BSD and then jumped to Linux because that is where the momentum was. Red Hat's IPO sealed the deal.

      BTW, I introduced Pat Volkerding to the Church of the SubGenius, and pioneered a lot of the early work with Linux at Fermilab. I know a little about these things.

      --
      "To those who are overly cautious, everything is impossible. "
    4. Re:FreeBSD's developers CHOSE to not be popular by Anonymous Coward · · Score: 4, Interesting

      It wasn't just something specific like floppy boot, it was the entire attitude that Linux was for "Peecees" or "Windoze" users, while *BSD was for the Sun Workstation Master Race (who couldn't actually personally afford a sun workstation). Just as an example, *BSD thought "real workstations use SCSI (period)". While Linux had all sorts of workarounds for your buggy IDE chipset and support for your proprietary Soundblaster CD-ROM drive.

      And while the Net/Open/Free factions were flaming each other on the maillists, there was this persistant attitude that Linux was vastly inferior thing, even after the "the battle was over", and Linux had clearly won. When the history is really written, the story of *BSD has little do with AT&T and is more about how arrogance and personal politics alienated a entire genration of users.

    5. Re:FreeBSD's developers CHOSE to not be popular by jbolden · · Score: 1

      Great example of what was different between the BSD and Linux culture of the mid 1990s.

    6. Re:FreeBSD's developers CHOSE to not be popular by jbolden · · Score: 3, Interesting

      Red Hat's IPO was in 1999. The Linux :: BSD ratio was already massive by then.

      I don't agree with you about 1994. I don't think it was losing time. I think the BSD community was hostile to people like me (Windows Power Users and Unix users -- non admins) who became the people who pushed Linux into corporate America during the 1990s and early 2000s.

    7. Re:FreeBSD's developers CHOSE to not be popular by jbolden · · Score: 2

      Honestly it was worse than that. Linux also had the "I wish I could buy a Sun workstation but can't afford one" crowd. BSDs were focused on Unix admin types they didn't want Unix user types with light admin knowledge.

    8. Re:FreeBSD's developers CHOSE to not be popular by Anonymous Coward · · Score: 0

      Yes I know, because now we all run BSD on our Deskto.. oh wait.

      No what I mean to say was that BSD is now the most used OS for Serv.. oh wait..

      Sorry.. what was your point again?

    9. Re:FreeBSD's developers CHOSE to not be popular by Anonymous Coward · · Score: 0

      And Linux back then supported booting the OS from an extended partition, a feature FreeBSD didn't have until many years later.

      Yes. Because you didn't need the extended partitions as you could do slices in a primary one. The DOS partitioning scheme was and is awful and you really didn't need to do that.

    10. Re:FreeBSD's developers CHOSE to not be popular by Anonymous Coward · · Score: 0

      Might die ahead of the rest too.

    11. Re:FreeBSD's developers CHOSE to not be popular by Anonymous Coward · · Score: 0

      Linux may run the Internet, but the Internet runs on top of BSD.

    12. Re:FreeBSD's developers CHOSE to not be popular by Antique+Geekmeister · · Score: 1

      This is debatable. Booting from a CD is really booting from a floppy image written on the CD, so the feature is still in use worldwide for installers and for livd CD or live DVD environments.

      Few modern kernels and boot environments fit on a single 1.44 Megabyte floppy image anymore.

    13. Re:FreeBSD's developers CHOSE to not be popular by Anonymous Coward · · Score: 0

      Sun didn't help: when they went from BSD style UNIX to AT&T style UNIX with their release of that amazingly buggy and contorted and re-written mess called "Solaris", they threw away years of hard-won BSD based loyalty. And Linux scooped them up: The BSD releases failed to scoop us up, including their FreeBSD fans, because their installers were *horrible* and there was no help for new users who wanted to try this stuff out on weird hardware.

      That's also when HURD's failure to have a working kernel and installer cost them the "cheap, free as in money" market to Linux.

    14. Re:FreeBSD's developers CHOSE to not be popular by Anonymous Coward · · Score: 0

      RedHat's IPO??? from 1988 to 1999 is a lot of years.

    15. Re:FreeBSD's developers CHOSE to not be popular by unixisc · · Score: 1

      Actually, the efforts in PC-BSD seem to suggest otherwise. From everything I've read, they've done their level best to ensure simple things - such as gui utilities working in the same way that CLI utilities work. That would have taken a lot of work. Once they get that entire OS pnp installable, that will be good enough to challenge the likes of Ubuntu, Mint, Fedora and other Linux distros. PC-BSD also offers a much wider choice of DEs

    16. Re:FreeBSD's developers CHOSE to not be popular by Anonymous Coward · · Score: 0

      "DOS partitioning" was actually an IBM standard that nearly every PC OS supported.

    17. Re:FreeBSD's developers CHOSE to not be popular by Anonymous Coward · · Score: 0

      The early "big sites" like Yahoo and Hotmail did run on FreeBSD... unclear why that didn't continue.

      The AT&T lawsuit was settled by 1993, a year or two before the internet boom started. You might have 'been there', but the timing doesn't match up.

    18. Re:FreeBSD's developers CHOSE to not be popular by Xtifr · · Score: 1

      If you're talking about an era where Slackware (or even SLS) existed, then you're looking too late in the history to see what might have happened to BSD if Linux hadn't existed. If it hadn't been for the existence of Linux for the hobbyist crowd, then there's a good chance those tools that were developed to allow early Linux systems to boot from floppy would have been developed for BSD instead.

      Now if you want to talk about a deal-breaker--the BSD refusal to operate on a system without an FPU is what initially convinced me to go with Linux, once I got tired of the 16-bit limitations of Minix. (Although I was quite pleased with my success at getting Minix to run in an OS/2 "virtual DOS box".)

  13. May it rest in peace (as a desktop) by Billly+Gates · · Score: 1

    Found memories back in the day. My favorite release was 4.12 right when 4.x was getting a little long in the tooth. Nothing seemed to work right on non server hardware after that.

  14. users by Anonymous Coward · · Score: 0

    I bet all 7 users are super excited.

  15. pkgng by jphamlore · · Score: 1

    There's new infrastructure that has been developed from FreeBSD, pkgng. It holds the promise of much better binary package management. There's just one problem: https://wiki.freebsd.org/pkgng "As a consequence of the security incident on 11th November 2012, for the time being pre-compiled packages for pkgng are not available from any official FreeBSD repository." The security incident happened in NOVEMBER 2012. Yet as of at least June 5, 2013, "Target dates for when service may be resumed have not been released."

    1. Re:pkgng by Arker · · Score: 1

      A predictable problem I would have expected the *BSDs to avoid. Pre-compiled packages have never been ideal. We used to rely on them simply because our systems were so slow that compiling took so long. With a modern computer you should be able to compile an entire system in about 20 minutes so why on earth would you want to invite problems by using someone elses binaries?

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    2. Re:pkgng by Anonymous Coward · · Score: 0

      Pre-compiled packages have never been ideal

      On the flip side, running a server with a complete compiler toolchain installed makes the security types twitch.

    3. Re:pkgng by Anonymous Coward · · Score: 0

      Those people don't know much about security if they think having a compiler installed makes one iota of difference.

    4. Re:pkgng by TheRaven64 · · Score: 1

      Recovering from the security incident is not just a matter of reformatting the machines. You don't just turn things back on and hope. All of the code that is being used to build the packages is being audited (this is now basically done). The FreeBSD cluster is now running auditdistd, so that auditing logs of all of the build machines are preserved even in the case of a compromise. The goal is to ensure that a compromise like this can't happen again, not to rush out packages and then have to do the whole thing again next time there's an incident.

      For what it's worth, with Poudriere, you can build the entire ports tree into pkgng packages in about 48 hours on a reasonably powerful machine. If you don't want all 20+K packages, then you can do it a lot faster. If you trust iX Systems, you can just point pkgng at the PC-BSD repository...

      --
      I am TheRaven on Soylent News
    5. Re:pkgng by Antique+Geekmeister · · Score: 1

      Because your build environment may be subtly different than mine., or the build environment on which the software was first generated and tested. And this can seriously break the software.

      The presence, or absence, of optional compilation components makes a large change in software features. A very small change in one system library, or compiler environment, added to allow one component to build, may break other live components in ways the original author of either component never envisioned. And if I patch that source for my local build environment, how can I publish those patches for others with similar environments? The complexity of building this, and maintaining this, is one of the serious failures of "just build everything from scratch" approaches. It's exacerbated by carelessly written installers that simply overwrite, or dynamically modify, critical system files such as cron or inittab.

      This is also an old discussion: developers who can build tools locally, and quickly, often want to use them instead of packaged or managed tools that are more likely to be correctly and securely installed, and less likely to save people's passwords in plain text.

  16. Happy birthday, 20, FreeBSD. by Anonymous Coward · · Score: 0

    We are Tomahawk Desktop, a FreeBSD-based operating system. A very big sorry for all as that we had to switch our focus to another project (http://www.tomahawkworld.com/), which is now almost completed and about to be released in mid July, 2013.

    After the TomahawkWorld is released we intend to start work on Tomahawk Desktop OS based on FreeBSD v.10, which we think more suitable for desktop/laptop environments.

  17. What's the difference with Linux ? by dargaud · · Score: 1, Interesting

    I'm not trolling here, but as a Linux user I never took interest in BSD, I hardly know what it is. The impression I have is that it is solid but somewhat backwards compared to Linux. It's just strange to me that there are two similar OSes coming out the same year and they are still both here. So what are the differences besides the licensing scheme ?

    --
    Non-Linux Penguins ?
    1. Re:What's the difference with Linux ? by kthreadd · · Score: 1

      As a regular user you don't see any difference. The same software works on both.

      The main differences are in the kernel, and in the way the systems are developed. In Linux land the kernel and most other operating system components are developed in separate projects, and the distributions are responsible for packaging them so that they work together as one cohesive operating system. In FreeBSD everything is developed by essentially the same team as one big project. That's why we often don't speak about BSD distributions, because unlike Linux distributions the BSD kernel is developed in parallell by each distribution. Some prefer one way or the other, but overall both systems are fine.

    2. Re:What's the difference with Linux ? by real-modo · · Score: 3, Informative

      Hmmm.. last used for any length of time: FreeBSD 2.2.2 with FVWM95 (serial mouse!), back in '00 or thereabouts. (At the time, FreeBSD was reliable; Linux was not. Corel Linux--remember that, anyone? Urg. Red Hat? flaky, at the time. Mandrake Linux: slightly less flaky.)

      But the culture hasn't changed much, from a recent scout-round. I'd say your impression is correct. Here are some random thoughts:-

        *BSDers will say *BSD is more like "real Un*x", but as far as I can tell the OS has been riddled with schisms since the '70s. The "real Un*x" is a nostalgic fantasy (or an artefact of Stockholm syndrome, take your pick).

      *BSDers will say *BSD is reliable. That hasn't been a problem for Linux for a decade. (Except for Intel's video drivers...grrr.)

      Differences...apart from being behind the times hardware-wise (which you can do with Centos 4, if you want), the main difference is: only one "distro". (Although there are a few derivatives of FreeBSD and NetBSD, only their creators use them, pretty much.) BDSM submissives enjoy OpenBSD; no-one'd dare fork it.

      The FreeBSD man pages were better. Way better, as I recall. That's in part because they tried to avoid all that dubious GNU stuff. Can't say they were wrong about info(1), but I can say they were wrong about make(1).

      Filesystems. Linux and *BSD have *FAT*, NTFS, and ZFS in common. That's about it. FreeBSD has had ZFS for a couple of years longer than Linux.

      Culture. For a long time the *BSDs' attitude was "compile it from source, and fix the dependencies yourself". Like combining the bad parts of old-time Slackware and Gentoo. Might be better now; I've only tried Live CDs.

      Startup: I like the rc.conf startup configuration approach. (Way better than System Five initscripts. "Fragile" hardly begins to describe that approach.) I used Arch Linux for a long time because it had the closest approximation to rc.conf, but it also had drivers for USB and stuff. You know, the hardware I had attached to my PC. Not much, back in the day; but I wanted to use it. Arch was a pretty good compromise.

      Now, Arch Linux has moved away from an rc.conf-ish approach to using systemd. I've been getting progressively more annoyed with all the Sieved Poots appearing in linux, so I recently tried PC-BSD, which is supposed to be an end-user friendly porcelain on top of FreeBSD. Unfortunately, it's dire. Bug after glitch after missing object. On both my PCs, the typography is eyewatering. Worse than Windows 3.11.

      You're better off with FreeBSD. I might be going back there soon. Probably, though, it won't have support for my USB wifi stick. If you never see me comment again, you'll know what's happened.

    3. Re:What's the difference with Linux ? by real-modo · · Score: 1

      Correction: That was FreeBSD 2.2.26.

    4. Re:What's the difference with Linux ? by dargaud · · Score: 1

      Filesystems. Linux and *BSD have *FAT*, NTFS, and ZFS in common. That's about it.

      Strange, I expected a lot of common pieces between the two. The source for most things in /bin/ is the same, right ? Or are all options to, say, 'ls' different ?

      --
      Non-Linux Penguins ?
    5. Re:What's the difference with Linux ? by kthreadd · · Score: 1

      They are similar but not the same. Most Linux distributions uses the GNU user land, where FreeBSD develops its own. Programs like ls will still fulfill the same task, but the options will be different and some features might be missing. You can still install the GNU user land on top of FreeBSD if you want it.

    6. Re:What's the difference with Linux ? by Anonymous Coward · · Score: 0

      BSD is designed, Linux is grown.

    7. Re:What's the difference with Linux ? by TheRaven64 · · Score: 3, Interesting

      The reason I switched for FreeBSD around 2001 is that in-kernel sound mixing Just Worked. Two apps could write to /dev/dsp and get working sound. I'm now writing this while watching a DVD on the FreeBSD box connected to my projector and 5.1 surround sound system and I didn't need to do any configuration.

      The other big difference is ZFS, which makes a huge difference to how you manage storage. Creating a new volume is as easy (and fast) as creating a new directory. You get compression, deduplication, constant-time snapshots, and a load of other things via a very easy administration interface.

      If you're doing development work or running servers, jails give you a way of deploying a complete system that's got almost the same isolation as a VM but with much lower overhead. With ZFS, you can create one stock install and then clone it into a new jail in a few seconds.

      The base system is maintained as a whole and the developers take the principle of least astonishment (POLA) seriously. User-visible changes are minimised and new configuration utilities are expected to follow the pattern of existing ones.

      For firewalling, there are a number of choices, but the most sensible is probably the fork of OpenBSD's pf, modified to have better SMP scalability.

      For security, there's the MAC framework, which is roughly equivalent to SELinux, that the sandboxing on OS X and iOS are based on, and also Capscium, which provides a capability model that is better suited to application compartmentalisation. An increasing number of the system daemons use Capsicum for privilege separation.

      That's probably most of the user-facing things. You'll notice that GPU drivers (except for the nVidia blobs) tend to lag Linux somewhat. For Intel it's not so bad, for AMD it's quite a way behind (catching up, but not there yet).

      --
      I am TheRaven on Soylent News
    8. Re:What's the difference with Linux ? by inasity_rules · · Score: 1

      ZFS appears to have a performance advantage under BSD. Or am I out of date again? In any case, I use BSD as a cheap NAS for precisely this reason. It can saturate gigabit ethernet on a cheap slow system.

      --
      I have determined that my sig is indeterminate.
    9. Re:What's the difference with Linux ? by drinkypoo · · Score: 1

      Filesystems. Linux and *BSD have *FAT*, NTFS, and ZFS in common. That's about it. FreeBSD has had ZFS for a couple of years longer than Linux.

      Last I looked, Linux supported BSD disklabels and filesystems.

      FreeBSD has had ZFS for a couple of years longer than Linux

      Doesn't in-kernel ZFS still lead on BSD, too?

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    10. Re:What's the difference with Linux ? by Anonymous Coward · · Score: 0

      I've been getting progressively more annoyed with all the Sieved Poots appearing in linux

      What are Sieved Poots? I googled it, the first hit was your post and the others were about Mr. Poot's books on sieves.

    11. Re:What's the difference with Linux ? by unixisc · · Score: 1

      Linux can read NTFS, but that's about it. Neither FAT nor NTFS are native to Linux - you have the Ext2/3/4s, and coming soon, Btrfs. On the BSD side, you have UFS & ZFS/Hammer.

    12. Re:What's the difference with Linux ? by unixisc · · Score: 1

      That's what Debian's kFreeBSD project is.

      Does anyone know if there is a similar projects that puts a non-GNU userland on top of Linux?

  18. The license by neurophys · · Score: 1

    Is not a major part of the diffrence in success due to the license: In BSD you just take the code and use it, In most of the Linux-software it was GPL where you had to give back your development to the community?

    1. Re:The license by jbolden · · Score: 1

      I think so. I think that the GPL provide a way for corporations to cooperate and avoid the tragedy of the commons. Under the GPL you as a company get to use this valuable codebase for your project but in exchange you have to help a bunch of companies you neither know about nor care about. That worked much better than a situation where people were free to take without having to share.

    2. Re:The license by TheRaven64 · · Score: 1

      No. The GPL does not say you have to give back to the community, it means that you have to pass the source to anyone that you give the binary to. When Google extended Linux to run on their cluster infrastructure, most of those changes remained private. Given that 90% of all software development is in-house and not for public release, this only means that 10% of developers would be compelled to release code by the GPL. The remaining 90% are not affected, but often avoid GPL'd code because of possible future problems.

      Giving back to the community is a lot more about culture than license. Companies like Juniper, Yahoo! and NetFlix contribute a lot to FreeBSD, because it reduces their cost to maintain a smaller fork and because the more they give back, the more other developers are likely to care about bugs that they report.

      --
      I am TheRaven on Soylent News
    3. Re:The license by unixisc · · Score: 1

      But that works badly if the bunch of companies end up being competitors - which is a good part of what's plagued Ubuntu (even before they invented Unity). The Copyleft aspect of GPL is what sinks it. Let's say you have an ISV AcmeWare which puts together an HDL CAD software package. It costs millions to create, and its customers are essentially system designers who actually would find the source code useful (unlike the bulk of LibreOffice or Firefox users who don't know and don't care). The company knows this and decides to distribute the source code w/ the license.

      AcmeWare doesn't have an issue doing this. However, let's say that AcmeWare sells it to their customer Libre Micro (for say $50k) and licenses it under the GPL. Libre Micro buys it, and then does everything w/ it - install it on, say, 100 workstations, modifying some installations of it to do things specific to certain fabs, and works w/ certain customers and certain fabs. Libre Micro decides to recoup their software costs by selling it to their partners - fabs as well as system design customers, and since this license (and honestly, the BSD licenses as well) allow it, Libre Micro either gives it away, or sells it for, say $5k to 10 such companies. Following that, since Libre has recouped its expenses, they decide to either just give it away when they sell their system designs, or sell it for something nominal.

      After a while, it's well known in the market that this $50k package from Acme can be gotten from Libre for free, or close to it. Acme's sales dry up, and the company can't pay its bills. They can't tell Libre to cease & desist, b'cos the licenses very explicitly allow it. Essentially, those licenses would put their commercial creators out of business.

      That's why a modified version of GPL - call it NDOL (Non distributable Open License) - would be good. Retain all the rights in GPL3, except one - the inability to prevent redistribution. Under this, in the above example, AcmeWare could give Libre Micro all the rights that even GPL3 gives, but tell them that they can't distribute it outside their company. That way, Acme's potential customer base can only get that software from Acme, while Libre gets everything they need under this deal. As they get more workstations, they can spread out that initial cost even more, maintain that code inhouse if they differ w/ Acme's subsequent versions, but they can't do the things that would put Acme out of business.

      Something like this would preserve the GNU freedoms (except Freedom 2 - help your neighbor), w/o threatening to put GPL users out of business.

    4. Re:The license by jbolden · · Score: 1

      What you are talking about is something more like "shared source" than open source. Under shared source a company buys a commercial product with all sorts of license restrictions. They can get a copy of the source code and rights to modify the source for their own needs. But they have no right to redistribute. They don't necessarily need to contribute back so they can use their own IP in their improvement fairly freely. Those licenses exist. Military contractors are famous for shared source agreements.

      Ultimately though the core of the open source licenses is to have a very generous license that allows for redistribution. It is not the ability to modify source, but the ability to redistribute modifications. What you are basically saying is the GPL is a terrible shared source license, and you are right it is. It is an open source license. Two of the four freedoms are the are the freedom to redistribute and the freedom to improve and distribute improvements.

      There is no question the GPL makes selling software without a dual license scheme or without another service more or less impossible. But lots of licenses are incompatible with some business models.

  19. More Memories by normalbloke · · Score: 2

    I remember downloading 386BSD via ftpmail one floppy image at a time. And writing those images to soooo many floppies and again when some of them were corrupted. It took days to download and install 386BSD for the first time but eventually I got it up and running on an 386DX machine. The sense of awe and wonder I had when it finally booted was indescribable. Those were the days.

  20. Why didn't 'Andriod' use BSD codebase? by Anonymous Coward · · Score: 0

    Probably a naive question here but If the BSD license is so 'nonrestrictive' why are our Smart Phones not all BSD based?

    I realise that iOS has its roots in it, but was that purely for license issues?

    I'd have thought with all the super security and broad sweeping license that our smart phones would all be BSD based not 'Linux'.

    1. Re:Why didn't 'Andriod' use BSD codebase? by kthreadd · · Score: 1

      Android is mostly Apache license, which is very similar to BSD in nature. The kernel is more or less the only thing they ship that is GPL.

    2. Re:Why didn't 'Andriod' use BSD codebase? by steg0 · · Score: 1
      A good question which I've asked myself a number of times. As for Android, its libc is BSD based, but the kernel isn't.

      I don't know whether the decision to use a Linux kernel for Android was made at Android, Inc or later at Google, but it's pretty clear that Google wanted Linux.

      I suppose at the time, the whole Linux mobile thing had already generated a sufficient amount of traction so that a lot of the necessary infrastructure was already there.

      I was working for a mobile phone manufacturer at the time (that was later acquired and shut down by BenQ) and for us, the successor to Symbian would have been Linux, too, built along the Opie and Qtopia userlands on Texas Instruments OMAP hardware. Both Google and Trolltech had offices in the city (Munich). At that time, Google was still developing its products as J2ME software though.

    3. Re:Why didn't 'Andriod' use BSD codebase? by TheRaven64 · · Score: 1

      It did. Android's libc uses a lot of FreeBSD code. They've recently been talking to us about syncing some of their changes and treating us as they do other upstream projects that they pull code from, rather than maintaining a complete fork. They picked the Linux kernel for a very simple reason: Android was created by a small team, and they had experience with the Linux kernel.

      --
      I am TheRaven on Soylent News
    4. Re:Why didn't 'Andriod' use BSD codebase? by Anonymous Coward · · Score: 0

      This is really good news. On the other hand though I wonder if the reason Linux was chosen has more to do with mobile hardware providers doing up their SDKs with Linux in mind and not BSD? I wish just one hardware provider that manufactures with ARM processors would go with BSD seeing how well iOS has done commercially. BSD needs its own version of Android with an emphasis on LLVM. In a world with Emscripten and NetBSD rump kernels it could potentially be the most extensible mobile platform out there. LLVM has so many interpreters already you could script games with Lua, write business logic in Python, and blur the lines between web and native app with Ruby. Yes, you can do this with whats already out there but the licensing terms and pricing models are soul-crushing we need BSD to fight the good fight in the mobile arena as well.

    5. Re:Why didn't 'Andriod' use BSD codebase? by TheRaven64 · · Score: 1

      With my FreeBSD Core Team hat on, I have fairly regular meetings with people at ARM (which, conveniently, is about half an hour's cycle ride away). It's coming, but it's coming more slowly than I'd like...

      --
      I am TheRaven on Soylent News
    6. Re:Why didn't 'Andriod' use BSD codebase? by unixisc · · Score: 1

      I wonder whether Android could completely replace their Linux underpinnings w/ something like Minix (once it's ready for ARM) or FBSD? Then the footprint of the OS that runs everything in the phone or tablet would be even smaller, while at the same time, Google can make their thing shared source or closed source, as they like, and have the same advantages that iOS has by being closed source. The original team may have created it using Linux, but I don't see why Dalvik and all the userland technologies used by Google can't be ported to BSD, and avoid any GPL issues altogether.

      To address one thing the GP said, iOS was derived from OS-X - the underlying OS - XNU and FBSD userland - is the same, and that dates back from the NEXTSTEP days. It wasn't something that Apple decided to go w/ due to any licensing issues.

    7. Re:Why didn't 'Andriod' use BSD codebase? by TheRaven64 · · Score: 1

      We've ported Dalvik to FreeBSD. The Binder IPC stuff also needs porting, however having done this the isolation between applications could be much better enforced using Capsicum. For real-world usage, you'd also need to port the GPU drivers, because Android has its own graphics stack.

      --
      I am TheRaven on Soylent News
  21. i love u by Anonymous Coward · · Score: 0

    oh freebsd i loved u. these days were a minimal install took 60MB and a pkg_info of a working xfree desktop withbrowser (netscape uah) did not require 'less' to fit on one screen. binary pkgs tf- we all red the src before we compiled the packages :] it was a pleasure to read and patch your kernel code.

    ps. u remember the adaptec support story bro? >.

  22. Re:DEd by jones_supa · · Score: 1

    Aaaaaaaaaaaa!

  23. Where are the BSD/Linux Distros? by nbritton · · Score: 1

    I'm still waiting to see the BSD userland / toolchain environment spliced together with the Linux kernel. My headache with BSD was always hardware driver support. Linux, the kernel, has won that race, and rather then duplicate efforts I would like to see the best parts of *BSD merged on top of a Linux kernel. Instead of just GNU/Linux (SysV Style Linux), you could have an alternative BSD/Linux (BSD Style Linux) distribution. If you include Mac OS X, BSD style unix far an away out numbers SysV style machines.

    1. Re:Where are the BSD/Linux Distros? by jbolden · · Score: 1

      That sound like Gentoo. You take the Linux kernel and the BSD ports systems and engineer around that. What else are you looking for?

    2. Re:Where are the BSD/Linux Distros? by drinkypoo · · Score: 1

      So basically, you want a SunOS-like directory full of BSD userland applications? It seems like that should exist already.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    3. Re:Where are the BSD/Linux Distros? by slacka · · Score: 1

      I think BSD/Linux is a brilliant idea. I started off with SOLARIS and various flavors of BSD and have gradually moved over to GNU/Linux for hardware compatibility. Linux has finally reached BSDs rock solid stability, but I still miss the rc scripts, logical parameters, and well written man files of the BSD userland. Have you tried Starch Linux?

    4. Re:Where are the BSD/Linux Distros? by unixisc · · Score: 1

      It would be nice if Debian were to do something like this. Just like they have kFreeBSD, they could have BSDkLinux where they could take their Linux kernel, bring in a whole bunch of FBSD userland and port it there. Then they'd have kFreeBSD and BSDkLinux, in addition to their normal Linux and HURD projects. Heck, they could even toss in a Minix project into the lot.

  24. And good hard driver support is still missing! by Murdoch5 · · Score: 1

    I've attempted to use FreeBSD over the last 10 years and every single time I attempt to, I run into the exact same issue with hard drives. Simply the fact that my chipsets are never supported, IDE and Sata. I've been in the chatrooms on IRC, I've been on the forums and no one was ever able to answer me. So FreeBSD might be 20 years old but they still don't have hard drive support.

    1. Re:And good hard driver support is still missing! by Anonymous Coward · · Score: 0

      What type of weird hardware do you have?

    2. Re:And good hard driver support is still missing! by Anonymous Coward · · Score: 0

      Probably still using the same system from 10 years ago that didn't use IDE/SCSI. Dude, you got a Dell!

    3. Re:And good hard driver support is still missing! by Anonymous Coward · · Score: 0

      this is a horrible troll. Rarely a new RAID controller will be introduced by someone like Dell and it won't be supported in the current release, but there are always good instructions on how to work around this and usually an installer based on a -STABLE snapshot is floating around to assist you.

  25. VMware by Anonymous Coward · · Score: 0

    Single reason keeping me from using FreeBSD is lack of VMware.

    1. Re:VMware by unixisc · · Score: 1

      Have you tried VirtualBSD?

  26. Happy Birthday! by Anonymous Coward · · Score: 0

    Today, FreeBSD stands not only for software freedom, usability, stability, and the lasting legacy of a great idea, (the basis of UNIX,) but just as much, it stands for...

    FREakin' Excellent BIRTHDAY Software Distribution!

    That's the best I can do off the top of my head. If anyone can improve this joke, please feel free to download the source, tweak as you like, and re-release. All I ask is that you give credit to this post as the original basis of the joke. That's right, this joke is released under the FreeBSD License.

  27. Ooh! Yeah! by Greyfox · · Score: 1

    Happy birthday! Your user will be celebrating in the atrium! I understand there is to be cake!

    --

    I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

  28. FreeBSD and build breakage by jphamlore · · Score: 1

    Building current FreeBSD appears to have been broken since last night on amd64, as of the tinderbox build at 2013-06-22 13:32 UTC http://tinderbox.freebsd.org/ This frequent and lengthy build breakage appears to be both a technical and a social problem. It is a technical problem because FreeBSD appears to lack suitable incremental build tools so that developers can quickly test patches before committing them. It is a social problem because even using plain CVS, OpenBSD's developers seem to have almost zero problem keeping their current source at least buildable.

    1. Re:FreeBSD and build breakage by Anonymous Coward · · Score: 0

      FreeBSD CURRENT is working with an entirely new compiler. That update may have brought in an updated CLANG and now it won't build. I'm not sure why you should care about this; it will be fixed before release. If you're not a developer you don't gain much by building CURRENT these days.

    2. Re:FreeBSD and build breakage by jphamlore · · Score: 1

      That does not appear to be the problem, that is, a new compiler version: http://lists.freebsd.org/pipermail/freebsd-current/2013-June/042598.html Note the report to freebsd-current was submitted Sat Jun 22 13:09:04 UTC 2013. /usr/src/sys/fs/nfsclient/nfs_clstate.c:5160:33: error: format specifies type 'long long' but the argument has type 'uint64_t' (aka 'unsigned long')

  29. CopyRight, CopyLeft, CopyFree by srobert · · Score: 2

    That's a good description. I would add that each develops with a different open source philosophy; Linux under GPL, the BSD's under the BSD license.
    Proprietary software companies use CopyRight to preserve power for themselves.
    The GPL answer to it is CopyLeft, (I'll share with you, but only if you agree to share with everyone else).
    The BSD answer is CopyFree (I'll share with you. Period. I have faith that some good will come out of it).
    Perhaps both approaches in parallel are needed to prevent CopyRight holders from gaining absolute control over how we use computers.

  30. Different, not backwards by dbIII · · Score: 1

    There's a few things where it's ahead and a few where it is not. ZFS is the biggest thing it leads with IMHO, since the linux implementation (which I'm using on the computer I'm typing this on) has a lot of catching up to do.
    Another thing which really astonished me is it's performance on 32 bit hardware. To learn how to use freebsd I put it on a disused server full of IDE disks and it performed far better than the linux that had been on there previously. On more recent systems it behaves as well as linux does.
    Others who've used it for more than six months will have more to say.

  31. Still no Xen/Dom0 by cpghost · · Score: 1
    Happy Birthday FreeBSD! I've been around since the 1.x series, and I'm still using it on a day-to-day basis, both @home and @work (there, with thousands of FreeBSD servers).

    Having said that, I'm not really happy about the status of Xen on FreeBSD. Sure, Xen/DomU is working, no complaints about it. But we're waiting for Xen/Dom0 support for quite some time now, basically to host various VMs on FreeBSD/ZFS clusters. Sadly, Xen/Dom0 support is nowhere to be seen.

    --
    cpghost at Cordula's Web.
  32. Happy Bday! But the happy one is me by water-and-sewer · · Score: 1

    I still dabble with BSD on the desktop but usually revert to openSUSE or Bodhi Linux. But on my servers I reach for FreeBSD first, every time. After learning Linux, I found it wasn't hard to grasp the nuances of the system, and there was lots more to like: I find it gives preference to security over desktop conveniences as a default, ships a well-locked down system out of the box you can then add the minimum to as you need (rather than having to strip down a Linux install). I love its documentation, and despite all the hoo-hah about the user community, I have had great experiences with the BSD crowd: they're friendly and knowledgable and supportive. I've got a personal server running FreeBSD 9 and serving up postgresql and mysql databases, usenet newsgroups, email, and four different websites. It's chugging along beautifully with lots of RAM to spare, and it was super-easy to write a few scripts to do things I do regularly. Yes, you can do all this on Linux too (and I do prefer Linux for the desktop) but on FreeBSD you're forced to be methodical and explicit and really think about which services you are going to offer, what resources you're going to make available, and how it all fits together. It's been a great OS for me and I wish it another 20 years of life.

    --
    If this were Usenet, I'd killfile the lot of you.
  33. SunOS & Solaris by unixisc · · Score: 1

    History lesson wanted here - anyone knows if there were any reasons other than political why Sun went from a BSD based SunOS to an SVR4 based Solaris - aside from their partnership w/ AT&T/USL and enmity w/ the OSF guys IBM/DEC/HP? Did SVR4 actually have anything (in terms of features) that Sun needed, but that SunOS/BSD didn't have?

    1. Re:SunOS & Solaris by jbolden · · Score: 1

      I think it had a lot more to do with the kernel. Sun was moving from the Motorolla 68000 series processors (BSD kernel) to Sparc. They wanted technologies from Xenix (yes it hard to believe but Sun wanted Microsoft technologies in their Unix) and AT&T. More or less symmetric multiprocessing and multithreading were what drove the changes all the other stuff was incidental.

    2. Re:SunOS & Solaris by unixisc · · Score: 1

      But the early SPARCstation pizza boxes that we had on campus had SunOS running on them - on top of that, we had OpenLook, tcsh and other SunOS utilities (I forget whether we also had NeWS as well). Politically, there were a lot of splits - SVR4 vs OSF/1, OpenLook vs Motif, NFS vs DCE and so on. Was Xenix SVR4 based as well?

    3. Re:SunOS & Solaris by jbolden · · Score: 1

      Xenix was SVR3 based. SVR4 was Xenix based, SVR5 was defined by SCO which was the new name for Xenix and Unixware (also SVR4 based Novell product that was acquired by SCO).

      As for the architecture the cutover was the sun4c architecture that was the first hardware that supported Solaris. The Sun-4u architecture (64 bit processors) was the first architecture which was Solaris only.

    4. Re:SunOS & Solaris by hansot · · Score: 1

      Actually Sun co-created SVR4 8-). Quite early, I think in 1987 Sun and AT&T cut a deal (As I remember Sun stock was also involved) to jointly develop and market a unified version of Unix, containing features from SunOS, SVR3.2, 4.3BSD and Xenix (that originally was based on V7 and marketed by Microsoft).

      Such a unified version was not unwelcome after a decade of incompatible Unix versions from many different vendors. When SVR4 was released in 1988 it also promised compliance with the then new IEEE Posix standard. And additionally, the Berkeley CSRG had made clear on several occasions that they would not and could not offer commercial-grade support on their BSD system: they were an academic research group after all. And since the BSD source code was not yet publicly available, these were quite convincing arguments for both the Unix system vendors and their customers to move away from BSD toward SVR4.

      Of course the Sun-AT&T deal by itself caused quite a few new schisms. And Sun seriously botched the first releases of there SVR4 version (especially Solaris 2.2 and 2.3), which made Sun customers stick with SunOS 4 for a very long time (some even "downgraded" from Solaris to SunOS in response to continuing issues). The last release of SunOS (4.1.4) was in 1994, and I guess nobody expected it to last that long (especially not Sun).

      I don't think hardware was much a driver for Solaris. SunOS was also available for the Sparc and the M68K was quickly forgotten after the introduction of the Sparc. And though there actually was an MP version of SVR4 available at a certain point in time, it really smelled badly 8-) The reputation of Solaris for SMP stems mostly from its later releases (from Solaris 6 onwards) that considerably diverged from pure SVR4.

      So there probably were not many hardcore technical reasons to move to Solaris. But there was a class of users for whom the technical problems with Solaris (e.g. with its weird socket interface) motivated a move away from it during the first years of the Internet boom toward Linux and (of course) FreeBSD (both at least SunOS-like) and to Windows NT.

  34. Tomahawk BSD by unixisc · · Score: 1

    Is this desktop OS similar to, or based on, PC-BSD? What would be the differences, if any? How good/widespread would be the device support, which I believe would be the major roadblock to trying out BSD on a lot of hardware?

  35. Distros of both types by unixisc · · Score: 1

    Regardless of how they are developed, both Linux & BSD have distros, and in fact, distro families. In BSD, they started off w/ FreeBSD & NetBSD, which in turn spawned off other derivative distros. On the NetBSD side, you have OpenBSD (which now has its own fork in Bitrig), while on the FreeBSD side, you have DragonFlyBSD, Ghost BSD, Midnight BSD and others. The FreeBSD side also has distros specific to certain functions, such as FreeNAS for SANs and pFsense and m0n0wall for routers/firewalls.

    On the Linux side, the distro families are pretty much as varied as FBSD and NBSD are - you have Redhat/Fedora (Scientific Linux, OEL, Mandriva, et al), Debian (Mint, SolusOS, ZavenOS, et al), Gentoo (Sabayon, Calculate Linux), Slackware (Vector Linux, Salix, .Slackel) & Arch (Chakra, Manjaro). Of course, under Debian, you have Ubuntu and under that, Mint, Zorin, Trisquel, Hybryde, and so on.

    In short, both have distributions - yeah, fewer in BSD than in Linux, but still, plenty of choice in BSD as well.

  36. ZFS on BSD vs Solaris by unixisc · · Score: 1

    Does anyone know how the performance of ZFS compares on FreeBSD vs Solaris? Preferably on the same test beds - be it UltraSPARC or Xeon servers, so that the comparison is apples to apples

  37. ZFS on Linux? by unixisc · · Score: 1

    Does ZFS exist on Linux? The last I read about that was some loadable ZFS modules on Linux, since ZFS can't be a part of a GPLed kernel, since it's under an incompatible license called the CDDL

    1. Re:ZFS on Linux? by drinkypoo · · Score: 1

      http://zfsonlinux.org/faq.html

      google can be your friend

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  38. FBSD & IPv6 by unixisc · · Score: 1

    The biggest attractive thing about FBSD is IPv6 - FBSD has been ahead of the curve in supporting it. The only pity is that some of the other derivative projects, such as pFsense or m0n0wall are still not as good in their support of IPv6 as they are about IPv4.

    I am particularly excited about PC-BSD, although I haven't had the chance to use it as yet.

  39. Mac OS X is not founded on FreeBSD by Anonymous Coward · · Score: 0

    I cannot understand why year after year we have to bring this topic up... Gentlemen! Why can't you do your research and believe that Darwin is not based / founded on FreeBSD. Most of the Darwin / Mac OS X source code is from 386-BSD and not from the FreeBSD. Darwin Is a fork from 4.4 BSD fork 386-BSD fork made for NextStep. It's true it was updated with some of the components from the FreeBSD userland, but that is pretty minor. That's also the primary reason why there are security issues affecting OSX which don't exist in FreeBSD. FreeBSD and Darwin share same ancestry and some components but are separate BSD family members and very different from each other. The source code is out there, go read it...

    1. Re:Mac OS X is not founded on FreeBSD by mbadolato · · Score: 1

      I cannot understand why year after year we have to bring this topic up... Gentlemen! Why can't you do your research and believe that Darwin is not based / founded on FreeBSD. Most of the Darwin / Mac OS X source code is from 386-BSD and not from the FreeBSD. Darwin Is a fork from 4.4 BSD fork 386-BSD fork made for NextStep. It's true it was updated with some of the components from the FreeBSD userland, but that is pretty minor.

      So the page right on Apple's site, where it states:

      Darwin 1.4.1 is the UNIX-based, open-source foundation of Mac OS X. It is based on FreeBSD and Mach 3.0 technologies and provides...

      is incorrect then?

    2. Re:Mac OS X is not founded on FreeBSD by borehawg · · Score: 1

      NextStep consisted of the Mach microkernel, BSD (probably the 4.3 release, and updated to 4.4 and Net/2 when later available), and some other technologies outside the BSD arena. After Apple purchased it, it probably contained whatever the latest free BSD code was available...4.4 BSD-Lite, probably, since 386BSD was the original BSD port to Intel hardware (from which FreeBSD was derived)/ Darwin was Apple's open source release of their [then] current version of Mac OS X...Cheetah, I think? I played with a copy of OS X server when it was first released in 1998, and found the command-line remarkably similar to FreeBSD 2.x (though I was not an expert and the BSDs have kept many BSD-isms throughout the ages). Apple had probably integrated the latest BSD derivative available for that Mac OS X release. I remember reading about a switch to from FreeBSD 3.x to 5.x in the Panther release notes or somewhere similar, so they had long since switched to FreeBSD from whatever NextStep used by the time Darwin was released.

      So, no. Darwin wasn't originally based on FreeBSD. Darwin was the source code based on released version Mac OS X, which was originally based on NextStep/OpenStep, which was based on Mach/BSD, which existed before FreeBSD.

      The Apple Darwin kb page linked above is part of Apple's (now-defunct) attempt to drum up interest in Darwin as the core of Mac OS X, but wasn't a fork of 4.4BSD as the AC post above implied.

  40. freebsd got me through the 90s by xuvetyn · · Score: 1

    but with that said, desktopbsd seems to be dead. =(

    --
    alive to the universe, dead to the world
    1. Re:freebsd got me through the 90s by unixisc · · Score: 1

      PC-BSD is still alive, though

  41. GPU Drivers? by Anonymous Coward · · Score: 0

    Do game consoles even use drivers? I thought they just compile the OpenGL code into binaries, bypassing the need for drivers.