Dictionary De - En
De - Es
De - Pt| Proverbs, aphorisms, quotations (English) | by Linux fortune |
| And 1.1.81 is officially BugFree(tm), so if you receive any bug-reports on it, you know they are just evil lies." (By Linus Torvalds, Linus.Torvalds@cs.helsinki.fi) | |
| "I'm an idiot.. At least this one [bug] took about 5 minutes to find.." (Linus Torvalds in response to a bug report.) > I'm an idiot.. At least this [bug] took about 5 minutes to find.. Disquieting ... (Gonzalo Tornaria in response to Linus Torvalds's mailing about a kernel bug.) > I'm an idiot.. At least this [bug] took about 5 minutes to find.. We need to find some new terms to describe the rest of us mere mortals then. (Craig Schlenter in response to Linus Torvalds's mailing about a kernel bug.) > I'm an idiot.. At least this [bug] took about 5 minutes to find.. Surely, Linus is talking about the kind of idiocy that others aspire to :-). (Bruce Perens in response to Linus Torvalds's mailing about a kernel bug.) | |
| "Never make any mistaeks." (Anonymous, in a mail discussion about to a kernel bug report.) | |
| Pentium FDIV bug | |
| The vendor put the bug there. | |
| Party-bug in the Aloha protocol. | |
| Operators killed by year 2000 bug bite. | |
| A Tale of Two Cities LITE(tm) -- by Charles Dickens A lawyer who looks like a French Nobleman is executed in his place. The Metamorphosis LITE(tm) -- by Franz Kafka A man turns into a bug and his family gets annoyed. Lord of the Rings LITE(tm) -- by J.R.R. Tolkien Some guys take a long vacation to throw a ring into a volcano. Hamlet LITE(tm) -- by Wm. Shakespeare A college student on vacation with family problems, a screwy girl-friend and a mother who won't act her age. | |
| Consider well the proportions of things. It is better to be a young June-bug than an old bird of paradise. -- Mark Twain, "Pudd'nhead Wilson's Calendar" | |
| The difference between the right word and the almost right word is the difference between lightning and the lightning bug. -- Mark Twain | |
| A bug in the code is worth two in the documentation. | |
| A bug in the hand is better than one as yet undetected. | |
| All programmers are optimists. Perhaps this modern sorcery especially attracts those who believe in happy endings and fairy godmothers. Perhaps the hundreds of nitty frustrations drive away all but those who habitually focus on the end goal. Perhaps it is merely that computers are young, programmers are younger, and the young are always optimists. But however the selection process works, the result is indisputable: "This time it will surely run," or "I just found the last bug." -- Frederick Brooks, "The Mythical Man Month" | |
| === ALL USERS PLEASE NOTE ======================== Bug reports now amount to an average of 12,853 per day. Unfortunately, this is only a small fraction [ < 1% ] of the mail volume we receive. In order that we may more expeditiously deal with these valuable messages, please communicate them by one of the following paths: ARPA: WastebasketSLMHQ.ARPA UUCP: [berkeley, seismo, harpo]!fubar!thekid!slmhq!wastebasket Non-network sites: Federal Express to: Wastebasket Room NE43-926 Copernicus, The Moon, 12345-6789 For that personal contact feeling call 1-415-642-4948; our trained operators are on call 24 hours a day. VISA/MC accepted.* * Our very rich lawyers have assured us that we are not responsible for any errors or advice given over the phone. | |
| Any sufficiently advanced bug is indistinguishable from a feature. -- Rich Kulawiec | |
| Ever wondered about the origins of the term "bugs" as applied to computer technology? U.S. Navy Capt. Grace Murray Hopper has firsthand explanation. The 74-year-old captain, who is still on active duty, was a pioneer in computer technology during World War II. At the C.W. Post Center of Long Island University, Hopper told a group of Long Island public school adminis- trators that the first computer "bug" was a real bug--a moth. At Harvard one August night in 1945, Hopper and her associates were working on the "granddaddy" of modern computers, the Mark I. "Things were going badly; there was something wrong in one of the circuits of the long glass-enclosed computer," she said. "Finally, someone located the trouble spot and, using ordinary tweezers, removed the problem, a two-inch moth. From then on, when anything went wrong with a computer, we said it had bugs in it." Hopper said that when the veracity of her story was questioned recently, "I referred them to my 1945 log book, now in the collection of the Naval Surface Weapons Center, and they found the remains of that moth taped to the page in question." [actually, the term "bug" had even earlier usage in regard to problems with radio hardware. Ed.] | |
| Every program has at least one bug and can be shortened by at least one instruction -- from which, by induction, one can deduce that every program can be reduced to one instruction which doesn't work. | |
| Heuristics are bug ridden by definition. If they didn't have bugs, then they'd be algorithms. | |
| If it happens once, it's a bug. If it happens twice, it's a feature. If it happens more than twice, it's a design philosophy. | |
| In every non-trivial program there is at least one bug. | |
| ... Jesus cried with a loud voice: Lazarus, come forth; the bug hath been found and thy program runneth. And he that was dead came forth... -- John 11:43-44 [version 2.0?] | |
| Proposed Additions to the PDP-11 Instruction Set: BBW Branch Both Ways BEW Branch Either Way BBBF Branch on Bit Bucket Full BH Branch and Hang BMR Branch Multiple Registers BOB Branch On Bug BPO Branch on Power Off BST Backspace and Stretch Tape CDS Condense and Destroy System CLBR Clobber Register CLBRI Clobber Register Immediately CM Circulate Memory CMFRM Come From -- essential for truly structured programming CPPR Crumple Printer Paper and Rip CRN Convert to Roman Numerals | |
| Proposed Additions to the PDP-11 Instruction Set: DC Divide and Conquer DMPK Destroy Memory Protect Key DO Divide and Overflow EMPC Emulate Pocket Calculator EPI Execute Programmer Immediately EROS Erase Read Only Storage EXCE Execute Customer Engineer HCF Halt and Catch Fire IBP Insert Bug and Proceed INSQSW Insert into queue somewhere (for FINO queues [First in never out]) PBC Print and Break Chain PDSK Punch Disk | |
| System going down at 5 this afternoon to install scheduler bug. | |
| The bug stops here. | |
| The bug starts here. | |
| "The net result is a system that is not only binary compatible with 4.3 BSD, but is even bug for bug compatible in almost all features." -- Avadit Tevanian, Jr., "Architecture-Independent Virtual Memory Management for Parallel and Distributed Environments: The Mach Approach" | |
| Bug, n.: An aspect of a computer program which exists because the programmer was thinking about Jumbo Jacks or stock options when s/he wrote the program. Fortunately, the second-to-last bug has just been fixed. -- Ray Simard | |
| bug, n: A son of a glitch. | |
| bug, n: An elusive creature living in a program that makes it incorrect. The activity of "debugging", or removing bugs from a program, ends when people get tired of doing it, not when the bugs are removed. -- "Datamation", January 15, 1984 | |
| Drew's Law of Highway Biology: The first bug to hit a clean windshield lands directly in front of your eyes. | |
| feature, n: A surprising property of a program. Occasionaly documented. To call a property a feature sometimes means the author did not consider that case, and the program makes an unexpected, though not necessarily wrong response. See BUG. "That's not a bug, it's a feature!" A bug can be changed to a feature by documenting it. | |
| Lubarsky's Law of Cybernetic Entomology: There's always one more bug. | |
| Police: Good evening, are you the host? Host: No. Police: We've been getting complaints about this party. Host: About the drugs? Police: No. Host: About the guns, then? Is somebody complaining about the guns? Police: No, the noise. Host: Oh, the noise. Well that makes sense because there are no guns or drugs here. (An enormous explosion is heard in the background.) Or fireworks. Who's complaining about the noise? The neighbors? Police: No, the neighbors fled inland hours ago. Most of the recent complaints have come from Pittsburgh. Do you think you could ask the host to quiet things down? Host: No Problem. (At this point, a Volkswagon bug with primitive religious symbols drawn on the doors emerges from the living room and roars down the hall, past the police and onto the lawn, where it smashes into a tree. Eight guests tumble out onto the grass, moaning.) See? Things are starting to wind down. | |
| Q: How many elephants can you fit in a VW Bug? A: Four. Two in the front, two in the back. Q: How can you tell if an elephant is in your refrigerator? A: There's a footprint in the mayo. Q: How can you tell if two elephants are in your refrigerator? A: There's two footprints in the mayo. Q: How can you tell if three elephants are in your refrigerator? A: The door won't shut. Q: How can you tell if four elephants are in your refrigerator? A: There's a VW Bug in your driveway. | |
| It's grad exam time... COMPUTER SCIENCE Inside your desk you'll find a listing of the DEC/VMS operating system in IBM 1710 machine code. Show what changes are necessary to convert this code into a UNIX Berkeley 7 operating system. Prove that these fixes are bug free and run correctly. You should gain at least 150% efficiency in the new system. (You should take no more than 10 minutes on this question.) MATHEMATICS If X equals PI times R^2, construct a formula showing how long it would take a fire ant to drill a hole through a dill pickle, if the length-girth ratio of the ant to the pickle were 98.17:1. GENERAL KNOWLEDGE Describe the Universe. Give three examples. | |
| The Commandments of the EE: (9) Trifle thee not with radioactive tubes and substances lest thou commence to glow in the dark like a lightning bug, and thy wife be frustrated and have not further use for thee except for thy wages. (10) Commit thou to memory all the words of the prophets which are written down in thy Bible which is the National Electrical Code, and giveth out with the straight dope and consoleth thee when thou hast suffered a ream job by the chief electrician. (11) When thou muckest about with a device in an unthinking and/or unknowing manner, thou shalt keep one hand in thy pocket. Better that thou shouldest keep both hands in thy pockets than experimentally determine the electrical potential of an innocent-seeming device. | |
| 99 blocks of crud on the disk, 99 blocks of crud! You patch a bug, and dump it again: 100 blocks of crud on the disk! 100 blocks of crud on the disk, 100 blocks of crud! You patch a bug, and dump it again: 101 blocks of crud on the disk! ... | |
| As I was passing Project MAC, I met a Quux with seven hacks. Every hack had seven bugs; Every bug had seven manifestations; Every manifestation had seven symptoms. Symptoms, manifestations, bugs, and hacks, How many losses at Project MAC? | |
| Buzz off, Banana Nose; Relieve mine eyes Of hateful soreness, purge mine ears of corn; Less dear than army ants in apple pies Art thou, old prune-face, with thy chestnuts worn, Dropt from thy peeling lips like lousy fruit; Like honeybees upon the perfum'd rose They suck, and like the double-breasted suit Are out of date; therefore, Banana Nose, Go fly a kite, thy welcome's overstayed; And stem the produce of thy waspish wits: Thy logick, like thy locks, is disarrayed; Thy cheer, like thy complexion, is the pits. Be off, I say; go bug somebody new, Scram, beat it, get thee hence, and nuts to you. | |
| God rest ye CS students now, The bearings on the drum are gone, Let nothing you dismay. The disk is wobbling, too. The VAX is down and won't be up, We've found a bug in Lisp, and Algol Until the first of May. Can't tell false from true. The program that was due this morn, And now we find that we can't get Won't be postponed, they say. At Berkeley's 4.2. (chorus) (chorus) We've just received a call from DEC, And now some cheery news for you, They'll send without delay The network's also dead, A monitor called RSuX We'll have to print your files on It takes nine hundred K. The line printer instead. The staff committed suicide, The turnaround time's nineteen weeks. We'll bury them today. And only cards are read. (chorus) (chorus) And now we'd like to say to you CHORUS: Oh, tidings of comfort and joy, Before we go away, Comfort and joy, We hope the news we've brought to you Oh, tidings of comfort and joy. Won't ruin your whole day. You've got another program due, tomorrow, by the way. (chorus) -- to God Rest Ye Merry Gentlemen | |
| "No program is perfect," They said with a shrug. "The customer's happy-- What's one little bug?" But he was determined, Then change two, then three more, The others went home. As year followed year. He dug out the flow chart And strangers would comment, Deserted, alone. "Is that guy still here?" Night passed into morning. He died at the console The room was cluttered Of hunger and thirst With core dumps, source listings. Next day he was buried "I'm close," he muttered. Face down, nine edge first. Chain smoking, cold coffee, And his wife through her tears Logic, deduction. Accepted his fate. "I've got it!" he cried, Said "He's not really gone, "Just change one instruction." He's just working late." -- The Perfect Programmer | |
| Once there was a little nerd who loved to read your mail, And then yank back the i-access times to get hackers off his tail, And once as he finished reading from the secretary's spool, He wrote a rude rejection to her boyfriend (how uncool!) And this as delivermail did work and he ran his backfstat, He heard an awful crackling like rat fritters in hot fat, And hard errors brought the system down 'fore he could even shout! And the bio bug'll bring yours down too, ef you don't watch out! And once they was a little flake who'd prowl through the uulog, And when he went to his blit that night to play at being god, The ops all heard him holler, and they to the console dashed, But when they did a ps -ut they found the system crashed! Oh, the wizards adb'd the dumps and did the system trace, And worked on the file system 'til the disk head was hot paste, But all they ever found was this: "panic: never doubt", And the bio bug'll crash your box too, ef you don't watch out! When the day is done and the moon comes out, And you hear the printer whining and the rk's seems to count, When the other desks are empty and their terminals glassy grey, And the load is only 1.6 and you wonder if it'll stay, You must mind the file protections and not snoop around, Or the bio bug'll getcha and bring the system down! | |
| To code the impossible code, This is my quest -- To bring up a virgin machine, To debug that code, To pop out of endless recursion, No matter how hopeless, To grok what appears on the screen, No matter the load, To write those routines To right the unrightable bug, Without question or pause, To endlessly twiddle and thrash, To be willing to hack FORTRAN IV To mount the unmountable magtape, For a heavenly cause. To stop the unstoppable crash! And I know if I'll only be true To this glorious quest, And the queue will be better for this, That my code will run CUSPy and calm, That one man, scorned and When it's put to the test. destined to lose, Still strove with his last allocation To scrap the unscrappable kludge! -- To "The Impossible Dream", from Man of La Mancha | |
| Twas FORTRAN as the doloop goes Did logzerneg the ifthen block All kludgy were the function flows And subroutines adhoc. Beware the runtime-bug my friend squrooneg, the false goto Beware the infiniteloop And shun the inprectoo. -- "OUTCONERR," to the scheme of "Jabberwocky" | |
| What segment's this, that, laid to rest On FHA0, is sleeping? What system file, lay here a while This, this is "acct.run," While hackers around it were weeping? Accounting file for everyone. Dump, dump it and type it out, The file, the highseg of login. Why lies it here, on public disk And why is it now unprotected? A bug in incant, made it thus. Mount, mount all your DECtapes now And copy the file somehow, somehow. The problem has not been corrected. Dump, dump it and type it out, The file, the highseg of login. -- to Greensleeves | |
| Dave Finton gazes into his crystal ball... May 2049: Transmeta Updates Webpage In a bold move that shocked observers everywhere, Transmeta Corp., a secretive Silicon Valley company, updated their webpage. According to our sources, Transmeta fixed a bug in their existing web page located in the comment "This page contains no tyops". The message has been fixed to read "This page contains no typso". | |
| Brief History Of Linux (#17) Terrible calamity IBM chose Microsoft's Quick & Dirty Operating System instead of CP/M for its new line of PCs. QDOS (along with the abomination known as EDLIN) had been acquired from a Seattle man, Tim Paterson, for the paltry sum of $50,000. "Quick" and "Dirty" were truly an accurate description of this system, because IBM's quality assurance department discovered 300 bugs in QDOS's 8,000 lines of assember code (that's about 1 bug per 27 lines -- which, at the time, was appalling, but compared with Windows 98 today, it really wasn't that shabby). Thanks in part to IBM's new marketing slogan, "Nobody Ever Got Fired For Choosing IBM(tm)", and the release of the VisiCalc spreadsheet program that everybody and their brother wanted, IBM PCs running DOS flew off the shelves and, unfortunately, secured Microsoft's runaway success. Bill Gates was now on his way to the Billionaire's Club; his days as a mediocre programmer were long gone: he was now a Suit. The only lines of code he would ever see would be the passcodes to his Swiss bank accounts. | |
| Brief History Of Linux (#28) Free, Open, Libre, Whatever Software Eric S. Raymond's now famous paper, "The Cathedral and the Bazaar", set the stage for the lucrative business of giving software away. In CatB, ESR likened the software industry to an anarchistic bazaar, with each vendor looking out for himself, trying to hoodwink customers and fellow vendors. The produce vendor (i.e. Apple), for instance, felt no need to cooperate with the crystal-ball seller (Oracle) or the con artist hocking miracle drugs (Microsoft). Each kept their property and trade secrets to themselves, hoping to gain an edge and make money fast. "With enough eyeballs, all bug-ridden software programs are marketable," ESR observed. ESR contrasted the "caveat emptor" Bazaar to an idealistic Cathedral model used by free software developers. European cathedrals of medieval days were built block-by-block with extensive volunteer manpower from the surrounding community. Such projects were "open" in the sense that everybody could see their progress, and interested people could wander inside and offer comments or praise about construction methods. "Those medieval cathedrals are still standing," ESR mused. "But bazaars built in the 14th Century are long gone, a victim of their inferior nature." | |
| "I want you guys to look at your computer screen, imagining the worst monster you can (the cacodeamon from Quake will do, just make him hairier and bigger and more MEAN), and think of me. Think of me like I am when I see a patch which isn't a pure bug-fix. If you're whimpering just _thinking_ about sending me a new feature, you're in the right mindframe. Keep that mindframe." - Linus Torvalds | |
| "Yeah. Maybe we fixed truncate, and maybe we didn't. I've thought that we fixed it now several times, and I was always wrong. Time for some reverse psychology: I'm sure this one doesn't fix the truncate bug either. - Linus Torvalds | |
| "It's just that I was born with a highly developed case of Altzheimers, and I have trouble keeping details around in my head for more than about five minutes." - Linus Torvalds on bug tracking | |
| I can see the intent. I can also see that the code doesn't match up to the intent. I call that a bug. You don't. Fine. - Linus Torvalds rejecting a patch on linux-kernel | |
| Nvidia driver loaded - bugs to nvidia. vmware loaded bugs to vmware, both loaded, god help you, nobody else will - Alan Cox explaining where to send bug reports for binary-only drivers | |
| If you _really_ feel this strongly about the bug, you could either try to increase the number of hours a day for all of us or you could talk to my boss about hiring me as a consultant to fix the problem for you on an emergency basis :) - Rik van Riel explaining what to do against kernel bugs | |
| Drivers are a more complex issue. I'm not opposed to binary only drivers, providing its easy to tell they are there and dump all bug reports about them. Freedom generally includes the right to give up freedom. I'll tell people its a bad idea but once they get caught, well it was their right to do so... - Alan Cox on linux-kernel | |
| There seems to be a bug in the mail routing again. It may be related to the recent problem with ditto copier history outbreaks on Linux S/390 and the infamous 'pdp-11 memory subsystem' article routing bug that plagued comp.os.minix once. In the meantime can people check that their mailer hasnt spontaneously added linux-kernel to their history articles before posting them ? - Alan Cox about off topic cross posting on lkml | |
| > If you took my patch for it, PLEASE don't send it for inclusion; it's an > evil hack and no longer needed when Intel fixes the bug in their 440GX bios. "when" is not a word I find useful about most bios bugs. Try "if" or "less likely that being hit on the head by an asteroid" - Alan Cox on linux-kernel | |
| And there was much suffering among the people, for g++ was a necessity. And one rose up from the mass and cried, "Lord Root, if thou canst not help us, then call upon the gods of far gcc@gcc.gnu.org for among them are sages of wisdom who may be of help!" - bug report from Sean Callanan send to the GCC mailing list | |
| <james> abuse me. I'm so lame I sent a bug report to debian-devel-changes | |
| <Overfiend> partycle: I seriously do need a vacation from this package. I actually had a DREAM about introducing a stupid new bug into xbase-preinst last night. That's a Bad Sign. | |
| acme-cannon (3.1415) unstable; urgency=low * Added safety to prevent operator dismemberment, closes: bug #98765, bug #98713, #98714. * Added manpage. closes: #98725. -- Wile E. Coyote <genius@debian.org> Sun, 31 Jan 1999 07:49:57 -0600 | |
| * knghtbrd can already envision: "Subject: [INTENT TO PREPARE TO PROPOSE FILING OF BUG REPORT] Typos in the policy document" | |
| <aph> manoj is going nuts on the bug fixing crusade! woo woo! <Knghtbrd> manoj went nuts long time ago. but the bug fixing is cool => | |
| I stopped a long time ago to try to find anything in the bug list of dpkg. We should run for an entry in the Guinness Book of Records. -- Stephane Bortzmeyer | |
| Subject: Bug#42432: debian-policy: Proposal for CTV for Draft for Proof of Concept for Draft for Proposal for Proposal for CTV for a CTV to decide on a proposal for a CTV for the CTV on whether or not we shoud have a CTV on the /usr/doc to /usr/share/doc transition now, or later. -- Ed Lang | |
| Red Hat has recently released a Security Advisory (RHSA-1999:030-01) covering a buffer overflow in the vixie cron package. Debian has discovered this bug two years ago and fixed it. Therefore versions in both, the stable and the unstable, distributions of Debian are not vulnerable to this problem.. | |
| <Joy> wow... simple maths show that Debian developers have closed more than *31* *thousand* bug reports since our BTS exists! <Joy> that is about 30999 more than Microsoft ;) | |
| <jt> should a bug be marked critical if it only affects one arch? <james-workaway> jt: rc for that arch maybe, but those kind of arch specific bugs are rare... <jt> not when it's caused by a bug in gcc <doogie> jt: get gcc removed from that arch. :) | |
| 99 little bugs in the code, 99 bugs in the code, fix one bug, compile it again... 101 little bugs in the code.... | |
| <Dabb> hehe, I really hate bug reports which are like calling fire department and saying: "There is fire here, come!" :) <Dabb> (and hanging up) * Dabb kills off dozen bug reports. | |
| <doogie> Culus: my bug with openssh appears to be fixed in 2.5.2, but master runs 2.3.0 <Culus> Don't even start <doogie> I just did. <Culus> You guys are going to drive me to build a huge giant robot and destroy all of texas, aren't you? | |
| And 1.1.81 is officially BugFree(tm), so if you receive any bug-reports on it, you know they are just evil lies. -- Linus Torvalds | |
| > I'm an idiot.. At least this [bug] took about 5 minutes to find.. Disquieting ... -- Gonzalo Tornaria in response to Linus Torvalds's | |
| > I'm an idiot.. At least this [bug] took about 5 minutes to find.. We need to find some new terms to describe the rest of us mere mortals then. -- Craig Schlenter in response to Linus Torvalds's | |
| > I'm an idiot.. At least this [bug] took about 5 minutes to find.. Surely, Linus is talking about the kind of idiocy that others aspire to :-). -- Bruce Perens in response to Linus Torvalds's | |
| Never make any mistaeks. -- Anonymous, in a mail discussion about to a kernel bug report | |
| A feature is nothing more than a bug with seniority. -- Unknown source | |
| <james> abuse me. I'm so lame I sent a bug report to debian-devel-changes -- Seen on #Debian | |
| You will not censor me through bug terrorism. -- James Troup | |
| <Overfiend> partycle: I seriously do need a vacation from this package. I actually had a DREAM about introducing a stupid new bug into xbase-preinst last night. That's a Bad Sign. -- Seen on #Debian shortly before the release of Debian 2.0 | |
| Alex Buell: Or how about a Penguin logo painted in really really trippy colours, and emblazoned with the word LSD. :o) Geert Uytterhoeven: We already had that one, but unfortunately Russell King fixed that nasty palette bug in drivers/video/fbcon.c :-) -- linux-kernel | |
| No, that's wrong too. Now there's a race condition between the rm and the mv. Hmm, I need more coffee. -- Guy Maor on Debian Bug#25228 | |
| "I find this a nice feature but it is not according to the documentation. Or is it a BUG?" "Let's call it an accidental feature. :-)" -- Larry Wall in <6909@jpl-devvax.JPL.NASA.GOV> | |
| There are still some other things to do, so don't think if I didn't fix your favorite bug that your bug report is in the bit bucket. (It may be, but don't think it. :-) Larry Wall in <7238@jpl-devvax.JPL.NASA.GOV> | |
| If you remove stricture from a large Perl program currently, you're just installing delayed bugs, whereas with this feature, you're installing an instant bug that's easily fixed. Whoopee. -- Larry Wall in <199710050130.SAA04762@wall.org> | |
