Slashdot Mirror
Chock Full o' NetBSD!
jschauma writes "While it's no Indigo
Espresso or a VAX Bar (though,
of course, there is NetBSD/sgimips and NetBSD/vax), at least you can log
in on a Mr.
Coffee. And while the JavaStation has been running NetBSD for a while,
full support is now completely in-tree:
NetBSD's Martin Husemann announced today
that he has fixed all outstanding issues with JavaStation support. This
means, that you can now run your JavaStation with a stock distribution of NetBSD/sparc. The JavaStation-NC
is a network computer class machine built on the microSPARC-IIep processor.
More information about the JavaStation can be found in the JavaStation
HOWTO, Martin's email to
the port-sparc mailing list and Valeriy E. Ushakov's paper 'Porting NetBSD to
JavaStation-NC.'"
fp mother fucker!
Not very hard on BSD article... hehe
I use a BSD system for my server, and I find that the ports collection is somthing that is extremely usefull for any system administrator that wants to save time.
I dont want to downlaod dependencies, I wan the computer to do it, and this is why it is so great.
thank you!
NetBSD is DYING!
There can't be a lot of those machine around. And a new Mini ITX machine can be ahd for under $200, is more powerful, more featureful, and has far more software available for it.
NetBSD's got my coffee maker on-lock, but it looks like my dishwasher will be safe for a little while longer. NetBSD should produce a full kitchen appliance set. I would buy it, just as long as I don't have to compile anything (recompiling your kernel on a blender takes surprisingly long).
Seems kind of odd that someone submitted a news story that is an exact copy of an OSNews one. And it is sad that it made it to the front page.
Well hey, good way to get free karma.
_d8b____________________d8b_______d8,
_?88____________________88P______`8P
__88b__________________d88
__888888b__.d888b,_d888888________88b_.d888b,
__88P_`?8b_?8b,___d8P'_?88________88P_?8b,
_d88,__d88___`?8b_88b__,88b______d88____`?8b
d88'`?88P'`?888P'_`?88P'`88b____d88'_`?888P'
______d8b________________________d8b
______88P________________________88P
_____d88________________________d88
_d888888___d8888b_d888b8b___d888888
d8P'_?88__d8b_,dPd8P'_?88__d8P'_?88
88b__,88b_88b____88b__,88b_88b__,88b
`?88P'`88b`?888P'`?88P'`88b`?88P'`88b
I checked ebay, and i didnt find anything doing a search for the terms "mr coffee sparc". Also, the specs of these java machines is pretty poor, no better then most of the x86 boxes that were running around 95-96.
Lawyers, MBA's, RIAA? A jedi fears not these things!
NetBSD is much, much more portable than 'Linux' if you refer to an Operating System, and not just a Kernal. 'NetBSD' represents a kernal and a complete base userland, all under one unified seamless source tree. Linux, on the other hand, is a kernal, and any number of different utilities and packages lumped together. There are dozens of versions of 'Linux' just for the x86, let alone the variations when you move from one architecture to another, whereas there is one NetBSD port for each platform, and all the NetBSD ports consist of base userlands compiled from the same source tree.
/etc directory from a NetBSD 1.6 Sparc machine and expand it into the /etc directory of any x86 or 68000 or MIPS or PPC NetBSD 1.6 machine and it will just work
Hope this makes sense. What it means in the final analysis is that I can (almost) tar up the
49640+5012614
For any wanna-be trolls:
*BSD is not dying and you are not cute,funny, or clever. Get over it.
Elegy For *BSD
I am a *BSD user
and I try hard to be brave
That is a tall order,
*BSD's foot is in the grave.
I tap at my toy keyboard
and whistle a happy tune
but keeping happy's so hard,
*BSD died so soon.
Each day I wake and softly sob
Nightfall finds me crying
Not only am I a zit faced slob
but *BSD is dying.
I'm sure the 12 people that use NetBSD & Sparc are gonna be super happy!
Don't use NetBSD myself, but I'm curious. What are the differences?
When someone might yell at me, it has to be OpenBSD.
DEAL
1. You can not play games on it.
2. It cannot be used by my grandma.
3. It lacks a GUI of any note.
4. There is no support available for it.
5. It is an assortment of fragmented OSes.
6. It cannot be run on the x86 platform.
7. You have to compile everything and know C.
8. Support for the latest hardware is always poor.
9. It is incompatiable with GNU/Linux.
10. It is dying.
How can people say BSD is dying when it has a mascot like this?! Linux needs to get its act together if it's going to compete with the kind of hot chicks and gorgeous babes that BSD has to offer!
You just can't take Linux seriously when its fronted by losers like these. Would you buy software from them? I don't think so! You Linux groupies need to find some sexy girls like her! I mean just look at this girl! Doesn't she excite you? I know this little hottie puts me in need of a cold shower! This guy looks like he is about to cream his pants standing next to such a fox. As you can see, no man can resist this sexy little minx. I mean are you telling me you wouldn't like to get your hands on this ass?!
With sexy chicks like the lovely Ceren you could have people queuing up to buy open source products. Could you really refuse to buy a copy of BSD if she told you to? Come on, you must admit she is better than an overweight penguin or a gay looking goat! Don't you wish you could get one of these? Personally I know I would give my right arm to get this close to such a divine beauty!
Join the campaign for more cute open source babes today!
... read the topic as "BSD Chock Full o' NetBSD" and assume that, with the recent SCO/Linux issues, that NetBSD was going down the same war path as SCO but with BSD ?
[cartman] I feel as though SCO has warped my fragile little mind [/cartman]
chris at darkrock dot co dot uk
http colon slash slash www dot darkrock dot co dot uk
[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
Good news world, Saddam Hussein (Or however the fucker spells it) has been captured by U.S. forces from the 4th ID. Score one for the good guys.
It's always nice to see BSD being used in strange new ways. I like knowing that using it allows me to move to any platforms in the future without any difficulty. With uncertainty of the x86 platform and lack of portability of Linux distributions not to mention little drivers outside of the x86 realm, NetBSD makes a perfect platform. I'm not even going to mention the problems of the GPL license.
This is why BSD is so great. You have actual portability. It's truly open and free. Stable and secure. Much better code base then Linux with a better development group. The only area it's lacking is XFree86, but in time drivers will come around.
Fortress of Insanity
Area horse owners, especially those around Echo Lake, may want to keep a close eye on their equine companions after two recent instances of abuse and theft.
A naked man was found having intercourse with a horse in a stable on McCaffery Road around 6:30 a.m. on Nov. 17. Flathead County Sheriff Jim Dupont said the man, still nude, fled on foot when the owner of the horse entered the stable.
"He left his boots and a bottle of hand lotion behind," Dupont said.
Also found were a Yoda doll, Crisco, and a ticket marked "FreeBSD anniversary party". Sheriff's deputies concur that the suspect is an unemployed BSD developer.
The incident came just days after a Flathead County deputy reported his horse missing. The horse had apparently been taken from its stable near Echo Lake early in the weekend. The horse was back in its stable by late in the weekend with traces of lanolin around its rectum, Dupont said.
"It appears we have a serial horse rapist," Dupont said. The sheriff's office is investigating, and Dupont advised horse owners to be vigilant. "BSD is dying, and there is nothing which these BSD weirdos won't do in an act of desperation," he concluded.
Yet another crippling bombshell hit the beleaguered *BSD community when recently IDC confirmed that *BSD accounts for less than a fraction of 1 percent of all servers. Coming on the heels of the latest 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 hobbyist 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 dead
http://www.cnn.com/2003/WORLD/meast/12/14/sprj.irq .main/index.html
NetBSD is much, much more portable than 'Linux' if you refer to an Operating System, and not just a Kernal. 'NetBSD' represents a kernal and a complete base userland, all under one unified seamless source tree. Linux, on the other hand, is a kernal, and any number of different utilities and packages lumped together. There are dozens of versions of 'Linux' just for the x86, let alone the variations when you move from one architecture to another, whereas there is one NetBSD port for each platform, and all the NetBSD ports consist of base userlands compiled from the same source tree.
/etc directory from a NetBSD 1.6 Sparc machine and expand it into the /etc directory of any x86 or 68000 or MIPS or PPC NetBSD 1.6 machine and it will just work
Its stupid to compare like that. There are lots of versions of BSD just for the x86. NetBSD is a complete operating system package, so lets compare it to another orange. Take Debian for example.
Debain is a single, complete source tree, with probably as many architectures as NetBSD. And it works with more relevant ones such as Power4 and IA64.
Hope this makes sense. What it means in the final analysis is that I can (almost) tar up the
Yeah this obviously works with Debian as you'd expect. I don't see why you're touting it as anything special...
I love BSD. It's so easy for any Evil Corporation to take it, modify it, redistribute it under a draconian closed-source license, charge an arm-and-a-leg for it, and REAP THE REWARDS! Even if 99% of the code is untouched. Muahahaha!
Guys, wake up. BSD is not free software. It never was. Well it is free, but it's not designed to stay free due to its overly permissive license. Any true supporter of free software would shun it and stick with GNU/Linux these days.
BSD comes with a lot of GNU utils. Heck, BSD wouldn't exist without GNU gcc. They *owe* the GNU project, and would do well to switch their license to the FSF's GPL.
(Let me make a piece of software. Call it RedWM, the Red Window Manager, and within it offer only shades of burgundy and not any real Red. That's an analogy for how misnamed NetBSD truly is!)
*BSD is like a problem child dying of some rare incurable disease.
So, you bleeding heart anti-liberation wankers. This is the end-game.
If the Coalition has the guts to turn Saddam over to the Iraqis for some real "interrogation", we'll soon find those missing WMDs. I hope you're not going to start whining about HIS human rights...
Why would one choose a particular one? And what differentiates BSD from Linux, and from Unix?
Use the BBC or Al-Jazeera.
hmmm. let's see... :-)
I have one of those lying down, unused... US$ 0.
ITX etc etc... US$ 200.
my bank account balance after paying household bills... US$ 0.
Which one?
Now THAT's insightful, informative and interesting.
It's better to be the foot on the boot than the face on the pavement. ~~ tkx Kadin2048
The record is clear on one thing: no operating system has ever come back from the grave. Efforts to resuscitate *BSD are one step away from spiritualists wishing to communicate with the dead. As the situation grows more desperate for the adherents of this doomed OS, the sorrow takes hold. An unremitting gloom hangs like a death shroud over a once hopeful *BSD community. The hope is gone; a mournful nostalgia has settled in. Now is the end time for *BSD.
So he's captured, end of story. What else can you fucking say man? Discuss his fashion, maybe his play?
Caviar or something like that?
You definitely fail it.
BSD HELP
A Beginners Guide
BSDs are a proud, independent breed of animal. Their breed, their social
life, their training (or lack therof), and their own developing personality
are a few of the variables that must be accounted for when attempting to
understand them individualy. BSDs, like people, all have individual
personalities so one must really spend a great deal of time with an animal
to develop a significant relationship. I can say with a great deal of
confidence however, that anyone that spends a significant amount of time
observing and interacting with BSDs can do ANYTHING with them.
Basic reproductive behavior
BSDs, like most animals, depend on the sense of smell to signify the
readiness of a female for an encounter. The Windows will approach the
Linux from behind and make a squealing noise...if the Linux is in heat she
will "wink" her pussy and squirt a few short squirts of urine. The
Windows will have to approach her several times (unless shes a real slut)
before she will acquiesse. The Linux will often prove recalcitrant for some
time, even threatening to kick the Windows. As he squeals and nips her
however, with time, she becomes acquiessent and allows him to mount her and
complete the union.
The Windows
A full grown Windows's cock, when fully erect, will measure some two to
three feet long. It can be three to six inches thick at the base, to about
two inches thick at the head. BSDs are somewhat different from other
animals in the way their cock head works. When a BSD is fully erect and
excited and ready to mount, his cock head is somewhat pointed and not as
thick as might be normally observed. This is to facillatate an easier
entry into the Linux. After the BSD has entered and reaches a climax the
head swells (though it is more spongy then hard) into a fist sized mass as
he ejacultates. It is thought that this serves as a plug to force the
semen deep into the Linux rather then allowing it to leak out. A full grown
Windows can ejaculate about one cup ( 8 ounces ) of semen. It will take
quite a few spurts to accomplish this. Each time his tail will raise and
lower in a brief flick. The first few jets are of a thin to average
consistency of cum. The final few jets are of a thick gelatinous
substance... it is thought that this serves to "seal" the Linuxs pussy so
that the semen has time to do it's thing before leaking out. BSD semen
is extremely viscous, if you touch your finger to a pool of it you can draw
a thin string of it five to six feet long! BSD cum has a nice flat taste
to it...not at all bitter like man's cum. You can easily drink cups of it
with no discomfort.
The Linux - how to do it.
Linuxs can be quite satisfactory for the average well endowed male. If you
are somewhat less developed you might find better pleasure with a pony or
Miniature BSD. These are also better as they are lower to the ground. A
pony you can fuck standing up. A miniature BSD on your knees or
squatting depending on the size. A Linux will require something to stand on
or "platform shoes"...(IE mini stilts to raise you a foot off the ground)
so that you can reach her pussy.
Fucking any BSD will depend on the BSD. Some will be ready right
away...some will take coaxing. Pet the animal, talk to it softly, spend
time with it gaining it's trust. If something you are doing upsets it then
don't force it. Talk to it and calm it. If you work slowly you can make
an animal accept anything. It is just a question of helping it overcome
it's fears. All animals fear man if raised in the wild. How any animal
reacts will depend on it's own experiences. If you haved raised the animal
yourself in a loving enviroment, then you should have no problem
associating with it, if it is a strange animal that you have met in the
wild then you will have to go through an extended "courtship" to learn how
to respond
HOW'S MY POSTING? CALL 1-800-POSTING
Gentoo has had a similar system for quite a while already. Get with the times.
Check ya fav news sight NOW
You've illegally invaded a sovereign nation. That hardly makes you one of the "good guys", asshat.
The ends never justifies the means.
You might want to check Ebay for Javastation rather than Mr Coffee. The latter was just the Sun code name for that particular Javastation (Krups being the other model IIRC).
The low spec is irrelevant on a machine like this, as it is nothing more than a thin client. I occasionally use a similar NCD ThinStar to login to one of the development servers at work. The client runs nothing more than WinCE and an X server, and all the apps are run on the server.
Chris
This will boost the chances of GWB winning the 2004 elections. Four more years of "spend, spend, spend", militarization of the nation, blurring the lines of the church and the state as well as pursuing foreign policy that drives even our allies mad.
You nigger-loving cocksuckers are next!
Bring it on...
[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. I
Don't use NetBSD myself, but I'm curious. What are the differences?
Compared to Linux, there is only one NetBSD distribution. Companies like Wasabi Systems may offer branded copies of a release, but they contain the same software as the ISO images found on the NetBSD ftp servers. Another key difference is that the NetBSD project maintains an entire operating system, rather than Linus Torvalds and his loose knit team, who concern themseles almost exclusively with the Linux kernel itself. The NetBSD approach leads to a greater consistency and closer integration of kernel and userland. The downsides are that third party software which NetBSD relies on (gcc for instance), often takes a while to update to new releases while Linux'isms are worked out.
The NetBSD project is based around a core team, and peer review is encouraged before any changes are commited by non-core developers. This leads to a very consistent, clear code base that conforms to number of good coding practices. For instance, the NetBSD kernel drivers liberally use #defines for addresses and registers, while Linux doesn't frown on undocumented magic numbers. The Linux style makes supporting someone elses code a nightmare, unless you're very familiar with the hardware the driver is for.
The NetBSD project has a server farm dedicated to autobuilds, and it is easy for port masters (people concerned with NetBSD on a particular platform) to see when the development version has broken for their platform. In the Linux world, as long as x86 works the other platforms are considered secondary. This is why I run NetBSD on my non-x86 hardware - I got pissed off with Linux claiming fot support a platform when it had clearly been broken for months.
Finally, there is the pkgsrc collection. This allows me to install all the software I need, confident that it has been tested (and patched if necessary). The dependency tracking of pkgsrc makes the much vaunted Debian Linux look very ho-hum in comparison.
Chris
The cute newsreader with the pink lipstick is on Al-Jazeera right now! I'd give her one anyday!
the last link is booby trapped with some kind of weird thing.
Your comment has too few characters per line
Your comment has too few characters per line
Your comment has too few characters per line
Has there ever been one? I dare you to name one single invasion that has been "legal".
Sixty years ago, I worked in what was once my Grandfather's Greenhouses. Gramps had died a year earlier and Grandma, now in her seventies had been forced to sell to the competition. I got a job with the new owners and mostly worked the range by myself. That summer, they hired a man to help me get the benches ready for the fall planting.
Ike always looked like he was three days from a shave and his whiskers were dirty white, shaded by the brim of his battered felt fedora.
He did not chew tobacco but the corners of his mouth turned down in a way that, at any moment, I expected a trickle of thin, brown juice to creep down his chin. His bushy, brown eyebrows shaded pale, gray eyes.
The old-timer extended his hand, lifted his leg like a dog about to mark a bush and let go the loudest fart I ever heard. The old fellow then winked at me, "Ike Thomas is the name and playing pecker's my game."
I thought he said, "Checkers." I was nineteen, green as grass. I said, "I was never much good at that game."
"Now me," said Ike, "I just love jumping men . . ."
"I'll bet you do."
". . . and grabbing on to their peckers," said Ike.
"I though we were talking about . . ."
"You like jumping old men's peckers?"
I shook my head.
"I reckon we'll have to remedy that." Ike lifted his right leg and let go another tremendous fart. "He said, "We best be getting to work."
That summer of 1941 was a more innocent time. I learned most of the sex I knew from those little eight pager cartoon booklets of comic-page characters going at it. Young men read them in the privacy of an outside john, played with themselves, by themselves and didn't brag about it. Sometimes, we got off with a trusted friend and helped each other out.
Under the greenhouse glass, the temperature sometimes climbed over the hundred degree mark. I had worked stripped to the waist since April and was as brown as a berry. On only his second day on the job and in the middle of August, Ike wore old fashioned overalls. Those and socks in his high-top work shoes was every stitch he wore. When he bent forward, the bib front billowed out and I could see the white curly hairs on his chest and belly.
"Me? I just love to eat pussy!" Ike licked his lips from corner to corner then sticking his tongue out far enough that the tip could touch the end of his nose. He said, A man's not a man till he knows first hand, the flavor of a lady's pussy."
"People do that?"
He winked. "Of course the taste of a hard cock ain't to be sneezed at neither. Now you answer me, yes or no. Does a man's cock taste salty or not?"
"I never . . ."
"Well, old Ike's willing to let you find out."
"No way."
"Just teasing," said Ike. "But don't give me no sass or I'll show you my ass." He winked. "Might show it to you anyway, if you was to ask."
"Why would I do that?"
"Curiosity, maybe. I'm guessing you never had a good piece of man ass."
"I'm no queer."
"Now don't be getting judgmental. Enjoying what's at hand ain't being queer. It's taking pleasure where you find it with anybody willing." Ike slipped a hand into the side slit of his overalls and I could tell he was fondling and straightening out his cock. "Now I admit I got me a hole that satisfied a few guys."
I swallowed, hard.
Ike winked. "Care to be asshole buddies?"
***
We worked steadily until noon. Ike drew a worn pocket watch from the bib pocket of his loose overalls and croaked, "Bean time. But first its time to reel out our limber hoses and make with the golden arches before lunch."
I followed Ike to the end of the greenhouse where he stopped at the outside wall of the potting shed. He opened his fly, fished inside, and finger-hooked a soft white penis with a pouting foreskin puckered half an inch past the hidden head.
bush is a great president!
Back in the day, around FreeBSD 2.2.8, it was a very nice operating system. However, when RELENG_5 was branched, a lot of wrong decisions were made, most of them by people with zero clue about how to implement proper SMP (e.g. John Baldwin). Matt Dillon tried to fix the situation, but all he got in response was a commit bit suspension, which later lead to his expulsion.
You can thank assholes like: Poul-Henning Kamp (POT, KETTLE, BLACK), Greg Lehey, Dag-Erling Smorgrav, Mark Murray and Bill Fumerola for kicking him out and making sure that, thanks to overengineering, RELENG_5 will never work.
Further proof, FreeBSD recently went 100% dynamic to allow the use of NSS switch system. John Dyson, who did most of the VM work back in the day, pointed out how wrong this decision was. Dillon also jumped in and offered a better solution. What he got as reward was Scott Long telling him to go away. Listen Scott, YOU ARE A FUCKING IDIOT. Not only you don't even know how to quote, but you also managed to fuck the 5.1-R isos twice. I wonder how can you be in re@, that sure has lead to the piss-poor quality of the last 2 or 3 releases.
Joseph Mallett, an ex-committer.
10814OK, they've got NetBSD up on the JavaStation. This is no real suprise, "Of course it runs NetBSD".
A friend of mine just recently came into a bunch of Sunrays... Has anyone figured out if they're good for anything unless you've got a Sparc to hang them off of?
my sig's at the bottom of the page.
Back in the day, around FreeBSD 2.2.8, it was a very nice operating system. However, when RELENG_5 was branched, a lot of wrong decisions were made, most of them by people with zero clue about how to implement proper SMP (e.g. John Baldwin). Matt Dillon tried to fix the situation, but all he got in response was a commit bit suspension, which later lead to his expulsion.
You can thank assholes like: Poul-Henning Kamp (POT, KETTLE, BLACK), Greg Lehey, Dag-Erling Smorgrav, Mark Murray and Bill Fumerola for kicking him out and making sure that, thanks to overengineering, RELENG_5 will never work.
Further proof, FreeBSD recently went 100% dynamic to allow the use of NSS switch system. John Dyson, who did most of the VM work back in the day, pointed out how wrong this decision was. Dillon also jumped in and offered a better solution. What he got as reward was Scott Long telling him to go away. Listen Scott, YOU ARE A FUCKING IDIOT. Not only you don't even know how to quote, but you also managed to fuck the 5.1-R isos twice. I wonder how can you be in re@, that sure has lead to the piss-poor quality of the last 2 or 3 releases.
Joseph Mallett, an ex-committer.
1492Are you UNCIRCUMCISED?
Then you should FEEL dirty and ASHAMED! How can you have that aardvark hanging between your filthy puke inducing crotch when there is a treatment for the UGLY DICK condition? That's right, as a Linux chick I can't count the many times I've encountered this DIGUSTING problem.
Linux Guys are VERY GROSSLY uncircumcised do to the fact that the leaders of this movement are not. Linus "long foreskin" Torvalds and Alan "uncut" Cox are PRIME examples of ugly SMELLY SMEGMA dick. I suggest that we take up a collection and CIRCUMCISE these guys.
Until this is done, I'll only use GPL software from properly circumcised and beautiful cocked men like RMS. So NO Linux kernel for this HOT GPL chick..only the HURD until these filthy uncircumcised Linux guys get the operation and become clean.
Back in the day, around FreeBSD 2.2.8, it was a very nice operating system. However, when RELENG_5 was branched, a lot of wrong decisions were made, most of them by people with zero clue about how to implement proper SMP (e.g. John Baldwin). Matt Dillon tried to fix the situation, but all he got in response was a commit bit suspension, which later lead to his expulsion.
You can thank assholes like: Poul-Henning Kamp (POT, KETTLE, BLACK), Greg Lehey, Dag-Erling Smorgrav, Mark Murray and Bill Fumerola for kicking him out and making sure that, thanks to overengineering, RELENG_5 will never work.
Further proof, FreeBSD recently went 100% dynamic to allow the use of NSS switch system. John Dyson, who did most of the VM work back in the day, pointed out how wrong this decision was. Dillon also jumped in and offered a better solution. What he got as reward was Scott Long telling him to go away. Listen Scott, YOU ARE A FUCKING IDIOT. Not only you don't even know how to quote, but you also managed to fuck the 5.1-R isos twice. I wonder how can you be in re@, that sure has lead to the piss-poor quality of the last 2 or 3 releases.
Joseph Mallett, an ex-committer.
26617and they combined their names to call the distribution ``Debian''. Ok so far. But riddle me this:
- Where
is Debby now?
- Are Debby and Ian still together?
- What does
Debby look like (jpg, if possible).
- Does Debby do Linux or is she
really a Windows gal?
- Where was Debby from originally (town, high
school, etc)?
I'd sort of like to start a Debby fan club for this unsung heroine of Free Software.Hey Debby, wherever you are -- we love ya, baby!
And you guys call Windows bloated....
What We Can Learn From NetBSD
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 final demise.
woo hooo now there is someone to blame instead of bush!!!
Solitarysoviet
Rolf!!ROLF!!!
l!ol!ol!ol!ol!LO!LO!LO!LO!LOLOLO!OL
BSD is in my pants!!.
get out!! looooooooooool
I know it is now almost a mantra set in stone that "NetBSD is dying". Unfortunately, the abuse of that fact by trolls has obscured the truth, that truth being that NetBSD really is dying.
My main reason for moving away from NetBSD has been twofold. First, to avoid the constant political infighting and bickering. And secondly, to investigate more promising and viable entries into the operating systems sweepstakes. NetBSD is no longer a legitimate player, I'm sorry to say.
The question is not why you would install it, the question is why anybody would spend time making the port. The hardware has no future, and the only thing that makes it interesting from a geek point of view is that it is running JavaOS.
Iraqi resistance expected to diminish provided all the guerrillas receive Paul Bremer's memo. Initial reports of Saddam Hussein's capture indicate that he kept himself busy attempting to backdoor the Linux kernel and install rootkits on several Debian servers.
Elegy For *BSD
I am a *BSD user
and I try hard to be brave
That is a tall order
*BSD's foot is in the grave.
I tap at my toy keyboard
and whistle a happy tune
but keeping happy's so hard,
*BSD died so soon.
Each day I wake and softly sob
Nightfall finds me crying
Not only am I a zit faced slob
but *BSD is dying.
Bones: It's dead, Jim.
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.
NetBSD also runs on machines like Dreamcast or Playstation -- and I doubt anyone at a serious enterprise would consider running his/hers business using game consoles. Why does NetBSD community does that? Because it is fun, because people do have unused hardware, which becomes great when it has unix installed, because they _can_.
Porting software to NetBSD's pkgsrc collection brings also a great deal of _learning_ - if you introduce patches, you cannot think just about one platform, you have to think about 52 platforms - your patches must be portable and they cannot break builds on other operating systems.
I recommend NetBSD. Give it a try, not to mention it is very stable operating system, it has a great Linux emulation layer, which runs - among others - latest VMware, Intel C Compiler or Kylix.
And you can do the same for Redhat Linux 9 to any machine and it will work too. Nice try. Being open source, both BSD and Linux suffer from the too many choices syndrome. Does that /etc work on OpenBSD, FreeBSD and NetBSD? I am ignorantly asking, if you'll forgive me.
/etc would be platform specific and would break on other platforms. Maybe if it contained microcode updates for a specific processor; but, hey, you did say "(almost)", so I would assume this still qualifies.
When we look at SuSE vs Redhat vs Debian, etc., we must remind ourselves the myriad of BSDs out on the market as well. I'm still trying to connect exactly what aspects of
Anyway, the whole Linux vs BSD thing doesn't work, just like Emacs vs VI. Just wanted to point out a few things... (I like VI BTW)
... and sleeps with the fishes.
Who else thought some nut had finally ported NetBSD to a kitchen appliance for real?
"I object to doing things that computers can do." -- Olin Shivers, lispers.org
I thought Red Hat discontinued Red Hat Linux?
Neither. Debby does dallas. *rimjob*
Debian is Slow, Worse, Expensive
/lib/modules, as you are going to need it.
Open source may be good, but there is one example that sticks out like a sore thumb as a problem with open source. Debian gnu/Linux. It is offically the Worst Linux Distribution ever made.
First of all, Debian has the most out of date software packages of any major mainstream distros. Even in the unstable version, is KDE 2.2 and Gnome 2.0, with Xfree86 4.1 (A version that really sucks). There are literally years that pass between each update of Debian.
Secondly, its a pain in the goatse to set up, first of all, you are forced to use Kernel 2.2, which is horribly hacked with "backports" to get any use on any modern machine (Read, made after 1999). Good luck memorizing all the *.ko files in
Configuring XFree86 is hell! If you don't have a Thick X11 orilley book, and a list of your horizontal sync values from your monitor's intruction manual (if you even have one), BOOM! There goes your monitor.
Even then, good luck getting anything over 640x480@16 colours.
The most common response to help questions on the Debian mailing list is "n00b, READ THE FUCKING MANUAL, you idiot, go back to WINDOWS XP if you can't learn to use dselect", true too, search the archives if you think I'm lying. Other distros give you comprehensive PRINTED MANUALS, PHONE SUPPPORT and/or freindly forums where repling RTFM gets you banned!
Debians support for any decent hardware, including USB mice, scanners, Sound cards, heck even Serial devices struggle. If you can even get 80x25 text mode with PS/2 input devices you are really lucky.
Apt-get has many flaws. First of all it uses a non standard package format (the rest of the world uses RPM, deprecate the DEB format!), has broken respetories, and out of date software to install. All this combined with the kludgey dselect user interface make package management a nightmare.
And if you think I'm joking about this, find out why THOUSANDS of Debian users are switching to REAL distributions Debian is falling to pieces, if it is to survive any market share it will be through its superior forks (Xandros, Lindows, K/G-noppix) and unoffical package respetories.
Of course, while all this is going on, the only thing the Debian maintainers do is argue about politics on the mailing lists. The distribution decays while its creators argue over inane details like software licensing and the virtues of Marxism. Please! Spare me the political rhetoric and just give me a working distro!
Don't get me wrong, I love Linux, and I'm happily using distros such as Mandrake, SuSE, Gentoo and Fedora. But I'm sick to death of zealots that push obsolete Distros on me EVERY FREAKING TIME linux is mentioned. I'm speaking from real world experiance here.
The GPL is a non-Free license, because it restricts the freedom of what users can do with the software.
We have our own judicial system which should be MORE than sufficent for trying the likes of HIM.
uhg. Oops. Should have been less ambiguous. I meant what are the differences to /etc between platforms (namely i386 and SPARC)? I don't use NetBSD, but I used to (1.6.1, stopped using it because that box died) and I currently use OpenBSD. I'm considering purchasing some SPARC hardware* for another OpenBSD system.
I'm assuming OpenBSD will have some more weird differences because of all the security.
I agree about the pkgsrc/ports thing. I used it on NetBSD and I use it now on OpenBSD. I also use Gentoo and it beats the crap out of Portage.
* - Before anyone says anything, yes I know I'll get more bang for my buck on x86, AMD64, POWER, PowerPC, and quite possibly Itanium.
When someone might yell at me, it has to be OpenBSD.
They both forgot to mention this page...
Manipulate the moderator system! Mod someone as "overrated" today.
Who cares. As long as existant and future versions of NetBSD are available, what do I care if there is an SCOBSD or MSBSD that I will never use.
Case in point: M$ used BSD code in their TCP/IP stack. Oddly enough, the world didn't come to an end, there are still several freely availible BSD releases, and Slashdot users have yet another year of "BSD is dead" and "BSD isn't free" trolls.
What it means in the final analysis is that I can (almost) tar up the /etc directory from a NetBSD 1.6 Sparc machine and expand it into the /etc directory of any x86 or 68000 or MIPS or PPC NetBSD 1.6 machine and it will just work
NetBSD doesn't use fstab?
XF86Config is portable to different videocards/monitors?
Not being a NetBSD user, I didn't gain any understanding of what I am missing from that statement. Could you please elaborate.
A Usenet Troll Triumphs on Slashdot
The troll posted the cid and sid he stole it from for God's sake!
i d= 5012614
http://bsd.slashdot.org/comments.pl?sid=49640&c
The Original Post did qualify that statement with (almost). NetBSD does use fstab and XF86Config would need to be tuned for different video cards. I run two NetBSD systems without X (qube2's as servers), so that wouldn't be a concern for me. The fstabs between any two boxes depends less on the processor/NetBSD version than on the size of the disk and the partition layout.
The key with NetBSD is that the configuration differences apply only to the limited area being configured. fstab would need to be changed to deal with differences betwen filesystems on two systems, not CPUs.
Using the same Linux distro on two different architectures may give the same sort of 'constancy', but typically you can't get one linux distro that runs on all the architectures supported by some linux distro.
Awesome furniture, accessories and cabinetry in Santa Rosa, CA: http://humanity-home.com/
Apart from fstab and the network bits in rc.conf, all the files in /etc that I edit after an install are identical on my SPARC, Vax and x86 machines. There might be minor differences in files that describe devices, but all the files I'm likely to actually edit have the same format regardless of the machines architecture.
Chris
It does use fstab, but the device names may be different.
/dev/sda1 on a sparc machine but /dev/wd0a on an x86.
/ may be on
Network device names are different as well le0 on sparc versus fxp0 on x86.
This is a direct copy (plagerism) from an osnews article. Please give credit where credit is due!
This means, that you can now run your JavaStation with a stock distribution of NetBSD/sparc.
Hey, that's cool. I was actually looking at Javastations a while ago as a candidate to add to my "what the hell is that?" hardware collection.
Unfortunately, they seem to be pretty hard to come by on eBay. Anyone know of a surplus house or anything that's selling off the Javastations at a reasonable price?
--saint
Seriously. The BSD trolls only exist because they know that people like you will take time out of your life to "correct" them, as if they will actually be influenced by what you say and go "Golly jeeze, You're Right!".
Somewhere, in a lonely hospital room,
*BSD is dying
huh?
I've read the SunRay ROM and disassembled the begining 1st startup, PCI enumeration, etc. When I got distracted I sent materials to Uwe (the BSD guy), he completed the disassembly of the 1st stage, and, I think, uncompressed the 2nd stage with the actual software. It was too tedious to continue. SunRay has only 8MB or RAM. Also, debugging without a serial port is a bitch. So we gave up on it.
In fact, Zaitcev (Linux @JS guy) and Uwe (NetBSD @JS guy) are friends, Zaitcev helped Uwe with some elements of the port.
This really makes all "BSD Rulz" zealots look silly. While they whail, real hackers help each other across the Linux/BSD boundary. What is it in OS for a hacker? Linux and BSDs come and go, hackers remain forever.
Never let your emotions get mixed up with something as silly as a computer
operating system. It isn't healthy. So BSD fails. Big whoop. Deal with it and move on.
Hope this helps.
I should know too, I created it.
What it demonstrates is the zealot nature of BSD users. They can't resist replying to such an obvious trolls. They think that it is a serious post.
Oh God I'm laughing so hard now.
you fell for an old cut and paste troll.
but, I have NetBSD i386 machines with sd* (scsi isn't rare) and le* (damn old compaq servers).
apt-get remove moron
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.
Oct. 23 -- BSD resumed receiving life-sustaining care yesterday in a
Florida hospital room, but many experts said there is virtually no hope
that it will ever recover, despite it fan boy's desperate hopes.
"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 De Ratt, 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.
This is because you forgot to include typical BSD zealot phrases such as:
'Oh it just rocks'
'I love it'
The Year of Our Lord 2003 has been a particularly bad year for the "B"s,
- Bob Hope
- Buddy Ebsen
- Buddy Hackett
- Barry White
- BSD
This honored list of dead is but a small token of adieu from the many fans of the deceased.These dead were truly some American Icons. They will be missed.
In a startling turn of events today, a previously little-known fact came into the public eye: "*BSD Sux0rs". This came as a complete surprise to the BUWLA, or BSD Users With Large Assholes, as they previously thought that *BSD 0wned.
"You see, even though I have never contributed code to any BSD project, I thought it was my duty to be a big asshole to others which don't use the OS I do, because it just 0wnz.", said one FreeBSD user. "Now that I know it sux0rs, though, I have to go find something else to be an asshole about."
One notorious OpenBSD fanatic known as WideOpen, told reporters, "I have to kill myself. This isn't how it was supposed to happen. My BSD has always been the best, and shouting that opinion in other people's faces at every chance I got has been my only hobby. It was all I ever did. It was what got me out of bed in the morning. Now I have to die. I will jam my bedpost up my ass until I hit my brain. It is the only way to go: BSD style."
In the volatile world of operating systems anything can happen. "At least we don't sux0r as much as Windows users", BigAzz, a relatively well-known NetBSD user said. "Screaming things in people's faces is my calling. Now I need to scream that BSD sux0rs. What a sad world. At least I won't kill myself like those uber-asshole OpenBSD guys. They are just way over the top. Or were, at least."
Nobody knows for sure what the future holds for the state of operating systems, but with Netcraft confirming the sux0r status, *BSD users all over the world will have to stick something else up their asses from now on or risk looking even more gay than they used to.
Perhaps they love their stupid mascots because they don't know what to do with a woman? Maybe they really like their choice of fat penguin or gay goat over a nice pair of tits with a devil tail. The world may never know.
The Failure of *BSD
Of course we can all agree that BSD is a failure, but why did BSD fail Once you get past the fact that BSD is fragmented between a myriad of incompatible kernels, there is the historical record of failure and of failed operating systems. BSD experienced moderate success about 15 years ago in academic circles. Since then it has been in steady decline. We all know BSD keeps losing market share but why Is it the problematic personalities of many of the key players Or is it larger than their troubled personalities
The record is clear on one thing no operating system has ever come back from the grave. Efforts to resuscitate BSD are one step away from spiritualists wishing to communicate with the dead. As the situation grows more desperate for the adherents of this doomed OS, the sorrow takes hold. An unremitting gloom hangs like a death shroud over a once hopeful BSD community. The hope is gone; a mournful nostalgia has settled in. Now is the end time for BSD.
look at all the anti-BSD trolls that get modded down..
then some anti-Linux troll (and a old copy-and-paste one at that) comes in and it is summarily modded up +5.
Hypocrites.
how does it feel to be a dumbass?
Somewhere, in a lonely hospital room,
*BSD is dying.
Let's think about it for a moment. NetBSD is going down the tubes. Pretty soon it will be gone. Kaput. Adios amigo. Buh-bye NetBSD.
_d8b____________________d8b_______d8,
_?88____________________88P______`8P
__88b__________________d88
__888888b__.d888b,_d888888________88b_.d888b,
__88P_`?8b_?8b,___d8P'_?88________88P_?8b,
_d88,__d88___`?8b_88b__,88b______d88____`?8b
d88'`?88P'`?888P'_`?88P'`88b____d88'_`?888P'
______d8b________________________d8b
______88P________________________88P
_____d88________________________d88
_d888888___d8888b_d888b8b___d888888
d8P'_?88__d8b_,dPd8P'_?88__d8P'_?88
88b__,88b_88b____88b__,88b_88b__,88b
`?88P'`88b`?888P'`?88P'`88b`?88P'`88b
"Do not stand at my hard disk and forever weep.
I am not there; I do not sleep.
I am a thousand winds that blow.
I am the diamond glints on snow.
I am the sunlight on ripened grain.
I am the gentle autumn's rain.
When you reboot in the morning's hush
I am the swift uplifting rush
Of quiet birds in circled flight.
I am the soft stars that shine at night.
Do not stand at my hard disk and forever cry.
I am not there. "
Thought you'd be interested in this little tidbit:
Hope this helps!
- Dave
BSD you grow in the ghetto, living second rate
And your eyes will sing a song of deep hate.
The places you play and where you stay
Looks like one great big alley way.
You'll admire all the numberbook takers,
Thugs, BSD pimps and pushers, and the big money makers.
You are dead *BSD.
You have departed this mortal world.
You are no more.
You are dead *BSd
So very dead.
This troll supported by the letters R, I and P.
don't support an operating system that supports niggers
This crutch and vacant stool have become orphans, not unlike the now dead *BSD. No longer will *BSD hobble about on its cripple's crutch. Like the empty hearth, and the vacant stool, *BSD lies cold and still. *BSD's corpse, lifeless beneath frozen earth and December snows, will see no more Christmas cheer. No, there will be no Christmas ever again for *BSD, for *BSD is dead.
Goodbye, *BSD. The pain of life forever stilled, sleep for all eternity in that long winter's nap. Fade gently into Earth's frozen bosom where in dreams even cripples walk and blind men see.