Slashdot Mirror
DragonFlyBSD 1.0 Released
eeg3 writes "One year after starting the project as a fork of the FreeBSD-4.x tree, the DragonFly Team is pleased to announce its 1.0 release. Check out the project's diary for a list of the improvements the project has implemented. Also, be sure to grab it from one of the mirrors."
Sounds like good information
first ps0t
But Gartner research just confirmed that BSD is dieing.
Im dreaming ofa big bndwdth, That can resist the
BSD dead
Why bother to release shit for a dead and dying OS? I mean, BSD is even worse off than Linsux, which is on life support itself...!
Where would we be without it?!
GNAA Announces Victory over Apple Community
..."
GNAA Announces Victory over Apple Community
San Francisco, California - Just three days after being the first in the world to leak photos of Apple's upcoming revision to MacOS X, version 10.4, Steve Jobs announced to the world facts about the new Operating System consistent with information leaked by elite GNAA operator Gary Niger and prospective member Ron Delsner.
"We've pulled it off!", noted Niger during Jobs' announcement at Apple's Worldwide Developers Conference. "The GNAA plan was clever from the start with this one I think. When we received our leaked copy of the OS, we knew that by releasing only partial information and some screenshots, the association people would make with the GNAA would lead them to believe the screenshots were fake. Now that Steve 'Rim' Jobs has verified everything we leaked, we have managed to fool the entire Mac community. In essense, a few hundred thousand people have been trolled, a few hundred thousand people have lost. Though I do wish they have a nice day"
"I don't think it could have worked out any better; Every single one of the features shown in our screenshots, particularly Dashboard, which everybody called as fake, was demoed by Jobs. This is my revenge for being beat up on the rent", quoted Ron Delsner on being approached by reporters. "I've been wanting to join the Gay Nigger Association of America for quite some time, and knew that I help pull off something big if they were to let me in."
Delsner was right, as upon hearing this, Gary Niger immediately produced a vial of what he called the "Holy Gay Nigger Seed" from his front pocket, and asked Ron to kneel, at which time the Seed was poured upon Ron's head, making him an official member of the GNAA. Noticing the television cameras present in the press room, Gary cited that this was in fact the first televised induction of a member into the GNAA.
"But back to the troll", Niger said quickly after. "I had a sneaking suspicion that the homosexual caucasians of the Mac community would feel threatened by the GNAA's massive nigger cocks and immediately cast doubts upon any screenshots we produced for them. I saw this as an opportunity to troll hundreds of thousands of people. It just goes to show that GNAA is greater than j00, and that fristage postage is mine."
And Niger certainly did not fail it, as can be seen from the following excerpts taken from various Internet website's covering the leak:
ThinkSecret.com - "In fact, it was the source that led many users to call the shots fake; the information in that story, as well as this one, was provided by Gary Niger and Ron Delsner of the GNAA, an organization that deals in crapfloods and Slashdot trolling."
AppleInsider.com - "Enjoy the photoshop work. I seriously don't think Apple would be so crazy to use those jargons."
MacRumors.com - "Hmm... Information by "Gary Niger" of GNAA. Sounds too stupid to be true. And that dashboard thing? Hogwash me thinks
MacRumors.com - "I immediately thought of them when I saw "GNAA". Anyone who reads Slashdot would be familiar with them - they put big spam posts everywhere. Yes, and it doesn't surprise me. I don't think the screenshots are real (at least not the Dashboard ones), but I have no trouble believing the PDF."
Kim Kap Sol on AppleInsider.com said "I can guarantee those are fake." He then continued by saying "Hello I R Korea KEKEKEKE OMG ZERG RUSH GOGOGOGO ^_^"
Gary's reply to this was "Way to make a complete idiot of yourself you dog-eating douchebag."
Steve Jobs was unavailable for comment immediately following the keynote address, though WWDC attendee and GNAA member Porfa noticed "A cute wiggle in Jobs' ass as he walked away."
About Apple
Apple Computer is the creator of the Macintosh, popularly known as the "gay computer". 87% of GNAA members are Mac users. Founded in 1974 by Steve Jobs and Steve Wozniak, Apple was nearly out of business in the mid
What was the reason behind this fork?
wtb changelog
diary just sounds so.....blog
I thought BSD already had a fork stuck in it!
It has been dead for some time now!
Netcraft Confirms!
Am I under the impression there is no PPC port of this. Pitty.... And for all you damn BSD is dying slashdotters, enough! It's OLD and it needs to die XD
Yeah, I would like to go back to a BSD variant if I can run vmware and crossover. Otherwise, I will have to stick with Gentoo. I miss the daemon on the desktop.
I currently use Linux on most of my computers.. but I don't mind FreeBSD at all. I think DragonFly has the capability of becoming "the" BSD, except that right now it seems like the team is pretty small compared to FreeBSD's. I do, however, really like some of their ideas and think that they know what they're doing. I think I'm going to try this out on my laptop. I installed Windows XP on it a week ago and I miss FreeBSD already... FreeBSD *worked* properly...
10 minutes after posting and there are 14 replies ... none of which have a score over 0 :)
It is more productive to voice thoughtful opinions (reply) than to judge (moderate) others.
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
omg!!!!!!!11 BSD am teh dead!!!
For those of us hearing about this fork for the first time, could somebody explain what these people felt was so wrong about the FreeBSD tree that they decided to go off on their own?
Or, to put it another way... what's the diference between DragonFlyBSD and FreeBSD?
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.
DragonFly is rotting in the grave
BSD is deader than Ronald Reagan
FIRST P0zt
They felt that the approach the FreeBSD was taking for FreeBSD 5 was going in the wrong direction. I believe they hada problem with all the Mutexs or something specific like that. The main focus of DragonflyBSD is scalability and clustering. The are hoping to have SIS (Single Image Systems) as a priority. It won't be hear anytime son but thats a long term goal. OSNews has had some stuff on them over that last while. Here is the thread http://osnews.com/comment.php?news_id=7660 and here is the torrent I used http://download.exodusmachine.net/torrents/dfly-1. 0REL.iso.gz.torrent .
Let me be the first to say: I for one welcome our new Dragonflu overlords! http://www.dragonflybsd.org/main/mascot.cgi
Your CPU is not doing anything else, at least do something.
I'm gonna kill the other Anonymous Cowards.
What is the ports/packages situation look like for Dragonfly? Have they ported the old ones over, or is their selection severely limited?
I've been an avid follower of the developments in FreeBSD for around 5 years now, so my overview of the entire history of "glue that binds" FreeBSD together isn't complete. That said, I've come to be a bit disappointed at how events in the last 18 months or so seem to be pushing the project in a direction that has made things more difficult, instead of more successful, that has shown distain for experience and quality and made FreeBSD a platform for large ego's to push their personal projects down everyone's throat.
The statistics sample from 2001 over a year was a cheap attempt to minimize Matt Dillon's contribution to the project. The reason why he has been mostly silent is probably one of the most prominent signs of his superior maturity. The fact that the official defense (mostly fronted by Greg, atm) he wasn't such a substantial committer is crap, for the most part. If one wanted to go by the stats, Jeff Robertson (sorry if I munged the spelling) would be one of the key committers, and his UMA system isn't even entirely ripe yet, it's just been committed within the sample timeframe. That suddenly phk is at the top of the list, is simple a result of his newest attempt to add another large chunk of bit rot to the project that he can later claim not to have time to maintain "unless someone is willing to pay for my time" (like the atm bits, the half-finished devd monster, et.al.) One can hardly get him to look at his malloc bits, that put his name in lights at some point in the long past.
Matt didn't contribute because he was convinced that that the smp development direction that was chosen (my impression at least from the archives and my fading memory) was overly complex, too complex for the number and talent level of the contributers involved, and that it would delay a release from the -current branch significantly. So he was right. I'll almost bet that that was a constant sore for John, who still hasn't gotten his long-promised, but little delivered re-entrant work done, but he always had time enough to object to any other commits that might help along the way. Strangely Julian and Matt could work together. One might attribute certain commits to both Matt and Julian (if that would matter anyway, since -core is interested in proving the opposite statistically).
If the issue here had anything to do with IPFW, then you all better get out your C-coder hats and take a little more time to fix that rotting pile of muck that has been the standard broken packet filter interface for FreeBSD long past its possible usefulness. A packet filter with no central maintainer which is subject to once yearly random feature bloat through some wild university project from Luigi. The brokenness that Luigi introduced (and the repository bloat through backing out and recommitting, ad absurdum) was probably no less a threat to security than anything Matt did. If the security officer was to be blatantly honest with himself, ipfw would be marked broken for either a full audit or full removal (just port obsd's pf or something that someone actually actively _cares_ about).
You've alienated Jordan, Mike, Bill Paul (for all I can see), Greenman, you constantly rag on Terry, even though he's seen and done more with FreeBSD than most of you, O'Brien is on the verge of quitting (since he, like I, am not convinced that GEOM is anything more than an ego trip that will never be completely maintained or usefully documented). There are certainly others, too, that have attempted to make technically correct contributions, but didn't fit into the sort of paranoid "glee club" that core would like to have around them. You guys lack the talent to steer the positive from Matt into the project and let the crap fall by the wayside. I'm not saying Matt's rants are the most intelligent thing he's done, but he's sat by the wayside and watch the superstars beat up the code to a point where it's less stable, slower, and more bloated than it ever was. I, for one, can understand his frustration (as I ca
Isn't it funny how Slashdot is ignoring the fact that Red Hat's CFO quit, AND that they are restating their earning for the past three years AND that the SEC is now investigating them?
m l
If MSFT had done the same thing, it would be splashed all over the place, but when Red Hat delves in financial misdoings, they just bury it. What a bunch of hypocrites.
http://biz.yahoo.com/rb/040713/tech_redhat_3.ht
Both died of a drug overdose.
Red Hat is in the toilet. Serious Enron action. Yet Slashdot fails to report.
Deserve their own slashdot icon. Give this thing 3 months, and if they're still around, do the right thing Taco.
BUNCHA KARMAWHORES!11~`1
When will the "*BSD IS DEAD" posts stop?
When I read the article, I thought "Okay, I'm guessing the first 10 posts are *BSD IS DEAD" and yeah, I was right.
I mean, come on. They are instantly modded down, there is NO CHANCE IN HELL you can gain karma from them (even though 99% of all "BSD IS DEAD" posts are from AC's).
Get a life folks
fish wife!....flying tart! no, no! It got off to a flying START, and it's name...
was DragonFly!
Forbidden /main/FAQ.cgi on this server.
You don't have permission to access
Darl here, with another fine Fr1st P0st. After all -- SCO did everything first, and the rest of the responses to this story will owe their heritage to a foundation built on SCO's staff of talented programmers.
You may be wondering why SCO salesmen are not answering your numerous calls while you try to order more SCO licenses. Well, we aren't answering the phones because we're too busy celebrating our newest business partner. Rather than explaining it myself, I'll let our formal press release do the talking. Take it away, Mr. Reuters...
LINDON, Utah, Sept. 8/PRNewswire - FirstCall/ -- The SCO Group, Inc. (Nasdaq: SCOX - News), the owner and licensor of the core UNIX operating system source code, today announced its second Fortune 500 clent for the SCO Linux IP license, the GNAA (Nasdaq: RHAT - News), developer of fine Slashdot trolls on irc.efnet.net #GNAA, also well-known for revolutionizing small business development with its "Step 2: ??????" profit model. The availability of the SCO Intellectual Property License for Linux affords Linux deployments to come into compliance with international law for the use of all 2.4 and future kernels. The run-time license permits the use of SCO's intellectual property, in binary form only, as contained in Linux distributions.
By purchasing a SCO Intellectual Property License, customers avoid infringement of SCO's intellectual property rights in Linux 2.4 and Linux 2.5 kernels and assure Darl financial security for the purchase of his second home. Because the SCO license authorizes run-time use only, customers also comply with the General Public License, under which Linux is distributed. Source may still be distributed under the terms of the GPL, however source distributors are held accountable for all violation of SCO's IP. Indemnification is provided for customers of runtime clients only. Read that twice, dirty hippy. You're not in the clear yet.
GNAA spokesperson penisbird said of the licensure, "coming into compliance affords us a new competitive advantage with the other Slashdot authors. By being in the right, we can thumb down our noses at not only the Windows users and the BSD-thieving Mac Users, but also the unwashed Linux hippies running stolen code on their parents' PCs." VP of anus enlargement goat-see added, "fr1st p0st? damn i miss. how do i next story?"
Mr. Darl McBride concurred with GNAA's analysis, adding "We soon hope to convince additional clients such as Trollklore and Cabal of Logged In Trolls of the benefits of licensing SCO's valuable IP. Also, I <3 GNAA bunny. (@.@)" JesuitX clarified the nature of the SCO and GNAA alliance, adding "We're more than just a licensing client. We're also going to be helping to bring these other potential licensors into compliance. We can break them in little by little as paying sublicensors. The alternative is pretty horrible. Our lawyers can take a reticent client from virgin to hello.jpg [figure 2] in under an hour, and believe me -- it is not pleasant."
Commander Taco was unavailable for comment, however Cowboy Kneel was said to ask for a print of [figure 2] for his basement apartment. Simoniker remained British and unable to spell "color," while Timothy responded by posting the same story six times, and Hemos reposted a seventh time, the submission differing only from his application of that damned Einstein icon.
If you have mod points and would like to support GNAA, please moderate this post up.
________________________________________________
| ______________________________________._a,____ |
| _______a_.______
DeForest Kelley's great observation:
netcraft confirms: gartner is dying
(not to mention run by complete fscking morons who couldn't analyse themselves out of a paper bag)
Once again, the small fast moving team blazes ahead.
The logo looks neat but the name is way too long to pronouce in conversation.
Maybe they could name it Firebird. Oh wait...
Hey, lets all do a news submission and post ascii goatse in the "The Scoop" field! Here's some goatse now!
_ _ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __ __
*_g_o_a_t_s_e_x_*_g_o_a_t_s_e_x_*_g_o_a_t_s_e_x_*
g_______________________________________________g
o_/_____\_____________\____________/____\_______o
a|_______|_____________\__________|______|______a
t|_______`._____________|_________|_______:_____t
s`________|_____________|________\|_______|_____s
e_\_______|_/_______/__\\\___--___\\_______:____e
x__\______\/____--~~__________~--__|_\_____|____x
*___\______\_-~____________________~-_\____|____*
g____\______\_________.--------.______\|___|____g
o______\_____\______//_________(_(__>__\___|____o
a_______\___.__C____)_________(_(____>__|__/____a
t_______/\_|___C_____)/______\_(_____>__|_/_____t
s______/_/\|___C_____)_______|__(___>___/__\____s
e_____|___(____C_____)\______/__//__/_/_____\___e
x_____|____\__|_____\\_________//_(__/_______|__x
*____|_\____\____)___`----___--'_____________|__*
g____|__\______________\_______/____________/_|_g
o___|______________/____|_____|__\____________|_o
a___|_____________|____/_______\__\___________|_a
t___|__________/_/____|_________|__\___________|t
s___|_________/_/______\__/\___/____|__________|s
e__|_________/_/________|____|_______|_________|e
x__|__________|_________|____|_______|_________|x
*_g_o_a_t_s_e_x_*_g_o_a_t_s_e_x_*_g_o_a_t_s_e_x_*
Important Stuff: Please try to keep posts on topic. Try to reply to other people's comments instead of starting new threads. Read other people's messages before posting your own to avoid simply duplicating what has already been said. Use a clear subject that describes what your message is about. Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page) If you want replies to your comments sent to you, consider logging in or creating an account.
Important Stuff: Please try to keep posts on topic. Try to reply to other people's comments instead of starting new threads. Read other people's messages before posting your own to avoid simply duplicating what has already been said. Use a clear subject that describes what your message is about. Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page) If you want replies to your comments sent to you, consider logging in or creating an account.
Important Stuff: Please try to keep posts on topic. Try to reply to other people's comments instead of starting new threads. Read other people's messages before posting your own to avoid simply duplicating what has already been said. Use a clear subject that describes what your message is about. Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page) If you want replies to your comments sent to you, consider logging in or creating an account.
BSD is still dead.
duty to be a big lube or we sell kked to be Kreskin
go ahead, copy and paste!!!
*_g_o_a_t_s_e_x_*_g_o_a_t_s_e_x_*_g_o_a_t_s_e_x_*
g_______________________________________________g
o_/_____\_____________\____________/____\_______o
a|_______|_____________\__________|______|______a
t|_______`._____________|_________|_______:_____t
s`________|_____________|________\|_______|_____s
e_\_______|_/_______/__\\\___--___\\_______:____e
x__\______\/____--~~__________~--__|_\_____|____x
*___\______\_-~____________________~-_\____|____*
g____\______\_________.--------.______\|___|____g
o______\_____\______//_________(_(__>__\___|____o
a_______\___.__C____)_________(_(____>__|__/____a
t_______/\_|___C_____)/______\_(_____>__|_/_____t
s______/_/\|___C_____)_______|__(___>___/__\____s
e_____|___(____C_____)\______/__//__/_/_____\___e
x_____|____\__|_____\\_________//_(__/_______|__x
*____|_\____\____)___`----___--'_____________|__*
g____|__\______________\_______/____________/_|_g
o___|______________/____|_____|__\____________|_o
a___|_____________|____/_______\__\___________|_a
t___|__________/_/____|_________|__\___________|t
s___|_________/_/______\__/\___/____|__________|s
e__|_________/_/________|____|_______|_________|e
x__|__________|_________|____|_______|_________|x
*_g_o_a_t_s_e_x_*_g_o_a_t_s_e_x_*_g_o_a_t_s_e_x_*
Important Stuff: Please try to keep posts on topic. Try to reply to other people's comments instead of starting new threads. Read other people's messages before posting your own to avoid simply duplicating what has already been said. Use a clear subject that describes what your message is about. Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page) If you want replies to your comments sent to you, consider logging in or creating an account.
Important Stuff: Please try to keep posts on topic. Try to reply to other people's comments instead of starting new threads. Read other people's messages before posting your own to avoid simply duplicating what has already been said. Use a clear subject that describes what your message is about. Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page) If you want replies to your comments sent to you, consider logging in or creating an account.
Important Stuff: Please try to keep posts on topic. Try to reply to other people's comments instead of starting new threads. Read other people's messages before posting your own to avoid simply duplicating what has already been said. Use a clear subject that describes what your message is about. Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page) If you want replies to your comments sent to you, consider logging in or creating an account.
It's not even worthy of hosting their web site.
"IF IT'S over a year, BSD's not ever going to get up," said Fred Plum, a professor emeritus at Weill Cornell College in New York. "You'd just don't see it. It just doesn't happen."
BSD, 39, has been in a persistent vegetative state since its heart stopped for unknown reasons in 1990. A feeding tube in BSD's stomach was removed this past Wednesday after its husband, Theo the Rat, who said his wife had told him she (BSD) would not want to be kept alive under such circumstances, won a long series of court battles to have life-sustaining nourishment withdrawn so she (BSD) could die.
I wonder if the new installer is much better than freebsd's sysinstall. If it is, it might be nice if FreeBSD filched the source code (along with a number of other Dragonfly tweaks).
Or is it whack?
CmdrTaco comes to the pharmacy and asks for a vial of
cyanide. The pharmacist, trying to keep up a professional
posture, asks the customer what he might need it for.
"Oh" says taco, "I want to poison my wife".
"I am sorry Sir," says the pharmacist "but you will have to
understand, that under these circumstances, it is
impossible for me to sell you the cyanide."
CmdrTaco reaches in to his wallet and pulls out a picture of
his wife and quietly lays it on the sales counter.
The pharmacist blushes and politely remarks "I'm sorry Sir,
I didn't realize you had a prescription".
I thank you!
Fentz in tha mutha-grabbin' hizzouse!!!!!!
I think I shall never see
a tree as dead as BSD
"While you guys were down here talking, we were upstairs having hot buttered corn".
HeHE!
Everyone knows that Orange Sherbert icecream is better than Rocky-Road icecream.
You can ask anyone who works in an icecream shop, everyone wants Orange Sherbert!
If you eat Rocky-Road icecream, then you are a necropheliac because Rocky-Road icecream is dead!
Everyone knows that Orange Sherbert icecream is superior. Rocky-Road icecream eaters a re morons.
Even the people who make Rocky-Road icecream know that their days are numbered. They don't sell as much icecream as the Orange Sherbert icecream makers.
See this really raises a serious question for me about your project. What I like about the *BSD's is that they are integrated OS with their port trees or whatever as opposed to Linux being just a bunch of package thrown on top of a kernel. Well how can you justify a 1.0 release when even you admit that your port system is a hack and you're not even sure what you want to do with it? Seems like jumping the gun a little? I don't mean to troll but I'm sincerely interested.
Anyways best of luck in the future.
Your CPU is not doing anything else, at least do something.
Does Dragonfly offer any visible differences to the casual end user?
I'm not sure why you posted that link... according to that page, dragonflybsd.org is running FreeBSD. Dragonfly BSD is a fork of FreeBSD.
Question - is it possible that a Dragonfly BSD installation would report itself as a FreeBSD installation, since that's what it forked off of? If so, Dragonfly BSD is not dead. And regardless, BSD in general is far from dead. I'll bet the trolls that post "BSD is dead" all the time are running BSD themselves.
Hear recorded Slashdot headlines on your phone! New service beta testing. Just call (248) 434-5508
Congratulations to the Dragonfly team! Instead of continously whining and moaning, they are speaking their opinion with what really matters: hard work and code. It will be interesting to see how well it continues to develope and evolve.
"To those who are overly cautious, everything is impossible. "
I think you're going too far with what the OS is all about.
/bin/foo is xBSD's /bin/foo. Your kernel is the xBSD version kernel. The core system is a fully-functioning ready-to-go operating system.
The integrated OS concept is more about all the base utilities and such being all part of the release. Your bootscripts are xBSD bootscripts. Your
This contrasts with Linux because Linux is just the kernel. You build your own ls, your own tar, your own bootscripts, your own login systems and password checkers, etc.
The ports tree is above and beyond all of that. Any properly (for my particular version of "properly") configured production FreeBSD server will definitely NOT contain the ports tree, for example. It will have the base FreeBSD operating system plus exactly the installed packages that it requires to do its job properly. Nothing more.
In any field, find the strangest thing and then explore it. -John Archibald Wheeler
You're comparing future DragonflyBSD features
with current Linux features.
Hey, Linux has a future too. It isn't stagnant.
There are a number of active projects to give
seamless clustering to Linux. The filesystem
will be shared, including coherent page cache
and user-accesible (flock, etc.) locks. There
are a couple SSI projects. This stuff now has
a conference of it's own. Major developers care.
It is interesting to see posts like this turn up on Slashdot and other fora. These posts are tendentious, often personally insulting and usually written by someone who is obviously pretty closely involved with whatever group they are ranting about from behind their cover of anonymity. Why be anonymous in cases like this? Don't you have the guts to put your name to your accusations? Do you really think that you will change things you don't like by spewing venom anonymously?
I think you can use xsetroot to load wallpaper.
Nothing prevents a Linux box from having a daemon
on the desktop.
Of course, you'd be condemned to eternal damnation,
but that's your choice.
"Maybe others would like to chip in here."
HAHAHAHAHAHA! I get it! "chip in", SMP. HAHAHAHAHA!
Yet another sickening blow has struck what's left of the *BSD community, as a soon-to-be-released report by the independent Commision for Technology Management (CTM) after a year-long study has concluded: *BSD is already dead. Here are some of the commission's findings:
.005% of internet servers. A recent attempt at a face-to-face summit in Boulder, Colorado culminated in an out-and-out fistfight between core developers, reportedly over code commenting formats (tabs vs. spaces). Hotel security guards broke up the melee and banned the participants from the hotel. Two of the developers were hospitalized, and one continues to have his jaw wired shut.
Fact: DragonflyBSD, yet another offshoot of the beleaguered FreeBSD "project", is already collapsing under the weight of internal power struggles and in-fighting. "They haven't done a single decent release," notes Mark Baron, an industry watcher and columnist. "Their mailing lists read like an online version of a Jerry Springer episode, complete with food fights, swearing, name-calling, and chair-throwing." Netcraft reports that DragonflyBSD is run on exactly 0% of internet servers.
Fact: the *BSDs have balkanized yet again. There are now no less than twelve separate, competing *BSD projects, each of which has introduced fundamental incompatibilities with the other *BSDs, and frequently with Unix standards. Average number of developers in each project: fewer than five. Average number of users per project: there are no definitive numbers, but reports show that all projects are on the decline.
Fact: X.org will not include support *BSD. The newly formed group believes that the *BSDs have strayed too far from Unix standards and have become too difficult to support along with Linux and Solaris x86. "It's too much trouble," said one anonymous developer. "If they want to make their own standards, let them doing the porting for us."
Fact: There are almost no FreeBSD developers left, and its use, according to Netcraft, is down to a sadly crippled
Fact: NetBSD, which claims to focus on portability (whatever that is supposed to mean), is slow, and cannot take advantage of multiple CPUs. "That about drove the last nail in the coffin for BSD use here," said Michael Curry, CTO of Amazon.com. "We took our NetBSD boxes out to the backyard and shot them in the head. We're much happier running Linux."
Fact: *BSD has no support from the media. Number of Linux magazines available at bookstores: 5 (Linux Journal, Linux World, Linux Developer, Linux Format, Linux User). Number of available *BSD magazines: 0. Current count of Linux-oriented technical books: 1071. Current count of *BSD books: 6.
Fact: Many user-level applications will no longer work under *BSD, and no one is working to change this. The GIMP, a Photoshop-like application, has not worked at all under *BSD since version 1.1 (sorry, too much trouble for such a small base, developers have said). OpenOffice, a Microsoft Office clone, has never worked under *BSD and never will. ("Why would we bother?" said developer Steven Andrews, an OpenOffice team lead.)
Fact: servers running OpenBSD, which claims to focus on security, are frequently compromised. According to Jim Markham, editor of the online security forum SecurityWatch, the few OpenBSD servers that exist on the internet have become a joke among the hacker community. "They make a game out of it," he says. "(OpenBSD leader) Theo [de Raadt] will scramble to make a new patch to fix one problem, and they've already compromised a bunch of boxes with a different exploit."
With these incontroverible facts staring (what's left of) the *BSD community in the face, they can only draw one conclusion: *BSD is already dead.
There are some really cool innovations here that were a long time coming. One thing about Linux being slightly aged, large and now widley adopted, is that there is too much inertia against major change. DragonFly targets some serios kernel inefficiencies that will probably never get addressed in Linux. Rock on DragonFly!
Matt: "(seemless != the current hacks you see on Linux currently)"
r00t: " You're comparing future DragonflyBSD features with current Linux features."
I think he just meant it as an example. You know, brackets...
And besides, he put in "current" and "currently" in the same sentense so your comment seams a bit tense as well as redundant. I think we all agree that Linux will improve over time...
Here's a nice, in depth interview at ONLamp with the core developer team from just last week. Covers a lot of ground, I found it very informative.
Grieving is a process, and it's totally normal to go through feelings of shock, sadness, anger even guilt. The healing process is different for everyone. It might take you six weeks to move on, or it might take you six years. Don't beat yourself up because you're not "over it" yet. It takes time to heal wounds.
So what else can you do to feel better? It might sound corny, but try writing a letter, making a collage, or planting a tree in memory of the operating system you've lost. Remembering and celebrating all the good things *BSD brought to your life might help give you some closure, and having a keepsake to honor *BSD may help you get through some tough times in the future when you'll be missing it.
It's true that life won't be the same without *BSD around. It may seem like you'll never feel better, but eventually you will. Take some comfort in the old saying, "Time heals all wounds," and remember that *BSD will always be with you in your heart.
Just wanted to thank you a "little" belatedly for your ixemul.library for the Amiga in the days of yore, and IIRC the initial port of gcc... saved my ass in a dev project as my A3000 was the only thing my company "had" that could build/run the code I was working on... the project HAD to compile/run/work on a Solaris box I did not have physical or remote access to... It did.
Once Dragonfly matures a bit, I will have to try it.
Peace.
http://www.dragonflybsd.org/main/mascot.cgi
Fred is one mean looking insect, the go-lucky demon and the fat penguin are TOAST!
Oh, it's ON now!
If Mr. Edison had thought smarter he wouldn't sweat as much. --Nikola Tesla
Could someone type "uname -a" and send results!
NOT THE M$!
B$D is not the M$!
So therefore it must be good, even if the company is found to torture little animals and fund terrorists!
DragonFlyBSD is by far the recommended BSD distribution for patriotic, red-blooded American Christian Conservatives. It does away with the horrendous and evil satanic connotations of FreeBSD, OpenBSD and NetBSD, instead bringing into play the dragonfly.
As is well known in the Christian community, the dragonfly is a sign of prosperity and conservatism. The animal mascot of the Republican Party between 1904 and 1928 was in fact the dragonfly! This was a reference to the Biblical verse Leviticus 5:12, ``Let he who romeths the land; he who conservates the dragonfly; let him be loyal to the Son of the Lord.''
The BSD communities alone are just about enough to sell me on using a BSD. They're not as ready to jump into flamewars as some others can be. If there's an unresolvable disagreement, one side will just fork it and everybody still gets along. If I had the fortitude to switch to BSD I probably would. Being part of such a level-headed group would be much easier on the nerves when looking for help.
Or am I mistaken? These are just my perceptions from the outside. Is the BSD Way not as rosy as I picture it?
We care because we want a better product that is also SOCIALLY ACCEPTABLE...
.22 handgun), Apple is a Neutral logo, Windows has a neutral logo.
On another note? If your CEO or CIO is a bible thumping Christian you'll have an easier time convincing him of a product that has a nice abstract lookin Dragon Fly as a mascot then as a stupid looking childish cartoon demon or a fat dorky looking penguin, even the Darwin looks better then those two...
Try to comprehend... hackers=pests=mosquitos
OpenBSD is a Passive logo, FreeBSD is unacceptable logo (put a "powered by Demon logo" on your site and watch your sales drop), Linux is a logo that licits no feelings (fat, retarded and non-flying animal "barreling at you at 90 miles an hour?" yeah, here is my
PEOPLE ARE NOT GOVERNED BY REASON OR LOGIC!!!
Grieving is a process, and it's totally normal to go through feelings of shock, sadness, anger even guilt. The healing process is different for everyone. It might take you six weeks to move on, or it might take you six years. Don't beat yourself up because you're not "over it" yet. It takes time to heal wounds.
So what else can you do to feel better? It might sound corny, but try writing a letter, making a collage, or planting a tree in memory of the operating system you've lost. Remembering and celebrating all the good things *BSD brought to your life might help give you some closure, and having a keepsake to honor *BSD may help you get through some tough times in the future when you'll be missing it.
It's true that life won't be the same without *BSD around. It may seem like you'll never feel better, but eventually you will. Take some comfort in the old saying, "Time heals all wounds," and remember that *BSD will always be with you in your heart.
$ whatis themeaningoflife
themeaningoflife: not found
Isn't it bad Karma for an OS to have a BUG as their mascot?
09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
[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's when
BAHHAHAHAHAHAHAHAHAHAHAHAHAAHAHAHAHAH
......
HAHAAHAHAHAHAHAHAAHAHAHAHAHAHAHAHAHAHAHAAHAHAH
*deep breath*
HAHAHAHAAHAHAHAHAHAHAHAHAAHAHHAHAHAAHAHAHAHHAHAH
awesome, man. Im putting my money on DragonFly though.
Use it for servers, dummy. Use a OS X or Windows, or even Linux on the desktop.
Mr. BSD, a 57-year-old construction worker, was found lying in a pool of blood with bruises all over his body, said police Major Amnaj Sirichantanond. Mr. BSD is believed to have been killed by the penguin when he got too close to the animal, which had been tied to a tree behind the conference center on the outskirts of Bangkok.
I used to be a ksh guy, but I went to bash.
pdksh is ksh88. bash functionality is a superset of that. things like programmable completion, brace expansion, small typo correction (cdspell) makes it hard for me to go back to ksh. Yes, I know zsh is a superset of bash, but I never got into it, bash adds a little functionality without me having to change the way I think (evben though one could argue zsh is for the better). I find all thee not only useful, but essential, but as always, YMMV.
even outside of that, pdksh isn't perfect, and it has it's quirks. Think about pdksh as not so much a ksh clone, but an interpretation of the kornshell spec. It just feels different, in ways I can't think of now since it's been so long it's been my default shell.
"Why would you want to use bash?" Why would anyone want to write an OS? Why would some guy buy a Honda and not a Toyota? sometimes things are just personal prefs.
Nothing is perfect, but for a shell it has all the functionality anyone really needs. I have seen people asking before on mailing lists why BSDs don't have bash as the default, all Linux users checking it out and curious I guess. But that has always made me equally curious, why do people assume they need it? For a .bash script I can understand needing bash, but I cannot see why everyone asks about it for the default shell.
I'm sick of following my dreams - I'm just going to ask them where they're going and hook up with them later.
Fact: DragonflyBSD, yet another offshoot of the beleaguered FreeBSD "project", is already collapsing under the weight of internal power struggles and in-fighting. "They haven't done a single decent release," notes Mark Baron, an industry watcher and columnist. "Their mailing lists read like an online version of a Jerry Springer episode, complete with food fights, swearing, name-calling, and chair-throwing." Netcraft reports that DragonflyBSD is run on exactly 0% of internet servers.
Yet another sickening blow has struck what's left of the *BSD community, as a soon-to-be-released report by the independent Commision for Technology Management (CTM) after a year-long study has concluded: *BSD is already dead. Here are some of the commission's findings:
.005% of internet servers. A recent attempt at a face-to-face summit in Boulder, Colorado culminated in an out-and-out fistfight between core developers, reportedly over code commenting formats (tabs vs. spaces). Hotel security guards broke up the melee and banned the participants from the hotel. Two of the developers were hospitalized, and one continues to have his jaw wired shut.
Fact: DragonflyBSD, yet another offshoot of the beleaguered FreeBSD "project", is already collapsing under the weight of internal power struggles and in-fighting. "They haven't done a single decent release," notes Mark Baron, an industry watcher and columnist. "Their mailing lists read like an online version of a Jerry Springer episode, complete with food fights, swearing, name-calling, and chair-throwing." Netcraft reports that DragonflyBSD is run on exactly 0% of internet servers.
Fact: the *BSDs have balkanized yet again. There are now no less than twelve separate, competing *BSD projects, each of which has introduced fundamental incompatibilities with the other *BSDs, and frequently with Unix standards. Average number of developers in each project: fewer than five. Average number of users per project: there are no definitive numbers, but reports show that all projects are on the decline.
Fact: X.org will not include support *BSD. The newly formed group believes that the *BSDs have strayed too far from Unix standards and have become too difficult to support along with Linux and Solaris x86. "It's too much trouble," said one anonymous developer. "If they want to make their own standards, let them doing the porting for us."
Fact: There are almost no FreeBSD developers left, and its use, according to Netcraft, is down to a sadly crippled
Fact: NetBSD, which claims to focus on portability (whatever that is supposed to mean), is slow, and cannot take advantage of multiple CPUs. "That about drove the last nail in the coffin for BSD use here," said Michael Curry, CTO of Amazon.com. "We took our NetBSD boxes out to the backyard and shot them in the head. We're much happier running Linux."
Fact: *BSD has no support from the media. Number of Linux magazines available at bookstores: 5 (Linux Journal, Linux World, Linux Developer, Linux Format, Linux User). Number of available *BSD magazines: 0. Current count of Linux-oriented technical books: 1071. Current count of *BSD books: 6.
Fact: Many user-level applications will no longer work under *BSD, and no one is working to change this. The GIMP, a Photoshop-like application, has not worked at all under *BSD since version 1.1 (sorry, too much trouble for such a small base, developers have said). OpenOffice, a Microsoft Office clone, has never worked under *BSD and never will. ("Why would we bother?" said developer Steven Andrews, an OpenOffice team lead.)
Fact: servers running OpenBSD, which claims to focus on security, are frequently compromised. According to Jim Markham, editor of the online security forum SecurityWatch, the few OpenBSD servers that exist on the internet have become a joke among the hacker community. "They make a game out of it," he says. "(OpenBSD leader) Theo [de Raadt] will scramble to make a new patch to fix one problem, and they've already compromised a bunch of boxes with a different exploit."
With these incontroverible facts staring (what's left of) the *BSD community in the face, they can only draw one conclusion: *BSD is already dead.
To: Secretary of State Colin Powell
March 10, 2003
Dear Mr. Secretary:
I am joining my colleague AmigaOS in submitting my resignation from the list of living operating systems (effective immediately) because I cannot in good conscience compete with Linux.
I have failed:
--To support SMP
--To generate media attention
--To spawn a professionally managed distribution
--To innovate
--To be relevant.
Throughout the globe *BSD is becoming associated with in-fighting and sloppy coding. My disregard for views of other operating systems, borne out by my neglect of technical competence, is giving birth to an anti-BSD century.
I joined the operating system world because I love technology. Respectfully, Mr. Secretary, I am now bringing this calling to a close, with a heavy heart but for the same reason that I embraced it.
Sincerely,
*BSD
Dead Operating System