Dictionary De - En
De - Es
De - Pt| Proverbs, aphorisms, quotations (English) | by Linux fortune |
| Anyone who considers protocol unimportant has never dealt with a cat. -- R. Heinlein | |
| /* * [...] Note that 120 sec is defined in the protocol as the maximum * possible RTT. I guess we'll have to use something other than TCP * to talk to the University of Mars. * PAWS allows us longer timeouts and large windows, so once implemented * ftp to mars will work nicely. */ (from /usr/src/linux/net/inet/tcp.c, concerning RTT [retransmission timeout]) | |
| Party-bug in the Aloha protocol. | |
| transient bus protocol violation | |
| If you ever want to have a lot of fun, I recommend that you go off and program an imbedded system. The salient characteristic of an imbedded system is that it cannot be allowed to get into a state from which only direct intervention will suffice to remove it. An imbedded system can't permanently trust anything it hears from the outside world. It must sniff around, adapt, consider, sniff around, and adapt again. I'm not talking about ordinary modular programming carefulness here. No. Programming an imbedded system calls for undiluted raging maniacal paranoia. For example, our ethernet front ends need to know what network number they are on so that they can address and route PUPs properly. How do you find out what your network number is? Easy, you ask a gateway. Gateways are required by definition to know their correct network numbers. Once you've got your network number, you start using it and before you can blink you've got it wired into fifteen different sockets spread all over creation. Now what happens when the panic-stricken operator realizes he was running the wrong version of the gateway which was giving out the wrong network number? Never supposed to happen. Tough. Supposing that your software discovers that the gateway is now giving out a different network number than before, what's it supposed to do about it? This is not discussed in the protocol document. Never supposed to happen. Tough. I think you get my drift. | |
| "We invented a new protocol and called it Kermit, after Kermit the Frog, star of "The Muppet Show." [3] [3] Why? Mostly because there was a Muppets calendar on the wall when we were trying to think of a name, and Kermit is a pleasant, unassuming sort of character. But since we weren't sure whether it was OK to name our protocol after this popular television and movie star, we pretended that KERMIT was an acronym; unfortunately, we could never find a good set of words to go with the letters, as readers of some of our early source code can attest. Later, while looking through a name book for his forthcoming baby, Bill Catchings noticed that "Kermit" was a Celtic word for "free", which is what all Kermit programs should be, and words to this effect replaced the strained acronyms in our source code (Bill's baby turned out to be a girl, so he had to name her Becky instead). When BYTE Magazine was preparing our 1984 Kermit article for publication, they suggested we contact Henson Associates Inc. for permission to say that we did indeed name the protocol after Kermit the Frog. Permission was kindly granted, and now the real story can be told. I resisted the temptation, however, to call the present work "Kermit the Book." -- Frank da Cruz, "Kermit - A File Transfer Protocol" | |
| A diplomat's life consists of three things: protocol, Geritol, and alcohol. -- Adlai Stevenson | |
| handshaking protocol, n: A process employed by hostile hardware devices to initate a terse but civil dialogue, which, in turn, is characterized by occasional misunderstanding, sulking, and name-calling. | |
| MAFIA, n: [Acronym for Mechanized Applications in Forced Insurance Accounting.] An extensive network with many on-line and offshore subsystems running under OS, DOS, and IOS. MAFIA documentation is rather scanty, and the MAFIA sales office exhibits that testy reluctance to bona fide inquiries which is the hallmark of so many DP operations. From the little that has seeped out, it would appear that MAFIA operates under a non-standard protocol, OMERTA, a tight-lipped variant of SNA, in which extended handshakes also perform complex security functions. The known timesharing aspects of MAFIA point to a more than usually autocratic operating system. Screen prompts carry an imperative, nonrefusable weighting (most menus offer simple YES/YES options, defaulting to YES) that precludes indifference or delay. Uniquely, all editing under MAFIA is performed centrally, using a powerful rubout feature capable of erasing files, filors, filees, and entire nodal aggravations. -- Stan Kelly-Bootle, "The Devil's DP Dictionary" | |
| If Dr. Seuss Were a Technical Writer..... Here's an easy game to play. Here's an easy thing to say: If a packet hits a pocket on a socket on a port, And the bus is interrupted as a very last resort, And the address of the memory makes your floppy disk abort, Then the socket packet pocket has an error to report! If your cursor finds a menu item followed by a dash, And the double-clicking icon puts your window in the trash, And your data is corrupted 'cause the index doesn't hash, then your situation's hopeless, and your system's gonna crash! You can't say this? What a shame, sir! We'll find you another game, sir. If the label on the cable on the table at your house, Says the network is connected to the button on your mouse, But your packets want to tunnel on another protocol, That's repeatedly rejected by the printer down the hall, And your screen is all distorted by the side effects of gauss, So your icons in the window are as wavy as a souse, Then you may as well reboot and go out with a bang, 'Cause as sure as I'm a poet, the sucker's gonna hang! When the copy of your floppy's getting sloppy on the disk, And the microcode instructions cause unnecessary risc, Then you have to flash your memory and you'll want to ram your rom. Quickly turn off the computer and be sure to tell your mom! -- DementDJ@ccip.perkin-elmer.com (DementDJ) [rec.humor.funny] | |
| 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," | |
| Severe Acronym Shortage Cripples Computer Industry SILICON VALLEY, CALIFORNIA (SVC) -- According to a recent study by the Blartner Group, 99.5% of all possible five letter combinations have already been appropriated for computer industry acronyms. The impending shortage of 5LC's is casting a dark shadow over the industry, which relies heavily on short, easy-to-remember acronyms for everything. "Acronym namespace collisions (ANCs) are increasing at a fantastic rate and threaten the very fabric of the computing world," explained one ZD pundit. "For example, when somebody talks about XP, I don't know whether they mean eXtreme Programming or Microsoft's eXceptionally Pathetic operating system. We need to find a solution now or chaos will result." Leaders of several SVC companies have floated the idea of an "industry-wide acronym conservation protocol" (IWACP -- one of the few 5LCs not already appropriated). Explained Bob Smith, CTO of IBM, "If companies would voluntarily limit the creation of new acronyms while recycling outdated names, we could reduce much of the pollution within the acronym namespace ourselves. The last thing we want is for Congress to get involved and try to impose a solution for this SAS (Severe Acronym Shortage) that would likely only create many new acronyms in the process." | |
| Alan Cox wrote: > RFC1122 also requires that your protocol stack SHOULD be able to leap tall > buldings at a single bound of course... And, of course my protocol stack does :) It is also a floor wax, AND a dessert topping!-) - Rick Jones trying to sell his protocol stack | |
| /* * [...] Note that 120 sec is defined in the protocol as the maximum * possible RTT. I guess we'll have to use something other than TCP * to talk to the University of Mars. * PAWS allows us longer timeouts and large windows, so once implemented * ftp to mars will work nicely. */ -- from /usr/src/linux/net/inet/tcp.c, concerning RTT [round trip time] | |
