Slashdot Mirror


FreeBSD Status Report for 2005 Q2

koinu writes "FreeBSD Status Report for the second quarter 2005 has been published by Scott Long. It gives a more precise description of what is being done on the 18 Summer Of Code projects." From the post: "The Google Summer of Code project has also generated quite a bit of excitement. FreeBSD has been granted 18 funded mentorship spots, the fourth most of all of participating organizations. Projects being worked on range from UFS Journalling to porting the new BSDInstaller to redesigning the venerable www.FreeBSD.org website."

145 comments

  1. 5.4 - 6? by Neo-Rio-101 · · Score: 1

    Whaaa.... I just installed 5.4 and they're already thinking of jumping ship to a PRODUCTION version of FreeBSD 6.0 already?

    --
    READY.
    PRINT ""+-0
    1. Re:5.4 - 6? by thundercatslair · · Score: 0, Redundant

      I see a hard drive format in the future for you.

    2. Re:5.4 - 6? by Anonymous Coward · · Score: 4, Informative

      Did you not read it?

      "The purpose of
      quickly jumping from 5.x to 6.0 is to reduce the amount of transition
      pain that most users and developers felt when switching from 4-STABLE
      to 5.x. 6.0 will feature improved performance and stability over 5.x,
      experimental PowerPC support, and many new WiFi/802.11 features. The
      5.x series will continue for at least one more release this fall, and
      will then be supported by the security team for at least 2 years after
      that. We encourage everyone to give the 6.0-BETA snapshots a try and
      help us make it ready for production. We hope to release FreeBSD 6.0
      by the end of August."

    3. Re:5.4 - 6? by Seumas · · Score: 1, Funny

      Does it even really matter?

      FreeBSD is DYYYYYYYYIIIIIIIIIINNNNNNGGG!

      (Queue the dramatic music).

    4. Re:5.4 - 6? by waltznumber3 · · Score: 0

      (Dramatic music) PS: nice way to twist a BSD article to a google post PSS: BSD, unfortunately, is in fact dead. Too bad. Wait no, not really.

      --
      If you just took anything I said seriously, read it again.
    5. Re:5.4 - 6? by jericho4.0 · · Score: 4, Funny

      I see...Less pain, more often.

      --
      "A language that doesn't affect the way you think about programming, is not worth knowing" - Alan Perlis
    6. Re:5.4 - 6? by mat+catastrophe · · Score: 1

      = -0.6

      --
      sig not found
    7. Re:5.4 - 6? by Neo-Rio-101 · · Score: 1

      Of course I read it. Thing is, what the heck is the point of maintaining a FreeBSD 5.x machine when they're going to stop security patches in a year or two? At least FreeBSD 4.x had a run of... how many years? I've been able to patch boxes running or 4.x for quite a while now, but jumping from 4 to 5, or in this case from 5 to 6 requires a complete reinstall. That sucks if you've just unrolled a 5.x server.

      --
      READY.
      PRINT ""+-0
    8. Re:5.4 - 6? by someonehasmyname · · Score: 1

      It doesn't require a complete reinstall to migrate from 4.x to 5.x, and I'm sure going from 5.x to 6.x won't require one either.

      I've upgraded about 20 machines from 4.x to 5.x all without any problems.

      Instrustions are near the bottom of /usr/src/UPDATING once you've cvsup'd the RELENG_5_4 branch.

      --
      Common sense is not so common.
    9. Re:5.4 - 6? by laffer1 · · Score: 1

      Yes, if you have PHYSICAL access to a machine its POSSIBLE to upgrade from 4.x to 5.x. Its also strongly discouraged.

      I've actually tested several times doing an upgrade from source using ssh on two machines here to see if it would be possible on a 4.x production server I have colocated. Its not possible in the least bit with 5.4 release from 4.10. I followed /usr/src/UPDATING.

      Now if you were to have serial/console access and could go into single user remotely, then maybe it would be fine.

      I'd love to upgrade 5.x as i'm running it at home on several machines. I hope port maintainers remember people like me or its going to be a real pain in the near future. I have a feeling the 6.x release will spark the 4.x is two versions behind argument.

      Also, for anyone thinking of upgrading to 6.x or running a beta on an amd Semptron 2300+, dont. I can't even boot the iso install cd. Kernel panics like crazy. I've got an MSI nforce2 based motherboard with an nvraid sata controller and my install partition is on an ide drive. I tried to contact someone about this, no response. The sata controller is not supported in 5.x with my patches.

    10. Re:5.4 - 6? by HvitRavn · · Score: 1

      No wonder you got into troubles if you didn't drop into single user mode before installing the kernel and the userland binaries. It might be worth reading the handbook too, not just UPDATING. And where does the FreeBSD organization strongly discourage upgrading from 4.x to 5.x?

    11. Re:5.4 - 6? by laffer1 · · Score: 1

      Prior to 5.4 it was often said on freebsd-questions and a few times on freebsd-hackers. I'm on both mailing lists. I've read the handbook and was told several times its usually safe to do an install kernel and mergemaster -p. If the kernel boots ok, you can do an installworld and mergemaster and then reboot again safely.

    12. Re:5.4 - 6? by Anonymous Coward · · Score: 0

      I have in fact read that moving from 4x to 5x isn't really encouraged. Generally there is just too much that changed and the chances of you having libraries that don't jive is too high. So it's easier just to back up your data, wipe the drive and start over (Also because you wouldn't get UFS2 with a 4x upgrade).

  2. Re:Must resist... by Anonymous Coward · · Score: 0

    why does this article have the google logo?
    did google buy freebsd?

  3. Re:Must resist... by qbwiz · · Score: 3, Informative

    No but Google did bring in some $90000 worth of support through their Summer of Code project.

    --
    Ewige Blumenkraft.
  4. Holy crap... by shadowmatter · · Score: 3, Funny

    The first guy on the list, Anders Persson, works in the same lab as I do and I had no idea he had a SoC project.

    I need to get outside my cubicle more...

    - shadowmatter

    1. Re:Holy crap... by nxtr · · Score: 2, Insightful

      Wasn't Summer of Code meant for school students? I think your friend might be in it for more than the coding...

    2. Re:Holy crap... by jericho4.0 · · Score: 2, Funny

      No kidding. You're number 8 on the list, get to work.

      --
      "A language that doesn't affect the way you think about programming, is not worth knowing" - Alan Perlis
    3. Re:Holy crap... by Anonymous Coward · · Score: 0
      No, you need to get outside the *building* more.

      P.S. Ask him if this is the summer it finally dies.

  5. Re:Must resist... by Anonymous Coward · · Score: 0, Funny

    No, BSD is dead, silly. You can't use their logo.

  6. Allah... by Anonymous Coward · · Score: 1, Funny

    ...Akbar!

    *pushes detonator*

    1. Re:Allah... by Anonymous Coward · · Score: 0

      Um. I suppose suicide bombers are funny?

      I'm not exactly a Bush-voting Fox-news-watching terror-exaggerating neo-con zionist, but I find that pretty offensive. I mean, Christ. That's awful.

  7. Re:Allow me to be the first to point out that by PakProtector · · Score: 1

    You know the Trolling community has really gone downhill when they copy and paste the trolls and don't even put in the effort to remove the extra [somesite.com] information blocks that show up after links...

    Are we witnessing the end, or the beginning, of an Era of Trolldom?

    --

    Edward@Tomato - /home/Edward/ man woman
    man: no entry for woman in the manual.
    "Qua!?"

  8. Re:FreeBSD Status Report for 2005 Q2 by Anonymous Coward · · Score: 0

    I'm confused. Why is it supposed to be dead?

  9. Re: the end of trolls by Anonymous Coward · · Score: 1, Funny

    FACT: BSD Trolls on Slashdot are dying.

  10. Wireless networking ! ? by Anonymous Coward · · Score: 0

    Is the wireless networking just someone scratching his own itch?

    I had sort of a hazy idea of what FreeBSD is all about and it didn't include wireless. Maybe I've got the wrong idea about wireless. (Wireless == desktop (y/n)) Anyway I thought wireless was not required for a 'serious' OS.

    What am I missing here?

    1. Re:Wireless networking ! ? by someonehasmyname · · Score: 4, Informative

      Wireless has worked with FreeBSD for a long time.

      What hasn't worked was newer forms of wireless encryption, like WPA-PSK.

      --
      Common sense is not so common.
    2. Re:Wireless networking ! ? by Anonymous Coward · · Score: 0

      I have 2 bsd machines here at home, one to handle some server tasks, ipfw/dummynet, natd, ntp, dhcpd, dns ... it sits in a closet with no monitor or keyboard and certainly does not need wireless. But I also have a laptop that i use to check email, slashdot and stock quotes on occasionally. It is silly that I cannot use secure wireless networking such as wpa with AES but need to downgrade to wep. Why not? the access point supports it, my wifes windows machine supports it, in fact I almost have to say with windows "it just worked" but the freebsd does not. It is a shame that windows has a more secure wireless implmentation than freebsd.

    3. Re:Wireless networking ! ? by bnitsua · · Score: 1

      works fine for me... use hostapd.

    4. Re:Wireless networking ! ? by TheRaven64 · · Score: 1

      Wireless has worked for ages. I used to use a 4.7 machine as a wireless access point (Prism card). My ThinkPad uses FreeBSD's Project Evil to run a no-name WiFi card using the Windows drivers.

      --
      I am TheRaven on Soylent News
    5. Re:Wireless networking ! ? by setagllib · · Score: 1

      WPA uses the same algorithm as WEP, A/RC4, just it uses a more intelligently designed key distribution and regeneration system which makes up for a few of the algorithm's deficiencies. Since you probably don't believe me, "Data is encrypted using the RC4 stream cipher, with a 128-bit key and a 48-bit initialization vector (IV).".

      I don't know where the misconception that WPA is based on AES came from. There was never any credible document to suggest it.

      WPA still sucks compared to IPSec or OpenVPN, and I use the latter to make my wireless network (including Windows clients, which are very hard to support with IPSec) essentially a slow wired one, including strong encryption and authentication, and normalisation of out-of-order and replayed packets (the latter being particularly common for Wifi). This is especially good since OpenVPN doesn't care what your wireless device supports: your processor does the crypto itself. There's no need to buy new hardware because you want WPA, which some people actually do.

      --
      Sam ty sig.
    6. Re:Wireless networking ! ? by Anonymous Coward · · Score: 1, Informative

      Very good comment on openVPN - likely the most flexible solution.

      However, as for wpa with aes:

      With 802.11 and WEP, data integrity is provided by a 32-bit integrity check value (ICV) that is appended to the 802.11 payload and encrypted with WEP. Although the ICV is encrypted, you can use cryptanalysis to change bits in the encrypted payload and update the encrypted ICV without being detected by the receiver.

      With WPA, a method known as Michael specifies a new algorithm that calculates an 8-byte message integrity code (MIC) using the calculation facilities available on existing wireless devices. The MIC is placed between the data portion of the IEEE 802.11 frame and the 4-byte ICV. The MIC field is encrypted together with the frame data and the ICV.

      Michael also helps provide replay protection. A new frame counter in the IEEE 802.11 frame helps prevent replay attacks.

      AES support
      WPA defines the use of Advanced Encryption Standard (AES) as an additional replacement for WEP encryption. Because you may not be able to add AES support through a firmware update to existing wireless equipment, support for AES is optional and is dependant on vendor driver support.

      Google for "wpa aes" to find 344,000 other articles about it.

    7. Re:Wireless networking ! ? by Anonymous Coward · · Score: 0

      Clearly, you have no fucking clue what you are talking about. WPA uses TKIP, not the WEP protocol or encryption method. WPA2 (the vendor pre-implementation of the 802.11 enhanced security standard) uses AES. Tons of companies support WPA2 in their 802.11g and newer 802.11a products. Get with it, moron.

    8. Re:Wireless networking ! ? by setagllib · · Score: 1

      http://en.wikipedia.org/wiki/Wi-Fi_Protected_Acces s

      Read my post AND a reference before assuming I'm wrong. I did not say WPA used WEP. I said it used the same encryption algorithm, RC4 (called ARC4 in non-official implementations because of the license requirement).

      AES is only in WPA2, which we were not talking about.

      "Get with it, moron."

      --
      Sam ty sig.
  11. Re:FreeBSD Status Report for 2005 Q2 by Saeed+al-Sahaf · · Score: 1
    I'm confused. Why is it supposed to be dead?

    I believe the joke is that Netcraft confirms it, or something like that.

    --
    "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
  12. Re: the end of trolls by binary+paladin · · Score: 3, Funny

    I heard Netcraft even confirmed it.

  13. thank you, one person who gets the joke by Anonymous Coward · · Score: 0

    you made it totally worth my time.

  14. Soft updates by fsterman · · Score: 2, Insightful

    I though soft updates made journaling unneeded and everything slower?

    Please enlighten.

    --
    Is there anything better than clicking through Microsoft ads on Slashdot?
    1. Re:Soft updates by Anonymous Coward · · Score: 0

      Sounds like the MySQL attitude: badmouth features you don't have, until you implement them, at which time they become brilliant. Remember when referential integrity was "unnecessary bloat"? Don't hear that now that MySQL has it, do you?

    2. Re:Soft updates by fsterman · · Score: 1

      Uh-oh. I didn't really know what soft updates were, the stuff I had been reading was a little too high level. From my latest googleing I am afraid I may have started a flame war, I apologize in advance.

      --
      Is there anything better than clicking through Microsoft ads on Slashdot?
    3. Re:Soft updates by Mr.Ned · · Score: 4, Informative

      Soft updates are an alternative to journaling, but they still require a fsck on an unclean unmount. Although this fsck can be done in the background (with snapshots) after the filesystem has been mounted and is otherwise available for normal use, the fsck still takes significant time and system load - neither of which are an issue with an unclean unmount of a journalled filesystem. I believe one of the primary motivations behind adding journaling to UFS is to remove this drawback relative to journaled filesystems.

    4. Re:Soft updates by Anonymous Coward · · Score: 1, Insightful
      When Aesop wrote his fable of the Fox and the Grapes he could have been thinking about FreeBSD.

      It seems that mangy old fox was trotting along a dusty lane when he came upon a grape arbor. Those juicy grapes hanging up there looked mighty tempting to that old fox. So he leaped and he jumped. Try as he might, that fox could not jump high enough to reach those prize grapes. After awhile that old fox was left panting and thirsty. His big red tongue was hanging out, swollen and dry. Finally he said to himself "who wants those grapes anyhow? Those grapes are probably sour anyway." So he hung his head and trotted away.

      That is the the age old story of FreeBSD. Every time another operating system offers a good feature not available in FreeBSD, the FreeBSD pr machine works overtime disparaging that functionality--at least until FreeBSD figures out how to implement it too!

      You name it, the FreeBSD pr machine has historically exhibited the dubious honor of having disparaged

      • shared libraries
      • journaled file systems
      • ELF object files and binaries
      • ide disk drives
      • X.org
      • on, and on, . . .
    5. Re:Soft updates by r7 · · Score: 1

      I though soft updates made journaling unneeded and everything slower?

      Not even close. Soft Updates, background writes, and background fsck do not protect against data loss and corruption like journalling. The only thing you ever need to worry about on journalling filesystems is a hardware error, and that mainly on non-SCSI drives without RAID.

      Also, journalling tends to speed up more types of writes than it slows. On busy filesystems it is almost universally faster.

      A journalling filesystem should bring FreeBSD to about the level of performance and reliablity that Solaris reached 7 years ago. It's about time!

      r7

    6. Re:Soft updates by Anonymous Coward · · Score: 0

      Only until FreeBSD finally found someone stupid enough to spend man-years adding them under the license-to-work-as-a-slave,... and suddenly, they become the thing to have -- and naturally, FreeBSDs version is better than everyone else's... even if it's not really.

    7. Re:Soft updates by Anonymous Coward · · Score: 0

      Mod this up... clever, funny and pointed.

    8. Re:Soft updates by mr.mighty · · Score: 1

      Actually, the lack of journalling drove me from FreeBSD a few months ago. My "mail server" runs on an old box I got out of the garage, so I'm not really interested in spending money on a UPS. The power went out, and when it came back on the boot loader couldn't find the kernel. Fairly easy to fix, but I remember thinking that this wouldn't have happened with ext3.

      Unfortunately, I find the performance to be quite a bit slower with Linux now. I realize that a different choice of distro might have helped, but I really would prefer FreeBSD, if they had journalling.

    9. Re:Soft updates by Anonymous Coward · · Score: 0

      Sorry to burst your buble, but journaling isn't bullet proof either. Sure, there's no fsck involved, but data loss is still there. Try it yourself, pull the plug on a jfs or xfs formatted system under heavy i/o and see your files disappear. I've seen this happen several times. The files are gone, even their directory entries are removed.

      About Solaris, you mean paying a lot of cash to use Veritas Filesystem, right? Because Sun's UFS certainly wasn't journaled 7 years ago, although ISTR they've added some features for Solaris 10.

    10. Re:Soft updates by geniusj · · Score: 1

      The only thing a fsck will do for you with softupdates is free up some space that didn't get properly free'd before a crash. You can completely skip the fsck if you want though and everything will still work fine, you'll just have some space that's unaccounted for.

  15. Why is the topic so ? by Gopal.V · · Score: 1

    I think it's not fair to mark this as Google.

    Sure google's doing a lot to *many* OSS projects out theres - but the news article was about BSD, should be marked the reliable 'red' devil (uh.. daemon).

    I guess half the comments would be about this :)

    -1: Redundant

  16. MOD PARENT DOWN by linguae · · Score: 1

    I can't believe that this post is already at +2, with Informative mods. This is just another Anonymous Coward trying to post another "BSD is Dying" troll, just in a different way by posting some developer's dissatisfaction with BSD. If this were the real Mike Smith, then he would have signed in. "The End of FreeBSD"? Hardly. FreeBSD is growing in nice numbers, and FreeBSD is getting better with every release.

    1. Re:MOD PARENT DOWN by Doc+Ruby · · Score: 1

      The AC did not claim to be Mike Smith. To the contrary, their note as "Ed." (editor) implies that they are someone who is not Mike Smith. And the note is authentic. They did, however, omit the date: three years ago, 5/9/02.

      Therefore, "BSD is dying" inferences are up to you. If you're not going to check an anonymous info dump on the Internet, then any mistaken inferences are your own fault.

      --

      --
      make install -not war

  17. Re: the end of trolls by mbrewthx · · Score: 1

    But in Soviet Russia BSD (Open, Net and Free) confirms Netcraft is dead!!!!

    --
    __________ Leave me alone I'm compiling a RPG II program on my S/36...Thanks to metamucil I'm a Regular Meta Moderator
  18. Why all the FreeBsd Hate comments? by refactored · · Score: 1
    If you browse at -1, there are lot of A/C's trolling freebsd.

    Are these just trolls figuring it would easy to spark a Linux/Bsd or XBsd vs YBsd flamewar here...

    Or is there a deeper reason for the dissension that I'm not aware of.

    If it's just trolls, they and the moderators are working unusually hard at fighting each other.

    1. Re:Why all the FreeBsd Hate comments? by thebagel · · Score: 1

      Howabout a new mod option, -1 Needs a Sense of Humour...

  19. *nix. What the hell does splat mean? by elgee · · Score: 0, Flamebait

    I was thinking of putting some flavor of *nix on a spare machine at home. But the more I read /., the more I am leaning towards just letting the spare machine be a piece of non-functional furniture.

    It is like going into some mythical hamburger joint intendding to get a burger and being confronted with a menu of 8000 burgers. And many of those burgers have multiple versions. "Chunky Munkey Burger V5.3"

    I gotta get more of a real life. Call me offtopic or whatever.

  20. that's close to the truth by r00t · · Score: 5, Informative
    There are many types of journalling. The ext3 filesystem alone supports three! You can journal all data (extreme), you can journal metadata prior to writing plain data, or you can just journal the metadata.

    There is softupdates, which orders things a bit. After a crash, there should be (knock on wood) only a few minor errors related to free space not being marked free.

    There is sync, the traditional and fairly slow way. This generally provides unneeded determinism for directory operations. Normally we want as many pre-crash changes as possible, not just ones that can be made in perfect order. Some very unportable BSD software relys on sync behavior.

    There is async, which plays fast and loose with everything. This works rather poorly on FreeBSD. It is likely that fsck will make a mess on boot, and illogically an async mount is slower than a softupdates mount. Linux has a nearly-true async, the default for ext2, that is very fast. (if an app explicitly requests a sync, the request is not ignored) The ext2 fsck is also extremely reliable, allowing for recovery of async filesystems that would be unheard of in the BSD world.

    So that is:

    • async
    • sync
    • soft updates
    • full data journalling
    • ordered data journalling
    • metadata journalling
    (and the patented obsolete delayed ordered writes from SysV, if I remember right)

    The really strange thing is that sometimes heavy-duty journalling can be fastest. This is often the case with mail servers which explicitly sync data to disk. A full-data journalling filesystem (as ext3 can be) may legitimately report completion as soon as the data hits the log, which is a nice big linear disk write. Other filesystems, though faster for normal use, will have to seek all over the disk before they can legitimately report completion.

    Modern hardware screws all of this up horribly though. As the XFS developers discovered to their horror, power loss will corrupt data in memory or in transit to the disk before it stops the disk from operating. (yes, even when using appropriate fence or flush operations) Uh oh...

    1. Re:that's close to the truth by timmarhy · · Score: 1

      hah Evil Write Cache tm

      --
      If you mod me down, I will become more powerful than you can imagine....
  21. Upgrades do not require "complete reinstalls" by toadlife · · Score: 2, Informative

    "I've been able to patch boxes running or 4.x for quite a while now, but jumping from 4 to 5, or in this case from 5 to 6 requires a complete reinstall."

    It's very hard for me to believe that you've been running FreeBSD servers for years, and don't know that version to version upgrades can be done with minimal pain. Upgrades from one version of FreeBSD to another *do not* require complete reinstalls.

    Yes, a 4.x to 5.x upgrade has the potential to be tricky, due to the major changes involved, but upgrading from 5.x to 6.x will not be a nearly as hairy.

    Take a look at this email from one of the FreeBSD developers, in response to a question just like yours.

    --
    I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
    1. Re:Upgrades do not require "complete reinstalls" by Anonymous Coward · · Score: 0

      im new to freebsd and was actually attempting to try the 6.0 beta today (with the full upgrade from cd)

      thanks for the info i feel a lot better about doing it now

      (its a nonproduction machine so if it doesnt work oh well (but hey if i run into probs i can report them)

    2. Re:Upgrades do not require "complete reinstalls" by Neo-Rio-101 · · Score: 1

      If you read my mail, you would have noticed that I was referring to the difficulty of jumping from version 4 to 5, and not incremental upgrades (such as from version 4.10 -> 4.11 for example)

      All in all, trying to upgrade from version 4 to 5 is not supported (or recommended) from the FreeBSD team - and while it probably is possible to do in one form or another - from a support point of view it's simply not worth the hassle or risk.

      Good to hear that an upgrade from 5 to 6 won't be painful or risky. (I hope)

      --
      READY.
      PRINT ""+-0
    3. Re:Upgrades do not require "complete reinstalls" by toadlife · · Score: 2, Interesting

      Understandable. I would be cary cautious at moving a 4.x box to 5.x, (as I've seen the big changes) if it were a very important production setup.

      I had the same kind of 'WTF?' reaction back when it was announced that 6.x was coming soon, before reading that the difference between 5 and 6 wasn't earth shattering and updating from 5 wouldn't be a huge deal.

      --
      I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
  22. Tired of obligatory *BSD is dying comments by Zweideutig · · Score: 4, Interesting

    I think I speak for the rest of the Slashdot community when I say I am tired of the "*BSD sucks" and "*BSD is dying" posts I see. I view at -1 threshold because I don't care for someone else deciding what I should read, but I get annoyed when I see Anonymous Cowards posting these obligatory trolls. Netcraft confirms that *BSD is not dead. Some of the sites with the highest uptimes are running *BSD. I run NetBSD and OpenBSD on servers/firewall, and Gentoo Linux on my desktops, so I am not a *BSD elitest either.

    --
    Powered by caffeine and sugar; BSD
    1. Re:Tired of obligatory *BSD is dying comments by Anonymous Coward · · Score: 5, Funny

      Sir, this post is to warn you that we Anonymous Cowards do not value your opinion regarding the status of "BSD is dying" posts. Frankly, since Netcraft confirms that BSD is dying, it is clear that BSD is dying. This makes "BSD is dying" posts on topic in the context of an official FreeBSD status report. Now, sir, I suggest you do your part to help the BSD family of operating systems die gracefully by

      1. Grounding yourself in the fact that BSD is dying.
      2. Stop complaining about the fact that BSD is dying.
      3. Removing NetBSD and OpenBSD from your servers/firewall.
      4. Installing any VMS derivative operating system you'd like on your servers/firewall.

      We Anonymous Cowards understand your frustration. The BSD family was a wonderful group of operating systems, but the time has come for them to finally rest. You have our sympathy.

    2. Re:Tired of obligatory *BSD is dying comments by Dwedit · · Score: 2, Insightful

      I don't think anyone who posts those messages actually thinks that BSD is dying. They are just posting to keep up a traditional joke.

    3. Re:Tired of obligatory *BSD is dying comments by bnitsua · · Score: 3, Funny

      oddly enough, netcraft runs FreeBSD... does that mean netcraft is dying?

    4. Re:Tired of obligatory *BSD is dying comments by jandrese · · Score: 1

      What you're really saying is that you don't trust the Moderators on Slashdot, but you also don't want to see useless posts/spam? You can't have it both ways, you need to either accept someone else's opinions or you need to sift through all of the chaff yourself. There is no magical anti-spam faery that will do your work for you exactly the same way you would. Either invest some trust in the moderators, or stop complaining.

      --

      I read the internet for the articles.
    5. Re:Tired of obligatory *BSD is dying comments by Hanji · · Score: 1

      That gives me an interesting, absolutely absurd idea. Would it be conceivably possible to hack a GreaseMonkey plugin that gave you a pseudo-moderation dropdown for every post, and used that info to train a Bayesian filter that would automatically hide or show posts based on inference from your past, personal moderation? There are a number of obvious issues, but it seems like it could potentially be a cool idea...

      --
      A Minesweeper clone that doesn't suck
  23. Re:*nix. What the hell does splat mean? by iggymanz · · Score: 1

    aw c'mon, just grab a splat-nix that sounds hip/interesting/mysterious to you and go with it, whatever flavor of splat-nix you choose they'll be plenty of zealots who'll make you feel like you did the right thing. They're all cool in their own way, they're free, and you learn one you've learned 80% of the others. The same software will more than likely run on all of them. I don't know why you got modded down, there ARE more Linux distros out there than any one person could name, and 3 no wait 4 BSD and now opensolaris...I could see why someone would throw up their hands and say WTF??!!

  24. launchd and PowerPC by ArbitraryConstant · · Score: 2, Interesting
    So far progress has been slow, the autoconf build system has been removed from all of the launchd(8) code, and launchctl(1) is building and semi-functional on FreeBSD-CURRENT (i.e. CoreFoundation hooks have been removed)

    I'm currently working on porting "liblaunch" which is the core backend to both launchd(8) (the actual daemon) and launchctl(1), there are some mach/xnu specific hooks and calls that need to be remove and either reimplemented or worked around.

    We're also waiting on a response from Apple on a possible BSD-licensed version of the code (it's currently under the APSL) Progress is slow, but steady.
    Haven't worked with launchd, but there isn't an init system left that I don't hate so any hope of improvement is welcome.

    also...
    Florent Thoumie has updated the massively out-of-date platform page. Work continues to creating a 6.0 release of the PowerPC port.
    With Apple giving up on it, is it really worthwhile to develop a PowerPC port? IBM and others will still sell PowerPC hardware, but it's not going to be a major desktop/small server platform anymore. Big server and embedded, sure, but the middle is going away and FreeBSD lives in the middle ground.
    --
    I rarely criticize things I don't care about.
    1. Re:launchd and PowerPC by Anonymous Coward · · Score: 0

      Yes!

      As soon as I heard about launchd, I was hoping that someone would port it to FreeBSD, glad to see that it's in the works.

    2. Re:launchd and PowerPC by Macka · · Score: 2, Insightful


      With Apple giving up on it, is it really worthwhile to develop a PowerPC port

      You're falling into the same trap that most of the herd seem to. Just because a vendor announces platform retirement doesn't mean its dead the moment they announce it.

      Alpha retirement was announced years ago, yet I still work on projects that are putting new Tru64 Alpha's in. Albeit not for much longer I'm sure. Same with Apple PowerPC. They will be selling new PowerPC systems for a couple of years yet, and then after that there will be a few score million systems out there for many years that will be excellent candidates for FreeBSD servers. I expect there will be lots of bargains to be had on eBay.

    3. Re:launchd and PowerPC by Anonymous Coward · · Score: 0

      Talk about being late for the party. FreeBSD doesn't even have a functional port to the PowerPC and now the plug is being pulled on it. How many years has FreeBSD been trying to get a port to the PowerPC architecture? At least 10 years -- and it's still not ready. The failed effort has outlived its target :-) That's a hot one!

    4. Re:launchd and PowerPC by TheRaven64 · · Score: 1

      Launchd is a fairly sane init system. The real block to its adoption is the license which has some rather nasty clauses about IP in it (i.e. you use our software, we are free to steal all of your IP). If they can persuade Apple to release it under a BSD license then it could well become the new standard (although Solaris won't use it because they've only just migrated to their new SMF system).

      --
      I am TheRaven on Soylent News
    5. Re:launchd and PowerPC by laffer1 · · Score: 1

      It was asked on the freebsd-ppc list why they are still doing the port. The main guy, Peter Graham (sp?) said the plan was to port it for IBM hardware to begin with. He considers that the important step. The mac stuff was a nice bonus and a way to get help with the project.

    6. Re:launchd and PowerPC by Nimrangul · · Score: 1
      I really don't think that it will become any kind of standard for Unix-likes.

      The idea behind Unix has always been to have small parts that do their own job, not some giant monster that does everything.

      It would probably become the common with Linux distributions pretty quickly if it worked well on FreeBSD and Apple allowed for the code to be relicensed under BSD terms - but I don't think that the operating systems that are trying to be Unix-like will adopt it.

      --
      I'm sick of following my dreams - I'm just going to ask them where they're going and hook up with them later.
    7. Re:launchd and PowerPC by ArbitraryConstant · · Score: 1

      "The idea behind Unix has always been to have small parts that do their own job, not some giant monster that does everything."

      UNIX accepts integration when it makes sense, for example inetd.

      --
      I rarely criticize things I don't care about.
    8. Re:launchd and PowerPC by Anonymous Coward · · Score: 0

      Um. All inetd does is create sockets and do fork()s and exec()s. It doesn't actually contain the network daemons. Those are external processes.

      That's "small parts" philosophy. inetd creates the socket and nothing more. The external processes for ftpd, fingerd, telnetd, identd, etc. do the actual work separately, with stdin/stdout being the socket.

  25. You see a hard drive format.... by toadlife · · Score: 1

    ...BSD users see cvsup, make *world, and mergemaster.

    --
    I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
  26. Lighten Up... by Saeed+al-Sahaf · · Score: 3, Insightful

    Oh come on. It's no more annoying than any of the many other trolls and LAME jokes here at Slashdot, and certainly LESS annoying than the Gay Nigger thing (and certainly less offensive). It's also less annoying than all the questionable "editing" that goes on here, what with all the dupes and crap stories. Learn to mentally filter out trolls and none of them will bother you, your blood pressure will be lower, and your quality of life will in general be higher. Just let it go, that's the price you pay for surfing a public forum.

    --
    "Who are in control, they are not in control of anything - they don't even control themselves!" - Glen Beck
  27. Re:*nix. What the hell does splat mean? by SirSlud · · Score: 3, Funny

    Yeah, I wouldn't use a car right now, because so many people use different makes and models that it all seems pointless. In the light 99% of them choosing the wrong model, I guess the right decision is not to use any of them at all!

    --
    "Old man yells at systemd"
  28. worse than that by r00t · · Score: 1

    It's not just the write cache. In fact, it's not
    that at all, because I stated that appropriate
    fence or flush operations are being used.

    Power is cut. The motherboard chips start to
    suffer a bit, corrupting data as it moves over
    the various busses. Meanwhile, the disk is doing
    just fine. Corrupt data arrives at the disk, and
    is stored as it arrives.

    Ouch. Bummer. What are you going to do? Cry?

    Really fancy filesystems tend to fall apart
    when they get corrupted a bit. Filesystems
    with less imaginative designs may be fixable.

    Perhaps you'd better checksum your data.
    Better yet, do like Google. Replicate your
    data at many different physical locations.
    (still with a checksum, just in case)

  29. Don't forget the other projects by fv · · Score: 4, Informative

    Google did bring in some $90000 worth of support through their Summer of Code project.

    Not to mention the remaining 1.91M they spent on other projects. FreeBSD just one of about 40 projects mentoring 400 students. The Nmap Security Scanner project is mentoring 10 of them, who have already produced great work! A list of their credentials and projects is available here. I'll give an update on their progress at my Defcon Presentation this Friday at 10AM.

    Meanwhile, many of the other SoC mentors have posted details on the projects being worked on. For example,

    Cheers,
    Fyodor @ Insecure.Org
  30. FreeBSD is the new Linux. by Anonymous Coward · · Score: 0

    I like to think of FreeBSD as starting to become what Linux could have if Linux hadn't fragmented into a million distributions that did nothing but squabble and spit at each other.

    Linux always went with flashy pointless features and many advocates became obsessed with it "taking the desktop" from Windows. I almost feel like Linux lost it's way as it could never shake off the inferiority complex about Windows having a larger install base.

    Meanwhile FreeBSD has felt no pressure to compete and has been moving in it's own direction in it's own time. As a result, using it feels more consistent, more of an integrated whole than a grab-bag jumble of distributions that all do things differently. Sure, this means that it's slightly more boring than Linux, but it also gets in the way slightly less. It's the OS of choice for many who just want to get on and do some work (or simply browse the web and write email) in a pleasant and mature Unix environment (which is even capable of running games - with the Linux translation layer it's even capable of running the Linux version of Unreal Tournament with full OpenGL acceleration).

    1. Re:FreeBSD is the new Linux. by Anonymous Coward · · Score: 0

      Actually Linux is much more powerful than FreeBSD is at this point.

      FreeBSD is more for hobbiest tinkerers and college kids than any serious enterprise computing.

    2. Re:FreeBSD is the new Linux. by Anne+Thwacks · · Score: 2, Interesting
      FreeBSD as starting to become what Linux could have ???

      Linux started life as a clone of BSD, because BSD had legal problems. Now you can have the real thing for free, why would you want the cheap imitation?

      --
      Sent from my ASR33 using ASCII
    3. Re:FreeBSD is the new Linux. by setagllib · · Score: 1

      Power isn't everything. Not all users need to scale to 128 processors linearly. A lot of users need to install, run, update and manage their systems as a single robust unit that will always work, and not have to decide between a few thousand distributions and always feel they're missing out on something. In FreeBSD, you get all of the FreeBSD generation you chose: you don't have to think "oh, but distribution X has ACL support out of the box, and gcc 3.4..." because FreeBSD 5/6 have them as highly tested standards.

      Some people want a powerful and consistent operating system, not just a powerful kernel. It's narrow minded to assume only hobbyists would want an easy-to-use and well documented system. This behavior is consistent with most Slashdot trolls.

      --
      Sam ty sig.
  31. 10 Million BSD Users Respectfully Disagree by Gary+W.+Longsine · · Score: 2, Insightful

    Silly Anonymous Coward Troll, stats are for ids.

    With an installed base up from zero five years ago to about 10 Millon today and with another million added each quarter, the users of Mac OS X as well as any real armchair operating system aficionados would be surprised to hear that *BSD is anything but alive and kicking. It's certainly growing faster than any Un*x has ever grown in the past, and has a larger installed user base than any *nix ever.

    Regarding the number of NetBSD posts to Usenet... good grief. This correlation can be easily explained by other factors. Most likely, NetBSD users are more mature both technically and emotionally, and don't participate in Usenet any longer. Perhaps they're too busy shipping gazillions of embedded devices to bother with a forum with such a poor signal to noise ratio as Usenet. They probably also have more education, drive nicer cars, and have 1.2 girlfriends (vs. 0.1 for the average AC Troll) .

    --
    If you mod me down, I shall become more powerful than you could possibly imagine.
    1. Re:10 Million BSD Users Respectfully Disagree by Anonymous Coward · · Score: 0

      You actually fell for that old troll? Jiminy Christmas!

    2. Re:10 Million BSD Users Respectfully Disagree by RLiegh · · Score: 1

      Only one problem; OS X isn't BSD, it's Mach.

    3. Re:10 Million BSD Users Respectfully Disagree by Anonymous Coward · · Score: 0

      im sorry but Mac OSX does not count as BSD.

      I hate that troll that the parent did. but Mac OSX is MacOSX not BSD.

      yes the core kernel shares a lot and is basically BSD but the total operating SYSTEM is not bsd. it is something else.

      radical differences do in fact make a new operating system

      still the gp was a troll no questions asked

    4. Re:10 Million BSD Users Respectfully Disagree by J.+Random+Luser · · Score: 1

      Don't worry sonny. you're allowed to display your ignorance on /. OS-X has indeed got a mach kernel, and the Darwin engine is the purest mongrel BSD, lots from Free- & -4.4Lite, and even some Apple wrote themselves. It's a free download from Apple, check it out and save yourself some blisters...

    5. Re:10 Million BSD Users Respectfully Disagree by RLiegh · · Score: 1

      >OS-X has indeed got a mach kernel,

      Exactly my point; the core part of the OS isn't BSD, it's mach. Various userland toys aren't relevent given the fact that the kernel is vastly different from every other BSD out there (right down to being a microkernel as opposed a monolithic one).

      And, unless you buy the GNU/Linux argument, calling this MACH-based OS "BSD" doesn't make a whole lot of sense. Particularly since a good deal of what's used to build Darwin is not BSD, but GNU (gcc, etc).

      Oh, and this is my preferred site for obtaining Darwin, kthxby.

    6. Re:10 Million BSD Users Respectfully Disagree by toadlife · · Score: 1

      And Mach was born out of BSD.

      Some history for you...

      (From this document.)
      "Mach's development followed an evolutionary path from BSD UNIX systems.
      Mach code was initially developed inside the 4.2 BSD kernel, with BSD
      kernel components being replaced by Mach components as the Mach componentswere
      completed. The BSD components were updated to 4.3 BSD when that
      became available. By 1986, the virtual memory and communication subsystems
      were running on the DEC VAX computer family, including multiprocessor
      versions of the VAX. Versions for the IBM RT/PC and for Sun 3 workstations
      followed shortly; 1987 saw the completion of the EncoreMultimax and Sequent
      Balance multiprocessor versions, including task and thread support, as well as
      the first official releases of the system, Release 0 and Release 1.
      Through Release 2, Mach provides compatibility with the corresponding
      BSD systems by including much of BSD's code in the kernel. The new features
      and capabilities of Mach make the kernels in these releases larger than the
      corresponding BSD kernels. Mach 3 (Figure B.1) moves the BSD code outside
      of the kernel, leaving a much smaller microkernel. This system implements
      only basic Mach features in the kernel; all UNIX-specific code has been evicted
      to run in user-mode servers. Excluding UNIX-specific code from the kernel
      allows replacement of BSD with another operating system or the simultaneous
      execution of multiple operating-system interfaces on top of the microkernel.
      In addition to BSD, user-mode implementations have been developed for DOS,
      the Macintosh operating system, and OSF/1. This approach has similarities to
      the virtual-machine concept, but the virtual machine is defined by software
      (the Mach kernel interface), rather than by hardware. As of Release 3.0, Mach
      became available on a wide variety of systems, including single-processor Sun,
      Intel, IBM, and DEC machines and multiprocessor DEC, Sequent, and Encore
      systems."

      --
      I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
    7. Re:10 Million BSD Users Respectfully Disagree by tigga · · Score: 1
      Exactly my point; the core part of the OS isn't BSD, it's mach.

      It's mutant, really ;)

      Read this blurb taken here http://www.apple.com/server/macosx/features/

      Darwin: Kernel and BSD

      Mac OS X Server starts with Darwin, the same open source foundation used in Mac OS X, Apple's operating system for desktop and mobile computers. Darwin is built around the Mach 3.0 microkernel, which provides features critical to server operations, such as fine-grained multi-threading, symmetric multiprocessing (SMP), protected memory, a unified buffer cache (UBC), 64-bit kernel services and system notifications. Darwin also includes the latest innovations from the open source BSD community, particularly the FreeBSD development community.

  32. Hidden Message..... by mr.snookie · · Score: 1

    So....Google's secret OS is going to be based off of FreeBSD?

  33. Re:*nix. What the hell does splat mean? by ArbitraryConstant · · Score: 1

    "And many of those burgers have multiple versions."

    An OS that doesn't have multiple versions is an OS that died before they could start fixing the bugs. All the survivors have huge numbers of releases.

    --
    I rarely criticize things I don't care about.
  34. Re:Yahoo dumps FreeBSD by linguae · · Score: 1
    it's official. BSD is dead.

    For the last time, BSD IS NOT DYING! Hotmail switched to Windows 2000 after MS has bought Hotmail because Microsoft needed to "eat its own dog food." I don't know why Yahoo is using Linux, though. But anyways, BSD isn't dying. Development is going strong, and each new release keeps getting better. BSD is a very capable and complete operating system.

  35. Re:Lighten Up... here-here by Anonymous Coward · · Score: 0

    Here-here. It's also much less anoying than the "In Soviet Russia" reports run FreeBSD or whatever comments....

  36. Re:Yahoo dumps FreeBSD by Anonymous Coward · · Score: 0, Troll

    Let's see; recently thigns were "going strong" for netbsd so much they had to beg for donations. OpenBSD is still feeling the fallout from the OSS community over Theo's bombastic remarks in Forbes and FreeBSD has just announced that they are abandoning the 5.x series (presumably in embarassment).

    In contrast, HP joins the ranks of luminaries such as Yahoo and IBM as members of the Linux community, drawn by both the quality of enterprise level support as well as the technicnological edge which Linux continues to display over the fragmented BSD camp (which has yet to come up with a fully functional SMP implementation).

    As far as capabilities go; BSD is not capable of journalling, SMP OR of maintaining any sort of prescence in the corporate IT infrastructure.

    Maybe because it's dying? Seems likely.

  37. Free? BSD by J.+Random+Luser · · Score: 1

    Surprising in view of the pleas in TFA for funding, and acknowledgements of where some came from, that nobody here sees a link between this and the true cost of software

  38. Re:Yahoo dumps FreeBSD by XNormal · · Score: 1

    Many hosting providers use FreeBSD and swear by it. I don't expect Pair networks, for example to change from FreeBSD anytime soon.

    --
    Stop worrying about the risks of nuclear power and start worrying about the risks of not using nuclear power.
  39. Requiem for the FUD by Anonymous Coward · · Score: 0
    // Please *don't* mod this up. It has already been done! Thx

    ... facts are facts. ;)

    FreeBSD:
    FreeBSD, Stealth-Growth Open Source Project (Jun 2004)
    "FreeBSD has dramatically increased its market penetration over the last year."
    Nearly 2.5 Million Active Sites running FreeBSD (Jun 2004)
    "[FreeBSD] has secured a strong foothold with the hosting community and continues to grow, gaining over a million hostnames and half a million active sites since July 2003."
    What's New in the FreeBSD Network Stack (Sep 2004)
    "FreeBSD can now route 1Mpps on a 2.8GHz Xeon whilst Linux can't do much more than 100kpps."

    NetBSD:
    NetBSD, for When Portability and Stability Matter (Oct 2004)
    NetBSD sets Internet2 Land Speed World Record (May 2004)
    NetBSD again sets Internet2 Land Speed World Record (Sep 2004)

    OpenBSD:
    OpenBSD Widens Its Scope (Nov 2004)
    Review: OpenBSD 3.6 shows steady improvement (Nov 2004)
    OpenSSH (OpenBSD subproject) has become a de facto Internet standard.

    *BSD in general:
    Deep study: The world's safest computing environment (Nov 2004)
    "The world's safest and most secure 24/7 online computing environment - operating system plus applications - is proving to be the Open Source platform of BSD (Berkeley Software Distribution) and the Mac OS X based on Darwin."
    BSD Success Stories (O'Reilly, 2004) (pdf) ~ from Onlamp BSD DevCenter
    "The BSDs - FreeBSD, OpenBSD, NetBSD, Darwin, and others - have earned a reputation for stability, security, performance, and ease of administration."
    ..and last but not least, we have the cutest mascot as well - undisputedly. ;)

    --
    Being able to read *other people's* source code is a nice thing, not a 'fundamental freedom'.

  40. Re:Yahoo dumps FreeBSD by tigga · · Score: 1
    Not much left for FreeBSD now that Yahoo is dropping it -- Yahoo switches to Linux.

    If you read article it does not say anything about switching from FreeBSD. Most of servers getting Linux are database servers - meaning Oracle etc. I believe losers there are Solaris and Windows.

  41. Re:Yahoo dumps FreeBSD by flynn_nrg · · Score: 1

    I don't usually reply to trolls, but I'm building world right now, so here we go...

    Moderators, the parent post is not informative at all. The BSDs have never been about hype or world domination. The OpenBSD developers make OpenBSD for their own use. If you like it you're free to use it. And the same goes for the other BSDs. So NetBSD got new machines thanks to donations. Guess what, the same thing has happened to Drupal recently, and I'd hardly call that project a failure.

    HP, IBM, SGI use Linux because they can actually save money by doing so. They sell hardware and services and, by embracing Linux, they save loads of cash on R&D and get geeks to like them. Look, IBM uses Linux, they're the good guys!

    You are so wrong about the status of the BSDs. Have you even taken a look at FreeBSD's SMP architecture? And, for your info, Scott Long is working on a journaling layer for FFS. The thing is, most people on BSD land care little about journaling because production BSD systems don't crash, they just chug along. One of the FreeBSD project's mail servers has a constant load of near 100 with very heavy disk i/o as well, and it just works .

    I don't know what world you live in, but I deploy OpenBSD firewalls and FreeBSD servers all the time, and people are very happy with them. Oh, and Juniper routers use the FreeBSD kernel. Must be pretty good if it drives some of biggest iron routers in the world.

    I have nothing against Linux and use it when it's the best tool for the job, but there's more in the freenix world than Linux distros. Give the BSDs a try, you might like them. For a quick test read the excellent OpenBSD man pages and then compare them to the ones included in your average Linux distro. That alone should show you the effort its developers put on technical excellence.

  42. Re:Yahoo dumps FreeBSD by Anonymous Coward · · Score: 0
    For what it's worth, I'm a "rent-a-temp" tech working at Yahoo as part of their Linux deployment. I have no idea what the ultimate goal is. I can tell you that Linux is being deployed on a *massive* scale here, at all levels. From what I can see, they are going to standardize on Linux for much (most?) of their infrastructure. I don't know if FreeBSD is going to be squeezed out completely, but it is obvious that it has assumed a secondary role.

    Yahoo has grown up, and I think they have started to realize that doing everything in-house is not always economically feasible. The way I see it, I suppose with Linux they can get vendor support to take care of more of the headaches. Just my 2 cents.

  43. 16 Million BSD Users Respectfully Disagree by Been+on+TV · · Score: 1

    Seem to remember from Apple's latest quarterly press conference they now have 16 million on OS X, and were growing at about 1.2 million for the last quarter.

    --
    The future is in beta
  44. Re:Yahoo dumps FreeBSD by setagllib · · Score: 2, Interesting

    Well, let's look at the big picture instead of the parts that interest you. FreeBSD is dropping 5.x because 6.x is of significantly higher quality, but their 'minimal surprise in incremental upgrades' policy requires a major version number change to accomodate the stable but new functionality. There is absolutely nothing wrong with this. It's a sign of positive growth and recovery from what some thought would be the death of FreeBSD (the less than impressive 5.3 release).

    Companies use Linux because it's a market horse, not because it's the best technical option. Remember: corporations want money. If they can lose some uptime but gain a lot of PR and friendliness with developer communities, they'll do it. I can't believe people don't see this yet. It's capitalism, not technological idealism. Deal with it and move on. Linux does have its uses on extremely high-end machines where super scalability is needed, but DragonFly BSD will move in over it in due time.

    BSDs are gaining journalling (DragonFly's work being particularly interesting and non-hackish), they all have SMP which is improving gradually (FBSD's system is becoming more fine grained, NetBSD will move to fine-grained locking in a major version or two, DragonFly is resolving the only remaining SMP-related issues and will thereafter receive more testing and acceptance, and I'm sure OpenBSD will move up later). If FreeBSD being one of the most present and reliable serving platforms noted by NetCraft itself is not a presence in corporate IT, what is? Are you telling me all of those sites are mom-n-pop stores that just happen to stay up for years and serve tremendous amounts of data? Not to say it compares with some of the things Linux is being used for these days: but it's definitely a presence it is unwise to ignore.

    It helps to know what you're talking about rather than just to listen to what a few Slashdot posts and articles say. If you really believe that everything you read is objective and do no hands-on investigation, you run the risk of ignoring really good options and thinking your mediocre software is a golden fleece of IT. Linux is cool, it has its uses, but it's still nowhere near the universal kernel it aims to be, and its efforts to stabilise and clean up won't work out until the development model changes and the code quality standard is raised. The BSDs' academic nature and elitism may slow progress, but at least the progress (usually) goes solidly. I can't speak for some of the things that FreeBSD has done in recent years, but DragonFly BSD and NetBSD seem to be progressing really well where they want to go (not necessarily where you might want them to go).

    --
    Sam ty sig.
  45. Launch.d Vs Rc.d by Goo.cc · · Score: 2, Interesting

    Personally, I am a little surprised that Launch.d is being ported to FreeBSD, as Luke Mewburn's rc.d is a very nice startup system. You can read more about rc.d here.

    1. Re:Launch.d Vs Rc.d by laffer1 · · Score: 1

      Look at the source code for the init process some time.. you might see why they are thinking about it. Luke's code was mostly shell scripting. Its nice, but its not a rehaul on init to get it caught up to current security and style coding practices. Unfortunetely, I doubt the replacement will be all that great either. I've had a lot of problems with lauchd on my mac so far.

  46. like this one : by DrSkwid · · Score: 1

    In Soviet Russia, FreeBSD trolls you !!

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  47. No hidden message at all by ccharles · · Score: 1

    There's very little evidence of a Google OS beyond the speculation of Google fanboys everywhere. I love them as much as the next guy, but this is just talk.

    Additionally, Google's SoC is supporting other OSes as well, notably Fedora Core, Ubuntu Linux and NetBSD.

    A complete list.

  48. Real Status of BSD by doublem · · Score: 1

    "I'm not dead yet!"

    --
    "Live Free or Die." Don't like it? Then keep out of the USA
  49. Re:Holy crap... no GPL legal hurdles by Anonymous Coward · · Score: 0

    BSD works and our company's legal department did not even hesitate to approve using BSD licensed code in our systems. Prior efforts to get GPL licensed code into our shop failed to get an approval from our legal department.

  50. Re:Yahoo dumps FreeBSD by Anonymous Coward · · Score: 0

    I think they have started to realize that doing everything in-house is not always economically feasible.

    The first sign of a dying company is when it starts "outsourcing" things that it used to do itself. Outsourcing is /always/ more expensive, and it shows that the company is mismanaged.

  51. I call BS by bluGill · · Score: 4, Informative

    I can't recall FreeBSD saying anything bad about shared libraries. Care to provide some proof?

    FreeBSD did not disparage journalled file systems. They said soft updates gave most of the advantages without the cost, and may be faster. For some workloads soft updates are better, for some they are not, but until FreeBSD implemented them nobody knew.

    FreeBSD was never against ELF. They just had no need - ELF solved some very real problems in the early versions of Linux, and because it was the standard when the linux developers went to fix those problems (back when linux was only a few years old) they went with ELF at the same time. FreeBSD did linking differently, and didn't have the problems early Linux did. The only reason FreeBSD now uses ELF is the GNU tools support ELF better. Otherwise the old FreeBSD a.out is just as good.

    IDE disk drives are still bad. However they are cheap so everyone uses them. (the advantages of SCSI are rarely seen on home machines. High end servers still use SCSI for good reason)

    I don't know where you got the idea that FreeBSD ever said anything against X.org, because they never did. The position is We don't care about what X server you run, but the X.org people seem like they might be more responsive to users, and that is a win, so we are going with X.org for all new versions. Because they are conservative about changes in general, they maintain XFree86 for old versions.

    1. Re:I call BS by Intron · · Score: 1

      "The only reason FreeBSD now uses ELF is the GNU tools support ELF better. Otherwise the old FreeBSD a.out is just as good."

      GNU tools don't support a.out well? They've had, what, 30 years to work on it? a.out didn't support dynamically loaded libraries. ELF appeared before and independently of linux to solve the problem (mid 80s?).

      Please add "freebsd pr machine" to your sig. You have earned the label.

      --
      Intron: the portion of DNA which expresses nothing useful.
    2. Re:I call BS by bluGill · · Score: 2, Informative

      Most of the GNU developers were using linux, with ELF. They were letting the a.out support get out of date. It was easier in the long run to switch to ELF (which was in general a good thing and the way forward, but not required for any technical reasons) than to keep maintaining a.out in the GNU tools along with the other FreeBSD changes.

      FreeBSD supported dynamically loaded libraries in a.out.

      I never implied that ELF was developed by Linux. The linux developers could have solved their shared library problems (which were a mess back when linux was just a couple years old) in a.out. However they made the decision (correctly) to solve the problem as part of moving to ELF because ELF was the way they wanted to go in the long run anyway.

  52. K kernel meta langauage by njyoder · · Score: 1

    Is it just me or does this look like it's trying to implement a bunch of features on top of C for which standard C++ would be sufficient? They want an ingrained list type? Then, uh, use "list" in C++. I didn't look at it in detail, but from what I saw they could just use C++.

    Unfortunately there seems to be some fun anti-C++ sentiment among many OSS developers, especially core developers who would probably say "ZOMG BLOAT WTFLOLOLZ." Of course, any remotely legitimate complaints could be addressed just by making your own kernel libs, which is already done with their C language counter-parts anyawy.

    1. Re:K kernel meta langauage by setagllib · · Score: 1

      ...Are you sure you typed that all at once? It doesn't make logical sense.

      Implementing kernel features in C++ requires ABI changes and extern"C" de-mangling and all kinds of hackish crap which would make the code and build processs messier, not cleaner. Writing some storage primitives to share around the kernel would (hopefully) clean it up instead.

      BSDs are known for their cleanliness. While a fully C++ kernel could conceivably be good and clean, it adds little real value since the interface between kernel and userland can not be object oriented (it's not any real language - system call vectors bridge the gap between memory spaces and don't particularly care about language), and while inheritance might be just great for writing cleaner drivers or something, there hasn't been a significant need. And writing a brand new kernel from the ground up in this day and age would be way too much work - most projects these days are forks.

      --
      Sam ty sig.
    2. Re:K kernel meta langauage by njyoder · · Score: 1

      Implementing kernel features in C++ requires ABI changes and extern"C" de-mangling and all kinds of hackish crap which would make the code and build processs messier, not cleaner.

      "Extra work? We'd rather think in the short term!"

      BSDs are known for their cleanliness.

      No, they are most definitely not. Have you taken a look at the kernel code? It's already ugly as hell with all kinds of macros and ugly hacks. That's not to mention absolutely horrible single-letter variable naming conventions. So many basic style rules are violated it's not funny.

      While a fully C++ kernel could conceivably be good and clean, it adds little real value since the interface between kernel and userland can not be object oriented

      Making a kernel more easy to read and maintain adds little real value?! There's a lot more to the kernel than interfacing with userland, in case you didn't know.

      while inheritance might be just great for writing cleaner drivers or something, there hasn't been a significant need.

      Ok, this phrase here just set off alarm bells. The fact that you just described C++ exclusively in terms of inheritance means you don't even know C++.

      First of all, C++ is not just an OO language and to dscribe it in terms of inheritance is extroadinarily ignorant. If you take a look at the features that K implements, for example, you'd note that they would be implemented with completely different features like templates and operator overloads.

      Second of all, the kernel is already heavily OO and uses C based hacks for "inheritance" as you call it. Kludge, kludge, kludge.

      And writing a brand new kernel from the ground up in this day and age would be way too much work - most projects these days are forks.

      There comes a time when you need to start doing major rewrites. You can't just use the same old code forever. The idea of using old ass design and style methods for decades to come is appalling.

    3. Re:K kernel meta langauage by Anonymous Coward · · Score: 0

      Inheritance already exists at the kernel level. For example, sockets, files, directories, pipes, FIFOs, and devices all inherit from the "file" class.

      It is not done with C++. It is does with plain C structs that contain function pointers for "methods." You can do various really simple tricks to simulate single-object inheritence, and if you really wanted to, you could hack together multiple inheritance.

      You don't need to use C++ to do object orientation in a C program. Kernels are a good example of doing this. Gtk+ and GLIB are another.

      Remember. The first C++ compilers generated C code. OO in C is quite possible, and in practice very managable.

  53. BSD/linux/?/OpenSource by Anonymous Coward · · Score: 0

    bsd has some cool things. Ports KFA (Kick Fu&&& As). pkg_add is awsome. Linux is a little more hackable. Solaris as my unix mentor put it: "it's good because it has stock holders to report to, so it can only start to suck so much before it/company fials". However throught all of this I would like to know a an inteligent reason why on earth most (if not all) software is not open source, not nescosarily any particular licence. And I'd also like to know why hardware is not mandated to be open sourse. I meen think about it No specs meens hard to support, say if your in a shop and need to replace a battery or what not.