The Jargon File, Version 4.0.0, 24 Jul 1996 Papyras Classics

← The Jargon File, Version 4.0.0, 24 Jul 1996

Chapter 2

Attention (part 1)

This room is fullfilled mit special electronische equippment. Fingergrabbing and pressing the cnoeppkes from the computers is allowed for die experts only! So all the "lefthanders" stay away and do not disturben the brainstorming von here working intelligencies. Otherwise you will be out thrown and kicked anderswhere! Also: please keep still and only watchen astaunished the blinkenlights.

See also {geef}.

Old-time hackers sometimes get nostalgic for blinkenlights because they were so much more fun to look at than a blank panel. Sadly, very few computers still have them (the three LEDs on a PC keyboard certainly don't count). The obvious reasons (cost of wiring, cost of front-panel cutouts, almost nobody needs or wants to interpret machine-register states on the fly anymore) are only part of the story. Another part of it is that radio-frequency leakage from the lamp wiring was beginning to be a problem as far back as transistor machines. But the most fundamental fact is that there are very few signals slow enough to blink an LED these days! With slow CPUs, you could watch the bus register or instruction counter tick, but at 33/66/150MHz it's all a blur.

:blit: /blit/ /vt./ 1. To copy a large array of bits from one part of a computer's memory to another part, particularly when the memory is being used to determine what is shown on a display screen. "The storage allocator picks through the table and copies the good parts up into high memory, and then blits it all back down again." See {bitblt}, {BLT}, {dd}, {cat}, {blast}, {snarf}. More generally, to perform some operation (such as toggling) on a large array of bits while moving them. 2. Sometimes all-capitalized as `BLIT': an early experimental bit-mapped terminal designed by Rob Pike at Bell Labs, later commercialized as the AT&T 5620. (The folk etymology from `Bell Labs Intelligent Terminal' is incorrect. Its creators liked to claim that "Blit" stood for the Bacon, Lettuce, and Interactive Tomato.)

:blitter: /blit'r/ /n./ A special-purpose chip or hardware system built to perform {blit} operations, esp. used for fast implementation of bit-mapped graphics. The Commodore Amiga and a few other micros have these, but sine 1990 the trend is away from them (however, see {cycle of reincarnation}). Syn. {raster blaster}.

:blivet: /bliv'*t/ /n./ [allegedly from a World War II military term meaning "ten pounds of manure in a five-pound bag"] 1. An intractable problem. 2. A crucial piece of hardware that can't be fixed or replaced if it breaks. 3. A tool that has been hacked over by so many incompetent programmers that it has become an unmaintainable tissue of hacks. 4. An out-of-control but unkillable development effort. 5. An embarrassing bug that pops up during a customer demo. 6. In the subjargon of computer security specialists, a denial-of-service attack performed by hogging limited resources that have no access controls (for example, shared spool space on a multi-user system).

This term has other meanings in other technical cultures; among experimental physicists and hardware engineers of various kinds it seems to mean any random object of unknown purpose (similar to hackish use of {frob}). It has also been used to describe an amusing trick-the-eye drawing resembling a three-pronged fork that appears to depict a three-dimensional object until one realizes that the parts fit together in an impossible way.

:BLOB: 1. /n./ [acronym: Binary Large OBject] Used by database people to refer to any random large block of bits that needs to be stored in a database, such as a picture or sound file. The essential point about a BLOB is that it's an object that cannot be interpreted within the database itself. 2. /v./ To {mailbomb} someone by sending a BLOB to him/her; esp. used as a mild threat. "If that program crashes again, I'm going to BLOB the core dump to you."

:block: /v./ [from process scheduling terminology in OS theory] 1. /vi./ To delay or sit idle while waiting for something. "We're blocking until everyone gets here." Compare {busy-wait}. 2. `block on' /vt./ To block, waiting for (something). "Lunch is blocked on Phil's arrival."

:block transfer computations: /n./ [from the television series "Dr. Who"] Computations so fiendishly subtle and complex that they could not be performed by machines. Used to refer to any task that should be expressible as an algorithm in theory, but isn't. (The Z80's LDIR instruction, "Computed Block Transfer with increment", may also be relevant)

:Bloggs Family, the: /n./ An imaginary family consisting of
Fred and Mary Bloggs and their children. Used as a standard
example in knowledge representation to show the difference between
extensional and intensional objects. For example, every occurrence
of "Fred Bloggs" is the same unique person, whereas occurrences
of "person" may refer to different people. Members of the Bloggs
family have been known to pop up in bizarre places such as the DEC
Telephone Directory. Compare {Mbogo, Dr. Fred}.

:blow an EPROM: /bloh *n ee'prom/ /v./ (alt. `blast an
EPROM', `burn an EPROM') To program a read-only memory, e.g.
for use with an embedded system. This term arose because the
programming process for the Programmable Read-Only Memories (PROMs)
that preceded present-day Erasable Programmable Read-Only Memories
(EPROMs) involved intentionally blowing tiny electrical fuses on
the chip. The usage lives on (it's too vivid and expressive to
discard) even though the write process on EPROMs is nondestructive.

:blow away: /vt./ To remove (files and directories) from permanent storage, generally by accident. "He reformatted the wrong partition and blew away last night's netnews." Oppose {nuke}.

:blow out: /vi./ [prob. from mining and tunneling jargon] Of software, to fail spectacularly; almost as serious as {crash and burn}. See {blow past}, {blow up}, {die horribly}.

:blow past: /vt./ To {blow out} despite a safeguard. "The server blew past the 5K reserve buffer."

:blow up: /vi./ 1. [scientific computation] To become unstable. Suggests that the computation is diverging so rapidly that it will soon overflow or at least go {nonlinear}. 2. Syn. {blow out}.

:BLT: /B-L-T/, /bl*t/ or (rarely) /belt/ /n.,vt./ Synonym for {blit}. This is the original form of {blit} and the ancestor of {bitblt}. It referred to any large bit-field copy or move operation (one resource-intensive memory-shuffling operation done on pre-paged versions of ITS, WAITS, and TOPS-10 was sardonically referred to as `The Big BLT'). The jargon usage has outlasted the {PDP-10} BLock Transfer instruction from which {BLT} derives; nowadays, the assembler mnemonic {BLT} almost always means `Branch if Less Than zero'.

:Blue Book: /n./ 1. Informal name for one of the three standard references on the page-layout and graphics-control language {{PostScript}} ("PostScript Language Tutorial and Cookbook", Adobe Systems, Addison-Wesley 1985, QA76.73.P67P68, ISBN 0-201-10179-3); the other three official guides are known as the {Green Book}, the {Red Book}, and the {White Book} (sense 2). 2. Informal name for one of the three standard references on Smalltalk: "Smalltalk-80: The Language and its Implementation", David Robson, Addison-Wesley 1983, QA76.8.S635G64, ISBN 0-201-11371-63 (this book also has green and red siblings). 3. Any of the 1988 standards issued by the CCITT's ninth plenary assembly. These include, among other things, the X.400 email spec and the Group 1 through 4 fax standards. See also {{book titles}}.

:blue box: /n./ 1. obs. Once upon a time, before all-digital switches made it possible for the phone companies to move them out of band, one could actually hear the switching tones used to route long-distance calls. Early {phreaker}s built devices called `blue boxes' that could reproduce these tones, which could be used to commandeer portions of the phone network. (This was not as hard as it may sound; one early phreak acquired the sobriquet `Captain Crunch' after he proved that he could generate switching tones with a plastic whistle pulled out of a box of Captain Crunch cereal!) There were other colors of box with more specialized phreaking uses; red boxes, black boxes, silver boxes, etc. 2. /n./ An {IBM} machine, especially a large (non-PC) one.

:Blue Glue: /n./ [IBM] IBM's SNA (Systems Network Architecture), an incredibly {losing} and {bletcherous} communications protocol widely favored at commercial shops that don't know any better. The official IBM definition is "that which binds blue boxes together." See {fear and loathing}. It may not be irrelevant that {Blue Glue} is the trade name of a 3M product that is commonly used to hold down the carpet squares to the removable panel floors common in {dinosaur pen}s. A correspondent at U. Minn. reports that the CS department there has about 80 bottles of the stuff hanging about, so they often refer to any messy work to be done as `using the blue glue'.

:blue goo: /n./ Term for `police' {nanobot}s intended to prevent {gray goo}, denature hazardous waste, destroy pollution, put ozone back into the stratosphere, prevent halitosis, and promote truth, justice, and the American way, etc. The term `Blue Goo' can be found in Dr. Seuss's "Fox In Socks" to refer to a substance much like bubblegum. `Would you like to chew blue goo, sir?'. See {{nanotechnology}}.

:blue wire: /n./ [IBM] Patch wires added to circuit boards at the factory to correct design or fabrication problems. These may be necessary if there hasn't been time to design and qualify another board version. Compare {purple wire}, {red wire}, {yellow wire}.

:blurgle: /bler'gl/ /n./ [UK] Spoken {metasyntactic variable}, to indicate some text that is obvious from context, or which is already known. If several words are to be replaced, blurgle may well be doubled or tripled. "To look for something in several files use `grep string blurgle blurgle'." In each case, "blurgle blurgle" would be understood to be replaced by the file you wished to search. Compare {mumble}, sense 7.

:BNF: /B-N-F/ /n./ 1. [techspeak] Acronym for `Backus-Naur Form', a metasyntactic notation used to specify the syntax of programming languages, command sets, and the like. Widely used for language descriptions but seldom documented anywhere, so that it must usually be learned by osmosis from other hackers. Consider this BNF for a U.S. postal address:

<postal-address> ::= <name-part> <street-address> <zip-part>

<personal-part> ::= <name> | <initial> "."

<name-part> ::= <personal-part> <last-name> [<jr-part>] <EOL> | <personal-part> <name-part>

<street-address> ::= [<apt>] <house-num> <street-name> <EOL>

<zip-part> ::= <town-name> "," <state-code> <ZIP-code> <EOL>

This translates into English as: "A postal-address consists of a name-part, followed by a street-address part, followed by a zip-code part. A personal-part consists of either a first name or an initial followed by a dot. A name-part consists of either: a personal-part followed by a last name followed by an optional `jr-part' (Jr., Sr., or dynastic number) and end-of-line, or a personal part followed by a name part (this rule illustrates the use of recursion in BNFs, covering the case of people who use multiple first and middle names and/or initials). A street address consists of an optional apartment specifier, followed by a street number, followed by a street name. A zip-part consists of a town-name, followed by a comma, followed by a state code, followed by a ZIP-code followed by an end-of-line." Note that many things (such as the format of a personal-part, apartment specifier, or ZIP-code) are left unspecified. These are presumed to be obvious from context or detailed somewhere nearby. See also {parse}. 2. Any of a number number of variants and extensions of BNF proper, possibly containing some or all of the {regexp} wildcards such as `*' or `+'. In fact the example above isn't the pure form invented for the Algol-60 report; it uses `', which was introduced a few years later in IBM's PL/I definition but is now universally recognized. 3. In {{science-fiction fandom}}, a `Big-Name Fan' (someone famous or notorious). Years ago a fan started handing out black-on-green BNF buttons at SF conventions; this confused the hacker contingent terribly.

:boa: [IBM] /n./ Any one of the fat cables that lurk under the floor in a {dinosaur pen}. Possibly so called because they display a ferocious life of their own when you try to lay them straight and flat after they have been coiled for some time. It is rumored within IBM that channel cables for the 370 are limited to 200 feet because beyond that length the boas get dangerous — and it is worth noting that one of the major cable makers uses the trademark `Anaconda'.

:board: /n./ 1. In-context synonym for {bboard}; sometimes used even for Usenet newsgroups (but see usage note under {bboard}, sense 1). 2. An electronic circuit board.

:boat anchor: /n./ 1. Like {doorstop} but more severe; implies that the offending hardware is irreversibly dead or useless. "That was a working motherboard once. One lightning strike later, instant boat anchor!" 2. A person who just takes up space. 3. Obsolete but still working hardware, especially when used of an old S100-bus hobbyist system; originally a term of annoyance, but became more and more affectionate as the hardware became more and more obsolete.

:bodysurf code: /n./ A program or segment of code written quickly in the heat of inspiration without the benefit of formal design or deep thought. Like its namesake sport, the result is too often a wipeout that leaves the programmer eating sand.

:BOF: /B-O-F/ or /bof/ /n./ Abbreviation for the phrase "Birds Of a Feather" (flocking together), an informal discussion group and/or bull session scheduled on a conference program. It is not clear where or when this term originated, but it is now associated with the USENIX conferences for Unix techies and was already established there by 1984. It was used earlier than that at DECUS conferences and is reported to have been common at SHARE meetings as far back as the early 1960s.

:BOFH: // /n./ Acronym, Bastard Operator From Hell. A system administrator with absolutely no tolerance for {luser}s. "You say you need more filespace? <massive-global-delete> Seems to me you have plenty left…" Many BOFHs (and others who would be BOFHs if they could get away with it) hang out in the newsgroup alt.sysadmin.recovery, although there has also been created a top-level newsgroup hierarchy (bofh.*) of their own.

Several people have written stories about BOFHs. The set usually
considered canonical is by Simon Travaglia and may be found at the
Bastard Home Page,
http://prime-mover.cc.waikato.ac.nz/Bastard.html.

:bogo-sort: /boh`goh-sort'/ /n./ (var. `stupid-sort') The archetypical perversely awful algorithm (as opposed to {bubble sort}, which is merely the generic *bad* algorithm). Bogo-sort is equivalent to repeatedly throwing a deck of cards in the air, picking them up at random, and then testing whether they are in order. It serves as a sort of canonical example of awfulness. Looking at a program and seeing a dumb algorithm, one might say "Oh, I see, this program uses bogo-sort." Compare {bogus}, {brute force}, {Lasherism}.

:bogometer: /boh-gom'-*t-er/ /n./ A notional instrument for measuring {bogosity}. Compare the `wankometer' described in the {wank} entry; see also {bogus}.

:bogon: /boh'gon/ /n./ [by analogy with proton/electron/neutron, but doubtless reinforced after 1980 by the similarity to Douglas Adams's `Vogons'; see the {Bibliography} in Appendix C and note that Arthur Dent actually mispronounces `Vogons' as `Bogons' at one point] 1. The elementary particle of bogosity (see {quantum bogodynamics}). For instance, "the Ethernet is emitting bogons again" means that it is broken or acting in an erratic or bogus fashion. 2. A query packet sent from a TCP/IP domain resolver to a root server, having the reply bit set instead of the query bit. 3. Any bogus or incorrectly formed packet sent on a network. 4. By synecdoche, used to refer to any bogus thing, as in "I'd like to go to lunch with you but I've got to go to the weekly staff bogon". 5. A person who is bogus or who says bogus things. This was historically the original usage, but has been overtaken by its derivative senses 1—4. See also {bogosity}, {bogus}; compare {psyton}, {fat electrons}, {magic smoke}.

The bogon has become the type case for a whole bestiary of nonce particle names, including the `clutron' or `cluon' (indivisible particle of cluefulness, obviously the antiparticle of the bogon) and the futon (elementary particle of {randomness}, or sometimes of lameness). These are not so much live usages in themselves as examples of a live meta-usage: that is, it has become a standard joke or linguistic maneuver to "explain" otherwise mysterious circumstances by inventing nonce particle names. And these imply nonce particle theories, with all their dignity or lack thereof (we might note parenthetically that this is a generalization from "(bogus particle) theories" to "bogus (particle theories)"!). Perhaps such particles are the modern-day equivalents of trolls and wood-nymphs as standard starting-points around which to construct explanatory myths. Of course, playing on an existing word (as in the `futon') yields additional flavor. Compare {magic smoke}.

:bogon filter: /boh'gon fil'tr/ /n./ Any device, software or
hardware, that limits or suppresses the flow and/or emission of
bogons. "Engineering hacked a bogon filter between the Cray and
the VAXen, and now we're getting fewer dropped packets." See also
{bogosity}, {bogus}.

:bogon flux: /boh'gon fluhks/ /n./ A measure of a supposed
field of {bogosity} emitted by a speaker, measured by a
{bogometer}; as a speaker starts to wander into increasing
bogosity a listener might say "Warning, warning, bogon flux is
rising". See {quantum bogodynamics}.

:bogosity: /boh-go's*-tee/ /n./ 1. The degree to which something is {bogus}. At CMU, bogosity is measured with a {bogometer}; in a seminar, when a speaker says something bogus, a listener might raise his hand and say "My bogometer just triggered". More extremely, "You just pinned my bogometer" means you just said or did something so outrageously bogus that it is off the scale, pinning the bogometer needle at the highest possible reading (one might also say "You just redlined my bogometer"). The agreed-upon unit of bogosity is the {microLenat}. 2. The potential field generated by a {bogon flux}; see {quantum bogodynamics}. See also {bogon flux}, {bogon filter}, {bogus}.

:bogotify: /boh-go't*-fi:/ /vt./ To make or become bogus. A program that has been changed so many times as to become completely disorganized has become bogotified. If you tighten a nut too hard and strip the threads on the bolt, the bolt has become bogotified and you had better not use it any more. This coinage led to the notional `autobogotiphobia' defined as `the fear of becoming bogotified'; but is not clear that the latter has ever been `live' jargon rather than a self-conscious joke in jargon about jargon. See also {bogosity}, {bogus}.

:bogue out: /bohg owt/ /vi./ To become bogus, suddenly and unexpectedly. "His talk was relatively sane until somebody asked him a trick question; then he bogued out and did nothing but {flame} afterwards." See also {bogosity}, {bogus}.

:bogus: /adj./ 1. Non-functional. "Your patches are bogus." 2. Useless. "OPCON is a bogus program." 3. False. "Your arguments are bogus." 4. Incorrect. "That algorithm is bogus." 5. Unbelievable. "You claim to have solved the halting problem for Turing Machines? That's totally bogus." 6. Silly. "Stop writing those bogus sagas."

Astrology is bogus. So is a bolt that is obviously about to break. So is someone who makes blatantly false claims to have solved a scientific problem. (This word seems to have some, but not all, of the connotations of {random} — mostly the negative ones.)

It is claimed that `bogus' was originally used in the hackish sense at Princeton in the late 1960s. It was spread to CMU and Yale by Michael Shamos, a migratory Princeton alumnus. A glossary of bogus words was compiled at Yale when the word was first popularized (see {autobogotiphobia} under {bogotify}). The word spread into hackerdom from CMU and MIT. By the early 1980s it was also current in something like the hackish sense in West Coast teen slang, and it had gone mainstream by 1985. A correspondent from Cambridge reports, by contrast, that these uses of `bogus' grate on British nerves; in Britain the word means, rather specifically, `counterfeit', as in "a bogus 10-pound note".

:Bohr bug: /bohr buhg/ /n./ [from quantum physics] A repeatable {bug}; one that manifests reliably under a possibly unknown but well-defined set of conditions. Antonym of {heisenbug}; see also {mandelbug}, {schroedinbug}.

:boink: /boynk/ [Usenet: variously ascribed to the TV
series "Cheers" "Moonlighting", and "Soap"]
1. /v./ To have sex with; compare {bounce}, sense 3. (This is
mainstream slang.) In Commonwealth hackish the variant `bonk' is
more common. 2. /n./ After the original Peter Korn `Boinkon'
{Usenet} parties, used for almost any net social gathering,
e.g., Miniboink, a small boink held by Nancy Gillett in 1988;
Minniboink, a Boinkcon in Minnesota in 1989; Humpdayboinks,
Wednesday get-togethers held in the San Francisco Bay Area.
Compare {@-party}. 3. Var of `bonk'; see {bonk/oif}.

:bomb: 1. /v./ General synonym for {crash} (sense 1) except
that it is not used as a noun; esp. used of software or OS
failures. "Don't run Empire with less than 32K stack, it'll
bomb." 2. /n.,v./ Atari ST and Macintosh equivalents of a Unix
`panic' or Amiga {guru} (sense 2), in which icons of little
black-powder bombs or mushroom clouds are displayed, indicating
that the system has died. On the Mac, this may be accompanied by a
decimal (or occasionally hexadecimal) number indicating what went
wrong, similar to the Amiga {guru meditation} number.
{{MS-DOS}} machines tend to get {locked up} in this situation.

:bondage-and-discipline language: /n./ A language (such as {{Pascal}}, {{Ada}}, APL, or Prolog) that, though ostensibly general-purpose, is designed so as to enforce an author's theory of `right programming' even though said theory is demonstrably inadequate for systems hacking or even vanilla general-purpose programming. Often abbreviated `B&D'; thus, one may speak of things "having the B&D nature". See {{Pascal}}; oppose {languages of choice}.

:bonk/oif: /bonk/, /oyf/ /interj./ In the {MUD} community, it has become traditional to express pique or censure by `bonking' the offending person. Convention holds that one should acknowledge a bonk by saying `oif!' and there is a myth to the effect that failing to do so upsets the cosmic bonk/oif balance, causing much trouble in the universe. Some MUDs have implemented special commands for bonking and oifing. See also {talk mode}.

:book titles:: There is a tradition in hackerdom of informally tagging important textbooks and standards documents with the dominant color of their covers or with some other conspicuous feature of the cover. Many of these are described in this lexicon under their own entries. See {Aluminum Book}, {Blue Book}, {Camel Book}, {Cinderella Book}, {Devil Book}, {Dragon Book}, {Green Book}, {Orange Book}, {Pink-Shirt Book}, {Purple Book}, {Red Book}, {Silver Book}, {White Book}, {Wizard Book}, {Yellow Book}, and {bible}; see also {rainbow series}. Since about 1983 this tradition has gotten a boost from the popular O'Reilly Associates line of technical books, which usually feature some kind of exotic animal on the cover.

:boot: /v.,n./ [techspeak; from `by one's bootstraps'] To load and initialize the operating system on a machine. This usage is no longer jargon (having passed into techspeak) but has given rise to some derivatives that are still jargon.

The derivative `reboot' implies that the machine hasn't been down for long, or that the boot is a {bounce} (sense 4) intended to clear some state of {wedgitude}. This is sometimes used of human thought processes, as in the following exchange: "You've lost me." "OK, reboot. Here's the theory…."

This term is also found in the variants `cold boot' (from power-off condition) and `warm boot' (with the CPU and all devices already powered up, as after a hardware reset or software crash).

Another variant: `soft boot', reinitialization of only part of a system, under control of other software still running: "If you're running the {mess-dos} emulator, control-alt-insert will cause a soft-boot of the emulator, while leaving the rest of the system running."

Opposed to this there is `hard boot', which connotes hostility towards or frustration with the machine being booted: "I'll have to hard-boot this losing Sun." "I recommend booting it hard." One often hard-boots by performing a {power cycle}.

Historical note: this term derives from `bootstrap loader', a short program that was read in from cards or paper tape, or toggled in from the front panel switches. This program was always very short (great efforts were expended on making it short in order to minimize the labor and chance of error involved in toggling it in), but was just smart enough to read in a slightly more complex program (usually from a card or paper tape reader), to which it handed control; this program in turn was smart enough to read the application or operating system from a magnetic tape drive or disk drive. Thus, in successive steps, the computer `pulled itself up by its bootstraps' to a useful operating state. Nowadays the bootstrap is usually found in ROM or EPROM, and reads the first stage in from a fixed location on the disk, called the `boot block'. When this program gains control, it is powerful enough to load the actual OS and hand control over to it.

:bottom feeder: /n./ Syn. for {slopsucker}, derived from the fishermen's and naturalists' term for finny creatures who subsist on the primordial ooze.

:bottom-up implementation: /n./ Hackish opposite of the techspeak term `top-down design'. It is now received wisdom in most programming cultures that it is best to design from higher levels of abstraction down to lower, specifying sequences of action in increasing detail until you get to actual code. Hackers often find (especially in exploratory designs that cannot be closely specified in advance) that it works best to *build* things in the opposite order, by writing and testing a clean set of primitive operations and then knitting them together.

:bounce: /v./ 1. [perhaps by analogy to a bouncing check] An electronic mail message that is undeliverable and returns an error notification to the sender is said to `bounce'. See also {bounce message}. 2. [Stanford] To play volleyball. The now-demolished {D. C. Power Lab} building used by the Stanford AI Lab in the 1970s had a volleyball court on the front lawn. From 5 P.M. to 7 P.M. was the scheduled maintenance time for the computer, so every afternoon at 5 would come over the intercom the cry: "Now hear this: bounce, bounce!", followed by Brian McCune loudly bouncing a volleyball on the floor outside the offices of known volleyballers. 3. To engage in sexual intercourse; prob. from the expression `bouncing the mattress', but influenced by Roo's psychosexually loaded "Try bouncing me, Tigger!" from the "Winnie-the-Pooh" books. Compare {boink}. 4. To casually reboot a system in order to clear up a transient problem. Reported primarily among {VMS} users. 5. [VM/CMS programmers] *Automatic* warm-start of a machine after an error. "I logged on this morning and found it had bounced 7 times during the night" 6. [IBM] To {power cycle} a peripheral in order to reset it.

:bounce message: /n./ [Unix] Notification message returned to sender
by a site unable to relay {email} to the intended {{Internet
address}} recipient or the next link in a {bang path} (see
{bounce}, sense 1). Reasons might include a nonexistent or
misspelled username or a {down} relay site. Bounce messages can
themselves fail, with occasionally ugly results; see {sorcerer's
apprentice mode} and {software laser}. The terms `bounce
mail' and `barfmail' are also common.

:boustrophedon: /n./ [from a Greek word for turning like an ox
while plowing] An ancient method of writing using alternate
left-to-right and right-to-left lines. This term is actually
philologists' techspeak and typesetters' jargon. Erudite hackers
use it for an optimization performed by some computer typesetting
software and moving-head printers. The adverbial form
`boustrophedonically' is also found (hackers purely love
constructions like this).

:box: /n./ 1. A computer; esp. in the construction `foo box' where foo is some functional qualifier, like `graphics', or the name of an OS (thus, `Unix box', `MS-DOS box', etc.) "We preprocess the data on Unix boxes before handing it up to the mainframe." 2. [IBM] Without qualification but within an SNA-using site, this refers specifically to an IBM front-end processor or FEP /F-E-P/. An FEP is a small computer necessary to enable an IBM {mainframe} to communicate beyond the limits of the {dinosaur pen}. Typically used in expressions like the cry that goes up when an SNA network goes down: "Looks like the {box} has fallen over." (See {fall over}.) See also {IBM}, {fear and loathing}, {fepped out}, {Blue Glue}.

:boxed comments: /n./ Comments (explanatory notes attached to program instructions) that occupy several lines by themselves; so called because in assembler and C code they are often surrounded by a box in a style something like this:

/*************************************************
*
* This is a boxed comment in C style
*
*************************************************/

Common variants of this style omit the asterisks in column 2 or add
a matching row of asterisks closing the right side of the box. The
sparest variant omits all but the comment delimiters themselves;
the `box' is implied. Oppose {winged comments}.

:boxen: /bok'sn/ /pl.n./ [by analogy with {VAXen}]
Fanciful plural of {box} often encountered in the phrase `Unix
boxen', used to describe commodity {{Unix}} hardware. The
connotation is that any two Unix boxen are interchangeable.

:boxology: /bok-sol'*-jee/ /n./ Syn. {ASCII art}. This
term implies a more restricted domain, that of box-and-arrow
drawings. "His report has a lot of boxology in it." Compare
{macrology}.

:bozotic: /boh-zoh'tik/ or /boh-zo'tik/ /adj./ [from the name of a TV clown even more losing than Ronald McDonald] Resembling or having the quality of a bozo; that is, clownish, ludicrously wrong, unintentionally humorous. Compare {wonky}, {demented}. Note that the noun `bozo' occurs in slang, but the mainstream adjectival form would be `bozo-like' or (in New England) `bozoish'.

:BQS: /B-Q-S/ /adj./ Syn. {Berkeley Quality Software}.

:brain dump: /n./ The act of telling someone everything one knows about a particular topic or project. Typically used when someone is going to let a new party maintain a piece of code. Conceptually analogous to an operating system {core dump} in that it saves a lot of useful {state} before an exit. "You'll have to give me a brain dump on FOOBAR before you start your new job at HackerCorp." See {core dump} (sense 4). At Sun, this is also known as `TOI' (transfer of information).

:brain fart: /n./ The actual result of a {braino}, as opposed to the mental glitch that is the braino itself. E.g., typing `dir' on a Unix box after a session with DOS.

:brain-damaged: /adj./ 1. [generalization of `Honeywell Brain Damage' (HBD), a theoretical disease invented to explain certain utter cretinisms in Honeywell {{Multics}}] /adj./ Obviously wrong; {cretinous}; {demented}. There is an implication that the person responsible must have suffered brain damage, because he should have known better. Calling something brain-damaged is really bad; it also implies it is unusable, and that its failure to work is due to poor design rather than some accident. "Only six monocase characters per file name? Now *that's* brain-damaged!" 2. [esp. in the Mac world] May refer to free demonstration software that has been deliberately crippled in some way so as not to compete with the commercial product it is intended to sell. Syn. {crippleware}.

:brain-dead: /adj./ Brain-damaged in the extreme. It tends to imply terminal design failure rather than malfunction or simple stupidity. "This comm program doesn't know how to send a break — how brain-dead!"

:braino: /bray'no/ /n./ Syn. for {thinko}. See also {brain fart}.

:branch to Fishkill: /n./ [IBM: from the location of one of the corporation's facilities] Any unexpected jump in a program that produces catastrophic or just plain weird results. See {jump off into never-never land}, {hyperspace}.

:bread crumbs: /n./ Debugging statements inserted into a program that emit output or log indicators of the program's {state} to a file so you can see where it dies or pin down the cause of surprising behavior. The term is probably a reference to the Hansel and Gretel story from the Brothers Grimm; in several variants, a character leaves a trail of bread crumbs so as not to get lost in the woods.

:break: 1. /vt./ To cause to be {broken} (in any sense).
"Your latest patch to the editor broke the paragraph commands."
2. /v./ (of a program) To stop temporarily, so that it may
debugged.
The place where it stops is a `breakpoint'. 3. [techspeak]
/vi./ To send an RS-232 break (two character widths of line high)
over a serial comm line. 4. [Unix] /vi./ To strike whatever key
currently causes the tty driver to send SIGINT to the current
process. Normally, break (sense 3), delete or {control-C} does
this. 5. `break break' may be said to interrupt a conversation
(this is an example of verb doubling). This usage comes from radio
communications, which in turn probably came from landline
telegraph/teleprinter usage, as badly abused in the Citizen's Band
craze a few years ago.

:break-even point: /n./ In the process of implementing a new computer language, the point at which the language is sufficiently effective that one can implement the language in itself. That is, for a new language called, hypothetically, FOOGOL, one has reached break-even when one can write a demonstration compiler for FOOGOL in FOOGOL, discard the original implementation language, and thereafter use working versions of FOOGOL to develop newer ones. This is an important milestone; see {MFTL}.

Since this entry was first written, several correspondents have reported that there actually was a compiler for a tiny Algol-like language called Foogol floating around on various {VAXen} in the early and mid-1980s. A FOOGOL implementation is available at the Retrocomputing Museum http://www.ccil.org/retro.

:breath-of-life packet: /n./ [XEROX PARC] An Ethernet packet that contains bootstrap (see {boot}) code, periodically sent out from a working computer to infuse the `breath of life' into any computer on the network that has happened to crash. Machines depending on such packets have sufficient hardware or firmware code to wait for (or request) such a packet during the reboot process. See also {dickless workstation}.

The notional `kiss-of-death packet', with a function complementary to that of a breath-of-life packet, is recommended for dealing with hosts that consume too many network resources. Though `kiss-of-death packet' is usually used in jest, there is at least one documented instance of an Internet subnet with limited address-table slots in a gateway machine in which such packets were routinely used to compete for slots, rather like Christmas shoppers competing for scarce parking spaces.

:breedle: /n./ See {feep}.

:bring X to its knees: /v./ To present a machine, operating system, piece of software, or algorithm with a load so extreme or {pathological} that it grinds to a halt. "To bring a MicroVAX to its knees, try twenty users running {vi} — or four running {EMACS}." Compare {hog}.

:brittle: /adj./ Said of software that is functional but easily broken by changes in operating environment or configuration, or by any minor tweak to the software itself. Also, any system that responds inappropriately and disastrously to abnormal but expected external stimuli; e.g., a file system that is usually totally scrambled by a power failure is said to be brittle. This term is often used to describe the results of a research effort that were never intended to be robust, but it can be applied to commercially developed software, which displays the quality far more often than it ought to. Oppose {robust}.

:broadcast storm: /n./ An incorrect packet broadcast on a network that causes most hosts to respond all at once, typically with wrong answers that start the process over again. See {network meltdown}; compare {mail storm}.

:brochureware: /n./ Planned but non-existent product like {vaporware}, but with the added implication that marketing is actively selling and promoting it (they've printed brochures). Brochureware is often deployed as a strategic weapon; the idea is to con customers into not committing to an existing product of the competition's. It is a safe bet that when a brochureware product finally becomes real, it will be more expensive than and inferior to the alternatives that had been available for years.

:broken: /adj./ 1. Not working properly (of programs). 2. Behaving strangely; especially (when used of people) exhibiting extreme depression.

:broken arrow: /n./ [IBM] The error code displayed on line 25 of a 3270 terminal (or a PC emulating a 3270) for various kinds of protocol violations and "unexpected" error conditions (including connection to a {down} computer). On a PC, simulated with `->/_', with the two center characters overstruck.

Note: to appreciate this term fully, it helps to know that `broken arrow' is also military jargon for an accident involving nuclear weapons….

:BrokenWindows: /n./ Abusive hackerism for the {crufty} and {elephantine} {X} environment on Sun machines; properly called `OpenWindows'.

:broket: /broh'k*t/ or /broh'ket`/ /n./ [by analogy with `bracket': a `broken bracket'] Either of the characters `<' and `>', when used as paired enclosing delimiters. This word originated as a contraction of the phrase `broken bracket', that is, a bracket that is bent in the middle. (At MIT, and apparently in the {Real World} as well, these are usually called {angle brackets}.)

:Brooks's Law: /prov./ "Adding manpower to a late software project makes it later" — a result of the fact that the expected advantage from splitting work among N programmers is O(N) (that is, proportional to N), but the complexity and communications cost associated with coordinating and then merging their work is O(N^2) (that is, proportional to the square of N). The quote is from Fred Brooks, a manager of IBM's OS/360 project and author of "The Mythical Man-Month" (Addison-Wesley, 1975, ISBN 0-201-00650-2), an excellent early book on software engineering. The myth in question has been most tersely expressed as "Programmer time is fungible" and Brooks established conclusively that it is not. Hackers have never forgotten his advice; too often, {management} still does. See also {creationism}, {second-system effect}, {optimism}.

:browser: /n./ A program specifically designed to help users view and navigate hypertext, on-line documentation, or a database. While this general sense has been present in jargon for a long time, the proliferation of browsers for the World Wide Web after 1992 has made it much more popular and provided a central or default meaning of the word previously lacking in hacker usage. Nowadays, if someone mentions using a `browser' without qualification, one may assume it is a Web browser.

:BRS: /B-R-S/ /n./ Syn. {Big Red Switch}. This abbreviation is fairly common on-line.

:brute force: /adj./ Describes a primitive programming style, one in which the programmer relies on the computer's processing power instead of using his or her own intelligence to simplify the problem, often ignoring problems of scale and applying naive methods suited to small problems directly to large ones. The term can also be used in reference to programming style: brute-force programs are written in a heavyhanded, tedious way, full of repetition and devoid of any elegance or useful abstraction (see also {brute force and ignorance}).

The {canonical} example of a brute-force algorithm is associated with the `traveling salesman problem' (TSP), a classical {NP-}hard problem: Suppose a person is in, say, Boston, and wishes to drive to N other cities. In what order should the cities be visited in order to minimize the distance travelled? The brute-force method is to simply generate all possible routes and compare the distances; while guaranteed to work and simple to implement, this algorithm is clearly very stupid in that it considers even obviously absurd routes (like going from Boston to Houston via San Francisco and New York, in that order). For very small N it works well, but it rapidly becomes absurdly inefficient when N increases (for N = 15, there are already 1,307,674,368,000 possible routes to consider, and for N = 1000 — well, see {bignum}). Sometimes, unfortunately, there is no better general solution than brute force. See also {NP-}.

A more simple-minded example of brute-force programming is finding the smallest number in a large list by first using an existing program to sort the list in ascending order, and then picking the first number off the front.

Whether brute-force programming should actually be considered stupid or not depends on the context; if the problem is not terribly big, the extra CPU time spent on a brute-force solution may cost less than the programmer time it would take to develop a more `intelligent' algorithm. Additionally, a more intelligent algorithm may imply more long-term complexity cost and bug-chasing than are justified by the speed improvement.

Ken Thompson, co-inventor of Unix, is reported to have uttered the epigram "When in doubt, use brute force". He probably intended this as a {ha ha only serious}, but the original Unix kernel's preference for simple, robust, and portable algorithms over {brittle} `smart' ones does seem to have been a significant factor in the success of that OS. Like so many other tradeoffs in software design, the choice between brute force and complex, finely-tuned cleverness is often a difficult one that requires both engineering savvy and delicate esthetic judgment.

:brute force and ignorance: /n./ A popular design technique at many software houses — {brute force} coding unrelieved by any knowledge of how problems have been previously solved in elegant ways. Dogmatic adherence to design methodologies tends to encourage this sort of thing. Characteristic of early {larval stage} programming; unfortunately, many never outgrow it. Often abbreviated BFI: "Gak, they used a {bubble sort}! That's strictly from BFI." Compare {bogosity}.

:BSD: /B-S-D/ /n./ [abbreviation for `Berkeley Software Distribution'] a family of {{Unix}} versions for the {DEC} {VAX} and PDP-11 developed by Bill Joy and others at {Berzerkeley} starting around 1980, incorporating paged virtual memory, TCP/IP networking enhancements, and many other features. The BSD versions (4.1, 4.2, and 4.3) and the commercial versions derived from them (SunOS, ULTRIX, and Mt. Xinu) held the technical lead in the Unix world until AT&T's successful standardization efforts after about 1986, and are still widely popular. Note that BSD versions going back to 2.9 are often referred to by their version numbers, without the BSD prefix. See {4.2}, {{Unix}}, {USG Unix}.

:BUAF: // /n./ [abbreviation, from alt.fan.warlord] Big Ugly ASCII Font — a special form of {ASCII art}. Various programs exist for rendering text strings into block, bloob, and pseudo-script fonts in cells between four and six character cells on a side; this is smaller than the letters generated by older {banner} (sense 2) programs. These are sometimes used to render one's name in a {sig block}, and are critically referred to as `BUAF's. See {warlording}.

:BUAG: // /n./ [abbreviation, from alt.fan.warlord] Big Ugly ASCII Graphic. Pejorative term for ugly {ASCII art}, especially as found in {sig block}s. For some reason, mutations of the head of Bart Simpson are particularly common in the least imaginative {sig block}s. See {warlording}.

:bubble sort: /n./ Techspeak for a particular sorting technique in which pairs of adjacent values in the list to be sorted are compared and interchanged if they are out of order; thus, list entries `bubble upward' in the list until they bump into one with a lower sort value. Because it is not very good relative to other methods and is the one typically stumbled on by {naive} and untutored programmers, hackers consider it the {canonical} example of a naive algorithm. The canonical example of a really *bad* algorithm is {bogo-sort}. A bubble sort might be used out of ignorance, but any use of bogo-sort could issue only from brain damage or willful perversity.

:bucky bits: /buh'kee bits/ /n./ 1. obs. The bits produced by the CONTROL and META shift keys on a SAIL keyboard (octal 200 and 400 respectively), resulting in a 9-bit keyboard character set. The MIT AI TV (Knight) keyboards extended this with TOP and separate left and right CONTROL and META keys, resulting in a 12-bit character set; later, LISP Machines added such keys as SUPER, HYPER, and GREEK (see {space-cadet keyboard}). 2. By extension, bits associated with `extra' shift keys on any keyboard, e.g., the ALT on an IBM PC or command and option keys on a Macintosh.

It has long been rumored that `bucky bits' were named for Buckminster Fuller during a period when he was consulting at Stanford. Actually, bucky bits were invented by Niklaus Wirth when *he* was at Stanford in 1964—65; he first suggested the idea of an EDIT key to set the 8th bit of an otherwise 7-bit ASCII character). It seems that, unknown to Wirth, certain Stanford hackers had privately nicknamed him `Bucky' after a prominent portion of his dental anatomy, and this nickname transferred to the bit. Bucky-bit commands were used in a number of editors written at Stanford, including most notably TV-EDIT and NLS.

The term spread to MIT and CMU early and is now in general use. Ironically, Wirth himself remained unaware of its derivation for nearly 30 years, until GLS dug up this history in early 1993! See {double bucky}, {quadruple bucky}.

:buffer chuck: /n./ Shorter and ruder syn. for {buffer overflow}.

:buffer overflow: /n./ What happens when you try to stuff more data into a buffer (holding area) than it can handle. This may be due to a mismatch in the processing rates of the producing and consuming processes (see {overrun} and {firehose syndrome}), or because the buffer is simply too small to hold all the data that must accumulate before a piece of it can be processed. For example, in a text-processing tool that {crunch}es a line at a time, a short line buffer can result in {lossage} as input from a long line overflows the buffer and trashes data beyond it. Good defensive programming would check for overflow on each character and stop accepting data when the buffer is full up. The term is used of and by humans in a metaphorical sense. "What time did I agree to meet you? My buffer must have overflowed." Or "If I answer that phone my buffer is going to overflow." See also {spam}, {overrun screw}.

:bug: /n./ An unwanted and unintended property of a program or piece of hardware, esp. one that causes it to malfunction. Antonym of {feature}. Examples: "There's a bug in the editor: it writes things out backwards." "The system crashed because of a hardware bug." "Fred is a winner, but he has a few bugs" (i.e., Fred is a good guy, but he has a few personality problems).

Historical note: Admiral Grace Hopper (an early computing pioneer better known for inventing {COBOL}) liked to tell a story in which a technician solved a {glitch} in the Harvard Mark II machine by pulling an actual insect out from between the contacts of one of its relays, and she subsequently promulgated {bug} in its hackish sense as a joke about the incident (though, as she was careful to admit, she was not there when it happened). For many years the logbook associated with the incident and the actual bug in question (a moth) sat in a display case at the Naval Surface Warfare Center (NSWC). The entire story, with a picture of the logbook and the moth taped into it, is recorded in the "Annals of the History of Computing", Vol. 3, No. 3 (July 1981), pp. 285—286.

The text of the log entry (from September 9, 1947), reads "1545 Relay #70 Panel F (moth) in relay. First actual case of bug being found". This wording establishes that the term was already in use at the time in its current specific sense — and Hopper herself reports that the term `bug' was regularly applied to problems in radar electronics during WWII.

Indeed, the use of `bug' to mean an industrial defect was already established in Thomas Edison's time, and a more specific and rather modern use can be found in an electrical handbook from 1896 ("Hawkin's New Catechism of Electricity", Theo. Audel & Co.) which says: "The term `bug' is used to a limited extent to designate any fault or trouble in the connections or working of electric apparatus." It further notes that the term is "said to have originated in quadruplex telegraphy and have been transferred to all electric apparatus."

The latter observation may explain a common folk etymology of the term; that it came from telephone company usage, in which "bugs in a telephone cable" were blamed for noisy lines. Though this derivation seems to be mistaken, it may well be a distorted memory of a joke first current among *telegraph* operators more than a century ago!

Or perhaps not a joke. Historians of the field inform us that the term "bug" was regularly used in the early days of telegraphy to refer to a variety of semi-automatic telegraphy keyers that would send a string of dots if you held them down. In fact, the Vibroplex keyers (which were among the most common of this type) even had a graphic of a beetle on them! While the ability to send repeated dots automatically was very useful for professional morse code operators, these were also significantly trickier to use than the older manual keyers, and it could take some practice to ensure one didn't introduce extraneous dots into the code by holding the key down a fraction too long. In the hands of an inexperienced operator, a Vibroplex "bug" on the line could mean that a lot of garbled Morse would soon be coming your way.

Actually, use of `bug' in the general sense of a disruptive event goes back to Shakespeare! In the first edition of Samuel Johnson's dictionary one meaning of `bug' is "A frightful object; a walking spectre"; this is traced to `bugbear', a Welsh term for a variety of mythological monster which (to complete the circle) has recently been reintroduced into the popular lexicon through fantasy role-playing games.

In any case, in jargon the word almost never refers to insects.
Here is a plausible conversation that never actually happened:

"There is a bug in this ant farm!"

"What do you mean? I don't see any ants in it."

"That's the bug."

A careful discussion of the etymological issues can be found in a paper by Fred R. Shapiro, 1987, "Entomology of the Computer Bug: History and Folklore", American Speech 62(4):376-378.

[There has been a widespread myth that the original bug was moved to the Smithsonian, and an earlier version of this entry so asserted. A correspondent who thought to check discovered that the bug was not there. While investigating this in late 1990, your editor discovered that the NSWC still had the bug, but had unsuccessfully tried to get the Smithsonian to accept it — and that the present curator of their History of American Technology Museum didn't know this and agreed that it would make a worthwhile exhibit. It was moved to the Smithsonian in mid-1991, but due to space and money constraints has not yet been exhibited. Thus, the process of investigating the original-computer-bug bug fixed it in an entirely unexpected way, by making the myth true! —ESR]

:bug-compatible: /adj./ Said of a design or revision that has been badly compromised by a requirement to be compatible with {fossil}s or {misfeature}s in other programs or (esp.) previous releases of itself. "MS-DOS 2.0 used \ as a path separator to be bug-compatible with some cretin's choice of / as an option character in 1.0."

:bug-for-bug compatible: /n./ Same as {bug-compatible}, with the additional implication that much tedious effort went into ensuring that each (known) bug was replicated.

:bug-of-the-month club: /n./ [from "book-of-the-month club", a time-honored mail-order-marketing technique in the U.S.] A mythical club which users of `sendmail(1)' (the UNIX mail daemon) belong to; this was coined on the Usenet newsgroup comp.security.unix at a time when sendmail security holes, which allowed outside {cracker}s access to the system, were being uncovered at an alarming rate, forcing sysadmins to update very often. Also, more completely, `fatal security bug-of-the-month club'.

:buglix: /buhg'liks/ /n./ Pejorative term referring to {DEC}'s ULTRIX operating system in its earlier *severely* buggy versions. Still used to describe ULTRIX, but without nearly so much venom. Compare {AIDX}, {HP-SUX}, {Nominal Semidestructor}, {Telerat}, {sun-stools}.

:bulletproof: /adj./ Used of an algorithm or implementation considered extremely {robust}; lossage-resistant; capable of correctly recovering from any imaginable exception condition — a rare and valued quality. Syn. {armor-plated}.

:bum: 1. /vt./ To make highly efficient, either in time or
space, often at the expense of clarity. "I managed to bum three
more instructions out of that code." "I spent half the night
bumming the interrupt code." In 1996, this term and the practice
it
describes are semi-obsolete. In {elder days}, John McCarthy
(inventor of {LISP}) used to compare some efficiency-obsessed
hackers among his students to "ski bums"; thus, optimization
became "program bumming", and eventually just "bumming". 2. To
squeeze out excess; to remove something in order to improve
whatever it was removed from (without changing function; this
distinguishes the process from a {featurectomy}). 3. /n./ A small
change to an algorithm, program, or hardware device to make it more
efficient. "This hardware bum makes the jump instruction
faster." Usage: now uncommon, largely superseded by /v./ {tune}
(and /n./ {tweak}, {hack}), though none of these exactly
capture sense 2. All these uses are rare in Commonwealth hackish,
because in the parent dialects of English `bum' is a rude synonym
for `buttocks'.

:bump: /vt./ Synonym for increment. Has the same meaning as C's ++ operator. Used esp. of counter variables, pointers, and index dummies in `for', `while', and `do-while' loops.

:burble: /v./ [from Lewis Carroll's "Jabberwocky"] Like {flame}, but connotes that the source is truly clueless and ineffectual (mere flamers can be competent). A term of deep contempt. "There's some guy on the phone burbling about how he got a DISK FULL error and it's all our comm software's fault." This is mainstream slang in some parts of England.

:buried treasure: /n./ A surprising piece of code found in some program. While usually not wrong, it tends to vary from {crufty} to {bletcherous}, and has lain undiscovered only because it was functionally correct, however horrible it is. Used sarcastically, because what is found is anything *but* treasure. Buried treasure almost always needs to be dug up and removed. "I just found that the scheduler sorts its queue using {bubble sort}! Buried treasure!"

:burn-in period: /n./ 1. A factory test designed to catch systems with {marginal} components before they get out the door; the theory is that burn-in will protect customers by outwaiting the steepest part of the {bathtub curve} (see {infant mortality}). 2. A period of indeterminate length in which a person using a computer is so intensely involved in his project that he forgets basic needs such as food, drink, sleep, etc. Warning: Excessive burn-in can lead to burn-out. See {hack mode}, {larval stage}.

Historical note: the origin of "burn-in" (sense 1) is apparently
the practice of setting a new-model airplane's brakes on fire, then
extinguishing the fire, in order to make them hold better. This
was
done on the first version of the U.S. spy-plane, the U-2.

:burst page: /n./ Syn. {banner}, sense 1.

:busy-wait: /vi./ Used of human behavior, conveys that the subject is busy waiting for someone or something, intends to move instantly as soon as it shows up, and thus cannot do anything else at the moment. "Can't talk now, I'm busy-waiting till Bill gets off the phone."

Technically, `busy-wait' means to wait on an event by {spin}ning through a tight or timed-delay loop that polls for the event on each pass, as opposed to setting up an interrupt handler and continuing execution on another part of the task. This is a wasteful technique, best avoided on time-sharing systems where a busy-waiting program may {hog} the processor.

:buzz: /vi./ 1. Of a program, to run with no indication of progress and perhaps without guarantee of ever finishing; esp. said of programs thought to be executing tight loops of code. A program that is buzzing appears to be {catatonic}, but never gets out of catatonia, while a buzzing loop may eventually end of its own accord. "The program buzzes for about 10 seconds trying to sort all the names into order." See {spin}; see also {grovel}. 2. [ETA Systems] To test a wire or printed circuit trace for continuity by applying an AC rather than DC signal. Some wire faults will pass DC tests but fail a buzz test. 3. To process an array or list in sequence, doing the same thing to each element. "This loop buzzes through the tz array looking for a terminator type."

:BWQ: /B-W-Q/ /n./ [IBM: abbreviation, `Buzz Word Quotient'] The percentage of buzzwords in a speech or documents. Usually roughly proportional to {bogosity}. See {TLA}.

:by hand: /adv./ 1. Said of an operation (especially a repetitive, trivial, and/or tedious one) that ought to be performed automatically by the computer, but which a hacker instead has to step tediously through. "My mailer doesn't have a command to include the text of the message I'm replying to, so I have to do it by hand." This does not necessarily mean the speaker has to retype a copy of the message; it might refer to, say, dropping into a subshell from the mailer, making a copy of one's mailbox file, reading that into an editor, locating the top and bottom of the message in question, deleting the rest of the file, inserting `>' characters on each line, writing the file, leaving the editor, returning to the mailer, reading the file in, and later remembering to delete the file. Compare {eyeball search}. 2. By extension, writing code which does something in an explicit or low-level way for which a presupplied library routine ought to have been available. "This cretinous B-tree library doesn't supply a decent iterator, so I'm having to walk the trees by hand."

:byte:: /bi:t/ /n./ [techspeak] A unit of memory or data equal to the amount used to represent one character; on modern architectures this is usually 8 bits, but may be 9 on 36-bit machines. Some older architectures used `byte' for quantities of 6 or 7 bits, and the PDP-10 supported `bytes' that were actually bitfields of 1 to 36 bits! These usages are now obsolete, and even 9-bit bytes have become rare in the general trend toward power-of-2 word sizes.

Historical note: The term was coined by Werner Buchholz in 1956 during the early design phase for the IBM Stretch computer; originally it was described as 1 to 6 bits (typical I/O equipment of the period used 6-bit chunks of information). The move to an 8-bit byte happened in late 1956, and this size was later adopted and promulgated as a standard by the System/360. The word was coined by mutating the word `bite' so it would not be accidentally misspelled as {bit}. See also {nybble}.

:bytesexual: /bi:t`sek'shu-*l/ /adj./ Said of hardware, denotes willingness to compute or pass data in either {big-endian} or {little-endian} format (depending, presumably, on a {mode bit} somewhere). See also {NUXI problem}.

:bzzzt, wrong: /bzt rong/ /excl./ [Usenet/Internet] From a Robin Williams routine in the movie "Dead Poets Society" spoofing radio or TV quiz programs, such as *Truth or Consequences*, where an incorrect answer earns one a blast from the buzzer and condolences from the interlocutor. A way of expressing mock-rude disagreement, usually immediately following an included quote from another poster. The less abbreviated "*Bzzzzt*, wrong, but thank you for playing" is also common; capitalization and emphasis of the buzzer sound varies.

= C = =====

:C: /n./ 1. The third letter of the English alphabet. 2. ASCII
1000011. 3. The name of a programming language designed by Dennis
Ritchie during the early 1970s and immediately used to reimplement
{{Unix}}; so called because many features derived from an earlier
compiler named `B' in commemoration of *its* parent, BCPL.
(BCPL was in turn descended from an earlier Algol-derived language,
CPL.) Before Bjarne Stroustrup settled the question by designing
{C++}, there was a humorous debate over whether C's successor
should
be named `D' or `P'. C became immensely popular outside Bell Labs
after about 1980 and is now the dominant language in systems and
microcomputer applications programming. See also {languages of
choice}, {indent style}.

C is often described, with a mixture of fondness and disdain varying according to the speaker, as "a language that combines all the elegance and power of assembly language with all the readability and maintainability of assembly language".

:C Programmer's Disease: /n./ The tendency of the undisciplined C programmer to set arbitrary but supposedly generous static limits on table sizes (defined, if you're lucky, by constants in header files) rather than taking the trouble to do proper dynamic storage allocation. If an application user later needs to put 68 elements into a table of size 50, the afflicted programmer reasons that he or she can easily reset the table size to 68 (or even as much as 70, to allow for future expansion) and recompile. This gives the programmer the comfortable feeling of having made the effort to satisfy the user's (unreasonable) demands, and often affords the user multiple opportunities to explore the marvelous consequences of {fandango on core}. In severe cases of the disease, the programmer cannot comprehend why each fix of this kind seems only to further disgruntle the user.

:C++: /C'-pluhs-pluhs/ /n./ Designed by Bjarne Stroustrup
of AT&T Bell Labs as a successor to {C}. Now one of the
{languages of choice}, although many hackers still grumble that
it is the successor to either Algol 68 or {Ada} (depending on
generation), and a prime example of {second-system effect}.
Almost anything that can be done in any language can be done in
C++, but it requires a {language lawyer} to know what is and
what is not legal— the design is *almost* too large to hold
in even hackers' heads. Much of the {cruft} results from C++'s
attempt to be backward compatible with C. Stroustrup himself has
said in his retrospective book "The Design and Evolution of
C++" (p. 207), "Within C++, there is a much smaller and cleaner
language struggling to get out." [Many hackers would now add
"Yes, and it's called Java" —ESR]

:calculator: [Cambridge] /n./ Syn. for {bitty box}.

:Camel Book: /n./ Universally recognized nickname for the book
"Programming Perl", by Larry Wall and Randal L. Schwartz,
O'Reilly Associates 1991, ISBN 0-937175-64-1. The definitive
reference on {Perl}.

:can: /vt./ To abort a job on a time-sharing system. Used esp. when the person doing the deed is an operator, as in "canned from the {{console}}". Frequently used in an imperative sense, as in "Can that print job, the LPT just popped a sprocket!" Synonymous with {gun}. It is said that the ASCII character with mnemonic CAN (0011000) was used as a kill-job character on some early OSes. Alternatively, this term may derive from mainstream slang `canned' for being laid off or fired.

:can't happen: The traditional program comment for code executed under a condition that should never be true, for example a file size computed as negative. Often, such a condition being true indicates data corruption or a faulty algorithm; it is almost always handled by emitting a fatal error message and terminating or crashing, since there is little else that can be done. Some case variant of "can't happen" is also often the text emitted if the `impossible' error actually happens! Although "can't happen" events are genuinely infrequent in production code, programmers wise enough to check for them habitually are often surprised at how frequently they are triggered during development and how many headaches checking for them turns out to head off. See also {firewall code} (sense 2).

:candygrammar: /n./ A programming-language grammar that is mostly {syntactic sugar}; the term is also a play on `candygram'. {COBOL}, Apple's Hypertalk language, and a lot of the so-called `4GL' database languages share this property. The usual intent of such designs is that they be as English-like as possible, on the theory that they will then be easier for unskilled people to program. This intention comes to grief on the reality that syntax isn't what makes programming hard; it's the mental effort and organization required to specify an algorithm precisely that costs. Thus the invariable result is that `candygrammar' languages are just as difficult to program in as terser ones, and far more painful for the experienced hacker.

[The overtones from the old Chevy Chase skit on Saturday Night Live should not be overlooked. This was a "Jaws" parody. Someone lurking outside an apartment door tries all kinds of bogus ways to get the occupant to open up, while ominous music plays in the background. The last attempt is a half-hearted "Candygram!" When the door is opened, a shark bursts in and chomps the poor occupant. There is a moral here for those attracted to candygrammars. Note that, in many circles, pretty much the same ones who remember Monty Python sketches, all it takes is the word "Candygram!", suitably timed, to get people rolling on the floor. — GLS]

:canonical: /adj./ [historically, `according to religious law'] The usual or standard state or manner of something. This word has a somewhat more technical meaning in mathematics. Two formulas such as 9 + x and x + 9 are said to be equivalent because they mean the same thing, but the second one is in `canonical form' because it is written in the usual way, with the highest power of x first. Usually there are fixed rules you can use to decide whether something is in canonical form. The jargon meaning, a relaxation of the technical meaning, acquired its present loading in computer-science culture largely through its prominence in Alonzo Church's work in computation theory and mathematical logic (see {Knights of the Lambda Calculus}). Compare {vanilla}.

Non-technical academics do not use the adjective `canonical' in any of the senses defined above with any regularity; they do however use the nouns `canon' and `canonicity' (not **canonicalness or **canonicality). The `canon' of a given author is the complete body of authentic works by that author (this usage is familiar to Sherlock Holmes fans as well as to literary scholars). `*The* canon' is the body of works in a given field (e.g., works of literature, or of art, or of music) deemed worthwhile for students to study and for scholars to investigate.

The word `canon' has an interesting history. It derives
ultimately from the Greek
`kanon'
(akin to the English `cane') referring to a reed. Reeds were used
for measurement, and in Latin and later Greek the word `canon'
meant a rule or a standard. The establishment of a canon of
scriptures within Christianity was meant to define a standard or a
rule for the religion. The above non-techspeak academic usages
stem from this instance of a defined and accepted body of work.
Alongside this usage was the promulgation of `canons' (`rules')
for the government of the Catholic Church. The techspeak usages
("according to religious law") derive from this use of the Latin
`canon'.

Hackers invest this term with a playfulness that makes an ironic contrast with its historical meaning. A true story: One Bob Sjoberg, new at the MIT AI Lab, expressed some annoyance at the incessant use of jargon. Over his loud objections, GLS and RMS made a point of using as much of it as possible in his presence, and eventually it began to sink in. Finally, in one conversation, he used the word `canonical' in jargon-like fashion without thinking. Steele: "Aha! We've finally got you talking jargon too!" Stallman: "What did he say?" Steele: "Bob just used `canonical' in the canonical way."

Of course, canonicality depends on context, but it is implicitly defined as the way *hackers* normally expect things to be. Thus, a hacker may claim with a straight face that `according to religious law' is *not* the canonical meaning of `canonical'.

:card walloper: /n./ An EDP programmer who grinds out batch programs that do stupid things like print people's paychecks. Compare {code grinder}. See also {{punched card}}, {eighty-column mind}.

:careware: /keir'weir/ /n./ A variety of {shareware} for which either the author suggests that some payment be made to a nominated charity or a levy directed to charity is included on top of the distribution charge. Syn. {charityware}; compare {crippleware}, sense 2.

:cargo cult programming: /n./ A style of (incompetent) programming dominated by ritual inclusion of code or program structures that serve no real purpose. A cargo cult programmer will usually explain the extra code as a way of working around some bug encountered in the past, but usually neither the bug nor the reason the code apparently avoided the bug was ever fully understood (compare {shotgun debugging}, {voodoo programming}).

The term `cargo cult' is a reference to aboriginal religions that grew up in the South Pacific after World War II. The practices of these cults center on building elaborate mockups of airplanes and military style landing strips in the hope of bringing the return of the god-like airplanes that brought such marvelous cargo during the war. Hackish usage probably derives from Richard Feynman's characterization of certain practices as "cargo cult science" in his book "Surely You're Joking, Mr. Feynman!" (W. W. Norton & Co, New York 1985, ISBN 0-393-01921-7).

:cascade: /n./ 1. A huge volume of spurious error-message output produced by a compiler with poor error recovery. Too frequently, one trivial syntax error (such as a missing `)' or `}') throws the parser out of synch so that much of the remaining program text is interpreted as garbaged or ill-formed. 2. A chain of Usenet followups, each adding some trivial variation or riposte to the text of the previous one, all of which is reproduced in the new message; an {include war} in which the object is to create a sort of communal graffito.

:case and paste: /n./ [from `cut and paste'] 1. The addition of a new {feature} to an existing system by selecting the code from an existing feature and pasting it in with minor changes. Common in telephony circles because most operations in a telephone switch are selected using `case' statements. Leads to {software bloat}.

In some circles of EMACS users this is called `programming by Meta-W', because Meta-W is the EMACS command for copying a block of text to a kill buffer in preparation to pasting it in elsewhere. The term is condescending, implying that the programmer is acting mindlessly rather than thinking carefully about what is required to integrate the code for two similar cases.

At DEC, this is sometimes called `clone-and-hack' coding.

:casters-up mode: /n./ [IBM, prob. fr. slang belly up] Yet
another synonym for `broken' or `down'. Usually connotes a
major failure. A system (hardware or software) which is `down'
may be already being restarted before the failure is noticed,
whereas one which is `casters up' is usually a good excuse to
take the rest of the day off (as long as you're not responsible for
fixing it).

:casting the runes: /n./ What a {guru} does when you ask him
or her to run a particular program and type at it because it never
works for anyone else; esp. used when nobody can ever see what
the guru is doing different from what J. Random Luser does.
Compare {incantation}, {runes}, {examining the entrails};
also see the AI koan about Tom Knight in "{AI Koans}"
(Appendix A).

A correspondent from England tells us that one of ICL's most talented systems designers used to be called out occasionally to service machines which the {field circus} had given up on. Since he knew the design inside out, he could often find faults simply by listening to a quick outline of the symptoms. He used to play on this by going to some site where the field circus had just spent the last two weeks solid trying to find a fault, and spreading a diagram of the system out on a table top. He'd then shake some chicken bones and cast them over the diagram, peer at the bones intently for a minute, and then tell them that a certain module needed replacing. The system would start working again immediately upon the replacement.

:cat: [from `catenate' via {{Unix}} `cat(1)'] /vt./ 1. [techspeak] To spew an entire file to the screen or some other output sink without pause. 2. By extension, to dump large amounts of data at an unprepared target or with no intention of browsing it carefully. Usage: considered silly. Rare outside Unix sites. See also {dd}, {BLT}.

Among Unix fans, `cat(1)' is considered an excellent example of user-interface design, because it delivers the file contents without such verbosity as spacing or headers between the files, and because it does not require the files to consist of lines of text, but works with any sort of data.

Among Unix haters, `cat(1)' is considered the {canonical} example of *bad* user-interface design, because of its woefully unobvious name. It is far more often used to {blast} a file to standard output than to concatenate two files. The name `cat' for the former operation is just as unintuitive as, say, LISP's {cdr}.

Of such oppositions are {holy wars} made….

:catatonic: /adj./ Describes a condition of suspended animation in which something is so {wedged} or {hung} that it makes no response. If you are typing on a terminal and suddenly the computer doesn't even echo the letters back to the screen as you type, let alone do what you're asking it to do, then the computer is suffering from catatonia (possibly because it has crashed). "There I was in the middle of a winning game of {nethack} and it went catatonic on me! Aaargh!" Compare {buzz}.

:cd tilde: /C-D til-d*/ /vi./ To go home. From the Unix C-shell and Korn-shell command `cd ~', which takes one to one's `$HOME' (`cd' with no arguments happens to do the same thing). By extension, may be used with other arguments; thus, over an electronic chat link, `cd ~coffee' would mean "I'm going to the coffee machine."

:CDA: /C-D-A/ The "Communications Decency Act" of 1996, passed on {Black Thursday} as section 502 of a major telecommunications reform bill. The CDA made it a federal crime in the USA to send a communication which is "obscene, lewd, lascivious, filthy, or indecent, with intent to annoy, abuse, threaten, or harass another person." It also threatens with imprisonment anyone who "knowingly" makes accessible to minors any message that "describes, in terms patently offensive as measured by contemporary community standards, sexual or excretory activities or organs".

While the CDA was sold as a measure to protect minors from the putative evils of pornography, the repressive political aims of the bill were laid bare by the Hyde amendment, which intended to outlaw discussion of abortion on the Internet.

To say that this direct attack on First Amendment free-speech rights was not well received on the Internet would be putting it mildly. A firestorm of protest followed, including a February 29th mass demonstration by thousands of netters who turned their {home page}s black for 48 hours. Several civil-rights groups and computing/telecommunications companies sought an immediate injunction to block enforcement of the CDA pending a constitutional challenge. This injunction was granted on the likelihood that plaintiffs would prevail on the merits of the case. At time of writing (Spring 1996), the fate of the CDA, and its effect on the Internet, is still unknown. See also {Exon}.

To join the fight against the CDA (if it's still law) and other forms of Internet censorship, visit the Center for Democracy and Technology Home Page at http://www.cdt.org.

:cdr: /ku'dr/ or /kuh'dr/ /vt./ [from LISP] To skip past the first item from a list of things (generalized from the LISP operation on binary tree structures, which returns a list consisting of all but the first element of its argument). In the form `cdr down', to trace down a list of elements: "Shall we cdr down the agenda?" Usage: silly. See also {loop through}.

Historical note: The instruction format of the IBM 704 that hosted the original LISP implementation featured two 15-bit fields called the `address' and `decrement' parts. The term `cdr' was originally `Contents of Decrement part of Register'. Similarly, `car' stood for `Contents of Address part of Register'.

The cdr and car operations have since become bases for formation of compound metaphors in non-LISP contexts. GLS recalls, for example, a programming project in which strings were represented as linked lists; the get-character and skip-character operations were of course called CHAR and CHDR.

:chad: /chad/ /n./ 1. The perforated edge strips on printer paper, after they have been separated from the printed portion. Also called {selvage} and {perf}. 2. obs. The confetti-like paper bits punched out of cards or paper tape; this has also been called `chaff', `computer confetti', and `keypunch droppings'. This use may now be mainstream; it has been reported seen (1993) in directions for a card-based voting machine in California.

Historical note: One correspondent believes `chad' (sense 2) derives from the Chadless keypunch (named for its inventor), which cut little u-shaped tabs in the card to make a hole when the tab folded back, rather than punching out a circle/rectangle; it was clear that if the Chadless keypunch didn't make them, then the stuff that other keypunches made had to be `chad'. There is a legend that the word was originally acronymic, standing for "Card Hole Aggregate Debris", but this has all the earmarks of a bogus folk etymology.

:chad box: /n./ A metal box about the size of a lunchbox (or in some models a large wastebasket), for collecting the {chad} (sense 2) that accumulated in {Iron Age} card punches. You had to open the covers of the card punch periodically and empty the chad box. The {bit bucket} was notionally the equivalent device in the CPU enclosure, which was typically across the room in another great gray-and-blue box.

:chain: 1. /vi./ [orig. from BASIC's `CHAIN' statement] To hand off execution to a child or successor without going through the {OS} command interpreter that invoked it. The state of the parent program is lost and there is no returning to it. Though this facility used to be common on memory-limited micros and is still widely supported for backward compatibility, the jargon usage is semi-obsolescent; in particular, most Unix programmers will think of this as an {exec}. Oppose the more modern `subshell'. 2. /n./ A series of linked data areas within an operating system or application. `Chain rattling' is the process of repeatedly running through the linked data areas searching for one which is of interest to the executing program. The implication is that there is a very large number of links on the chain.

:channel: /n./ [IRC] The basic unit of discussion on {IRC}. Once one joins a channel, everything one types is read by others on that channel. Channels are named with strings that begin with a `#' sign and can have topic descriptions (which are generally irrelevant to the actual subject of discussion). Some notable channels are `#initgame', `#hottub', and `#report'. At times of international crisis, `#report' has hundreds of members, some of whom take turns listening to various news services and typing in summaries of the news, or in some cases, giving first-hand accounts of the action (e.g., Scud missile attacks in Tel Aviv during the Gulf War in 1991).

:channel hopping: /n./ [IRC, GEnie] To rapidly switch channels on {IRC}, or a GEnie chat board, just as a social butterfly might hop from one group to another at a party. This term may derive from the TV watcher's idiom, `channel surfing'.

:channel op: /chan'l op/ /n./ [IRC] Someone who is endowed with privileges on a particular {IRC} channel; commonly abbreviated `chanop' or `CHOP'. These privileges include the right to {kick} users, to change various status bits, and to make others into CHOPs.

:chanop: /chan'-op/ /n./ [IRC] See {channel op}.

:char: /keir/ or /char/; rarely, /kar/ /n./ Shorthand for `character'. Esp. used by C programmers, as `char' is C's typename for character data.

:charityware: /cha'rit-ee-weir`/ /n./ Syn. {careware}.

:chase pointers: 1. /vi./ To go through multiple levels of indirection, as in traversing a linked list or graph structure. Used esp. by programmers in C, where explicit pointers are a very common data type. This is techspeak, but it remains jargon when used of human networks. "I'm chasing pointers. Bob said you could tell me who to talk to about…." See {dangling pointer} and {snap}. 2. [Cambridge] `pointer chase' or `pointer hunt': The process of going through a {core dump} (sense 1), interactively or on a large piece of paper printed with hex {runes}, following dynamic data-structures. Used only in a debugging context.

:chawmp: /n./ [University of Florida] 16 or 18 bits (half of a machine word). This term was used by FORTH hackers during the late 1970s/early 1980s; it is said to have been archaic then, and may now be obsolete. It was coined in revolt against the promiscuous use of `word' for anything between 16 and 32 bits; `word' has an additional special meaning for FORTH hacks that made the overloading intolerable. For similar reasons, /gaw'bl/ (spelled `gawble' or possibly `gawbul') was in use as a term for 32 or 48 bits (presumably a full machine word, but our sources are unclear on this). These terms are more easily understood if one thinks of them as faithful phonetic spellings of `chomp' and `gobble' pronounced in a Florida or other Southern U.S. dialect. For general discussion of similar terms, see {nybble}.

:check: /n./ A hardware-detected error condition, most commonly used to refer to actual hardware failures rather than software-induced traps. E.g., a `parity check' is the result of a hardware-detected parity error. Recorded here because the word often humorously extended to non-technical problems. For example, the term `child check' has been used to refer to the problems caused by a small child who is curious to know what happens when s/he presses all the cute buttons on a computer's console (of course, this particular problem could have been prevented with {molly-guard}s).

:chemist: /n./ [Cambridge] Someone who wastes computer time on {number-crunching} when you'd far rather the machine were doing something more productive, such as working out anagrams of your name or printing Snoopy calendars or running {life} patterns. May or may not refer to someone who actually studies chemistry.

:Chernobyl chicken: /n./ See {laser chicken}.

:Chernobyl packet: /cher-noh'b*l pak'*t/ /n./ A network packet that induces a {broadcast storm} and/or {network meltdown}, in memory of the April 1986 nuclear accident at Chernobyl in Ukraine. The typical scenario involves an IP Ethernet datagram that passes through a gateway with both source and destination Ether and IP address set as the respective broadcast addresses for the subnetworks being gated between. Compare {Christmas tree packet}.

:chicken head: /n./ [Commodore] The Commodore Business Machines logo, which strongly resembles a poultry part. Rendered in ASCII as `C='. With the arguable exception of the Amiga (see {amoeba}), Commodore's machines are notoriously crocky little {bitty box}es (see also {PETSCII}). Thus, this usage may owe something to Philip K. Dick's novel "Do Androids Dream of Electric Sheep?" (the basis for the movie "Blade Runner"; the novel is now sold under that title), in which a `chickenhead' is a mutant with below-average intelligence.

:chiclet keyboard: /n./ A keyboard with a small, flat rectangular or lozenge-shaped rubber or plastic keys that look like pieces of chewing gum. (Chiclets is the brand name of a variety of chewing gum that does in fact resemble the keys of chiclet keyboards.) Used esp. to describe the original IBM PCjr keyboard. Vendors unanimously liked these because they were cheap, and a lot of early portable and laptop products got launched using them. Customers rejected the idea with almost equal unanimity, and chiclets are not often seen on anything larger than a digital watch any more.

:chine nual: /sheen'yu-*l/ /n. obs./ [MIT] The LISP Machine Manual, so called because the title was wrapped around the cover so only those letters showed on the front.

:Chinese Army technique: /n./ Syn. {Mongolian Hordes technique}.

:choad: /chohd/ /n./ Synonym for `penis' used in alt.tasteless and popularized by the denizens thereof. They say: "We think maybe it's from Middle English but we're all too damned lazy to check the OED." [I'm not. It isn't. —ESR] This term is alleged to have been inherited through 1960s underground comics, and to have been recently sighted in the Beavis and Butthead cartoons. Speakers of the Hindi, Bengali and Gujarati languages have confirmed that `choad' is in fact an Indian vernacular word equivalent to `fuck'; it is therefore likely to have entered English slang via the British Raj.

:choke: /v./ 1. To reject input, often ungracefully. "NULs make System V's `lpr(1)' choke." "I tried building an {EMACS} binary to use {X}, but `cpp(1)' choked on all those `#define's." See {barf}, {gag}, {vi}. 2. [MIT] More generally, to fail at any endeavor, but with some flair or bravado; the popular definition is "to snatch defeat from the jaws of victory."

:chomp: /vi./ To {lose}; specifically, to chew on something of which more was bitten off than one can. Probably related to gnashing of teeth. See {bagbiter}.

A hand gesture commonly accompanies this. To perform it, hold the four fingers together and place the thumb against their tips. Now open and close your hand rapidly to suggest a biting action (much like what Pac-Man does in the classic video game, though this pantomime seems to predate that). The gesture alone means `chomp chomp' (see "{Verb Doubling}" in the "{Jargon Construction}" section of the Prependices). The hand may be pointed at the object of complaint, and for real emphasis you can use both hands at once. Doing this to a person is equivalent to saying "You chomper!" If you point the gesture at yourself, it is a humble but humorous admission of some failure. You might do this if someone told you that a program you had written had failed in some surprising way and you felt dumb for not having anticipated it.

:chomper: /n./ Someone or something that is chomping; a loser. See {loser}, {bagbiter}, {chomp}.

:CHOP: /chop/ /n./ [IRC] See {channel op}.

:Christmas tree: /n./ A kind of RS-232 line tester or breakout box featuring rows of blinking red and green LEDs suggestive of Christmas lights.

:Christmas tree packet: /n./ A packet with every single option set for whatever protocol is in use. See {kamikaze packet}, {Chernobyl packet}. (The term doubtless derives from a fanciful image of each little option bit being represented by a different-colored light bulb, all turned on.)

:chrome: /n./ [from automotive slang via wargaming] Showy features added to attract users but contributing little or nothing to the power of a system. "The 3D icons in Motif are just chrome, but they certainly are *pretty* chrome!" Distinguished from {bells and whistles} by the fact that the latter are usually added to gratify developers' own desires for featurefulness. Often used as a term of contempt.

:chug: /vi./ To run slowly; to {grind} or {grovel}. "The disk is chugging like crazy."

:Church of the SubGenius: /n./ A mutant offshoot of {Discordianism} launched in 1981 as a spoof of fundamentalist Christianity by the `Reverend' Ivan Stang, a brilliant satirist with a gift for promotion. Popular among hackers as a rich source of bizarre imagery and references such as "Bob" the divine drilling-equipment salesman, the Benevolent Space Xists, and the Stark Fist of Removal. Much SubGenius theory is concerned with the acquisition of the mystical substance or quality of {slack}.

:Cinderella Book: [CMU] /n./ "Introduction to Automata Theory, Languages, and Computation", by John Hopcroft and Jeffrey Ullman, (Addison-Wesley, 1979). So called because the cover depicts a girl (putatively Cinderella) sitting in front of a Rube Goldberg device and holding a rope coming out of it. On the back cover, the device is in shambles after she has (inevitably) pulled on the rope. See also {{book titles}}.

:CI$: // /n./ Hackerism for `CIS', CompuServe Information Service. The dollar sign refers to CompuServe's rather steep line charges. Often used in {sig block}s just before a CompuServe address. Syn. {Compu$erve}.

:Classic C: /klas'ik C/ [a play on `Coke Classic'] /n./ The C programming language as defined in the first edition of {K&R}, with some small additions. It is also known as `K&R C'. The name came into use while C was being standardized by the ANSI X3J11 committee. Also `C Classic'.

An analogous construction is sometimes applied elsewhere: thus, `X Classic', where X = Star Trek (referring to the original TV series) or X = PC (referring to IBM's ISA-bus machines as opposed to the PS/2 series). This construction is especially used of product series in which the newer versions are considered serious losers relative to the older ones.

:clean: 1. /adj./ Used of hardware or software designs, implies `elegance in the small', that is, a design or implementation that may not hold any surprises but does things in a way that is reasonably intuitive and relatively easy to comprehend from the outside. The antonym is `grungy' or {crufty}. 2. /v./ To remove unneeded or undesired files in a effort to reduce clutter: "I'm cleaning up my account." "I cleaned up the garbage and now have 100 Meg free on that partition."

:CLM: /C-L-M/ [Sun: `Career Limiting Move'] 1. /n./ An action endangering one's future prospects of getting plum projects and raises, and possibly one's job: "His Halloween costume was a parody of his manager. He won the prize for `best CLM'." 2. adj. Denotes extreme severity of a bug, discovered by a customer and obviously missed earlier because of poor testing: "That's a CLM bug!"

:clobber: /vt./ To overwrite, usually unintentionally: "I walked off the end of the array and clobbered the stack." Compare {mung}, {scribble}, {trash}, and {smash the stack}.

:clocks: /n./ Processor logic cycles, so called because each generally corresponds to one clock pulse in the processor's timing. The relative execution times of instructions on a machine are usually discussed in clocks rather than absolute fractions of a second; one good reason for this is that clock speeds for various models of the machine may increase as technology improves, and it is usually the relative times one is interested in when discussing the instruction set. Compare {cycle}.

:clone: /n./ 1. An exact duplicate: "Our product is a clone of their product." Implies a legal reimplementation from documentation or by reverse-engineering. Also connotes lower price. 2. A shoddy, spurious copy: "Their product is a clone of our product." 3. A blatant ripoff, most likely violating copyright, patent, or trade secret protections: "Your product is a clone of my product." This use implies legal action is pending. 4. `PC clone:' a PC-BUS/ISA or EISA-compatible 80x86-based microcomputer (this use is sometimes spelled `klone' or `PClone'). These invariably have much more bang for the buck than the IBM archetypes they resemble. 5. In the construction `Unix clone': An OS designed to deliver a Unix-lookalike environment without Unix license fees, or with additional `mission-critical' features such as support for real-time programming. 6. /v./ To make an exact copy of something. "Let me clone that" might mean "I want to borrow that paper so I can make a photocopy" or "Let me get a copy of that file before you {mung} it".

:clone-and-hack coding: /n./ [DEC] Syn. {case and paste}.

:clover key: /n./ [Mac users] See {feature key}.

:clustergeeking: /kluh'st*r-gee`king/ /n./ [CMU] Spending more time at a computer cluster doing CS homework than most people spend breathing.

:COBOL: /koh'bol/ /n./ [COmmon Business-Oriented Language] (Synonymous with {evil}.) A weak, verbose, and flabby language used by {card walloper}s to do boring mindless things on {dinosaur} mainframes. Hackers believe that all COBOL programmers are {suit}s or {code grinder}s, and no self-respecting hacker will ever admit to having learned the language. Its very name is seldom uttered without ritual expressions of disgust or horror. One popular one is Edsger W. Dijkstra's famous observation that "The use of COBOL cripples the mind; its teaching should, therefore, be regarded as a criminal offense." (from "Selected Writings on Computing: A Personal Perspective") See also {fear and loathing}, {software rot}.

:COBOL fingers: /koh'bol fing'grz/ /n./ Reported from Sweden, a (hypothetical) disease one might get from coding in COBOL. The language requires code verbose beyond all reason (see {candygrammar}); thus it is alleged that programming too much in COBOL causes one's fingers to wear down to stubs by the endless typing. "I refuse to type in all that source code again; it would give me COBOL fingers!"

:code grinder: /n./ 1. A {suit}-wearing minion of the sort hired in legion strength by banks and insurance companies to implement payroll packages in RPG and other such unspeakable horrors. In its native habitat, the code grinder often removes the suit jacket to reveal an underplumage consisting of button-down shirt (starch optional) and a tie. In times of dire stress, the sleeves (if long) may be rolled up and the tie loosened about half an inch. It seldom helps. The {code grinder}'s milieu is about as far from hackerdom as one can get and still touch a computer; the term connotes pity. See {Real World}, {suit}. 2. Used of or to a hacker, a really serious slur on the person's creative ability; connotes a design style characterized by primitive technique, rule-boundedness, {brute force}, and utter lack of imagination. Compare {card walloper}; contrast {hacker}, {Real Programmer}.

:Code of the Geeks: /n./ see {geek code}.

:code police: /n./ [by analogy with George Orwell's `thought police'] A mythical team of Gestapo-like storm troopers that might burst into one's office and arrest one for violating programming style rules. May be used either seriously, to underline a claim that a particular style violation is dangerous, or ironically, to suggest that the practice under discussion is condemned mainly by anal-retentive {weenie}s. "Dike out that goto or the code police will get you!" The ironic usage is perhaps more common.

:codes: /n./ [scientific computing] Programs. This usage is common in people who hack supercomputers and heavy-duty {number-crunching}, rare to unknown elsewhere (if you say "codes" to hackers outside scientific computing, their first association is likely to be "and cyphers").

:codewalker: /n./ A program component that traverses other programs for a living. Compilers have codewalkers in their front ends; so do cross-reference generators and some database front ends. Other utility programs that try to do too much with source code may turn into codewalkers. As in "This new `vgrind' feature would require a codewalker to implement."

:coefficient of X: /n./ Hackish speech makes heavy use of pseudo-mathematical metaphors. Four particularly important ones involve the terms `coefficient', `factor', `index', and `quotient'. They are often loosely applied to things you cannot really be quantitative about, but there are subtle distinctions among them that convey information about the way the speaker mentally models whatever he or she is describing.

`Foo factor' and `foo quotient' tend to describe something for which the issue is one of presence or absence. The canonical example is {fudge factor}. It's not important how much you're fudging; the term simply acknowledges that some fudging is needed. You might talk of liking a movie for its silliness factor. Quotient tends to imply that the property is a ratio of two opposing factors: "I would have won except for my luck quotient." This could also be "I would have won except for the luck factor", but using *quotient* emphasizes that it was bad luck overpowering good luck (or someone else's good luck overpowering your own).

`Foo index' and `coefficient of foo' both tend to imply that foo is, if not strictly measurable, at least something that can be larger or smaller. Thus, you might refer to a paper or person as having a `high bogosity index', whereas you would be less likely to speak of a `high bogosity factor'. `Foo index' suggests that foo is a condensation of many quantities, as in the mundane cost-of-living index; `coefficient of foo' suggests that foo is a fundamental quantity, as in a coefficient of friction. The choice between these terms is often one of personal preference; e.g., some people might feel that bogosity is a fundamental attribute and thus say `coefficient of bogosity', whereas others might feel it is a combination of factors and thus say `bogosity index'.

:cokebottle: /kohk'bot-l/ /n./ Any very unusual character, particularly one you can't type because it it isn't on your keyboard. MIT people used to complain about the `control-meta-cokebottle' commands at SAIL, and SAIL people complained right back about the `{altmode}-altmode-cokebottle' commands at MIT. After the demise of the {space-cadet keyboard}, `cokebottle' faded away as serious usage, but was often invoked humorously to describe an (unspecified) weird or non-intuitive keystroke command. It may be due for a second inning, however. The OSF/Motif window manager, `mwm(1)', has a reserved keystroke for switching to the default set of keybindings and behavior. This keystroke is (believe it or not) `control-meta-bang' (see {bang}). Since the exclamation point looks a lot like an upside down Coke bottle, Motif hackers have begun referring to this keystroke as `cokebottle'. See also {quadruple bucky}.

:cold boot: /n./ See {boot}.

:COME FROM: /n./ A semi-mythical language construct dual to the `go to'; `COME FROM' <label> would cause the referenced label to act as a sort of trapdoor, so that if the program ever reached it control would quietly and {automagically} be transferred to the statement following the `COME FROM'. `COME FROM' was first proposed in R. Lawrence Clark's "A Linguistic Contribution to GOTO-less programming", which appeared in a 1973 {Datamation} issue (and was reprinted in the April 1984 issue of "Communications of the ACM"). This parodied the then-raging `structured programming' {holy wars} (see {considered harmful}). Mythically, some variants are the `assigned COME FROM' and the `computed COME FROM' (parodying some nasty control constructs in FORTRAN and some extended BASICs). Of course, multi-tasking (or non-determinism) could be implemented by having more than one `COME FROM' statement coming from the same label.

In some ways the FORTRAN `DO' looks like a `COME FROM'
statement. After the terminating statement number/`CONTINUE'
is reached, control continues at the statement following the DO.
Some generous FORTRANs would allow arbitrary statements (other than
`CONTINUE') for the statement, leading to examples like:

DO 10 I=1,LIMIT
C imagine many lines of code here, leaving the
C original DO statement lost in the spaghetti…
WRITE(6,10) I,FROB(I)
10 FORMAT(1X,I5,G10.4)

in which the trapdoor is just after the statement labeled 10. (This is particularly surprising because the label doesn't appear to have anything to do with the flow of control at all!)

While sufficiently astonishing to the unsuspecting reader, this form of `COME FROM' statement isn't completely general. After all, control will eventually pass to the following statement. The implementation of the general form was left to Univac FORTRAN, ca. 1975 (though a roughly similar feature existed on the IBM 7040 ten years earlier). The statement `AT 100' would perform a `COME FROM 100'. It was intended strictly as a debugging aid, with dire consequences promised to anyone so deranged as to use it in production code. More horrible things had already been perpetrated in production languages, however; doubters need only contemplate the `ALTER' verb in {COBOL}.

`COME FROM' was supported under its own name for the first time 15 years later, in C-INTERCAL (see {INTERCAL}, {retrocomputing}); knowledgeable observers are still reeling from the shock.

:comm mode: /kom mohd/ /n./ [ITS: from the feature supporting on-line chat; the term may spelled with one or two m's] Syn. for {talk mode}.

:command key: /n./ [Mac users] Syn. {feature key}.

:comment out: /vt./ To surround a section of code with comment delimiters or to prefix every line in the section with a comment marker; this prevents it from being compiled or interpreted. Often done when the code is redundant or obsolete, but is being left in the source to make the intent of the active code clearer; also when the code in that section is broken and you want to bypass it in order to debug some other part of the code. Compare {condition out}, usually the preferred technique in languages (such as {C}) that make it possible.

:Commonwealth Hackish:: /n./ Hacker jargon as spoken in English outside the U.S., esp. in the British Commonwealth. It is reported that Commonwealth speakers are more likely to pronounce truncations like `char' and `soc', etc., as spelled (/char/, /sok/), as opposed to American /keir/ and /sohsh/. Dots in {newsgroup} names (especially two-component names) tend to be pronounced more often (so soc.wibble is /sok dot wib'l/ rather than /sohsh wib'l/). The prefix {meta} may be pronounced /mee't*/; similarly, Greek letter beta is usually /bee't*/, zeta is usually /zee't*/, and so forth. Preferred {metasyntactic variable}s include {blurgle}, `eek', `ook', `frodo', and `bilbo'; {wibble}, `wobble', and in emergencies `wubble'; `flob', `banana', `tom', `dick', `harry', `wombat', `frog', {fish}, and so on and on (see {foo}, sense 4).

Alternatives to verb doubling include suffixes `-o-rama', `frenzy' (as in feeding frenzy), and `city' (examples: "barf city!" "hack-o-rama!" "core dump frenzy!"). Finally, note that the American terms `parens', `brackets', and `braces' for , , and {} are uncommon; Commonwealth hackish prefers `brackets', `square brackets', and `curly brackets'. Also, the use of `pling' for {bang} is common outside the United States.

See also {attoparsec}, {calculator}, {chemist}, {console jockey}, {fish}, {go-faster stripes}, {grunge}, {hakspek}, {heavy metal}, {leaky heap}, {lord high fixer}, {loose bytes}, {muddie}, {nadger}, {noddy}, {psychedelicware}, {plingnet}, {raster blaster}, {RTBM}, {seggie}, {spod}, {sun lounge}, {terminal junkie}, {tick-list features}, {weeble}, {weasel}, {YABA}, and notes or definitions under {Bad Thing}, {barf}, {bogus}, {bum}, {chase pointers}, {cosmic rays}, {crippleware}, {crunch}, {dodgy}, {gonk}, {hamster}, {hardwarily}, {mess-dos}, {nybble}, {proglet}, {root}, {SEX}, {tweak}, and {xyzzy}.

:compact: /adj./ Of a design, describes the valuable property that it can all be apprehended at once in one's head. This generally means the thing created from the design can be used with greater facility and fewer errors than an equivalent tool that is not compact. Compactness does not imply triviality or lack of power; for example, C is compact and FORTRAN is not, but C is more powerful than FORTRAN. Designs become non-compact through accreting {feature}s and {cruft} that don't merge cleanly into the overall design scheme (thus, some fans of {Classic C} maintain that ANSI C is no longer compact).

:compiler jock: /n./ See {jock} (sense 2).

:compress: [Unix] /vt./ When used without a qualifier, generally refers to {crunch}ing of a file using a particular C implementation of compression by James A. Woods et al. and widely circulated via {Usenet}; use of {crunch} itself in this sense is rare among Unix hackers. Specifically, compress is built around the Lempel-Ziv-Welch algorithm as described in "A Technique for High Performance Data Compression", Terry A. Welch, "IEEE Computer", vol. 17, no. 6 (June 1984), pp. 8—19.

:Compu$erve: /n./ See {CI$}. Synonyms CompuSpend and
Compu$pend are also reported.

:computer confetti: /n./ Syn. {chad}. Though this term is common, this use of punched-card chad is not a good idea, as the pieces are stiff and have sharp corners that could injure the eyes. GLS reports that he once attended a wedding at MIT during which he and a few other guests enthusiastically threw chad instead of rice. The groom later grumbled that he and his bride had spent most of the evening trying to get the stuff out of their hair.

:computer geek: /n./ 1. One who eats (computer) bugs for a living. One who fulfills all the dreariest negative stereotypes about hackers: an asocial, malodorous, pasty-faced monomaniac with all the personality of a cheese grater. Cannot be used by outsiders without implied insult to all hackers; compare black-on-black vs. white-on-black usage of `nigger'. A computer geek may be either a fundamentally clueless individual or a proto-hacker in {larval stage}. Also called `turbo nerd', `turbo geek'. See also {propeller head}, {clustergeeking}, {geek out}, {wannabee}, {terminal junkie}, {spod}, {weenie}. 2. Some self-described computer geeks use this term in a positive sense and protest sense 1 (this seems to have been a post-1990 development). For one such argument, see http://samsara.circus.com/~omni/geek.html.

:computron: /kom'pyoo-tron`/ /n./ 1. A notional unit of computing power combining instruction speed and storage capacity, dimensioned roughly in instructions-per-second times megabytes-of-main-store times megabytes-of-mass-storage. "That machine can't run GNU Emacs, it doesn't have enough computrons!" This usage is usually found in metaphors that treat computing power as a fungible commodity good, like a crop yield or diesel horsepower. See {bitty box}, {Get a real computer!}, {toy}, {crank}. 2. A mythical subatomic particle that bears the unit quantity of computation or information, in much the same way that an electron bears one unit of electric charge (see also {bogon}). An elaborate pseudo-scientific theory of computrons has been developed based on the physical fact that the molecules in a solid object move more rapidly as it is heated. It is argued that an object melts because the molecules have lost their information about where they are supposed to be (that is, they have emitted computrons). This explains why computers get so hot and require air conditioning; they use up computrons. Conversely, it should be possible to cool down an object by placing it in the path of a computron beam. It is believed that this may also explain why machines that work at the factory fail in the computer room: the computrons there have been all used up by the other hardware. (This theory probably owes something to the "Warlock" stories by Larry Niven, the best known being "What Good is a Glass Dagger?", in which magic is fueled by an exhaustible natural resource called `mana'.)

:con: [from SF fandom] /n./ A science-fiction convention. Not used of other sorts of conventions, such as professional meetings. This term, unlike many others of SF-fan slang, is widely recognized even by hackers who aren't {fan}s. "We'd been corresponding on the net for months, then we met face-to-face at a con."

:condition out: /vt./ To prevent a section of code from being compiled by surrounding it with a conditional-compilation directive whose condition is always false. The {canonical} examples of these directives are `#if 0' (or `#ifdef notdef', though some find the latter {bletcherous}) and `#endif' in C. Compare {comment out}.

:condom: /n./ 1. The protective plastic bag that accompanies 3.5-inch microfloppy diskettes. Rarely, also used of (paper) disk envelopes. Unlike the write protect tab, the condom (when left on) not only impedes the practice of {SEX} but has also been shown to have a high failure rate as drive mechanisms attempt to access the disk — and can even fatally frustrate insertion. 2. The protective cladding on a {light pipe}. 3. `keyboard condom': A flexible, transparent plastic cover for a keyboard, designed to provide some protection against dust and {programming fluid} without impeding typing. 4. `elephant condom': the plastic shipping bags used inside cardboard boxes to protect hardware in transit. 5. /n. obs./ A dummy directory `/usr/tmp/sh', created to foil the Great Worm by exploiting a portability bug in one of its parts. So named in the title of a comp.risks article by Gene Spafford during the Worm crisis, and again in the text of "The Internet Worm Program: An Analysis", Purdue Technical Report CSD-TR-823. See {Great Worm, the}.

:confuser: /n./ Common soundalike slang for `computer'. Usually encountered in compounds such as `confuser room', `personal confuser', `confuser guru'. Usage: silly.

:connector conspiracy: /n./ [probably came into prominence with the appearance of the KL-10 (one model of the {PDP-10}), none of whose connectors matched anything else] The tendency of manufacturers (or, by extension, programmers or purveyors of anything) to come up with new products that don't fit together with the old stuff, thereby making you buy either all new stuff or expensive interface devices. The KL-10 Massbus connector was actually *patented* by {DEC}, which reputedly refused to license the design and thus effectively locked third parties out of competition for the lucrative Massbus peripherals market. This policy is a source of never-ending frustration for the diehards who maintain older PDP-10 or VAX systems. Their CPUs work fine, but they are stuck with dying, obsolescent disk and tape drives with low capacity and high power requirements.

(A closely related phenomenon, with a slightly different intent, is the habit manufacturers have of inventing new screw heads so that only Designated Persons, possessing the magic screwdrivers, can remove covers and make repairs or install options. A good 1990s example is the use of Torx screws for cable-TV set-top boxes. Older Apple Macintoshes took this one step further, requiring not only a hex wrench but a specialized case-cracking tool to open the box.)

In these latter days of open-systems computing this term has fallen somewhat into disuse, to be replaced by the observation that "Standards are great! There are so many of them to choose from!" Compare {backward combatability}.

:cons: /konz/ or /kons/ [from LISP] 1. /vt./ To add a new element to a specified list, esp. at the top. "OK, cons picking a replacement for the console TTY onto the agenda." 2. `cons up': /vt./ To synthesize from smaller pieces: "to cons up an example".

In LISP itself, `cons' is the most fundamental operation for building structures. It takes any two objects and returns a `dot-pair' or two-branched tree with one object hanging from each branch. Because the result of a cons is an object, it can be used to build binary trees of any shape and complexity. Hackers think of it as a sort of universal constructor, and that is where the jargon meanings spring from.

:considered harmful: /adj./ Edsger W. Dijkstra's note in the March 1968 "Communications of the ACM", "Goto Statement Considered Harmful", fired the first salvo in the structured programming wars (text at http://www.acm.org/classics). Amusingly, the ACM considered the resulting acrimony sufficiently harmful that it will (by policy) no longer print an article taking so assertive a position against a coding practice. In the ensuing decades, a large number of both serious papers and parodies have borne titles of the form "X considered Y". The structured-programming wars eventually blew over with the realization that both sides were wrong, but use of such titles has remained as a persistent minor in-joke (the `considered silly' found at various places in this lexicon is related).

:console:: /n./ 1. The operator's station of a {mainframe}. In times past, this was a privileged location that conveyed godlike powers to anyone with fingers on its keys. Under Unix and other modern timesharing OSes, such privileges are guarded by passwords instead, and the console is just the {tty} the system was booted from. Some of the mystique remains, however, and it is traditional for sysadmins to post urgent messages to all users from the console (on Unix, /dev/console). 2. On microcomputer Unix boxes, the main screen and keyboard (as opposed to character-only terminals talking to a serial port). Typically only the console can do real graphics or run {X}. See also {CTY}.

:console jockey: /n./ See {terminal junkie}.

:content-free: /adj./ [by analogy with techspeak `context-free'] Used of a message that adds nothing to the recipient's knowledge. Though this adjective is sometimes applied to {flamage}, it more usually connotes derision for communication styles that exalt form over substance or are centered on concerns irrelevant to the subject ostensibly at hand. Perhaps most used with reference to speeches by company presidents and other professional manipulators. "Content-free? Uh… that's anything printed on glossy paper." (See also {four-color glossies}.) "He gave a talk on the implications of electronic networks for postmodernism and the fin-de-siecle aesthetic. It was content-free."

:control-C: /vi./ 1. "Stop whatever you are doing." From the interrupt character used on many operating systems to abort a running program. Considered silly. 2. /interj./ Among BSD Unix hackers, the canonical humorous response to "Give me a break!"

:control-O: /vi./ "Stop talking." From the character used on some operating systems to abort output but allow the program to keep on running. Generally means that you are not interested in hearing anything more from that person, at least on that topic; a standard response to someone who is flaming. Considered silly. Compare {control-S}.

:control-Q: /vi./ "Resume." From the ASCII DC1 or {XON} character (the pronunciation /X-on/ is therefore also used), used to undo a previous {control-S}.

:control-S: /vi./ "Stop talking for a second." From the ASCII DC3 or XOFF character (the pronunciation /X-of/ is therefore also used). Control-S differs from {control-O} in that the person is asked to stop talking (perhaps because you are on the phone) but will be allowed to continue when you're ready to listen to him — as opposed to control-O, which has more of the meaning of "Shut up." Considered silly.

:Conway's Law: /prov./ The rule that the organization of the software and the organization of the software team will be congruent; originally stated as "If you have four groups working on a compiler, you'll get a 4-pass compiler".

The law was named after Melvin Conway, an early proto-hacker who
wrote an assembler for the Burroughs 220 called SAVE. (The name
`SAVE' didn't stand for anything; it was just that you lost fewer
card decks and listings because they all had SAVE written on them.)

There is also Tom Cheatham's amendment of Conway's Law:
"If a group of N persons implements a COBOL compiler, there will be
N-1 passes. Someone in the group has to be the manager."

:cookbook: /n./ [from amateur electronics and radio] A book of small code segments that the reader can use to do various {magic} things in programs. One current example is the "{{PostScript}} Language Tutorial and Cookbook" by Adobe Systems, Inc (Addison-Wesley, ISBN 0-201-10179-3), also known as the {Blue Book} which has recipes for things like wrapping text around arbitrary curves and making 3D fonts. Cookbooks, slavishly followed, can lead one into {voodoo programming}, but are useful for hackers trying to {monkey up} small programs in unknown languages. This function is analogous to the role of phrasebooks in human languages.

:cooked mode: /n./ [Unix, by opposition from {raw mode}] The normal character-input mode, with interrupts enabled and with erase, kill and other special-character interpretations performed directly by the tty driver. Oppose {raw mode}, {rare mode}. This term is techspeak under Unix but jargon elsewhere; other operating systems often have similar mode distinctions, and the raw/rare/cooked way of describing them has spread widely along with the C language and other Unix exports. Most generally, `cooked mode' may refer to any mode of a system that does extensive preprocessing before presenting data to a program.

:cookie: /n./ A handle, transaction ID, or other token of agreement between cooperating programs. "I give him a packet, he gives me back a cookie." The claim check you get from a dry-cleaning shop is a perfect mundane example of a cookie; the only thing it's useful for is to relate a later transaction to this one (so you get the same clothes back). Compare {magic cookie}; see also {fortune cookie}.

:cookie bear: /n. obs./ Original term, pre-Sesame-Street, for what is now universally called a {cookie monster}. A correspondent observes "In those days, hackers were actually getting their yucks from…sit down now…Andy Williams. Yes, *that* Andy Williams. Seems he had a rather hip (by the standards of the day) TV variety show. One of the best parts of the show was the recurring `cookie bear' sketch. In these sketches, a guy in a bear suit tried all sorts of tricks to get a cookie out of Williams. The sketches would always end with Williams shrieking (and I don't mean figuratively), `No cookies! Not now, not ever…NEVER!!!' And the bear would fall down. Great stuff."

:cookie file: /n./ A collection of {fortune cookie}s in a format that facilitates retrieval by a fortune program. There are several different cookie files in public distribution, and site admins often assemble their own from various sources including this lexicon.

:cookie jar: /n./ An area of memory set aside for storing {cookie}s. Most commonly heard in the Atari ST community; many useful ST programs record their presence by storing a distinctive {magic number} in the jar. Programs can inquire after the presence or otherwise of other programs by searching the contents of the jar.

:cookie monster: /n./ [from the children's TV program "Sesame Street"] Any of a family of early (1970s) hacks reported on {{TOPS-10}}, {{ITS}}, {{Multics}}, and elsewhere that would lock up either the victim's terminal (on a time-sharing machine) or the {{console}} (on a batch {mainframe}), repeatedly demanding "I WANT A COOKIE". The required responses ranged in complexity from "COOKIE" through "HAVE A COOKIE" and upward. Folklorist Jan Brunvand (see {FOAF}) has described these programs as urban legends (implying they probably never existed) but they existed, all right, in several different versions. See also {wabbit}. Interestingly, the term `cookie monster' appears to be a {retcon}; the original term was {cookie bear}.

:copious free time: /n./ [Apple; orig. fr. the intro to Tom Lehrer's song "It Makes A Fellow Proud To Be A Soldier"] 1. [used ironically to indicate the speaker's lack of the quantity in question] A mythical schedule slot for accomplishing tasks held to be unlikely or impossible. Sometimes used to indicate that the speaker is interested in accomplishing the task, but believes that the opportunity will not arise. "I'll implement the automatic layout stuff in my copious free time." 2. [Archly] Time reserved for bogus or otherwise idiotic tasks, such as implementation of {chrome}, or the stroking of {suit}s. "I'll get back to him on that feature in my copious free time."

:copper: /n./ Conventional electron-carrying network cable with
a core conductor of copper — or aluminum! Opposed to {light
pipe} or, say, a short-range microwave link.

:copy protection: /n./ A class of methods for preventing
incompetent pirates from stealing software and legitimate customers
from using it. Considered silly.

:copybroke: /kop'ee-brohk/ /adj./ 1. [play on `copyright']
Used to describe an instance of a copy-protected program that has
been `broken'; that is, a copy with the copy-protection scheme
disabled. Syn. {copywronged}. 2. Copy-protected software
which is unusable because of some bit-rot or bug that has confused
the anti-piracy check. See also {copy protection}.

:copyleft: /kop'ee-left/ /n./ [play on `copyright'] 1. The
copyright notice (`General Public License') carried by {GNU}
{EMACS} and other Free Software Foundation software, granting reuse
and reproduction rights to all comers (but see also {General
Public Virus}). 2. By extension, any copyright notice intended to
achieve similar aims.

:copywronged: /kop'ee-rongd/ /adj./ [play on `copyright']
Syn. for {copybroke}.

:core: /n./ Main storage or RAM. Dates from the days of ferrite-core memory; now archaic as techspeak most places outside IBM, but also still used in the Unix community and by old-time hackers or those who would sound like them. Some derived idioms are quite current; `in core', for example, means `in memory' (as opposed to `on disk'), and both {core dump} and the `core image' or `core file' produced by one are terms in favor. Some varieties of Commonwealth hackish prefer {store}.

:core cancer: /n./ A process that exhibits a slow but inexorable resource {leak} — like a cancer, it kills by crowding out productive `tissue'.

:core dump: /n./ [common {Iron Age} jargon, preserved by Unix] 1. [techspeak] A copy of the contents of {core}, produced when a process is aborted by certain kinds of internal error. 2. By extension, used for humans passing out, vomiting, or registering extreme shock. "He dumped core. All over the floor. What a mess." "He heard about X and dumped core." 3. Occasionally used for a human rambling on pointlessly at great length; esp. in apology: "Sorry, I dumped core on you". 4. A recapitulation of knowledge (compare {bits}, sense 1). Hence, spewing all one knows about a topic (syn. {brain dump}), esp. in a lecture or answer to an exam question. "Short, concise answers are better than core dumps" (from the instructions to an exam at Columbia). See {core}.

:core leak: /n./ Syn. {memory leak}.

:Core Wars: /n./ A game between `assembler' programs in a simulated machine, where the objective is to kill your opponent's program by overwriting it. Popularized by A. K. Dewdney's column in "Scientific American" magazine, this was actually devised by Victor Vyssotsky, Robert Morris Sr., and Dennis Ritchie in the early 1960s (their original game was called `Darwin' and ran on a PDP-1 at Bell Labs). See {core}.

:corge: /korj/ /n./ [originally, the name of a cat] Yet another {metasyntactic variable}, invented by Mike Gallaher and propagated by the {GOSMACS} documentation. See {grault}.

:cosmic rays: /n./ Notionally, the cause of {bit rot}. However, this is a semi-independent usage that may be invoked as a humorous way to {handwave} away any minor {randomness} that doesn't seem worth the bother of investigating. "Hey, Eric — I just got a burst of garbage on my {tube}, where did that come from?" "Cosmic rays, I guess." Compare {sunspots}, {phase of the moon}. The British seem to prefer the usage `cosmic showers'; `alpha particles' is also heard, because stray alpha particles passing through a memory chip can cause single-bit errors (this becomes increasingly more likely as memory sizes and densities increase).

Factual note: Alpha particles cause bit rot, cosmic rays do not (except occasionally in spaceborne computers). Intel could not explain random bit drops in their early chips, and one hypothesis was cosmic rays. So they created the World's Largest Lead Safe, using 25 tons of the stuff, and used two identical boards for testing. One was placed in the safe, one outside. The hypothesis was that if cosmic rays were causing the bit drops, they should see a statistically significant difference between the error rates on the two boards. They did not observe such a difference. Further investigation demonstrated conclusively that the bit drops were due to alpha particle emissions from thorium (and to a much lesser degree uranium) in the encapsulation material. Since it is impossible to eliminate these radioactives (they are uniformly distributed through the earth's crust, with the statistically insignificant exception of uranium lodes) it became obvious that one has to design memories to withstand these hits.

:cough and die: /v./ Syn. {barf}. Connotes that the program is throwing its hands up by design rather than because of a bug or oversight. "The parser saw a control-A in its input where it was looking for a printable, so it coughed and died." Compare {die}, {die horribly}, {scream and die}.

:cowboy: /n./ [Sun, from William Gibson's {cyberpunk} SF] Synonym for {hacker}. It is reported that at Sun this word is often said with reverence.

:CP/M:: /C-P-M/ /n./ [Control Program/Monitor; later {retcon}ned to Control Program for Microcomputers] An early microcomputer {OS} written by hacker Gary Kildall for 8080- and Z80-based machines, very popular in the late 1970s but virtually wiped out by MS-DOS after the release of the IBM PC in 1981. Legend has it that Kildall's company blew its chance to write the OS for the IBM PC because Kildall decided to spend a day IBM's reps wanted to meet with him enjoying the perfect flying weather in his private plane. Many of CP/M's features and conventions strongly resemble those of early {DEC} operating systems such as {{TOPS-10}}, OS/8, RSTS, and RSX-11. See {{MS-DOS}}, {operating system}.

:CPU Wars: /C-P-U worz/ /n./ A 1979 large-format comic by Chas Andres chronicling the attempts of the brainwashed androids of IPM (Impossible to Program Machines) to conquer and destroy the peaceful denizens of HEC (Human Engineered Computers). This rather transparent allegory featured many references to {ADVENT} and the immortal line "Eat flaming death, minicomputer mongrels!" (uttered, of course, by an IPM stormtrooper). It is alleged that the author subsequently received a letter of appreciation on IBM company stationery from the head of IBM's Thomas J. Watson Research Laboratories (then, as now, one of the few islands of true hackerdom in the IBM archipelago). The lower loop of the B in the IBM logo, it is said, had been carefully whited out. See {eat flaming death}.

:crack root: /v./ To defeat the security system of a Unix machine and gain {root} privileges thereby; see {cracking}.

:cracker: /n./ One who breaks security on a system. Coined ca. 1985 by hackers in defense against journalistic misuse of {hacker} (q.v., sense 8). An earlier attempt to establish `worm' in this sense around 1981—82 on Usenet was largely a failure.

Use of both these neologisms reflects a strong revulsion against the theft and vandalism perpetrated by cracking rings. While it is expected that any real hacker will have done some playful cracking and knows many of the basic techniques, anyone past {larval stage} is expected to have outgrown the desire to do so except for immediate, benign, practical reasons (for example, if it's necessary to get around some security in order to get some work done).

Thus, there is far less overlap between hackerdom and crackerdom than the {mundane} reader misled by sensationalistic journalism might expect. Crackers tend to gather in small, tight-knit, very secretive groups that have little overlap with the huge, open poly-culture this lexicon describes; though crackers often like to describe *themselves* as hackers, most true hackers consider them a separate and lower form of life.

Ethical considerations aside, hackers figure that anyone who can't imagine a more interesting way to play with their computers than breaking into someone else's has to be pretty {losing}. Some other reasons crackers are looked down on are discussed in the entries on {cracking} and {phreaking}. See also {samurai}, {dark-side hacker}, and {hacker ethic}. For a portrait of the typical teenage cracker, see {warez d00dz}.

:cracking: /n./ The act of breaking into a computer system; what a {cracker} does. Contrary to widespread myth, this does not usually involve some mysterious leap of hackerly brilliance, but rather persistence and the dogged repetition of a handful of fairly well-known tricks that exploit common weaknesses in the security of target systems. Accordingly, most crackers are only mediocre hackers.

:crank: /vt./ [from automotive slang] Verb used to describe the performance of a machine, especially sustained performance. "This box cranks (or, cranks at) about 6 megaflops, with a burst mode of twice that on vectorized operations."

:CrApTeX: /krap'tekh/ /n./ [University of York, England] Term of abuse used to describe TeX and LaTeX when they don't work (when used by TeXhackers), or all the time (by everyone else). The non-TeX-enthusiasts generally dislike it because it is more verbose than other formatters (e.g. {{troff}}) and because (particularly if the standard Computer Modern fonts are used) it generates vast output files. See {religious issues}, {{TeX}}.

:crash: 1. /n./ A sudden, usually drastic failure. Most often said of the {system} (q.v., sense 1), esp. of magnetic disk drives (the term originally described what happens when the air gap of a hard disk collapses). "Three {luser}s lost their files in last night's disk crash." A disk crash that involves the read/write heads dropping onto the surface of the disks and scraping off the oxide may also be referred to as a `head crash', whereas the term `system crash' usually, though not always, implies that the operating system or other software was at fault. 2. /v./ To fail suddenly. "Has the system just crashed?" "Something crashed the OS!" See {down}. Also used transitively to indicate the cause of the crash (usually a person or a program, or both). "Those idiots playing {SPACEWAR} crashed the system." 3. /vi./ Sometimes said of people hitting the sack after a long {hacking run}; see {gronk out}.

:crash and burn: /vi.,n./ A spectacular crash, in the mode of the conclusion of the car-chase scene in the movie "Bullitt" and many subsequent imitators (compare {die horribly}). Sun-3 monitors losing the flyback transformer and lightning strikes on VAX-11/780 backplanes are notable crash and burn generators. The construction `crash-and-burn machine' is reported for a computer used exclusively for alpha or {beta} testing, or reproducing bugs (i.e., not for development). The implication is that it wouldn't be such a disaster if that machine crashed, since only the testers would be inconvenienced.

:crawling horror: /n./ Ancient crufty hardware or software that is kept obstinately alive by forces beyond the control of the hackers at a site. Like {dusty deck} or {gonkulator}, but connotes that the thing described is not just an irritation but an active menace to health and sanity. "Mostly we code new stuff in C, but they pay us to maintain one big FORTRAN II application from nineteen-sixty-X that's a real crawling horror…." Compare {WOMBAT}.

:cray: /kray/ /n./ 1. (properly, capitalized) One of the line of supercomputers designed by Cray Research. 2. Any supercomputer at all. 3. The {canonical} {number-crunching} machine.

The term is actually the lowercased last name of Seymour Cray, a noted computer architect and co-founder of the company. Numerous vivid legends surround him, some true and some admittedly invented by Cray Research brass to shape their corporate culture and image.

:cray instability: /n./ 1. A shortcoming of a program or algorithm that manifests itself only when a large problem is being run on a powerful machine (see {cray}). Generally more subtle than bugs that can be detected in smaller problems running on a workstation or mini. 2. More specifically, a shortcoming of algorithms which are well behaved when run on gentle floating point hardware (such as IEEE-standard or DEC) but which break down badly when exposed to a Cray's unique `rounding' rules.

:crayola: /kray-oh'l*/ /n./ A super-mini or -micro computer that provides some reasonable percentage of supercomputer performance for an unreasonably low price. Might also be a {killer micro}.

:crayola books: /n./ The {rainbow series} of National Computer Security Center (NCSC) computer security standards (see {Orange Book}). Usage: humorous and/or disparaging.

:crayon: /n./ 1. Someone who works on Cray supercomputers.
More specifically, it implies a programmer, probably of the CDC
ilk, probably male, and almost certainly wearing a tie
(irrespective of gender). Systems types who have a Unix background
tend not to be described as crayons. 2. A {computron} (sense 2)
that participates only in {number-crunching}. 3. A unit of
computational power equal to that of a single Cray-1. There is a
standard joke about this usage that derives from an old Crayola
crayon promotional gimmick: When you buy 64 crayons you get a free
sharpener.

:creationism: /n./ The (false) belief that large, innovative
software designs can be completely specified in advance and then
painlessly magicked out of the void by the normal efforts of a team
of normally talented programmers. In fact, experience has shown
repeatedly that good designs arise only from evolutionary,
exploratory interaction between one (or at most a small handful of)
exceptionally able designer(s) and an active user population —-
and that the first try at a big new idea is always wrong.
Unfortunately, because these truths don't fit the planning models
beloved of {management}, they are generally ignored.

:creep: /v./ To advance, grow, or multiply inexorably. In hackish usage this verb has overtones of menace and silliness, evoking the creeping horrors of low-budget monster movies.

:creeping elegance: /n./ Describes a tendency for parts of a design to become {elegant} past the point of diminishing return, something which often happens at the expense of the less interesting parts of the design, the schedule, and other things deemed important in the {Real World}. See also {creeping featurism}, {second-system effect}, {tense}.

:creeping featurism: /kree'ping fee'chr-izm/ /n./ 1. Describes a systematic tendency to load more {chrome} and {feature}s onto systems at the expense of whatever elegance they may have possessed when originally designed. See also {feeping creaturism}. "You know, the main problem with {BSD} Unix has always been creeping featurism." 2. More generally, the tendency for anything complicated to become even more complicated because people keep saying "Gee, it would be even better if it had this feature too". (See {feature}.) The result is usually a patchwork because it grew one ad-hoc step at a time, rather than being planned. Planning is a lot of work, but it's easy to add just one extra little feature to help someone … and then another … and another…. When creeping featurism gets out of hand, it's like a cancer. Usually this term is used to describe computer programs, but it could also be said of the federal government, the IRS 1040 form, and new cars. A similar phenomenon sometimes afflicts conscious redesigns; see {second-system effect}. See also {creeping elegance}.

:creeping featuritis: /kree'ping fee'-chr-i:`t*s/ /n./ Variant of {creeping featurism}, with its own spoonerization: `feeping creaturitis'. Some people like to reserve this form for the disease as it actually manifests in software or hardware, as opposed to the lurking general tendency in designers' minds. (After all, -ism means `condition' or `pursuit of', whereas -itis usually means `inflammation of'.)

:cretin: /kret'in/ or /kree'tn/ /n./ Congenital {loser}; an obnoxious person; someone who can't do anything right. It has been observed that many American hackers tend to favor the British pronunciation /kret'in/ over standard American /kree'tn/; it is thought this may be due to the insidious phonetic influence of Monty Python's Flying Circus.

:cretinous: /kret'n-*s/ or /kreet'n-*s/ /adj./ Wrong; stupid; non-functional; very poorly designed. Also used pejoratively of people. See {dread high-bit disease} for an example. Approximate synonyms: {bletcherous}, {bagbiting} {losing}, {brain-damaged}.

:crippleware: /n./ 1. Software that has some important functionality deliberately removed, so as to entice potential users to pay for a working version. 2. [Cambridge] Variety of {guiltware} that exhorts you to donate to some charity (compare {careware}, {nagware}). 3. Hardware deliberately crippled, which can be upgraded to a more expensive model by a trivial change (e.g., cutting a jumper).

An excellent example of crippleware (sense 3) is Intel's 486SX chip, which is a standard 486DX chip with the co-processor dyked out (in some early versions it was present but disabled). To upgrade, you buy a complete 486DX chip with *working* co-processor (its identity thinly veiled by a different pinout) and plug it into the board's expansion socket. It then disables the SX, which becomes a fancy power sink. Don't you love Intel?

:critical mass: /n./ In physics, the minimum amount of fissionable material required to sustain a chain reaction. Of a software product, describes a condition of the software such that fixing one bug introduces one plus {epsilon} bugs. (This malady has many causes: {creeping featurism}, ports to too many disparate environments, poor initial design, etc.) When software achieves critical mass, it can never be fixed; it can only be discarded and rewritten.

:crlf: /ker'l*f/, sometimes /kru'l*f/ or /C-R-L-F/ /n./ (often capitalized as `CRLF') A carriage return (CR, ASCII 0001101) followed by a line feed (LF, ASCII 0001010). More loosely, whatever it takes to get you from the end of one line of text to the beginning of the next line. See {newline}, {terpri}. Under {{Unix}} influence this usage has become less common (Unix uses a bare line feed as its `CRLF').

:crock: /n./ [from the American scatologism `crock of shit'] 1. An awkward feature or programming technique that ought to be made cleaner. For example, using small integers to represent error codes without the program interpreting them to the user (as in, for example, Unix `make(1)', which returns code 139 for a process that dies due to {segfault}). 2. A technique that works acceptably, but which is quite prone to failure if disturbed in the least. For example, a too-clever programmer might write an assembler which mapped instruction mnemonics to numeric opcodes algorithmically, a trick which depends far too intimately on the particular bit patterns of the opcodes. (For another example of programming with a dependence on actual opcode values, see {The Story of Mel, a Real Programmer} in Appendix A.) Many crocks have a tightly woven, almost completely unmodifiable structure. See {kluge}, {brittle}. The adjectives `crockish' and `crocky', and the nouns `crockishness' and `crockitude', are also used.

:cross-post: [Usenet] /vi./ To post a single article simultaneously to several newsgroups. Distinguished from posting the article repeatedly, once to each newsgroup, which causes people to see it multiple times (which is very bad form). Gratuitous cross-posting without a Followup-To line directing responses to a single followup group is frowned upon, as it tends to cause {followup} articles to go to inappropriate newsgroups when people respond to only one part of the original posting.

:crudware: /kruhd'weir/ /n./ Pejorative term for the hundreds of megabytes of low-quality {freeware} circulated by user's groups and BBS systems in the micro-hobbyist world. "Yet *another* set of disk catalog utilities for {{MS-DOS}}? What crudware!"

:cruft: /kruhft/ [back-formation from {crufty}] 1. /n./ An unpleasant substance. The dust that gathers under your bed is cruft; the TMRC Dictionary correctly noted that attacking it with a broom only produces more. 2. /n./ The results of shoddy construction. 3. /vt./ [from `hand cruft', pun on `hand craft'] To write assembler code for something normally (and better) done by a compiler (see {hand-hacking}). 4. /n./ Excess; superfluous junk; used esp. of redundant or superseded code. 5. [University of Wisconsin] /n./ Cruft is to hackers as gaggle is to geese; that is, at UW one properly says "a cruft of hackers".

:cruft together: /vt./ (also `cruft up') To throw together something ugly but temporarily workable. Like /vt./ {kluge up}, but more pejorative. "There isn't any program now to reverse all the lines of a file, but I can probably cruft one together in about 10 minutes." See {hack together}, {hack up}, {kluge up}, {crufty}.

:cruftsmanship: /kruhfts'm*n-ship / /n./ [from {cruft}] The antithesis of craftsmanship.

:crufty: /kruhf'tee/ /adj./ [origin unknown; poss. from `crusty' or `cruddy'] 1. Poorly built, possibly over-complex. The {canonical} example is "This is standard old crufty {DEC} software". In fact, one fanciful theory of the origin of `crufty' holds that was originally a mutation of `crusty' applied to DEC software so old that the `s' characters were tall and skinny, looking more like `f' characters. 2. Unpleasant, especially to the touch, often with encrusted junk. Like spilled coffee smeared with peanut butter and catsup. 3. Generally unpleasant. 4. (sometimes spelled `cruftie') /n./ A small crufty object (see {frob}); often one that doesn't fit well into the scheme of things. "A LISP property list is a good place to store crufties (or, collectively, {random} cruft)."

This term is one of the oldest in the jargon and no one is sure of its etymology, but it is suggestive that there is a Cruft Hall at Harvard University which is part of the old physics building; it's said to have been the physics department's radar lab during WWII. To this day (early 1993) the windows appear to be full of random techno-junk. MIT or Lincoln Labs people may well have coined the term as a knock on the competition.

:crumb: /n./ Two binary digits; a {quad}. Larger than a {bit}, smaller than a {nybble}. Considered silly. Syn. {tayste}. General discussion of such terms is under {nybble}.

:crunch: 1. /vi./ To process, usually in a time-consuming or complicated way. Connotes an essentially trivial operation that is nonetheless painful to perform. The pain may be due to the triviality's being embedded in a loop from 1 to 1,000,000,000. "FORTRAN programs do mostly {number-crunching}." 2. /vt./ To reduce the size of a file by a complicated scheme that produces bit configurations completely unrelated to the original data, such as by a Huffman code. (The file ends up looking something like a paper document would if somebody crunched the paper into a wad.) Since such compression usually takes more computations than simpler methods such as run-length encoding, the term is doubly appropriate. (This meaning is usually used in the construction `file crunch(ing)' to distinguish it from {number-crunching}.) See {compress}. 3. /n./ The character `#'. Used at XEROX and CMU, among other places. See {{ASCII}}. 4. /vt./ To squeeze program source into a minimum-size representation that will still compile or execute. The term came into being specifically for a famous program on the BBC micro that crunched BASIC source in order to make it run more quickly (it was a wholly interpretive BASIC, so the number of characters mattered). {Obfuscated C Contest} entries are often crunched; see the first example under that entry.

:cruncha cruncha cruncha: /kruhn'ch* kruhn'ch* kruhn'ch*/ /interj./ An encouragement sometimes muttered to a machine bogged down in a serious {grovel}. Also describes a notional sound made by groveling hardware. See {wugga wugga}, {grind} (sense 3).

:cryppie: /krip'ee/ /n./ A cryptographer. One who hacks or implements cryptographic software or hardware.

:CTSS: /C-T-S-S/ /n./ Compatible Time-Sharing System. An early (1963) experiment in the design of interactive time-sharing operating systems, ancestral to {{Multics}}, {{Unix}}, and {{ITS}}. The name {{ITS}} (Incompatible Time-sharing System) was a hack on CTSS, meant both as a joke and to express some basic differences in philosophy about the way I/O services should be presented to user programs.

:CTY: /sit'ee/ or /C-T-Y/ /n./ [MIT] The terminal physically associated with a computer's system {{console}}. The term is a contraction of `Console {tty}', that is, `Console TeleTYpe'. This {{ITS}}- and {{TOPS-10}}-associated term has become less common, as most Unix hackers simply refer to the CTY as `the console'.

:cube: /n./ 1. [short for `cubicle'] A module in the open-plan offices used at many programming shops. "I've got the manuals in my cube." 2. A NeXT machine (which resembles a matte-black cube).

:cubing: /vi./ [parallel with `tubing'] 1. Hacking on an IPSC (Intel Personal SuperComputer) hypercube. "Louella's gone cubing *again*!!" 2. Hacking Rubik's Cube or related puzzles, either physically or mathematically. 3. An indescribable form of self-torture (see sense 1 or 2).

:cursor dipped in X: /n./ There are a couple of metaphors in
English of the form `pen dipped in X' (perhaps the most common
values of X are `acid', `bile', and `vitriol'). These map
over neatly to this hackish usage (the cursor being what moves,
leaving letters behind, when one is composing on-line). "Talk
about a {nastygram}! He must've had his cursor dipped in acid
when he wrote that one!"

:cuspy: /kuhs'pee/ /adj./ [WPI: from the {DEC}
abbreviation CUSP, for `Commonly Used System Program', i.e., a
utility program used by many people] 1. (of a program)
Well-written. 2. Functionally excellent. A program that performs
well and interfaces well to users is cuspy. See {rude}.
3. [NYU] Said of an attractive woman, especially one regarded as
available. Implies a certain curvaceousness.

:cut a tape: /vi./ To write a software or document distribution
on magnetic tape for shipment. Has nothing to do with physically
cutting the medium! Early versions of this lexicon claimed that
one never analogously speaks of `cutting a disk', but this has
since been reported as live usage. Related slang usages are
mainstream business's `cut a check', the recording industry's
`cut a record', and the military's `cut an order'.

All of these usages reflect physical processes in obsolete recording and duplication technologies. The first stage in manufacturing an old-style vinyl record involved cutting grooves in a stamping die with a precision lathe. More mundanely, the dominant technology for mass duplication of paper documents in pre-photocopying days involved "cutting a stencil", punching away portions of the wax overlay on a silk screen. More directly, paper tape with holes punched in it was an important early storage medium.

:cybercrud: /si:'ber-kruhd/ /n./ 1. [coined by Ted Nelson] Obfuscatory tech-talk. Verbiage with a high {MEGO} factor. The computer equivalent of bureaucratese. 2. Incomprehensible stuff embedded in email. First there were the "Received" headers that show how mail flows through systems, then MIME (Multi-purpose Internet Mail Extensions) headers and part boundaries, and now huge blocks of hex for PEM (Privacy Enhanced Mail) or PGP (Pretty Good Privacy) digital signatures and certificates of authenticity. This stuff all services a purpose and good user interfaces should hide it, but all too often users are forced to wade through it.

:cyberpunk: /si:'ber-puhnk/ /n.,adj./ [orig. by SF writer Bruce Bethke and/or editor Gardner Dozois] A subgenre of SF launched in 1982 by William Gibson's epoch-making novel "Neuromancer" (though its roots go back through Vernor Vinge's "True Names" (see the {Bibliography} in Appendix C) to John Brunner's 1975 novel "The Shockwave Rider"). Gibson's near-total ignorance of computers and the present-day hacker culture enabled him to speculate about the role of computers and hackers in the future in ways hackers have since found both irritatingly na"ive and tremendously stimulating. Gibson's work was widely imitated, in particular by the short-lived but innovative "Max Headroom" TV series. See {cyberspace}, {ice}, {jack in}, {go flatline}.

Since 1990 or so, popular culture has included a movement or fashion trend that calls itself `cyberpunk', associated especially with the rave/techno subculture. Hackers have mixed feelings about this. On the one hand, self-described cyberpunks too often seem to be shallow trendoids in black leather who have substituted enthusiastic blathering about technology for actually learning and *doing* it. Attitude is no substitute for competence. On the other hand, at least cyberpunks are excited about the right things and properly respectful of hacking talent in those who have it. The general consensus is to tolerate them politely in hopes that they'll attract people who grow into being true hackers.

:cyberspace: /si:'br-spays`/ /n./ 1. Notional `information-space' loaded with visual cues and navigable with brain-computer interfaces called `cyberspace decks'; a characteristic prop of {cyberpunk} SF. Serious efforts to construct {virtual reality} interfaces modeled explicitly on Gibsonian cyberspace are under way, using more conventional devices such as glove sensors and binocular TV headsets. Few hackers are prepared to deny outright the possibility of a cyberspace someday evolving out of the network (see {network, the}). 2. The Internet or {Matrix} (sense #2) as a whole, considered as a crude cyberspace (sense 1). Although this usage became widely popular in the mainstream press during 1994 when the Internet exploded into public awareness, it is strongly deprecated among hackers because the Internet does not meet the high, SF-inspired standards they have for true cyberspace technology. Thus, this use of the term usually tags a {wannabee} or outsider. 3. Occasionally, the metaphoric location of the mind of a person in {hack mode}. Some hackers report experiencing strong eidetic imagery when in hack mode; interestingly, independent reports from multiple sources suggest that there are common features to the experience. In particular, the dominant colors of this subjective `cyberspace' are often gray and silver, and the imagery often involves constellations of marching dots, elaborate shifting patterns of lines and angles, or moire patterns.

:cycle: 1. /n./ The basic unit of computation. What every hacker wants more of (noted hacker Bill Gosper describes himself as a "cycle junkie"). One can describe an instruction as taking so many `clock cycles'. Often the computer can access its memory once on every clock cycle, and so one speaks also of `memory cycles'. These are technical meanings of {cycle}. The jargon meaning comes from the observation that there are only so many cycles per second, and when you are sharing a computer the cycles get divided up among the users. The more cycles the computer spends working on your program rather than someone else's, the faster your program will run. That's why every hacker wants more cycles: so he can spend less time waiting for the computer to respond. 2. By extension, a notional unit of *human* thought power, emphasizing that lots of things compete for the typical hacker's think time. "I refused to get involved with the Rubik's Cube back when it was big. Knew I'd burn too many cycles on it if I let myself." 3. /vt./ Syn. {bounce} (sense 4), {120 reset}; from the phrase `cycle power'. "Cycle the machine again, that serial port's still hung."

:cycle crunch: /n./ A situation wherein the number of people trying to use a computer simultaneously has reached the point where no one can get enough cycles because they are spread too thin and the system has probably begun to {thrash}. This scenario is an inevitable result of Parkinson's Law applied to timesharing. Usually the only solution is to buy more computer. Happily, this has rapidly become easier since the mid-1980s, so much so that the very term `cycle crunch' now has a faintly archaic flavor; most hackers now use workstations or personal computers as opposed to traditional timesharing systems.

:cycle drought: /n./ A scarcity of cycles. It may be due to a {cycle crunch}, but it could also occur because part of the computer is temporarily not working, leaving fewer cycles to go around. "The {high moby} is {down}, so we're running with only half the usual amount of memory. There will be a cycle drought until it's fixed."

:cycle of reincarnation: /n./ [coined in a paper by T. H. Myer and I.E. Sutherland "On the Design of Display Processors", Comm. ACM, Vol. 11, no. 6, June 1968)] Term used to refer to a well-known effect whereby function in a computing system family is migrated out to special-purpose peripheral hardware for speed, then the peripheral evolves toward more computing power as it does its job, then somebody notices that it is inefficient to support two asymmetrical processors in the architecture and folds the function back into the main CPU, at which point the cycle begins again.

Several iterations of this cycle have been observed in graphics-processor design, and at least one or two in communications and floating-point processors. Also known as `the Wheel of Life', `the Wheel of Samsara', and other variations of the basic Hindu/Buddhist theological idea. See also {blitter}, {bit bang}.

:cycle server: /n./ A powerful machine that exists primarily for running large compute-, disk-, or memory-intensive jobs. Implies that interactive tasks such as editing are done on other machines on the network, such as workstations.

:cypherpunk: /n./ [from {cyberpunk}] Someone interested in the uses of encryption via electronic ciphers for enhancing personal privacy and guarding against tyranny by centralized, authoritarian power structures, especially government. There is an active cypherpunks mailing list at cypherpunks-request@toad.com coordinating work on public-key encryption freeware, privacy, and digital cash. See also {tentacle}.

= D = =====

:D. C. Power Lab: /n./ The former site of {{SAIL}}. Hackers thought this was very funny because the obvious connection to electrical engineering was nonexistent — the lab was named for a Donald C. Power. Compare {Marginal Hacks}.

:daemon: /day'mn/ or /dee'mn/ /n./ [from the mythological meaning, later rationalized as the acronym `Disk And Execution MONitor'] A program that is not invoked explicitly, but lies dormant waiting for some condition(s) to occur. The idea is that the perpetrator of the condition need not be aware that a daemon is lurking (though often a program will commit an action only because it knows that it will implicitly invoke a daemon). For example, under {{ITS}} writing a file on the {LPT} spooler's directory would invoke the spooling daemon, which would then print the file. The advantage is that programs wanting (in this example) files printed need neither compete for access to nor understand any idiosyncrasies of the {LPT}. They simply enter their implicit requests and let the daemon decide what to do with them. Daemons are usually spawned automatically by the system, and may either live forever or be regenerated at intervals.

Daemon and {demon} are often used interchangeably, but seem to have distinct connotations. The term `daemon' was introduced to computing by {CTSS} people (who pronounced it /dee'mon/) and used it to refer to what ITS called a {dragon}. Although the meaning and the pronunciation have drifted, we think this glossary reflects current (1996) usage.

:daemon book: /n./ "The Design and Implementation of the 4.3BSD UNIX Operating System", by Samuel J. Leffler, Marshall Kirk McKusick, Michael J. Karels, and John S. Quarterman (Addison-Wesley Publishers, 1989, ISBN 0-201-06196-1) — the standard reference book on the internals of {BSD} Unix. So called because the cover has a picture depicting a little devil (a visual play on {daemon}) in sneakers, holding a pitchfork (referring to one of the characteristic features of Unix, the `fork(2)' system call). Also known as the {Devil Book}.

:dahmum: /dah'mum/ /n./ [Usenet] The material of which
protracted {flame war}s, especially those about operating
systems, is composed. Homeomorphic to {spam}. The term
`dahmum' is derived from the name of a militant {OS/2}
advocate, and originated when an extensively crossposted
OS/2-versus-{Linux} debate was fed through {Dissociated
Press}.

:dangling pointer: /n./ A reference that doesn't actually lead
anywhere (in C and some other languages, a pointer that doesn't
actually point at anything valid). Usually this happens because it
formerly pointed to something that has moved or disappeared. Used
as jargon in a generalization of its techspeak meaning; for
example, a local phone number for a person who has since moved to
the other coast is a dangling pointer. Compare {dead link}.

:dark-side hacker: /n./ A criminal or malicious hacker; a {cracker}. From George Lucas's Darth Vader, "seduced by the dark side of the Force". The implication that hackers form a sort of elite of technological Jedi Knights is intended. Oppose {samurai}.

:Datamation: /day`t*-may'sh*n/ /n./ A magazine that many hackers assume all {suit}s read. Used to question an unbelieved quote, as in "Did you read that in `Datamation?'" (But see below; this slur may be dated by the time you read this.) It used to publish something hackishly funny every once in a while, like the original paper on {COME FROM} in 1973, and Ed Post's "Real Programmers Don't Use Pascal" ten years later, but for a long time after that it was much more exclusively {suit}-oriented and boring. Following a change of editorship in 1994, Datamation is trying for more of the technical content and irreverent humor that marked its early days.

Datamation now has a WWW page at http://www.datamation.com
worth visiting for its selection of computer humor, including
"Real Programmers Don't Use Pascal" and the `Bastard Operator
From Hell' stories by Simon Travaglia (see {BOFH}).

:DAU: /dow/ [German FidoNet] /n./ German acronym for D"ummster Anzunehmender User (stupidest imaginable user). From the engineering-slang GAU for Gr"osster Anzunehmender Unfall, worst assumable accident, esp. of a LNG tank farm plant or something with similarly disastrous consequences. In popular German, GAU is used only to refer to worst-case nuclear acidents such as a core meltdown. See {cretin}, {fool}, {loser} and {weasel}.

:day mode: /n./ See {phase} (sense 1). Used of people only.

:dd: /dee-dee/ /vt./ [Unix: from IBM {JCL}] Equivalent to {cat} or {BLT}. Originally the name of a Unix copy command with special options suitable for block-oriented devices; it was often used in heavy-handed system maintenance, as in "Let's `dd' the root partition onto a tape, then use the boot PROM to load it back on to a new disk". The Unix `dd(1)' was designed with a weird, distinctly non-Unixy keyword option syntax reminiscent of IBM System/360 JCL (which had an elaborate DD `Dataset Definition' specification for I/O devices); though the command filled a need, the interface design was clearly a prank. The jargon usage is now very rare outside Unix sites and now nearly obsolete even there, as `dd(1)' has been {deprecated} for a long time (though it has no exact replacement). The term has been displaced by {BLT} or simple English `copy'.

:DDT: /D-D-T/ /n./ 1. Generic term for a program that assists in debugging other programs by showing individual machine instructions in a readable symbolic form and letting the user change them. In this sense the term DDT is now archaic, having been widely displaced by `debugger' or names of individual programs like `adb', `sdb', `dbx', or `gdb'. 2. [ITS] Under MIT's fabled {{ITS}} operating system, DDT (running under the alias HACTRN, a six-letterism for `Hack Translator') was also used as the {shell} or top level command language used to execute other programs. 3. Any one of several specific DDTs (sense 1) supported on early {DEC} hardware. The DEC PDP-10 Reference Handbook (1969) contained a footnote on the first page of the documentation for DDT that illuminates the origin of the term:

Historical footnote: DDT was developed at MIT for the PDP-1 computer in 1961. At that time DDT stood for "DEC Debugging Tape". Since then, the idea of an on-line debugging program has propagated throughout the computer industry. DDT programs are now available for all DEC computers. Since media other than tape are now frequently used, the more descriptive name "Dynamic Debugging Technique" has been adopted, retaining the DDT abbreviation. Confusion between DDT-10 and another well known pesticide, dichloro-diphenyl-trichloroethane (C14-H9-Cl5) should be minimal since each attacks a different, and apparently mutually exclusive, class of bugs.

(The `tape' referred to was, incidentally, not magnetic but paper.) Sadly, this quotation was removed from later editions of the handbook after the {suit}s took over and DEC became much more `businesslike'.

The history above is known to many old-time hackers. But there's more: Peter Samson, compiler of the original {TMRC} lexicon, reports that he named `DDT' after a similar tool on the TX-0 computer, the direct ancestor of the PDP-1 built at MIT's Lincoln Lab in 1957. The debugger on that ground-breaking machine (the first transistorized computer) rejoiced in the name FLIT (FLexowriter Interrogation Tape).

:de-rezz: /dee-rez'/ [from `de-resolve' via the movie
"Tron"] (also `derez') 1. /vi./ To disappear or dissolve; the
image that goes with it is of an object breaking up into raster
lines and static and then dissolving. Occasionally used of a
person who seems to have suddenly `fuzzed out' mentally rather than
physically. Usage: extremely silly, also rare. This verb was
actually invented as *fictional* hacker jargon, and adopted in
a spirit of irony by real hackers years after the fact. 2. /vt./
The
Macintosh resource decompiler. On a Macintosh, many program
structures (including the code itself) are managed in small
segments of the program file known as `resources'; `Rez' and
`DeRez' are a pair of utilities for compiling and decompiling
resource files. Thus, decompiling a resource is `derezzing'.
Usage: very common.

:dead: /adj./ 1. Non-functional; {down}; {crash}ed. Especially used of hardware. 2. At XEROX PARC, software that is working but not undergoing continued development and support. 3. Useless; inaccessible. Antonym: `live'. Compare {dead code}.

:dead code: /n./ Routines that can never be accessed because all calls to them have been removed, or code that cannot be reached because it is guarded by a control structure that provably must always transfer control somewhere else. The presence of dead code may reveal either logical errors due to alterations in the program or significant changes in the assumptions and environment of the program (see also {software rot}); a good compiler should report dead code so a maintainer can think about what it means. (Sometimes it simply means that an *extremely* defensive programmer has inserted {can't happen} tests which really can't happen — yet.) Syn. {grunge}. See also {dead}, and {The Story of Mel, a Real Programmer}.

:dead link: /n./ [WWW] A World-Wide-Web URL that no longer points to the information it was written to reach. Usually this happens because the document has been moved or deleted. Lots of dead links make a WWW page frustrating and useless and are the #1 sign of poor page maintainance. Compare {dangling pointer}.

:DEADBEEF: /ded-beef/ /n./ The hexadecimal word-fill pattern for freshly allocated memory (decimal -21524111) under a number of IBM environments, including the RS/6000. Some modern debugging tools deliberately fill freed memory with this value as a way of converting {heisenbug}s into {Bohr bug}s. As in "Your program is DEADBEEF" (meaning gone, aborted, flushed from memory); if you start from an odd half-word boundary, of course, you have BEEFDEAD. See also the anecdote under {fool}.

:deadlock: /n./ 1. [techspeak] A situation wherein two or more processes are unable to proceed because each is waiting for one of the others to do something. A common example is a program communicating to a server, which may find itself waiting for output from the server before sending anything more to it, while the server is similarly waiting for more input from the controlling program before outputting anything. (It is reported that this particular flavor of deadlock is sometimes called a `starvation deadlock', though the term `starvation' is more properly used for situations where a program can never run simply because it never gets high enough priority. Another common flavor is `constipation', in which each process is trying to send stuff to the other but all buffers are full because nobody is reading anything.) See {deadly embrace}. 2. Also used of deadlock-like interactions between humans, as when two people meet in a narrow corridor, and each tries to be polite by moving aside to let the other pass, but they end up swaying from side to side without making any progress because they always move the same way at the same time.

:deadly embrace: /n./ Same as {deadlock}, though usually used only when exactly two processes are involved. This is the more popular term in Europe, while {deadlock} predominates in the United States.

:death code: /n./ A routine whose job is to set everything in the computer — registers, memory, flags, everything — to zero, including that portion of memory where it is running; its last act is to stomp on its own "store zero" instruction. Death code isn't very useful, but writing it is an interesting hacking challenge on architectures where the instruction set makes it possible, such as the PDP-8 (it has also been done on the DG Nova).

Perhaps the ultimate death code is on the TI 990 series, where all registers are actually in RAM, and the instruction "store immediate 0" has the opcode "0". The PC will immediately wrap around core as many times as it can until a user hits HALT. Any empty memory location is death code. Worse, the manufacturer recommended use of this instruction in startup code (which would be in ROM and therefore survive).

:Death Square: /n./ The corporate logo of Novell, the people who acquired USL after AT&T let go of it (Novell eventually sold the Unix group to SCO). Coined by analogy with {Death Star}, because many people believed Novell was bungling the lead in Unix systems exactly as AT&T did for many years.

:Death Star: /n./ [from the movie "Star Wars"] 1. The AT&T corporate logo, which appears on computers sold by AT&T and bears an uncanny resemblance to the Death Star in the movie. This usage is particularly common among partisans of {BSD} Unix, who tend to regard the AT&T versions as inferior and AT&T as a bad guy. Copies still circulate of a poster printed by Mt. Xinu showing a starscape with a space fighter labeled 4.2 BSD streaking away from a broken AT&T logo wreathed in flames. 2. AT&T's internal magazine, "Focus", uses `death star' to describe an incorrectly done AT&T logo in which the inner circle in the top left is dark instead of light — a frequent result of dark-on-light logo images.

:DEC:: /dek/ /n./ Commonly used abbreviation for Digital Equipment Corporation, now deprecated by DEC itself in favor of "Digital". Before the {killer micro} revolution of the late 1980s, hackerdom was closely symbiotic with DEC's pioneering timesharing machines. The first of the group of cultures described by this lexicon nucleated around the PDP-1 (see {TMRC}). Subsequently, the PDP-6, {PDP-10}, {PDP-20}, PDP-11 and {VAX} were all foci of large and important hackerdoms, and DEC machines long dominated the ARPANET and Internet machine population. DEC was the technological leader of the minicomputer era (roughly 1967 to 1987), but its failure to embrace microcomputers and Unix early cost it heavily in profits and prestige after {silicon} got cheap. Nevertheless, the microprocessor design tradition owes a heavy debt to the PDP-11 instruction set, and every one of the major general-purpose microcomputer OSs so far (CP/M, MS-DOS, Unix, OS/2, Windows NT) was either genetically descended from a DEC OS, or incubated on DEC hardware, or both. Accordingly, DEC is still regarded with a certain wry affection even among many hackers too young to have grown up on DEC machines. The contrast with {IBM} is instructive.

[1996 update: DEC has gradually been reclaiming some of its old reputation among techies in the last five years. The success of the Alpha, an innovatively-designed and very high-performance {killer micro}, has helped a lot. So has DEC's newfound receptiveness to Unix and open systems in general. —ESR]

:dec: /dek/ /v./ Verbal (and only rarely written) shorthand for decrement, i.e. `decrease by one'. Especially used by assembly programmers, as many assembly languages have a `dec' mnemonic. Antonym: {inc}.

:DEC Wars: /n./ A 1983 {Usenet} posting by Alan Hastings and Steve Tarr spoofing the "Star Wars" movies in hackish terms. Some years later, ESR (disappointed by Hastings and Tarr's failure to exploit a great premise more thoroughly) posted a 3-times-longer complete rewrite called "Unix WARS"; the two are often confused.

:decay: /n.,vi/ [from nuclear physics] An automatic conversion which is applied to most array-valued expressions in {C}; they `decay into' pointer-valued expressions pointing to the array's first element. This term is borderline techspeak, but is not used in the official standard for the language.

:DEChead: /dek'hed/ /n./ 1. A {DEC} {field servoid}. Not flattering. 2. [from `deadhead'] A Grateful Dead fan working at DEC.

:deckle: /dek'l/ /n./ [from dec- and {nybble}; the original
spelling seems to have been `decle'] Two {nickle}s; 10
bits. Reported among developers for Mattel's GI 1600 (the
Intellivision games processor), a chip with 16-bit-wide RAM but
10-bit-wide ROM. See {nybble} for other such terms.

:DED: /D-E-D/ /n./ Dark-Emitting Diode (that is, a burned-out
LED). Compare {SED}, {LER}, {write-only memory}. In the
early 1970s both Signetics and Texas instruments released DED spec
sheets as {AFJ}s (suggested uses included "as a power-off
indicator").

:deep hack mode: /n./ See {hack mode}.

:deep magic: /n./ [poss. from C. S. Lewis's "Narnia"
books] An awesomely arcane technique central to a program or
system, esp. one neither generally published nor available to
hackers at large (compare {black art}); one that could only have
been composed by a true {wizard}. Compiler optimization
techniques and many aspects of {OS} design used to be {deep
magic}; many techniques in cryptography, signal processing,
graphics, and AI still are. Compare {heavy wizardry}. Esp.
found in comments of the form "Deep magic begins here…".
Compare {voodoo programming}.

:deep space: /n./ 1. Describes the notional location of any
program that has gone {off the trolley}. Esp. used of
programs that just sit there silently grinding long after either
failure or some output is expected. "Uh oh. I should have gotten
a prompt ten seconds ago. The program's in deep space somewhere."
Compare {buzz}, {catatonic}, {hyperspace}. 2. The
metaphorical location of a human so dazed and/or confused or caught
up in some esoteric form of {bogosity} that he or she no longer
responds coherently to normal communication. Compare {page
out}.

:defenestration: /n./ [from the traditional Czechoslovakian method of assassinating prime ministers, via SF fandom] 1. Proper karmic retribution for an incorrigible punster. "Oh, ghod, that was *awful*!" "Quick! Defenestrate him!" 2. The act of exiting a window system in order to get better response time from a full-screen program. This comes from the dictionary meaning of `defenestrate', which is to throw something out a window. 3. The act of discarding something under the assumption that it will improve matters. "I don't have any disk space left." "Well, why don't you defenestrate that 100 megs worth of old core dumps?" 4. Under a GUI, the act of dragging something out of a window (onto the screen). "Next, defenestrate the MugWump icon." 5. [proposed] The requirement to support a command-line interface. "It has to run on a VT100." "Curses! I've been defenestrated!"

:defined as: /adj./ In the role of, usually in an organization-chart sense. "Pete is currently defined as bug prioritizer." Compare {logical}.

:dehose: /dee-hohz/ /vt./ To clear a {hosed} condition.

:delint: /dee-lint/ /v. obs./ To modify code to remove problems detected when {lint}ing. Confusingly, this process is also referred to as `linting' code. This term is no longer in general use because ANSI C compilers typically issue compile-time warnings almost as detailed as lint warnings.

:delta: /n./ 1. [techspeak] A quantitative change, especially a small or incremental one (this use is general in physics and engineering). "I just doubled the speed of my program!" "What was the delta on program size?" "About 30 percent." (He doubled the speed of his program, but increased its size by only 30 percent.) 2. [Unix] A {diff}, especially a {diff} stored under the set of version-control tools called SCCS (Source Code Control System) or RCS (Revision Control System). 3. /n./ A small quantity, but not as small as {epsilon}. The jargon usage of {delta} and {epsilon} stems from the traditional use of these letters in mathematics for very small numerical quantities, particularly in `epsilon-delta' proofs in limit theory (as in the differential calculus). The term {delta} is often used, once {epsilon} has been mentioned, to mean a quantity that is slightly bigger than {epsilon} but still very small. "The cost isn't epsilon, but it's delta" means that the cost isn't totally negligible, but it is nevertheless very small. Common constructions include `within delta of —-', `within epsilon of —-': that is, `close to' and `even closer to'.

:demented: /adj./ Yet another term of disgust used to describe a program. The connotation in this case is that the program works as designed, but the design is bad. Said, for example, of a program that generates large numbers of meaningless error messages, implying that it is on the brink of imminent collapse. Compare {wonky}, {bozotic}.

:demigod: /n./ A hacker with years of experience, a world-wide reputation, and a major role in the development of at least one design, tool, or game used by or known to more than half of the hacker community. To qualify as a genuine demigod, the person must recognizably identify with the hacker community and have helped shape it. Major demigods include Ken Thompson and Dennis Ritchie (co-inventors of {{Unix}} and {C}), Richard M. Stallman (inventor of {EMACS}), Linus Torvalds (inventor of Linux), and most recently James Gosling (inventor of Java). In their hearts of hearts, most hackers dream of someday becoming demigods themselves, and more than one major software project has been driven to completion by the author's veiled hopes of apotheosis. See also {net.god}, {true-hacker}.

:demo: /de'moh/ [short for `demonstration'] 1. /v./ To demonstrate a product or prototype. A far more effective way of inducing bugs to manifest than any number of {test} runs, especially when important people are watching. 2. /n./ The act of demoing. "I've gotta give a demo of the drool-proof interface; how does it work again?" 3. /n./ Esp. as `demo version', can refer either to an early, barely-functional version of a program which can be used for demonstration purposes as long as the operator uses *exactly* the right commands and skirts its numerous bugs, deficiencies, and unimplemented portions, or to a special version of a program (frequently with some features crippled) which is distributed at little or no cost to the user for enticement purposes.

:demo mode: /n./ 1. [Sun] The state of being {heads down} in order to finish code in time for a {demo}, usually due yesterday. 2. A mode in which video games sit by themselves running through a portion of the game, also known as `attract mode'. Some serious {app}s have a demo mode they use as a screen saver, or may go through a demo mode on startup (for example, the Microsoft Windows opening screen — which lets you impress your neighbors without actually having to put up with {Microsloth Windows}).

:demon: /n./ 1. [MIT] A portion of a program that is not invoked explicitly, but that lies dormant waiting for some condition(s) to occur. See {daemon}. The distinction is that demons are usually processes within a program, while daemons are usually programs running on an operating system. 2. [outside MIT] Often used equivalently to {daemon} — especially in the {{Unix}} world, where the latter spelling and pronunciation is considered mildly archaic.

Demons in sense 1 are particularly common in AI programs. For example, a knowledge-manipulation program might implement inference rules as demons. Whenever a new piece of knowledge was added, various demons would activate (which demons depends on the particular piece of data) and would create additional pieces of knowledge by applying their respective inference rules to the original piece. These new pieces could in turn activate more demons as the inferences filtered down through chains of logic. Meanwhile, the main program could continue with whatever its primary task was.

:demon dialer: /n./ A program which repeatedly calls the same telephone number. Demon dialing may be benign (as when a number of communications programs contend for legitimate access to a {BBS} line) or malign (that is, used as a prank or denial-of-service attack). This term dates from the {blue box} days of the 1970s and early 1980s and is now semi-obsolescent among {phreaker}s; see {war dialer} for its contemporary progeny.

:depeditate: /dee-ped'*-tayt/ /n./ [by (faulty) analogy with `decapitate'] Humorously, to cut off the feet of. When one is using some computer-aided typesetting tools, careless placement of text blocks within a page or above a rule can result in chopped-off letter descenders. Such letters are said to have been depeditated.

:deprecated: /adj./ Said of a program or feature that is considered obsolescent and in the process of being phased out, usually in favor of a specified replacement. Deprecated features can, unfortunately, linger on for many years. This term appears with distressing frequency in standards documents when the committees writing the documents realize that large amounts of extant (and presumably happily working) code depend on the feature(s) that have passed out of favor. See also {dusty deck}.

:derf: /derf/ /v.,n./ [PLATO] The act of exploiting a terminal which someone else has absentmindedly left logged on, to use that person's account, especially to post articles intended to make an ass of the victim you're impersonating.

:deserves to lose: /adj./ Said of someone who willfully does the {Wrong Thing}; humorously, if one uses a feature known to be {marginal}. What is meant is that one deserves the consequences of one's {losing} actions. "Boy, anyone who tries to use {mess-dos} deserves to {lose}!" ({{ITS}} fans used to say the same thing of {{Unix}}; many still do.) See also {screw}, {chomp}, {bagbiter}.

:desk check: /n.,v./ To {grovel} over hardcopy of source code, mentally simulating the control flow; a method of catching bugs. No longer common practice in this age of on-screen editing, fast compiles, and sophisticated debuggers — though some maintain stoutly that it ought to be. Compare {eyeball search}, {vdiff}, {vgrep}.

:despew: /d*-spyoo'/ /v./ [Usenet] To automatically generate a large amount of garbage to the net, esp. from an automated posting program gone wild. See {ARMM}.

:Devil Book: /n./ See {daemon book}, the term preferred by its authors.

:dickless workstation: /n./ Extremely pejorative hackerism for `diskless workstation', a class of botches including the Sun 3/50 and other machines designed exclusively to network with an expensive central disk server. These combine all the disadvantages of time-sharing with all the disadvantages of distributed personal computers; typically, they cannot even {boot} themselves without help (in the form of some kind of {breath-of-life packet}) from the server.

:dictionary flame: /n./ [Usenet] An attempt to sidetrack a debate away from issues by insisting on meanings for key terms that presuppose a desired conclusion or smuggle in an implicit premise. A common tactic of people who prefer argument over definitions to disputes about reality. Compare {spelling flame}.

:diddle: 1. /vt./ To work with or modify in a not particularly serious manner. "I diddled a copy of {ADVENT} so it didn't double-space all the time." "Let's diddle this piece of code and see if the problem goes away." See {tweak} and {twiddle}. 2. /n./ The action or result of diddling. See also {tweak}, {twiddle}, {frob}.

:die: /v./ Syn. {crash}. Unlike {crash}, which is used
primarily of hardware, this verb is used of both hardware and
software. See also {go flatline}, {casters-up mode}.

:die horribly: /v./ The software equivalent of {crash and
burn}, and the preferred emphatic form of {die}. "The
converter choked on an FF in its input and died horribly".

:diff: /dif/ /n./ 1. A change listing, especially giving differences between (and additions to) source code or documents (the term is often used in the plural `diffs'). "Send me your diffs for the Jargon File!" Compare {vdiff}. 2. Specifically, such a listing produced by the `diff(1)' command, esp. when used as specification input to the `patch(1)' utility (which can actually perform the modifications; see {patch}). This is a common method of distributing patches and source updates in the Unix/C world. 3. /v./ To compare (whether or not by use of automated tools on machine-readable files); see also {vdiff}, {mod}.

:digit: /n./ An employee of Digital Equipment Corporation. See also {VAX}, {VMS}, {PDP-10}, {{TOPS-10}}, {DEChead}, {double DECkers}, {field circus}.

:dike: /vt./ To remove or disable a portion of something, as a wire from a computer or a subroutine from a program. A standard slogan is "When in doubt, dike it out". (The implication is that it is usually more effective to attack software problems by reducing complexity than by increasing it.) The word `dikes' is widely used among mechanics and engineers to mean `diagonal cutters', esp. the heavy-duty metal-cutting version, but may also refer to a kind of wire-cutters used by electronics techs. To `dike something out' means to use such cutters to remove something. Indeed, the TMRC Dictionary defined dike as "to attack with dikes". Among hackers this term has been metaphorically extended to informational objects such as sections of code.

:Dilbert: /n./ Name and title character of a comic strip nationally syndicated in the U.S. and enormously popular among hackers. Dilbert is an archetypical engineer-nerd who works at an anonymous high-technology company; the strips present a lacerating satire of insane working conditions and idiotic {management} practices all too readily recognized by hackers. Adams, who spent nine years in {cube} 4S700R at Pacific Bell (not {DEC} as often reported), often remarks that he has never been able to come up with a fictional management blunder that his correspondents didn't quickly either report to have actually happened or top with a similar but even more bizarre incident. In 1996 Adams distilled his insights into the collective psychology of businesses into an even funnier book, "The Dilbert Principle" (HarperCollins, ISBN 0-887-30787-6). See also {rat dance}.

:ding: /n.,vi./ 1. Synonym for {feep}. Usage: rare among hackers, but commoner in the {Real World}. 2. `dinged': What happens when someone in authority gives you a minor bitching about something, esp. something trivial. "I was dinged for having a messy desk."

:dink: /dink/ /adj./ Said of a machine that has the {bitty
box} nature; a machine too small to be worth bothering with —-
sometimes the system you're currently forced to work on. First
heard from an MIT hacker working on a CP/M system with 64K, in
reference to any 6502 system, then from fans of 32-bit
architectures about 16-bit machines. "GNUMACS will never work on
that dink machine." Probably derived from mainstream `dinky',
which isn't sufficiently pejorative. See {macdink}.

:dinosaur: /n./ 1. Any hardware requiring raised flooring and
special power. Used especially of old minis and mainframes, in
contrast with newer microprocessor-based machines. In a famous
quote from the 1988 Unix EXPO, Bill Joy compared the liquid-cooled
mainframe in the massive IBM display with a grazing dinosaur "with
a truck outside pumping its bodily fluids through it". IBM was
not amused. Compare {big iron}; see also {mainframe}.
2. [IBM] A very conservative user; a {zipperhead}.

:dinosaur pen: /n./ A traditional {mainframe} computer room complete with raised flooring, special power, its own ultra-heavy-duty air conditioning, and a side order of Halon fire extinguishers. See {boa}.

:dinosaurs mating: /n./ Said to occur when yet another {big iron} merger or buyout occurs; reflects a perception by hackers that these signal another stage in the long, slow dying of the {mainframe} industry. In its glory days of the 1960s, it was `IBM and the Seven Dwarves': Burroughs, Control Data, General Electric, Honeywell, NCR, RCA, and Univac. RCA and GE sold out early, and it was `IBM and the Bunch' (Burroughs, Univac, NCR, Control Data, and Honeywell) for a while. Honeywell was bought out by Bull; Burroughs merged with Univac to form Unisys (in 1984 —- this was when the phrase `dinosaurs mating' was coined); and in 1991 AT&T absorbed NCR. More such earth-shaking unions of doomed giants seem inevitable.

:dirtball: /n./ [XEROX PARC] A small, perhaps struggling outsider; not in the major or even the minor leagues. For example, "Xerox is not a dirtball company".

[Outsiders often observe in the PARC culture an institutional arrogance which usage of this term exemplifies. The brilliance and scope of PARC's contributions to computer science have been such that this superior attitude is not much resented. —ESR]

:dirty power: /n./ Electrical mains voltage that is unfriendly to the delicate innards of computers. Spikes, {drop-outs}, average voltage significantly higher or lower than nominal, or just plain noise can all cause problems of varying subtlety and severity (these are collectively known as {power hit}s).

:disclaimer: /n./ [Usenet] Statement ritually appended to many Usenet postings (sometimes automatically, by the posting software) reiterating the fact (which should be obvious, but is easily forgotten) that the article reflects its author's opinions and not necessarily those of the organization running the machine through which the article entered the network.

:Discordianism: /dis-kor'di-*n-ism/ /n./ The veneration of {Eris}, a.k.a. Discordia; widely popular among hackers. Discordianism was popularized by Robert Shea and Robert Anton Wilson's novel "{Illuminatus!}" as a sort of self-subverting Dada-Zen for Westerners — it should on no account be taken seriously but is far more serious than most jokes. Consider, for example, the Fifth Commandment of the Pentabarf, from "Principia Discordia": "A Discordian is Prohibited of Believing What he Reads." Discordianism is usually connected with an elaborate conspiracy theory/joke involving millennia-long warfare between the anarcho-surrealist partisans of Eris and a malevolent, authoritarian secret society called the Illuminati. See {Religion} in Appendix B, {Church of the SubGenius}, and {ha ha only serious}.

:disk farm: /n./ (also {laundromat}) A large room or rooms filled with disk drives (esp. {washing machine}s).

:display hack: /n./ A program with the same approximate purpose as a kaleidoscope: to make pretty pictures. Famous display hacks include {munching squares}, {smoking clover}, the BSD Unix `rain(6)' program, `worms(6)' on miscellaneous Unixes, and the {X} `kaleid(1)' program. Display hacks can also be implemented without programming by creating text files containing numerous escape sequences for interpretation by a video terminal; one notable example displayed, on any VT100, a Christmas tree with twinkling lights and a toy train circling its base. The {hack value} of a display hack is proportional to the esthetic value of the images times the cleverness of the algorithm divided by the size of the code. Syn. {psychedelicware}.

:Dissociated Press: /n./ [play on `Associated Press'; perhaps
inspired by a reference in the 1950 Bugs Bunny cartoon
"What's Up, Doc?"] An algorithm for transforming any text
into potentially humorous garbage even more efficiently than by
passing it through a {marketroid}. The algorithm starts by
printing any N consecutive words (or letters) in the text.
Then at every step it searches for any random occurrence in the
original text of the last N words (or letters) already
printed and then prints the next word or letter. {EMACS} has a
handy command for this. Here is a short example of word-based
Dissociated Press applied to an earlier version of this Jargon
File:

wart: /n./ A small, crocky {feature} that sticks out of an array (C has no checks for this). This is relatively benign and easy to spot if the phrase is bent so as to be not worth paying attention to the medium in question.

Here is a short example of letter-based Dissociated Press applied to the same source:

window sysIWYG: /n./ A bit was named aften /bee't*/ prefer to use the other guy's re, especially in every cast a chuckle on neithout getting into useful informash speech makes removing a featuring a move or usage actual abstractionsidered /interj./ Indeed spectace logic or problem!

A hackish idle pastime is to apply letter-based Dissociated Press to a random body of text and {vgrep} the output in hopes of finding an interesting new word. (In the preceding example, `window sysIWYG' and `informash' show some promise.) Iterated applications of Dissociated Press usually yield better results. Similar techniques called `travesty generators' have been employed with considerable satirical effect to the utterances of Usenet flamers; see {pseudo}.

:distribution: /n./ 1. A software source tree packaged for
distribution; but see {kit}. 2. A vague term encompassing
mailing lists and Usenet newsgroups (but not {BBS} {fora});
any topic-oriented message channel with multiple recipients. 3. An
information-space domain (usually loosely correlated with
geography) to which propagation of a Usenet message is restricted;
a much-underutilized feature.

:disusered: /adj./ [Usenet] Said of a person whose account on a
computer has been removed, esp. for cause rather than through
normal attrition. "He got disusered when they found out he'd been
cracking through the school's Internet access." The verbal form
`disuser' is live but less common. Both usages probably derive
from the DISUSER account status flag on VMS; setting it disables
the account. Compare {star out}.

:do protocol: /vi./ [from network protocol programming] To perform an interaction with somebody or something that follows a clearly defined procedure. For example, "Let's do protocol with the check" at a restaurant means to ask for the check, calculate the tip and everybody's share, collect money from everybody, generate change as necessary, and pay the bill. See {protocol}.

:doc: /dok/ /n./ Common spoken and written shorthand for `documentation'. Often used in the plural `docs' and in the construction `doc file' (i.e., documentation available on-line).

:documentation:: /n./ The multiple kilograms of macerated, pounded, steamed, bleached, and pressed trees that accompany most modern software or hardware products (see also {tree-killer}). Hackers seldom read paper documentation and (too) often resist writing it; they prefer theirs to be terse and on-line. A common comment on this predilection is "You can't {grep} dead trees". See {drool-proof paper}, {verbiage}, {treeware}.

:dodgy: /adj./ Syn. with {flaky}. Preferred outside the U.S.

:dogcow: /dog'kow/ /n./ See {Moof}. The dogcow is a semi-legendary creature that lurks in the depths of the Macintosh Technical Notes Hypercard stack V3.1. The full story of the dogcow is told in technical note #31 (the particular dogcow illustrated is properly named `Clarus'). Option-shift-click will cause it to emit a characteristic `Moof!' or `!fooM' sound. *Getting* to tech note 31 is the hard part; to discover how to do that, one must needs examine the stack script with a hackerly eye. Clue: {rot13} is involved. A dogcow also appears if you choose `Page Setup…' with a LaserWriter selected and click on the `Options' button.

:dogpile: /v./ [Usenet: prob. fr. mainstream "puppy pile"]
When many people post unfriendly responses in short order to a
single posting, they are sometimes said to "dogpile" or "dogpile
on" the person to whom they're responding. For example, when a
religious missionary posts a simplistic appeal to alt.atheism,
he can expect to be dogpiled.

:dogwash: /dog'wosh/ [From a quip in the `urgency' field
of a very optional software change request, ca. 1982. It was
something like "Urgency: Wash your dog first".] 1. /n./ A project
of minimal priority, undertaken as an escape from more serious
work. 2. /v./ To engage in such a project. Many games and much
{freeware} get written this way.

:domainist: /doh-mayn'ist/ /adj./ 1. [USENET, by pointed analogy with "sexist", "racist", etc.] Someone who judges people by the domain of their email addresses; esp. someone who dismisses anyone who posts from a public internet provider. "What do you expect from an article posted from aol.com?" 2. Said of an {{Internet address}} (as opposed to a {bang path}) because the part to the right of the `@' specifies a nested series of `domains'; for example, esr@snark.thyrsus.com specifies the machine called snark in the subdomain called thyrsus within the top-level domain called com. See also {big-endian}, sense 2.

The meaning of this term has drifted. At one time sense 2 was primary. In elder days it was also used of a site, mailer, or routing program which knew how to handle domainist addresses; or of a person (esp. a site admin) who preferred domain addressing, supported a domainist mailer, or proselytized for domainist addressing and disdained {bang path}s. These senses are now (1996) obsolete, as effectively all sites have converted.

:Don't do that, then!: /imp./ [from an old doctor's office joke about a patient with a trivial complaint] Stock response to a user complaint. "When I type control-S, the whole system comes to a halt for thirty seconds." "Don't do that, then!" (or "So don't do that!"). Compare {RTFM}.

:dongle: /dong'gl/ /n./ 1. A security or {copy protection} device for commercial microcomputer programs consisting of a serialized EPROM and some drivers in a D-25 connector shell, which must be connected to an I/O port of the computer while the program is run. Programs that use a dongle query the port at startup and at programmed intervals thereafter, and terminate if it does not respond with the dongle's programmed validation code. Thus, users can make as many copies of the program as they want but must pay for each dongle. The idea was clever, but it was initially a failure, as users disliked tying up a serial port this way. Almost all dongles on the market today (1993) will pass data through the port and monitor for {magic} codes (and combinations of status lines) with minimal if any interference with devices further down the line — this innovation was necessary to allow daisy-chained dongles for multiple pieces of software. The devices are still not widely used, as the industry has moved away from copy-protection schemes in general. 2. By extension, any physical electronic key or transferable ID required for a program to function. Common variations on this theme have used parallel or even joystick ports. See {dongle-disk}.

[Note: in early 1992, advertising copy from Rainbow Technologies (a manufacturer of dongles) included a claim that the word derived from "Don Gall", allegedly the inventor of the device. The company's receptionist will cheerfully tell you that the story is a myth invented for the ad copy. Nevertheless, I expect it to haunt my life as a lexicographer for at least the next ten years. :-( —ESR]

:dongle-disk: /don'gl disk/ /n./ A special floppy disk that is required in order to perform some task. Some contain special coding that allows an application to identify it uniquely, others *are* special code that does something that normally-resident programs don't or can't. (For example, AT&T's "Unix PC" would only come up in {root mode} with a special boot disk.) Also called a `key disk'. See {dongle}.

:donuts: /n. obs./ A collective noun for any set of memory bits. This usage is extremely archaic and may no longer be live jargon; it dates from the days of ferrite-{core} memories in which each bit was implemented by a doughnut-shaped magnetic flip-flop.

:doorstop: /n./ Used to describe equipment that is non-functional and halfway expected to remain so, especially obsolete equipment kept around for political reasons or ostensibly as a backup. "When we get another Wyse-50 in here, that ADM 3 will turn into a doorstop." Compare {boat anchor}.

:dot file: [Unix] /n./ A file that is not visible by default to normal directory-browsing tools (on Unix, files named with a leading dot are, by convention, not normally presented in directory listings). Many programs define one or more dot files in which startup or configuration information may be optionally recorded; a user can customize the program's behavior by creating the appropriate file in the current or home directory. (Therefore, dot files tend to {creep} — with every nontrivial application program defining at least one, a user's home directory can be filled with scores of dot files, of course without the user's really being aware of it.) See also {profile} (sense 1), {rc file}.

:double bucky: /adj./ Using both the CTRL and META keys. "The command to burn all LEDs is double bucky F."

This term originated on the Stanford extended-ASCII keyboard, and was later taken up by users of the {space-cadet keyboard} at MIT. A typical MIT comment was that the Stanford {bucky bits} (control and meta shifting keys) were nice, but there weren't enough of them; you could type only 512 different characters on a Stanford keyboard. An obvious way to address this was simply to add more shifting keys, and this was eventually done; but a keyboard with that many shifting keys is hard on touch-typists, who don't like to move their hands away from the home position on the keyboard. It was half-seriously suggested that the extra shifting keys be implemented as pedals; typing on such a keyboard would be very much like playing a full pipe organ. This idea is mentioned in a parody of a very fine song by Jeffrey Moss called "Rubber Duckie", which was published in "The Sesame Street Songbook" (Simon and Schuster 1971, ISBN 0-671-21036-X). These lyrics were written on May 27, 1978, in celebration of the Stanford keyboard:

Double Bucky

Double bucky, you're the one!
You make my keyboard lots of fun.
Double bucky, an additional bit or two:
(Vo-vo-de-o!)
Control and meta, side by side,
Augmented ASCII, nine bits wide!
Double bucky! Half a thousand glyphs, plus a few!
Oh,
I sure wish that I
Had a couple of
Bits more!
Perhaps a
Set of pedals to
Make the number of
Bits four:
Double double bucky!
Double bucky, left and right
OR'd together, outta sight!
Double bucky, I'd like a whole word of
Double bucky, I'm happy I heard of
Double bucky, I'd like a whole word of you!

—- The Great Quux (with apologies to Jeffrey Moss)

[This, by the way, is an excellent example of computer {filk} —ESR] See also {meta bit}, {cokebottle}, and {quadruple bucky}.

:double DECkers: /n./ Used to describe married couples in which both partners work for Digital Equipment Corporation.

:doubled sig: [Usenet] /n./ A {sig block} that has been included twice in a {Usenet} article or, less commonly, in an electronic mail message. An article or message with a doubled sig can be caused by improperly configured software. More often, however, it reveals the author's lack of experience in electronic communication. See {B1FF}, {pseudo}.

:down: 1. /adj./ Not operating. "The up escalator is down" is considered a humorous thing to say (unless of course you were expecting to use it), and "The elevator is down" always means "The elevator isn't working" and never refers to what floor the elevator is on. With respect to computers, this term has passed into the mainstream; the extension to other kinds of machine is still confined to techies (e.g. boiler mechanics may speak of a boiler being down). 2. `go down' /vi./ To stop functioning; usually said of the {system}. The message from the {console} that every hacker hates to hear from the operator is "System going down in 5 minutes". 3. `take down', `bring down' /vt./ To deactivate purposely, usually for repair work or {PM}. "I'm taking the system down to work on that bug in the tape drive." Occasionally one hears the word `down' by itself used as a verb in this /vt./ sense. See {crash}; oppose {up}.

:download: /vt./ To transfer data or (esp.) code from a larger `host' system (esp. a {mainframe}) over a digital comm link to a smaller `client' system, esp. a microcomputer or specialized peripheral. Oppose {upload}.

However, note that ground-to-space communications has its own usage rule for this term. Space-to-earth transmission is always `down' and the reverse `up' regardless of the relative size of the computers involved. So far the in-space machines have invariably been smaller; thus the upload/download distinction has been reversed from its usual sense.

:DP: /D-P/ /n./ 1. Data Processing. Listed here because, according to hackers, use of the term marks one immediately as a {suit}. See {DPer}. 2. Common abbrev for {Dissociated Press}.

:DPB: /d*-pib'/ /vt./ [from the PDP-10 instruction set] To plop something down in the middle. Usage: silly. "DPB yourself into that couch there." The connotation would be that the couch is full except for one slot just big enough for one last person to sit in. DPB means `DePosit Byte', and was the name of a PDP-10 instruction that inserts some bits into the middle of some other bits. Hackish usage has been kept alive by the Common LISP function of the same name.

:DPer: /dee-pee-er/ /n./ Data Processor. Hackers are absolutely amazed that {suit}s use this term self-referentially. *Computers* process data, not people! See {DP}.

:dragon: /n./ [MIT] A program similar to a {daemon}, except that it is not invoked at all, but is instead used by the system to perform various secondary tasks. A typical example would be an accounting program, which keeps track of who is logged in, accumulates load-average statistics, etc. Under ITS, many terminals displayed a list of people logged in, where they were, what they were running, etc., along with some random picture (such as a unicorn, Snoopy, or the Enterprise), which was generated by the `name dragon'. Usage: rare outside MIT — under Unix and most other OSes this would be called a `background demon' or {daemon}. The best-known Unix example of a dragon is `cron(1)'. At SAIL, they called this sort of thing a `phantom'.

:Dragon Book: /n./ The classic text "Compilers: Principles, Techniques and Tools", by Alfred V. Aho, Ravi Sethi, and Jeffrey D. Ullman (Addison-Wesley 1986; ISBN 0-201-10088-6), so called because of the cover design featuring a dragon labeled `complexity of compiler design' and a knight bearing the lance `LALR parser generator' among his other trappings. This one is more specifically known as the `Red Dragon Book' (1986); an earlier edition, sans Sethi and titled "Principles Of Compiler Design" (Alfred V. Aho and Jeffrey D. Ullman; Addison-Wesley, 1977; ISBN 0-201-00022-9), was the `Green Dragon Book' (1977). (Also `New Dragon Book', `Old Dragon Book'.) The horsed knight and the Green Dragon were warily eying each other at a distance; now the knight is typing (wearing gauntlets!) at a terminal showing a video-game representation of the Red Dragon's head while the rest of the beast extends back in normal space. See also {{book titles}}.

:drain: /v./ [IBM] Syn. for {flush} (sense 2). Has a connotation of finality about it; one speaks of draining a device before taking it offline.

:dread high-bit disease: /n./ A condition endemic to some now-obsolete computers and peripherals (including ASR-33 teletypes and PRIME minicomputers) that results in all characters having their high (0x80) bit forced on. This of course makes transporting files to other systems much more difficult, not to mention the problems these machines have talking with true 8-bit devices.

This term was originally used specifically of PRIME (a.k.a. PR1ME)
minicomputers. Folklore has it that PRIME adopted the
reversed-8-bit
convention in order to save 25 cents per serial line per machine;
PRIME old-timers, on the other hand, claim they inherited the
disease from Honeywell via customer NASA's compatibility
requirements and struggled heroically to cure it. Whoever was
responsible, this probably qualifies as one of the most
{cretinous} design tradeoffs ever made. See {meta bit}.

:DRECNET: /drek'net/ /n./ [from Yiddish/German `dreck', meaning filth] Deliberate distortion of DECNET, a networking protocol used in the {VMS} community. So called because DEC helped write the Ethernet specification and then (either stupidly or as a malignant customer-control tactic) violated that spec in the design of DRECNET in a way that made it incompatible. See also {connector conspiracy}.

:driver: /n./ 1. The {main loop} of an event-processing program; the code that gets commands and dispatches them for execution. 2. [techspeak] In `device driver', code designed to handle a particular peripheral device such as a magnetic disk or tape unit. 3. In the TeX world and the computerized typesetting world in general, a program that translates some device-independent or other common format to something a real device can actually understand.

:droid: /n./ [from `android', SF terminology for a humanoid robot of essentially biological (as opposed to mechanical/electronic) construction] A person (esp. a low-level bureaucrat or service-business employee) exhibiting most of the following characteristics: (a) naive trust in the wisdom of the parent organization or `the system'; (b) a blind-faith propensity to believe obvious nonsense emitted by authority figures (or computers!); (c) a rule-governed mentality, one unwilling or unable to look beyond the `letter of the law' in exceptional situations; (d) a paralyzing fear of official reprimand or worse if Procedures are not followed No Matter What; and (e) no interest in doing anything above or beyond the call of a very narrowly-interpreted duty, or in particular in fixing that which is broken; an "It's not my job, man" attitude.

Typical droid positions include supermarket checkout assistant and bank clerk; the syndrome is also endemic in low-level government employees. The implication is that the rules and official procedures constitute software that the droid is executing; problems arise when the software has not been properly debugged. The term `droid mentality' is also used to describe the mindset behind this behavior. Compare {suit}, {marketroid}; see {-oid}.

:drool-proof paper: /n./ Documentation that has been obsessively {dumbed down}, to the point where only a {cretin} could bear to read it, is said to have succumbed to the `drool-proof paper syndrome' or to have been `written on drool-proof paper'. For example, this is an actual quote from Apple's LaserWriter manual: "Do not expose your LaserWriter to open fire or flame."

:drop on the floor: /vt./ To react to an error condition by silently discarding messages or other valuable data. "The gateway ran out of memory, so it just started dropping packets on the floor." Also frequently used of faulty mail and netnews relay sites that lose messages. See also {black hole}, {bit bucket}.

:drop-ins: /n./ [prob. by analogy with {drop-outs}] Spurious characters appearing on a terminal or console as a result of line noise or a system malfunction of some sort. Esp. used when these are interspersed with one's own typed input. Compare {drop-outs}, sense 2.

:drop-outs: /n./ 1. A variety of `power glitch' (see {glitch}); momentary 0 voltage on the electrical mains. 2. Missing characters in typed input due to software malfunction or system saturation (one cause of such behavior under Unix when a bad connection to a modem swamps the processor with spurious character interrupts; see {screaming tty}). 3. Mental glitches; used as a way of describing those occasions when the mind just seems to shut down for a couple of beats. See {glitch}, {fried}.

:drugged: /adj./ (also `on drugs') 1. Conspicuously stupid, heading toward {brain-damaged}. Often accompanied by a pantomime of toking a joint. 2. Of hardware, very slow relative to normal performance.

:drum: adj, /n./ Ancient techspeak term referring to slow,
cylindrical magnetic media that were once state-of-the-art storage
devices. Under BSD Unix the disk partition used for swapping is
still called `/dev/drum'; this has led to considerable humor
and not a few straight-faced but utterly bogus `explanations'
getting foisted on {newbie}s. See also "{The Story of Mel, a
Real Programmer}" in Appendix A.

:drunk mouse syndrome: /n./ (also `mouse on drugs') A malady
exhibited by the mouse pointing device of some computers. The
typical symptom is for the mouse cursor on the screen to move in
random directions and not in sync with the motion of the actual
mouse. Can usually be corrected by unplugging the mouse and
plugging it back again. Another recommended fix for optical mice
is to rotate your mouse pad 90 degrees.

At Xerox PARC in the 1970s, most people kept a can of copier cleaner (isopropyl alcohol) at their desks. When the steel ball on the mouse had picked up enough {cruft} to be unreliable, the mouse was doused in cleaner, which restored it for a while. However, this operation left a fine residue that accelerated the accumulation of cruft, so the dousings became more and more frequent. Finally, the mouse was declared `alcoholic' and sent to the clinic to be dried out in a CFC ultrasonic bath.

:Duff's device: /n./ The most dramatic use yet seen of {fall through} in C, invented by Tom Duff when he was at Lucasfilm. Trying to {bum} all the instructions he could out of an inner loop that copied data serially onto an output port, he decided to unroll it. He then realized that the unrolled version could be implemented by *interlacing* the structures of a switch and a loop:

register n = (count + 7) / 8; /* count > 0 assumed */

switch (count % 8)
{
case 0: do { *to = *from++;
case 7: *to = *from++;
case 6: *to = *from++;
case 5: *to = *from++;
case 4: *to = *from++;
case 3: *to = *from++;
case 2: *to = *from++;
case 1: *to = *from++;
} while (—n > 0);
}

Shocking though it appears to all who encounter it for the first time, the device is actually perfectly valid, legal C. C's default {fall through} in case statements has long been its most controversial single feature; Duff observed that "This code forms some sort of argument in that debate, but I'm not sure whether it's for or against."

[For maximal obscurity, the outermost pair of braces above could be actually be removed — GLS]

:dumb terminal: /n./ A terminal that is one step above a {glass tty}, having a minimally addressable cursor but no on-screen editing or other features normally supported by a {smart terminal}. Once upon a time, when glass ttys were common and addressable cursors were something special, what is now called a dumb terminal could pass for a smart terminal.

:dumbass attack: /duhm'as *-tak'/ /n./ [Purdue] Notional cause of a novice's mistake made by the experienced, especially one made while running as {root} under Unix, e.g., typing `rm -r *' or `mkfs' on a mounted file system. Compare {adger}.

:dumbed down: /adj./ Simplified, with a strong connotation of *over*simplified. Often, a {marketroid} will insist that the interfaces and documentation of software be dumbed down after the designer has burned untold gallons of midnight oil making it smart. This creates friction. See {user-friendly}.

:dump: /n./ 1. An undigested and voluminous mass of information about a problem or the state of a system, especially one routed to the slowest available output device (compare {core dump}), and most especially one consisting of hex or octal {runes} describing the byte-by-byte state of memory, mass storage, or some file. In {elder days}, debugging was generally done by `groveling over' a dump (see {grovel}); increasing use of high-level languages and interactive debuggers has made such tedium uncommon, and the term `dump' now has a faintly archaic flavor. 2. A backup. This usage is typical only at large timesharing installations.

:dumpster diving: /dump'-ster di:'-ving/ /n./ 1. The practice of sifting refuse from an office or technical installation to extract confidential data, especially security-compromising information (`dumpster' is an Americanism for what is elsewhere called a `skip'). Back in AT&T's monopoly days, before paper shredders became common office equipment, phone phreaks (see {phreaking}) used to organize regular dumpster runs against phone company plants and offices. Discarded and damaged copies of AT&T internal manuals taught them much. The technique is still rumored to be a favorite of crackers operating against careless targets. 2. The practice of raiding the dumpsters behind buildings where producers and/or consumers of high-tech equipment are located, with the expectation (usually justified) of finding discarded but still-valuable equipment to be nursed back to health in some hacker's den. Experienced dumpster-divers not infrequently accumulate basements full of moldering (but still potentially useful) {cruft}.

:dup killer: /d[y]oop kill'r/ /n./ [FidoNet] Software that is supposed to detect and delete duplicates of a message that may have reached the FidoNet system via different routes.

:dup loop: /d[y]oop loop/ (also `dupe loop') /n./ [FidoNet]
An infinite stream of duplicated, near-identical messages on a
FidoNet {echo}, the only difference being unique or mangled
identification information applied by a faulty or incorrectly
configured system or network gateway, thus rendering {dup
killer}s ineffective. If such a duplicate message eventually
reaches a system through which it has already passed (with the
original identification information), all systems passed on the way
back to that system are said to be involved in a {dup loop}.

:dusty deck: /n./ Old software (especially applications) which
one is obliged to remain compatible with, or to maintain ({DP}
types call this `legacy code', a term hackers consider smarmy and
excessively reverent). The term implies that the software in
question is a holdover from card-punch days. Used esp. when
referring to old scientific and {number-crunching} software,
much of which was written in FORTRAN and very poorly documented but
is believed to be too expensive to replace. See {fossil};
compare {crawling horror}.

:DWIM: /dwim/ [acronym, `Do What I Mean'] 1. /adj./ Able to
guess, sometimes even correctly, the result intended when bogus
input was provided. 2. /n. obs./ The BBNLISP/INTERLISP function
that
attempted to accomplish this feat by correcting many of the more
common errors. See {hairy}. 3. Occasionally, an interjection
hurled at a balky computer, esp. when one senses one might be
tripping over legalisms (see {legalese}).

Warren Teitelman originally wrote DWIM to fix his typos and spelling errors, so it was somewhat idiosyncratic to his style, and would often make hash of anyone else's typos if they were stylistically different. Some victims of DWIM thus claimed that the acronym stood for `Damn Warren's Infernal Machine!'.

In one notorious incident, Warren added a DWIM feature to the command interpreter used at Xerox PARC. One day another hacker there typed `delete *$' to free up some disk space. (The editor there named backup files by appending `$' to the original file name, so he was trying to delete any backup files left over from old editing sessions.) It happened that there weren't any editor backup files, so DWIM helpfully reported `*$ not found, assuming you meant 'delete *'.' It then started to delete all the files on the disk! The hacker managed to stop it with a {Vulcan nerve pinch} after only a half dozen or so files were lost.

The disgruntled victim later said he had been sorely tempted to go to Warren's office, tie Warren down in his chair in front of his workstation, and then type `delete *$' twice.

DWIM is often suggested in jest as a desired feature for a complex program; it is also occasionally described as the single instruction the ideal computer would have. Back when proofs of program correctness were in vogue, there were also jokes about `DWIMC' (Do What I Mean, Correctly). A related term, more often seen as a verb, is DTRT (Do The Right Thing); see {Right Thing}.

:dynner: /din'r/ /n./ 32 bits, by analogy with {nybble} and {{byte}}. Usage: rare and extremely silly. See also {playte}, {tayste}, {crumb}. General discussion of such terms is under {nybble}.

= E = =====

:earthquake: /n./ [IBM] The ultimate real-world shock test for computer hardware. Hackish sources at IBM deny the rumor that the Bay Area quake of 1989 was initiated by the company to test quality-assurance procedures at its California plants.

:Easter egg: /n./ [from the custom of the Easter Egg hunt observed in the U.S. and many parts of Europe] 1. A message hidden in the object code of a program as a joke, intended to be found by persons disassembling or browsing the code. 2. A message, graphic, or sound effect emitted by a program (or, on a PC, the BIOS ROM) in response to some undocumented set of commands or keystrokes, intended as a joke or to display program credits. One well-known early Easter egg found in a couple of OSes caused them to respond to the command `make love' with `not war?'. Many personal computers have much more elaborate eggs hidden in ROM, including lists of the developers' names, political exhortations, snatches of music, and (in one case) graphics images of the entire development team.

:Easter egging: /n./ [IBM] The act of replacing unrelated components more or less at random in hopes that a malfunction will go away. Hackers consider this the normal operating mode of {field circus} techs and do not love them for it. See also the jokes under {field circus}. Compare {shotgun debugging}.

:eat flaming death: /imp./ A construction popularized among hackers by the infamous {CPU Wars} comic; supposedly derive from a famously turgid line in a WWII-era anti-Nazi propaganda comic that ran "Eat flaming death, non-Aryan mongrels!" or something of the sort (however, it is also reported that the Firesign Theater's 1975 album "In The Next World, You're On Your Own" included the phrase "Eat flaming death, fascist media pigs"; this may have been an influence). Used in humorously overblown expressions of hostility. "Eat flaming death, {{EBCDIC}} users!"

:EBCDIC:: /eb's*-dik/, /eb'see`dik/, or /eb'k*-dik/ /n./ [abbreviation, Extended Binary Coded Decimal Interchange Code] An alleged character set used on IBM {dinosaur}s. It exists in at least six mutually incompatible versions, all featuring such delights as non-contiguous letter sequences and the absence of several ASCII punctuation characters fairly important for modern computer languages (exactly which characters are absent varies according to which version of EBCDIC you're looking at). IBM adapted EBCDIC from {{punched card}} code in the early 1960s and promulgated it as a customer-control tactic (see {connector conspiracy}), spurning the already established ASCII standard. Today, IBM claims to be an open-systems company, but IBM's own description of the EBCDIC variants and how to convert between them is still internally classified top-secret, burn-before-reading. Hackers blanch at the very *name* of EBCDIC and consider it a manifestation of purest {evil}. See also {fear and loathing}.

:echo: [FidoNet] /n./ A {topic group} on {FidoNet}'s echomail system. Compare {newsgroup}.

:eighty-column mind: /n./ [IBM] The sort said to be possessed by persons for whom the transition from {punched card} to tape was traumatic (nobody has dared tell them about disks yet). It is said that these people, including (according to an old joke) the founder of IBM, will be buried `face down, 9-edge first' (the 9-edge being the bottom of the card). This directive is inscribed on IBM's 1402 and 1622 card readers and is referenced in a famous bit of doggerel called "The Last Bug", the climactic lines of which are as follows:

He died at the console
Of hunger and thirst.
Next day he was buried,
Face down, 9-edge first.

The eighty-column mind is thought by most hackers to dominate IBM's customer base and its thinking. See {IBM}, {fear and loathing}, {card walloper}.

:El Camino Bignum: /el' k*-mee'noh big'nuhm/ /n./ The road mundanely called El Camino Real, running along San Francisco peninsula. It originally extended all the way down to Mexico City; many portions of the old road are still intact. Navigation on the San Francisco peninsula is usually done relative to El Camino Real, which defines {logical} north and south even though it isn't really north-south in many places. El Camino Real runs right past Stanford University and so is familiar to hackers.

The Spanish word `real' (which has two syllables: /ray-ahl'/) means `royal'; El Camino Real is `the royal road'. In the FORTRAN language, a `real' quantity is a number typically precise to seven significant digits, and a `double precision' quantity is a larger floating-point number, precise to perhaps fourteen significant digits (other languages have similar `real' types).

When a hacker from MIT visited Stanford in 1976, he remarked what a long road El Camino Real was. Making a pun on `real', he started calling it `El Camino Double Precision' — but when the hacker was told that the road was hundreds of miles long, he renamed it `El Camino Bignum', and that name has stuck. (See {bignum}.) In recent years, the synonym `El Camino Virtual' has been reported as an alternate at IBM and Amdahl sites in the Valley.

[GLS has since let slip that the unnamed hacker in this story was in fact he —ESR]

:elder days: /n./ The heroic age of hackerdom (roughly, pre-1980); the era of the {PDP-10}, {TECO}, {{ITS}}, and the ARPANET. This term has been rather consciously adopted from J. R. R. Tolkien's fantasy epic "The Lord of the Rings". Compare {Iron Age}; see also {elvish} and {Great Worm, the}.

:elegant: /adj./ [from mathematical usage] Combining simplicity, power, and a certain ineffable grace of design. Higher praise than `clever', `winning', or even {cuspy}.

The French aviator, adventurer, and author Antoine de Saint-Exup'ery, probably best known for his classic children's book "The Little Prince", was also an aircraft designer. He gave us perhaps the best definition of engineering elegance when he said "A designer knows he has achieved perfection not when there is nothing left to add, but when there is nothing left to take away."

:elephantine: /adj./ Used of programs or systems that are both conspicuous {hog}s (owing perhaps to poor design founded on {brute force and ignorance}) and exceedingly {hairy} in source form. An elephantine program may be functional and even friendly, but (as in the old joke about being in bed with an elephant) it's tough to have around all the same (and, like a pachyderm, difficult to maintain). In extreme cases, hackers have been known to make trumpeting sounds or perform expressive proboscatory mime at the mention of the offending program. Usage: semi-humorous. Compare `has the elephant nature' and the somewhat more pejorative {monstrosity}. See also {second-system effect} and {baroque}.

:elevator controller: /n./ An archetypal dumb embedded-systems application, like {toaster} (which superseded it). During one period (1983—84) in the deliberations of ANSI X3J11 (the C standardization committee) this was the canonical example of a really stupid, memory-limited computation environment. "You can't require `printf(3)' to be part of the default runtime library — what if you're targeting an elevator controller?" Elevator controllers became important rhetorical weapons on both sides of several {holy wars}.

:elite: /adj./ Clueful. Plugged-in. One of the cognoscenti.
Also used as a general positive adjective. This term is not
actually hacker slang in the strict sense; it is used primarily by
crackers and {warez d00dz}. Cracker usage is probably related to
a 19200cps modem called the `Courier Elite' that was widely popular
on pirate boards before the V.32bis standard. A true hacker would
be more likely to use `wizardly'. Oppose {lamer}.

:ELIZA effect: /*-li:'z* *-fekt'/ /n./ [AI community] The
tendency of humans to attach associations to terms from prior
experience. For example, there is nothing magic about the symbol
`+' that makes it well-suited to indicate addition; it's just
that people associate it with addition. Using `+' or `plus'
to mean addition in a computer language is taking advantage of the
ELIZA effect.

This term comes from the famous ELIZA program by Joseph Weizenbaum, which simulated a Rogerian psychotherapist by rephrasing many of the patient's statements as questions and posing them to the patient. It worked by simple pattern recognition and substitution of key words into canned phrases. It was so convincing, however, that there are many anecdotes about people becoming very emotionally caught up in dealing with ELIZA. All this was due to people's tendency to attach to words meanings which the computer never put there. The ELIZA effect is a {Good Thing} when writing a programming language, but it can blind you to serious shortcomings when analyzing an Artificial Intelligence system. Compare {ad-hockery}; see also {AI-complete}.

:elvish: /n./ 1. The Tengwar of Feanor, a table of letterforms resembling the beautiful Celtic half-uncial hand of the "Book of Kells". Invented and described by J. R. R. Tolkien in "The Lord of The Rings" as an orthography for his fictional `elvish' languages, this system (which is both visually and phonetically {elegant}) has long fascinated hackers (who tend to be intrigued by artificial languages in general). It is traditional for graphics printers, plotters, window systems, and the like to support a Feanorian typeface as one of their demo items. See also {elder days}. 2. By extension, any odd or unreadable typeface produced by a graphics device. 3. The typeface mundanely called `B"ocklin', an art-decoish display font.

:EMACS: /ee'maks/ /n./ [from Editing MACroS] The ne plus ultra of hacker editors, a programmable text editor with an entire LISP system inside it. It was originally written by Richard Stallman in {TECO} under {{ITS}} at the MIT AI lab; AI Memo 554 described it as "an advanced, self-documenting, customizable, extensible real-time display editor". It has since been reimplemented any number of times, by various hackers, and versions exist that run under most major operating systems. Perhaps the most widely used version, also written by Stallman and now called "{GNU} EMACS" or {GNUMACS}, runs principally under Unix. It includes facilities to run compilation subprocesses and send and receive mail; many hackers spend up to 80% of their {tube time} inside it. Other variants include {GOSMACS}, CCA EMACS, UniPress EMACS, Montgomery EMACS, jove, epsilon, and MicroEMACS.

Some EMACS versions running under window managers iconify as an overflowing kitchen sink, perhaps to suggest the one feature the editor does not (yet) include. Indeed, some hackers find EMACS too {heavyweight} and {baroque} for their taste, and expand the name as `Escape Meta Alt Control Shift' to spoof its heavy reliance on keystrokes decorated with {bucky bits}. Other spoof expansions include `Eight Megabytes And Constantly Swapping', `Eventually `malloc's All Computer Storage', and `EMACS Makes A Computer Slow' (see {{recursive acronym}}). See also {vi}.

:email: /ee'mayl/ (also written `e-mail' and `E-mail') 1. /n./ Electronic mail automatically passed through computer networks and/or via modems over common-carrier lines. Contrast {snail-mail}, {paper-net}, {voice-net}. See {network address}. 2. /vt./ To send electronic mail.

Oddly enough, the word `emailed' is actually listed in the OED; it means "embossed (with a raised pattern) or perh. arranged in a net or open work". A use from 1480 is given. The word is probably derived from French `'emaill'e' (enameled) and related to Old French `emmaille"ure' (network). A French correspondent tells us that in modern French, `email' is a hard enamel obtained by heating special paints in a furnace; an `emailleur' (no final e) is a craftsman who makes email (he generally paints some objects (like, say, jewelry) and cooks them in a furnace).

There are numerous spelling variants of this word. In Internet traffic up to 1995, `email' predominates, `e-mail' runs a not-too-distant second, and `E-mail' and `Email' are a distant third and fourth.

:emoticon: /ee-moh'ti-kon/ /n./ An ASCII glyph used to indicate an emotional state in email or news. Although originally intended mostly as jokes, emoticons (or some other explicit humor indication) are virtually required under certain circumstances in high-volume text-only communication forums such as Usenet; the lack of verbal and visual cues can otherwise cause what were intended to be humorous, sarcastic, ironic, or otherwise non-100%-serious comments to be badly misinterpreted (not always even by {newbie}s), resulting in arguments and {flame war}s.

Hundreds of emoticons have been proposed, but only a few are in
common use. These include:

:-)
`smiley face' (for humor, laughter, friendliness,
occasionally sarcasm)

:-(
`frowney face' (for sadness, anger, or upset)

;-)
`half-smiley' ({ha ha only serious}); also known as
`semi-smiley' or `winkey face'.

:-/
`wry face'

(These may become more comprehensible if you tilt your head
sideways, to the left.)

The first two listed are by far the most frequently encountered. Hyphenless forms of them are common on CompuServe, GEnie, and BIX; see also {bixie}. On {Usenet}, `smiley' is often used as a generic term synonymous with {emoticon}, as well as specifically for the happy-face emoticon.

It appears that the emoticon was invented by one Scott Fahlman on the CMU {bboard} systems around 1980. He later wrote: "I wish I had saved the original post, or at least recorded the date for posterity, but I had no idea that I was starting something that would soon pollute all the world's communication channels." [GLS confirms that he remembers this original posting].

Note for the {newbie}: Overuse of the smiley is a mark of loserhood! More than one per paragraph is a fairly sure sign that you've gone over the line.

:empire: /n./ Any of a family of military simulations derived from a game written by Peter Langston many years ago. Five or six multi-player variants of varying degrees of sophistication exist, and one single-player version implemented for both Unix and VMS; the latter is even available as MS-DOS freeware. All are notoriously addictive.

:engine: /n./ 1. A piece of hardware that encapsulates some function but can't be used without some kind of {front end}. Today we have, especially, `print engine': the guts of a laser printer. 2. An analogous piece of software; notionally, one that does a lot of noisy crunching, such as a `database engine'.

The hackish senses of `engine' are actually close to its original, pre-Industrial-Revolution sense of a skill, clever device, or instrument (the word is cognate to `ingenuity'). This sense had not been completely eclipsed by the modern connotation of power-transducing machinery in Charles Babbage's time, which explains why he named the stored-program computer that he designed in 1844 the `Analytical Engine'.

:English: 1. /n. obs./ The source code for a program, which may be in any language, as opposed to the linkable or executable binary produced from it by a compiler. The idea behind the term is that to a real hacker, a program written in his favorite programming language is at least as readable as English. Usage: mostly by old-time hackers, though recognizable in context. 2. The official name of the database language used by the Pick Operating System, actually a sort of crufty, brain-damaged SQL with delusions of grandeur. The name permits {marketroid}s to say "Yes, and you can program our computers in English!" to ignorant {suit}s without quite running afoul of the truth-in-advertising laws.

:enhancement: /n./ Common {marketroid}-speak for a bug {fix}. This abuse of language is a popular and time-tested way to turn incompetence into increased revenue. A hacker being ironic would instead call the fix a {feature} — or perhaps save some effort by declaring the bug itself to be a feature.

:ENQ: /enkw/ or /enk/ [from the ASCII mnemonic ENQuire for 0000101] An on-line convention for querying someone's availability. After opening a {talk mode} connection to someone apparently in heavy hack mode, one might type `SYN SYN ENQ?' (the SYNs representing notional synchronization bytes), and expect a return of {ACK} or {NAK} depending on whether or not the person felt interruptible. Compare {ping}, {finger}, and the usage of `FOO?' listed under {talk mode}.

:EOF: /E-O-F/ /n./ [abbreviation, `End Of File'] 1. [techspeak] The {out-of-band} value returned by C's sequential character-input functions (and their equivalents in other environments) when end of file has been reached. This value is -1 under C libraries postdating V6 Unix, but was originally 0. 2. [Unix] The keyboard character (usually control-D, the ASCII EOT (End Of Transmission) character) that is mapped by the terminal driver into an end-of-file condition. 3. Used by extension in non-computer contexts when a human is doing something that can be modeled as a sequential read and can't go further. "Yeah, I looked for a list of 360 mnemonics to post as a joke, but I hit EOF pretty fast; all the library had was a {JCL} manual." See also {EOL}.

:EOL: /E-O-L/ /n./ [End Of Line] Syn. for {newline}, derived perhaps from the original CDC6600 Pascal. Now rare, but widely recognized and occasionally used for brevity. Used in the example entry under {BNF}. See also {EOF}.

:EOU: /E-O-U/ /n./ The mnemonic of a mythical ASCII control character (End Of User) that would make an ASR-33 Teletype explode on receipt. This construction parodies the numerous obscure delimiter and control characters left in ASCII from the days when it was associated more with wire-service teletypes than computers (e.g., FS, GS, RS, US, EM, SUB, ETX, and esp. EOT). It is worth remembering that ASR-33s were big, noisy mechanical beasts with a lot of clattering parts; the notion that one might explode was nowhere near as ridiculous as it might seem to someone sitting in front of a {tube} or flatscreen today.

:epoch: /n./ [Unix: prob. from astronomical timekeeping] The time and date corresponding to 0 in an operating system's clock and timestamp values. Under most Unix versions the epoch is 00:00:00 GMT, January 1, 1970; under VMS, it's 00:00:00 of November 17, 1858 (base date of the U.S. Naval Observatory's ephemerides); on a Macintosh, it's the midnight beginning January 1 1904. System time is measured in seconds or {tick}s past the epoch. Weird problems may ensue when the clock wraps around (see {wrap around}), which is not necessarily a rare event; on systems counting 10 ticks per second, a signed 32-bit count of ticks is good only for 6.8 years. The 1-tick-per-second clock of Unix is good only until January 18, 2038, assuming at least some software continues to consider it signed and that word lengths don't increase by then. See also {wall time}.

:epsilon: [see {delta}] 1. /n./ A small quantity of anything. "The cost is epsilon." 2. /adj./ Very small, negligible; less than {marginal}. "We can get this feature for epsilon cost." 3. `within epsilon of': close enough to be indistinguishable for all practical purposes, even closer than being `within delta of'. "That's not what I asked for, but it's within epsilon of what I wanted." Alternatively, it may mean not close enough, but very little is required to get it there: "My program is within epsilon of working."

:epsilon squared: /n./ A quantity even smaller than {epsilon}, as small in comparison to epsilon as epsilon is to something normal; completely negligible. If you buy a supercomputer for a million dollars, the cost of the thousand-dollar terminal to go with it is {epsilon}, and the cost of the ten-dollar cable to connect them is epsilon squared. Compare {lost in the underflow}, {lost in the noise}.

:era, the: /n./ Syn. {epoch}. Webster's Unabridged makes these words almost synonymous, but `era' more often connotes a span of time rather than a point in time, whereas the reverse is true for {epoch}. The {epoch} usage is recommended.

:Eric Conspiracy: /n./ A shadowy group of mustachioed hackers named Eric first pinpointed as a sinister conspiracy by an infamous talk.bizarre posting ca. 1987; this was doubtless influenced by the numerous `Eric' jokes in the Monty Python oeuvre. There do indeed seem to be considerably more mustachioed Erics in hackerdom than the frequency of these three traits can account for unless they are correlated in some arcane way. Well-known examples include Eric Allman (he of the `Allman style' described under {indent style}) and Erik Fair (co-author of NNTP); your editor has heard from about fifteen others by email, and the organization line `Eric Conspiracy Secret Laboratories' now emanates regularly from more than one site. See the Eric Conspiracy Web Page at http://www.ccil.org/~esr/ecsl.html for full details.

:Eris: /e'ris/ /n./ The Greek goddess of Chaos, Discord, Confusion, and Things You Know Not Of; her name was latinized to Discordia and she was worshiped by that name in Rome. Not a very friendly deity in the Classical original, she was reinvented as a more benign personification of creative anarchy starting in 1959 by the adherents of {Discordianism} and has since been a semi-serious subject of veneration in several `fringe' cultures, including hackerdom. See {Discordianism}, {Church of the SubGenius}.

:erotics: /ee-ro'tiks/ /n./ [Helsinki University of
Technology, Finland] /n./ English-language university slang for
electronics. Often used by hackers in Helsinki, maybe because good
electronics excites them and makes them warm.

:error 33: [XEROX PARC] /n./ 1. Predicating one research effort
upon the success of another. 2. Allowing your own research effort
to be placed on the critical path of some other project (be it a
research effort or not).

:evil: /adj./ As used by hackers, implies that some system, program, person, or institution is sufficiently maldesigned as to be not worth the bother of dealing with. Unlike the adjectives in the {cretinous}/{losing}/{brain-damaged} series, `evil' does not imply incompetence or bad design, but rather a set of goals or design criteria fatally incompatible with the speaker's. This usage is more an esthetic and engineering judgment than a moral one in the mainstream sense. "We thought about adding a {Blue Glue} interface but decided it was too evil to deal with." "{TECO} is neat, but it can be pretty evil if you're prone to typos." Often pronounced with the first syllable lengthened, as /eeee'vil/. Compare {evil and rude}.

:evil and rude: /adj./ Both {evil} and {rude}, but with the additional connotation that the rudeness was due to malice rather than incompetence. Thus, for example: Microsoft's Windows NT is evil because it's a competent implementation of a bad design; it's rude because it's gratuitously incompatible with Unix in places where compatibility would have been as easy and effective to do; but it's evil and rude because the incompatibilities are apparently there not to fix design bugs in Unix but rather to lock hapless customers and developers into the Microsoft way. Hackish evil and rude is close to the mainstream sense of `evil'.

:exa-: /ek's*/ /pref./ [SI] See {{quantifiers}}.

:examining the entrails: /n./ The process of {grovel}ling through a {core dump} or hex image in an attempt to discover the bug that brought a program or system down. The reference is to divination from the entrails of a sacrified animal. Compare {runes}, {incantation}, {black art}, {desk check}.

:EXCH: /eks'ch*/ or /eksch/ /vt./ To exchange two things, each for the other; to swap places. If you point to two people sitting down and say "Exch!", you are asking them to trade places. EXCH, meaning EXCHange, was originally the name of a PDP-10 instruction that exchanged the contents of a register and a memory location. Many newer hackers are probably thinking instead of the {{PostScript}} exchange operator (which is usually written in lowercase).

:excl: /eks'kl/ /n./ Abbreviation for `exclamation point'. See {bang}, {shriek}, {{ASCII}}.

:EXE: /eks'ee/ or /eek'see/ or /E-X-E/ /n./ An executable binary file. Some operating systems (notably MS-DOS, VMS, and TWENEX) use the extension .EXE to mark such files. This usage is also occasionally found among Unix programmers even though Unix executables don't have any required suffix.

:exec: /eg-zek'/ or /eks'ek/ vt., /n./ 1. [Unix: from `execute'] Synonym for {chain}, derives from the `exec(2)' call. 2. [from `executive'] obs. The command interpreter for an {OS} (see {shell}); term esp. used around mainframes, and prob. derived from UNIVAC's archaic EXEC 2 and EXEC 8 operating systems. 3. At IBM and VM/CMS shops, the equivalent of a shell command file (among VM/CMS users).

The mainstream `exec' as an abbreviation for (human) executive is *not* used. To a hacker, an `exec' is a always a program, never a person.

:exercise, left as an: /adj./ [from technical books] Used to complete a proof when one doesn't mind a {handwave}, or to avoid one entirely. The complete phrase is: "The proof [or `the rest'] is left as an exercise for the reader." This comment *has* occasionally been attached to unsolved research problems by authors possessed of either an evil sense of humor or a vast faith in the capabilities of their audiences.

:Exon: /eks'on/ /excl./ A generic obscenity that quickly
entered wide use on the Internet and Usenet after {Black
Thursday}. From the last name of Senator James Exon
(Democrat-Nevada), primary author of the {CDA}.

:external memory: /n./ A memo pad, palmtop computer, or written
notes. "Hold on while I write that to external memory". The
analogy is with store or DRAM versus nonvolatile disk storage on
computers.

:eye candy: /i:' kand`ee/ /n./ [from mainstream slang
"ear candy"] A display of some sort that's presented to {luser}s
to keep them distracted while the program performs necessary
background tasks. "Give 'em some eye candy while the back-end
{slurp}s that {BLOB} into core."

:eyeball search: /n.,v./ To look for something in a mass of
code or data with one's own native optical sensors, as opposed to
using some sort of pattern matching software like {grep} or any
other automated search tool. Also called a {vgrep}; compare
{vdiff}, {desk check}.

= F = =====

:face time: /n./ Time spent interacting with somebody face-to-face (as opposed to via electronic links). "Oh, yeah, I spent some face time with him at the last Usenix."

:factor: /n./ See {coefficient of X}.

:fall over: /vi./ [IBM] Yet another synonym for {crash} or {lose}. `Fall over hard' equates to {crash and burn}.

:fall through: /v./ (n. `fallthrough', var. `fall-through') 1. To exit a loop by exhaustion, i.e., by having fulfilled its exit condition rather than via a break or exception condition that exits from the middle of it. This usage appears to be *really* old, dating from the 1940s and 1950s. 2. To fail a test that would have passed control to a subroutine or some other distant portion of code. 3. In C, `fall-through' occurs when the flow of execution in a switch statement reaches a `case' label other than by jumping there from the switch header, passing a point where one would normally expect to find a `break'. A trivial example:

switch (color)
{
case GREEN:
do_green;
break;
case PINK:
do_pink;
/* FALL THROUGH */
case RED:
do_red;
break;
default:
do_blue;
break;
}

The variant spelling `/* FALL THRU */' is also common.

The effect of the above code is to `do_green' when color is `GREEN', `do_red' when color is `RED', `do_blue' on any other color other than `PINK', and (and this is the important part) `do_pink' *and then* `do_red' when color is `PINK'. Fall-through is {considered harmful} by some, though there are contexts (such as the coding of state machines) in which it is natural; it is generally considered good practice to include a comment highlighting the fall-through where one would normally expect a break. See also {Duff's device}.

:fan: /n./ Without qualification, indicates a fan of science fiction, especially one who goes to {con}s and tends to hang out with other fans. Many hackers are fans, so this term has been imported from fannish slang; however, unlike much fannish slang it is recognized by most non-fannish hackers. Among SF fans the plural is correctly `fen', but this usage is not automatic to hackers. "Laura reads the stuff occasionally but isn't really a fan."

:fandango on core: /n./ [Unix/C hackers, from the Mexican dance] In C, a wild pointer that runs out of bounds, causing a {core dump}, or corrupts the `malloc(3)' {arena} in such a way as to cause mysterious failures later on, is sometimes said to have `done a fandango on core'. On low-end personal machines without an MMU, this can corrupt the OS itself, causing massive lossage. Other frenetic dances such as the rhumba, cha-cha, or watusi, may be substituted. See {aliasing bug}, {precedence lossage}, {smash the stack}, {memory leak}, {memory smash}, {overrun screw}, {core}.

:FAQ: /F-A-Q/ or /fak/ /n./ [Usenet] 1. A Frequently Asked Question. 2. A compendium of accumulated lore, posted periodically to high-volume newsgroups in an attempt to forestall such questions. Some people prefer the term `FAQ list' or `FAQL' /fa'kl/, reserving `FAQ' for sense 1.

This lexicon itself serves as a good example of a collection of one kind of lore, although it is far too big for a regular FAQ posting. Examples: "What is the proper type of NULL?" and "What's that funny name for the `#' character?" are both Frequently Asked Questions. Several FAQs refer readers to this file.

:FAQ list: /F-A-Q list/ or /fak list/ /n./ [Usenet] Syn
{FAQ}, sense 2.

:FAQL: /fa'kl/ /n./ Syn. {FAQ list}.

:faradize: /far'*-di:z/ /v./ [US Geological Survey] To start any hyper-addictive process or trend, or to continue adding current to such a trend. Telling one user about a new octo-tetris game you compiled would be a faradizing act — in two weeks you might find your entire department playing the faradic game.

:farkled: /far'kld/ /adj./ [DeVry Institute of Technology, Atlanta] Syn. {hosed}. Poss. owes something to Yiddish `farblondjet' and/or the `Farkle Family' skits on "Rowan and Martin's Laugh-In", a popular comedy show of the late 1960s.

:farming: /n./ [Adelaide University, Australia] What the heads of a disk drive are said to do when they plow little furrows in the magnetic media. Associated with a {crash}. Typically used as follows: "Oh no, the machine has just crashed; I hope the hard drive hasn't gone {farming} again."

:fascist: /adj./ 1. Said of a computer system with excessive or annoying security barriers, usage limits, or access policies. The implication is that said policies are preventing hackers from getting interesting work done. The variant `fascistic' seems to have been preferred at MIT, poss. by analogy with `touristic' (see {tourist}). 2. In the design of languages and other software tools, `the fascist alternative' is the most restrictive and structured way of capturing a particular function; the implication is that this may be desirable in order to simplify the implementation or provide tighter error checking. Compare {bondage-and-discipline language}, although that term is global rather than local.

:fat electrons: /n./ Old-time hacker David Cargill's theory on the causation of computer glitches. Your typical electric utility draws its line current out of the big generators with a pair of coil taps located near the top of the dynamo. When the normal tap brushes get dirty, they take them off line to clean them up, and use special auxiliary taps on the *bottom* of the coil. Now, this is a problem, because when they do that they get not ordinary or `thin' electrons, but the fat'n'sloppy electrons that are heavier and so settle to the bottom of the generator. These flow down ordinary wires just fine, but when they have to turn a sharp corner (as in an integrated-circuit via), they're apt to get stuck. This is what causes computer glitches. [Fascinating. Obviously, fat electrons must gain mass by {bogon} absorption —ESR] Compare {bogon}, {magic smoke}.

:faulty: /adj./ Non-functional; buggy. Same denotation as {bletcherous}, {losing}, q.v., but the connotation is much milder.

:fd leak: /F-D leek/ /n./ A kind of programming bug analogous to a {core leak}, in which a program fails to close file descriptors (`fd's) after file operations are completed, and thus eventually runs out of them. See {leak}.

:fear and loathing: /n./ [from Hunter S. Thompson] A state inspired by the prospect of dealing with certain real-world systems and standards that are totally {brain-damaged} but ubiquitous — Intel 8086s, or {COBOL}, or {{EBCDIC}}, or any {IBM} machine except the Rios (a.k.a. the RS/6000). "Ack! They want PCs to be able to talk to the AI machine. Fear and loathing time!"

:feature: /n./ 1. A good property or behavior (as of a program). Whether it was intended or not is immaterial. 2. An intended property or behavior (as of a program). Whether it is good or not is immaterial (but if bad, it is also a {misfeature}). 3. A surprising property or behavior; in particular, one that is purposely inconsistent because it works better that way — such an inconsistency is therefore a {feature} and not a {bug}. This kind of feature is sometimes called a {miswart}; see that entry for a classic example. 4. A property or behavior that is gratuitous or unnecessary, though perhaps also impressive or cute. For example, one feature of Common LISP's `format' function is the ability to print numbers in two different Roman-numeral formats (see {bells, whistles, and gongs}). 5. A property or behavior that was put in to help someone else but that happens to be in your way. 6. A bug that has been documented. To call something a feature sometimes means the author of the program did not consider the particular case, and that the program responded in a way that was unexpected but not strictly incorrect. A standard joke is that a bug can be turned into a {feature} simply by documenting it (then theoretically no one can complain about it because it's in the manual), or even by simply declaring it to be good. "That's not a bug, that's a feature!" is a common catchphrase. See also {feetch feetch}, {creeping featurism}, {wart}, {green lightning}.

The relationship among bugs, features, misfeatures, warts, and miswarts might be clarified by the following hypothetical exchange between two hackers on an airliner:

A: "This seat doesn't recline."

B: "That's not a bug, that's a feature. There is an emergency exit door built around the window behind you, and the route has to be kept clear."

A: "Oh. Then it's a misfeature; they should have increased the spacing between rows here."

B: "Yes. But if they'd increased spacing in only one section it would have been a wart — they would've had to make nonstandard-length ceiling panels to fit over the displaced seats."

A: "A miswart, actually. If they increased spacing throughout they'd lose several rows and a chunk out of the profit margin. So unequal spacing would actually be the Right Thing."

B: "Indeed."

`Undocumented feature' is a common, allegedly humorous euphemism for a {bug}. There's a related joke that is sometimes referred to as the "one-question geek test". You say to someone "I saw a Volkswagen Beetle today with a vanity license plate that read FEATURE". If he/she laughs, he/she is a geek (see {computer geek}, sense #2).

:feature creature: /n./ [poss. fr. slang `creature feature' for a horror movie] 1. One who loves to add features to designs or programs, perhaps at the expense of coherence, concision, or {taste}. 2. Alternately, a mythical being that induces otherwise rational programmers to perpetrate such crocks. See also {feeping creaturism}, {creeping featurism}.

:feature key: /n./ The Macintosh key with the cloverleaf graphic on its keytop; sometimes referred to as `flower', `pretzel', `clover', `propeller', `beanie' (an apparent reference to the major feature of a propeller beanie), {splat}, or the `command key'. The Mac's equivalent of an {alt} key. The proliferation of terms for this creature may illustrate one subtle peril of iconic interfaces.

Many people have been mystified by the cloverleaf-like symbol that appears on the feature key. Its oldest name is `cross of St. Hannes', but it occurs in pre-Christian Viking art as a decorative motif. Throughout Scandinavia today the road agencies use it to mark sites of historical interest. Apple picked up the symbol from an early Mac developer who happened to be Swedish. Apple documentation gives the translation "interesting feature"!

There is some dispute as to the proper (Swedish) name of this symbol. It technically stands for the word `sev"ardhet' (interesting feature); many of these are old churches. Some Swedes report as an idiom for it the word `kyrka', cognate to English `church' and Scots-dialect `kirk' but pronounced /shir'k*/ in modern Swedish. Others say this is nonsense. Another idiom reported for the sign is `runsten' /roon'stn/, derived from the fact that many of the interesting features are Viking rune-stones.

:feature shock: /n./ [from Alvin Toffler's book title "Future Shock"] A user's (or programmer's!) confusion when confronted with a package that has too many features and poor introductory material.

:featurectomy: /fee`ch*r-ek't*-mee/ /n./ The act of removing a feature from a program. Featurectomies come in two flavors, the `righteous' and the `reluctant'. Righteous featurectomies are performed because the remover believes the program would be more elegant without the feature, or there is already an equivalent and better way to achieve the same end. (Doing so is not quite the same thing as removing a {misfeature}.) Reluctant featurectomies are performed to satisfy some external constraint such as code size or execution speed.

:feep: /feep/ 1. /n./ The soft electronic `bell' sound of a display terminal (except for a VT-52); a beep (in fact, the microcomputer world seems to prefer {beep}). 2. /vi./ To cause the display to make a feep sound. ASR-33s (the original TTYs) do not feep; they have mechanical bells that ring. Alternate forms: {beep}, `bleep', or just about anything suitably onomatopoeic. (Jeff MacNelly, in his comic strip "Shoe", uses the word `eep' for sounds made by computer terminals and video games; this is perhaps the closest written approximation yet.) The term `breedle' was sometimes heard at SAIL, where the terminal bleepers are not particularly soft (they sound more like the musical equivalent of a raspberry or Bronx cheer; for a close approximation, imagine the sound of a Star Trek communicator's beep lasting for five seconds). The `feeper' on a VT-52 has been compared to the sound of a '52 Chevy stripping its gears. See also {ding}.

:feeper: /fee'pr/ /n./ The device in a terminal or
workstation (usually a loudspeaker of some kind) that makes the
{feep} sound.

:feeping creature: /n./ [from {feeping creaturism}] An
unnecessary feature; a bit of {chrome} that, in the speaker's
judgment, is the camel's nose for a whole horde of new features.

:feeping creaturism: /fee'ping kree`ch*r-izm/ /n./ A deliberate spoonerism for {creeping featurism}, meant to imply that the system or program in question has become a misshapen creature of hacks. This term isn't really well defined, but it sounds so neat that most hackers have said or heard it. It is probably reinforced by an image of terminals prowling about in the dark making their customary noises.

:feetch feetch: /feech feech/ /interj./ If someone tells you about some new improvement to a program, you might respond: "Feetch, feetch!" The meaning of this depends critically on vocal inflection. With enthusiasm, it means something like "Boy, that's great! What a great hack!" Grudgingly or with obvious doubt, it means "I don't know; it sounds like just one more unnecessary and complicated thing". With a tone of resignation, it means, "Well, I'd rather keep it simple, but I suppose it has to be done".

:fence: /n./ 1. A sequence of one or more distinguished ({out-of-band}) characters (or other data items), used to delimit a piece of data intended to be treated as a unit (the computer-science literature calls this a `sentinel'). The NUL (ASCII 0000000) character that terminates strings in C is a fence. Hex FF is also (though slightly less frequently) used this way. See {zigamorph}. 2. An extra data value inserted in an array or other data structure in order to allow some normal test on the array's contents also to function as a termination test. For example, a highly optimized routine for finding a value in an array might artificially place a copy of the value to be searched for after the last slot of the array, thus allowing the main search loop to search for the value without having to check at each pass whether the end of the array had been reached. 3. [among users of optimizing compilers] Any technique, usually exploiting knowledge about the compiler, that blocks certain optimizations. Used when explicit mechanisms are not available or are overkill. Typically a hack: "I call a dummy procedure there to force a flush of the optimizer's register-coloring info" can be expressed by the shorter "That's a fence procedure".

:fencepost error: /n./ 1. A problem with the discrete equivalent of a boundary condition, often exhibited in programs by iterative loops. From the following problem: "If you build a fence 100 feet long with posts 10 feet apart, how many posts do you need?" (Either 9 or 11 is a better answer than the obvious 10.) For example, suppose you have a long list or array of items, and want to process items m through n; how many items are there? The obvious answer is n - m, but that is off by one; the right answer is n - m + 1. A program that used the `obvious' formula would have a fencepost error in it. See also {zeroth} and {off-by-one error}, and note that not all off-by-one errors are fencepost errors. The game of Musical Chairs involves a catastrophic off-by-one error where N people try to sit in N - 1 chairs, but it's not a fencepost error. Fencepost errors come from counting things rather than the spaces between them, or vice versa, or by neglecting to consider whether one should count one or both ends of a row. 2. [rare] An error induced by unexpected regularities in input values, which can (for instance) completely thwart a theoretically efficient binary tree or hash table implementation. (The error here involves the difference between expected and worst case behaviors of an algorithm.)

:fepped out: /fept owt/ /adj./ The Symbolics 3600 LISP Machine has a Front-End Processor called a `FEP' (compare sense 2 of {box}). When the main processor gets {wedged}, the FEP takes control of the keyboard and screen. Such a machine is said to have `fepped out' or `dropped into the fep'.

:FidoNet: /n./ A worldwide hobbyist network of personal computers which exchanges mail, discussion groups, and files. Founded in 1984 and originally consisting only of IBM PCs and compatibles, FidoNet now includes such diverse machines as Apple ][s, Ataris, Amigas, and Unix systems. FidoNet has grown rapidly and in early 1996 has approximately 38000 nodes.

:field circus: /n./ [a derogatory pun on `field service'] The field service organization of any hardware manufacturer, but especially DEC. There is an entire genre of jokes about DEC field circus engineers:

Q: How can you recognize a DEC field circus engineer
with a flat tire?
A: He's changing one tire at a time to see which one is flat.

Q: How can you recognize a DEC field circus engineer
who is out of gas?
A: He's changing one tire at a time to see which one is flat.

[See {Easter egging} for additional insight on these jokes.]

There is also the `Field Circus Cheer' (from the {plan file} for
DEC on MIT-AI):

Maynard! Maynard!
Don't mess with us!
We're mean and we're tough!
If you get us confused
We'll screw up your stuff.

(DEC's service HQ is located in Maynard, Massachusetts.)

:field servoid: [play on `android'] /fee'ld ser'voyd/ /n./
Representative of a field service organization (see {field
circus}). This has many of the implications of {droid}.

:Fight-o-net: /n./ [FidoNet] Deliberate distortion of {FidoNet},
often applied after a flurry of {flamage} in a particular
{echo}, especially the SYSOP echo or Fidonews (see {'Snooze}).

:File Attach: [FidoNet] 1. /n./ A file sent along with a mail
message from one BBS to another. 2. /vt./ Sending someone a file
by
using the File Attach option in a BBS mailer.

:File Request: [FidoNet] 1. /n./ The {FidoNet} equivalent of {FTP}, in which one BBS system automatically dials another and {snarf}s one or more files. Often abbreviated `FReq'; files are often announced as being "available for FReq" in the same way that files are announced as being "available for/by anonymous FTP" on the Internet. 2. /vt./ The act of getting a copy of a file by using the File Request option of the BBS mailer.

:file signature: /n./ A {magic number}, sense 3.

:filk: /filk/ /n.,v./ [from SF fandom, where a typo for `folk' was adopted as a new word] A popular or folk song with lyrics revised or completely new lyrics, intended for humorous effect when read, and/or to be sung late at night at SF conventions. There is a flourishing subgenre of these called `computer filks', written by hackers and often containing rather sophisticated technical humor. See {double bucky} for an example. Compare {grilf}, {hing} and {newsfroup}.

:film at 11: [MIT: in parody of TV newscasters] 1. Used in conversation to announce ordinary events, with a sarcastic implication that these events are earth-shattering. "{{ITS}} crashes; film at 11." "Bug found in scheduler; film at 11." 2. Also widely used outside MIT to indicate that additional information will be available at some future time, *without* the implication of anything particularly ordinary about the referenced event. For example, "The mail file server died this morning; we found garbage all over the root directory. Film at 11." would indicate that a major failure had occurred but that the people working on it have no additional information about it as yet; use of the phrase in this way suggests gently that the problem is liable to be fixed more quickly if the people doing the fixing can spend time doing the fixing rather than responding to questions, the answers to which will appear on the normal "11:00 news", if people will just be patient.

:filter: /n./ [orig. {{Unix}}, now also in {{MS-DOS}}] A program that processes an input data stream into an output data stream in some well-defined way, and does no I/O to anywhere else except possibly on error conditions; one designed to be used as a stage in a `pipeline' (see {plumbing}). Compare {sponge}.

:Finagle's Law: /n./ The generalized or `folk' version of {Murphy's Law}, fully named "Finagle's Law of Dynamic Negatives" and usually rendered "Anything that can go wrong, will". One variant favored among hackers is "The perversity of the Universe tends towards a maximum" (but see also {Hanlon's Razor}). The label `Finagle's Law' was popularized by SF author Larry Niven in several stories depicting a frontier culture of asteroid miners; this `Belter' culture professed a religion and/or running joke involving the worship of the dread god Finagle and his mad prophet Murphy. Some technical and scientific cultures (e.g., paleontologists) know it under the name `Sod's Law'; this usage may be more common in Great Britain.

:fine: /adj./ [WPI] Good, but not good enough to be {cuspy}. The word `fine' is used elsewhere, of course, but without the implicit comparison to the higher level implied by {cuspy}.

:finger: [WAITS, via BSD Unix] 1. /n./ A program that displays
information about a particular user or all users logged on the
system, or a remote system. Typically shows full name, last login
time, idle time, terminal line, and terminal location (where
applicable). May also display a {plan file} left by the user
(see also {Hacking X for Y}). 2. /vt./ To apply finger to a
username. 3. /vt./ By extension, to check a human's current state
by
any means. "Foodp?" "T!" "OK, finger Lisa and see if she's
idle." 4. Any picture (composed of ASCII characters) depicting
`the finger'. Originally a humorous component of one's plan file
to deter the curious fingerer (sense 2), it has entered the arsenal
of some {flamer}s.

:finger trouble: /n./ Mistyping, typos, or generalized keyboard incompetence (this is surprisingly common among hackers, given the amount of time they spend at keyboards). "I keep putting colons at the end of statements instead of semicolons", "Finger trouble again, eh?".

:finger-pointing syndrome: /n./ All-too-frequent result of bugs, esp. in new or experimental configurations. The hardware vendor points a finger at the software. The software vendor points a finger at the hardware. All the poor users get is the finger.

:finn: /v./ [IRC] To pull rank on somebody based on the amount
of time one has spent on {IRC}. The term derives from the fact
that IRC was originally written in Finland in 1987. There may be
some influence from the `Finn' character in William Gibson's
seminal cyberpunk novel "Count Zero", who at one point says to
another (much younger) character "I have a pair of shoes older
than you are, so shut up!"

:firebottle: /n./ A large, primitive, power-hungry active
electrical device, similar in function to a FET but constructed out
of glass, metal, and vacuum. Characterized by high cost, low
density, low reliability, high-temperature operation, and high
power dissipation. Sometimes mistakenly called a `tube' in the
U.S. or a `valve' in England; another hackish term is
{glassfet}.

:firefighting: /n./ 1. What sysadmins have to do to correct sudden operational problems. An opposite of hacking. "Been hacking your new newsreader?" "No, a power glitch hosed the network and I spent the whole afternoon fighting fires." 2. The act of throwing lots of manpower and late nights at a project, esp. to get it out before deadline. See also {gang bang}, {Mongolian Hordes technique}; however, the term `firefighting' connotes that the effort is going into chasing bugs rather than adding features.

:firehose syndrome: /n./ In mainstream folklore it is observed that trying to drink from a firehose can be a good way to rip your lips off. On computer networks, the absence or failure of flow control mechanisms can lead to situations in which the sending system sprays a massive flood of packets at an unfortunate receiving system, more than it can handle. Compare {overrun}, {buffer overflow}.

:firewall code: /n./ 1. The code you put in a system (say, a telephone switch) to make sure that the users can't do any damage. Since users always want to be able to do everything but never want to suffer for any mistakes, the construction of a firewall is a question not only of defensive coding but also of interface presentation, so that users don't even get curious about those corners of a system where they can burn themselves. 2. Any sanity check inserted to catch a {can't happen} error. Wise programmers often change code to fix a bug twice: once to fix the bug, and once to insert a firewall which would have arrested the bug before it did quite as much damage.

:firewall machine: /n./ A dedicated gateway machine with special security precautions on it, used to service outside network connections and dial-in lines. The idea is to protect a cluster of more loosely administered machines hidden behind it from {cracker}s. The typical firewall is an inexpensive micro-based Unix box kept clean of critical data, with a bunch of modems and public network ports on it but just one carefully watched connection back to the rest of the cluster. The special precautions may include threat monitoring, callback, and even a complete {iron box} keyable to particular incoming IDs or activity patterns. Syn. {flytrap}, {Venus flytrap}.

[When first coined in the mid-1980s this term was pure jargon. Now (1996) it is borderline techspeak, and may have to be dropped from this lexicon before very long —ESR]

:fireworks mode: /n./ The mode a machine is sometimes said to
be in when it is performing a {crash and burn} operation.

:firmy: /fer'mee/ /n./ Syn. {stiffy} (a 3.5-inch floppy
disk).

:fish: /n./ [Adelaide University, Australia] 1. Another {metasyntactic variable}. See {foo}. Derived originally from the Monty Python skit in the middle of "The Meaning of Life" entitled "Find the Fish". 2. A pun for `microfiche'. A microfiche file cabinet may be referred to as a `fish tank'.

:FISH queue: /n./ [acronym, by analogy with FIFO (First In, First Out)] `First In, Still Here'. A joking way of pointing out that processing of a particular sequence of events or requests has stopped dead. Also `FISH mode' and `FISHnet'; the latter may be applied to any network that is running really slowly or exhibiting extreme flakiness.

:FITNR: // /adj./ [Thinking Machines, Inc.] Fixed In The
Often Next Release. A written-only notation attached to bug
reports.
wishful thinking.

:fix: /n.,v./ What one does when a problem has been reported too many times to be ignored.

:FIXME: /imp./ A standard tag often put in C comments near a piece of code that needs work. The point of doing so is that a `grep' or a similar pattern-matching tool can find all such places quickly.

/* FIXME: note this is common in {GNU} code. */

Compare {XXX}.

:flag: /n./ A variable or quantity that can take on one of two values; a bit, particularly one that is used to indicate one of two outcomes or is used to control which of two things is to be done. "This flag controls whether to clear the screen before printing the message." "The program status word contains several flag bits." Used of humans analogously to {bit}. See also {hidden flag}, {mode bit}.

:flag day: /n./ A software change that is neither forward- nor backward-compatible, and which is costly to make and costly to reverse. "Can we install that without causing a flag day for all users?" This term has nothing to do with the use of the word {flag} to mean a variable that has two values. It came into use when a massive change was made to the {{Multics}} timesharing system to convert from the old ASCII code to the new one; this was scheduled for Flag Day (a U.S. holiday), June 14, 1966. See also {backward combatability}.

:flaky: /adj./ (var sp. `flakey') Subject to frequent {lossage}. This use is of course related to the common slang use of the word to describe a person as eccentric, crazy, or just unreliable. A system that is flaky is working, sort of — enough that you are tempted to try to use it — but fails frequently enough that the odds in favor of finishing what you start are low. Commonwealth hackish prefers {dodgy} or {wonky}.

:flamage: /flay'm*j/ /n./ Flaming verbiage, esp. high-noise, low-signal postings to {Usenet} or other electronic {fora}. Often in the phrase `the usual flamage'. `Flaming' is the act itself; `flamage' the content; a `flame' is a single flaming message. See {flame}, also {dahmum}.

:flame: 1. /vi./ To post an email message intended to insult
and provoke. 2. /vi./ To speak incessantly and/or rabidly on some
relatively uninteresting subject or with a patently ridiculous
attitude. 3. /vt./ Either of senses 1 or 2, directed with
hostility
at a particular person or people. 4. /n./ An instance of flaming.
When a discussion degenerates into useless controversy, one might
tell the participants "Now you're just flaming" or "Stop all
that flamage!" to try to get them to cool down (so to speak).

The term may have been independently invented at several different places. It has been reported from MIT, Carleton College and RPI (among many other places) from as far back as 1969.

It is possible that the hackish sense of `flame' is much older than that. The poet Chaucer was also what passed for a wizard hacker in his time; he wrote a treatise on the astrolabe, the most advanced computing device of the day. In Chaucer's "Troilus and Cressida", Cressida laments her inability to grasp the proof of a particular mathematical theorem; her uncle Pandarus then observes that it's called "the fleminge of wrecches." This phrase seems to have been intended in context as "that which puts the wretches to flight" but was probably just as ambiguous in Middle English as "the flaming of wretches" would be today. One suspects that Chaucer would feel right at home on Usenet.

:flame bait: /n./ A posting intended to trigger a {flame war}, or one that invites flames in reply. See also {troll}.

:flame on: vi.,/interj./ 1. To begin to {flame}. The punning reference to Marvel Comics's Human Torch is no longer widely recognized. 2. To continue to flame. See {rave}, {burble}.

:flame war: /n./ (var. `flamewar') An acrimonious dispute, especially when conducted on a public electronic forum such as {Usenet}.

:flamer: /n./ One who habitually {flame}s. Said esp. of obnoxious {Usenet} personalities.

:flap: /vt./ 1. To unload a DECtape (so it goes flap, flap, flap…). Old-time hackers at MIT tell of the days when the disk was device 0 and {microtape}s were 1, 2,… and attempting to flap device 0 would instead start a motor banging inside a cabinet near the disk. 2. By extension, to unload any magnetic tape. See also {macrotape}. Modern cartridge tapes no longer actually flap, but the usage has remained. (The term could well be re-applied to DEC's TK50 cartridge tape drive, a spectacularly misengineered contraption which makes a loud flapping sound, almost like an old reel-type lawnmower, in one of its many tape-eating failure modes.)

:flarp: /flarp/ /n./ [Rutgers University] Yet another {metasyntactic variable} (see {foo}). Among those who use it, it is associated with a legend that any program not containing the word `flarp' somewhere will not work. The legend is discreetly silent on the reliability of programs which *do* contain the magic word.

:flat: /adj./ 1. Lacking any complex internal structure. "That {bitty box} has only a flat filesystem, not a hierarchical one." The verb form is {flatten}. 2. Said of a memory architecture (like that of the VAX or 680x0) that is one big linear address space (typically with each possible value of a processor register corresponding to a unique core address), as opposed to a `segmented' architecture (like that of the 80x86) in which addresses are composed from a base-register/offset pair (segmented designs are generally considered {cretinous}).

Note that sense 1 (at least with respect to filesystems) is usually used pejoratively, while sense 2 is a {Good Thing}.

:flat-ASCII: /adj./ Said of a text file that contains only 7-bit ASCII characters and uses only ASCII-standard control characters (that is, has no embedded codes specific to a particular text formatter markup language, or output device, and no {meta}-characters). Syn. {plain-ASCII}. Compare {flat-file}.

:flat-file: /adj./ A {flatten}ed representation of some database or tree or network structure as a single file from which the structure could implicitly be rebuilt, esp. one in {flat-ASCII} form. See also {sharchive}.

:flatten: /vt./ To remove structural information, esp. to filter something with an implicit tree structure into a simple sequence of leaves; also tends to imply mapping to {flat-ASCII}. "This code flattens an expression with parentheses into an equivalent {canonical} form."

:flavor: /n./ 1. Variety, type, kind. "DDT commands come in two flavors." "These lights come in two flavors, big red ones and small green ones." See {vanilla}. 2. The attribute that causes something to be {flavorful}. Usually used in the phrase "yields additional flavor". "This convention yields additional flavor by allowing one to print text either right-side-up or upside-down." See {vanilla}. This usage was certainly reinforced by the terminology of quantum chromodynamics, in which quarks (the constituents of, e.g., protons) come in six flavors (up, down, strange, charm, top, bottom) and three colors (red, blue, green) — however, hackish use of `flavor' at MIT predated QCD. 3. The term for `class' (in the object-oriented sense) in the LISP Machine Flavors system. Though the Flavors design has been superseded (notably by the Common LISP CLOS facility), the term `flavor' is still used as a general synonym for `class' by some LISP hackers.

:flavorful: /adj./ Full of {flavor} (sense 2); esthetically pleasing. See {random} and {losing} for antonyms. See also the entries for {taste} and {elegant}.

:flippy: /flip'ee/ /n./ A single-sided floppy disk altered
for double-sided use by addition of a second write-notch, so called
because it must be flipped over for the second side to be
accessible. No longer common.

:flood: /v./ [IRC] To dump large amounts of text onto an
{IRC} channel. This is especially rude when the text is
uninteresting and the other users are trying to carry on a serious
conversation.

:flowchart:: /n./ [techspeak] An archaic form of visual control-flow specification employing arrows and `speech balloons' of various shapes. Hackers never use flowcharts, consider them extremely silly, and associate them with {COBOL} programmers, {card walloper}s, and other lower forms of life. This attitude follows from the observations that flowcharts (at least from a hacker's point of view) are no easier to read than code, are less precise, and tend to fall out of sync with the code (so that they either obfuscate it rather than explaining it, or require extra maintenance effort that doesn't improve the code). See also {pdl}, sense 3.

:flower key: /n./ [Mac users] See {feature key}.

:flush: /v./ 1. To delete something, usually superfluous, or to abort an operation. "All that nonsense has been flushed." 2. [Unix/C] To force buffered I/O to disk, as with an `fflush(3)' call. This is *not* an abort or deletion as in sense 1, but a demand for early completion! 3. To leave at the end of a day's work (as opposed to leaving for a meal). "I'm going to flush now." "Time to flush." 4. To exclude someone from an activity, or to ignore a person.

`Flush' was standard ITS terminology for aborting an output operation; one spoke of the text that would have been printed, but was not, as having been flushed. It is speculated that this term arose from a vivid image of flushing unwanted characters by hosing down the internal output buffer, washing the characters away before they could be printed. The Unix/C usage, on the other hand, was propagated by the `fflush(3)' call in C's standard I/O library (though it is reported to have been in use among BLISS programmers at DEC and on Honeywell and IBM machines as far back as 1965). Unix/C hackers find the ITS usage confusing, and vice versa.

:flypage: /fli:'payj/ /n./ (alt. `fly page') A {banner}, sense 1.

:Flyspeck 3: /n./ Standard name for any font that is so tiny as to be unreadable (by analogy with names like `Helvetica 10' for 10-point Helvetica). Legal boilerplate is usually printed in Flyspeck 3.

:flytrap: /n./ See {firewall machine}.

:FM: /F-M/ /n./ 1. *Not* `Frequency Modulation' but rather an abbreviation for `Fucking Manual', the back-formation from {RTFM}. Used to refer to the manual itself in the {RTFM}. "Have you seen the Networking FM lately?" 2. Abbreviation for "Fucking Magic", used in the sense of {black magic}.

:fnord: /n./ [from the "Illuminatus Trilogy"] 1. A word used in email and news postings to tag utterances as surrealist mind-play or humor, esp. in connection with {Discordianism} and elaborate conspiracy theories. "I heard that David Koresh is sharing an apartment in Argentina with Hitler. (Fnord.)" "Where can I fnord get the Principia Discordia from?" 2. A {metasyntactic variable}, commonly used by hackers with ties to {Discordianism} or the {Church of the SubGenius}.

:FOAF: // /n./ [Usenet] Acronym for `Friend Of A Friend'. The source of an unverified, possibly untrue story. This term was not originated by hackers (it is used in Jan Brunvand's books on urban folklore), but is much better recognized on Usenet and elsewhere than in mainstream English.

:FOD: /fod/ /v./ [Abbreviation for `Finger of Death', originally a spell-name from fantasy gaming] To terminate with extreme prejudice and with no regard for other people. From {MUD}s where the wizard command `FOD <player>' results in the immediate and total death of <player>, usually as punishment for obnoxious behavior. This usage migrated to other circumstances, such as "I'm going to fod the process that is burning all the cycles." Compare {gun}.

In aviation, FOD means Foreign Object Damage, e.g., what happens when a jet engine sucks up a rock on the runway or a bird in flight. Finger of Death is a distressingly apt description of what this generally does to the engine.

:fold case: /v./ See {smash case}. This term tends to be used more by people who don't mind that their tools smash case. It also connotes that case is ignored but case distinctions in data processed by the tool in question aren't destroyed.

:followup: /n./ On Usenet, a {posting} generated in response to another posting (as opposed to a {reply}, which goes by email rather than being broadcast). Followups include the ID of the {parent message} in their headers; smart news-readers can use this information to present Usenet news in `conversation' sequence rather than order-of-arrival. See {thread}.

:fontology: /n./ [XEROX PARC] The body of knowledge dealing with the construction and use of new fonts (e.g., for window systems and typesetting software). It has been said that fontology recapitulates file-ogeny.

[Unfortunately, this reference to the embryological dictum that "Ontogeny recapitulates phylogeny" is not merely a joke. On the Macintosh, for example, System 7 has to go through contortions to compensate for an earlier design error that created a whole different set of abstractions for fonts parallel to `files' and `folders' —ESR]

:foo: /foo/ 1. /interj./ Term of disgust. 2. Used very generally as a sample name for absolutely anything, esp. programs and files (esp. scratch files). 3. First on the standard list of {metasyntactic variable}s used in syntax examples. See also {bar}, {baz}, {qux}, {quux}, {corge}, {grault}, {garply}, {waldo}, {fred}, {plugh}, {xyzzy}, {thud}.

The etymology of hackish `foo' is obscure. When used in connection with `bar' it is generally traced to the WWII-era Army slang acronym FUBAR (`Fucked Up Beyond All Repair'), later bowdlerized to {foobar}. (See also {FUBAR}.)

However, the use of the word `foo' itself has more complicated antecedents, including a long history in comic strips and cartoons. The old "Smokey Stover" comic strips by Bill Holman often included the word `FOO', in particular on license plates of cars; allegedly, `FOO' and `BAR' also occurred in Walt Kelly's "Pogo" strips. In the 1938 cartoon "The Daffy Doc", a very early version of Daffy Duck holds up a sign saying "SILENCE IS FOO!"; oddly, this seems to refer to some approving or positive affirmative use of foo. It has been suggested that this might be related to the Chinese word `fu' (sometimes transliterated `foo'), which can mean "happiness" when spoken with the proper tone (the lion-dog guardians flanking the steps of many Chinese restaurants are properly called "fu dogs").

Paul Dickson's excellent book "Words" (Dell, 1982, ISBN 0-440-52260-7) traces "Foo" to an unspecified British naval magazine in 1946, quoting as follows: "Mr. Foo is a mysterious Second World War product, gifted with bitter omniscience and sarcasm."

Other sources confirm that `FOO' was a semi-legendary subject of WWII British-army graffiti more-or-less equivalent to the American Kilroy. Where British troops went, the graffito "FOO was here" or something similar showed up. Several slang dictionaries aver that FOO probably came from Forward Observation Officer. In this connection, the later American military slang `foo fighters' is interesting; at least as far back as the 1950s, radar operators used it for the kind of mysterious or spurious trace that would later be called a UFO (the older term resurfaced in popular American usage in 1995 via the name of one of the better grunge-rock bands).

Earlier versions of this entry suggested the possibility that hacker usage actually sprang from "FOO, Lampoons and Parody", the title of a comic book first issued in September 1958, a joint project of Charles and Robert Crumb. Though Robert Crumb (then in his mid-teens) later became one of the most important and influential artists in underground comics, this venture was hardly a success; indeed, the brothers later burned most of the existing copies in disgust. The title FOO was featured in large letters on the front cover. However, very few copies of this comic actually circulated, and students of Crumb's `oeuvre' have established that this title was a reference to the earlier Smokey Stover comics.

An old-time member reports that in the 1959 "Dictionary of the
TMRC Language", compiled at {TMRC}, there was an entry that went
something like this:

FOO: The first syllable of the sacred chant phrase "FOO MANE
PADME HUM." Our first obligation is to keep the foo counters
turning.

For more about the legendary foo counters, see {TMRC}. Almost
the entire staff of what later became the MIT AI Lab was involved
with TMRC, and probably picked the word up there.

Very probably, hackish `foo' had no single origin and derives
through all these channels from Yiddish `feh' and/or English
`fooey'.

:foobar: /n./ Another common {metasyntactic variable}; see
{foo}. Hackers do *not* generally use this to mean
{FUBAR} in either the slang or jargon sense.

:fool: /n./ As used by hackers, specifically describes a person who habitually reasons from obviously or demonstrably incorrect premises and cannot be persuaded by evidence to do otherwise; it is not generally used in its other senses, i.e., to describe a person with a native incapacity to reason correctly, or a clown. Indeed, in hackish experience many fools are capable of reasoning all too effectively in executing their errors. See also {cretin}, {loser}, {fool file, the}.

The Algol 68-R compiler used to initialize its storage to the character string "F00LF00LF00LF00L…" because as a pointer or as a floating point number it caused a crash, and as an integer or a character string it was very recognizable in a dump. Sadly, one day a very senior professor at Nottingham University wrote a program that called him a fool. He proceeded to demonstrate the correctness of this assertion by lobbying the university (not quite successfully) to forbid the use of Algol on its computers. See also {DEADBEEF}.

:fool file, the: /n./ [Usenet] A notional repository of all the most dramatically and abysmally stupid utterances ever. An entire subgenre of {sig block}s consists of the header "From the fool file:" followed by some quote the poster wishes to represent as an immortal gem of dimwittery; for this usage to be really effective, the quote has to be so obviously wrong as to be laughable. More than one Usenetter has achieved an unwanted notoriety by being quoted in this way.

:Foonly: /n./ 1. The {PDP-10} successor that was to have been built by the Super Foonly project at the Stanford Artificial Intelligence Laboratory along with a new operating system. The intention was to leapfrog from the old DEC timesharing system SAIL was then running to a new generation, bypassing TENEX which at that time was the ARPANET standard. ARPA funding for both the Super Foonly and the new operating system was cut in 1974. Most of the design team went to DEC and contributed greatly to the design of the PDP-10 model KL10. 2. The name of the company formed by Dave Poole, one of the principal Super Foonly designers, and one of hackerdom's more colorful personalities. Many people remember the parrot which sat on Poole's shoulder and was a regular companion. 3. Any of the machines built by Poole's company. The first was the F-1 (a.k.a. Super Foonly), which was the computational engine used to create the graphics in the movie "TRON". The F-1 was the fastest PDP-10 ever built, but only one was ever made. The effort drained Foonly of its financial resources, and the company turned towards building smaller, slower, and much less expensive machines. Unfortunately, these ran not the popular {TOPS-20} but a TENEX variant called Foonex; this seriously limited their market. Also, the machines shipped were actually wire-wrapped engineering prototypes requiring individual attention from more than usually competent site personnel, and thus had significant reliability problems. Poole's legendary temper and unwillingness to suffer fools gladly did not help matters. By the time of the Jupiter project cancellation in 1983, Foonly's proposal to build another F-1 was eclipsed by the {Mars}, and the company never quite recovered. See the {Mars} entry for the continuation and moral of this story.

:footprint: /n./ 1. The floor or desk area taken up by a piece of hardware. 2. [IBM] The audit trail (if any) left by a crashed program (often in plural, `footprints'). See also {toeprint}. 3. "RAM footprint": The minimum amount of RAM which an OS or other program takes; this figure gives one one an idea of how much will be left for other applications. How actively this RAM is used is another matter entirely. Recent tendencies to featuritis and software bloat can expand the RAM footprint of an OS to the point of making it nearly unusable in practice. [This problem is, thankfully, limited to operating systems so stupid that they don't do virtual memory — ESR]