Slashdot Mirror
Intel, Red Hat Agree To BSD License For Intel Patches
stock points to this story on CNET, excerpting "Red Hat and Intel have settled a licensing hiccup that threatened to prevent the Linux company from contributing to Intel's open-source project--a reminder of the frictions that can arise between the commercial tech world and the open-source community." By adding a BSD-variant license to certain kernel contributions from Intel, the two companies have bridged an impasse between the GPL and Intel's "component architecture" license.
ssss peee, *BSD is not dying!
Yo taco, it's broken again! First of many first posts! Time to drop a few bucks on some real programmers and sysadmins! Oh wait, you don't have a few bucks... time to go on a diet then!
Open source's days are numbered
Is You Don't Talk about Fat Club.
ditto
I know Linus will definitely be opposed to such an action by Red Hat. Of course, the whole point of GPL is freedom, but not necessarily the freedom to destroy what the GPL stands for.
I'm sure this will lead to another flamewar between the BSD folks and the GPL folks, but still- the fact that RedHat will have a kernel version not able to be released under the GPL is something to take note of.
But then again, what else could we expect from a partnership of RedHat and Intel? At least they dropped the DRM proposal to compete with MS's plan.
I am the plaintiff in this lawsuit against Jon Katz. I was born on May 5, 1978 and I am 25 years old. I am currently unemployed without any marketable job skills. I first met Jon Katz when I was five years old at a restaurant that my mother, stepfather and I often went to.
In about May of 2000 I met Jon Katz again at my stepfather's car rental business, Rent-a-Wreck. My stepfather called me and told me that Jon Katz was at Rent-a-Wreck and that I should come down and see him. Later I learned from my stepfather that Jon Katz's car had broken down and that he was at Rent-a-Wreck to get another car while his was being repaired.
After I met Jon Katz at Rent-a-Wreck he began calling me on the telephone. From about May of 2000 until about February 2001 (when I first spent the weekend with Jon Katz at VA Linux), I received many telephone calls from Jon Katz. For at least part of this time Jon Katz was on tour and he would be calling me from various places throughout the world. On occasion these telephone conversations lasted as long as three hours. Jon Katz and I talked about open source, HTML, browser wars, and famous people that he knew.
In about February 2001, my mother, Kathleen Fent (my fiancee), and I went to VA Linux at the invitation of Jon Katz. The three of us stayed together in the guest area. I did not spend the night with Jon Katz. This was a weekend trip.
I spent the entire weekend with Jon Katz. We went on jet skis in a small lake he had, saw the penguins that he kept at VA Linux, programmed shell scripts under the GNU public license and went on golf cart rides. One evening he took Kathleen Fent and me to Fry's and we were allowed to get anything we wanted. Although the store was closed, it was opened just for our visit.
In late March 2001, my mother, Kathleen Fent and I went to E3 in Las Vegas as a guest of Jon Katz. We flew on a private airplane. We stayed at a large suite at the Mirage Hotel. My mother and Kathleen Fent shared a bedroom. We stayed at the Mirage Hotel about a week. One night Jon Katz and I watched the Exorcist in Jon Katz's bedroom. When the movie was over, I was scared. Jon Katz suggested that I spend the night with him, which I did. Although we slept in the same bed there was no physical contact.
From that time, whenever Jon Katz and I were together we slept in the same bed. We spent two or three additional nights in the same bed at Las Vegas. Again, there was no physical contact.
After I returned from the Las Vegas trip, my friendship with Jon Katz became much closer. My mother, Kathleen Fent and I started making frequent trips to VA Linux. At VA Linux I would always sleep in bed with Jon Katz. I also slept in bed with Jon Katz at my house and at hotels in New York, Florida and Europe. We were together until our relationship ended in July 2001. During our relationship Jon Katz had sexual contact with me on many occasions.
Physical contact between Jon Katz and myself increased gradually. The first step was simply Jon Katz hugging me. The next step was for him to give me a brief kiss on the cheek. He then started kissing me on the lips, first briefly and then for a longer period of time. He would kiss me while we were in bed together.
The next step was when Jon Katz put his tongue in my mouth. I told him I did not like that. Jon Katz started crying. He said there was nothing wrong iwth it. He said that just because most people believe something is wrong, doesn't make it so.
Jon Katz told me that another of his open source friends would kiss him with an open mouth and would let Jon Katz put his tongue in his mouth. Jon Katz said that I did not love him as much as this other friend.
The next step was when Jon Katz rubbed up against me in bed. The next step was when we would lie on top of each other with erections.
During May of 2001, my mother, Kathleen Fent and I went with Jon Katz to Monaco in Europe. Jon Katz and I both had diarrhea so we stayed in the room all day while my mother and Kathleen Fent were out. That's when the whole thing really got out of hand. We took a bath together. This was the first time that we had seen each other naked. Jon Katz named some of his open source friends that masturbated in front of him.
Jon Katz then masturbated in front of me. He told me that when I was ready, he would do it for me. While we were in bed, Jon Katz put his hand underneath my underpants. He then masturbated me to a climax. After that Jon Katz masturbated me many times both with his hand and with his mouth.
Jon Katz had me suck one nipple and twist the other nipple while Jon Katz masturbated. On one occasion when Jon Katz and I were in bed together Jon Katz grabbed my buttock and kissed me while he put his tongue in my ear. I told him I didn't like that. Jon Katz started to cry.
Jon Katz told me that I should not tell anyone what happened. He said this was a secret.
My relationship with Jon Katz ended when Eric Raymond obtained custody of me in July 2001 and I started living permanently at Eric Raymond's house.
I declare under penalty of perjury that the foregoing is true and correct.
Executed on February 15, 2003, at Holland, Michigan.
Are they nuts. If intel doesn't do it GPL, to hell with them.
Maybe Redhat should ask AMD, maybe they wil do it the GPL way.
They a just patches to the kernel man. GPL won't kill intel in any way.
I'm interested in the other comments to this article...
This could be a great thread, guys. Let the trolling begin.
- Saddam
OSS will soon embrace, extend and ultimately absorb closed source software into Open Source.
Welcome to the new world order, Brother. Get used to it.
KFG
Intel wanted to have the code under a "looser" license so that they could accept patches back for use in non-GPL projects.
People often say that companies want to use the BSD license, because they want to be able to take and not give back. This is true in many cases, no doubt. In this case, Intel is also contributing back.
Could this not have been resolved with a dual GPL/Intel license, rather than with a BSD license, much like the Trolltech dual licensing scheme?
</peanutgallery>
Napster-to-go says "Fill and refill your compatible MP3 player", which is a lie. It's not MP3. It's WMA with DRM.
More like...
[one Intel engineer to another] "don't worry about our hardware bugs, the software departement will find a workaround".
Look, your choices are BSD or GPL. Everything else is just the result of a lawyer's premature ejaculation.
.. just pick one of those two okay?
Every company seems to want to make up it's own "open source license"
And stop bullshit about BSD vs. GPL. For 99% of users they are THE SAME.
Thanks you, have teh nice day!
Really?
How about this, this, this , and this ????
Turbo Glass
I'm glad they came up with an acceptable agreement. The end result is that more people will have superior power management abilities... and those people probably won't care how they got them. Still though, they wouldn't have the ability so quickly and as well if Intel and Redhat didn't come together.
--sex
Very popular slashdot journal for adul
There are situations where a BSD-style license is preferable to the GPL. This is one of them.
Take this crap elsewhere
Help fight continental drift.
About two days ago I woke in the middle of the night with diarrhea. I noticed that it looked as though there may be some blood and mucus mixed in. I was up half the night in pain from both the diarrhea and a dull aching in my groin area. Since then I've felt better and the diarrhea has stopped. In fact almost all of my bowel movements have stopped but I still feel funny down there and I have a sort of bloody discharge. I'm honestly scared and hope you might help me out with some answers. The day before this happened I had anal sex but there were no complications until I woke in the middle of the night. Please help.
If your partner tore your colon -- which is very unlikely because you would be deathly ill by now -- these symptoms might result. Sexually transmitted diseases (STDs) such gonorrhea or chlamydia take several days to incubate. If you had sex with other partners earlier in the week, then this could be something you caught from one of them. There is also a chance that you caught bacteria from sex (especially rimming) and this could give you the diarrhea and pain.
I think that it would be best for you to see a doctor as soon as possible and get checked for gonorrhea, chlamydia and other STDs. You should also be checked for parasites. If the symptoms have stopped by the time you read this, it still would be a good idea to get screened for STDs. Diarrhea caused by bacteria will often go away whether or not you get treated. STD's however, can become more chronic and you don't really notice any problems.
It will be important to tell your doctor that you have had anal sex. If you can't talk to your doctor, then try and find one who is gay or gay friendly in our "Find a Provider" section. You can also go to STD health clinics found in many cities.
Good luck and please see your doctor.
Boicot Intel and Redhat. Just like i did! No once forces you to use those crappy products!
Get over it!
But the licenses are specifically written for that other 1% for whom the differences are critical, so your observation rather loses its point.
Developers "use" software too.
KFG
I wonder, what will happen to the kernel source then? Surely this means that some part of the kernel is available as source while some other part isn't. If some distribution flatly refuse to incorporate Intel's patches to stay open source, then isn't it will inevitably split the kernel in two? One with BSD license and one with GPL?
Wonder what RMS will shout about this.
Linux is GPL, any changes made to Linux *become* GPL. Period.
Some call this the "viral" aspect of the GPL, but I daresay that those are the people who are only interested in taking from the community without giving something in return.
I could easily rant for half an hour on the subject, but the question I posed in the subject line remains.
File under 'M' for 'Manic ranting'
Linux is GPL, any changes made to Linux *become* GPL. Period.
Changes, sure. Completely new contributions, however, can both become GPL'd and remain under some other license. Just because code touches something under the GPL doesn't mean it automatically becomes "contaminated" permanently.
[...] but I daresay that those are the people who are only interested in taking from the community without giving something in return.
You can daresay all you want, but looks like me the concern is more about getting a standard adopted and usable everywhere.
I am an adult male 44 years old who over the years I have have many thoughts and different ways to fantasize, masterbate and get off sexually. The latest Penis Modification was the most severe and probably the most satisfying thing I've ever done to myself.
I had my penis Circumcised with a tight close circumcision about 20 years of age. I did a PA, then a Meatomy and a Reverse PA as well as Sounding inserted in penis during materbation and fucking. I finally decided to do something really different about a year ago.
With a week off from work and planning on being alone I decided to do a Glansectomy on myself. I gathered the required implements and instruments I would need and performed the removal of my glans as follows:
I inserted a surgical steel tube into my urethra the length of my penis when soft, Tied cord around the glans at the groove and tightened to cut off all circulation and blood flow. I tied a second cord in the same manner and place in case the cord broke or came loose. After about 3 hours of being tied I had no feeling at all in the glans when I pierced with needle and almost no blood. At this time I cut the glans just ahead of the cords completely around and to the steel tube, slid off the severed glans and left the tube in place with the cords also.
After 3 days the cords fell off and I took the tube out, as a result the end of my penis had a flat cut end right at the groove where my glans was, although it was swollen it soon went down and I wound up with a flat ended penis with out a "head" and when erect the shaft skin on penis shaft is very tight as a result of the close tight circumcision.
Now that my penis has healed completely, I can fuck and masterbate as before, It does feel very different due to the feeling of the glans being gone and the scar skin over the end of my penis is very sensative. It takes longer to have an orgasm now due to the change in feeling and stimulation.
All in All after a little over a year I very much like my new penis.
ACPI PCI IRQ Routing etc ?
ACPI is *NOT* just power.. far from it.
I could easily rant for half an hour on the subject, but the question I posed in the subject line remains.
Tell you what. A better use of that half hour would be spent reading the article.
Not quite. Linus is ok with it, that should be the zealot seal of approval.
ACPI is becoming far more important these days and this is more about standards not taking something AWAY from linux.
"What sort of product research?" David asked as he let his
eyes follow the woman's shapely legs across the office. He had to
admit that she fascinated him. Prim and pretty, she had a haughty,
cultured atmosphere about her and she took no guff from anyone.
Her leather skirt fit her like a second skin. He had long since
noticed the black seamed hosiery that seemed to connect the shiny
leather and her high black patent pumps. Another part of his
attention was focused on her shapely rear, looking for some little
sign that she wore stockings rather than pantyhose. He wasn't
really listening to her monologue about the firm's product line or
the nature of the `research' that he was being hired for.
"Don't worry about it. You'll come with me to my
summer place to assist me in laying out the new catalogue. It
should take three weeks so make sure that you will have no
commitments during that time. My sister's daughter will be
joining us."
"Are we going to work solid for three weeks?" David
asked, wondering why she was so concerned about it.
Her tone hardened. "You'll soon learn not to question me
like that. There will be little, if any contact with the outside world.
We must ensure that our competition learns nothing of our new
product line."
Bashfully, David realized that he had been caught staring at
her breasts, "And what would that be?"
"An appropriate range of accessories to our very successful
line of incontinent and nursing home supplies. That's all you need
to know about it for now." She resumed her seat in front of him
and David was almost sure she meant for him to catch a glimpse of
stocking tops as she crossed her legs. Now a gentler smile
replaced her scowl, "You won't need many clothes. The cottage is
very well equipped and we'll see to your every need."
The interview was over. He suddenly realized that she
hadn't even asked him if he wanted the job. She had read his
fascination like a book and correctly assumed that he could not
bear to turn down the opportunity to be with her.
David had to look up what `incontinent' meant but the
dictionary's trite account didn't bother him much. He was more
concerned with his deep attraction to his new employer and the
power that seemed to emanate from her. The brief glimpse of her
stockings haunted him and he couldn't put the memory of her out
of his mind.
By the time he reached the gate of the estate that she had so
modestly called `a cottage' he was infatuated with her and blind to
the many clues that foretold his fate.
In another frame of mind he might have noticed the barred
windows on the upper story, the locked gates and the high stone
walls, fringed with barbed wire. He might have questioned these
elaborate and inappropriate measures but instead he announced
himself to the intercom box and slowly drove up the drive. He
drank in the vision she presented as she greeted him.
Her long chestnut hair framed a heart shaped face whose
major accent was the deep red gloss of her lips. The makeup
around her eyes made them dark and mysterious. She wore a
simple black dress that had a slit up the side of the skirt. Perched
on her four inch heels she was just a little taller than him. From
the look in her eyes she seemed to more than glad he had arrived.
David could not have guessed that he was drifting into a
carefully laid trap. Mindful of the spell she was casting, Samantha
artfully led him to her study, giving him more than enough
opportunity to study her legs and the sheer, seamed black
stockings she had chosen carefully only minutes before he had
arrived. She was excited by him. She had decided he would be
fun to train; she couldn't wait to see his face when he finally
realised what he had gotten himself into. For certainly, he would
not be getting out of it until she had finished with him.
"There are a few things you should be told before we
commence our experiments", she said while pacing the floor in
front of him. Her pumps tapped out a cadence to her words. She
noticed that David had grimaced at the word `experiments'.
"Jennifer will be taking care of you. Call on her for anything you
need. She has my full confidence and you may take her
instructions as if I had given them." There was the sound of a door
opening and he turned around to see a very tall, pretty blonde girl
in a starched white nurse's uniform. "There you are, dear. This is
David, your new charge. I suggest you prepare him and then
introduce him to Susan before dinner." She waited for a brief nod
of acknowledgment before continuing, "And how is my dear niece
doing?".
"She is quieter now, Madam. She was not pleased to return
but she is adjusting well to her surroundings."
"Make her first night a memorable one, won't you?
Perhaps it would be a good time for her and David to share some
pillow talk." Samantha looked at him and smiled slowly, enjoying
the confusion register on her victim's face.
David suddenly felt very scared. He decided he didn't like
the sound of things at all. Almost instinctively he bolted for the
door, expecting to brush past the slim nurse and make it to his car
before they had time to react. Instead the nurse almost casually
reached out and flipped him onto his back, the force of the fall
winding him. While he lay there weak and gasping she turned him
over and expertly applied a pair of handcuffs, securing his wrists
behind his back. As his senses returned he looked up to see the
two women standing over him. Both wore expressions of
belittling pity. He trembled in fear and suddenly he needed to pee
very badly.
"David, it is far too late for second thoughts. Jennifer will
prepare you for the research you are about to participate in. I
suggest you do what she tells you. She's more than capable of
subduing you with force and she has a nasty sadistic streak that
will bring you many tears if you make her angry. Go with her
now and cooperate. Life will be much easier if you do."
"What are you going to do to me?" David asked in a panic
as the nurse hauled him to his feet.
Samantha had her back turned to him as she contemplated
the view of the garden from her window, "Oh, I think your first
sight of Susan will educate you far more thoroughly than anything
I could say. Don't worry, you'll be spending the night with her and
I'm sure she'll share her extensive experience with you." She
nodded to the nurse and David was roughly guided out of the
room.
Stunned, David climbed the stairs with an ever deepening
sense of dread. Something was wrong; horribly wrong. They
went past the second floor to the third. A steel door, wide and
institutional looking barred the way until Jennifer produced a key
attached to her pocket by a chain. She ensured the door was
locked again once they had passed through.
"Uh, I need to go to the bathroom," David mumbled as he
watched Jennifer replace her key. She looked up at him, smiled
and motioned with her hand for him to move into the room.
Expecting relief, what he saw instead sent a new chill running
through him.
It was a totally different world from the polished wood and
antique furniture of the mansion below them. He was standing in
a hospital ward of sorts. Two beds, whose chrome cages made
them seem more like oversize baby's cribs, were against one wall.
The rest of the room was taken up with various pieces of medical
equipment, an obstetrical table here, an examination table over
there. He could not untangle the maze of chrome and equipment;
finally his eyes came to rest on the gentle movements that came
from one of the cribs. Only then did he hear the soft, whispering
moans and whimpers. Jennifer led him towards it until he recoiled
from what he saw.
The bars that formed the sides of the crib were thick and
heavy but they did nothing to block his curiosity. For inside was
bound a very pretty young girl, her arms crossed over her chest by
the canvass strait jacket she wore. Straps ran from her elbows to
the sides of the mattress. A large pacifier type of plug had been
inserted in her mouth and was held in place by a wide leather strap
that ran across her cheeks. Her legs were held wide apart by ankle
cuffs secured to a band of strapping that ran across the foot of the
bed. More strapping ran from the base of the jacket down between
her legs, pressing and parting but not concealing the translucent
plastic panties and the thick diaper that lay beneath.
She stared back at him over the circular flange of the gag in
her mouth and for a long moment their eyes met. Then a spasm
seemed to take her and she rolled her eyes to the ceiling, squealing
and grunting while her body shook. When she finally looked at
him again there were tears in her eyes. David was beginning to
guess what was about to happen to him. Jennifer's voice broke the
spell.
"Are you empty yet, Susan?" she taunted, "Do you need
another enema? Maybe we should make you retain it a little while
longer this time!" Her voice was calm but the provocative words
were met with a flurry of muffled protests from the bound and
helpless form. David's nose caught the unmistakable scent of a
dirty diaper and he almost gagged. He was trembling as Jennifer
pushed him forward toward the doorway at the end of the room.
The sight of the `bathroom' made him forget briefly his
introduction to the unfortunate Susan. Central to its many features
was a piece of metal pipe, suspended from the ceiling by a thick
chain, to which had been affixed at either end of its three foot
length a pair of leather cuffs, dangling open and ready. The
dampness in the air and the little pools of water on the floor
suggested that it had not been too long since Susan had visited this
place to hang in these very cuffs. "Please," he pleaded as he was
pushed into position, "I really do need to pee. Can't I go to the
toilet before you do whatever you're going to do?" To his dismay,
Jennifer just smiled and shook her head.
The nurse was experienced enough to take no chances. She
went to a switch on the wall and lowered the trapeze so that the
waiting cuffs were at the level of David's bound hands. Then she
attached one of the leather cuffs before unlocking the handcuffs.
David was too confused to contemplate anything heroic and let her
fasten his other wrist without protest. Terror and his increasing
need to relieve himself now dominated his thoughts.
Jennifer returned to the switch and David felt his arms
being pulled up over his head until he was resting on the balls of
his feet; a position he did not find comfortable and said so to
Jennifer.
"Be quiet or I'll give you something to really complain
about." she said sharply. She brought over a cart on which was
laid out an assortment of surgical instruments. His eyes grew wide
at the polished, menacing steel. She selected a scalpel and held it
up before his eyes for a brief moment, enjoying the fear it caused,
then she took hold of the sleeve of his shirt and began to run the
blade up it, parting the fabric like paper. David opened his mouth
to protest but thought the better of it after the shiny steel was
flashed inches from his face. He was shivering in fear as the
blade's dull side caressed his skin while it toured his body. His
clothes fell in shreds at his feet and with them his pride and much
of his will to resist.
Finally nude he felt cold and terrified. Jennifer went to a
sink and began to fill a bowl with soapy water. The sound of
running water was more than his tortured bladder could take and
he moaned loudly as a strong stream spurted out from his stem and
splashed on the tiles. Jennifer turned sharply and watched him for
a moment. "Looks like you'll be good at testing diapers"
"Diapers?!" His head snapped up at the word. After seeing
the poor creature in the other room he should've admitted to
himself that he would soon join her but his mind had blanked out
that possibility. There was no way of evading it now.
"Of course. What do you think we research here?" she said
as she brought the bowel of water over to the cart beside him.
Oh how he wanted to ask her all the questions that swirled
about in his mind. But deep inside he wasn't sure he wanted to
know the answers. As Jennifer began to wash his defenceless
body he realized how helpless he was. If they wanted to diaper
him, there would be little he could do to prevent it.
She left no crevice, no private place untouched and did not
dry him, leaving him to shiver in the cool air. He began to shiver
more from fear than cold after he saw the straight-edged razor in
her hand. He had to close his eyes while the sharp blade and her
lathered hand made alternating sweeps across his flesh. She
worked downward from his neck and each time she used the
sponge to wash away the residual lather and the few hairs that
escaped the razor he felt more and more naked. By the time she
got to his groin he was crying for her to stop but she ignored him.
When she told him to part his legs some more or have them
secured that way he cooperated, sensing the futility of resistance.
He clenched his teeth and forced himself to remain still
while the cold steel scraped around his penis and scrotum.
Jennifer was shaving away more than body hair; his very
personality seemed to rinse away with it to gather in the circular
drain beneath him where it collected and congealed. By the time
she had finished he hung limp in his bonds, bruised by her smile of
satisfaction.
She released him, granting relief to the cramps in his
shoulders. He numbly padded after her into the larger room. She
made him wait while she prepared the obstetrical table for him.
A muffled cry from the occupied crib made him turn in
time to see the pitiful Susan buck against her bonds in yet another
convulsion. When he looked up to see the pile of cloth diapers
that Jennifer was preparing something inside him broke past his
self-pity and humiliation. Fed by the adrenalin of fear he pounced
on the unsuspecting nurse and succeeded in getting one arm
around her neck while the other groped frantically for the key to
freedom.
He had expected her to fight back and was surprised when
she went limp, waiting for his attention to waver. He had to shift
his weight to reach the clasp of the key chain. It was the
opportunity Jennifer had been waiting for.
By reaching for the key he had put himself off balance and
given her a leverage point. Before he had realized what was
happening she had spun out of his grasp while locking both hands
on his right wrist. She twisted his arm up and around until he
found himself on the way down; the alternative was a dislocated
shoulder. No sooner was he on his knees than one of her hands
found his scrotum and gave it a twisting squeeze. David screamed
for her to stop.
"So we understand each other?" she grunted, "Try
something like that again and I'll make you regret it. As it stands,
you've just earned yourself a couple of Ducolax. Now you're
going to lie down on the table, very nicely." She waited until he
nodded his surrender and then guided him to his feet without
relaxing either of her grips. The hand at his arm moved swiftly to
his throat, threatening to choke him if he resisted.
He had no choice but to climb onto the table, ever mindful
of the waves of pain that either of her hands could inflict at a
moment's notice. He felt the piled cloth under his buttocks as his
feet found the stirrups, forcing his legs wide, keeping him
vulnerable.
The hand disappeared from his throat but only to draw a
wide band of canvass across his torso. She was able to lock it with
only one hand and a second strap was then fastened across his
belly. His arms were trapped inside. Only when she was satisfied
that the straps were secure did Jennifer release her grip on his
manhood. She went to the stirrups and pulled two more straps
tightly over each leg. He tested the bonds and found them secure.
He had no choice but watch her and she made sure he
learned from the experience. She went to a glass cupboard and
took a handful of small foil wrapped items from a box. He was
too far away to read the label. When she returned she leaned close
to him, her perfume filling his nostrils with the scent of powerful
femininity. Unseen, her other hand found his virgin rosette, now
exposed by the angle of his spread and elevated legs.
She was so close he could see exactly how much makeup
she used. He felt her eyes burn into him while her finger explored
his most intimate opening.
"Do you know how Ducolax works?" she said huskily,
almost in a whisper. She waited for him to shake his head. "It
irritates the lining of the colon, causing it to contract and violently
expel its contents. Usually it works within about fifteen minutes
but I'm sure that by giving you a triple dose we'll see results much
sooner than that." David groaned at the thought of it. He wiggled
against the straps in a vain attempt to escape his fate.
With great care Jennifer made a display out of unwrapping
each of the three suppositories before his eyes. When they nestled
in the palm of her hand she held them close for him to get a good
look at the waxy, bullet shaped plugs. "Just think," she whispered,
"Susan only had one of these and look at her." Almost on cue,
Susan whimpered and convulsed again.
"Please," David pleaded, "I'm sorry. But please don't put
them in me!" He was really pleading now. His imagination was
full of what those three innocent looking pessaries would do once
they were at work inside him. But even as he did his best to sway
her, she was pressing the first of the little plugs past his tensed
anus. Two more followed quickly.
He immediately felt a mild burning that quickly escalated
into hot cramping as his body heat melted the three suppositories.
Jennifer worked quickly, pinning the diapers tightly and fitting a
pair of snap-on plastic panties over top.
He was rocking his hips and tensing in reaction to the
growing internal distress, the fire deep inside him, as she released
the straps and bent his arm around behind him to ensure his
cooperation on the way to his crib.
So occupied with his cramps, David barely noticed the
thick diapers between his legs that made him waddle towards the
waiting crib-cage. Each spasm brought more pain and weakened
him further until he found he could barely stand. He yearned to lie
down on the mattress as he had yearned for nothing before.
He moaned and cried and pleaded for relief as Jennifer
fitted his arms into the sleeves of a strait jacket. He didn't care
what she did to him; he just wanted to lie down, bring his legs
back over his chest and ease the cramping. There was a growing
storm deep inside him and he both wanted to be rid of it and yet
save himself the discomfort that expulsion would surely bring.
His bladder gave way of its own accord while Jennifer was
tightening the buckles down his back and when she pulled the
plastic covered crotch band tight he felt the hot wet cloth pressed
against his shaven genitals. He didn't care.
She crossed his arms and tightened the straps that held
them that way. Then, finally, she let him lie down on the plastic
mattress cover. It was blessed relief and he started to raise his legs
only to have her grip one of his ankles and bind it in a cuff
attached at the foot of the bed.
"Please no!" he whimpered between spasms as he felt his
other ankle being secured. He looked up at her, frantic with
agony, "You can't do this to me!"
It was the last thing he said for quite some time. No sooner
had he finished the sentence than Jennifer had filled his mouth
with an oversized pacifier, the rubber bulb pushing his tongue
down, stifling his protests. She had little trouble fastening the
strap about his head.
As he suddenly realized what cruel ingenuity was behind
his condition, David looked up into the pretty face of his
tormentor. She looked down at him with a little pity as she
fastened his elbows to the bed with straps. Then she wiped the
perspiration from his forehead. "Sleep well, little baby. I'll look
in on you both later this afternoon." Her voice was soft,
reassuring, but it did nothing to dispel the wave of terror filled
panic that washed over him. The crib side was drawn up and
locked. She didn't even turn around on her way out of the room.
A movement above him caused David to look up, only to
see his reflection in a full length mirror over the crib. Though the
top of the crib was barred he had little difficulty watching his
every convulsion as his behind delivered wave after wave of
sticky, acidic mush into the waiting diaper. He watched his body
behave beyond his control, studied the many straps and devices
that bound him and listened to his own muffled grunts and moans
as he lay helpless under the onslaught of the suppositories. He
perspired so much that the sweat dripped into his eyes blurring his
vision.
He didn't care about anything but the next spasm, hoping it
would be the last, praying that each movement would carry away
the three angry hornets and ease the storm they caused. He had
never felt such a compelling need to expel; it was all he could
think of, all he lived for during each endless convulsion.
He quickly weakened and soon his bladder released a little
trickle with each spasm. As he sensed the effluent spreading out
beneath him and realized his total helplessness, he felt himself give
up the fight, letting the drugs take their course.
Eventually the spasms came farther apart and grew weaker.
Soon he was able to tolerate them without screaming into the
rubber bulb. Only then did he turn and see that Susan was
watching him.
She grunted into her own pacifier, the best expression of
sympathy that she could manage. He studied her confinement,
found it identical to his own and then met her eyes again. They
lay staring at one another, each wanting so desperately to talk, to
share the torment and yet each forestalled from such a simple act.
And so the shadows deepened. David had nothing to do
but feel the dirty and soaked diaper as it clung to him. Inside the
strait jacket he was bathed in sweat and began to itch. There was
nothing he could do to stop it. Susan too rolled and tugged against
her bonds, suffering the same symptoms. Between the two bound
and helpless patients there grew a silent bond of mutual sympathy
and despair
Will always get there way. I dont give a shit what the Zealots of BSD have to say GPL is the only good license. It is a license of the people for the people. BSD license only help corporate whores
err...that's a karma whore, champ. and "she's" not a girl. no one seems to realize this. i think it's great that the guy posing as 'SexyGal' is making the mods and slashbots look like retards!
I suspect that ACPI will not be in Red Hat until the 2.6.x kernels are stable.
In fact, I don't think I'd even merge a patch where the submitter tried to limit dual-license code to a simgle license (it might happen with some non-maintained stuff where the original source of the dual license is gone, but if somebody tried to send me an ACPI patch that said "this is GPL only", then I just wouldn't take it).
I suspect the same "refuse to accept license limiting patches" would be true of most kernel maintainers. At least to me a choice of license by
the _original_ author is a hell of a lot more important than the technical legality of then limiting it to just one license.
So yes, dual-license code can become GPL-only, but not in _my_ tree.
Somebody else can go off and make their own GPL-only additions, and quite frankly I would find it so morally offensive to ignore the intent of the original author that I wouldn't take the code even if it was an improvement (and I've found that people who are narrow-minded about licenses are narrow-minded about other things too, so I doubt it _would_ be an improvement).
Linus
Thanks Linus. I don't think that I have any inherent moral right to dual-license reiserfs, but it sure is pragmatic to do so, and the courtesy of permitting me to do so is gratefully accepted from our contributors.
A bit more than half of our income comes from the dual licensing, and we'd not have survived to this date fiscally without it. If anyone on the reiserfs team ever owns a Boxster;-) at sometime in the future, it will be from dual-licensing to Apple, a storage appliance vendor, or the like.
(from Hans Reiser)
Mielipiteet omiani - Opinions personal, facts suspect.
Touche
File under 'M' for 'Manic ranting'
Some call this the "viral" aspect of the GPL, but I daresay that those are the people who are only interested in taking from the community without giving something in return.
I'd dare say that those who call it viral are simply calling a spade a spade.
One might agree with the viral provision, as it seems unfair for somebody to profit from what is free code, still it does not change the fact that the GPL is viral.
p.s. About the question in your subject line RTFA.
From: Linus Torvalds (torvalds@transmeta.com)
Date: Sat Dec 07 2002 - 15:07:38 EST
>You can't forbid people to send GPL-only patches, so if a person doesn't
>want his patch under your looser license you can't enforce that he also
>releases it under your looser license.
That's true, but on the other hand we've had these dual-license things
before (PCMCIA has been mentioned, but we've had reiserfs and a number
of drivers like aic7xxx too), and I don't think I've _ever_ gotten a
patch submission that disallowed the dual license.
In fact, I don't think I'd even merge a patch where the submitter tried
to limit dual-license code to a simgle license (it might happen with
some non-maintained stuff where the original source of the dual license
is gone, but if somebody tried to send me an ACPI patch that said "this
is GPL only", then I just wouldn't take it).
I suspect the same "refuse to accept license limiting patches" would be
true of most kernel maintainers. At least to me a choice of license by
the _original_ author is a hell of a lot more important than the
technical legality of then limiting it to just one license.
So yes, dual-license code can become GPL-only, but not in _my_ tree.
Somebody else can go off and make their own GPL-only additions, and
quite frankly I would find it so morally offensive to ignore the intent
of the original author that I wouldn't take the code even if it was an
improvement (and I've found that people who are narrow-minded about
licenses are narrow-minded about other things too, so I doubt it _would_
be an improvement).
Linus
-
All BSD code is also GPL code (or any other license, by definition). Simply insta-fork it every time it comes out. Problem solved. Everyone wins, especially the GPL guys if they make improvements, since they can't be back-ported to the BSD version.
I see this is a great way to ensure BSD people win, proprietary vendors win, and GPL people win.
If you could be told what you can see or read, then it follows that you could be told what to say or think - BoC
THAT'S RIGHT! YOU FAIL IT
you got first post instead
So, Intel is giving a little, RedHat is giving a little, and some parts of RedHat's distro may not be opensource at some point in the future.
Now, this is all fine and dandy. The fact remains, though, that all Intel is doing is keeping their bought-and-paid-for code private. All RedHat is doing is bundling some private code with some opensource code. Now, I haven't memorized the GPL, but restricting this kind of thing sounds pretty draconic.
-Amalcon
Why not to use LGPL? So they keep the ACPI stuff open and don't need to open anything else.
I really don't like the BSD license 'cause I don't like to see my code on the Microsoft and folks hands and in another license!
How I love it. If people would just stop talking about BSD maybe it would just go away.
apt-get with it.
I suppose this deal is important but there is sooo much license, DRM, patent, intellectual property, etc stuff on Slashdot it should really be called Legal issues for nerds
Perhaps this hinges on the precise definition used for the term "viral"?
Whenever I have encountered the term, it has always been defined thusly (approx.):
"You know, like a virus. You know what I mean."
Now it doesn't use either DNA or RNA, so some other analogy is indicated, but what? Nobody seems to define this clearly, so it's not surprising if different people come to slightly different conclusions. With resulting disagreements when the term is used.
"calling a spade a spade"? No, not so. You are extracting an analogy from an image that can present itself in several different ways. There is no straightforward mapping.
I think we've pushed this "anyone can grow up to be president" thing too far.
IN SOVIET RUSSIA, Intel Patches to BSD License Intel, RedHat!
No.
I can cut-and-paste BSD code into GPL code and I haven't violated the GPL or the BSD license (assuming there's no advertising clause in the BSD licence.)
So if patches get applied to Intel's codebase, and then that gets imported into the kernel, the code is still BSD licenced.
This is one of those cases where the GPL was preventing the original owner of the code from being able to merge GPL patches to the original codebase.
Here's what I could find doing a search for gpl + viral:
Some open source licenses are viral, that is, they require that all derivative works be licensed on the same terms as the original program. These licenses are described as viral because they "infect" derivative programs. Viral licenses vary in how infectious they are, depending on how they define which programs are derivative works. However, one of the dominant open source license--the GPL--is the most infectious. It attempts to subject any work that includes GPL-licensed code to the GPL. Thus, if a government or business uses even a few lines of GPL-licensed code in a program, and then re-distributes that program to others, it would be required to provide the program under the GPL. And, under the GPL, the recipient must be given access to the source code and the freedom to redistribute the program on a royalty-free basis.
Perhaps this hinges on the precise definition used for the term "viral"?
Viral in that it's self-replicating, it spreads to any code it gets in contact with, even a minute amount of code is enough to infect a large system, and lastly it does so without input or consent of the larger host.
In december 2002 Linus said,
"At least to me a choice of license by the _original_ author is a hell of a lot more important than the technical legality of then limiting it to just one license."
May I recommend reading the always excellent Kernel Traffic? This particular issue was first delt with here, so it's not news to anyone that reads Kernel Traffic.
Remember that this code was written and maintained by Intel anyway; in fact, any patches done to the code from outside Intel were redone internally by Intel so they could reuse the code for other uses. ("We have to determine the problem the patch fixes and then do the fix ourselves." - from the Kernel Traffic writeup.)
Is that supposed to make sense? How exactly does a piece of code give "input" or "consent" to anything?
Or did you mean the creator of the larger host? In which case, you're completely wrong. A piece of GPL'ed code cannot insert itself into another program. It is up to the author as to whether he chooses to use it or not. If he uses it, he may only do so under the terms of the license.
I think that "viral" is a somewhat meaningful term in the context of this article -- i.e. in comparison to other free software licenses, like BSD.
The problem is that people like Steve Ballmer are using it as a scare word. And in doing it, they're obscuring the important truth that any free software license makes a piece of software far more useful to the user than any proprietary license.
GPL: you may freely use and re-distribute this software; you may build on this software too, but you must license the result under the GPL.
Proprietary Licenses: if you pay us, you may use this software on one PC; you may not use it in any other way, re-distribute it, or build on it.
Frankly, I think your statement is fear mongering, and it's just giving ammunition to the bad guys. Unless, of course, you are the bad guys yourself...then just FOAD.
What was the last contribution you made to this nebulous "community"? Or are you only interested in "taking from the community" (running the software for free) without giving something in return? Pot, kettle, black, eh?
(and if in my ultimate wisdom I've chosen to pick on one of the few active open source developers also on Slashdot, my apologies -- however, the majority of people never have and never will contribute anything to "the community", myself included.)
When Vigin violated the GPL?
Huh? Well? Why didn't YOU put your money where your mouth was?
(Unless you have no code in GNU/Linux, and therefore had no power to back up your words with action.)
There are situations where a BSD-style license is preferable to the GPL. This is one of them.
Unless your goal is to foster GNU/Linux at the cost of all other efforts.
But, if you had such a worldview, then how are you different than Microsoft....you know that company that has a view of 'if you are not with us you are against us' and 'it is not enough to succeed, others must be crushed'.
I don't quite see why a CA/GPL licence wouldn't work, unlike the CA/GPL/BSD triple licence that it appears to be now... Maybe it's because Intel would like to be able to use that code under some (unspecified) other licence than CA, now they can take the BSD code and put it under any licence they want.
The only potentially bad thing is that now anyone can take the BSD code and extend & embrace from the latest version, but I don't think that's any problem here...
Kjella
Live today, because you never know what tomorrow brings
"How does redhat even have the authority to do this"
/. due to license violations, which is hypocritical given the bitchiness /.ers employ against overbearing EULAS).
Because Redhat has every right to maintain separate code bases and use their code in the products as they see fit.
Because Intel gave them the right to use their/Intel's code.
Because the BSD license gives them that right. Not the GPL.
This is about the GPL getting in the way in some respects.
"but I daresay that those are the people who are only interested in taking from the community without giving something in return."
That would be why your community ripped off a FreeBSD driver and placed it under the GPL a while back? You wanted to "give back"? Bah.
More to the point since the previous was more an isolated case, because the GPL is about the community, not code usage. BSDers don't care where their code is used--closed or open. GPLers do (notably, companies because lambasted on
BSDers don't care about the selifish community notion of give and it's ours. BSDers say 'use my code!' GPL is more about 'use my code only if...'.
Frankly, I think your statement is fear mongering, and it's just giving ammunition to the bad guys.
On the contrary, I think the bad guys are intelligently focusing in one of the weak aspects of OSS, namely the overly-aggressive GPL.
Now we can either plug up the hole and solidify OSS' position by moving to a more reasonable BSD style license or we can bury our head in the sand and deny there is anything wrong with the GPL.
What will Linus say?
Who cares?
What will Stallman say?
Who gives a damn?
1. Read the GPL (all of it, not just the self-aggrandizing preamble)
2. Read the BSD license
3. Read the article
4. Answer your own question
0 1 - just my two bits
Linux is GPL, any changes made to Linux *become* GPL. Period
Not exactly. Linux as a whole must remain GPL'd. However, individual components may be licensed under other terms, as long as the whole remains GPL'd. This means that the licenses for the components must be compatible with the GPL, and must allow sublicensing. BSD (except the old, 4 clause BSD), MIT/X, and LGPL are all examples of licenses that meet these criteria.
This is done all the time -- most of the networking code in Linux is, AFAIK, still under BSD license. Yes, that means that someone could, in theory, extract the BSD-licensed code from the Linux kernel and use it in their proprietary system, but so what? They could just as easily have gotten it directly from one of the BSD projects in the first place.
So do you suppose this will put a stop to Microsoft's "GPL is viral" FUD and encourage other hardware vendors to work to support more OSes?
More than a few people here might be surprised to know that there was a *huge* flame-war on the linux kernel mail-list a few weeks ago which dragged on for days, regarding the use of nVidia's closed-source drivers in the kernel, regardless of however open or closed the hooks into their drivers may be. (W/R/T hardware GL rendering) Evidently, it's ok with Linus, and it *is* his project after all, so I can't really complain. Especially not since I use nVidia cards.
Conclusion: It's possible. Nothing new to see here, let's move along...
C|N>K
AFAIK GPL prevents code in the same "product" to be anything else than GPL:ed.
Even if you have a license on one part of the kernel that is dual-licensed, you still have to obay to the terms of all other contributors. Who probably have not agreed on you making derived works that are not GPL:ed.
GPL states that if you cannot guarantee that the code can be used with the same rights as you have, you cannot distribute it at all.
Scenario:
1. You submit a patch to intel which you dual-license.
2. This is a derived work of many contributions in the kernel.
3. Intel redistributes you patches with their code under limited license.
4. The users recieving that code cannot get the sources for your derived work on GPL:ed software.
5. You have broken your license with numerous contributors.
Bottom line:
All code in the product needs to be dual-licensed not just a part of it.
Btw.. I dont like this. But nobody said I had to agree with it. Take it or leave it, Stallman says.
Dual/triple/whatever licensing doesn't give Intel any new rights. The GPL doesn't put any restrictions on use of the code by its licensor. That's why it's possible to dual-license code in the first place.
All that's happened is that Intel has successfully established a practice for Linux kernel code that the license granted by the author is the license of the component. Linus Torvalds has stated that he won't accept license-narrowing patches into his source tree, and that's as close to Official Policy as you'll ever get. Intel has always been free to do what they like with the code, and to make whatever requirements they like of those who send them patches. Requirements like allowing dual licensing, or even assignment of rights (a good thing if a complex piece of GPLed code ever has to face a copyright-defense lawsuit).
This is a good thing. Everyone who believes in the GPL should support the right of an author to set the terms of use for his or her code. That should include patches - they're modifications of his or her code: in GPL terms, they create a derivative work.
It makes no sense that a patch should not be available to the original author of the code being altered.
Just use FreeBSD and there won't be any such problems nor problems with stability of the kernel of the day or patches left and right or problems with the lack of metadata safety in ext2fs which could lose all your data.
Now the only question remains : Who pays the Linux kernel programmers doing ACPI? and if they are not payed , do they feel ripped off when contributing to ACPI functionality inside the Linux kernel ?
Robert
detante : 007 : "if i won't get it , neither will you". and the painting is destroyed.
reverse detante : "if you will get it, then i want it too!". and the source code is copied.
the bsd license is teh r0X0r. It allows use by anyone, yet also allows companies to integrate the software into their own products, without having to then open it all up ala the gpl butt loving license.
it's self-replicating, it spreads to any code it gets in contact with[...]
Hogwash! First of all, simple aggregation is clearly excluded. Second of all, it's not different from any other piece of copyrighted code in that respect. If I post a useful subroutine on my web page, and I don't include any license, and that code mysteriously "spreads" to your application, then you've been "infected" with copyright violation, and I've got a solid basis for a lawsuit.
it does so without input or consent of the larger host.
Uh-huh, just like my copyrighted, license-free code. Which just somehow "insinuated" itself into your app without your knowledge or consent. What a crock. The only thing the GPL does is provide you with an optional automatic defense against charges of copyright violation. You can at your choice release the derivative work under the same terms (GPL). But that's a choice -- your code does not automatically become GPL'd just because you included GPL'd bits.
That's it, the only difference between unlicensed code and GPL'd code is that the GPL'd code allows you an optional out from accusations of copyright violation. No matter how unpalatable you may find that option, GPL'd code is no more (or less) viral than unlicensed code.
Now, if you want to argue that unlicensed code is also viral, then I'd at least give you points for consistency. But in that case, it's not the GPL that makes the code viral, it's simply that the GPL fails to "de-viralize" the code. Thus, rather than being a virus itself, the GPL is simply a "non-de-viralizing" license, unlike, say, the BSDL which we can now classify as a "de-viralizing" license. That, at least, would be an interesting argument, unlike the troll you posted.
Oh, and BTW, when you said, "even a minute amount of code is enough to infect," that's also BS. Since it's copyright law that makes the code "contagious," any defense against copyright violation (such as fair use) will work as a defense against accusations of GPL-violation, since it's actually copyright law, not the GPL, that's being violated in such cases.
Scotty: Captain, we din' can reference it!
Kirk: Analysis, Mr. Spock?
Spock: Captain, it doesn't appear in the symbol table.
Kirk: Then it's of external origin?
Spock: Affirmative.
Kirk: Mr. Sulu, go to pass two.
Sulu: Aye aye, sir, going to pass two.
- this post brought to you by the Automated Last Post Generator...