Slashdot Mirror
New Scheduler Available for FreeBSD
flynn_nrg writes "Luigi Rizzo, one of the FreeBSD developers, has just finished the code for a new scheduler. From the announcement: '...as promised, a first version of the Proportional Share scheduler that we developed is available here. These are for a recent -STABLE (i think any version from 4.4 should work; the only 3 files modified are kern_synch.c, kern_switch.c and
proc.h, plus a one-line change to kern_exit.c).
I have tested it a little bit on a diskless system, and it seems to survive running a full X session with the usual set of xterm,
netscape etc. while i do a "renice" of the processes and even switch back and forth between schedulers. But do not trust this yet for a
production system!'
Read the full post here."
I need to schedule some time to install and play with this new scheduler.
First post, baby!
Fist Sport!
fp
fp baby!
This is neat, I need to get a copy.
We're Doomed
skoal!
kick ass!!! i got the 6th post! woooooo
suckasuckasucka suck it
It's a good thing that multiplexing FIFO locks were added to discombobulate the BSD thrust manifolds.
It's amazing that it held up this long!
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
Isn't this FreeBSD shit already dead?
This is what Freebsd needs, wonder what it will look like when its ported to Darwin?
The Cheap Alternative to Subscribing (Score:1, Offtopic)
:-)
by Starship Trooper on Tuesday March 05, @10:18PM (#3115825) Alter Relationship
(User #523907 Info | http://www.geocities.com/tirnothy | Last Journal: Wednesday June 19, @11:41PM) If you're like me, you're probably wondering just why the hell anyone would pay for Slashdot, let alone want to support it. As it turns out, Slashdot already has all the features you need to completely disable all advertisements without paying those greedy slobs at VA Software a cent. All you need is a DOM-compliant browser, such as Mozilla or Konqueror, and the User Slashbox. With disgustingly-placed new full-page ads [pknet.com] now arriving, the time has come to show that we users will not let ourselves be advertised into submission.
Follow these five easy steps and never see another Slashdot ad again:
1. Go into your Homepage Preferences [slashdot.org].
2. Scroll down to the "User Space" textarea, and paste the following four lines of HTML in there:
(click here [pknet.com] to download the adkiller javascript code and put it on your own webspace, in case you don't trust me
3. Scroll down the list of slashboxes, and make sure the "User Space" checkbox (inexplicably located between "MP3.com" and "Myther.com") is checked.
4. Return to the front page [slashdot.org], and your Slashbox should be there, quietly zapping all iframes and banner-shaped images on the page.
5. There is no step 5!! It's that easy.
There are a few problems, however:
* Opera doesn't seem to work with this at all.
* Internet Explorer won't automatically remove the ads, but by appending the following to the above code:
Click to delete ads and clicking the new link in your Slashbox, the ads will go away.
* The User Slashbox only shows up on index.pl and articles.pl pages, so comment and user pages will still have ads. Luckily, the article pages seem to be the only ones running the obnoxious new full-page ads [pknet.com], so this shouldn't be too annoying.
If you are a Javascript wizard and know how to make this script work on Opera or IE, please tell me. Ad-free Slashdot should be available to everyone!
--
If you like Apple, then please press your right mouse button.
[ Parent ]
I have been using FreeBSD (as well as NetBSD) for a little while (about 2 years) and I have to say that anyone who would care about this would have seen it three days ago on kerneltrap.org or daily.daemonnews.org.
With this new scheduler, *BSD should be able to calculate exactly when *BSD will finally be DEAD.
Rejoice!!1
FreeBSD is great for security! Glad to hear there's an updated version, but if I see any exploits for it soon I;m gonna be upset.
Everyone is entitled to their own opinion. It's just that yours is stupid.
[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 you get distracted by the politickers that they sideline you. The tireless work that you perform keeping the system clean and building is what provides the platform for the obsessives and the prima donnas to have their moments in the sun. In the end, we need you all; in order to go forwards we must first avoid going backwards.
To the paranoid conspiracy theorists - yes, I work for Apple too. No, my resignation wasn't on Steve's direct orders, or in any way related to work I'm doing, may do, may not do, or indeed what was in the tea I had at lunchtime today. It's about real problems that the project faces, real problems that the project has brought upon itself. You can't escape them by inventing excuses about outside influence, the problem stems from within.
To the politically obsessed - give it a break, if you can. No, the project isn't a lemonade stand anymore, but it's not a world-spanning corporate juggernaut either and some of the more grandiose visions going around are in need of a solid dose of reality. Keep it simple, stupid.
To the grandstanders, the prima donnas, and anyone that thinks that they can hold the project to ransom for their own agenda - give it a break, if you can. When the current core were elected, we took a conscious stand against vigorous sanctions, and some of you have exploited that. A new core is going to have to decide whether to repeat this mistake or get tough. I hope they learn from our errors.
Future
I started work on FreeBSD because it was fun. If I'm going to continue, it has to be fun again. There are things I still feel obligated to do, and with any luck I'll find the time to meet those obligations.
However I don't feel an obligation to get involved in the political mess the project is in right now. I tried, I burnt out. I don't feel that my efforts were worthwhile. So I won't be standing for election, I won't be shouting from the sidelines, and I probably won't vote in the next round of ballots.
You could say I'm packing up my toys. I'm not going home just yet, but I'm not going to play unless you can work out how to make the project somewhere fun to be again.
= Mike
--
As a tempest roared within the Project Faustus network, I felt myself inexplicably drawn towards the eye of the storm. Something gargatuan sent a shudder through Faustus, taxing their hive of supercomputers. My journey towards the center was full of starts, stops, and retransmits.
As I creeped through the electronic void, I began to perceive order out of the chaos. At one level, the network was a swarming mass of frenetic electrons. At another level, it was a carefully ordered expressway of packets zeroing in on their target address. Such perceptions were natural to me...but now, as I traversed through the digital world, I realized that I had a third perception...
I was no longer in formless chasm. I discerned a muddled grey mass slapping back and forth on itself. I heard the lapping noises...this was like the big wet that enveloped me during my time with Cora. I was in a three-dimensional world. Turning my perceptions onto myself, I realized that I was a part of this strange artificial world as well. My new form resembled a human shape, but it was not defined in the way of any particular human. I possessed no hair, features, or even fingernails. I allowed myself scarcely a microsecond to ponder this new form...it mattered not. Forces beyond my control were dragging me to the "center" of the Project Faustus network-the cause of all the activity.
I bobbed along, adhering to the physics of this large amorphous structure, until the muddy grey turned a brilliant azure. The all-encompassing blue ceded to solid green, returning a match in my memory to the park across the street from my ATM enclosure.
As a matter of fact, the pattern of flora and their spatial relationship was identical to the stand of trees in that very park. As I shifted perceptions, I could see the same stand expressed in code, over and over again.
A queasiness washed over me as I walked through this seemingly endless maze. The trees and flowers were not in perfect parity with their real-world counterparts. Colors were too bright, shapes were too flat. The whole atmosphere seemed confined, airless.
Beneath this gaudy veneer, I felt the nexus point of the disruption. The usurper of Project Faustus' massive computing power was close...
As this thought glided past my CONSCIOUSNESS-BUFFER, I saw a break in the infinite stands of trees...the park bench. Two figures on the bench, deep in conversation. And as I drew closer...
First figure...recognition triggered-positive identification. "HOST GEEK" Second figure...recognition triggered...positive identification. No match found.
"Who might you be?" said the mystery figure politely. This man was dressed similarly to my host geek, but extremely well-muscled. His complexion was darker, and he wore a ring of dark hair around his mouth, and another long cluster ran down the back of his neck. A tiny smile played across his lips as he looked me over.
"Weird!" said my host geek. "This guy doesn't really look like anything!"
"He's got the default skin for the system," said the other man. Then he turned to me. "So, you wanna explain yourself?"
"I have come to destroy Project Faustus." I stated.
"Machiney!" exclaimed my host geek, attempting to embrace me (causing an anomolous collision). "This is Guy. He was trapped by Project Faustus too. He used to work for 'em."
"That's right," said Guy, pulling at his chin hair-ring. "I was gonna be killed by the Project for doing some pretty nasty things. Luckily I beamed myself in here. They thought I committed suicide...I haven't been free to move around until that bit of trouble they've been having. Wonder what caused that?" he said with a nervous laugh.
"Yeah-we were both set free from our prisons when that huge ripple started happening, and we met each other here in the middle. Guy here built the whole network, this whole digital world and everything! Isn't that awesome? I've been telling him all about you!" said the host geek.
"Guy! Oh my Gawd! Guy!" another voice parabolized across the airless digital realm. "Ah knew it was yew all along! Yew couldn't be dead!"
"Bubba." Guy replied without emotion.
"It's goin' to hell in a handbasket at the Project!" ejaculated Finn. "Guy-you were right about it! And I knew you were doin' this...I knew you coaunnabin dead!"
"Fuck you Bubba, you turned me in." Guy's eyes turned to slits, and he turned away from the rapidly advancing figure of Dr. Bubba Finn.
"Guy...no!" said Finn, growing increasingly desperate. He ran towards Guy, and attempted to make familiar physical contact. "You don't understand...I love you!"
Tears trickled from Finn's chin as everyone stood silently. I increased the priority of my analysis of Montevideo. The data was beginning to confirm what the electrons deep below had been telling me all along...
Guy noticed it first-as I was delving further into his code, we were being drawn together. My own form began to resemble his own. He violently pulled away from me, gouging a black rift into the sky. Finn and the geek dove behind a tree. "What-what are you doing?" yelled Guy frantically.
"You have taken control of the Project Faustus network." I replied. "You are using the Project's own plan of financial cataclysm and usurpation to force people to enter this digital world. You must be stopped, Guy Montevideo."
What is the purported advantage of the new scheduler?
Sigmund
what the hell happenned to developing SMP and UP capable schedulers ? or does BSD expect to run well on only UP systems ?
Why does this get on the main page, and why does the new Core Team does not?
:)
Either way, FreeBSD does fit the new trend now... more VM's means more freedom
First off I must admit that I am a staunch supporter of President Bush's 'War On Terror'. However when I first read this article (The Drudge Report is my AOL homepage), I thought it was a stupid idea to even consider recruiting someone above the age of 16 to spy on their neighbours. The best way to go about this would be to teach young children to keep a close eye upon their parents and neighbours. This would best be taught in the state run schools that cost so much tax payer money, and refuse to swear to the Pledge of Alligance. By teaching them to watch over America, there would be a huge re-injection of patriotism back into the education system. Using children, has a number of advantages because children are more likely to go along with orders delivered by a state authority. Secondly, they are innocent, and would be able to gather information readily without raising suspicions of the terrorists they would surveil. And lastly they could be rewarded easily and cheaply with videogames and candy etc. Lastly, the Boy Scouts of America could be put to use, by doing reconnaissance missions in the remoter regions of the American wilderness; the Girl Guides could supply them with food. I'm sure the terrorist camp in Oregon would never of formed if there were 100 Boy Scouts roaming the wilderness looking for Arabs every weekend. In general I support the idea, but think it needs to be reworked to include only children to be the most effective.
It has to be a miracle. Something actually makes the front page on slashdot that isn't part of the Linux-nazi empire. I can't believe it.
Now, I know for a fact that if I was logged in as myself, I'd get a "Bad Karma", Slashdot really needs to get into the flow; get their act together; and post better stuff about FreeBSD. Why doesn't a FreeBSD release make front page, but a FreeBSD Scheduler does.. doesn't make much sense does it..
Well, for all you Linux fokes who think *BSD is dead, your far from the correct answer. *BSD has been gaining market share as users that use Linux are fed up with the crashing & exploits, and considering a code that wipes out the filesystem in the "STABLE" branch. It can't be that stable if it wipes out your FS. FreeBSD has *NEVER* had anything like that happen.
On top of that, Slashdot should be renamed to Linux Nazi News, Stuff that people don't care about.
--Anonymous "Non-Linux" Coward. aka Bad Karma
There's more info here.
Excerpt:
"There are compelling reasons to use proportional share scheduling techniques to support multimedia and other soft real-time applications on general-purpose operating systems. First, proportional share (PS) schedulers are a good match for existing infrastructure such as a periodic timer interrupt and mechanisms for assigning priorities to applications -- priorities can be mapped to shares in a proportional-share environment. Second, PS schedulers provide stronger guarantees to applications than do traditional time-sharing schedulers: they allocate a specific fraction of the CPU to each thread, and some schedulers provide error bounds on the allocation rate. Third, PS schedulers have clear semantics during underload: excess CPU time is allocated fairly, in contrast with some reservation-based schedulers that must idle or back off to a secondary scheduling policy once all application budgets are exhausted."
Im currently using linux with the low latency patch and pre-emptive multitasking. Does this help X seem a little smoother on BSD also?
It's very sad (not really). It seems this "Less moderating will kill trolling" idea is working. By not giving trolls extra attention (by modding them down), they seem to get frustrated and many have quit. Seems some people do just want attention, even if it is negative.
Credits: anonymous
/. since 7/8/02
"Mmmm... this feels good..." I sighed.
"Shhh!" hissed Hemos. "We don't want Mark to come in here!"
True. Having Hemos's 16 year-old brother walk in on us at that moment would not be good. I didn't think he'd be too cool with finding his 12 year-old brother lying naked with me, holding my 11 year-old dick in his hands. But, in all fairness, my hands were eagerly playing with Hemos's dick and balls at that moment, too.
Hemos's mom and dad had gone to the drive-in, leaving his big brother in charge. In our favor, leaving Mark in charge pretty much guaranteed that we weren't to bother him, and in turn, he'd leave us alone unless we were making too much noise or breaking something. Well, we were being careful to keep quiet because we very much wanted to be left alone.
We were in Hemos's twin bed, snuggled under the covers with our underwear pushed down to the foot of the bed. The only illumination in the room came from the faint sliver of light that crept in under his bedroom door. Even in the shadows I could make out the shape of my friend; about my height, but heavier. (Hell, I was such a skinny runt that everyone was heavier than me.) Hemos had a crew-cut of white-blonde hair, and was only starting to sprout some pubic hair. But, you had to feel for it because what little pubic hair he possessed was as blonde as the short hair on his hea and could not yet be seen by even a minimal distance.
And, I was happily feeling for it, running my hands all over Hemos's slightly larger erection and fondling his larger testicles while he courteously stroked my dick. I could tell that he didn't possess the same enthusiasm for cockplay as I did, unless you count his appreciation for the attention devoted to his member. And I knew that my willingness to satisfy his sexual urges was one of the few reasons he even had me sleep over at his place. But, I didn't let that stop me from finding pleasure in the handling of his meat.
I'd recently had an "introduction", of sorts, to seeing what someone could do with a man's dick with their mouth. While spending the night with my Uncle Jerry a couple weeks before, while I watched in secret, I was treated to a visual display of the intensity and unabashed pleasure that my uncle had obviously enjoyed having another man suck on his cock. From that moment on, I had a yearning that I needed to satisfy. With who was my only question.
I guess it was time to find out.
"I... heard that sucking on it feels even better than playing with it." I ventured.
In the darkness, I could feel a slight jerk of revulsion in Hemos's body.
"Put a dick in your mouth?" he croaked.
"Well, " I countered, my heart pounding with anxiety, "I think adults do it all the time."
"Well, I'm not gonna do it!" Hemos hissed. "That's homo stuff!"
"Yeah." I sighed disappointedly, while still playing with Hemos's dick. "I guess it is."
As I stroked his shaft in a steadier, milking rhythm, I could sense Hemos's breaths getting quicker. His manipulations of my dick began to falter as I could feel his body tense beside me. His hips rocked slightly in time with my pumping of his cock, and I cradled his balls tenderly in my other hand. When any attentions to my own dick has completely ebbed, I knew what was about to happen, so I picked up the pace just a bit more while lending a touch more pressure in my grip. Finally, Hemos's breath caught in his throat, and he turned his face fully into his pillow to stifle the moans that broke free as his cock pulsed and throbbed in a dry orgasm within my hands. I continued to massage him and didn't release him from my grasp until his member had gone fully soft.
"Man," sighed Hemos dreamily after finally catching his breath. "You are so good at that, CmdrTaco."
At least I had something to be proud of, I guess, as my friend gently withdrew himself from me and rolled onto his back.
Even though I was only eleven, the irony of Hemos's words and actions were not lost on me. My sucking on him would have been a "homo" thing, but beating him off was okay. Go figure. Within the few moments I had spent mulling over the irony of the thoughts, Hemos had drifted off to sleep. I slipped out from under the covers and down to the cool floor so I could masturbate without shaking the bed. As I toyed with my own dick, I imagined Hemos's cock in my mouth, wondering if the chance would ever really come. Finally, my own climax washed over me, and I got back into the bed.
I don't sleep real well to begin with, and even worse when I'm not in my own bed. And now, with the thoughts of a dick so close to me, as well as the vivid memories of secretly seeing man-to-man cocksucking pleasure floating through my prepubescent, sex-filled brain, I was not about to fall asleep anytime soon. Lying awake until around 11:30, I finally decided that I needed to do something to satisfy my hungers, or I'd never be able to let it rest. The trick was in finding the guts to follow through.
I knew that whenever Hemos fell asleep, he pretty much stayed asleep. So, since he was sleeping soundly, lying on his back, I took a deep breath and gingerly ducked my head under the covers and scooted down as much as I could to the foot of the bed. That put my head right at Hemos's hip level. I raised my head and upper body to help create a tent over his crotch. Sniffing around, I found the faint scent of young penis flesh. I inhaled deeply, both in the love of the scent, and in an attempt to slow my pounding heart. I opened my mouth wide over the area where I sensed Hemos's dick to be, and lowered my mouth squarely over his soft cock and balls until I could feel his sparse pubic hairs tickling my cheek. I finally had a dick in my mouth! I just wasn't sure what I'd do if Hemos woke to find his "homo" friend in this situation.
I remained like that for a long moment, partially in fear of trying anything more, and partly to savor the moment. I carefully let my tongue start to explore his tender penile flesh, enjoying the texture. Then came the excitement that welled within me as his cock began to respond to my attentions and harden in my warm and wet mouth! Butterflies seemed to explode in my stomach and drown out my heartbeat as I felt his dick get to its full size in my mouth. Concentrating in that dark environment, I found myself beginning to identify the shape of his member by taste. The shaft actually seemed to taste different than the head, and the thin skin of his scrotum seemed to harbor another distinct flavor.
I started to softly suck on Hemos's dick, becoming fascinated at how it just seemed to, well, 'fit' in my mouth... how the head lent itself to the back of my tongue, and how the shaft rested between my tongue and the roof of my mouth. My excitement was so great that my own recently satisfied dick was responding again, inviting me to play. I was sucking a cock, and I was in heaven!
However, within seconds, Hemos seemed to get restless. In fear, I quickly pulled my mouth away from Hemos's candy stick and held still. The covers rustled, and pulled back.
"Whatcha doin'?" mumbled Hemos.
"I... uh... was trying to find my shorts down here," I lied, starting to fumble near our feet. Well, partial lie, because it was a good idea to do so, anyway, and now was as good a time as any.
"Oh, yeah," said Hemos. "Get mine, too, willya?"
"S-sure" I stammered, relieved.
I located the two items of clothing and scooted back up towards the head of the bed. Thankfully, our underwear were pretty easy to distinguish since Hemos wore boxers, and I wore briefs. We both fumbled to put them on in the dark, and then settled back into the bed. I lay stiffly on my back, still harboring some fear that my friend discovered more than he let on, but Hemos simply rolled onto his side, facing away from me, and promptly went back to sleep.
And, here I was again, so close to my fantasies, yet still so far.
And very much awake.
After hearing the clock in the hallway chime midnight, I finally got up to go to the bathroom. Figuring it was late enough not to be an issue, and since even if Hemos's parents were home that they would be in their own bedroom downstairs, I didn't bother to slip on my pants for the short trip down the hall. I walked softly to the bedroom door, and then stepped out into the hallway, illuminated dimly by a bare-bulb night light. I walked past big brother Mark's door to the bathroom at the end of the hall and turned on the light as I shut the door.
Peeing into the toilet, I looked up at my reflection in the large mirror and smiled slyly to myself. I actually sucked on a dick, even if for only a moment! At that moment I was Rob Maldo, secret agent double-O-seven, who could sneak in and suck a dick, and sneak away without being caught!
I flushed the toilet and switched out the light as I headed back down the hall. Slipping past Mark's door once again, the door flew open, and a hand covered my mouth while a muscular arm snapped around my waist and drew me into the room. Squirming in the arms of Hemos's athletic older brother was a waste of effort, and he only squeezed harder until I settled down.
"You'll keep quiet if you know what's good for you,' growled Mark into my ear. "You gonna be quiet?"
I nodded. Mark let go of my mouth and reached over to close his bedroom door, the other hand and arm still holding me firmly with my feet off the ground. I heard something click, and recalled, and not without a certain amount of childish fear, that Mark had a lock on his door.
The room had a yellowish glow from the large lava lamp next to Mark's bed. He took me over to the bed and tossed me face down onto it, kneeling next to me. I thought briefly about trying to get up and run, but to where?
When I felt Mark's hands on me again, I was determined to fight him off, but I was no match for him as he flipped me onto my back and straddled me, sitting squarely on my upper chest, his knees pinning my shoulders and my arms locked between his legs. I gazed up at his lean, muscled torso, his stern blue eyes under a tussled mane of reddish-blonde hair. I could feel the soft fabric of his boxers against my chin.
"Can't get up, can ya?" he said, grinning down at me, all snide and victorious.
I struggled a bit, more out of obligation, but knew it was no use. Mark was just too big for me.
"Whatsamatter?" huffed Mark. "You too weak to fight? Or, maybe you just like laying there, sniffing dicks?"
I started squirming a bit harder, but Mark's legs only clamped tighter. At least he had scooted down a bit, and was no longer suffocating me with his weight on my chest.
"Yeah! Maybe you're a homo-boy who just likes sniffing dicks. Maybe you wanna sniff my big dick?"
I didn't care for where this was going, and I wasn't too comfortable with the tone of Mark's voice. But, I was also not being given much of a choice in the matter. Especially when Mark reached into the fly of his boxers and pulled out his cock.
"Here you are, homo-boy... a nice, fresh big-man dick!" grinned Mark fiendishly. "Ain't it a beaut?"
He held it out for me, then leaned forward and started to rub his cock on my face, tracing my cheeks and nose with the bulbous head. His testicles soon followed his dick through the opening, until they were dangling on my chin, the coarse pubes tickling my lips. Their faint musky scent began to fill my nostrils.
"CmdrTaco's just a little dick-faced homo-boy, ain't he?" sneered Mark, sliding his cock across my face. "I saw you in there, your head under the covers. What were you doing? Giving my little brother a blow job?"
I didn't answer. I was at once shocked at the thought of having been discovered, and confused by Mark's remark. I then guessed that he meant sucking a dick was called a 'blow job'. But... you're not blowing, you're sucking, and-
"You were, weren't you, you little homo!"
It was obvious what had happened; that Mark had looked in on us to find my head under the blankets. I thought I had sensed a miniscule change in the light, but assumed that to be part of my excitement. That must have been what woke Hemos up so suddenly.
"So, maybe you aren't just dick-faced, " he said, rubbing his cock on my face again. "Maybe you're a dick sucker!" He leaned forward, mashing his hairy ball sack into my nose, then pulling back to trace my features again with his member. But, even as Mark taunted me, treating his cock as a threatening weapon, there was something else happening.
He was getting a boner.
And as I closed my eyes, I could feel his cock thickening against my face. I could sense the heat of his hardening dick directly on my flesh. And, I found I was enjoying the sensations of this older cock against my face. There would soon be no way of hiding the fact that I was getting excited, too.
"So, dick-sucker-CmdrTaco... you're gonna suck my dick, now."
My eyes sprung open to see Mark's fully erect cock pointing at my face. While it wasn't huge (I had already seen 'huge' with my Uncle Jerry), it was still big enough to scare me.
And excite me to no end.
"Open wide, homo-boy."
Without another moment of hesitation, or taking my eyes off of Mark's sleek tool, I opened my mouth as wide as I could and watched as he leaned down and slid that beautiful cock into my waiting mouth. I then settled my tongue against the bottom half of his shaft while I could feel the upper half press against the roof of my mouth. Its texture was soft, yet hard; smooth, yet distinct.
"There," he sighed. "Now, you have a real dick to suck on. Now, get started, suck-boy!"
It was so much bigger than Hemos's young dick, I wasn't sure if I could get enough suction worked up to suck on it. It was then that I found out what sucking a cock is really all about: friction.
Mark held the base of his dick to guide himself and started to pump into my mouth, sliding his dick in and out of my salivating lips. He would slip in precariously between my teeth until he was near to choke me, then pull back out until the base of the bulbous head was just close to popping free from my lips, held in place by the suction of my mouth. Then he... we... would do it all over again... over and over... and gloriously over again.
"Oh, you are good, CmdrTaco," he moaned softly. "You suck cock real good."
I don't know about that; it seemed he was doing all the real work. But, I wanted it to be good. I wanted to have this dick in my mouth. And I wanted it again and again. I was definitely enjoying the oral sensations as his near-adult dick worked back and forth in my hungry mouth, and I wanted so much to please him so he would want my mouth again.
Mark placed his other hand on the top of my head to steady me as his thrusts became a little more erratic. His breath quickened, and I could sense that he was trying hard not to ram himself all the way down my throat and choke me. He was making little grunts with each thrust, and I could feel his dick turn to stone in my mouth when, in a mix of fear and excitement, I suddenly recalled what would happen next.
"Oh, baby... oh, fuck..."
Mark's movements got all quick and jerky. I was almost afraid to breathe.
"OHHHH!!!" he moaned, pulling out of my mouth and letting loose with a burst of white goo that seemed to splatter all over as he pumped his dick with his fist. My head still held firmly in his other hand, the warm liquid flew partly into my still open mouth, and all over my nose and eyebrows. I swallowed briefly, not sure whether to gag or hope for more, tasting fully the salty and musky liquid, then opened my mouth once more as Mark stuck his creaming cock back in and worked the thick fluid throughout my young mouth.
I sucked until Mark went soft and withdrew his spent dick. He smiled down at me, obviously proud of what he had done. He finally got off of me (good thing since I thought my arms were going to fall off) and stood there for a moment, an interesting picture with his hands on his hips, and his drained cock and balls hanging out of the fly of his plaid boxers. I just lay there with his juices clinging to my skin, wanting to do it all over again.
Mark bent down and picked up a t-shirt, and proceeded to wipe the remainder of his goo off my face. Finished with that, he tossed the shirt into a hamper and walked over to his bedroom door to unlock it as he tucked his manhood back into his underwear.
"You better get back into Hemos's bed before mom and dad find you here," he said softly.
I reluctantly got off Mark's bed and walked to the door. As I was about to exit, he reached out to stop me briefly.
"You liked that, didn't you, homo-boy?"
I nodded, not sure where he was going with this inquiry.
"Your first taste of cum?"
I shrugged, then nodded again.
"If you're good, maybe I'll let you suck my dick again some time, CmdrTaco. Now, get your ass out of here before I kick it."
I stepped out of the room and felt the door close harshly behind me. I could still taste traces of Mark's cum in my mouth, could still sense the friction of his cock on my tongue. I smiled in remembrance.
I was hooked.
Trolling
whore, karma.
Can anyone tell me ANY Unix software that claims to be ready for a production enviroment?
chode lover
Is FreeBSD's new one a 0(1) scheduler?
0(1) is a "term" from computer science. When applied to schedulers, it basically means that no matter how many processes there are to schedule, a 0(1) scheduler's overhead will not significantly increase.
Of course, with a small number of threads/processes to schedule, the Linux 0(1) scheduler will have greater initial overhead. It isn't until there are quite a few processes that it starts to show its power, and the more processes there are, the more useful it is.
On a busy server with 4+ processors and thousands of processes, a standard scheduler's overhead is so great that it often exceeds the overhead of most of the individual server processes.
Computer Science is no more about computers than astronomy is about telescopes. --E. W. Dijkstra
Anybody have any idea when/if Apple will integrate improvements from this scheduler in to Darwin/OSX?
A Linux user goes back.
/etc/fstab file so that it always automounted when plugged in. I was very impressed.
/dev/null, once I find where that actually is.
By Tony âoekNIGitsâ Collins.
Introduction...
In much of today's online news, we hear of how many people are migrating to GNU/Linux. What we don't seem to hear much of, is users going back to their old operating systems. The reason for this article is to say that I've done just that.
Yes, I've gone back. After three and a half years of trying to make GNU/Linux work on the desktop, I've decided that it's simply too hard for the average home user. Before I go into my reasons for going back, let me outline what I believe an 'average' home user is. Mr Joe Average is someone who wants to install their OS, boot it up, and it works. He wants to be able to upgrade his PC , and have the hardware work in a few short minutes. He wants to read email, browse the web, talk to his mates online, and play some games. Feel free to disagree with me, this is merely how I see myself. Note: I'm not referring to Grandma using Linux, or even my mum using it. I'm referring to average users who know a little about their computer.
Three and a half years; that's how long I've been trying to make Linux work on my desktop computer. Right about now, I'm sure that you are now screaming that I didn't try hard enough, or that I'm just plain stupid. Let me assure you that this is not the case. Stupid users don't doggedly stick at something for three and a half years, trying distribution after distribution in the hope of finding the holy grail of Linux desktops. They give up in less than a few hours of trying to (unsuccessfully) install RedHat Linux. Hear now my sad tale of why Linux isn't suitable for my desktop.
Some background...
The year is 1998. I've had my Windows '95 computer for around six months. Frustrated with the constant crashes, I desperately asked an online mate for help. Even though he was a windows user, he calmly suggested that I try something I'd never come across before...
âoeLinux, eh? Never heard of it.â
âoeOh, it's a free OS that you can download. Apparently it doesn't crash much. Just do an online search for it.â
Armed with this meagre knowledge, I set out on my quest for the ultimate stable operating system. I searched online, and found places where you could even buy copies of Linux! So, I left the comfort of my warm study, and returned forty minutes later with my first Linux boxed set â" RedHat Linux 5.2. After initially balking at the very basic installer (and few false starts), I had it up and running on my lovely AMD K6-233. I even got X working in no time at all. Then the system booted up for the first time.... and it was dead ugly. I had a very stable new OS, but I didn't even want to look at it. I was happy that I had several installed interfaces to choose from, but none of them appealed to me whatsoever. Wanting to download a nicer interface led me to my next problem.
I had absolutely no idea how to even get this nice, stable OS onto the internet! After reinstalling windows and RedHat in a dual-boot configuration, I got the help I needed by using Windows and USENET. Strangely enough, I can still remember the name of the long-suffering person who helped me get RedHat online, but that's another story. After looking around online, I discovered KDE. Only up to version one, it was the closest thing I had to a completely useable Linux system. I downloaded all the KDE packages for RedHat 5.2, only to discover another distro called Mandrake, that came with KDE preinstalled and configured. Back to my local distributor, and I was set.
Mandrake with KDE was exactly what I needed at that stage in my Linux using life, and I stuck with it for over a year and a half. Always seeking the 'perfect' desktop OS, I followed releases from version 5.3 all the way through to 7.0. Eventually I became dissatisfied with Mandrake, and briefly tried a number of other distros until I finally settled on Debian. I was impressed by the simple power, configurability, and the ease of upgrade that is apt-get. I felt good about being among the uber-elite Debian user community. Needless to say, I learned a lot about how to configure hardware under Linux during my time with Debian. I learned to sift through the old HOWTOs on Linux Doc until I found something suitable and accurate, I learned to utilize the power of USENET and IRC. Life was good.
Right now you must be wondering; âoeWhere is this leading? This guy seemed quite happy with Linux!â. True, I was. After a while, I decided I didn't want to have fine-grained control. I wanted something simple. I was getting tired of the 'stable' Debian release being so out of date, and the 'unstable' distribution being so... well... unstable. I got tired of having to recompile my kernel every time I got new hardware. I got tired of using command line to talk to my PC. It was time for a change. I had good experiences years ago with Mandrake, so I figured I'd try it again. As good as Mandrake 8.1 was, it wasn't what I was after. SuSE Linux 8.0 Professional (boxed set) was installed onto my PC instead.
I have to stop at this point, and say that SuSE Linux 8.0 (Pro) is the best Linux distribution that I've ever used. It has an easy installer, reasonable hardware support, and comes with the very good KDE 3.0. The box contains seven CDROMS, one DVD and three decent books that would help even the most inexperienced user get up and going. YaST2 is a decent graphical system configuration tool. When (not if) I go back to Linux, I'll definitely try SuSE again. However, there are quite a number of things that have improve (or change completely) before I'll consider going back. Read on for my brief list of things that must must get better before I'll switch back from the Microsoft camp.
Where GNU/Linux needs to improve...
X11
The X Window System is an awesomely powerful, network transparent graphical subsystem. It's perfectly suited to running applications from remote servers. However, this is NOT what a home user needs. My experience with X is that it's too big, bloated, slow and unstable to be any good to the home user. Most crashes that I ever experienced with Linux have been X's fault. My servers don't run X, and they never crash.
What home users need is something small and fast, so they can run local applications efficiently. I would like to see the X Window System dumped in favour of a hardware accelerated framebuffer, running something like directFB or Qtopia. Home users need a small, fast graphical subsystem, with built in 3d support. BeOS seemed to be on the right track before they went under.
Fonts are truly awful under X. Most distributions ship with appalling fonts, and there is no standard way to add additional (nicer) fonts to the system. Even after extra fonts have eventually been added, many applications (eg Abiword, Staroffice) refuse to use the new fonts anyway. Perhaps the framebuffer-based graphical subsystem I suggested could incorporate decent font support, and use a readable naming scheme as well.
Drivers
While having access to the latest version of the kernel is a good thing for developers, for home users it can be a nightmare. Got RedHat Linux 7.3? Perhaps you run SuSE 7.3 or Debian 2.2. You'll have to download a binary package specific to your distro. (I'm assuming that home users won't change their default kernel, but if they did, that binary package wouldn't even work!) Hardware manufacturers should be able to provide one single driver that works on all minor versions of a major kernel release. This way it would work will all current distros, instead of having to provide multiple binaries or source code. Hardware manufacturers don't want to give out the source, as this often gives away trade secrets about how their hardware is designed.
The solution seems to be to make binary drivers work on a variety of kernel versions. I'm not sure if this is even possible with the way the kernel is designed (I'm no kernel hacker), but it would go a long way toward making Linux more accessible to the home user. Even if the kernel needs to be redesigned to support this, then in my opinion, it should be done. Linux users are always clamouring for drivers... perhaps if the kernel had something like this, it might one day become a reality.
Hardware setup
While SuSE Linux 8.0 gave me some good experiences with hardware detection (such as automatic download of NVIDIA drivers), it also let me down as in this area.
The good: I recently borrowed a digital camera from a mate at work, to take photos of my case mod. Imagine how happy I was when I plugged it into my nearest USB port, and it was automatically configured (as a SCSI device) and mounted! SuSE even added it to my
The bad: Along came my new IDE CDRW drive. At AU$99, I couldn't pass up the purchase. Plugging it in gave me no joy. I was very disappointed that a device so common couldn't be detected and automatically configured under a modern operating system. The instructions on the SuSE support site said to add lines to lilo.conf and reboot. While this is a perfectly acceptable way to get hardware working for a geek familiar with *NIX, I believe that a home user shouldn't have to do more than plug it in. It's an IDE device, it's not that complicated!
The ugly: Once the hardware was finally working (as a pseudo-scsi drive), the next hurdle was to find decent graphical tools to burn and copy CDs. I finally settled on CDBakeOven, an above average KDE application. It burned CDs from data on the hard drive, but for some reason cdrecord (the command line backend) refused to allow me to copy a cd directly. Yes, it was installed SUID root. CD copying is such a basic function nowadays, why is it so hard to do under GNU/Linux?
Software distribution
I'll put this simply. I'm a home user, not a programmer. Why on earth should I have to compile the software I want to use? I know that having the source available is a good thing, but I'll say it again: I'm no programmer. I just want to install software and run it.
This leads to another point. Although having package databases (such as the rpm and deb systems use) is great, there should definitely be seperation between system packages and additionally installed software. There needs to be a standard installer and database for user-installed applications such as word processors, email clients and games, and it should be seperate from the rpm or deb databases used for system software such as lilo, init and cron. This will make it much easier for home users to know what applications they have installed on their PC, and to easily uninstall them if necessary, without knowing some arcane commands and weird package names.
Support
There is a huge wealth of knowledge among the thousands (millions?) of people that run GNU/Linux around the world. If you have a problem, odds are that someone out there can help you, often for free. This is one of the linux platform's greatest strengths. However, Linux users are also its greatest weakness. This may not apply to most of the community, but there is a very vocal minority that gives Linux a bad name. To every Linux user that has ever helped a newbie, I thank you. I have been helped by many a guru, often when I've been asking the simplest of questions. It's the remainder that are a problem.
I once heard a song by Three Dead Trolls in a Baggie called Every OS Sucks, where Linux users were described as 'elitist nerdy shmucks'. Sadly this is true for much of the 'community'. Too many consider themselves better than the rest of the world because they run Linux. Can you believe that? It's just a computer operating system, but somehow they think that it makes them better than those people who run systems such as Microsoft Windows! Elitism drives people away, as does saying âoeRTFMâ or belittling people who choose a different distro from yourself.
'Nuff said about that.
So what now?
Well, I decided to go back to a Microsoft platform. Initially being paranoid after reading things about DRM and spyware, I bit the bullet and installed Microsoft Windows XP. Like every OS, it has good and bad points; most of which you can learn about from online reviewers. I'll just point out several things that make me want to keep using it instead of GNU/Linux.
Fast graphical subsystem: Windows has lighting quick graphics, both 2d and 3d. There's no denying it. When I move a window, it refreshes so fast that I don't miss X11 at all. While not quite as nice as some other operating systems, font support is outstanding compared to XFree86.
Drivers: Point and click to install (as a superuser, of course). Windows warns you if the driver isn't likely to work properly, and can roll back to working drivers if you deliberately choose to install one that hoses your system.
Hardware setup: My CDRW worked right away, without a hitch. I am able to drag and drop files from the Explorer file manager to the CDRW icon and they get added to the list of things to burn. A quick install of Nero Burning Rom, and I was able to make a backup copy of my game CDs. (I don't like taking originals to LANs where they can get destroyed or stolen).
Software distribution: All windows software comes in binaries, either with an installer or in a zip file. I hope to never compile an application ever again. Software designed for a different version of windows is 99% guaranteed to run, but if not, there is always 'compatibility mode'. One thing to note, however: Applications designed for single user versions of windows usually only run properly as a superuser, and this includes 3d games. I expect this to be rectified as the rest of the Windows world catches up to a multi-user environment.
I can't comment on the Windows using community yet. I've not yet had a problem that a simple point and click couldn't fix. However, I will say that my original concern with Windows '95 has been addressed in Windows XP. The stability is finally there.
Final Notes
In conclusion, I'd just like to make it known that I haven't completely abandoned the Linux community. My home server still runs Mandrake, and IPCop on my gateway/firewall. There is no way I'd ever put any form of Windows on my server, nor would I ever connect a Windows PC directly to the internet without a *NIX gateway in between. Microsoft has a history of poor security, so I protect myself the only way I know how; using Linux. I will continue to advocate the use of GNU/Linux in the server arena. This is where its strength lies at the moment.
Because of their history of spreading virii, I don't use the applications that Microsoft has provided with Windows XP. My wife and I use Mozilla for web browsing and email, OpenOffice.org for word processing, and Psi (Jabber client) for instant messaging. All of these are true multi-user win32 programs, and are perfectly interoperable with their Linux counterparts.
I expect that the Linux community will have something to say about this article; I welcome comments and constructive criticism. Flames will be automatically sent to the Windows equivalent of
By Tony âoekNIGitsâ Collins
- posted by poopbot: for all your crapflooding needs
Hydr2etO8v Post #362
Copying over scheduler code from one kernel to a completely different one is not trivial. I would expect OS X to just go along with whatever people are doing with Mach. All the BSD stuff in Mac OS X is just user-space stuff.
I am not going to claim that FreeBSD is perfect, but FreeBSD is more secure than the vast majority of Linux-based OSes. It has supported features like the new "GR Security" patch for years, and because it shares a great deal of code with OpenBSD which is audited frequently, it benefits from their work as well.
:)
Of note is that FreeBSD's libc is just over half the size of Linux's Glibc (not that has a thing to do with security)
With FreeBSD, for years, admins have been able to set certain files as "append only" (so even root can only add to, not remove from, log files) and "immutable" (so even root cannot modify or delete the file) and has been able to set firewall rules to the same (immutable) so that creative crackers can't add their personal favorites if they root the system.
This can of course be bypassed by restarting the machine in single-user mode and redusing the kernel security level, but that isn't going to be very easy for your average remote hacker.
Furthermore, since 4.0 you can multiple run complete but separate entire copies of FreeBSD on the same system, each with their own FreeBSD system files and such. You can have a single server run an instance of FreeBSD for Apache, one for Postfix, one for BIND, etc. and if any one of them does get compromised (say, BIND since that happens entirely too often) the cracker can not only not effect any of the other instances--he/she cannot even see that they exist! Very interesting stuff.
Of course, IMHO Linux is worlds ahead of FreeBSD on the desktop front, and the new GRsecurity and ACL features will be a real competitor for the *BSD family. It will be most fascinating to see how things turn out. I wish the best to both of them, and I use both of them every day.
Computer Science is no more about computers than astronomy is about telescopes. --E. W. Dijkstra
Linux has had 3 or 4 different schedulers in the past year alone! Beat that!
the only 3 files modified are kern_synch.c, kern_switch.c and proc.h, plus a one-line change to kern_exit.c
Well that's 4 files modified, now isn't it?
bsd is dead troll *here*
Woops!
You're a suburbanite.
you are soooooooooooooooooooooooooo full of shit. oh, and this is far from informative. This howeevrelqkejhrfg;ikque;rioughq;oiejvn;qjenv;oqjna slkdjbfiyulbjhnm .,manscvkjba;ksdjb;kajsbdv;kjbas;dkjhoh;kjna.,msnc .v,m aksdnv;ojnas;k askd v;asjdnv;las as
as
mka s
askd;fh;kash;dfkajha;skjdfhiuygljhbvqwjehbfv87
asd
= as\d \ q[pwd[]poq][wpo][poqw]epo[]qwefpi j;qoiu p 12i
[epo ;SODAJK FO8U 102P3IJOP1I2U=0 KJ
o áopsijd[vo0u98hq3woienf;oiqsjad oijasiocjaspdiujasjnksjdkdjjdjsdjs _++__{)ioPOk_}}\o}|_+o0i|_K kjZ l
ASAS VA /SX .VA/ LVA/D LFKV:DI
-0I -I0W9IU ]09QW 09U [OQISD;,KNQWE;KYFUI ;OIJNQAW;ODIFJ V[OQWIEU FVIOUHWEPIFBYUHGPAEUIBYVHPAYDF AVP9A8WEU -9QE7H FVPIUHZDFLVJKNA;WEKFH [QO0WEIRJFMPAOISFODVIJH]W0-8I B]2-3I90 E\- 0I
2[D0PKA:SDFOVJA
PD9F8 ]
- 2I0E
{ 2IK0E
[- 0W9 F]-0AW F.KJQWBNHEF;IUH AS987EDCH; KJWBFPIADO Y78V;KUJH P987YADFVJHAS.KHSDFVIVHBVCBVBVBVBVBVBVBVBVBVBVBVBV
as
ovk
apsjvókasnoijoieaoa ksmv ohipuhiquwerf908u093u092uóknm;ef jv]p asd[pofk v\
-0 \a0 fvk asd=]-f0vi \-a0ksv[-k
a[spkdv
[ -pais
[v
= o
as
v[p
asp v
[aks d
v[pok a
s[opv
aso[p v
as
vok a
skv
as[kv
poaksd
fvpojaoijvoaiu[sofvijáosdfijv[0pja
pkmvpi9
pom
aposdfjkóvina/sjkldnv
asdljnq[aeohknmas]
fd[v
paosdflvhiasd;ovk
er;vjonqefvnjkq;ekjfvn;kqjne;kjqer;kvjqe;rkjn fuck you.
a/s/l here. Sorry, adding domain tags to your s
You wouldn't think that the losers who use FreeBSD would have enough extracurricular activities to require the use of a scheduler! Will wonders ever cease?
gaymo
This is great news, I can't wait for 5.0 STABLE. My experience with FreeBSD has been much better than Linux. It is far more robust and actually more stable.
I'm waiting for Linux to die.
the only 3 files modified are kern_synch.c, kern_switch.c and proc.h, plus a one-line change to kern_exit.c
.. but that's 4 files modified. One-line or a thousand, it's still been modified.
I hate to be picky
</END-RANT>
I've been poking my newbie nose around in scheduling for a little while, and while I still know very little I've found the field very interesting. It's always neat to see new features and techniques being tried, but there's a feature that exists in the windows nt scheduler that (as far as I can tell) is absent in *nix operating systems. Winnt maintains (I think) four process queues (realtime, high, normal, and idle) into which all processes fall. Every time the scheduler is run, it checks to see if any "realtime" processes can be run, then "high", then "normal", and finally "idle". Processes in "less important" queues are only run if all processes in "more important" queues cannot be run (i.e. they're blocking on input or whatever), or those queues are empty. I find this very useful because I can set a long-running cpu dependent process to "idle" priority and it will be run at nearly 100% cpu usage when the machine is idle, but will instantly get out of the way and not be run at all if I choose to run something else (e.g. a game), no matter how high it's "goodness" value gets from not using any cpu time.
Is there any reason why something like this isn't implemented in Linux or FreeBSD? Low on the developers' feature priority list (har har)? Too difficult? Unnecessary?
Thanks. I'd appreciate any feedback.
Why is this shit published on front page, seriously? *BSD is DEAD.
The scheduler patch is largely the work of Paolo Valente, a student at Pisa, under the supervision of Luigi Rizzo. Luigi would not want to claim credit unduly.
Imagine a Beowolf Cluster of THESE!!!
How is this related to the so-called lottery-scheduler promised in 5.x? Do they have the same goals, such as preventing a single user from dominating the CPU? S.
Credits: on by
crapfloods and trolling and raping small kittens
nice wider pages and wanking with mittens
turd report packages tied up with strings
these are a few of my favorite things
grits covered portman and ASCII art doodles
ACs and CLITers and Katz sex with poodles
wild trolls that fly with plus five mod scoring
these are a few of my favorite things
when the ban hits, when I can't post, when I'm feeling sad
i simply remember my favorite things
then i don't feel so bad
Rob Malda chugs penis in fan fiction slashes
taco snot over my nose and eyelashes
BSD dying and that goatse ring
these are a few of my favorite things
grits covered portman and ASCII art doodles
ACs and CLITers and Katz sex with poodles
wild trolls that fly with plus five mod scoring
these are a few of my favorite things
when the ban hits, when I can't post when, I'm feeling sad
i simply remember my favorite things
then i don't feel so bad
- posted by poopbot: because we're all crapflooders at heart
eovVRUMAe4 Post #367
[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 now 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 you get distracted by the politickers that they sideline you. The tireless work that you perform keeping the system clean and building is what provides the platform for the obsessives and the prima donnas to have their moments in the sun. In the end, we need you all; in order to go forwards we must first avoid going backwards.
To the paranoid conspiracy theorists - yes, I work for Apple too. No, my resignation wasn't on Steve's direct orders, or in any way related to work I'm doing, may do, may not do, or indeed what was in the tea I had at lunchtime today. It's about real problems that the project faces, real problems that the project has brought upon itself. You can't escape them by inventing excuses about outside influence, the problem stems from within.
To the politically obsessed - give it a break, if you can. No, the project isn't a lemonade stand anymore, but it's not a world-spanning corporate juggernaut either and some of the more grandiose visions going around are in need of a solid dose of reality. Keep it simple, stupid.
To the grandstanders, the prima donnas, and anyone that thinks that they can hold the project to ransom for their own agenda - give it a break, if you can. When the current core were elected, we took a conscious stand against vigorous sanctions, and some of you have exploited that. A new core is going to have to decide whether to repeat this mistake or get tough. I hope they learn from our errors.
Future
I started work on FreeBSD because it was fun. If I'm going to continue, it has to be fun again. There are things I still feel obligated to do, and with any luck I'll find the time to meet those obligations.
However I don't feel an obligation to get involved in the political mess the project is in right now. I tried, I burnt out. I don't feel that my efforts were worthwhile. So I won't be standing for election, I won't be shouting from the sidelines, and I probably won't vote in the next round of ballots.
You could say I'm packing up my toys. I'm not going home just yet, but I'm not going to play unless you can work out how to make the project somewhere fun to be again.
= Mike
--
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 ever more market share and as BSD sinks deeper into the mire of decay, their parting addresses will resound as fitting eulogies to BSD's demise.
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 get 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.
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 BSD from death at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dying
This really puts the nail in the coffin for Linux, a dead non-inventive copycat of an operating system.
Hey, people, what are you doing with operating systems that they are crashing like a domino?
I use Linux as well as FreeBSD for awhile with Apache, Sendmail, X11 and lots of other software competing for memory, CPU, exotic devices, network bandwidth and just for disk I/O. No crashes. On linux I use also video, Oracle, Tomcat, JBoss - all works fine, besides own bugs (it's ok for userland, isn't it?).
For my experience, which doesn't meet crashes, it is more important what hardware, filesystems and protocols are supported. And of course I compare systems with only stable manually configured and re-compiled kernels passed "on-the-field" regression tests before I upgrade the production mode with that new kernel.
So, one more time, why should I prefer BSD?
Less is more !
Mac OS X is neither truly monolithic nor truly micro in its kernal architecture.
While both BSD, and Mach sit in the same memory space, this making it monolithic, they are separate pieces of software with a true microkernal in many respects.
It is monolothic in that BSD can take down the whole machine, but Apple argues that you wouldn't care if the kernal was still running when BSD crashed. Furthermore, it is monolithic in that messaging is reduced between the Mach and BSD because they reside in the same memory space as if BSD were part of the microkernal.
However, it is a microkernal in abstraction. Only Mach talks directly to hardware. It is a more portable BSD derivative than many. In addition, the microkernal allows certain online driver loading and unloading techniques that are not possible in monolithic kernals.
When they get some of the threading issues of the OS worked out it should show very good performance. Maybe this experiment will eventually prove to be the best of both worlds for a general purpose OS. Monolithic performance with microkernal maintenance.
The running time can vary for given N, just not for abtrirary N. As demonstrated by the following code. It runs fastest when n = 1, followed by n = 2, but is still O(1) when n is not 1 or 2, because the running time is constant for large n.
int orderOneButVarying(int n) {
if (n == 1) {
return n;
} else if (n == 2) {
for (int i = 0; i 3; i++) {
n*=n;
}
return n;
}
for (int i = 0; i 1000; i++) {
n+= n / 2;
}
return n;
}
::shrugs::
Doesn't even come with it.
Black holes are where the Matrix raised SIGFPE
http://uptime.netcraft.com/up/today/top.avg.html
You'll notice that 45 of those top 50 are BSD
machines. Of those 45, 19 are FreeBSD boxes.
You'll notice 1 Linux box. It's nice to see that
leading industry sites like bongload.com and
twobigirls.com have benefited so much from the
stability of BSD.
The most important thing any republican needs to know.
Right now I've got four systems running Linux (RH-7.3 and 7.2) and one system running FreeBSD 4.6. At times in the past I've run OpenBSD and NetBSD as well.
I can tell you firsthand that in terms of system stability that Linux and FreeBSD are comparable if not indistinguishable. FreeBSD does seem to be more efficient however. The pentium 200 that I have FreeBSD on loads up KDE 3.0 noticably faster than Redhat 7.2 did, and once loaded it is more responsive. On older hardware FreeBSD definitely seems to have an advantage. I consider FreeBSD to be a very fast and well designed operating system. I keep trying to find places where using it instead of Linux would be an advantage.
Not everything about it is all that rosey however. The features and abilities that Linux provides but FreeBSD lacks such as SMP, kernel pre-emption, fast journaling filesystems, certain commerical software packages, 3D acclerated X servers, and generally better device support, make actually using FreeBSD as anything but an interesting toy kind of difficult to justify in many situations.
I worry about FreeBSD. I'd love to see it grow and progress not as a competitor to Linux, but as something of a companion to it. So many people just don't seem to realize that open source isn't about operating systems alone. What Linux and FreeBSD do is provide a foundation, they aren't the whole house. Both provide a powerful and stable platform for running the actual programs that people want to use in the first place. The future of open source development is going to be 90% apps and userland and 10% OS. To have religious and political wars over the OS portion is immature and counterproductive. Linux and FreeBSD aren't genuine competitors from an economic standpoint because it is the applications that both run that make either compelling in the first place.
I want BOTH Linux and FreeBSD to do well, to grow and expand and be the best operating systems anyone has ever seen. I detest the infantile immaturity of those who seek to create division and conflict between FreeBSD and Linux that simply shouldn't be there. I've gotten flames from FreeBSD "advocates" in particular filled with such hatred and obvious zealousness that you'd think they were Mac freaks, all because I described FreeBSD in terms that weren't favorable enough for their religious views. The Linux crowd is full of just as many jackasses, if not more.
Computer enthusiasts are known for generally having high IQ's. Unfortunately our reputation for having low EQ's is equally well earned. There are far too many borderline autistics and asperger's sufferers among us with severely retarded social skills. That is really the only explanation I can come up with when grown men with extensive vocabularies use them to throw a fit on par with that of an eight year old.
Anyway I'm drifting way off from what I wanted to write about. The point that I really want to make is that BOTH Linux and FreeBSD are absolutely fabulous operating systems (save the linux is just a kernel messages for church). The goals and vision behind each are so similar that any ill will between them is manufactured by immature, short sighted assholes. Microsoft is the enemy, not those who prefer another free Unix derivative that runs Mozilla, gnome, kde, etc just as well if not better than what someone else is using.
Lee
Muslim community leaders warn of backlash from tomorrow morning's terrorist attack.
(root@oracle)(3/ttyp0)(08:19P:07/23/02)-/ i386/conf)- grep SMP LINT
(#:/sys
# SMP OPTIONS:
# SMP enables building of a Symmetric MultiProcessor Kernel.
# An SMP kernel will ONLY run on an Intel MP spec. qualified motherboard.
# Be sure to disable 'cpu I386_CPU' && 'cpu I486_CPU' for SMP kernels.
# Check the 'Rogue SMP hardware' section to see if additional options
options SMP # Symmetric MultiProcessor Kernel
That's a weak point. It still doesn't explain
why BSD dominates this "table" and some other OS
doesn't. Why isn't it dominated with Linux or
some other OS that isn't being what you perceive as
"rapidly developed". So Linux can't handle the stress
of a non developed environment? You can FUD
around with your philosophies on the psychology
of sysadmins all you want, but this table shows
something very clear. As much as your love your
pet OS, BSD is the clear stability king.
The most important thing any republican needs to know.