The Hacker's Dictionary by - (romantic novels to read TXT) 📖

527 ("ARPAWOCKY", R. Merryman, UCSD; 22

June 1973), 748 ("Telnet Randomly-Lose Option", Mark R. Crispin; 1 April 1978), and 1149 ("A Standard for the Transmission of IP

Datagrams on Avian Carriers", D. Waitzman, BBN STC; 1 April 1990).

The first was a Lewis Carrol pastiche; the second a parody of the TCP-IP documentation style, and the third a deadpan skewering of standards-document legalese describing protocols for transmiitting Internet data packets by carrier pigeon.

The RFCs are most remarkable for how well they work --- they manage to have neither the ambiguities which are usually rife in informal specifications, nor the committee-perpetrated misfeatures which often haunt formal standards, and they define a network which has grown to truly worldwide proportions.

:RFE: /R-F-E/ n. 1. [techspeak] Request For Enhancement.

[from `Radio Free Europe', Bellcore and Sun] Radio Free Ethernet, a system (originated by Peter Langston) for broadcasting audio among Sun SPARCstations over the ethernet.

:rib site: [by analogy with {backbone site}] n. A machine that has an on-demand high-speed link to a {backbone site} and serves as a regional distribution point for lots of third-party traffic in email and USENET news. Compare {leaf site}, {backbone site}.

:rice box: [from ham radio slang] n. Any Asian-made commodity computer, esp. an 80x86-based machine built to IBM PC-compatible ISA or EISA-bus standards.

:Right Thing: n. That which is compellingly the correct or appropriate thing to use, do, say, etc. Often capitalized, always emphasized in speech as though capitalized. Use of this term often implies that in fact reasonable people may disagree. "What's the right thing for LISP to do when it sees (mod a 0)'? Should it returna', or give a divide-by-0 error?" Oppose {Wrong Thing}.

:RL: // [MUD community] n. Real Life. "Firiss laughs in RL"

means that Firiss's player is laughing. Oppose {VR}.

:roach: [Bell Labs] vt. To destroy, esp. of a data structure. Hardware gets {toast}ed or {fried}, software gets roached.

:robot: [IRC, MUD] n. An {IRC} or {MUD} user who is actually a program. On IRC, typically the robot provides some useful service. Examples are NickServ, which tries to prevent random users from adopting {nick}s already claimed by others, and MsgServ, which allows one to send asynchronous messages to be delivered when the recipient signs on. Also common are "annoybots", such as KissServ, which perform no useful function except to send cute messages to other people. Service robots are less common on MUDs; but some others, such as the `Julia' robot active in 1990-91, have been remarkably impressive Turing-test experiments, able to pass as human for as long as ten or fifteen minutes of conversation.

:robust: adj. Said of a system that has demonstrated an ability to recover gracefully from the whole range of exceptional inputs and situations in a given environment. One step below {bulletproof}.

Carries the additional connotation of elegance in addition to just careful attention to detail. Compare {smart}, oppose {brittle}.

:rococo: adj. {Baroque} in the extreme. Used to imply that a program has become so encrusted with the software equivalent of gold leaf and curlicues that they have completely swamped the underlying design. Called after the later and more extreme forms of Baroque architecture and decoration prevalent during the mid-1700s in Europe. Alan Perlis said: "Every program eventually becomes rococo, and then rubble." Compare {critical mass}.

:rogue: [UNIX] n. A Dungeons-and-Dragons-like game using character graphics, written under BSD UNIX and subsequently ported to other UNIX systems. The original BSD curses(3)' screen-handling package was hacked together by Ken Arnold to supportrogue(6)' and has since become one of UNIX's most important and heavily used application libraries. Nethack, Omega, Larn, and an entire subgenre of computer dungeon games all took off from the inspiration provided by `rogue(6)'. See {nethack}.

:room-temperature IQ: [IBM] quant. 80 or below. Used in describing the expected intelligence range of the {luser}. "Well, but how's this interface going to play with the room-temperature IQ

crowd?" See {drool-proof paper}. This is a much more insulting phrase in countries that use Celsius thermometers.

:root: [UNIX] n. 1. The {superuser} account that ignores permission bits, user number 0 on a UNIX system. This account has the user name `root'. The term {avatar} is also used.

The top node of the system directory structure (home directory of the root user). 3. By extension, the privileged system-maintenance login on any OS. See {root mode}, {go root}.

:root mode: n. Syn. with {wizard mode} or `wheel mode'. Like these, it is often generalized to describe privileged states in systems other than OSes.

:rot13: /rot ther'teen/ [USENET: from `rotate alphabet 13 places'] n., v. The simple Caesar-cypher encryption that replaces each English letter with the one 13 places forward or back along the alphabet, so that "The butler did it!" becomes "Gur ohgyre qvq vg!" Most USENET news reading and posting programs include a rot13 feature. It is used to enclose the text in a sealed wrapper that the reader must choose to open --- e.g., for posting things that might offend some readers, or answers to puzzles. A major advantage of rot13 over rot(N) for other N is that it is self-inverse, so the same code can be used for encoding and decoding.

:rotary debugger: [Commodore] n. Essential equipment for those late-night or early-morning debugging sessions. Mainly used as sustenance for the hacker. Comes in many decorator colors, such as Sausage, Pepperoni, and Garbage. See {pizza, ANSI standard}.

:round tape: n. Industry-standard 1/2" magnetic tape (7- or 9-track) on traditional circular reels; oppose {square tape}.

:RSN: /R-S-N/ adj. See {Real Soon Now}.

:RTBM: /R-T-B-M/ [UNIX] imp. Commonwealth Hackish variant of {RTFM}; expands to `Read The Bloody Manual'. RTBM is often the entire text of the first reply to a question from a {newbie}; the second would escalate to "RTFM".

:RTFAQ: /R-T-F-A-Q/ [USENET: primarily written, by analogy with {RTFM}] imp. Abbrev. for `Read the FAQ!', an exhortation that the person addressed ought to read the newsgroup's {FAQ list}

before posting questions.

:RTFB: /R-T-F-B/ [UNIX] imp. Acronym for `Read The Fucking Binary'. Used when neither documentation nor the the source for the problem at hand exists and the only thing to do is use some debugger or monitor and directly analyze the assembler or even the machine code. "No source for the buggy port driver? Aaargh! I hate proprietary operating systems. Time to RTFB."

:RTFM: /R-T-F-M/ [UNIX] imp. Acronym for `Read The Fucking Manual'. 1. Used by {guru}s to brush off questions they consider trivial or annoying. Compare {Don't do that, then!}

Used when reporting a problem to indicate that you aren't just asking out of {randomness}. "No, I can't figure out how to interface UNIX to my toaster, and yes, I have RTFM." Unlike sense 1, this use is considered polite. See also {FM}, {RTFAQ}, {RTFB}, {RTFS}, {RTM}, all of which mutated from RTFM, and compare {UTSL}.

:RTFS: /R-T-F-S/ [UNIX] 1. imp. Acronym for `Read The Fucking Source'. Stronger form of {RTFM}, used when the problem at hand is not necessarily obvious and not available from the manuals --- or the manuals are not yet written and maybe never will be. For even more tricky situations, see {RTFB}.

imp. `Read The Fucking Standard;' this oath can only be used when the problem area (e.g. a language or operating system interface) has actually been codified in a ratified standards document. The existence of these standards documents (and the technically inappropriate but politically mandated compromises which they inevitably contain, and the stifling language in which they are invariably written, and the unbelievably tedious bureaucratic process by which they are produced) can be unnerving to hackers, who are used to a certain amount of ambiguity in the specifications of the systems they use. (Hackers feel that such ambiguities are acceptable as long as the {Right Thing} to do is obvious to any thinking observer; sadly, this casual attitude towards specifications becomes unworkable when a system becomes popular in the {real world}.) Since a hacker is likely to feel that a standards document is both unnecessary and technically deficient, the deprecation inherent in this term may be directed as much against the standard as against the person who ought to read it.

:RTI: /R-T-I/ interj. The mnemonic for the return from interrupt' instruction on many computers including the 6502 and 6800. The variantRETI' is found among former Z80 hackers (almost nobody programs these things in assembler anymore).

Equivalent to "Now, where was I?" or used to end a conversational digression. See {pop}; see also {POPJ}.

:RTM: /R-T-M/ [USENET: abbreviation for `Read The Manual']

Politer variant of {RTFM}. 2. Robert T. Morris Jr., perpetrator of the great Internet worm of 1988 (see {Great Worm, the}); villain to many, na"ive hacker gone wrong to a few. Morris claimed that the worm that brought the Internet to its knees was a benign experiment that got out of control as the result of a coding error. After the storm of negative publicity that followed this blunder, Morris's name on ITS was hacked from RTM to {RTFM}.

:rude: [WPI] adj. 1. (of a program) Badly written. 2. Functionally poor, e.g., a program that is very difficult to use because of gratuitously poor (random?) design decisions. Oppose {cuspy}.

Anything that manipulates a shared resource without regard for its other users in such a way as to cause a (non-fatal) problem is said to be `rude'. Examples: programs that change