Yet another crippling bombshell hit the beleaguered Dirty GNU Hippie community when last month IDC confirmed that Rancid Smelling GNU Hippies account for less than a fraction of 1 percent of all humans. Coming on the heels of the latest Netcraft survey which plainly states that Natty haired greasy GNU Hippie have lost more market share, this news serves to reinforce what we've known all along. Reeking Linux Hippies are collapsing in complete disarray, as further exemplified by failing dead last [sysadminmag.com] in the recent Sys Admin comprehensive/usr/bin/sh test.
You don't need to be a Kreskin [amdest.com] to predict the future of the Stinking sweaty Linux hippie. The hand writing is on the wall: Foul-stenched GNU hippies with swampy armpits face a bleak future. In fact there won't be any future at all for them because they are dying. Things are looking very bad for Hairy-backed GNU hippie. As many of us are already aware, they continue to lose market share. Red ink flows like a river of blood.
Let's keep to the facts and look at the numbers.
Troll leader Anonymouse Coward states that there are 7000 goatse.cx trolls. How many ascii art trolls are there? Let's see. The number of goatse.cx versus ascii art posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 ascii art trolls. Pimply-faced GNU hippies posts on Slashdot are about half of the volume of ascii art posts. Therefore there are about 700 Dirty GNU Hippies. A recent article put "first post" at about 80 percent of the troll market. Therefore there are (7000+1400+700)*4 = 36400 "first post" trolls. This is consistent with the number of first posts.
All major surveys show that Putrid smelling greasy GNU hippies have steadily declined in market share. Slashdot is very sick and its long term survival prospects are very dim. If Grubby Smelly Linux Hippies are to survive at all it will be among troll hobbyist dabblers. Slashdot continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, Dirty GNU Hippies are dead.
Let us assume the fact that posts are showing up in reverse order is simply another bug resulting from shoddy half-ass open sores programming, and NOT INTENTIONAL. This is what happens when dirty GNU hippies smoke too much weed before coding.
Drain your swampy armpits, wash off your rancid body odor and fix the bug dammit!! But please - for Gods sake, TAKE A SHOWER!
Let us assume the fact that posts are showing up in reverse order is simply another bug resulting from shoddy half-ass open sores programming, and NOT INTENTIONAL. This is what happens when dirty GNU hippies smoke too much weed before coding.
Drain your swampy armpits, wash off your rancid body odor and fix the bug dammit!! But please - for Gods sake, TAKE A SHOWER!
Let us assume the fact that posts are showing up in reverse order is simply another bug resulting from shoddy half-ass open sores programming, and NOT INTENTIONAL. This is what happens when dirty GNU hippies smoke too much weed before coding.
Drain your swampy armpits, wash off your rancid body odor and fix the bug dammit!! But please - for Gods sake, TAKE A SHOWER!
Let us assume the fact that posts are showing up in reverse order is simply another bug resulting from shoddy half-ass open sores programming, and NOT INTENTIONAL. This is what happens when dirty GNU hippies smoke too much weed before coding.
Drain your swampy armpits, wash off your rancid body odor and fix the bug dammit!! But please - for Gods sake, TAKE A SHOWER!
Let us assume the fact that posts are showing up in reverse order is simply another bug resulting from shoddy half-ass open sores programming, and NOT INTENTIONAL. This is what happens when dirty GNU hippies smoke too much weed before coding.
Drain your swampy armpits, wash off your rancid body odor and fix the bug dammit!! But please - for Gods sake, TAKE A SHOWER!
Let us assume the fact that posts are showing up in reverse order is simply another bug resulting from shoddy half-ass open sores programming, and NOT INTENTIONAL. This is what happens when dirty GNU hippies smoke too much weed before coding.
Drain your swampy armpits, wash off your rancid body odor and fix the bug dammit!! But please - for Gods sake, TAKE A SHOWER!
Let us assume the fact that posts are showing up in reverse order is simply another bug resulting from shoddy half-ass open sores programming, and NOT INTENTIONAL. This is what happens when dirty GNU hippies smoke too much weed before coding.
Drain your swampy armpits, wash off your rancid body odor and fix the bug dammit!! But please - for Gods sake, TAKE A SHOWER!
Re:What the hell is wrong with slashdot!!
on
Disinformation.com
·
· Score: -1
Do you mind if I take your post and add it to my troll library? It means this post will be reposted at random for the rest of eternity.
No answer indicates your compliance.
What the hell is wrong with slashdot!!
on
Disinformation.com
·
· Score: -1
Let us assume the fact that posts are showing up in reverse order is simply another bug resulting from shoddy half-ass open sores programming, and NOT INTENTIONAL. This is what happens when dirty GNU hippies smoke too much weed before coding.
Clean your swampy armpits, correct your rancid body odor and fix the bug dammit!! But please for Gods sake TAKE A SHOWER!
Let us assume the fact that posts are showing up in reverse order is simply another bug resulting from shoddy half-ass open sores programming, and NOT INTENTIONAL. This is what happens when dirty GNU hippies smoke too much weed before coding.
Clean your swampy armpits, correct your rancid body odor and fix the bug dammit!! But please for Gods sake TAKE A SHOWER!
Let us assume the fact that posts are showing up in reverse order is simply another bug resulting from shoddy half-ass open sores programming, and NOT INTENTIONAL. This is what happens when dirty GNU hippies smoke too much weed before coding.
Clean your swampy armpits, correct your rancid body odor and fix the bug dammit!! But please for Gods sake TAKE A SHOWER!
Let us assume the fact that posts are showing up in reverse order is simply another bug resulting from shoddy half-ass open sores programming, and NOT INTENTIONAL. This is what happens when dirty GNU hippies smoke too much weed before coding.
Clean your swampy armpits, correct your rancid body odor and fix the bug dammit!! But please for Gods sake TAKE A SHOWER!
The Quake III Arena 1.31 patch has been released. The release notes include the following:
Linux only: fixed sound crash, going around memset bug in glibc i586/i686
Wondering how a bug could exist in such a fundamental basic function such as memset, we contacted Heinous Turdballs of Linux fame, and he was kind enough to give a few minutes of his time.
Q: Thanks for your time in answering some questions for us
A: No problem. As you know, I am umemployed and have no life, which is of course how I got involved in Linux in the first place.
Q: OK, Mr. Turdballs. By the way, do you mind if I call you 'Dirty GNU Hippie'?
A: I would rather you didn't. I prefer the term 'Dirty Linux Hippie'. As you know, my ratty and nasty hairdo, my rancid steaming armpits and my putrid stench of body odor makes me qualified, I think.
Q: I quite agree. Can you tell us about the memset bug?
A: Sure. We dont really know who is responsible for the bug. We don't know who is making changes, why they make them, or when.
Q: Hmm.. sounds chaotic!
A: It sure is. But Linux is free!!! We are dirty smelly GNU hippies with natty greasy long hair, enjoying the FREE LOVE of GNU software!
Q: Come to think of it, Linux sure does crash alot.
A: Yeah, but that will be fixed in the service pack - er, I mean kernel release. We also have support for some new device drivers that came out 2 years ago. You just have to recompile your kernel with the correct command line switches, after configuring your make file and making the correct edits to/etc/fstab. By the way, if you screw that up, you are really fucked.
Q: Sounds good. So, how do you organize who is working on Linux?
A: Mostly we don't. We pretty much let anyone have at it with the code base. We figure at some point, someone who actually knows something about operating systems will do some work on it. It has to happen eventually, its like a million monkeys banging on a million typewriters. Literally.
Q: That's great. What normally happens?
A: Normally someone comes in and fucks everything up completely, but we don't know who they are because we never actually talk to anyone who is making changes to the code. We assume that if you are capable of signing up for a Hotmail account, you must be pretty good at computers and you should be a tech lead in a major open sores project.
Q: Open sores?
A: Yes, I am sure you have heard of it. Its free, therefore its good. Check out sourceforge.net, where bad project ideas go to a quiet and lonely death when the developers realize that 12 year old kids should not be SQA leads when they are constantly getting atomic wedgies because they wear shirts saying "Put Linux Anywhere".
Q: OK, Back to the topic. Whats a typical day in the life of a Linux developer?
A: Usually his mom wakes him up in time to catch the school bus, like 8:00. We encourage this because we want the developers to be well edumacted.
By the time he gets home at 2:00 (the Linux enthusiast does not participate in socalled "extra cirricular" activities, or worry about being "well rounded" and does not have a "social identity" or "play well with others") he has been beaten up a few times for wearing a "I GNU SPOCK" tshirt.
Then, to take out his frustration, he hammers away at the keyboard for a few hours. If the resultant code compiles, he will go ahead and check it in. Then mommy tucks him in for the night.
Q: Interesting. So who will be in charge of resolving the memset bug?
A: We have a nice prospect in mind. He has a strong background in manual labor and performing menial tasks. I'm not sure what his name is but he has a hotmail account, dAsUpAhZillAZ99@hotmail.com.
Q: Sounds great. I'm looking forward to it!
A: Just keep reading slashdot, where are the pimply nerds congregate. You may get assaulted by some homosexual linux zealots, but you will learn to like it.
Q: Sounds like fun!
A: Also hang out at sourceforge.net, where bad project ideas go to a quiet and lonely death among the other dirty GNU hippie projects.
Q: Thanks for your time!
A: Tell commander tuna taco I said I will pay in full after I get a real job. Then I will be back for another taco-snotting.
The Quake III Arena 1.31 patch has been released. The release notes include the following:
Linux only: fixed sound crash, going around memset bug in glibc i586/i686
Wondering how a bug could exist in such a fundamental basic function such as memset, we contacted Heinous Turdballs of Linux fame, and he was kind enough to give a few minutes of his time.
Q: Thanks for your time in answering some questions for us
A: No problem. As you know, I am umemployed and have no life, which is of course how I got involved in Linux in the first place.
Q: OK, Mr. Turdballs. By the way, do you mind if I call you 'Dirty GNU Hippie'?
A: I would rather you didn't. I prefer the term 'Dirty Linux Hippie'. As you know, my ratty and nasty hairdo, my rancid steaming armpits and my putrid stench of body odor makes me qualified, I think.
Q: I quite agree. Can you tell us about the memset bug?
A: Sure. We dont really know who is responsible for the bug. We don't know who is making changes, why they make them, or when.
Q: Hmm.. sounds chaotic!
A: It sure is. But Linux is free!!! We are dirty smelly GNU hippies with natty greasy long hair, enjoying the FREE LOVE of GNU software!
Q: Come to think of it, Linux sure does crash alot.
A: Yeah, but that will be fixed in the service pack - er, I mean kernel release. We also have support for some new device drivers that came out 2 years ago. You just have to recompile your kernel with the correct command line switches, after configuring your make file and making the correct edits to/etc/fstab. By the way, if you screw that up, you are really fucked.
Q: Sounds good. So, how do you organize who is working on Linux?
A: Mostly we don't. We pretty much let anyone have at it with the code base. We figure at some point, someone who actually knows something about operating systems will do some work on it. It has to happen eventually, its like a million monkeys banging on a million typewriters. Literally.
Q: That's great. What normally happens?
A: Normally someone comes in and fucks everything up completely, but we don't know who they are because we never actually talk to anyone who is making changes to the code. We assume that if you are capable of signing up for a Hotmail account, you must be pretty good at computers and you should be a tech lead in a major open sores project.
Q: Open sores?
A: Yes, I am sure you have heard of it. Its free, therefore its good. Check out sourceforge.net, where bad project ideas go to a quiet and lonely death when the developers realize that 12 year old kids should not be SQA leads when they are constantly getting atomic wedgies because they wear shirts saying "Put Linux Anywhere".
Q: OK, Back to the topic. Whats a typical day in the life of a Linux developer?
A: Usually his mom wakes him up in time to catch the school bus, like 8:00. We encourage this because we want the developers to be well edumacted.
By the time he gets home at 2:00 (the Linux enthusiast does not participate in socalled "extra cirricular" activities, or worry about being "well rounded" and does not have a "social identity" or "play well with others") he has been beaten up a few times for wearing a "I GNU SPOCK" tshirt.
Then, to take out his frustration, he hammers away at the keyboard for a few hours. If the resultant code compiles, he will go ahead and check it in. Then mommy tucks him in for the night.
Q: Interesting. So who will be in charge of resolving the memset bug?
A: We have a nice prospect in mind. He has a strong background in manual labor and performing menial tasks. I'm not sure what his name is but he has a hotmail account, dAsUpAhZillAZ99@hotmail.com.
Q: Sounds great. I'm looking forward to it!
A: Just keep reading slashdot, where are the pimply nerds congregate. You may get assaulted by some homosexual linux zealots, but you will learn to like it.
Q: Sounds like fun!
A: Also hang out at sourceforge.net, where bad project ideas go to a quiet and lonely death among the other dirty GNU hippie projects.
Q: Thanks for your time!
A: Tell commander tuna taco I said I will pay in full after I get a real job. Then I will be back for another taco-snotting.
The Quake III Arena 1.31 patch has been released. The release notes include the following:
Linux only: fixed sound crash, going around memset bug in glibc i586/i686
Wondering how a bug could exist in such a fundamental basic function such as memset, we contacted Heinous Turdballs of Linux fame, and he was kind enough to give a few minutes of his time.
Q: Thanks for your time in answering some questions for us
A: No problem. As you know, I am umemployed and have no life, which is of course how I got involved in Linux in the first place.
Q: OK, Mr. Turdballs. By the way, do you mind if I call you 'Dirty GNU Hippie'?
A: I would rather you didn't. I prefer the term 'Dirty Linux Hippie'. As you know, my ratty and nasty hairdo, my rancid steaming armpits and my putrid stench of body odor makes me qualified, I think.
Q: I quite agree. Can you tell us about the memset bug?
A: Sure. We dont really know who is responsible for the bug. We don't know who is making changes, why they make them, or when.
Q: Hmm.. sounds chaotic!
A: It sure is. But Linux is free!!! We are dirty smelly GNU hippies with natty greasy long hair, enjoying the FREE LOVE of GNU software!
Q: Come to think of it, Linux sure does crash alot.
A: Yeah, but that will be fixed in the service pack - er, I mean kernel release. We also have support for some new device drivers that came out 2 years ago. You just have to recompile your kernel with the correct command line switches, after configuring your make file and making the correct edits to/etc/fstab. By the way, if you screw that up, you are really fucked.
Q: Sounds good. So, how do you organize who is working on Linux?
A: Mostly we don't. We pretty much let anyone have at it with the code base. We figure at some point, someone who actually knows something about operating systems will do some work on it. It has to happen eventually, its like a million monkeys banging on a million typewriters. Literally.
Q: That's great. What normally happens?
A: Normally someone comes in and fucks everything up completely, but we don't know who they are because we never actually talk to anyone who is making changes to the code. We assume that if you are capable of signing up for a Hotmail account, you must be pretty good at computers and you should be a tech lead in a major open sores project.
Q: Open sores?
A: Yes, I am sure you have heard of it. Its free, therefore its good. Check out sourceforge.net, where bad project ideas go to a quiet and lonely death when the developers realize that 12 year old kids should not be SQA leads when they are constantly getting atomic wedgies because they wear shirts saying "Put Linux Anywhere".
Q: OK, Back to the topic. Whats a typical day in the life of a Linux developer?
A: Usually his mom wakes him up in time to catch the school bus, like 8:00. We encourage this because we want the developers to be well edumacted.
By the time he gets home at 2:00 (the Linux enthusiast does not participate in socalled "extra cirricular" activities, or worry about being "well rounded" and does not have a "social identity" or "play well with others") he has been beaten up a few times for wearing a "I GNU SPOCK" tshirt.
Then, to take out his frustration, he hammers away at the keyboard for a few hours. If the resultant code compiles, he will go ahead and check it in. Then mommy tucks him in for the night.
Q: Interesting. So who will be in charge of resolving the memset bug?
A: We have a nice prospect in mind. He has a strong background in manual labor and performing menial tasks. I'm not sure what his name is but he has a hotmail account, dAsUpAhZillAZ99@hotmail.com.
Q: Sounds great. I'm looking forward to it!
A: Just keep reading slashdot, where are the pimply nerds congregate. You may get assaulted by some homosexual linux zealots, but you will learn to like it.
Q: Sounds like fun!
A: Also hang out at sourceforge.net, where bad project ideas go to a quiet and lonely death among the other dirty GNU hippie projects.
Q: Thanks for your time!
A: Tell commander tuna taco I said I will pay in full after I get a real job. Then I will be back for another taco-snotting.
The Quake III Arena 1.31 patch has been released. The release notes include the following:
Linux only: fixed sound crash, going around memset bug in glibc i586/i686
Wondering how a bug could exist in such a fundamental basic function such as memset, we contacted Heinous Turdballs of Linux fame, and he was kind enough to give a few minutes of his time.
Q: Thanks for your time in answering some questions for us
A: No problem. As you know, I am umemployed and have no life, which is of course how I got involved in Linux in the first place.
Q: OK, Mr. Turdballs. By the way, do you mind if I call you 'Dirty GNU Hippie'?
A: I would rather you didn't. I prefer the term 'Dirty Linux Hippie'. As you know, my ratty and nasty hairdo, my rancid steaming armpits and my putrid stench of body odor makes me qualified, I think.
Q: I quite agree. Can you tell us about the memset bug?
A: Sure. We dont really know who is responsible for the bug. We don't know who is making changes, why they make them, or when.
Q: Hmm.. sounds chaotic!
A: It sure is. But Linux is free!!! We are dirty smelly GNU hippies with natty greasy long hair, enjoying the FREE LOVE of GNU software!
Q: Come to think of it, Linux sure does crash alot.
A: Yeah, but that will be fixed in the service pack - er, I mean kernel release. We also have support for some new device drivers that came out 2 years ago. You just have to recompile your kernel with the correct command line switches, after configuring your make file and making the correct edits to/etc/fstab. By the way, if you screw that up, you are really fucked.
Q: Sounds good. So, how do you organize who is working on Linux?
A: Mostly we don't. We pretty much let anyone have at it with the code base. We figure at some point, someone who actually knows something about operating systems will do some work on it. It has to happen eventually, its like a million monkeys banging on a million typewriters. Literally.
Q: That's great. What normally happens?
A: Normally someone comes in and fucks everything up completely, but we don't know who they are because we never actually talk to anyone who is making changes to the code. We assume that if you are capable of signing up for a Hotmail account, you must be pretty good at computers and you should be a tech lead in a major open sores project.
Q: Open sores?
A: Yes, I am sure you have heard of it. Its free, therefore its good. Check out sourceforge.net, where bad project ideas go to a quiet and lonely death when the developers realize that 12 year old kids should not be SQA leads when they are constantly getting atomic wedgies because they wear shirts saying "Put Linux Anywhere".
Q: OK, Back to the topic. Whats a typical day in the life of a Linux developer?
A: Usually his mom wakes him up in time to catch the school bus, like 8:00. We encourage this because we want the developers to be well edumacted.
By the time he gets home at 2:00 (the Linux enthusiast does not participate in socalled "extra cirricular" activities, or worry about being "well rounded" and does not have a "social identity" or "play well with others") he has been beaten up a few times for wearing a "I GNU SPOCK" tshirt.
Then, to take out his frustration, he hammers away at the keyboard for a few hours. If the resultant code compiles, he will go ahead and check it in. Then mommy tucks him in for the night.
Q: Interesting. So who will be in charge of resolving the memset bug?
A: We have a nice prospect in mind. He has a strong background in manual labor and performing menial tasks. I'm not sure what his name is but he has a hotmail account, dAsUpAhZillAZ99@hotmail.com.
Q: Sounds great. I'm looking forward to it!
A: Just keep reading slashdot, where are the pimply nerds congregate. You may get assaulted by some homosexual linux zealots, but you will learn to like it.
Q: Sounds like fun!
A: Also hang out at sourceforge.net, where bad project ideas go to a quiet and lonely death among the other dirty GNU hippie projects.
Q: Thanks for your time!
A: Tell commander tuna taco I said I will pay in full after I get a real job. Then I will be back for another taco-snotting.
The Quake III Arena 1.31 patch has been released. The release notes include the following:
Linux only: fixed sound crash, going around memset bug in glibc i586/i686
Wondering how a bug could exist in such a fundamental basic function such as memset, we contacted Heinous Turdballs of Linux fame, and he was kind enough to give a few minutes of his time.
Q: Thanks for your time in answering some questions for us
A: No problem. As you know, I am umemployed and have no life, which is of course how I got involved in Linux in the first place.
Q: OK, Mr. Turdballs. By the way, do you mind if I call you 'Dirty GNU Hippie'?
A: I would rather you didn't. I prefer the term 'Dirty Linux Hippie'. As you know, my ratty and nasty hairdo, my rancid steaming armpits and my putrid stench of body odor makes me qualified, I think.
Q: I quite agree. Can you tell us about the memset bug?
A: Sure. We dont really know who is responsible for the bug. We don't know who is making changes, why they make them, or when.
Q: Hmm.. sounds chaotic!
A: It sure is. But Linux is free!!! We are dirty smelly GNU hippies with natty greasy long hair, enjoying the FREE LOVE of GNU software!
Q: Come to think of it, Linux sure does crash alot.
A: Yeah, but that will be fixed in the service pack - er, I mean kernel release. We also have support for some new device drivers that came out 2 years ago. You just have to recompile your kernel with the correct command line switches, after configuring your make file and making the correct edits to/etc/fstab. By the way, if you screw that up, you are really fucked.
Q: Sounds good. So, how do you organize who is working on Linux?
A: Mostly we don't. We pretty much let anyone have at it with the code base. We figure at some point, someone who actually knows something about operating systems will do some work on it. It has to happen eventually, its like a million monkeys banging on a million typewriters. Literally.
Q: That's great. What normally happens?
A: Normally someone comes in and fucks everything up completely, but we don't know who they are because we never actually talk to anyone who is making changes to the code. We assume that if you are capable of signing up for a Hotmail account, you must be pretty good at computers and you should be a tech lead in a major open sores project.
Q: Open sores?
A: Yes, I am sure you have heard of it. Its free, therefore its good. Check out sourceforge.net, where bad project ideas go to a quiet and lonely death when the developers realize that 12 year old kids should not be SQA leads when they are constantly getting atomic wedgies because they wear shirts saying "Put Linux Anywhere".
Q: OK, Back to the topic. Whats a typical day in the life of a Linux developer?
A: Usually his mom wakes him up in time to catch the school bus, like 8:00. We encourage this because we want the developers to be well edumacted.
By the time he gets home at 2:00 (the Linux enthusiast does not participate in socalled "extra cirricular" activities, or worry about being "well rounded" and does not have a "social identity" or "play well with others") he has been beaten up a few times for wearing a "I GNU SPOCK" tshirt.
Then, to take out his frustration, he hammers away at the keyboard for a few hours. If the resultant code compiles, he will go ahead and check it in. Then mommy tucks him in for the night.
Q: Interesting. So who will be in charge of resolving the memset bug?
A: We have a nice prospect in mind. He has a strong background in manual labor and performing menial tasks. I'm not sure what his name is but he has a hotmail account, dAsUpAhZillAZ99@hotmail.com.
Q: Sounds great. I'm looking forward to it!
A: Just keep reading slashdot, where are the pimply nerds congregate. You may get assaulted by some homosexual linux zealots, but you will learn to like it.
Q: Sounds like fun!
A: Also hang out at sourceforge.net, where bad project ideas go to a quiet and lonely death among the other dirty GNU hippie projects.
Q: Thanks for your time!
A: Tell commander tuna taco I said I will pay in full after I get a real job. Then I will be back for another taco-snotting.
The Quake III Arena 1.31 patch has been released. The release notes include the following:
Linux only: fixed sound crash, going around memset bug in glibc i586/i686
Wondering how a bug could exist in such a fundamental basic function such as memset, we contacted Heinous Turdballs of Linux fame, and he was kind enough to give a few minutes of his time.
Q: Thanks for your time in answering some questions for us
A: No problem. As you know, I am umemployed and have no life, which is of course how I got involved in Linux in the first place.
Q: OK. Can you tell us about the memset bug?
A: Sure. We dont really know who is responsible for the bug. We don't know who is making changes,
why they make them, or when.
Q: Hmm.. sounds chaotic!
A: It sure is. But Linux is free. We dont need to worry about things like "stability" or "usability". These are just terms that evil corporations made up to sound fancy and make you THINK they are important. "User friendly" is just another word for "Not Free".
Q: Come to think of it, Linux sure does crash alot.
A: Yeah, but that will be fixed in the service pack - er, I mean kernel release. We also have support for some new device drivers that came out 2 years ago. You just have to recompile your kernel
with the correct command line switches, after configuring your make file and making the correct edits to/etc/fstab. By the way, if you screw that up, you are really fucked.
Q: Sounds good. So, how do you organize who is working on Linux?
A: Mostly we don't. We pretty much let anyone have at it with the code base. We figure at some point,
someone who actually knows something about operating systems will do some work on it. It has to happen eventually, its like a million monkeys banging on a million typewriters. Literally.
Q: That's great. What normally happens?
A: Normally someone comes in and fucks everything up completely, but we don't know who they are because we never actually talk to anyone who is making changes to the code. We assume that if you
are capable of signing up for a Hotmail account, you must be pretty good at computers and you should be a tech lead in a major open sores project.
Q: Open sores?
A: Yes, I am sure you have heard of it. Its free, therefore its good.
Q: OK, Back to the topic. Whats a typical day in the life of a Linux developer?
A: Usually his mom wakes him up in time to catch the school bus, like 8:00. We encourage this because we
want the developers to be well edumacted.
By the time he gets home at 2:00 (the Linux enthusiast does not participate in socalled "extra cirricular" activities, or worry about being "well rounded" and does not have a "social identity" or "play well with others") he has been beaten up a few times for
wearing a "GNU 4EVER" tshirt.
Then, to take out his frustration, he hammers away at the keyboard for a few hours. If the resultant code compiles, he will go ahead and check it in. Then mommy tucks him in for the night.
Q: Interesting. So who will be in charge of resolving the memset bug?
A: We have a nice prospect in mind. He has a strong background in manual labor and performing menial tasks. I'm not sure what his name is but he has a hotmail account, dAsUpAhZillAZ99@hotmail.com.
Q: Sounds great. I'm looking forward to it!
A: Just keep reading slashdot, where are the pimply nerds congregate. You may get assaulted by some homosexual linux zealots, but you will learn to like it.
Q: Thanks for your time!
A: Tell commander tuna taco I said I will pay in full after I get a real job. Then I will
be back for another taco-snotting.
Slashdot Mirror
You don't need to be a Kreskin [amdest.com] to predict the future of the Stinking sweaty Linux hippie. The hand writing is on the wall: Foul-stenched GNU hippies with swampy armpits face a bleak future. In fact there won't be any future at all for them because they are dying. Things are looking very bad for Hairy-backed GNU hippie. As many of us are already aware, they continue to lose market share. Red ink flows like a river of blood.
Let's keep to the facts and look at the numbers.
Troll leader Anonymouse Coward states that there are 7000 goatse.cx trolls. How many ascii art trolls are there? Let's see. The number of goatse.cx versus ascii art posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 ascii art trolls. Pimply-faced GNU hippies posts on Slashdot are about half of the volume of ascii art posts. Therefore there are about 700 Dirty GNU Hippies. A recent article put "first post" at about 80 percent of the troll market. Therefore there are (7000+1400+700)*4 = 36400 "first post" trolls. This is consistent with the number of first posts.
All major surveys show that Putrid smelling greasy GNU hippies have steadily declined in market share. Slashdot is very sick and its long term survival prospects are very dim. If Grubby Smelly Linux Hippies are to survive at all it will be among troll hobbyist dabblers. Slashdot continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, Dirty GNU Hippies are dead.
Drain your swampy armpits, wash off your rancid body odor and fix the bug dammit!! But please - for Gods sake, TAKE A SHOWER!
Drain your swampy armpits, wash off your rancid body odor and fix the bug dammit!! But please - for Gods sake, TAKE A SHOWER!
Drain your swampy armpits, wash off your rancid body odor and fix the bug dammit!! But please - for Gods sake, TAKE A SHOWER!
Drain your swampy armpits, wash off your rancid body odor and fix the bug dammit!! But please - for Gods sake, TAKE A SHOWER!
Drain your swampy armpits, wash off your rancid body odor and fix the bug dammit!! But please - for Gods sake, TAKE A SHOWER!
Drain your swampy armpits, wash off your rancid body odor and fix the bug dammit!! But please - for Gods sake, TAKE A SHOWER!
Drain your swampy armpits, wash off your rancid body odor and fix the bug dammit!! But please - for Gods sake, TAKE A SHOWER!
Do you mind if I take your post and add it to my troll library? It means this post will be reposted at random for the rest of eternity.
No answer indicates your compliance.
Clean your swampy armpits, correct your rancid body odor and fix the bug dammit!! But please for Gods sake TAKE A SHOWER!
Clean your swampy armpits, correct your rancid body odor and fix the bug dammit!! But please for Gods sake TAKE A SHOWER!
Clean your swampy armpits, correct your rancid body odor and fix the bug dammit!! But please for Gods sake TAKE A SHOWER!
Clean your swampy armpits, correct your rancid body odor and fix the bug dammit!! But please for Gods sake TAKE A SHOWER!
Linux only:
fixed sound crash, going around memset bug in glibc i586/i686
Wondering how a bug could exist in such a fundamental basic function such as memset, we contacted Heinous Turdballs of Linux fame, and he was kind enough to give a few minutes of his time.
Q: Thanks for your time in answering some questions for us
A: No problem. As you know, I am umemployed and have no life, which is of course how I got involved in Linux in the first place.
Q: OK, Mr. Turdballs. By the way, do you mind if I call you 'Dirty GNU Hippie'?
A: I would rather you didn't. I prefer the term 'Dirty Linux Hippie'. As you know, my ratty and nasty hairdo, my rancid steaming armpits and my putrid stench of body odor makes me qualified, I think.
Q: I quite agree. Can you tell us about the memset bug?
A: Sure. We dont really know who is responsible for the bug. We don't know who is making changes, why they make them, or when.
Q: Hmm.. sounds chaotic!
A: It sure is. But Linux is free!!! We are dirty smelly GNU hippies with natty greasy long hair, enjoying the FREE LOVE of GNU software!
Q: Come to think of it, Linux sure does crash alot.
A: Yeah, but that will be fixed in the service pack - er, I mean kernel release. We also have support for some new device drivers that came out 2 years ago. You just have to recompile your kernel with the correct command line switches, after configuring your make file and making the correct edits to /etc/fstab. By the way, if you screw that up, you are really fucked.
Q: Sounds good. So, how do you organize who is working on Linux?
A: Mostly we don't. We pretty much let anyone have at it with the code base. We figure at some point, someone who actually knows something about operating systems will do some work on it. It has to happen eventually, its like a million monkeys banging on a million typewriters. Literally.
Q: That's great. What normally happens?
A: Normally someone comes in and fucks everything up completely, but we don't know who they are because we never actually talk to anyone who is making changes to the code. We assume that if you are capable of signing up for a Hotmail account, you must be pretty good at computers and you should be a tech lead in a major open sores project.
Q: Open sores?
A: Yes, I am sure you have heard of it. Its free, therefore its good. Check out sourceforge.net, where bad project ideas go to a quiet and lonely death when the developers realize that 12 year old kids should not be SQA leads when they are constantly getting atomic wedgies because they wear shirts saying "Put Linux Anywhere".
Q: OK, Back to the topic. Whats a typical day in the life of a Linux developer?
A: Usually his mom wakes him up in time to catch the school bus, like 8:00. We encourage this because we want the developers to be well edumacted.
By the time he gets home at 2:00 (the Linux enthusiast does not participate in socalled "extra cirricular" activities, or worry about being "well rounded" and does not have a "social identity" or "play well with others") he has been beaten up a few times for wearing a "I GNU SPOCK" tshirt.
Then, to take out his frustration, he hammers away at the keyboard for a few hours. If the resultant code compiles, he will go ahead and check it in. Then mommy tucks him in for the night.
Q: Interesting. So who will be in charge of resolving the memset bug?
A: We have a nice prospect in mind. He has a strong background in manual labor and performing menial tasks. I'm not sure what his name is but he has a hotmail account, dAsUpAhZillAZ99@hotmail.com.
Q: Sounds great. I'm looking forward to it!
A: Just keep reading slashdot, where are the pimply nerds congregate. You may get assaulted by some homosexual linux zealots, but you will learn to like it.
Q: Sounds like fun!
A: Also hang out at sourceforge.net, where bad project ideas go to a quiet and lonely death among the other dirty GNU hippie projects.
Q: Thanks for your time!
A: Tell commander tuna taco I said I will pay in full after I get a real job. Then I will be back for another taco-snotting.
Linux only:
fixed sound crash, going around memset bug in glibc i586/i686
Wondering how a bug could exist in such a fundamental basic function such as memset, we contacted Heinous Turdballs of Linux fame, and he was kind enough to give a few minutes of his time.
Q: Thanks for your time in answering some questions for us
A: No problem. As you know, I am umemployed and have no life, which is of course how I got involved in Linux in the first place.
Q: OK, Mr. Turdballs. By the way, do you mind if I call you 'Dirty GNU Hippie'?
A: I would rather you didn't. I prefer the term 'Dirty Linux Hippie'. As you know, my ratty and nasty hairdo, my rancid steaming armpits and my putrid stench of body odor makes me qualified, I think.
Q: I quite agree. Can you tell us about the memset bug?
A: Sure. We dont really know who is responsible for the bug. We don't know who is making changes, why they make them, or when.
Q: Hmm.. sounds chaotic!
A: It sure is. But Linux is free!!! We are dirty smelly GNU hippies with natty greasy long hair, enjoying the FREE LOVE of GNU software!
Q: Come to think of it, Linux sure does crash alot.
A: Yeah, but that will be fixed in the service pack - er, I mean kernel release. We also have support for some new device drivers that came out 2 years ago. You just have to recompile your kernel with the correct command line switches, after configuring your make file and making the correct edits to /etc/fstab. By the way, if you screw that up, you are really fucked.
Q: Sounds good. So, how do you organize who is working on Linux?
A: Mostly we don't. We pretty much let anyone have at it with the code base. We figure at some point, someone who actually knows something about operating systems will do some work on it. It has to happen eventually, its like a million monkeys banging on a million typewriters. Literally.
Q: That's great. What normally happens?
A: Normally someone comes in and fucks everything up completely, but we don't know who they are because we never actually talk to anyone who is making changes to the code. We assume that if you are capable of signing up for a Hotmail account, you must be pretty good at computers and you should be a tech lead in a major open sores project.
Q: Open sores?
A: Yes, I am sure you have heard of it. Its free, therefore its good. Check out sourceforge.net, where bad project ideas go to a quiet and lonely death when the developers realize that 12 year old kids should not be SQA leads when they are constantly getting atomic wedgies because they wear shirts saying "Put Linux Anywhere".
Q: OK, Back to the topic. Whats a typical day in the life of a Linux developer?
A: Usually his mom wakes him up in time to catch the school bus, like 8:00. We encourage this because we want the developers to be well edumacted.
By the time he gets home at 2:00 (the Linux enthusiast does not participate in socalled "extra cirricular" activities, or worry about being "well rounded" and does not have a "social identity" or "play well with others") he has been beaten up a few times for wearing a "I GNU SPOCK" tshirt.
Then, to take out his frustration, he hammers away at the keyboard for a few hours. If the resultant code compiles, he will go ahead and check it in. Then mommy tucks him in for the night.
Q: Interesting. So who will be in charge of resolving the memset bug?
A: We have a nice prospect in mind. He has a strong background in manual labor and performing menial tasks. I'm not sure what his name is but he has a hotmail account, dAsUpAhZillAZ99@hotmail.com.
Q: Sounds great. I'm looking forward to it!
A: Just keep reading slashdot, where are the pimply nerds congregate. You may get assaulted by some homosexual linux zealots, but you will learn to like it.
Q: Sounds like fun!
A: Also hang out at sourceforge.net, where bad project ideas go to a quiet and lonely death among the other dirty GNU hippie projects.
Q: Thanks for your time!
A: Tell commander tuna taco I said I will pay in full after I get a real job. Then I will be back for another taco-snotting.
Linux only:
fixed sound crash, going around memset bug in glibc i586/i686
Wondering how a bug could exist in such a fundamental basic function such as memset, we contacted Heinous Turdballs of Linux fame, and he was kind enough to give a few minutes of his time.
Q: Thanks for your time in answering some questions for us
A: No problem. As you know, I am umemployed and have no life, which is of course how I got involved in Linux in the first place.
Q: OK, Mr. Turdballs. By the way, do you mind if I call you 'Dirty GNU Hippie'?
A: I would rather you didn't. I prefer the term 'Dirty Linux Hippie'. As you know, my ratty and nasty hairdo, my rancid steaming armpits and my putrid stench of body odor makes me qualified, I think.
Q: I quite agree. Can you tell us about the memset bug?
A: Sure. We dont really know who is responsible for the bug. We don't know who is making changes, why they make them, or when.
Q: Hmm.. sounds chaotic!
A: It sure is. But Linux is free!!! We are dirty smelly GNU hippies with natty greasy long hair, enjoying the FREE LOVE of GNU software!
Q: Come to think of it, Linux sure does crash alot.
A: Yeah, but that will be fixed in the service pack - er, I mean kernel release. We also have support for some new device drivers that came out 2 years ago. You just have to recompile your kernel with the correct command line switches, after configuring your make file and making the correct edits to /etc/fstab. By the way, if you screw that up, you are really fucked.
Q: Sounds good. So, how do you organize who is working on Linux?
A: Mostly we don't. We pretty much let anyone have at it with the code base. We figure at some point, someone who actually knows something about operating systems will do some work on it. It has to happen eventually, its like a million monkeys banging on a million typewriters. Literally.
Q: That's great. What normally happens?
A: Normally someone comes in and fucks everything up completely, but we don't know who they are because we never actually talk to anyone who is making changes to the code. We assume that if you are capable of signing up for a Hotmail account, you must be pretty good at computers and you should be a tech lead in a major open sores project.
Q: Open sores?
A: Yes, I am sure you have heard of it. Its free, therefore its good. Check out sourceforge.net, where bad project ideas go to a quiet and lonely death when the developers realize that 12 year old kids should not be SQA leads when they are constantly getting atomic wedgies because they wear shirts saying "Put Linux Anywhere".
Q: OK, Back to the topic. Whats a typical day in the life of a Linux developer?
A: Usually his mom wakes him up in time to catch the school bus, like 8:00. We encourage this because we want the developers to be well edumacted.
By the time he gets home at 2:00 (the Linux enthusiast does not participate in socalled "extra cirricular" activities, or worry about being "well rounded" and does not have a "social identity" or "play well with others") he has been beaten up a few times for wearing a "I GNU SPOCK" tshirt.
Then, to take out his frustration, he hammers away at the keyboard for a few hours. If the resultant code compiles, he will go ahead and check it in. Then mommy tucks him in for the night.
Q: Interesting. So who will be in charge of resolving the memset bug?
A: We have a nice prospect in mind. He has a strong background in manual labor and performing menial tasks. I'm not sure what his name is but he has a hotmail account, dAsUpAhZillAZ99@hotmail.com.
Q: Sounds great. I'm looking forward to it!
A: Just keep reading slashdot, where are the pimply nerds congregate. You may get assaulted by some homosexual linux zealots, but you will learn to like it.
Q: Sounds like fun!
A: Also hang out at sourceforge.net, where bad project ideas go to a quiet and lonely death among the other dirty GNU hippie projects.
Q: Thanks for your time!
A: Tell commander tuna taco I said I will pay in full after I get a real job. Then I will be back for another taco-snotting.
Linux only:
fixed sound crash, going around memset bug in glibc i586/i686
Wondering how a bug could exist in such a fundamental basic function such as memset, we contacted Heinous Turdballs of Linux fame, and he was kind enough to give a few minutes of his time.
Q: Thanks for your time in answering some questions for us
A: No problem. As you know, I am umemployed and have no life, which is of course how I got involved in Linux in the first place.
Q: OK, Mr. Turdballs. By the way, do you mind if I call you 'Dirty GNU Hippie'?
A: I would rather you didn't. I prefer the term 'Dirty Linux Hippie'. As you know, my ratty and nasty hairdo, my rancid steaming armpits and my putrid stench of body odor makes me qualified, I think.
Q: I quite agree. Can you tell us about the memset bug?
A: Sure. We dont really know who is responsible for the bug. We don't know who is making changes, why they make them, or when.
Q: Hmm.. sounds chaotic!
A: It sure is. But Linux is free!!! We are dirty smelly GNU hippies with natty greasy long hair, enjoying the FREE LOVE of GNU software!
Q: Come to think of it, Linux sure does crash alot.
A: Yeah, but that will be fixed in the service pack - er, I mean kernel release. We also have support for some new device drivers that came out 2 years ago. You just have to recompile your kernel with the correct command line switches, after configuring your make file and making the correct edits to /etc/fstab. By the way, if you screw that up, you are really fucked.
Q: Sounds good. So, how do you organize who is working on Linux?
A: Mostly we don't. We pretty much let anyone have at it with the code base. We figure at some point, someone who actually knows something about operating systems will do some work on it. It has to happen eventually, its like a million monkeys banging on a million typewriters. Literally.
Q: That's great. What normally happens?
A: Normally someone comes in and fucks everything up completely, but we don't know who they are because we never actually talk to anyone who is making changes to the code. We assume that if you are capable of signing up for a Hotmail account, you must be pretty good at computers and you should be a tech lead in a major open sores project.
Q: Open sores?
A: Yes, I am sure you have heard of it. Its free, therefore its good. Check out sourceforge.net, where bad project ideas go to a quiet and lonely death when the developers realize that 12 year old kids should not be SQA leads when they are constantly getting atomic wedgies because they wear shirts saying "Put Linux Anywhere".
Q: OK, Back to the topic. Whats a typical day in the life of a Linux developer?
A: Usually his mom wakes him up in time to catch the school bus, like 8:00. We encourage this because we want the developers to be well edumacted.
By the time he gets home at 2:00 (the Linux enthusiast does not participate in socalled "extra cirricular" activities, or worry about being "well rounded" and does not have a "social identity" or "play well with others") he has been beaten up a few times for wearing a "I GNU SPOCK" tshirt.
Then, to take out his frustration, he hammers away at the keyboard for a few hours. If the resultant code compiles, he will go ahead and check it in. Then mommy tucks him in for the night.
Q: Interesting. So who will be in charge of resolving the memset bug?
A: We have a nice prospect in mind. He has a strong background in manual labor and performing menial tasks. I'm not sure what his name is but he has a hotmail account, dAsUpAhZillAZ99@hotmail.com.
Q: Sounds great. I'm looking forward to it!
A: Just keep reading slashdot, where are the pimply nerds congregate. You may get assaulted by some homosexual linux zealots, but you will learn to like it.
Q: Sounds like fun!
A: Also hang out at sourceforge.net, where bad project ideas go to a quiet and lonely death among the other dirty GNU hippie projects.
Q: Thanks for your time!
A: Tell commander tuna taco I said I will pay in full after I get a real job. Then I will be back for another taco-snotting.
Linux only:
fixed sound crash, going around memset bug in glibc i586/i686
Wondering how a bug could exist in such a fundamental basic function such as memset, we contacted Heinous Turdballs of Linux fame, and he was kind enough to give a few minutes of his time.
Q: Thanks for your time in answering some questions for us
A: No problem. As you know, I am umemployed and have no life, which is of course how I got involved in Linux in the first place.
Q: OK, Mr. Turdballs. By the way, do you mind if I call you 'Dirty GNU Hippie'?
A: I would rather you didn't. I prefer the term 'Dirty Linux Hippie'. As you know, my ratty and nasty hairdo, my rancid steaming armpits and my putrid stench of body odor makes me qualified, I think.
Q: I quite agree. Can you tell us about the memset bug?
A: Sure. We dont really know who is responsible for the bug. We don't know who is making changes, why they make them, or when.
Q: Hmm.. sounds chaotic!
A: It sure is. But Linux is free!!! We are dirty smelly GNU hippies with natty greasy long hair, enjoying the FREE LOVE of GNU software!
Q: Come to think of it, Linux sure does crash alot.
A: Yeah, but that will be fixed in the service pack - er, I mean kernel release. We also have support for some new device drivers that came out 2 years ago. You just have to recompile your kernel with the correct command line switches, after configuring your make file and making the correct edits to /etc/fstab. By the way, if you screw that up, you are really fucked.
Q: Sounds good. So, how do you organize who is working on Linux?
A: Mostly we don't. We pretty much let anyone have at it with the code base. We figure at some point, someone who actually knows something about operating systems will do some work on it. It has to happen eventually, its like a million monkeys banging on a million typewriters. Literally.
Q: That's great. What normally happens?
A: Normally someone comes in and fucks everything up completely, but we don't know who they are because we never actually talk to anyone who is making changes to the code. We assume that if you are capable of signing up for a Hotmail account, you must be pretty good at computers and you should be a tech lead in a major open sores project.
Q: Open sores?
A: Yes, I am sure you have heard of it. Its free, therefore its good. Check out sourceforge.net, where bad project ideas go to a quiet and lonely death when the developers realize that 12 year old kids should not be SQA leads when they are constantly getting atomic wedgies because they wear shirts saying "Put Linux Anywhere".
Q: OK, Back to the topic. Whats a typical day in the life of a Linux developer?
A: Usually his mom wakes him up in time to catch the school bus, like 8:00. We encourage this because we want the developers to be well edumacted.
By the time he gets home at 2:00 (the Linux enthusiast does not participate in socalled "extra cirricular" activities, or worry about being "well rounded" and does not have a "social identity" or "play well with others") he has been beaten up a few times for wearing a "I GNU SPOCK" tshirt.
Then, to take out his frustration, he hammers away at the keyboard for a few hours. If the resultant code compiles, he will go ahead and check it in. Then mommy tucks him in for the night.
Q: Interesting. So who will be in charge of resolving the memset bug?
A: We have a nice prospect in mind. He has a strong background in manual labor and performing menial tasks. I'm not sure what his name is but he has a hotmail account, dAsUpAhZillAZ99@hotmail.com.
Q: Sounds great. I'm looking forward to it!
A: Just keep reading slashdot, where are the pimply nerds congregate. You may get assaulted by some homosexual linux zealots, but you will learn to like it.
Q: Sounds like fun!
A: Also hang out at sourceforge.net, where bad project ideas go to a quiet and lonely death among the other dirty GNU hippie projects.
Q: Thanks for your time!
A: Tell commander tuna taco I said I will pay in full after I get a real job. Then I will be back for another taco-snotting.
Linux only:
fixed sound crash, going around memset bug in glibc i586/i686
Wondering how a bug could exist in such a fundamental basic function such as memset, we contacted Heinous Turdballs of Linux fame, and he was kind enough to give a few minutes of his time.
Q: Thanks for your time in answering some questions for us
A: No problem. As you know, I am umemployed and have no life, which is of course how I got involved in Linux in the first place.
Q: OK. Can you tell us about the memset bug?
A: Sure. We dont really know who is responsible for the bug. We don't know who is making changes,
why they make them, or when.
Q: Hmm.. sounds chaotic!
A: It sure is. But Linux is free. We dont need to worry about things like "stability" or "usability". These are just terms that evil corporations made up to sound fancy and make you THINK they are important. "User friendly" is just another word for "Not Free".
Q: Come to think of it, Linux sure does crash alot.
A: Yeah, but that will be fixed in the service pack - er, I mean kernel release. We also have support for some new device drivers that came out 2 years ago. You just have to recompile your kernel /etc/fstab. By the way, if you screw that up, you are really fucked.
with the correct command line switches, after configuring your make file and making the correct edits to
Q: Sounds good. So, how do you organize who is working on Linux?
A: Mostly we don't. We pretty much let anyone have at it with the code base. We figure at some point,
someone who actually knows something about operating systems will do some work on it. It has to happen eventually, its like a million monkeys banging on a million typewriters. Literally.
Q: That's great. What normally happens?
A: Normally someone comes in and fucks everything up completely, but we don't know who they are because we never actually talk to anyone who is making changes to the code. We assume that if you
are capable of signing up for a Hotmail account, you must be pretty good at computers and you should be a tech lead in a major open sores project.
Q: Open sores?
A: Yes, I am sure you have heard of it. Its free, therefore its good.
Q: OK, Back to the topic. Whats a typical day in the life of a Linux developer?
A: Usually his mom wakes him up in time to catch the school bus, like 8:00. We encourage this because we
want the developers to be well edumacted.
By the time he gets home at 2:00 (the Linux enthusiast does not participate in socalled "extra cirricular" activities, or worry about being "well rounded" and does not have a "social identity" or "play well with others") he has been beaten up a few times for
wearing a "GNU 4EVER" tshirt.
Then, to take out his frustration, he hammers away at the keyboard for a few hours. If the resultant code compiles, he will go ahead and check it in. Then mommy tucks him in for the night.
Q: Interesting. So who will be in charge of resolving the memset bug?
A: We have a nice prospect in mind. He has a strong background in manual labor and performing menial tasks. I'm not sure what his name is but he has a hotmail account, dAsUpAhZillAZ99@hotmail.com.
Q: Sounds great. I'm looking forward to it!
A: Just keep reading slashdot, where are the pimply nerds congregate. You may get assaulted by some homosexual linux zealots, but you will learn to like it.
Q: Thanks for your time!
A: Tell commander tuna taco I said I will pay in full after I get a real job. Then I will
be back for another taco-snotting.
This thread
will live in the anals of slashdot inflamery:
Moderation Totals: Offtopic=33, Flamebait=1, Troll=1, Redundant=2, Insightful=8, Interesting=22, Informative=7, Overrated=2, Total=76.
Mr. TACO, TEAR DOWN THIS WALL!!!!
This thread
will live in the anals of slashdot inflamery:
Moderation Totals: Offtopic=33, Flamebait=1, Troll=1, Redundant=2, Insightful=8, Interesting=22, Informative=7, Overrated=2, Total=76.
Mr. TACO, TEAR DOWN THIS WALL!!!!
This thread
will live in the anals of slashdot inflamery.
Mr. TACO, TEAR DOWN THIS WALL!!!!
So, what do you think about that, bitch!?
Bite me!! Losers. You all suck.
Im curious about your .sig.
You seem to be some kind of a moron.
Is that a fair statement?