Slashdot Mirror


ekkoBSD Officially Dead

sniperu writes "The EkkoBSD team leader announced the project's premature death , only 12 days after their latest release . No clue is given about the causes of such an unespected end other than saying "It's been a stressful fun trip" . You can still get the last release from the downloads page . Get it while you can ."

9 of 69 comments (clear)

  1. heh.. by Anonymous Coward · · Score: 4, Funny

    This is the trolling equivalent of pouring blood in shark-infested waters. *shudder*

  2. Re:inthe know by iggymanz · · Score: 4, Informative

    it was forked from OpenBSD 3.x (twice actually, first from 3.0 then 3.3) the idea was to make a easy gui based admin & install BSD oh well, still plenty of free / open / closed /proprietary BSD flavors to choose from that are very much alive and growing. The idea of an easier admin/install is very good & would help attract new users. Sure, an experienced person could whip out a configured machine in under 15 minutes for any flavor of BSD, but there's alot of confusing stuff for a newbie.

  3. How mysterious...and expected. by RLiegh · · Score: 2, Informative

    I tried ekkobsd and for my tastes, it was indistinguishable from regular openbsd. From the get-go it seemed as though there was no real compelling reason for this distribution to exist (aside from itch scratching, of course).

    However, I do wish the ekko project members success in their future endevours.

  4. Does this surprise anyone? by Anonymous Coward · · Score: 5, Interesting

    ekkoBSD was the idea of a guy named Rick Collette... now if you spend a little time googling that name you'll see that this guy has had his named attached to a few failed linux distributions. And on the ekkobsd.org webpage he even says: "Rick Collette - I actually only provided the Intel hardware, colo, marketing, path to completion, etc. I didn't do any coding at all - so my involvement was strictly in starting and attempting to guide the project. " the Operative word here is "didn't do any coding at all" This guy is a about as close to human hot air balloon as it gets. He starts up some project, makes a lot of noise, doesn't do a damn thing except get other people to do the work for him. This is just another failed attempt for this guy. Perhaps he'll learn to stop trying to make poor ripoff's of existing operating systems and wasting peoples time.

    Some choice urls:
    http://linuxpr.com/releases/1319.html
    http ://lwn.net/2000/0323/a/deeplinux.html

    Ever heard of SPIROlinux? DeepLinux? Same guy, same story.

  5. Re:Examining this FreeBSD train wreck by aphor · · Score: 2, Insightful

    Totally devoid of any knowledge which might help me validate the truth of anything in this flame, I can distill a claim from this piece which has universal value: egotism is a problem. Actually, I do remember JKH commenting on the FreeBSD experience in an interview that followed him taking the Apple job. He said that much of his energy in his most recent FreeBSD memory was spent refereeing egotistical contributors.

    The real lesson to be drawn from this is that the FreeBSD code base effectively, systematically, inflates the egos of some programmers. This is a real and biting criticism of the FreeBSD project, and I say this as an ardent fan of FreeBSD. The system, specifically the development methodology, entertains and maybe promotes problems between collaborators. Free software is inherently a social phenomenon, and the social aspect is actually centrally important. The technology is only the subject and product of the society that creates it.

    So, while the parent post appears to be just another BSD troll, I thought it probably deserved some credence and discussion for the light it shines on the social order of FreeBSD. I like it because ultimately it ask a good question: What is going on with the social aspect of FreeBSD?

    --
    --- Nothing clever here: move along now...
  6. Confirmation from netcraft? by MavEtJu · · Score: 4, Funny

    The EkkoBSD team leader announced the project's premature death

    Did somebody get a confirmation from Netcraft about this?

    --
    bash$ :(){ :|:&};:
  7. Re:Examining this FreeBSD train wreck by Anonymovs+Coward · · Score: 2, Interesting
    I thought it probably deserved some credence and discussion for the light it shines on the social order of FreeBSD.

    That's because it's a cut and paste from an old and outdated (Feb 2003) post (non-troll, or at least, non-anonymous) on freebsd-chat -- search the archives.

    Some FreeBSD people are jerks, but that's true everywhere. And some people believe that FreeBSD-5 went in an over-complicated and ultimately unmaintainable direction, and I don't disagree that the delay in making it stable is alarming. (But people had the same worries about linux during the 2.3.x and early 2.4.x days.) And that doesn't mean FreeBSD-5 work is junk: things regularly get merged in from FreeBSD-5 to DragonFly.

  8. And? by setagllib · · Score: 3, Informative

    Saying ekkoBSD's death is a "crippling bombshell" to the entire BSD community is analogous to saying that the burger some McDonalds patron dropped while walking home is a "crippling bombshell" to McDonalds itself. Nonsense. FreeBSD 5-CURRENT is steadily approaching a good level of stability, after which it will be a Linux-killer for most desktop and some server applications. NetBSD has been and always will be the best operating system for portability, and the 2 branch is making admirable progress into modern standards and functionality while retaining amazing stability and cleanliness. OpenBSD had some scalability issues which are resolved, and now is making way into modern SMP and other useful applications. DragonFlyBSD is making astonishing progress given its currently small (but talented and enthusiasatic) developer base, and is already very close to being a viable alternative to FreeBSD for those who want something different. None of the BSDs are 'dead'. Their developer bases are largely comprised of people who focus on their Operating System (yes, technical note, all BSDs are entire Operating Systems, unlike Linux which is a toy kernel often accompanied by a user space tool chain you can run anywhere, and some hackish utilities for interfacing with the kernel), not on how many file systems they can add barely-working support for, how many undocumented kernel options they can hack on without anyone's understanding, and how many tshirts they can sell for market saturation. Linux developers lost their goal as well, what began as a valiant and successful (even if more via media coverage than technical merit, as benchmarks of even 2.4 will show) development effort of a kernel from scratch, has become an orgy of random features, some to directly oppose Windows development, some for performance [on one machine in the world, with all else being much worse off], some for 'l33t points' which amount to nothing in the real world... look at all the different patch sets for the different versions of the Linux kernel, and it's hard to respect the project at all. Some of these will get integrated if they get enough hype, some will die away, some will set your machine on fire (or in my case of trying 2.6.7-mm6, completely misuse your standard 3Com 905B network adapter, which works in any other kernel). Most of the negative slander BSD gets is the few Linux-using trolls on Slashdot who post the same terrifyingly misinformed crap, many as Anonymous Coward. "NetCraft confirms: BSD is dying", and yet NetCraft servers run FreeBSD? Do your homework people. BSD is not dying. Neither is Windows, since even that has some place in the world, believe it or not. Linux is not a magic bullet. It is and, by design, always will be a curious project to see what features can be hacked on to a bootable kernel. It is not an Operating System. It only survives from amazing marketting and corporate sponsorship, the two being mutually sustainant. The most interesting aspect of all of this is how most BSD-haters have never actually properly used and administered a BSD machine (may as well be FreeBSD since that is ahead in ease-of-use and Linux-killing power). Most BSD users won't bother slandering Linux, but for once I'd like to. I've used it lots, watched the transition from 2.4 to 2.6 and so on, and at no stage did I consider it a work of art. The transition to FreeBSD was an utter bliss of administrative elegance and system design, to the point I never looked back [except to test emerging Linux kernel versions against FreeBSD-CURRENT, with Linux never being impressive]. Say what you want about the brilliance of Gentoo's Portage (based on the design of FreeBSD Ports and NetBSD pkgsrc, lest you forget), it is not Linux itself. Type up lengthly propaganda involving Linux' amazing growth in corporate and governmental applications, it only provides more evidence of globalisation at work, even if of free software. Post the same "BSD is dead" article over and over on /. with the kind of blind propaganda that would make a preacher blush, a

    --
    Sam ty sig.
    1. Re:And? by Anonymous Coward · · Score: 4, Insightful

      My god, you have a real bad attitude. And a big chip on your shoulder as well, by the sounds. Let's go through and dismantle some of your FUD.

      FreeBSD 5-CURRENT is steadily approaching a good level of stability

      Apart from being a few years late, and looking like being at least another year, they still have serious scalability problems (see for example the recent thread about MySQL not even improving performance when going from 1 to 2 Opteron CPUs), their threading models and scheduler are still in the air, and not stable. Their "tier 1" amd64 architecture is pretty unstable.

      after which it will be a Linux-killer for most desktop and some server applications.

      Why would it be a Linux-killer for most desktop applications? Both kernels (and computers in general) are past the point where performance really matters for most desktop situations. The main things that matter are device drivers and what userspace programs can be run. You could argue that they are about equal in terms of programs, but Linux has far more device drivers at the moment.

      As far as servers go, yeah it is possible and even probable that FreeBSD would be a better choice than Linux for some things. In what areas would it be a Linux killer though? (Please spare me the leet netcraft uptime or other template zealot bullshit).

      NetBSD has been and always will be the best operating system for portability, and the 2 branch is making admirable progress into modern standards and functionality while retaining amazing stability and cleanliness.

      Although the Linux kernel has more supported CPU architectures than NetBSD's. I grant that NetBSD exceeds all Linux distros that I know of, with only Debian coming close. I have heard that some NetBSD ports are pretty low quality though.

      OpenBSD had some scalability issues which are resolved, and now is making way into modern SMP and other useful applications.

      OpenBSD is still squarely at the the bottom of the performance heap, and if you think a completely serialised kernel is "modern SMP"... well... please don't bother replying.

      DragonFlyBSD is making astonishing progress given its currently small (but talented and enthusiasatic) developer base, and is already very close to being a viable alternative to FreeBSD for those who want something different.

      No it isn't. Even the core developers acknowledge it is nowhere near close at this stage. The recent developer release trashed your hard drive, for example. No big deal of course, because it is a development release.

      Also, have a look at this. DFBSD is 20% slower than FreeBSD 4.10 on this MySQL test. Trust me, they have a long way to go.

      None of the BSDs are 'dead'. Their developer bases are largely comprised of people who focus on their Operating System (yes, technical note, all BSDs are entire Operating Systems, unlike Linux which is a toy kernel often accompanied by a user space tool chain you can run anywhere, and some hackish utilities for interfacing with the kernel

      I'll interrupt you in this parenthesis... but you are wrong, Linux is a kernel, nothing more, nothing less. Its developer base is comprised of kernel developers. Sun, SGI, IBM, Intel, Dell, HP, Veritas, Toshiba, Sony, NEC, Google come to mind as they all have staff on Linux kernel development.

      ), not on how many file systems they can add barely-working support for, how many undocumented kernel options they can hack on without anyone's understanding, and how many tshirts they can sell for market saturation. Linux developers lost their goal as well, what began as a valiant and successful (even if more via media coverage than technical merit, as benchmarks of even 2.4 will show) development effort of a kernel from scratch, has become an orgy of random features,

      What makes you think that? It is as much an orgy of random features as the Fr