If you were alive in the 1980s you will also remember the war on drugs. There was a wonderful parody that featured MS-DOS, of course:
|
As a special witness to "At first, I just did it on weekends, with my friends, you know? We never wanted to hurt anyone. The girls loved it. We'd all sit around the computer and do a little DOS. It was just a kick. At least that's what we thought. Then it got worse." "It got so I'd have to do some DOS during the weekdays. After a while I couldn't even wake up in the morning without that craving to do DOS. Then it started affecting my job. I would just have to do it during my break. Maybe a Mode command or two. I eventually started doing DOS just to get through the day. Of course, it screwed up my mind so much that I couldn't even function as a normal cat. DOS got me fired from my job." "I'm lucky today. I've overcome my DOS problem. It wasn't easy. If you're smart, just don't start. Remember, if a weirdo in a blue suit offers you some DOS, just say no." MSDOS … Just Say No A special message brought to you by The President's War on DOS Committee. © 1987 |
The original file is a Postscript file that I've been carrying around for around 30 years. I don't know why it popped into my head, but here we are. Download a PDF by clicking here.
For a long time computer science students were taught the Open Systems Interconnection (OSI) networking model, which was a formalization that described all of the possible layers of a network from the electrical signalling all of the way to end user applications. It was needlessly complicated and verbose. So imagine how fun it was when somebody did a brutal take-down of the OSI networking model by comparing it to a Taco Bell Sevel Layer Burrito:
To hell with the OSI 7 Layer Model
Back in the 1980's, when all music sucked and men dressed like sissies, a bunch of sissy Europeans got together in a passionate effort to overstandardize computer networking. They created this thing called the Open Systems Interconnection (OSI) networking suite. Anyone who has taken a CS (Computer Science) or CIS (Computer Information Systems) course knows this; they cram this fact down the student's throat from day freaking one. It is only when the student enters the real world do they realise that the OSI seven layer model is a sham.
First off, what the hell is any European organization doing dictating standards that have to do with computers or networking? (Well...besides that paradigm shifting Linux stuff and all that other huge shit) Hello! How many bleeding edge computer or networking innovations have we seen come out of the European continent? Are they even participating in this revolution? Part of this is not really directly their fault; it probably has something to do with the fact that a minimum of venture capital spent in Europe even goes into high tech; most of it goes into high fashion and entertainment instead. No wonder we booger eating Yanks think the Europeans are sissies. Hey, we may be pigs, but at least we are running the Internet. Nah nah na-na nah.
Secondly, the seven layers proposed by OSI are completely out of touch with reality. The defacto networking standard is TCP/IP. TCP/IP is the grandaddy of XNS, IPX/SPX, Banyan, AppleTalk, and a host of other protocols and pre-dates that seven layer thing because it was funded by the largest organization in the world devoted to maintaining Eurocentric socioeconomic domination; the US Military. And for some reason, that makes it better. Yeah.
And yet this seven layer curse won't go away. Companies still have staffs of Marketing inspired artists drawing up elaborate maps of how their protocol maps to the OSI Seven Layer Model. Sham! Its a sham I say! To hell with the OSI Seven Layer Model!
To its credit, we have found that there are indeed a few things in this world that actually follow the seven layer model; but none of them have anything relevant to do with today's high tech world. Case in point; the Taco Bell Seven Layer Burrito.
You can currently buy one of these babies for just a buck (well, 99 cents anyway) and experience for yourself a portable example of what happens when pure Hispanic culinary brilliance gets flattened into consistency by the grinding blandness of American commercialization. I should know; I eat there once a week and suggest Taco Bell to all my friends.
To illustrate my point, I have included a table that compares the Taco Bell Seven Layer Burrito to the sham that is the OSI seven layer model.
OSI Seven Layer Model |
Taco Bell Seven Layer Burrito |
|---|---|
|
Layer 1: The Physical Layer The Physical Layer describes physical properties of the media, such as the electrical properties and interpretation of exchanged signals. |
Layer 1: Refried Beans Refried beans are always the first thing to be placed on any kind of intelligently built burrito. They not only make a great foundation, but also act as a glue to hold the tortilla together. And due to their high levels of sugars, they are also the largest reason you'll get gas after eating one of them. The resulting gas causes electrical exchanges, most often between married couples aproximately 6-8 hours after ingestion. |
|
Layer 2: The Data Link Layer The Datalink Layer describes the logical organization of data bits transmitted on a particular medium, for example the logical addressing of Ethernet packets. |
Layer 2: Seasoned Rice Rice is logically the second ingredient on a burrito. It is also a filler, just as beans are, but don't qualify as a foundation and cannot hold the tortilla together like beans can. Therefore, rice builds upon the foundation that beans have built, and rightfully deserve to always be the second ingredient. |
|
Layer 3: The Network Layer The Network Layer describes how a series of exchanges over various data links can deliver data between any two nodes in a network; basically describing how packets get routed through the 'net. |
Layer 3: Lettuce One of the most wonderful properties of Iceberg Lettuce is its almost complete lack of nutritional value and its ability to route itself directly through your digestive tract to your back door. And it, like beans, also gives you gas. |
|
Layer 4: The Transport Layer The Transport Layer describes the quality and nature of the data delivery. |
Layer 4: Tomatoes Tomatoes are added to the burrito to give the eater the impression that they are eating something healthy and natural. |
|
Layer 5: The Session Layer The Session Layer describes the organization of data sequences larger than the packets handled by the lower layers. Basically, its the job of the Session Layer to fix what the other layers have screwed up. |
Layer 5: Guacamole Guacamole is added to hide any kind of poor or bland flavor that may have come with the Iceberg Lettuce, the rice, or the beans. |
|
Layer 6: The Presentation Layer The Presentation Layer describes the syntax of data being transferred for communication with dissimilar systems. |
Layer 6: Cheese There isn't a whole lot of combinations of incompatable foods a bunch of cheese can't gloss over with its unique mixture of fats, cholesterol, and salt. When in doubt, throw in some cheese. |
|
Layer 7: The Application Layer The Application Layer describes how real work actually gets done; its the reason we do things in the first place. |
Layer 7: Sour Cream Its been said that the purpose of sour cream is to allow white dudes to eat spicy food. Without sour cream, most white folks couldn't bear to eat exotic foods like the kind that Taco Bell are serving up. |
Try and see how many things you can find that honestly conform to this sham of a model, and let me know what you find.
Ok, so this is flawed. I spaced that there is an eighth layer; the flour tortilla. No biggy; here's a better one:
Thank you, Dogman! The original can be viewed over at archive.org.
Every properly trained system administrator has secretly lived out their professional fantasies
through the work of Simon Travaglia, who wrote the BoFH series. Imagine an evil system administrator. And a smart one too. Who has utter contempt for his users, his boss, and most of the world in general.Simon posted these to Usenet in the early 1990s. Here is a choice excerpt from Episode 11, 1995:
<snip>
While I'm in the computer room, a hard drive arrives in preparation for a disk replacement, which means the engineer can't be far away.
Quick as a flash I have the box open, wind a couple of paper clips round the power terminals at the back of the drive and return it to its packaging.
Scant seconds later a pin-striped service engineer arrives.
"Hi, I've come to replace the faulty drive," he buzzes.
I lead him over to the machine with the Fault Status on it and he goes to work.
"Will you be wanting me to have the system shut down?" I ask.
"Oh no, didn't you know, this machine is mirrored and hot-swapable. I just pull the cover off like this."
Clip!
"Loosen these two retaining screws, grab the new disk and ... ... Hey, did you open this bag?"
"No, it must have been sent like that."
"Oh. It was probably the office when they pre-formatted it."
He has now added 'lying to the client' to his list of sins. Tragic.
He continues: "I get the new drive in one hand, slide out the old drive like so ... place it on the ground like so ..."
Clunk!
"And slide in the new one like so ... and ..."
BANG!
The smell of ozone tells me that both the paper clips and the power supply are no more. Time to play dirty.
"What the hell happened?!" I demand.
"Er, it appears that the replacement drive was slightly faulty, and the extra load may have overworked your power supply."
"You blew up our machine!"
"No, no, it's only a power supply problem. All I need to do is slide the disk out like so, switch the power off and flick this switch to change over the power supplies. Now I switch her on, and ..."
Nothing happens.
"Nothing's happened!"
He hits me with the old engineer special: "That's interesting!"
"Yeah, that's what yesterday's engineer said when he blew the other power supply."
A network loading alarm shakes me awake in front of my terminal and I realise that it had all been a pleasant dream. Ah well, I guess a network engineer's got to know his limitations.
In other epsides things blow up, phone calls get misrouted, people lose of all of their files because they run out of quota and demand more, more things blow up, etc. You get the idea.
Simon has the entire archive posted at "The Bastard Operator From Hell". Enjoy it!
An IBM memo annoucing the availability of replacement parts:
Abstract: Mouse Balls Available as FRU (Field Replacement Unit)
Mouse balls are now available as FRU. Therefore, if a mouse fails to operate or should it perform erratically, it may need a ball replace-ment. Because of the delicate nature of this procedure, replacement of mouse balls should only be attempted by properly trained personnel.
Before proceeding, determine the type of mouse balls by examining the underside of the mouse. Domestic balls will be larger and harder than foreign balls. Ball removal procedures differ depending upon manufac- turer of the mouse. Foreign balls can be replaced using the pop-off method. Domestic balls are replaced using the twist-off method. Mouse balls are not usually static sensitive. However, excessive handling can result in sudden discharge. Upon completion of ball replacement, the mouse may be used immediately.
It is recommended that each replacer have a pair of spare balls for maintaining optimum customer satisfaction, and that any customer missing his balls should suspect local personnel of removing these necessary items.
To re-order, specify one of the following:
P/N 33F8462 - Domestic Mouse Balls
P/N 33F8461 - Foreign Mouse Balls
I worked for IBM for over 18 years, and I doubt this was an official communication. But it could have been.
All computer people know about Read-Only Memory, but have you ever considered possibilities that write-Only Memory creates? Signetics, a forward thinking company did and offered a product to address these use cases:
Enjoy the original data sheet by clicking on the image below.
|
|
I clipped this from the newspaper when it ran back in the 1980's; what you are looking at is a scan of the faded newspaper.
GENE SIMMONS NEVER HAD A PERSONAL COMPUTER WHEN HE WAS A KID
How do we know? We know because our own well-documented research has shown conclusively that a child who lacks his own personal computer during those earlist school years will very probably grow up to be a bass player in a heavy-metal rock band who wears women's fishnet pantyhouse and sticks his tongue down to his kneecaps. Just like Gene Simmons.
Your child's future doesn't have to look like this. The Banana Junior 6000 Self-portable Personal Computer System, complete with optional software - Bananawrite, Bananadraw, Bananafile and Bananamanager - is just what your four-year-old needs to compete in today's cut-throat world of high tech and high expectations.
Say NO to spanex and chrome. Say YES to silicon.
The Banana Junior 6000 …
Buy one before it's too late.
Gene's mother wishes she had.
As the proud owner of a PCjr at the time, thank you Berke Breathed. (Bloom County was soooo good.)
I don't hold the copyright to any of this, I'm just trying to spread some joy. If this causes a problem let me know and I'll rectify it immediately.
Created January 26th, 2022