Dictionary De - En
De - Es
De - Pt| Proverbs, aphorisms, quotations (English) | by Linux fortune |
| The GPL Is Not Y2K-Compliant! BOSTON, MA -- Panic ensued earlier today at GNU Project Headquarters when it was discovered that the GNU General Public License is not ready for the year 2000. Thankfully, the panic quickly subsided when RMS posted an emergency diff file to Usenet that patches the GPL to eliminate the problem. The non-Y2K compliant material appears on lines 295 and 316 of version 2.0 of the GPL. Both lines contain the text, "Copyright (C) 19yy ", a classic example of unpreparedness for the year 2000. Microsoft was quick to respond to the news, saying in a rushed press release, "At least our license agreements don't contain any Y2K issues." The GNU Project immediately countered Microsoft's statement with a press release that said simply, "Whatever". | |
| Brief History Of Linux (#2) Hammurabi's Open-Source Code Hammurabi became king of Babylonia around 1750BC. Under his reign, a sophisticated legal code developed; Version 1, containing 282 clauses, was carved into a large rock column open to the public. However, the code contained several errors (Hammurabi must have been drunk), which numerous citizens demanded be fixed. One particularly brave Babylonian submitted to the king's court a stack of cloth patches that, when affixed to the column, would cover up and correct the errors. With the king's approval, these patches were applied to the legal code; within a month a new corrected rock column (Version 2.0) was officially announced. While future kings never embraced this idea (who wanted to admit they made a mistake?), the concept of submitting patches to fix problems is now taken for granted in modern times. | |
| Brief History Of Linux (#24) Linus Torvalds quotes from his interview in "LinuxNews" (October 1992): "I doubt Linux will be here to stay, and maybe Hurd is the wave of the future (and maybe not)..." "I'm most certainly going to continue to support it, until it either dies out or merges with something else. That doesn't necessarily mean I'll make weekly patches for the rest of my life, but hopefully they won't be needed as much when things stabilize." [If only he knew what he was getting into.] "World domination? No, I'm not interested in that. Galactic domination, on the other hand..." "Several people have already wondered if Linux should adopt a logo or mascot. Somebody even suggested a penguin for some strange reason, which I don't particularly like: how is a flightless bird supposed to represent an operating system? Well, it might work okay for Microsoft or even Minix..." "I would give Andy Tanenbaum a big fat 'F'." | |
| Brief History Of Linux (#25) By the mid-1990's the Linux community was burgeoning as countless geeks fled Redmond monopolistic oppression, Armonk cluelessness, and Cupertino click-and-drool reality distortion fields. By late 1991 there was an informal Linux User Group in Finland, although its primary focus was Linux advocacy, not drinking beer and telling Microsoft jokes as most do today. Kernel development continued at a steady clip, with more and more people joining in and hoping that their patches would be accepted by the Benevolent Dictator himself. To have a patch accepted by Linus was like winning the Nobel Prize, but to face rejection was like being rejected from Clown College. The reputation game certainly sparked some flame wars. One of the most memorable crisis was over the behavior of the delete and backspace keys. A certain faction of hackers wanted the Backspace key to actually backspace and the Delete key to actually delete. Linus wasn't too keen on the proposed changes; "It Works For Me(tm)" is all he said. Some observers now think Linus was pulling rank to get back at the unknown hacker who managed to slip a patch by him that replaced the "Kernel panic" error with "Kernel panic: Linus probably fscked it all up again". | |
| Microsoft Fights Linux -- By Contributing Kernel Patches If you can't beat 'em, join 'em... and then destory 'em. That seems to be the new Microsoft strategy for dealing with Linux. Instead of fighting a FUD or patent war, Microsoft operatives are doing something totally out of character: they are contributing patches for the Linux kernel and other programs. Don't worry, Microsoft is still evil. It's all part of a massive denial of service attack against Linus Torvalds designed to bring kernel development to a standstill. By sending over 10,000 patches per minute by email to Linus and other top kernel hackers, Microsoft has exposed Linux's Achilles heel. "I can't believe this is happening!" one stressed-out kernel hacker said at a press conference on IRC. "If this goes on, we may have to conduct kernel development over some other network protocol, like avian carriers... Aw crap, there's smoke coming from my email server! Ahh... it can't handle the load!" At this point the developer cut off and we haven't heard from him since. At first Linus was unsure where the deluge of patches was coming from. But when he saw one patch to replace kernel panics with bluescreens, the source was pretty obvious. "Oh, and the fact that all of the patches are covered by Microsoft's GPL [Grossly Private License] was a dead giveaway, too," | |
| The Humorix Oracle explains how to get a job at a major corporation: 1. Find an exploit in Microsoft IIS or another buggy Microsoft product to which large corporations rarely apply security patches. 2. Create a virus or worm that takes advantage of this exploit and then propogates itself by selecting IP numbers at random and then trying to infect those machines. 3. Keep an eye on your own website's server logs. When your virus starts propogating, your server will be hit with thousands of attacks from other infected systems trying to spread the virus to your machine. 4. Make a list of the IP numbers of all of the infected machines. 5. Perform a reverse DNS lookup on these IP numbers. 6. Make a note of all of the Fortune 500 companies that appear on the list of infected domains. 7. Send your resume to these companies and request an interview for a system administrator position. These companies are hiring -- whether they realize it or not. 8. Use your new salary to hire a good defense lawyer when the FBI comes knocking. | |
| Solving The Virus Problem Once And For All System administrators across the globe have tried installing anti-virus software. They've tried lecturing employees not to open unsolicited email attachments. They've tried installing firewalls and the latest security patches. But even with these precautions, email viruses continue to rank third only to Solitaire and the Blue Screen Of Death in the amount of lost productivity they cause. Meanwhile, Microsoft Exchange and LookOut! remain as the number one virus delivery products on the market today. But maybe not for much longer. A group of disgruntled administrators have teamed up to produce and sell a brand new way to fight viruses, one that attacks the root of the problem: stupid users. Salivating Dogs, Inc. of Ohio has unveiled the "Clue Delivery System" (CDS), a small device that plugs into the back of a standard PC keyboard and delivers a mild electric shock whenever the luser does something stupid. The device is triggered by a Windows program that detects when the luser attempts to open an unsolicited email attachment or perform another equally dangerous virus-friendly action. | |
| Linus Torvalds wrote: > Ehh.. Telling people "don't do that" simply doesn't work. Not if they can > do it easily anyway. Things really don't get fixed unless people have a > certain pain-level to induce it to get fixed. Umm... How about the following: you hit delete on patches that introduce new ioctls, I help to provide required level of pain. Deal? - Al Viro on linux-kernel | |
| Patches benefit all mankind. Products benefit the vendor. - Richard Gooch on linux-kernel | |
| Looks nice to me but about the only way you are likely to get Linus to take in kernel debugging patches is to turn them into hex and disguise them as USB firmware ;) - Alan Cox's guide on submitting Linux patches, today: chapter #3, kernel debuggers | |
| Re-sending is always the right thing to do. Sometimes it takes a few times, and you can add a small exasperated message at the top by the third time ("Don't you love me any more?"). - Linus Torvalds about sending patches to him | |
| Also, I've been getting a _lot_ of patches, and if yours didn't show up it's because I got too many. Never fear, there's always tomorrow. Except in this case it's "in a week or two". - Linus Torvalds announcing his holiday on linux-kernel | |
| Anyway, Zen And Art Of Feeding Patches Into Tree is a topic for a different thread... - Al Viro on linux-kernel | |
| <Oskuro> Overfiend: many patches on top of 4.0.1 already? <Overfiend> Oskuro: a few <Overfiend> only 152 megs | |
| I forgot to mention an important fact in the 1.3.67 announcement. In order to get a fully working kernel, you have to follow the steps below: - Walk around your computer widdershins 3 times, chanting "Linus is overworked, and he makes lousy patches, but we love him anyway". Get your spuouse to do this too for extra effect. Children are optional. - Apply the patch included in this mail - Call your system "Super-67", and don't forget to unapply the patch before you later applying the official 1.3.68 patch. - reboot -- Linus Torvalds, announcing another kernel patch | |
