Slashdot Mirror


FreeBSD Looks Ahead to 6.0

I was catching up on mailing list archives when I came across an announcement from Scott Long of FreeBSD's release engineering team, noting that after the rather substantial amount of time that it took to take FreeBSD 5 to a -STABLE designation, their release schedule will be speeding up in the future. With the official release of FreeBSD 5.3 coming Real Soon Now, a new branch for 6.0 is now tentatively scheduled for mid-2005. It would seem that while the version numbers may increase more rapidly, so will the rate at which new features are merged from -CURRENT, so end users can get new features faster.

68 comments

  1. first positive post by Anonymous Coward · · Score: 2, Insightful

    BSD lives!

    1. Re:first positive post by Anonymous Coward · · Score: 1, Funny

      Correction, BSD is undead.

    2. Re:first positive post by ulib · · Score: 1
      Ugh.. am I the only one tired of reading this crap?

      Is there some way to rise the moderators' standard for "fun"? :)

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

    3. Re:first positive post by YU+Nicks+NE+Way · · Score: 2, Funny

      No, it's double-plus undead.

  2. RTFA -- It's Quite Interesting by akpoff · · Score: 5, Insightful
    1. Move to a timeline-based release cycle rather than feature-based.
    2. Development of major features in Perforce. The goal is to keep the head branch from going unstable very often and allows major features to stay under development if it isn't ready for -STABLE branch point. Appears CVS will still be used for the main tree.
    3. Frequent scheduled releases will keep the bug count under control.
    4. Current plan is to branch for 6-STABLE in the May/June 2005 time frame with 6.1/.2 etc in 4-6 month intervals thereafter.
    Two very big, interesting changes. Given the very usable ports tree moving to scheduled releases for the core system makes a lot of sense. The decision to move development of major features out of the main CVS tree compliments the scheduled-release strategy. If anyone can make it work it'll be the FreeBSD team.

    Congratulations on achieving 5-STABLE and best wishes on 6-CURRENT development!

    1. Re:RTFA -- It's Quite Interesting by Anonymous Coward · · Score: 0

      There are two things I'd like to point out.

      IMHO calling it -STABLE is a disservice to the users community, specially considering the huge TO-DO list of bugs and problems that should have been fixed before calling it -RELEASE.

      Second, there's the issue of perforce development. This is still a problem when some people keep private p4 repos and don't commit to CVS for months. Some people have suggested looking at svn and arch. A free software project shouldn't rely on perforce for its development.

      --
      HawkinsOS, enterprise ready, today.

    2. Re:RTFA -- It's Quite Interesting by ulib · · Score: 4, Interesting

      TFA is really worth reading. And, as you say, moving to scheduled releases is a very good idea: even if 4.10 for production use is still very good in most cases, I think users are going to appreciate releases at more regular intervals.
      For all that they've done and all that they'll do, kudos to the FreeBSD team!
      --
      Being able to read *other people's* source code is a nice thing, not a 'fundamental freedom'.

  3. *cough* I meant "raise". [nt] by ulib · · Score: 1

    [nt]

  4. time-based releases a bad-thing(tm)? by CaptainPinko · · Score: 3, Insightful

    With feature based release you get the pressure to get things done because everyone is waiting for you. I'm worried that with time-based releases a lot of features will languish with tweaking or becoming more and more ambitious and they'll never get finished to be merge since there is no pressure. I'd rather see feature-based for at least one majour feature in a release. In other words keep it feature-based but bite off only a little (and not more than chew) and aim for that bite to be doable in 9-13 months (to leave for debugging, testing, etc.).

    --
    Your CPU is not doing anything else, at least do something.
    1. Re:time-based releases a bad-thing(tm)? by ArbitraryConstant · · Score: 4, Informative

      That could potentially be an issue, but it's also possible for a group of developers to work on their own branch, bringing in changes from CURRENT from time to time. SMP on OpenBSD took longer than the 6-month release interval, so there was a seperate SMP branch until the work was close enough to completion to make it into a release.

      --
      I rarely criticize things I don't care about.
    2. Re:time-based releases a bad-thing(tm)? by archen · · Score: 2

      I think that even of you only a "few" features you run the risk of having something not work out and still missing the time schedule (as the DragonFly BSD guys said about SMP in FreeBSD). This isn't neccesarily the end of the world - it's just a schedule and they can always change it back so I'm willing to see how this all goes.

      I think they want to avoid what happened to 5x stable. Many people like me have had all the features we need in 5x for a long time, but they keep pushing off 'stable' because of some new tweak. This time schedule may allow for development to continue at the same rate, while getting the userbase fresh releases with bugfixes and improvements.

    3. Re:time-based releases a bad-thing(tm)? by Eivind+Eklund · · Score: 3, Interesting
      I'm a FreeBSD developer.

      Our experience, after doing this for 10 years (I personally have been a developer for 7.5 years) is that we get serious problems whenever we try to go feature based, because we get wrong priorities, and it end up with releases taking too long and there being less feature development overall.

      This is why we want to switch back to a time based release cycle. We have had long discussions about this (there have been hundreds of messages debating various issues around it), and the overall result is that we believe things get better in close to every way with time based releases, based on what happens in practice.

      As we introduce fairly major features reasonably often, there will be major features introduced to releases. We just stop promising major features that are not yet implemented in a particular release. If there were nothing major new, we wouldn't bother with the work of cutting a new -stable branch.

      Eivind.

      --
      Doubting the existence of evolution is like doubting the existence of China: It just shows that you're uninformed.
  5. The Other BSD? by Anonymous Coward · · Score: 1

    This model seems similar to the one used by OpenBSD. It seems to have worked very well for OpenBSD; Hopefully the FreeBSD team will have similar results.

    I use FreeBSD heavily in my environment, and have been stuck on 4.x while waiting for some of the 5.x features (mainly UFS2's spiffy snapshots. While not has fast as WAFL's, still spiffy).

    I also use a pair of OpenBSD boxen as my firewall cluster. I have to say from an end user standpoint, I am far more pleased with the OpenBSD release cycle. I know in 6 months there will be a new rock solid stable release, so I can plan accordingly.

    From a purely PHB POV, IMO having published firm release cycles can help push OSS into the corporate world. Commercial software claims to have this advantage already, but just look at Longhorn and Solaris 10...

  6. MFCed?! by CaptainPinko · · Score: 1

    what does mean? anyone? does this mean that 5.4 will be released shortly after 5.3 or that a patch will appear or that...?

    --
    Your CPU is not doing anything else, at least do something.
    1. Re:MFCed?! by compass46 · · Score: 3, Informative

      MFCed stands for "Merged From Current". It means that something from -CURRENT was backported to -STABLE. For example, if bugs are found in something while working on FreeBSD-6 and they exist in FreeBSD-5, the fixes from FreeBSD-6 might be MFCed to fix the problem in FreeBSD-5.

  7. The quick answer. by ulib · · Score: 2
    I know, I know.. one shouldn't judge things solely on the basis of who's saying them.
    ..But do you know who you're listening to?
    "sold nearly 2,000 copies of my beta system"..
    "remove assholes like x and y from the team".. "I made money off *my* work"..
    "it's not usable in a production environment, not without my patches"..
    "they won't be getting my patches unless I see public apology from a and b"..
    ..Does this ring a bell??.. :-DDD

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

    1. Re:The quick answer. by DashEvil · · Score: 3, Informative

      I think there was a typo in your post.

      Surely you meant "Operating systems copied and rebranded by T. Hawkins: 1".

      --
      -If God wanted people to be better than me, he would have made them that way.
    2. Re:The quick answer. by Anonymous Coward · · Score: 0

      HawkinsOS is not the first OS project I've worked on. I wrote a full embedded operating system for vme mc68000 boards.

      The unified diff file between FreeBSD 5.3 and HawkinsOS is 7MiB big.

      --
      HawkinsOS, kicking Smorgrav in the ass since 2004.

    3. Re:The quick answer. by Anonymous Coward · · Score: 0
      The unified diff file between FreeBSD 5.3 and HawkinsOS is 7MiB big.

      What is MiB?
      "MicroBytes"? :-DDD

    4. Re:The quick answer. by Anonymous Coward · · Score: 0

      Take your time to study SI units

      And now go back to your proprietary GNU/Debina system. That is, if you can even find your way out of a paper bag when it comes to writing code. Oh wait, you can't even write a Hello, World. program.

      --
      HawkinsOS: kicking Smorgrav in the ass since 2004.

    5. Re:The quick answer. by DashEvil · · Score: 2

      Where can you find the source for this OS (the embedded one), I wouldn't mind having a look at your 1337 coding skillz, since I've not seen a single line you've written yet.

      --
      -If God wanted people to be better than me, he would have made them that way.
    6. Re:The quick answer. by Anonymous Coward · · Score: 0
      >Take your time to study SI units

      Ok, ok!.. You actually said something that remotely makes sense. I wasn't ready for that!

      ..now you can go back to your "Fortune 100" customers. :-D

    7. Re:The quick answer. by Anonymous Coward · · Score: 0


      Mr. Hawkins,

      I'm one of your several Fortune 100 customers.

      I know you enjoy trolling on slashdot, but we kinda need some assistance here.
      We deemed you trustworthy enough to make our Fortune 100 company migrate to your OS - a decision that has been very easy for us to make, since you're such a reliable person and such a skillful programmer - but enough is enough.
      We paid you a lot of money. I have no doubt that *your* HawkinsOS is worth every penny, and that these BSD alternatives are just pieces of junk since they don't have your "patches", but now it's time to come back to work.
      Sincerely,

      Mr. Joe Moron
      HawkinsOS user
      Fortune 100 company CEO

    8. Re:The quick answer. by Anonymous Coward · · Score: 0

      Mr. Hawkins,

      I'm one of your several Fortune 100 customers .

      I know you enjoy trolling on slashdot, but we kinda need some assistance here.
      We deemed you trustworthy enough to make our Fortune 100 company migrate to your OS - a decision that has been very easy for us to make, since you're such a reliable person and such a skillful programmer - but enough is enough.
      We paid you a lot of money. I have no doubt that *your* HawkinsOS is worth every penny, and that these BSD alternatives are just pieces of junk since they don't have your "patches", but now it's time to come back to work.
      Sincerely,

      Mr. Joe Moron
      HawkinsOS user
      Fortune 100 company CEO

    9. Re:The quick answer. by Brandybuck · · Score: 1

      He'll only give it to you if your apologize first.

      --
      Don't blame me, I didn't vote for either of them!
  8. ATTN Mr. Hawkins - your eyes only by Anonymous Coward · · Score: 0

    Mr. Hawkins,

    I'm one of your 2.000 customers.
    I know you enjoy trolling on slashdot, but we kinda need some assistance here.
    We deemed you trustworthy enough to buy 2.000 copies of your *beta* system - a decision that has been very easy for us to make, since you're such a reliable person and such a skillful programmer - but enough is enough.
    We paid you a lot of money. I have no doubt that *your* HawkinsOS is worth every penny, and that these BSD alternatives are just pieces of junk since they don't have your "patches", but now it's time to come back to work.
    Sincerely,

    Mr. Joe Moron
    HawkinsOS user

  9. Re:bsd roxorz by Anonymous Coward · · Score: 0

    Who modded this cheap copy & paste up?

    For your info, the original article was by Paul Webb, and it was pulled because it contains lots of factual errors. It's a troll, mod down.

    --
    HawkinsOS, for the BSD hacker in you.

  10. Private message for Mr. Hawkins by Anonymous Coward · · Score: 0

    Mr. Hawkins,

    I'm one of your 2.000 customers.
    I know you enjoy trolling on slashdot, but we kinda need some assistance here.
    We deemed you trustworthy enough to buy 2.000 copies of your *beta* system - a decision that has been very easy for us to make, since you're such a reliable person and such a skillful programmer - but enough is enough.
    We paid you a lot of money. I have no doubt that *your* HawkinsOS is worth every penny, and that these BSD alternatives are just pieces of junk since they don't have your "patches", but now it's time to come back to work.
    Sincerely,

    Mr. Joe Moron
    HawkinsOS user

    1. Re:Private message for Mr. Hawkins by gtoomey · · Score: 3, Insightful

      At the risk of damaging my karma, any post promoting HawkinsOS is a troll.

    2. Re:Private message for Mr. Hawkins by ValiantSoul · · Score: 0, Flamebait

      You F$*! A@! HOLE! Why do you insist on lying to people and why the F*!@ would anyone want to pay for some S*%$ like yours when they could get the EXACT SAME THING for FREE LEGALLY! Please /. admins, ban any post with "HawkinsOS" AKA S*!@%yOSMadeByADumbA*#GuyCravingAttention. Grow up

  11. Re:gvinum still broken by Bishop · · Score: 0, Offtopic

    HawkinsOS, for the adult in you.

    Oh the irony. Your post is nothing but a childish cheap shot.

  12. Time Based releases work by Anonymous Coward · · Score: 2, Interesting

    OpenBSD already does this and it shows. Things get introduced into the tree and gradually grow to perfection between releases, with snapshots regularly giving users a chance to test and give feedback. Theo gets angry if the current tree won't compile for more than 20 minutes.

    It allows gradual changes to happen, I can only remember one "flag day" when the binaries went from a.out to ELF format. Everything else has been pretty gradual. I happen to like installing snapshots, and have found them to be pretty stable, stable as a rock in my experience.

    Kudos to FreeBSD for going this route. It will mean wider exposure. The one problem is regular upgrades and supporting past releases. If it took 4 years to get 5 ready for stable, in that time OpenBSD has had 8 releases (one every 6 months). Noone has the resources to support all the old releases, so they only support the past two releases.

    Now if all the *BSDs will continue to cooperate, and maybe spread the release dates out so each can share in the publicity we can have a release each quarter. Of course I didn't notice the schedule of release dates, maybe FreeBSD will choose to release every 9 months, or 72 weeks or biennially or whatever.

    1. Re:Time Based releases work by Anonymous Coward · · Score: 0

      OpenBSD's development model is a bit different. For example, snapshots of current are created every other week or so, and those usually work fine. FreeBSD 5.x has gone broken for almost 1 month at times. They make more evolutionary changes (yes, the switch to ELF was the exception). All the development is done in CVS, no hidden perforce repositories that cannot be accessed by anyone but the coder himself.

      FreeBSD 5-STABLE is 2 years late and has about 30 serious bugs that need to be fixed. This is the price to pay for being too arrogant. But remember, Matt Dillon warned you about it almost 2 years ago.

      --
      HawkinsOS, FreeBSD 5.3 without the bugs.

  13. FreeBSD 5.3 RELEASE Released by Vividdream · · Score: 1

    The FreeBSD 5.3 RELEASE version looks like it just came out this morning and is being mirrored accross the FreeBSD FTP servers at the following address:
    http://www.freebsd.org/doc/en_US.ISO8859-1/books/h andbook/mirrors-ftp.html
    I have already downloaded and installed it. In addition, I set up a BitTorrent tracker for 5.3-RELEASE-i386-disc1.iso temporarily at the following URL:
    http://209.6.188.15:6969/

    1. Re:FreeBSD 5.3 RELEASE Released by Anonymous Coward · · Score: 0

      Mr. Hawkins,

      I'm one of your 2.000 customers.
      I know you enjoy trolling on slashdot, but we kinda need some assistance here.
      We deemed you trustworthy enough to buy 2.000 copies of your *beta* system - a decision that has been very easy for us to make, since you're such a reliable person and such a skillful programmer - but enough is enough.
      We paid you a lot of money. I have no doubt that *your* HawkinsOS is worth every penny, and that these BSD alternatives are just pieces of junk since they don't have your "patches", but now it's time to come back to work.
      Sincerely,

      Mr. Joe Moron
      HawkinsOS user

    2. Re:FreeBSD 5.3 RELEASE Released by Anonymous Coward · · Score: 0

      Stop pasting that crap. And you must be one of those smelly spics, since you can't even tell a comma from a period. It's 2,000.

      Now go back to your usual trolling in the FreeBSD mailing lists. Yes, I do know you're that AOL guy.

      --
      HawkinsOS, what FreeBSD could have been.

    3. Re:FreeBSD 5.3 RELEASE Released by Anonymous Coward · · Score: 0

      > > I'm one of your 2.000 customers.

      > And you must be one of those smelly spics, since you can't even tell a comma from a period. It's 2,000

      Two thousand is officially written as "2.000" in many "spic" countries, so it's not that they "can't tell a comma from a period." They officially use them differently.

    4. Re:FreeBSD 5.3 RELEASE Released by Anonymous Coward · · Score: 0

      That was indeed the reason why I 'slipped'. It's the official convention in almost all the Euro zone. But given the international ("intercontinental") context, I should have used "2,000". ;)

    5. Re:FreeBSD 5.3 RELEASE Released by cperciva · · Score: 1

      In addition, I set up a BitTorrent tracker for 5.3-RELEASE-i386-disc1.iso temporarily

      The 5.3-RELEASE announcement will include the location of official BitTorrent trackers for the iso images, so this isn't necessary.

      To everyone trying to get an early copy of the iso: Slow down, wait for the signed announcement, and check the MD5 hashes. I have no reason to think that Vividdream is doing anything evil, but this wouldn't be the first time that trojans were circulated in advance of an official release...

    6. Re:FreeBSD 5.3 RELEASE Released by cpugeniusmv · · Score: 1

      Official Release Announcement

      Bittorrent Downloads

      For ftp mirrors, see announcement.

    7. Re:FreeBSD 5.3 RELEASE Released by Anonymous Coward · · Score: 0

      Mr. Hawkins,

      I'm one of your 2.000 customers.
      I know you enjoy trolling on slashdot, but we kinda need some assistance here.
      We deemed you trustworthy enough to buy 2.000 copies of your *beta* system - a decision that has been very easy for us to make, since you're such a reliable person and such a skillful programmer - but enough is enough.
      We paid you a lot of money. I have no doubt that *your* HawkinsOS is worth every penny, and that these BSD alternatives are just pieces of junk since they don't have your "patches", but now it's time to come back to work.
      Sincerely,

      Mr. Joe Moron
      HawkinsOS user

  14. Private message for Mr. Hawkins by Anonymous Coward · · Score: 1

    Mr. Hawkins,

    I'm one of your 2.000 customers.
    I know you enjoy trolling on slashdot, but we kinda need some assistance here.
    We deemed you trustworthy enough to buy 2.000 copies of your *beta* system - a decision that has been very easy for us to make, since you're such a reliable person and such a skillful programmer - but enough is enough.
    We paid you a lot of money. I have no doubt that *your* HawkinsOS is worth every penny, and that these BSD alternatives are just pieces of junk since they don't have your "patches", but now it's time to come back to work.
    Sincerely,

    Mr. Joe Moron
    HawkinsOS user

  15. Re:gvinum still broken by Anonymous Coward · · Score: 0

    Does RAID-1 work though? Coz that's all I need....

  16. Re:gvinum still broken by Brandybuck · · Score: 1

    HawkinsOS, for the petulant child in you.

    --
    Don't blame me, I didn't vote for either of them!
  17. Re:gvinum still broken by Anonymous Coward · · Score: 0

    If all you need is RAID-1 one you might just use ccd(4) or gmirror(8).

    --
    HawkinsOS: kicking Smorgrav in the ass since 2004.

  18. Re:gvinum still broken by Anonymous Coward · · Score: 0

    HawkingOS?

    Hawking: To peddle goods aggressively, especially by calling out.

    HawkinSOS?

    SOS: a distress call
    SOS: Sack Of Stuff (polite form)
    SOS: Same Old Story
    SOS: Same Old Stuff (polite form)
    Take your pick...
  19. Re:*cough* I meant "raise". [nt] by Anonymous Coward · · Score: 0

    I bet these kind of mistakes keep you up at night.

  20. Kudos by molnarcs · · Score: 4, Interesting
    I just want to express my deep respect for FreeBSD developers. All the hype is around linux these days, and rightly so: it is a wonderful system. But few know that there are now ~100 paid developers working on linux (which is 'just' a kernel) at any given time, while there are none in FreeBSD. Yes, yes, PHK now is payed to do FreeBSD-only development for 8-10 months. There are others who receive either support from their employers to work on FreeBSD part-time, or some grants or others, but all in all, the FreeBSD project has 1/100 of the resources linux has.

    Of course, I realize that from a user/technical standpoint, this means nothing. But there are too many trolls out here who are bent on conducting a smear campaign against FreeBSD developers, going even as far as to question their programming skills. Now think about this: these developers have kept up with the pace linux development dictates with 1/100 of the resources linux development has. It is still one of the most reliable operating systems out there, no matter what disgruntled HawkinsOS guys will tell you about FreeBSD not being 'enterprise ready.' In fact, if you check netcraft's monthly reports about the most reliable sites, 4-5 sites from the top 10 is always running FreeBSD. In october, the top three sites having the fewest failed requests all ran FreeBSD (the 4th is Net~ or Open~).

    So I just can't emphasize enough how impressed I am (as a desktop user btw) with the work of these guys. And now this announcment! Excellent ideas there! And I hope to see ULE allowed in -STABLE again soon :))) (did I say I was a desktop user?).

    Thanks guys ... for everything!

    1. Re:Kudos by archen · · Score: 5, Insightful

      Now think about this: these developers have kept up with the pace linux development dictates with 1/100 of the resources linux development has.

      That sort of depends on what you mean by resources. An interesting thing was said by one of the DragonFly BSD guys, in that their development moved much more quickly because there weren't as many people involved in the project (as in FreeBSD). It's not neccesarily the size of the team, but the quality and how well they work together. Once you reach a criticle mass for a given team, you end up losing more and more productivity to human overhead as people are added.

      I think Linux may start to feel unnessesary pressure due to corperate interests - which might slow things down more than advance them.

    2. Re:Kudos by molnarcs · · Score: 2, Interesting
      Yeah, you might be right, I haven't thought of that from this perspective. Still, a bit more resources (necessary hardware for testing/writing drivers, at least a handful of developers working full time on FreeBSD wouldn't hurt :)).

      One thing they should do is to update the Foundations website. Advertise. Make donating easier and more compelling. An outdated website is not a good incentive to contribute. The best thing would be if they could achieve steady funding. I'm just a student, and my monthly budget is 76000HUF (~380$). Hungary is cheap, so that's OK, but it isn't much (it just covers my monthly expenses, it is not enough to save up), yet I think I could afford a monthly 5$ to help them. But I would only do that if I saw a very well organized 'campaign' to do that. A professional, easy to use website, specific goals (target amount for each month), way to track it, publicity, publicity, publicity. I think it would even be worth for the project to pay someone to organize this (let's say he or she would get x% of the income). I also think that income should be calculable.

      In other words, this 'campaign' (I'm looking for a better expression, english is not my native language!) should focus on getting to those who are willing to contribute (even very small amounts, like 5$) for a set amount of time (6-12-x months) - thus to make the 'income' as a said, predictable.

      Just an idea...

    3. Re:Kudos by Anonymovs+Coward · · Score: 1
      It is still one of the most reliable operating systems out there, no matter what disgruntled HawkinsOS guys

      HawkinsOS "guys"? It's one single disgruntled troll: please don't give him any importance or publicity.

  21. Re:gvinum still broken by Brandybuck · · Score: 2, Informative

    How many enterprise ready operating systems have you written?

    And I see that you've written *none*! All you've done is take FreeBSD and tweak it bit here and there. That is a much different thing from writing an operating system.

    Maybe my only claim to fame is homebrewing software (not counting the real time embedded systems software I do at work), but at least I'm secure enough not to feel the need to engage in casting puerile aspersions at my competitors.

    An error occurred while loading http://www.hawkinsos.com/

    I was going to look up what "several fortune 100 companies" were using HawkinsOS, but apparently the demand is so high it's swamped your server.

    --
    Don't blame me, I didn't vote for either of them!
  22. Perforce by Rubel · · Score: 2, Insightful

    Perforce is stable, fast, and well-tested. I don't see how using a great tool is a handicap, even for an open-source project.

  23. Re:gvinum still broken by R.Caley · · Score: 1
    Several fortune 100 companies have already migrated from FreeBSD to HawkinsOS.

    Someone should submit this as a full /. story,

    Anonymous Coward creates patch set for English which extends the `several' quantifier to cover the case of `0', but refuses to release it to the world because no one adopted his previous patch redefining `sad obsessive git' to mean `Emporer of the Internet with a Huge Cock'.

    BTW, what is the point of hiding behind AC but always posting the same paranoid drivel?

    --
    _O_
    .|<
    The named which can be named is not the true named
  24. Re:bsd roxorz by Anonymous Coward · · Score: 0

    Mr. Hawkins,

    I'm one of your several Fortune 100 customers.

    I know you enjoy trolling on slashdot, but we kind of need some assistance here.
    We deemed you trustworthy enough to make our Fortune 100 company migrate to your OS - a decision that has been very easy for us to make, since you're such a reliable person and such a skillful programmer - but enough is enough.
    We paid you a lot of money. I have no doubt that *your* HawkinsOS is worth every penny, and that these BSD alternatives are just pieces of junk since they don't have your "patches", but now it's time to come back to work.
    Sincerely,

    Mr. Joe Moron
    HawkinsOS user
    Fortune 100 company CEO

  25. Re:gvinum still broken by Chreo · · Score: 3, Informative

    You're getting rather pathetic... 1) Gvinum works and the RAID5 bug have been fixed in 5-STABLE stoopido! Anyone who is advanced anough to use RAID5 and vinum knows how to fix this issue by updating to latest 5-STABLE! 2) ULE patches are available that fixes things as well. If you feel the need to use ULE just grab'em or wait until ULE is MFC'd. Now please be so kind to eat shit or release those patches that you "claim" to have. If you even have anything... In your case, seeing is believing and we ain't seen nothing but whining yet from you. So either you put up or you STFU!

    --

    Life is what happened when Good Intentions met Harsh Reality (the brother of the more infamous Chaos).
  26. sendto() still broken by jaredmauch · · Score: 1
    I'm more concerned about basic socket operations bugs that haven't been resolved yet.. Example PR/26506 which impacts anyone who attempts to use snmp utilities inside a Jail. This means you can't use mrtg, or something else similar..

    This one has been impacting me for quite some time.

    1. Re:sendto() still broken by Anonymous Coward · · Score: 0

      Maybe you should try DragonFlyBSD. It's a better FreeBSD, with better networking people working on it.

    2. Re:sendto() still broken by jaredmauch · · Score: 1

      I'd much rather not have to reinstall my system more than once in a year. my prefered solution is to have sendto() work correctly from inside a jail.

  27. Re:gvinum still broken by R.Caley · · Score: 1
    I was going to look up what "several fortune 100 companies" were using HawkinsOS,[...]

    I presume he took the web site down before he posted for exactly that reason. The web site admits this supposed OS doesn't exist. ``under development'', ``release delayed'' etc.

    The action packed ``community'' area of his site is worth a visit too. All those beta testers exchanging knowlegable comments...

    --
    _O_
    .|<
    The named which can be named is not the true named