Slashdot Mirror
ekkoBSD 1.0 BETA1B Released
ragedev writes "Michael J. Denton, Public Relations for ekkoBSD, has announced the latest BETA release of the ekkoBSD Operating System to the public today. The new Operating System currently supports the ia32 (most PC's) platform, and will be followed soon with sparc64 and Pegasos II PPC support."
Ekko pronounced like echo? You know, like the echos coming from the sound of BSD dying?
*rimshot*
You're right, I wouldn't steal a car. But if it were possible, I sure as hell would download one!
How did that title make it through the lameness filter?
A brief overview of the situation is always valuable, so as a service to all Americans who still don't get it, I now offer you the story of the Middle East in just a few paragraphs, which is all you really need. Don't thank me. I'm a giver. Here we go:
The Palestinians want their own country. There's just one thing about that: There are no Palestinians. It's a made up word. Israel was called Palestine for two thousand years. Like "Wiccan," "Palestinian" sounds ancient but is really a modern invention.
Before the Israelis won the land in war, Gaza was owned by Egypt, and there were no "Palestinians" then, and the West Bank was owned by Jordan, and there were no "Palestinians" then. As soon as the Jews took over and started growing oranges as big as basketballs, what do you know, say hello to the "Palestinians," weeping for their deep bond with their lost "land" and "nation."
So for the sake of honesty, let's not use the word "Palestinian" any more to describe these delightful folks, who dance for joy at our deaths until someone points out they're being taped. Instead, let's call them what they are: "Other Arabs Accomplish Anything In Life And Would Rather Wrap Themselves In The Seductive Melodrama Of Eternal Struggle And Death." I know that's a bit unwieldy to expect to see on CNN. How about this, then: "Adjacent Jew-Haters."
Okay, so the Adjacent Jew-Haters want their own country. Oops, just one more thing. No, they don't. They could've had their own country any time in the last thirty years, especially two years ago at Camp David. But if you have your own country, you have to have traffic lights and garbage trucks and Chambers of Commerce, and, worse, you actually have to figure out some way to make a living. That's no fun. No, they want what all the other Jew-Haters in the region want: Israel. They also want a big pile of dead Jews, of course-that's where the real fun is-but mostly they want Israel. Why?
For one thing, trying to destroy Israel - or "The Zionist Entity" as their textbooks call it - for the last fifty years has allowed the rulers of Arab countries to divert the attention of their own people away from the fact that they're the blue-ribbon most illiterate, poorest, and tribally backward on G-d's Earth, and if you've ever been around G-d's Earth, you know that's really saying something.
It makes me roll my eyes every time one of our pundits waxes poetic about the great history and culture of the Muslim Mideast. Unless I'm missing something, the Arabs haven't given anything to the world since Algebra, and, by the way, thanks a hell of a lot for that one.
Chew this around and spit it out: Five hundred million Arabs; five million Jews. Think of all the Arab countries as a football field, and Israel as a pack of matches sitting in the middle of it. And now these same folks swear that if Israel gives them half of that pack of matches, everyone will be pals. Really? Wow, what neat news. Hey, but what about the string of wars to obliterate the tiny country and the constant din of rabid blood oaths to drive every Jew into the sea? Oh, that? We were just kidding.
My friend Kevin Rooney made a gorgeous point the other day: Just reverse the numbers. Imagine five hundred million Jews and five million Arabs. I was stunned at the simple brilliance of it. Can anyone picture the Jews strapping belts of razor blades and dynamite to themselves? Of course not. Or marshalling every fiber and force at their disposal for generations to drive a tiny Arab state into the sea? Nonsense. Or dancing for joy at the murder of innocents? Impossible. Or spreading and believing horrible lies about the Arabs baking their bread with the blood of children? Disgusting. No, as you know, left to themselves in a world of peace, the worst Jews would ever do to people is debate them to death.
Mr. Bush, G-d bless him, is walking a tightrope. I understand that with vital operations coming up against Iraq and others, it's in our interest, as Americans, to try to stabilize our Arab
So why another fork really? Security? You got OpenBSD, a standard OS, relatively well-known in the security circles and affiliated with many major security projects. Many VPN clients are benchmarked against this OS. Stability? yahoo and ftp.cdrom.com use FreeBSD. Can you convince us you can beat that? Extentions? Linux and NetBSD have numerous ports. Linux is used on many mainframes and microcontrollers as standard OS.
So all I need to know is why should ekkoBSD exist?
I'm concerned because I'm an OS buff, have used Plan9 and Xenix and Linux on a dreamcast. I'm just not sure I along with so many other alternative OS users should take this one seriously beside the reasons you've listed. If it is just a pet project for yourself... thats cool. We'll just go back to the BSD.
"Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
Even after looking at the web site, I don't see the point. Is it supposed to be a user friendly BSD?
As a default installation, ekkoBSD gives you an E-Mail server, Web Server, ssh, and several other services that would normally need to be added and secured.
This just sounds like bloat to me. Although, if you can pick a configuration you want, and have it update and patch automaticaly, that might be nifty. I can't see all that many BSD/*NIX users who want a web server installed by default though.
Pretty Pictures!
[ed. note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]
When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.
Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.
FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.
It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.
So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.
Discussion
I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.
From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.
There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.
Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.
Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?
Shouts
To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.
To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real goals. It
Mr. Bush, it pains me to see how my brothers are being tortured in the middle east.
A brief overview of the situation is always valuable, so as a service to all Americans who still don't get it, I now offer you the story of the Middle East in just a few paragraphs, which is all you really need. Don't thank me. I'm a giver. Here we go:
The Palestinians want their own country. There's just one thing about that: There are no Palestinians. It's a made up word. Israel was called Palestine for two thousand years. Like "Wiccan," "Palestinian" sounds ancient but is really a modern invention.
Before the Israelis won the land in war, Gaza was owned by Egypt, and there were no "Palestinians" then, and the West Bank was owned by Jordan, and there were no "Palestinians" then. As soon as the Jews took over and started growing oranges as big as basketballs, what do you know, say hello to the "Palestinians," weeping for their deep bond with their lost "land" and "nation."
So for the sake of honesty, let's not use the word "Palestinian" any more to describe these delightful folks, who dance for joy at our deaths until someone points out they're being taped. Instead, let's call them what they are: "Other Arabs Accomplish Anything In Life And Would Rather Wrap Themselves In The Seductive Melodrama Of Eternal Struggle And Death." I know that's a bit unwieldy to expect to see on CNN. How about this, then: "Adjacent Jew-Haters."
Okay, so the Adjacent Jew-Haters want their own country. Oops, just one more thing. No, they don't. They could've had their own country any time in the last thirty years, especially two years ago at Camp David. But if you have your own country, you have to have traffic lights and garbage trucks and Chambers of Commerce, and, worse, you actually have to figure out some way to make a living. That's no fun. No, they want what all the other Jew-Haters in the region want: Israel. They also want a big pile of dead Jews, of course-that's where the real fun is-but mostly they want Israel. Why?
For one thing, trying to destroy Israel - or "The Zionist Entity" as their textbooks call it - for the last fifty years has allowed the rulers of Arab countries to divert the attention of their own people away from the fact that they're the blue-ribbon most illiterate, poorest, and tribally backward on G-d's Earth, and if you've ever been around G-d's Earth, you know that's really saying something.
It makes me roll my eyes every time one of our pundits waxes poetic about the great history and culture of the Muslim Mideast. Unless I'm missing something, the Arabs haven't given anything to the world since Algebra, and, by the way, thanks a hell of a lot for that one.
Chew this around and spit it out: Five hundred million Arabs; five million Jews. Think of all the Arab countries as a football field, and Israel as a pack of matches sitting in the middle of it. And now these same folks swear that if Israel gives them half of that pack of matches, everyone will be pals. Really? Wow, what neat news. Hey, but what about the string of wars to obliterate the tiny country and the constant din of rabid blood oaths to drive every Jew into the sea? Oh, that? We were just kidding.
My friend Kevin Rooney made a gorgeous point the other day: Just reverse the numbers. Imagine five hundred million Jews and five million Arabs. I was stunned at the simple brilliance of it. Can anyone picture the Jews strapping belts of razor blades and dynamite to themselves? Of course not. Or marshalling every fiber and force at their disposal for generations to drive a tiny Arab state into the sea? Nonsense. Or dancing for joy at the murder of innocents? Impossible. Or spreading and believing horrible lies about the Arabs baking their bread with the blood of children? Disgusting. No, as you know, left to themselves in a world of peace, the worst Jews would ever do to people is debate them to death.
Mr. Bush, G-d bless him, is walking a tightrope. I understand that with vital operations coming
...won't be able to dig BSD out of the grave.
Then again, a dead operating system just does a forever loop on the NOOP operation.
I don't want to start a holy war here, but what is the deal with you BSD fanatics? I've been sitting here at my freelance gig in front of a BSD box (a PIII 800 w/512 Megs of RAM) for about 20 minutes now while it attempts to copy a 17 Meg file from one folder on the hard drive to another folder. 20 minutes. At home, on my Pentium Pro 200 running NT 4, which by all standards should be a lot slower than this BSD box, the same operation would take about 2 minutes. If that.
In addition, during this file transfer, Netscape will not work. And everything else has ground to a halt. Even Emacs Lite is straining to keep up as I type this.
I won't bore you with the laundry list of other problems that I've encountered while working on various BSD machines, but suffice it to say there have been many, not the least of which is I've never seen a BSD box that has run faster than its Windows counterpart, despite the BSD machines faster chip architecture. My 486/66 with 8 megs of ram runs faster than this 800 mhz machine at times. From a productivity standpoint, I don't get how people can claim that BSD is a "superior" machine.
BSD addicts, flame me if you'd like, but I'd rather hear some intelligent reasons why anyone would choose to use a BSD over other faster, cheaper, more stable systems.
switching to Macintosh?
I call it SharkBSD .. it's exactly like FreeBSD except Apache is installed by default, and I've changed about 40% of all the files to say SharkBSD instead. Hoo-wah!
I think this new BSD will TOTALLY revolutionize the computing world.
I RULE!!!
Donations accepted.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
The numbers continue to decline for *BSD but FreeBSD may be hurting the most. Look at the numbers. The loss of user base for FreeBSD continues in a head spinning downward spiral. In truth, for all practical purposes FreeBSD is already dead. It is a dead man walking. It's a fact: FreeBSD is dying.
All the *BSD is dying posts are contained in this one post to spare the BSD section of the heavy trolling. If you have mod points and you're a wanking Linux fagboy whose momma never loved him, please mod this up so that everybody will know your dark and dirty private fantasy -- that *BSD is dying, and that you masturbate like a monkey on drugs! There's no need to post your own trolls, as they will only be redundant and you'll make yourself look even more like an asshole than you already are!
Oh, and if I've missed any, please add your troll as a reply and I'll include it in the next Troll-in-one. Keep your flames to yourself -- I already know you have a distorted psychological need to imagine BSD as dying because it only helps to relieve the cognitive dissonance you are currently experiencing with Linux. In reality, though, it only shows a deep-seated jealousy towards BSD, which you'll go to any lengths to deny.
_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_
The *BSD Wailing Song
What's left for me to see
In my ship I sailed so far
What can the answer be
Don't know what the questions are.
And after all I've done
Still I cannot feel the sun
Tell me save me
In the end our lost souls must repent.
I must know it is for certain
Can it be the final curtain
As long as the wind will blow
I'll be searching high and low.
Who knows what's really true
They say the end is so near
Why are we all so cruel
We just fill ourselves with fear.
And heaven and hell will turn
All that we love shall burn
Hear me trust me
In the end our lost sould must repent.
I must know it is for certain
Can it be the final curtain
As long as the wind will blow
I'll be searching high and low
Final curtain
Final curtain
_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_
pressed to bsd lips
bsd drink up
_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_
I don't want to start a holy war here, but what is the deal with you BSD fanatics? I've been sitting here at my freelance gig in front of a BSD box (a PIII 800 w/512 Megs of RAM) for about 20 minutes now while it attempts to copy a 17 Meg file from one folder on the hard drive to another folder. 20 minutes. At home, on my Pentium Pro 200 running NT 4, which by all standards should be a lot slower than this BSD box, the same operation would take about 2 minutes. If that.
In addition, during this file transfer, Netscape will not work. And everything else has ground to a halt. Even Emacs Lite is straining to keep up as I type this.
I won't bore you with the laundry list of other problems that I've encountered while working on various BSD machines, but suffice it to say there have been many, not the least of which is I've never seen a BSD box that has run faster than its Windows counterpart, despite the BSD machines faster chip architecture. My 486/66 with 8 megs of ram runs faster than this 800 mhz machine at times. From a productivity standpoint, I don't get how people can claim that BSD is a "superior" machine.
BSD addicts, flame me if you'd like, but I'd rather hear some intelligent reasons why anyone would choose to use a BSD over other faster, cheaper, more stable systems.
_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_*_
It is common knowledge that *BSD is dying. Almost everyone knows that ever hapless *BSD is mired in an irrecoverable and mortifying tangle of fatal trouble. It is perhaps anybody's guess as to which *BSD is the worst off of an admittedly suffering *BSD community. The numbers continue to decline for *BSD but FreeBSD may be hurting the most. Look at the numbers. The erosion of user base for FreeBSD continues in a head spinning downward spiral.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users
Pretty much -all- of the commits I've seen had to do with syncing with the OpenBSD tree. Just how much code has the ekkoBSD project itself written?
BSD is dy-
ing, dying, dying, dying
Dying, dying, dead
I wonder if it will work on this Toshiba laptop - OpenBSD is fine and so is NetBSD, but I had a problem with FreeBSD - network driver wouldn't work.
Another bsd will give us more choice, so good luck to them.
And why would any sane Free/Open/Net-BSD user want to switch? I thought that the idea behind OpenBSD is that nothing is enabled by default and that if you want it, you enable it yourself. Besides, I don't know if I like the idea of one man directing development -- when one man answers the FAQ in first person, that is mildly disturbing. Further, how it is any different from DragonflyBSD? And trying to make BSD cooler, and more like Linux I think is a mistake.
The views expressed are mine own and do not express the views of my employer.
What We Can Learn From BSD
By Chinese Karma Whore, Version 1.0
Everyone knows about BSD's failure and imminent demise. As we pore over the history of BSD, we'll uncover a story of fatal mistakes, poor priorities, and personal rivalry, and we'll learn what mistakes to avoid so as to save Linux from a similarly grisly fate.
Let's not be overly morbid and give BSD credit for its early successes. In the 1970s, Ken Thompson and Bill Joy both made significant contributions to the computing world on the BSD platform. In the 80s, DARPA saw BSD as the premiere open platform, and, after initial successes with the 4.1BSD product, gave the BSD company a 2 year contract.
These early triumphs would soon be forgotten in a series of internal conflicts that would mar BSD's progress. In 1992, AT&T filed suit against Berkeley Software, claiming that proprietary code agreements had been haphazardly violated. In the same year, BSD filed countersuit, reciprocating bad intentions and fueling internal rivalry. While AT&T and Berkeley Software lawyers battled in court, lead developers of various BSD distributions quarreled on Usenet. In 1995, Theo de Raadt, one of the founders of the NetBSD project, formed his own rival distribution, OpenBSD, as the result of a quarrel that he documents on his website. Mr. de Raadt's stubborn arrogance was later seen in his clash with Darren Reed, which resulted in the expulsion of IPF from the OpenBSD distribution.
As personal rivalries took precedence over a quality product, BSD's codebase became worse and worse. As we all know, incompatibilities between each BSD distribution make code sharing an arduous task. Research conducted at MIT found BSD's filesystem implementation to be "very poorly performing." Even BSD's acclaimed TCP/IP stack has lagged behind, according to this study.
Problems with BSD's codebase were compounded by fundamental flaws in the BSD design approach. As argued by Eric Raymond in his watershed essay, The Cathedral and the Bazaar, rapid, decentralized development models are inherently superior to slow, centralized ones in software development. BSD developers never heeded Mr. Raymond's lesson and insisted that centralized models lead to 'cleaner code.' Don't believe their hype - BSD's development model has significantly impaired its progress. Any achievements that BSD managed to make were nullified by the BSD license, which allows corporations and coders alike to reap profits without reciprocating the goodwill of open-source. Fortunately, Linux is not prone to this exploitation, as it is licensed under the GPL.
The failure of BSD culminated in the resignation of Jordan Hubbard and Michael Smith from the FreeBSD core team. They both believed that FreeBSD had long lost its earlier vitality. Like an empire in decline, BSD had become bureaucratic and stagnant. As Linux gains market share and as BSD sinks deeper into the mire of decay, their parting addresses will resound as fitting eulogies to BSD's demise.
While people may be entitled to do their own thing, fracturing the community only breeds confusion and slows advancement, both technically and politically ( i.e. market )
Look at the Linux camp, part of the problem of adoption is the convoluted nature of it. Its hard to take something serious when you have TOO many unstable options.. ( unstable in the sense if they will be around tomorrow, and support you.. ) It makes rational decisions tenuous at best.
A better choice would be to make the 'improvements' available to the main BSD projects, as we don't need things watered down any more then they already are ( personally think the 3 major forks should be re-combined so we can all benefit from each others work, not have a bunch of pet-projects running around )
Same goes for Linux.. there needs to be predictiable consistency in business.
---- Booth was a patriot ----
One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.
FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dying
BSD is a walking corpse, putrefying on the hoof.