diff options
Diffstat (limited to '3008-h')
| -rw-r--r-- | 3008-h/3008-h.htm | 51319 |
1 files changed, 51319 insertions, 0 deletions
diff --git a/3008-h/3008-h.htm b/3008-h/3008-h.htm new file mode 100644 index 0000000..6dc7f6d --- /dev/null +++ b/3008-h/3008-h.htm @@ -0,0 +1,51319 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" +"http://www.w3.org/TR/1998/REC-html40-19980424/loose.dtd"> +<html> +<head> +<meta http-equiv="content-type" content="text/html; charset=utf-8"> +<title>The Project Gutenberg Etext of The New Hacker's Dictionary version 4.2.2</title> + +<style type="text/css"> + +body { margin-left: 20%; + margin-right: 20%; + text-align: justify; } + +a:link {color:blue; text-decoration:none} +a:visited {color:blue; text-decoration:none} +a:hover {color:red} + +</style> + +</head> +<body> + +<pre> +The Project Gutenberg eBook of The New Hacker's Dictionary version 4.2.2, by various editors + +This eBook is for the use of anyone anywhere in the United States and most +other parts of the world at no cost and with almost no restrictions +whatsoever. You may copy it, give it away or re-use it under the terms of +the Project Gutenberg License included with this eBook or online at +www.gutenberg.org. If you are not located in the United States, you'll have +to check the laws of the country where you are located before using this ebook. + +Title: The New Hacker's Dictionary version 4.2.2 + +Author: Various editors + +Release Date: January, 2002 [eBook #3008] +[Most recently updated: March 28, 2023] + +Language: English + +Character set encoding: UTF-8 + +*** START OF THIS PROJECT GUTENBERG EBOOK THE NEW HACKER'S DICTIONARY 4.2.2 *** + + + + + + + + + + + +</pre> + +<hr> + +Node: <a name="Top">Top</a>, +Next: <a rel="next" href="#Introduction">Introduction</a> + +<br> + + +<p> +#======= THIS IS THE JARGON FILE, VERSION 4.2.2, 20 AUG 2000 =======# +</p> + +<p>This is the Jargon File, a comprehensive compendium of hacker +slang illuminating many aspects of hackish tradition, folklore, +and humor.</p> + +<p>This document (the Jargon File) is in the public domain, to be +freely used, shared, and modified. There are (by intention) no +legal restraints on what you can do with it, but there are +traditions about its proper use to which many hackers are quite +strongly attached. Please extend the courtesy of proper citation +when you quote the File, ideally with a version number, as it +will change and grow over time. (Examples of appropriate citation +form: "Jargon File 4.2.2" or "The on-line hacker Jargon File, +version 4.2.2, 20 AUG 2000".)</p> + +<p>The Jargon File is a common heritage of the hacker culture. +Over the years a number of individuals have volunteered +considerable time to maintaining the File and been recognized by +the net at large as editors of it. Editorial responsibilities +include: to collate contributions and suggestions from others; to +seek out corroborating information; to cross-reference related +entries; to keep the file in a consistent format; and to announce +and distribute updated versions periodically. Current volunteer +editors include:</p> + +<p> +Eric Raymond +</p> + +<p>Although there is no requirement that you do so, it is +considered good form to check with an editor before quoting the +File in a published work or commercial product. We may have +additional information that would be helpful to you and can +assist you in framing your quote to reflect not only the letter +of the File but its spirit as well.</p> + +<p>All contributions and suggestions about this file sent to a +volunteer editor are gratefully received and will be regarded, +unless otherwise labelled, as freely given donations for possible +use as part of this public-domain file.</p> + +<p>From time to time a snapshot of this file has been polished, +edited, and formatted for commercial publication with the +cooperation of the volunteer editors and the hacker community at +large. If you wish to have a bound paper copy of this file, you +may find it convenient to purchase one of these. They often +contain additional material not found in on-line versions. The +two `authorized' editions so far are described in the Revision +History section; there may be more in the future.</p> + +<ul> +<li><a href="#Introduction">Introduction</a>: The purpose and +scope of this File</li> + +<li><a href="#AFewTerms">A Few Terms</a>: Of Slang, Jargon +and Techspeak</li> + +<li><a href="#RevisionHistory">Revision History</a>: How the +File came to be</li> + +<li><a href="#JargonConstruction">Jargon Construction</a>: How +hackers invent jargon</li> + +<li><a href="#HackerWritingStyle">Hacker Writing Style</a>: +How they write</li> + +<li><a href="#EmailQuotes">Email Quotes</a>: And the Inclusion +Problem</li> + +<li><a href="#HackerSpeechStyle">Hacker Speech Style</a>: +How hackers talk</li> + +<li><a href="#InternationalStyle">International Style</a>: +Some notes on usage outside the U.S.</li> + +<li><a href="#Lamer-speak">Lamer-speak</a>: Crackers, Phreaks, +and Lamers</li> + +<li><a href="#PronunciationGuide">Pronunciation Guide</a>: How +to read the pronunciation keys</li> + +<li><a href="#OtherLexiconConventions">Other Lexicon +Conventions</a>: How to read lexicon entries</li> + +<li><a href="#FormatforNewEntries">Format for New +Entries</a>: How to submit new entries for the File</li> + +<li><a href="#TheJargonLexicon">The Jargon Lexicon</a>: The +lexicon itself</li> + +<li><a href="#AppendixA">Appendix A</a>: Hacker Folklore</li> + +<li><a href="#AppendixB">Appendix B</a>: A Portrait of J. +Random Hacker</li> + +<li><a href="#AppendixC">Appendix C</a>: Helping Hacker +Culture Grow</li> + +<li><a href="#Bibliography">Bibliography</a>: For your further +enjoyment</li> +</ul> + +<hr> + +Node:<a name="Introduction">Introduction</a>, +Next:<a rel="next" href="#AFewTerms">A Few Terms</a>, +Previous:<a rel="previous" href="#Top">Top</a>, +Up:<a rel="up" href="#Top">Top</a><br> + +<h2>Introduction</h2> + +<p>This document is a collection of slang terms used by various +subcultures of computer hackers. Though some technical material +is included for background and flavor, it is not a technical +dictionary; what we describe here is the language hackers use +among themselves for fun, social communication, and technical +debate.</p> + +<p>The `hacker culture' is actually a loosely networked +collection of subcultures that is nevertheless conscious of some +important shared experiences, shared roots, and shared values. It +has its own myths, heroes, villains, folk epics, in-jokes, +taboos, and dreams. Because hackers as a group are particularly +creative people who define themselves partly by rejection of +`normal' values and working habits, it has unusually rich and +conscious traditions for an intentional culture less than 40 +years old.</p> + +<p>As usual with slang, the special vocabulary of hackers helps +hold their culture together -- it helps hackers recognize each +other's places in the community and expresses shared values and +experiences. Also as usual, <i>not</i> knowing the slang (or +using it inappropriately) defines one as an outsider, a mundane, +or (worst of all in hackish vocabulary) possibly even a <b><a +href="#suit">suit</a></b>. All human cultures use slang in this +threefold way -- as a tool of communication, and of inclusion, +and of exclusion.</p> + +<p>Among hackers, though, slang has a subtler aspect, paralleled +perhaps in the slang of jazz musicians and some kinds of fine +artists but hard to detect in most technical or scientific +cultures; parts of it are code for shared states of +<i>consciousness</i>. There is a whole range of altered states +and problem-solving mental stances basic to high-level hacking +which don't fit into conventional linguistic reality any better +than a Coltrane solo or one of Maurits Escher's `trompe l'oeil' +compositions (Escher is a favorite of hackers), and hacker slang +encodes these subtleties in many unobvious ways. As a simple +example, take the distinction between a <b><a href="#kluge">kluge</a></b> and an <b><a href="#elegant">elegant</a></b> solution, and the differing +connotations attached to each. The distinction is not only of +engineering significance; it reaches right back into the nature +of the generative processes in program design and asserts +something important about two different kinds of relationship +between the hacker and the hack. Hacker slang is unusually rich +in implications of this kind, of overtones and undertones that +illuminate the hackish psyche.</p> + +<p>But there is more. Hackers, as a rule, love wordplay and are +very conscious and inventive in their use of language. These +traits seem to be common in young children, but the +conformity-enforcing machine we are pleased to call an +educational system bludgeons them out of most of us before +adolescence. Thus, linguistic invention in most subcultures of +the modern West is a halting and largely unconscious process. +Hackers, by contrast, regard slang formation and use as a game to +be played for conscious pleasure. Their inventions thus display +an almost unique combination of the neotenous enjoyment of +language-play with the discrimination of educated and powerful +intelligence. Further, the electronic media which knit them +together are fluid, `hot' connections, well adapted to both the +dissemination of new slang and the ruthless culling of weak and +superannuated specimens. The results of this process give us +perhaps a uniquely intense and accelerated view of linguistic +evolution in action.</p> + +<p>Hacker slang also challenges some common linguistic and +anthropological assumptions. For example, it has recently become +fashionable to speak of `low-context' versus `high-context' +communication, and to classify cultures by the preferred context +level of their languages and art forms. It is usually claimed +that low-context communication (characterized by precision, +clarity, and completeness of self-contained utterances) is +typical in cultures which value logic, objectivity, +individualism, and competition; by contrast, high-context +communication (elliptical, emotive, nuance-filled, multi-modal, +heavily coded) is associated with cultures which value +subjectivity, consensus, cooperation, and tradition. What then +are we to make of hackerdom, which is themed around extremely +low-context interaction with computers and exhibits primarily +"low-context" values, but cultivates an almost absurdly +high-context slang style?</p> + +<p>The intensity and consciousness of hackish invention make a +compilation of hacker slang a particularly effective window into +the surrounding culture -- and, in fact, this one is the latest +version of an evolving compilation called the `Jargon File', +maintained by hackers themselves for over 15 years. This one +(like its ancestors) is primarily a lexicon, but also includes +topic entries which collect background or sidelight information +on hacker culture that would be awkward to try to subsume under +individual slang definitions.</p> + +<p>Though the format is that of a reference volume, it is +intended that the material be enjoyable to browse. Even a +complete outsider should find at least a chuckle on nearly every +page, and much that is amusingly thought-provoking. But it is +also true that hackers use humorous wordplay to make strong, +sometimes combative statements about what they feel. Some of +these entries reflect the views of opposing sides in disputes +that have been genuinely passionate; this is deliberate. We have +not tried to moderate or pretty up these disputes; rather we have +attempted to ensure that <i>everyone's</i> sacred cows get +gored, impartially. Compromise is not particularly a hackish +virtue, but the honest presentation of divergent viewpoints +is.</p> + +<p>The reader with minimal computer background who finds some +references incomprehensibly technical can safely ignore them. We +have not felt it either necessary or desirable to eliminate all +such; they, too, contribute flavor, and one of this document's +major intended audiences -- fledgling hackers already partway +inside the culture -- will benefit from them.</p> + +<p>A selection of longer items of hacker folklore and humor is +included in <b><a href="#AppendixA">Appendix A</a></b>. The +`outside' reader's attention is particularly directed to the +Portrait of J. Random Hacker in <b><a href="#AppendixB">Appendix B</a></b>. Appendix C, the <b><a href="#Bibliography">Bibliography</a></b>, lists some non-technical +works which have either influenced or described the hacker +culture.</p> + +<p>Because hackerdom is an intentional culture (one each +individual must choose by action to join), one should not be +surprised that the line between description and influence can +become more than a little blurred. Earlier versions of the Jargon +File have played a central role in spreading hacker language and +the culture that goes with it to successively larger populations, +and we hope and expect that this one will do likewise.</p> + +<hr> +Node:<a name="AFewTerms">A Few Terms</a>, Next:<a rel="next" href="#RevisionHistory">Revision History</a>, +Previous:<a rel="previous" href="#Introduction">Introduction</a>, +Up:<a rel="up" href="#Top">Top</a> <br> + + +<h2>Of Slang, Jargon, and Techspeak</h2> + +<p>Linguists usually refer to informal language as `slang' and +reserve the term `jargon' for the technical vocabularies of +various occupations. However, the ancestor of this collection was +called the `Jargon File', and hacker slang is traditionally `the +jargon'. When talking about the jargon there is therefore no +convenient way to distinguish it from what a <i>linguist</i> +would call hackers' jargon -- the formal vocabulary they learn +from textbooks, technical papers, and manuals.</p> + +<p>To make a confused situation worse, the line between hacker +slang and the vocabulary of technical programming and computer +science is fuzzy, and shifts over time. Further, this vocabulary +is shared with a wider technical culture of programmers, many of +whom are not hackers and do not speak or recognize hackish +slang.</p> + +<p>Accordingly, this lexicon will try to be as precise as the +facts of usage permit about the distinctions among three +categories:</p> + +<ul> +<li>`slang': informal language from mainstream English or +non-technical subcultures (bikers, rock fans, surfers, etc).</li> + +<li>`jargon': without qualifier, denotes informal `slangy' +language peculiar to or predominantly found among hackers -- the +subject of this lexicon.</li> + +<li>`techspeak': the formal technical vocabulary of programming, +computer science, electronics, and other fields connected to +hacking.</li> +</ul> + +<p>This terminology will be consistently used throughout the +remainder of this lexicon.</p> + +<p>The jargon/techspeak distinction is the delicate one. A lot of +techspeak originated as jargon, and there is a steady continuing +uptake of jargon into techspeak. On the other hand, a lot of +jargon arises from overgeneralization of techspeak terms (there +is more about this in the <b><a href="#JargonConstruction">Jargon Construction</a></b> section +below).</p> + +<p>In general, we have considered techspeak any term that +communicates primarily by a denotation well established in +textbooks, technical dictionaries, or standards documents.</p> + +<p>A few obviously techspeak terms (names of operating systems, +languages, or documents) are listed when they are tied to hacker +folklore that isn't covered in formal sources, or sometimes to +convey critical historical background necessary to understand +other entries to which they are cross-referenced. Some other +techspeak senses of jargon words are listed in order to make the +jargon senses clear; where the text does not specify that a +straight technical sense is under discussion, these are marked +with `[techspeak]' as an etymology. Some entries have a primary +sense marked this way, with subsequent jargon meanings explained +in terms of it.</p> + +<p>We have also tried to indicate (where known) the apparent +origins of terms. The results are probably the least reliable +information in the lexicon, for several reasons. For one thing, +it is well known that many hackish usages have been independently +reinvented multiple times, even among the more obscure and +intricate neologisms. It often seems that the generative +processes underlying hackish jargon formation have an internal +logic so powerful as to create substantial parallelism across +separate cultures and even in different languages! For another, +the networks tend to propagate innovations so quickly that `first +use' is often impossible to pin down. And, finally, compendia +like this one alter what they observe by implicitly stamping +cultural approval on terms and widening their use.</p> + +<p>Despite these problems, the organized collection of +jargon-related oral history for the new compilations has enabled +us to put to rest quite a number of folk etymologies, place +credit where credit is due, and illuminate the early history of +many important hackerisms such as <b><a href="#kluge">kluge</a></b>, <b><a href="#cruft">cruft</a></b>, and +<b><a href="#foo">foo</a></b>. We believe specialist +lexicographers will find many of the historical notes more than +casually instructive.</p> + +<hr> +Node:<a name="RevisionHistory">Revision History</a>, Next:<a +rel="next" href="#JargonConstruction">Jargon Construction</a>, +Previous:<a rel="previous" href="#AFewTerms">A Few +Terms</a>, Up:<a rel="up" href="#Top">Top</a> <br> + + +<h2>Revision History</h2> + +<p>The original Jargon File was a collection of hacker jargon +from technical cultures including the MIT AI Lab, the Stanford AI +lab (SAIL), and others of the old ARPANET AI/LISP/PDP-10 +communities including Bolt, Beranek and Newman (BBN), +Carnegie-Mellon University (CMU), and Worcester Polytechnic +Institute (WPI).</p> + +<p>The Jargon File (hereafter referred to as `jargon-1' or `the +File') was begun by Raphael Finkel at Stanford in 1975. From this +time until the plug was finally pulled on the SAIL computer in +1991, the File was named AIWORD.RF[UP,DOC] there. Some terms in +it date back considerably earlier (<b><a href="#frob">frob</a></b> and some senses of <b><a href="#moby">moby</a></b>, for instance, go back to the Tech Model +Railroad Club at MIT and are believed to date at least back to +the early 1960s). The revisions of jargon-1 were all unnumbered +and may be collectively considered `Version 1'.</p> + +<p>In 1976, Mark Crispin, having seen an announcement about the +File on the SAIL computer, <b><a href="#FTP">FTP</a></b>ed a copy +of the File to MIT. He noticed that it was hardly restricted to +`AI words' and so stored the file on his directory as AI:MRC;SAIL +JARGON.</p> + +<p>The file was quickly renamed JARGON > (the `>' caused +versioning under ITS) as a flurry of enhancements were made by +Mark Crispin and Guy L. Steele Jr. Unfortunately, amidst all this +activity, nobody thought of correcting the term `jargon' to +`slang' until the compendium had already become widely known as +the Jargon File.</p> + +<p>Raphael Finkel dropped out of active participation shortly +thereafter and Don Woods became the SAIL contact for the File +(which was subsequently kept in duplicate at SAIL and MIT, with +periodic resynchronizations).</p> + +<p>The File expanded by fits and starts until about 1983; Richard +Stallman was prominent among the contributors, adding many MIT +and ITS-related coinages.</p> + +<p>In Spring 1981, a hacker named Charles Spurgeon got a large +chunk of the File published in Stewart Brand's "CoEvolution +Quarterly" (issue 29, pages 26-35) with illustrations by Phil +Wadler and Guy Steele (including a couple of the Crunchly +cartoons). This appears to have been the File's first paper +publication.</p> + +<p>A late version of jargon-1, expanded with commentary for the +mass market, was edited by Guy Steele into a book published in +1983 as "The Hacker's Dictionary" (Harper & Row CN 1082, ISBN +0-06-091082-8). The other jargon-1 editors (Raphael Finkel, Don +Woods, and Mark Crispin) contributed to this revision, as did +Richard M. Stallman and Geoff Goodfellow. This book (now out of +print) is hereafter referred to as `Steele-1983' and those six as +the Steele-1983 coauthors.</p> + +<p>Shortly after the publication of Steele-1983, the File +effectively stopped growing and changing. Originally, this was +due to a desire to freeze the file temporarily to facilitate the +production of Steele-1983, but external conditions caused the +`temporary' freeze to become permanent.</p> + +<p>The AI Lab culture had been hit hard in the late 1970s by +funding cuts and the resulting administrative decision to use +vendor-supported hardware and software instead of homebrew +whenever possible. At MIT, most AI work had turned to dedicated +LISP Machines. At the same time, the commercialization of AI +technology lured some of the AI Lab's best and brightest away to +startups along the Route 128 strip in Massachusetts and out West +in Silicon Valley. The startups built LISP machines for MIT; the +central MIT-AI computer became a <b><a href="#TWENEX">TWENEX</a></b> system rather than a host for the AI +hackers' beloved <b><a href="#ITS">ITS</a></b>.</p> + +<p>The Stanford AI Lab had effectively ceased to exist by 1980, +although the SAIL computer continued as a Computer Science +Department resource until 1991. Stanford became a major <b><a +href="#TWENEX">TWENEX</a></b> site, at one point operating more +than a dozen TOPS-20 systems; but by the mid-1980s most of the +interesting software work was being done on the emerging BSD Unix +standard.</p> + +<p>In April 1983, the PDP-10-centered cultures that had nourished +the File were dealt a death-blow by the cancellation of the +Jupiter project at Digital Equipment Corporation. The File's +compilers, already dispersed, moved on to other things. +Steele-1983 was partly a monument to what its authors thought was +a dying tradition; no one involved realized at the time just how +wide its influence was to be.</p> + +<p>By the mid-1980s the File's content was dated, but the legend +that had grown up around it never quite died out. The book, and +softcopies obtained off the ARPANET, circulated even in cultures +far removed from MIT and Stanford; the content exerted a strong +and continuing influence on hacker language and humor. Even as +the advent of the microcomputer and other trends fueled a +tremendous expansion of hackerdom, the File (and related +materials such as the <b><a href="#SomeAIKoans">Some AI +Koans</a></b> in Appendix A) came to be seen as a sort of sacred +epic, a hacker-culture Matter of Britain chronicling the heroic +exploits of the Knights of the Lab. The pace of change in +hackerdom at large accelerated tremendously -- but the Jargon +File, having passed from living document to icon, remained +essentially untouched for seven years.</p> + +<p>This revision contains nearly the entire text of a late +version of jargon-1 (a few obsolete PDP-10-related entries were +dropped after careful consultation with the editors of +Steele-1983). It merges in about 80% of the Steele-1983 text, +omitting some framing material and a very few entries introduced +in Steele-1983 that are now also obsolete.</p> + +<p>This new version casts a wider net than the old Jargon File; +its aim is to cover not just AI or PDP-10 hacker culture but all +the technical computing cultures wherein the true hacker-nature +is manifested. More than half of the entries now derive from +<b><a href="#Usenet">Usenet</a></b> and represent jargon now +current in the C and Unix communities, but special efforts have +been made to collect jargon from other cultures including IBM PC +programmers, Amiga fans, Mac enthusiasts, and even the IBM +mainframe world.</p> + +<p> +Eric S. Raymond maintains the new File with assistance from Guy L. Steele Jr.; +these are the persons primarily reflected in the File's editorial +`we', though we take pleasure in acknowledging the special +contribution of the other coauthors of Steele-1983. Please email +all additions, corrections, and correspondence relating to the +Jargon File to <a href="mailto:jargon@thyrsus.com">jargon@thyrsus.com</a>.</p> + +<p>(Warning: other email addresses appear in this file <i>but +are not guaranteed to be correct</i> later than the revision +date on the first line. <i>Don't</i> email us if an attempt to +reach your idol bounces -- we have no magic way of checking +addresses or looking up people.)</p> + +<p>The 2.9.6 version became the main text of "The New Hacker's +Dictionary", by Eric Raymond (ed.), MIT Press 1991, ISBN +0-262-68069-6.</p> + +<p>The 3.0.0 version was published in September 1993 as the +second edition of "The New Hacker's Dictionary", again from MIT +Press (ISBN 0-262-18154-1).</p> + +<p>If you want the book, you should be able to find it at any of +the major bookstore chains. Failing that, you can order by mail +from</p> + +<p>The MIT Press 55 Hayward Street Cambridge, MA 02142</p> + +<p>or order by phone at (800)-356-0343 or (617)-625-8481.</p> + +<p>The maintainers are committed to updating the on-line version +of the Jargon File through and beyond paper publication, and will +continue to make it available to archives and public-access sites +as a trust of the hacker community.</p> + +<p>Here is a chronology of the high points in the recent on-line +revisions:</p> + +<p>Version 2.1.1, Jun 12 1990: the Jargon File comes alive again +after a seven-year hiatus. Reorganization and massive additions +were by Eric S. Raymond, approved by Guy Steele. Many items of +UNIX, C, USENET, and microcomputer-based jargon were added at +that time.</p> + +<p>Version 2.9.6, Aug 16 1991: corresponds to reproduction copy +for book. This version had 18952 lines, 148629 words, 975551 +characters, and 1702 entries.</p> + +<p>Version 2.9.7, Oct 28 1991: first markup for hypertext +browser. This version had 19432 lines, 152132 words, 999595 +characters, and 1750 entries.</p> + +<p>Version 2.9.8, Jan 01 1992: first public release since the +book, including over fifty new entries and numerous +corrections/additions to old ones. Packaged with version 1.1 of +vh(1) hypertext reader. This version had 19509 lines, 153108 +words, 1006023 characters, and 1760 entries.</p> + +<p>Version 2.9.9, Apr 01 1992: folded in XEROX PARC lexicon. This +version had 20298 lines, 159651 words, 1048909 characters, and +1821 entries.</p> + +<p>Version 2.9.10, Jul 01 1992: lots of new historical material. +This version had 21349 lines, 168330 words, 1106991 characters, +and 1891 entries.</p> + +<p>Version 2.9.11, Jan 01 1993: lots of new historical material. +This version had 21725 lines, 171169 words, 1125880 characters, +and 1922 entries.</p> + +<p>Version 2.9.12, May 10 1993: a few new entries & changes, +marginal MUD/IRC slang and some borderline techspeak removed, all +in preparation for 2nd Edition of TNHD. This version had 22238 +lines, 175114 words, 1152467 characters, and 1946 entries.</p> + +<p>Version 3.0.0, Jul 27 1993: manuscript freeze for 2nd edition +of TNHD. This version had 22548 lines, 177520 words, 1169372 +characters, and 1961 entries.</p> + +<p>Version 3.1.0, Oct 15 1994: interim release to test WWW +conversion. This version had 23197 lines, 181001 words, 1193818 +characters, and 1990 entries.</p> + +<p>Version 3.2.0, Mar 15 1995: Spring 1995 update. This version +had 23822 lines, 185961 words, 1226358 characters, and 2031 +entries.</p> + +<p>Version 3.3.0, Jan 20 1996: Winter 1996 update. This version +had 24055 lines, 187957 words, 1239604 characters, and 2045 +entries.</p> + +<p>Version 3.3.1, Jan 25 1996: Copy-corrected improvement on +3.3.0 shipped to MIT Press as a step towards TNHD III. This +version had 24147 lines, 188728 words, 1244554 characters, and +2050 entries.</p> + +<p>Version 3.3.2, Mar 20 1996: A number of new entries pursuant +on 3.3.2. This version had 24442 lines, 190867 words, 1262468 +characters, and 2061 entries.</p> + +<p>Version 3.3.3, Mar 25 1996: Cleanup before TNHD III manuscript +freeze. This version had 24584 lines, 191932 words, 1269996 +characters, and 2064 entries.</p> + +<p>Version 4.0.0, Jul 25 1996: The actual TNHD III version after +copy-edit. This version had 24801 lines, 193697 words, 1281402 +characters, and 2067 entries.</p> + +<p>Version 4.1.0, 8 Apr 1999: The Jargon File rides again after +three years. This version had 25777 lines, 206825 words, 1359992 +characters, and 2217 entries.</p> + +<p>Version 4.1.1, 18 Apr 1999: Corrections for minor errors in +4.1.0, and some new entries. This version had 25921 lines, 208483 +words, 1371279 characters, and 2225 entries.</p> + +<p>Version 4.1.2, 28 Apr 1999: Moving texi2html out of the +production path. This version had 26006 lines, 209479 words, +1377687 characters, and 2225 entries.</p> + +<p>Version 4.1.3, 14 Jun 1999: Minor updates and markup fixes. +This version had 26108 lines, 210480 words, 1384546 characters, +and 2234 entries.</p> + +<p>Version 4.1.4, 17 Jun 1999: Markup fixes for framed HTML. This +version had 26117 lines, 210527 words, 1384902 characters, and +2234 entries.</p> + +<p>Version 4.2.0, 31 Jan 2000: Fix processing of URLs. This +version had 26598 lines, 214639 words, 1412243 characters, and +2267 entries.</p> + +<p>Version 4.2.1, 5 Mar 2000: Point release to test new +production machinery. This version had 26647 lines, 215040 words, +1414942 characters, and 2269 entries.</p> + +<p>Version 4.2.2, 12 Aug 2000: This version had 27171 lines, +219630 words, 1444887 characters, and 2302 entries.</p> + +<p>Version numbering: Version numbers should be read as +<i>major</i>.<i>minor</i>.<i>revision</i>. Major version 1 is +reserved for the `old' (ITS) Jargon File, jargon-1. Major version +2 encompasses revisions by ESR (Eric S. Raymond) with assistance +from GLS (Guy L. Steele, Jr.) leading up to and including the +second paper edition. From now on, major version number N.00 will +probably correspond to the Nth paper edition. Usually later +versions will either completely supersede or incorporate earlier +versions, so there is generally no point in keeping old versions +around.</p> + +<p> +Our thanks to the coauthors of Steele-1983 for oversight and assistance, and to +the hundreds of Usenetters (too many to name here) who contributed entries and +encouragement. More thanks go to several of the old-timers on the Usenet group +<i>alt.folklore.computers</i>, who contributed much useful commentary and many +corrections and valuable historical perspective: Joseph M. Newcomer, Bernie +Cosell, Earl Boebert, and Joe Morris. +</p> + +<p> +We were fortunate enough to have the aid of some accomplished linguists. David +Stampe and Charles Hoequist contributed valuable criticism; Joe Keane helped us +improve the pronunciation guides. +</p> + +<p> +A few bits of this text quote previous works. We are indebted to Brian A. +LaMacchia for obtaining permission for us to use material from the "TMRC +Dictionary"; also, Don Libes contributed some appropriate material from his +excellent book "Life With UNIX". We thank Per Lindberg, author of the +remarkable Swedish-language 'zine "Hackerbladet", for bringing "FOO!" comics to +our attention and smuggling one of the IBM hacker underground's own baby jargon +files out to us. Thanks also to Maarten Litmaath for generously allowing the +inclusion of the ASCII pronunciation guide he formerly maintained. And our +gratitude to Marc Weiser of XEROX PARC for securing us permission to quote from +PARC's own jargon lexicon and shipping us a copy. +</p> + +<p> +It is a particular pleasure to acknowledge the major contributions of Mark +Brader and Steve Summit to the File and Dictionary; they have read and reread +many drafts, checked facts, caught typos, submitted an amazing number of +thoughtful comments, and done yeoman service in catching typos and minor usage +bobbles. Their rare combination of enthusiasm, persistence, wide-ranging +technical knowledge, and precisionism in matters of language has been of +invaluable help. Indeed, the sustained volume and quality of Mr. Brader's input +over several years and several different editions has only allowed him to +escape co-editor credit by the slimmest of margins. +</p> + +<p> +Finally, George V. Reilly helped with TeX arcana and painstakingly proofread +some 2.7 and 2.8 versions, and Eric Tiedemann contributed sage advice +throughout on rhetoric, amphigory, and philosophunculism. +</p> + +<hr> +Node:<a name="JargonConstruction">Jargon Construction</a>, +Next:<a rel="next" href="#HackerWritingStyle">Hacker +Writing Style</a>, Previous:<a rel="previous" href="#RevisionHistory">Revision History</a>, Up:<a rel="up" href="#Top">Top</a> <br> + + +<h2>How Jargon Works</h2> + +<h2>Jargon Construction</h2> + +<p>There are some standard methods of jargonification that became +established quite early (i.e., before 1970), spreading from such +sources as the Tech Model Railroad Club, the PDP-1 SPACEWAR +hackers, and John McCarthy's original crew of LISPers. These +include verb doubling, soundalike slang, the `-P' convention, +overgeneralization, spoken inarticulations, and +anthropomorphization. Each is discussed below. We also cover the +standard comparatives for design quality.</p> + +<p>Of these six, verb doubling, overgeneralization, +anthropomorphization, and (especially) spoken inarticulations +have become quite general; but soundalike slang is still largely +confined to MIT and other large universities, and the `-P' +convention is found only where LISPers flourish.</p> + +<ul> +<li><a href="#VerbDoubling">Verb Doubling</a>: Doubling a verb +may change its semantics</li> + +<li><a href="#Soundalike0Slang">Soundalike Slang</a>: Punning +jargon</li> + +<li><a href="#The-Pconvention">The -P convention</a>: A +LISPy way to form questions</li> + +<li><a href="#Overgeneralization">Overgeneralization</a>: +Standard abuses of grammar</li> + +<li><a href="#SpokenInarticulations">Spoken +Inarticulations</a>: Sighing and <*sigh*>ing</li> + +<li><a href="#Anthropomorphization">Anthropomorphization</a>: +Homunculi, daemons, and confused programs</li> + +<li><a href="#Comparatives">Comparatives</a>: Standard +comparatives for design quality</li> +</ul> + +<hr> +Node:<a name="VerbDoubling">Verb Doubling</a>, Next:<a rel="next" href="#Soundalike0Slang">Soundalike Slang</a>, Up:<a +rel="up" href="#JargonConstruction">Jargon Construction</a> +<br> + + +<h3>Verb Doubling</h3> + +<p>A standard construction in English is to double a verb and use +it as an exclamation, such as "Bang, bang!" or "Quack, quack!". +Most of these are names for noises. Hackers also double verbs as +a concise, sometimes sarcastic comment on what the implied +subject does. Also, a doubled verb is often used to terminate a +conversation, in the process remarking on the current state of +affairs or what the speaker intends to do next. Typical examples +involve <b><a href="#win">win</a></b>, <b><a href="#lose">lose</a></b>, <b><a href="#hack">hack</a></b>, <b><a +href="#flame">flame</a></b>, <b><a href="#barf">barf</a></b>, +<b><a href="#chomp">chomp</a></b>:</p> + +<blockquote>"The disk heads just crashed." "Lose, lose."<br> +"Mostly he talked about his latest crock. Flame, flame."<br> +"Boy, what a bagbiter! Chomp, chomp!"</blockquote> + +<p>Some verb-doubled constructions have special meanings not +immediately obvious from the verb. These have their own listings +in the lexicon.</p> + +<p>The <b><a href="#Usenet">Usenet</a></b> culture has one +<i>tripling</i> convention unrelated to this; the names of +`joke' topic groups often have a tripled last element. The first +and paradigmatic example was +<i>alt.swedish.chef.bork.bork.bork</i> (a "Muppet Show" +reference); other infamous examples have included:</p> + +<blockquote><i>alt.french.captain.borg.borg.borg</i><br> +<i>alt.wesley.crusher.die.die.die</i><br> +<i>comp.unix.internals.system.calls.brk.brk.brk</i><br> +<i>sci.physics.edward.teller.boom.boom.boom</i><br> +<i>alt.sadistic.dentists.drill.drill.drill</i></blockquote> + +<hr> +Node:<a name="Soundalike0Slang">Soundalike Slang</a>, Next:<a +rel="next" href="#The-Pconvention">The -P convention</a>, +Previous:<a rel="previous" href="#VerbDoubling">Verb +Doubling</a>, Up:<a rel="up" href="#JargonConstruction">Jargon +Construction</a> <br> + + +<h3>Soundalike slang</h3> + +<p>Hackers will often make rhymes or puns in order to convert an +ordinary word or phrase into something more interesting. It is +considered particularly <b><a href="#flavorful">flavorful</a></b> +if the phrase is bent so as to include some other jargon word; +thus the computer hobbyist magazine "Dr. Dobb's Journal" is +almost always referred to among hackers as `Dr. Frob's Journal' +or simply `Dr. Frob's'. Terms of this kind that have been in +fairly wide use include names for newspapers:</p> + +<pre> + Boston Herald => Horrid (or Harried) + Boston Globe => Boston Glob + Houston (or San Francisco) Chronicle + => the Crocknicle (or the Comical) + New York Times => New York Slime + Wall Street Journal => Wall Street Urinal +</pre> + +<p>However, terms like these are often made up on the spur of the +moment. Standard examples include:</p> + +<pre> + Data General => Dirty Genitals + IBM 360 => IBM Three-Sickly + Government Property --- Do Not Duplicate (on keys) + => Government Duplicity --- Do Not Propagate + for historical reasons => for hysterical raisins + Margaret Jacks Hall (the CS building at Stanford) + => Marginal Hacks Hall + Microsoft => Microsloth + Internet Explorer => Internet Exploiter +</pre> + +<p>This is not really similar to the Cockney rhyming slang it has +been compared to in the past, because Cockney substitutions are +opaque whereas hacker punning jargon is intentionally +transparent.</p> + +<hr> +Node:<a name="The-Pconvention">The -P convention</a>, +Next:<a rel="next" href="#Overgeneralization">Overgeneralization</a>, Previous:<a rel="previous" href="#Soundalike0Slang">Soundalike Slang</a>, Up:<a +rel="up" href="#JargonConstruction">Jargon Construction</a> +<br> + + +<h3>The `-P' convention</h3> + +<p>Turning a word into a question by appending the syllable `P'; +from the LISP convention of appending the letter `P' to denote a +predicate (a boolean-valued function). The question should expect +a yes/no answer, though it needn't. (See <b><a href="#T">T</a></b> and <b><a href="#NIL">NIL</a></b>.)</p> + +<pre> + At dinnertime:<br> + Q: ``Foodp?''<br> + A: ``Yeah, I'm pretty hungry.'' or ``T!''<br> + + At any time:<br> + Q: ``State-of-the-world-P?''<br> + A: (Straight) ``I'm about to go home.''<br> + A: (Humorous) ``Yes, the world has a state.''<br> + + On the phone to Florida:<br> + Q: ``State-p Florida?''<br> + A: ``Been reading JARGON.TXT again, eh?'' +</pre> + +<p>[One of the best of these is a <b><a href="#Gosperism">Gosperism</a></b>. Once, when we were at a Chinese +restaurant, Bill Gosper wanted to know whether someone would like +to share with him a two-person-sized bowl of soup. His inquiry +was: "Split-p soup?" -- GLS]</p> + +<hr> +Node:<a name="Overgeneralization">Overgeneralization</a>, Next:<a +rel="next" href="#SpokenInarticulations">Spoken +Inarticulations</a>, Previous:<a rel="previous" href="#The-Pconvention">The -P convention</a>, Up:<a rel="up" +href="#JargonConstruction">Jargon Construction</a> <br> + + +<h3>Overgeneralization</h3> + +<p>A very conspicuous feature of jargon is the frequency with +which techspeak items such as names of program tools, command +language primitives, and even assembler opcodes are applied to +contexts outside of computing wherever hackers find amusing +analogies to them. Thus (to cite one of the best-known examples) +Unix hackers often <b><a href="#grep">grep</a></b> for things +rather than searching for them. Many of the lexicon entries are +generalizations of exactly this kind.</p> + +<p>Hackers enjoy overgeneralization on the grammatical level as +well. Many hackers love to take various words and add the wrong +endings to them to make nouns and verbs, often by extending a +standard rule to nonuniform cases (or vice versa). For example, +because</p> + +<blockquote>porous => porosity<br> +generous => generosity</blockquote> + +<p>hackers happily generalize:</p> + +<blockquote>mysterious => mysteriosity<br> +ferrous => ferrosity<br> +obvious => obviosity<br> +dubious => dubiosity</blockquote> + +<p>Another class of common construction uses the suffix `-itude' +to abstract a quality from just about any adjective or noun. This +usage arises especially in cases where mainstream English would +perform the same abstraction through `-iness' or `-ingness'. +Thus:</p> + +<blockquote>win => winnitude (a common exclamation)<br> +loss => lossitude<br> +cruft => cruftitude<br> +lame => lameitude</blockquote> + +<p>Some hackers cheerfully reverse this transformation; they +argue, for example, that the horizontal degree lines on a globe +ought to be called `lats' -- after all, they're measuring +latitude!</p> + +<p>Also, note that all nouns can be verbed. E.g.: "All nouns can +be verbed", "I'll mouse it up", "Hang on while I clipboard it +over", "I'm grepping the files". English as a whole is already +heading in this direction (towards pure-positional grammar like +Chinese); hackers are simply a bit ahead of the curve.</p> + +<p>The suffix "-full" can also be applied in generalized and +fanciful ways, as in "As soon as you have more than one cachefull +of data, the system starts thrashing," or "As soon as I have more +than one headfull of ideas, I start writing it all down." A +common use is "screenfull", meaning the amount of text that will +fit on one screen, usually in text mode where you have no choice +as to character size. Another common form is "bufferfull".</p> + +<p>However, hackers avoid the unimaginative verb-making +techniques characteristic of marketroids, bean-counters, and the +Pentagon; a hacker would never, for example, `productize', +`prioritize', or `securitize' things. Hackers have a strong +aversion to bureaucratic bafflegab and regard those who use it +with contempt.</p> + +<p>Similarly, all verbs can be nouned. This is only a slight +overgeneralization in modern English; in hackish, however, it is +good form to mark them in some standard nonstandard way. +Thus:</p> + +<blockquote>win => winnitude, winnage<br> +disgust => disgustitude<br> +hack => hackification</blockquote> + +<p>Further, note the prevalence of certain kinds of nonstandard +plural forms. Some of these go back quite a ways; the TMRC +Dictionary includes an entry which implies that the plural of +`mouse' is <b><a href="#meeces">meeces</a></b>, and notes that +the defined plural of `caboose' is `cabeese'. This latter has +apparently been standard (or at least a standard joke) among +railfans (railroad enthusiasts) for many years.</p> + +<p>On a similarly Anglo-Saxon note, almost anything ending in `x' +may form plurals in `-xen' (see <b><a href="#VAXen">VAXen</a></b> +and <b><a href="#boxen">boxen</a></b> in the main text). Even +words ending in phonetic /k/ alone are sometimes treated this +way; e.g., `soxen' for a bunch of socks. Other funny plurals are +`frobbotzim' for the plural of `frobbozz' (see <b><a href="#frobnitz">frobnitz</a></b>) and `Unices' and `Twenices' (rather +than `Unixes' and `Twenexes'; see <b><a href="#Unix">Unix</a></b>, <b><a href="#TWENEX">TWENEX</a></b> in main +text). But note that `Twenexen' was never used, and `Unixen' was +not sighted in the wild until the year 2000, thirty years after +it might logically have come into use; it has been suggested that +this is because `-ix' and `-ex' are Latin singular endings that +attract a Latinate plural. Finally, it has been suggested to +general approval that the plural of `mongoose' ought to be +`polygoose'.</p> + +<p>The pattern here, as with other hackish grammatical quirks, is +generalization of an inflectional rule that in English is either +an import or a fossil (such as the Hebrew plural ending `-im', or +the Anglo-Saxon plural suffix `-en') to cases where it isn't +normally considered to apply.</p> + +<p>This is not `poor grammar', as hackers are generally quite +well aware of what they are doing when they distort the language. +It is grammatical creativity, a form of playfulness. It is done +not to impress but to amuse, and never at the expense of +clarity.</p> + +<hr> +Node:<a name="SpokenInarticulations">Spoken +Inarticulations</a>, Next:<a rel="next" href="#Anthropomorphization">Anthropomorphization</a>, Previous:<a +rel="previous" href="#Overgeneralization">Overgeneralization</a>, +Up:<a rel="up" href="#JargonConstruction">Jargon +Construction</a> <br> + + +<h3>Spoken inarticulations</h3> + +<p>Words such as `mumble', `sigh', and `groan' are spoken in +places where their referent might more naturally be used. It has +been suggested that this usage derives from the impossibility of +representing such noises on a comm link or in electronic mail, +MUDs, and IRC channels (interestingly, the same sorts of +constructions have been showing up with increasing frequency in +comic strips). Another expression sometimes heard is "Complain!", +meaning "I have a complaint!"</p> + +<hr> +Node:<a name="Anthropomorphization">Anthropomorphization</a>, +Next:<a rel="next" href="#Comparatives">Comparatives</a>, +Previous:<a rel="previous" href="#SpokenInarticulations">Spoken Inarticulations</a>, Up:<a +rel="up" href="#JargonConstruction">Jargon Construction</a> +<br> + + +<h3>Anthropomorphization</h3> + +<p>Semantically, one rich source of jargon constructions is the +hackish tendency to anthropomorphize hardware and software. +English purists and academic computer scientists frequently look +down on others for anthropomorphizing hardware and software, +considering this sort of behavior to be characteristic of naive +misunderstanding. But most hackers anthropomorphize freely, +frequently describing program behavior in terms of wants and +desires.</p> + +<p>Thus it is common to hear hardware or software talked about as +though it has homunculi talking to each other inside it, with +intentions and desires. Thus, one hears "The protocol handler got +confused", or that programs "are trying" to do things, or one may +say of a routine that "its goal in life is to X". One even hears +explanations like "<small>...</small> and its poor little brain +couldn't understand X, and it died." Sometimes modelling things +this way actually seems to make them easier to understand, +perhaps because it's instinctively natural to think of anything +with a really complex behavioral repertoire as `like a person' +rather than `like a thing'.</p> + +<p>At first glance, to anyone who understands how these programs +actually work, this seems like an absurdity. As hackers are among +the people who know best how these phenomena work, it seems odd +that they would use language that seemds to ascribe conciousness +to them. The mind-set behind this tendency thus demands +examination.</p> + +<p>The key to understanding this kind of usage is that it isn't +done in a naive way; hackers don't personalize their stuff in the +sense of feeling empathy with it, nor do they mystically believe +that the things they work on every day are `alive'. To the +contrary: hackers who anthropomorphize are expressing not a +vitalistic view of program behavior but a mechanistic view of +human behavior.</p> + +<p>Almost all hackers subscribe to the mechanistic, materialistic +ontology of science (this is in practice true even of most of the +minority with contrary religious theories). In this view, people +are biological machines - consciousness is an interesting and +valuable epiphenomenon, but mind is implemented in machinery +which is not fundamentally different in information-processing +capacity from computers.</p> + +<p>Hackers tend to take this a step further and argue that the +difference between a substrate of CHON atoms and water and a +substrate of silicon and metal is a relatively unimportant one; +what matters, what makes a thing `alive', is information and +richness of pattern. This is animism from the flip side; it +implies that humans and computers and dolphins and rocks are all +machines exhibiting a continuum of modes of `consciousness' +according to their information-processing capacity.</p> + +<p>Because hackers accept a that a human machine can have +intentions, it is therefore easy for them to ascribe +consciousness and intention to complex patterned systems such as +computers. If consciousness is mechanical, it is neither more or +less absurd to say that "The program wants to go into an infinite +loop" than it is to say that "I want to go eat some chocolate" - +and even defensible to say that "The stone, once dropped, wants +to move towards the center of the earth".</p> + +<p>This viewpoint has respectable company in academic philosophy. +Daniel Dennett organizes explanations of behavior using three +stances: the "physical stance" (thing-to-be-explained as a +physical object), the "design stance" (thing-to-be-explained as +an artifact), and the "intentional stance" (thing-to-be-explained +as an agent with desires and intentions). Which stances are +appropriate is a matter not of truth but of utility. Hackers +typically view simple programs from the design stance, but more +complex ones are modelled using the intentional stance.</p> + +<hr> +Node:<a name="Comparatives">Comparatives</a>, Previous:<a rel="previous" href="#Anthropomorphization">Anthropomorphization</a>, +Up:<a rel="up" href="#JargonConstruction">Jargon +Construction</a> <br> + + +<h3>Comparatives</h3> + +<p>Finally, note that many words in hacker jargon have to be +understood as members of sets of comparatives. This is especially +true of the adjectives and nouns used to describe the beauty and +functional quality of code. Here is an approximately correct +spectrum:</p> + +<blockquote>monstrosity brain-damage screw bug lose +misfeature<br> +crock kluge hack win feature elegance perfection</blockquote> + +<p>The last is spoken of as a mythical absolute, approximated but +never actually attained. Another similar scale is used for +describing the reliability of software:</p> + +<blockquote>broken flaky dodgy fragile brittle<br> +solid robust bulletproof armor-plated</blockquote> + +<p>Note, however, that `dodgy' is primarily Commonwealth Hackish +(it is rare in the U.S.) and may change places with `flaky' for +some speakers.</p> + +<p>Coinages for describing <b><a href="#lossage">lossage</a></b> +seem to call forth the very finest in hackish linguistic +inventiveness; it has been truly said that hackers have even more +words for equipment failures than Yiddish has for obnoxious +people.</p> + +<hr> +Node:<a name="HackerWritingStyle">Hacker Writing Style</a>, +Next:<a rel="next" href="#EmailQuotes">Email Quotes</a>, +Previous:<a rel="previous" href="#JargonConstruction">Jargon +Construction</a>, Up:<a rel="up" href="#Top">Top</a> <br> + + +<h2>Hacker Writing Style</h2> + +<p>We've already seen that hackers often coin jargon by +overgeneralizing grammatical rules. This is one aspect of a more +general fondness for form-versus-content language jokes that +shows up particularly in hackish writing. One correspondent +reports that he consistently misspells `wrong' as `worng'. Others +have been known to criticize glitches in Jargon File drafts by +observing (in the mode of Douglas Hofstadter) "This sentence no +verb", or "Too repetetetive", or "Bad speling", or "Incorrectspa +cing." Similarly, intentional spoonerisms are often made of +phrases relating to confusion or things that are confusing; `dain +bramage' for `brain damage' is perhaps the most common +(similarly, a hacker would be likely to write "Excuse me, I'm +cixelsyd today", rather than "I'm dyslexic today"). This sort of +thing is quite common and is enjoyed by all concerned.</p> + +<p>Hackers tend to use quotes as balanced delimiters like +parentheses, much to the dismay of American editors. Thus, if +"Jim is going" is a phrase, and so are "Bill runs" and "Spock +groks", then hackers generally prefer to write: "Jim is going", +"Bill runs", and "Spock groks". This is incorrect according to +standard American usage (which would put the continuation commas +and the final period inside the string quotes); however, it is +counter-intuitive to hackers to mutilate literal strings with +characters that don't belong in them. Given the sorts of examples +that can come up in discussions of programming, American-style +quoting can even be grossly misleading. When communicating +command lines or small pieces of code, extra characters can be a +real pain in the neck.</p> + +<p>Consider, for example, a sentence in a <b><a href="#vi">vi</a></b> tutorial that looks like this:</p> + +<blockquote>Then delete a line from the file by typing +"dd".</blockquote> + +<p>Standard usage would make this</p> + +<blockquote>Then delete a line from the file by typing +"dd."</blockquote> + +<p>but that would be very bad -- because the reader would be +prone to type the string d-d-dot, and it happens that in +<code>vi(1)</code> dot repeats the last command accepted. The net +result would be to delete <i>two</i> lines!</p> + +<p>The Jargon File follows hackish usage throughout.</p> + +<p>Interestingly, a similar style is now preferred practice in +Great Britain, though the older style (which became established +for typographical reasons having to do with the aesthetics of +comma and quotes in typeset text) is still accepted there. +"Hart's Rules" and the "Oxford Dictionary for Writers and +Editors" call the hacker-like style `new' or `logical' quoting. +This returns British English to the style Latin languages +(including Spanish, French, Italian, Catalan) have been using all +along.</p> + +<p>Another hacker habit is a tendency to distinguish between +`scare' quotes and `speech' quotes; that is, to use British-style +single quotes for marking and reserve American-style double +quotes for actual reports of speech or text included from +elsewhere. Interestingly, some authorities describe this as +correct general usage, but mainstream American English has gone +to using double-quotes indiscriminately enough that hacker usage +appears marked [and, in fact, I thought this was a personal quirk +of mine until I checked with Usenet --ESR]. One further +permutation that is definitely <i>not</i> standard is a hackish +tendency to do marking quotes by using apostrophes (single +quotes) in pairs; that is, 'like this'. This is modelled on +string and character literal syntax in some programming languages +(reinforced by the fact that many character-only terminals +display the apostrophe in typewriter style, as a vertical single +quote).</p> + +<p>One quirk that shows up frequently in the <b><a href="#email">email</a></b> style of Unix hackers in particular is a +tendency for some things that are normally all-lowercase +(including usernames and the names of commands and C routines) to +remain uncapitalized even when they occur at the beginning of +sentences. It is clear that, for many hackers, the case of such +identifiers becomes a part of their internal representation (the +`spelling') and cannot be overridden without mental effort (an +appropriate reflex because Unix and C both distinguish cases and +confusing them can lead to <b><a href="#lossage">lossage</a></b>). A way of escaping this dilemma is +simply to avoid using these constructions at the beginning of +sentences.</p> + +<p>There seems to be a meta-rule behind these nonstandard +hackerisms to the effect that precision of expression is more +important than conformance to traditional rules; where the latter +create ambiguity or lose information they can be discarded +without a second thought. It is notable in this respect that +other hackish inventions (for example, in vocabulary) also tend +to carry very precise shades of meaning even when constructed to +appear slangy and loose. In fact, to a hacker, the contrast +between `loose' form and `tight' content in jargon is a +substantial part of its humor!</p> + +<p>Hackers have also developed a number of punctuation and +emphasis conventions adapted to single-font all-ASCII +communications links, and these are occasionally carried over +into written documents even when normal means of font changes, +underlining, and the like are available.</p> + +<p>One of these is that TEXT IN ALL CAPS IS INTERPRETED AS +`LOUD', and this becomes such an ingrained synesthetic reflex +that a person who goes to caps-lock while in <b><a href="#talkmode">talk mode</a></b> may be asked to "stop shouting, +please, you're hurting my ears!".</p> + +<p>Also, it is common to use bracketing with unusual characters +to signify emphasis. The asterisk is most common, as in "What the +*hell*?" even though this interferes with the common use of the +asterisk suffix as a footnote mark. The underscore is also +common, suggesting underlining (this is particularly common with +book titles; for example, "It is often alleged that Joe Haldeman +wrote _The_Forever_War_ as a rebuttal to Robert Heinlein's +earlier novel of the future military, _Starship_Troopers_."). +Other forms exemplified by "=hell=", "\hell/", or "/hell/" are +occasionally seen (it's claimed that in the last example the +first slash pushes the letters over to the right to make them +italic, and the second keeps them from falling over). On FidoNet, +you might see #bright# and ^dark^ text, which was actually +interpreted by some reader software. Finally, words may also be +emphasized L I K E T H I S, or by a series of carets (^) under +them on the next line of the text.</p> + +<p>There is a semantic difference between *emphasis like this* +(which emphasizes the phrase as a whole), and *emphasis* *like* +*this* (which suggests the writer speaking very slowly and +distinctly, as if to a very young child or a mentally impaired +person). Bracketing a word with the `*' character may also +indicate that the writer wishes readers to consider that an +action is taking place or that a sound is being made. Examples: +*bang*, *hic*, *ring*, *grin*, *kick*, *stomp*, *mumble*.</p> + +<p>One might also see the above sound effects as <bang>, +<hic>, <ring>, <grin>, <kick>, +<stomp>, <mumble>. This use of angle brackets to mark +their contents originally derives from conventions used in <b><a +href="#BNF">BNF</a></b>, but since about 1993 it has been +reinforced by the HTML markup used on the World Wide Web.</p> + +<p>Angle-bracket enclosure is also used to indicate that a term +stands for some <b><a href="#random">random</a></b> member of a +larger class (this is straight from <b><a href="#BNF">BNF</a></b>). Examples like the following are common:</p> + +<pre> +So this <ethnic> walks into a bar one day... +</pre> + +<p>There is also an accepted convention for `writing under +erasure'; the text</p> + +<pre> +Be nice to this fool^H^H^H^Hgentleman, +he's visiting from corporate HQ. +</pre> + +<p>reads roughly as "Be nice to this fool, er, +gentleman<small>...</small>", with irony emphasized. The digraph +^H is often used as a print representation for a backspace, and +was actually very visible on old-style printing terminals. As the +text was being composed the characters would be echoed and +printed immediately, and when a correction was made the backspace +keystrokes would be echoed with the string '^H'. Of course, the +final composed text would have no trace of the backspace +characters (or the original erroneous text).</p> + +<p>This convention parallels (and may have been influenced by) +the ironic use of `slashouts' in science-fiction fanzines.</p> + +<p>A related habit uses editor commands to signify corrections to +previous text. This custom faded in email as more mailers got +good editing capabilities, only to tale on new life on IRCs and +other line-based chat systems.</p> + +<pre> +I've seen that term used on alt.foobar often. +Send it to Erik for the File. +Oops...s/Erik/Eric/. +</pre> + +<p>The s/Erik/Eric/ says "change Erik to Eric in the preceding". +This syntax is borrowed from the Unix editing tools +<code>ed</code> and <code>sed</code>, but is widely recognized by +non-Unix hackers as well.</p> + +<p>In a formula, <code>*</code> signifies multiplication but two +asterisks in a row are a shorthand for exponentiation (this +derives from FORTRAN). Thus, one might write 2 ** 8 = 256.</p> + +<p>Another notation for exponentiation one sees more frequently +uses the caret (^, ASCII 1011110); one might write instead +<code>2^8 = 256</code>. This goes all the way back to Algol-60, +which used the archaic ASCII `up-arrow' that later became the +caret; this was picked up by Kemeny and Kurtz's original BASIC, +which in turn influenced the design of the <code>bc(1)</code> and +<code>dc(1)</code> Unix tools, which have probably done most to +reinforce the convention on Usenet. (TeX math mode also uses ^ +for exponention.) The notation is mildly confusing to C +programmers, because <code>^</code> means bitwise exclusive-or in +C. Despite this, it was favored 3:1 over ** in a late-1990 +snapshot of Usenet. It is used consistently in this lexicon.</p> + +<p>In on-line exchanges, hackers tend to use decimal forms or +improper fractions (`3.5' or `7/2') rather than `typewriter +style' mixed fractions (`3-1/2'). The major motive here is +probably that the former are more readable in a monospaced font, +together with a desire to avoid the risk that the latter might be +read as `three minus one-half'. The decimal form is definitely +preferred for fractions with a terminating decimal +representation; there may be some cultural influence here from +the high status of scientific notation.</p> + +<p>Another on-line convention, used especially for very large or +very small numbers, is taken from C (which derived it from +FORTRAN). This is a form of `scientific notation' using `e' to +replace `*10^'; for example, one year is about 3e7 seconds +long.</p> + +<p>The tilde (~) is commonly used in a quantifying sense of +`approximately'; that is, <code>~50</code> means `about +fifty'.</p> + +<p>On Usenet and in the <b><a href="#MUD">MUD</a></b> world, +common C boolean, logical, and relational operators such as +<code>|</code>, <code>&</code>, <code>||</code>, +<code>&&</code>, <code>!</code>, <code>==</code>, +<code>!=</code>, <code>></code>, <code><</code>, +<code>>=</code>, and <code>=<</code> are often combined +with English. The Pascal not-equals, <code><></code>, is +also recognized, and occasionally one sees <code>/=</code> for +not-equals (from Ada, Common Lisp, and Fortran 90). The use of +prefix `!' as a loose synonym for `not-' or `no-' is particularly +common; thus, `!clue' is read `no-clue' or `clueless'.</p> + +<p>A related practice borrows syntax from preferred programming +languages to express ideas in a natural-language text. For +example, one might see the following:</p> + +<pre> +In <jrh578689@thudpucker.com> J. R. Hacker wrote: +>I recently had occasion to field-test the Snafu +>Systems 2300E adaptive gonkulator. The price was +>right, and the racing stripe on the case looked +>kind of neat, but its performance left something +>to be desired. + +Yeah, I tried one out too. + +#ifdef FLAME +Hasn't anyone told those idiots that you can't get +decent bogon suppression with AFJ filters at today's +net volumes? +#endif /* FLAME */ + +I guess they figured the price premium for true +frame-based semantic analysis was too high. +Unfortunately, it's also the only workable approach. +I wouldn't recommend purchase of this product unless +you're on a *very* tight budget. + +#include <disclaimer.h> +-- + == Frank Foonly (Fubarco Systems) +</pre> + +<br> +<p>In the above, the <code>#ifdef</code>/<code>#endif</code> pair +is a conditional compilation syntax from C; here, it implies that +the text between (which is a <b><a href="#flame">flame</a></b>) +should be evaluated only if you have turned on (or defined on) +the switch FLAME. The <code>#include</code> at the end is C for +"include standard disclaimer here"; the `standard disclaimer' is +understood to read, roughly, "These are my personal opinions and +not to be construed as the official position of my employer."</p> + +<p>The top section in the example, with > at the left margin, +is an example of an inclusion convention we'll discuss below.</p> + +<p>More recently, following on the huge popularity of the World +Wide Web, pseudo-HTML markup has become popular for similar +purposes:</p> + +<pre> +<flame> +Your father was a hamster and your mother smelt of elderberries! +</flame> +</pre> + +<br> +<p>You'll even see this with an HTML-style modifier:</p> + +<pre> +<flame intensity="100%"> +You seem well-suited for a career in government. +</flame> +</pre> + +<br> +<p>Another recent (late 1990s) construction now common on USENET +seems to be borrowed from Perl. It consists of using a dollar +sign before an uppercased form of a word or acronym to suggest +any <b><a href="#random">random</a></b> member of the class +indicated by the word. Thus: `$PHB' means "any random member of +the class `Pointy-Haired Boss'".</p> + +<p>Hackers also mix letters and numbers more freely than in +mainstream usage. In particular, it is good hackish style to +write a digit sequence where you intend the reader to understand +the text string that names that number in English. So, hackers +prefer to write `1970s' rather than `nineteen-seventies' or +`1970's' (the latter looks like a possessive).</p> + +<p>It should also be noted that hackers exhibit much less +reluctance to use multiply-nested parentheses than is normal in +English. Part of this is almost certainly due to influence from +LISP (which uses deeply nested parentheses (like this (see?)) in +its syntax a lot), but it has also been suggested that a more +basic hacker trait of enjoying playing with complexity and +pushing systems to their limits is in operation.</p> + +<p>Finally, it is worth mentioning that many studies of on-line +communication have shown that electronic links have a +de-inhibiting effect on people. Deprived of the body-language +cues through which emotional state is expressed, people tend to +forget everything about other parties except what is presented +over that ASCII link. This has both good and bad effects. A good +one is that it encourages honesty and tends to break down +hierarchical authority relationships; a bad one is that it may +encourage depersonalization and gratuitous rudeness. Perhaps in +response to this, experienced netters often display a sort of +conscious formal <i>politesse</i> in their writing that has +passed out of fashion in other spoken and written media (for +example, the phrase "Well said, sir!" is not uncommon).</p> + +<p>Many introverted hackers who are next to inarticulate in +person communicate with considerable fluency over the net, +perhaps precisely because they can forget on an unconscious level +that they are dealing with people and thus don't feel stressed +and anxious as they would face to face.</p> + +<p>Though it is considered gauche to publicly criticize posters +for poor spelling or grammar, the network places a premium on +literacy and clarity of expression. It may well be that future +historians of literature will see in it a revival of the great +tradition of personal letters as art.</p> + +<hr> +Node:<a name="EmailQuotes">Email Quotes</a>, Next:<a rel="next" href="#HackerSpeechStyle">Hacker Speech Style</a>, +Previous:<a rel="previous" href="#HackerWritingStyle">Hacker Writing Style</a>, Up:<a rel="up" href="#Top">Top</a> <br> + + +<h2>Email Quotes and Inclusion Conventions</h2> + +<p>One area where conventions for on-line writing are still in +some flux is the marking of included material from earlier +messages -- what would be called `block quotations' in ordinary +English. From the usual typographic convention employed for these +(smaller font at an extra indent), there derived a practice of +included text being indented by one ASCII TAB (0001001) +character, which under Unix and many other environments gives the +appearance of an 8-space indent.</p> + +<p>Early mail and netnews readers had no facility for including +messages this way, so people had to paste in copy manually. BSD +<code>Mail(1)</code> was the first message agent to support +inclusion, and early Usenetters emulated its style. But the TAB +character tended to push included text too far to the right +(especially in multiply nested inclusions), leading to ugly +wraparounds. After a brief period of confusion (during which an +inclusion leader consisting of three or four spaces became +established in EMACS and a few mailers), the use of leading +<code>></code> or <code>> </code> became standard, perhaps +owing to its use in <code>ed(1)</code> to display tabs +(alternatively, it may derive from the <code>></code> that +some early Unix mailers used to quote lines starting with "From" +in text, so they wouldn't look like the beginnings of new message +headers). Inclusions within inclusions keep their +<code>></code> leaders, so the `nesting level' of a quotation +is visually apparent.</p> + +<p>The practice of including text from the parent article when +posting a followup helped solve what had been a major nuisance on +Usenet: the fact that articles do not arrive at different sites +in the same order. Careless posters used to post articles that +would begin with, or even consist entirely of, "No, that's wrong" +or "I agree" or the like. It was hard to see who was responding +to what. Consequently, around 1984, new news-posting software +evolved a facility to automatically include the text of a +previous article, marked with "> " or whatever the poster +chose. The poster was expected to delete all but the relevant +lines. The result has been that, now, careless posters post +articles containing the <i>entire</i> text of a preceding +article, <i>followed</i> only by "No, that's wrong" or "I +agree".</p> + +<p>Many people feel that this cure is worse than the original +disease, and there soon appeared newsreader software designed to +let the reader skip over included text if desired. Today, some +posting software rejects articles containing too high a +proportion of lines beginning with `>' -- but this too has led +to undesirable workarounds, such as the deliberate inclusion of +zero-content filler lines which aren't quoted and thus pull the +message below the rejection threshold.</p> + +<p>Because the default mailers supplied with Unix and other +operating systems haven't evolved as quickly as human usage, the +older conventions using a leading TAB or three or four spaces are +still alive; however, >-inclusion is now clearly the prevalent +form in both netnews and mail.</p> + +<p>Inclusion practice is still evolving, and disputes over the +`correct' inclusion style occasionally lead to <b><a href="#holywars">holy wars</a></b>.</p> + +<p>Most netters view an inclusion as a promise that comment on it +will immediately follow. The preferred, conversational style +looks like this,</p> + +<pre> + > relevant excerpt 1 + response to excerpt + > relevant excerpt 2 + response to excerpt + > relevant excerpt 3 + response to excerpt +</pre> + +<p>or for short messages like this:</p> + +<pre> + > entire message + response to message +</pre> + +<p>Thanks to poor design of some PC-based mail agents, one will +occasionally see the entire quoted message <i>after</i> the +response, like this</p> + +<pre> + response to message + > entire message +</pre> + +<p>but this practice is strongly deprecated.</p> + +<p>Though <code>></code> remains the standard inclusion +leader, <code>|</code> is occasionally used for extended +quotations where original variations in indentation are being +retained (one mailer even combines these and uses +<code>|></code>). One also sees different styles of quoting a +number of authors in the same message: one (deprecated because it +loses information) uses a leader of <code>> </code> for +everyone, another (the most common) is +<code>> > > > </code> , <code>> > > </code> +, etc. (or <code>>>>> </code> , +<code>>>></code>, etc., depending on line length and +nesting depth) reflecting the original order of messages, and yet +another is to use a different citation leader for each author, +say <code>> </code> , <code>: </code> , <code>| </code> , +<code>} </code> (preserving nesting so that the inclusion order +of messages is still apparent, or tagging the inclusions with +authors' names). Yet <i>another</i> style is to use each +poster's initials (or login name) as a citation leader for that +poster.</p> + +<p>Occasionally one sees a <code># </code> leader used for +quotations from authoritative sources such as standards +documents; the intended allusion is to the root prompt (the +special Unix command prompt issued when one is running as the +privileged super-user).</p> + +<hr> +Node:<a name="HackerSpeechStyle">Hacker Speech Style</a>, +Next:<a rel="next" href="#InternationalStyle">International +Style</a>, Previous:<a rel="previous" href="#EmailQuotes">Email Quotes</a>, Up:<a rel="up" href="#Top">Top</a> <br> + + +<h2>Hacker Speech Style</h2> + +<p>Hackish speech generally features extremely precise diction, +careful word choice, a relatively large working vocabulary, and +relatively little use of contractions or street slang. Dry humor, +irony, puns, and a mildly flippant attitude are highly valued -- +but an underlying seriousness and intelligence are essential. One +should use just enough jargon to communicate precisely and +identify oneself as a member of the culture; overuse of jargon or +a breathless, excessively gung-ho attitude is considered tacky +and the mark of a loser.</p> + +<p>This speech style is a variety of the precisionist English +normally spoken by scientists, design engineers, and academics in +technical fields. In contrast with the methods of jargon +construction, it is fairly constant throughout hackerdom.</p> + +<p>It has been observed that many hackers are confused by +negative questions -- or, at least, that the people to whom they +are talking are often confused by the sense of their answers. The +problem is that they have done so much programming that +distinguishes between</p> + +<pre> +<tt>if (going) ...</tt> +</pre> + +<p>and</p> + +<pre> +<tt>if (!going) ...</tt> +</pre> + +<p>that when they parse the question "Aren't you going?" it may +seem to be asking the opposite question from "Are you going?", +and so to merit an answer in the opposite sense. This confuses +English-speaking non-hackers because they were taught to answer +as though the negative part weren't there. In some other +languages (including Russian, Chinese, and Japanese) the hackish +interpretation is standard and the problem wouldn't arise. +Hackers often find themselves wishing for a word like French +`si', German `doch', or Dutch `jawel' - a word with which one +could unambiguously answer `yes' to a negative question. (See +also <b><a href="#mu">mu</a></b>)</p> + +<p>For similar reasons, English-speaking hackers almost never use +double negatives, even if they live in a region where colloquial +usage allows them. The thought of uttering something that +logically ought to be an affirmative knowing it will be misparsed +as a negative tends to disturb them.</p> + +<p>In a related vein, hackers sometimes make a game of answering +questions containing logical connectives with a strictly literal +rather than colloquial interpretation. A non-hacker who is +indelicate enough to ask a question like "So, are you working on +finding that bug <i>now</i> or leaving it until later?" is +likely to get the perfectly correct answer "Yes!" (that is, "Yes, +I'm doing it either now or later, and you didn't ask +which!").</p> + +<hr> +Node:<a name="InternationalStyle">International Style</a>, +Next:<a rel="next" href="#Lamer-speak">Lamer-speak</a>, +Previous:<a rel="previous" href="#HackerSpeechStyle">Hacker +Speech Style</a>, Up:<a rel="up" href="#Top">Top</a> <br> + + +<h2>International Style</h2> + +<p>Although the Jargon File remains primarily a lexicon of hacker +usage in American English, we have made some effort to get input +from abroad. Though the hacker-speak of other languages often +uses translations of jargon from English (often as transmitted to +them by earlier Jargon File versions!), the local variations are +interesting, and knowledge of them may be of some use to +travelling hackers.</p> + +<p>There are some references herein to `Commonwealth hackish'. +These are intended to describe some variations in hacker usage as +reported in the English spoken in Great Britain and the +Commonwealth (Canada, Australia, India, etc. -- though Canada is +heavily influenced by American usage). There is also an entry on +<b><a href="#CommonwealthHackish">Commonwealth Hackish</a></b> +reporting some general phonetic and vocabulary differences from +U.S. hackish.</p> + +<p>Hackers in Western Europe and (especially) Scandinavia report +that they often use a mixture of English and their native +languages for technical conversation. Occasionally they develop +idioms in their English usage that are influenced by their +native-language styles. Some of these are reported here.</p> + +<p>On the other hand, English often gives rise to grammatical and +vocabulary mutations in the native language. For example, Italian +hackers often use the nonexistent verbs `scrollare' (to scroll) +and `deletare' (to delete) rather than native Italian `scorrere' +and `cancellare'. Similarly, the English verb `to hack' has been +seen conjugated in Swedish. In German, many Unix terms in English +are casually declined as if they were German verbs - thus: +mount/mounten/gemountet; grep/grepen/gegrept; +fork/forken/geforkt; core dump/core-dumpen, core-gedumpt. And +Spanish-speaking hackers use `linkar' (to link), `debugear' (to +debug), and `lockear' (to lock).</p> + +<p>European hackers report that this happens partly because the +English terms make finer distinctions than are available in their +native vocabularies, and partly because deliberate +language-crossing makes for amusing wordplay.</p> + +<p>A few notes on hackish usages in Russian have been added where +they are parallel with English idioms and thus comprehensible to +English-speakers.</p> + +<hr> +Node:<a name="Lamer-speak">Lamer-speak</a>, Next:<a rel="next" href="#PronunciationGuide">Pronunciation Guide</a>, +Previous:<a rel="previous" href="#InternationalStyle">International Style</a>, Up:<a rel="up" href="#Top">Top</a> <br> + + +<h2>Crackers, Phreaks, and Lamers</h2> + +<p>From the early 1980s onward, a flourishing culture of local, +MS-DOS-based bulletin boards developed separately from Internet +hackerdom. The BBS culture has, as its seamy underside, a stratum +of `pirate boards' inhabited by <b><a href="#cracker">cracker</a></b>s, phone phreaks, and <b><a href="#warezd00dz">warez d00dz</a></b>. These people (mostly +teenagers running IBM-PC clones from their bedrooms) have +developed their own characteristic jargon, heavily influenced by +skateboard lingo and underground-rock slang.</p> + +<p>Though crackers often call themselves `hackers', they aren't +(they typically have neither significant programming ability, nor +Internet expertise, nor experience with UNIX or other true +multi-user systems). Their vocabulary has little overlap with +hackerdom's. Nevertheless, this lexicon covers much of it so the +reader will be able to understand what goes by on bulletin-board +systems.</p> + +<p>Here is a brief guide to cracker and <b><a href="#warezd00dz">warez d00dz</a></b> usage:</p> + +<ul> +<li>Misspell frequently. The substitutions + +<pre> + phone => fone + freak => phreak +</pre> + +<p>are obligatory.</p> +</li> + +<li>Always substitute `z's for `s's. (i.e. "codes" -> +"codez"). The substitution of 'z' for 's' has evolved so that a +'z' is bow systematically put at the end of words to denote an +illegal or cracking connection. Examples : Appz, passwordz, +passez, utilz, MP3z, distroz, pornz, sitez, gamez, crackz, +serialz, downloadz, FTPz, etc.</li> + +<li>Type random emphasis characters after a post line (i.e. "Hey +Dudes!#!$#$!#!$").</li> + +<li>Use the emphatic `k' prefix ("k-kool", "k-rad", "k-awesome") +frequently.</li> + +<li>Abbreviate compulsively ("I got lotsa warez w/ docs").</li> + +<li>Substitute `0' for `o' ("r0dent", "l0zer").</li> + +<li>TYPE ALL IN CAPS LOCK, SO IT LOOKS LIKE YOU'RE YELLING ALL +THE TIME.</li> +</ul> + +<p>These traits are similar to those of <b><a href="#B1FF">B1FF</a></b>, who originated as a parody of naive <b><a +href="#BBS">BBS</a></b> users; also of his latter-day equivalent +<b><a href="#JeffK.">Jeff K.</a></b>. Occasionally, this sort +of distortion may be used as heavy sarcasm by a real hacker, as +in:</p> + +<pre> + > I got X Windows running under Linux! + + d00d! u R an 31337 hax0r +</pre> + +<p>The only practice resembling this in actual hacker usage is +the substitution of a dollar sign of `s' in names of products or +service felt to be excessively expensive, e.g. Compu$erve, +Micro$oft.</p> + +<p>For further discussion of the pirate-board subculture, see +<b><a href="#lamer">lamer</a></b>, <b><a href="#elite">elite</a></b>, <b><a href="#leech">leech</a></b>, <b><a +href="#poser">poser</a></b>, <b><a href="#cracker">cracker</a></b>, and especially <b><a href="#warezd00dz">warez d00dz</a></b>, <b><a href="#bannersite">banner site</a></b>, <b><a href="#ratiosite">ratio site</a></b>, <b><a href="#leechmode">leech mode</a></b>.</p> + +<hr> +Node:<a name="PronunciationGuide">Pronunciation Guide</a>, +Next:<a rel="next" href="#OtherLexiconConventions">Other +Lexicon Conventions</a>, Previous:<a rel="previous" href="#Lamer-speak">Lamer-speak</a>, Up:<a rel="up" href="#Top">Top</a> <br> + + +<h2>How to Use the Lexicon</h2> + +<h2>Pronunciation Guide</h2> + +<p>Pronunciation keys are provided in the jargon listings for all +entries that are neither dictionary words pronounced as in +standard English nor obvious compounds thereof. Slashes bracket +phonetic pronunciations, which are to be interpreted using the +following conventions:</p> + +<ol type="1" start="1"> +<li>Syllables are hyphen-separated, except that an accent or +back-accent follows each accented syllable (the back-accent marks +a secondary accent in some words of four or more syllables). If +no accent is given, the word is pronounced with equal +accentuation on all syllables (this is common for +abbreviations).</li> + +<li>Consonants are pronounced as in American English. The letter +`g' is always hard (as in "got" rather than "giant"); `ch' is +soft ("church" rather than "chemist"). The letter `j' is the +sound that occurs twice in "judge". The letter `s' is always as +in "pass", never a z sound. The digraph `kh' is the guttural of +"loch" or "l'chaim". The digraph 'gh' is the aspirated g+h of +"bughouse" or "ragheap" (rare in English).</li> + +<li>Uppercase letters are pronounced as their English letter +names; thus (for example) /H-L-L/ is equivalent to /aych el el/. +/Z/ may be pronounced /zee/ or /zed/ depending on your local +dialect.</li> + +<li>Vowels are represented as follows: + +<dl> +<dt>/a/</dt> + +<dd>back, that<br> +</dd> + +<dt>/ah/</dt> + +<dd>father, palm (see note)</dd> + +<dt>/ar/</dt> + +<dd>far, mark</dd> + +<dt>/aw/</dt> + +<dd>flaw, caught</dd> + +<dt>/ay/</dt> + +<dd>bake, rain</dd> + +<dt>/e/</dt> + +<dd>less, men</dd> + +<dt>/ee/</dt> + +<dd>easy, ski</dd> + +<dt>/eir/</dt> + +<dd>their, software</dd> + +<dt>/i/</dt> + +<dd>trip, hit</dd> + +<dt>/i:/</dt> + +<dd>life, sky</dd> + +<dt>/o/</dt> + +<dd>block, stock (see note)</dd> + +<dt>/oh/</dt> + +<dd>flow, sew</dd> + +<dt>/oo/</dt> + +<dd>loot, through</dd> + +<dt>/or/</dt> + +<dd>more, door</dd> + +<dt>/ow/</dt> + +<dd>out, how</dd> + +<dt>/oy/</dt> + +<dd>boy, coin</dd> + +<dt>/uh/</dt> + +<dd>but, some</dd> + +<dt>/u/</dt> + +<dd>put, foot</dd> + +<dt>/y/</dt> + +<dd>yet, young</dd> + +<dt>/yoo/</dt> + +<dd>few, chew</dd> + +<dt>/[y]oo/</dt> + +<dd>/oo/ with optional fronting as in `news' (/nooz/ or +/nyooz/)</dd> +</dl> +</li> +</ol> + +<p>The glyph /*/ is used for the `schwa' sound of unstressed or +occluded vowels (the one that is often written with an +upside-down `e'). The schwa vowel is omitted in syllables +containing vocalic r, l, m or n; that is, `kitten' and `color' +would be rendered /kit'n/ and /kuhl'r/, not /kit'*n/ and +/kuhl'*r/.</p> + +<p>Note that the above table reflects mainly distinctions found +in standard American English (that is, the neutral dialect spoken +by TV network announcers and typical of educated speech in the +Upper Midwest, Chicago, Minneapolis/St. Paul and Philadelphia). +However, we separate /o/ from /ah/, which tend to merge in +standard American. This may help readers accustomed to accents +resembling British Received Pronunciation.</p> + +<p>The intent of this scheme is to permit as many readers as +possible to map the pronunciations into their local dialect by +ignoring some subset of the distinctions we make. Speakers of +British RP, for example, can smash terminal /r/ and all +unstressed vowels. Speakers of many varieties of southern +American will automatically map /o/ to /aw/; and so forth. +(Standard American makes a good reference dialect for this +purpose because it has crisp consonants and more vowel +distinctions than other major dialects, and tends to retain +distinctions between unstressed vowels. It also happens to be +what your editor speaks.)</p> + +<p>Entries with a pronunciation of `//' are written-only usages. +(No, Unix weenies, this does <i>not</i> mean `pronounce like +previous pronunciation'!)</p> + +<hr> +Node:<a name="OtherLexiconConventions">Other Lexicon +Conventions</a>, Next:<a rel="next" href="#FormatforNewEntries">Format for New Entries</a>, +Previous:<a rel="previous" href="#PronunciationGuide">Pronunciation Guide</a>, Up:<a rel="up" href="#Top">Top</a> <br> + + +<h2>Other Lexicon Conventions</h2> + +<p>Entries are sorted in case-blind ASCII collation order (rather +than the letter-by-letter order ignoring interword spacing common +in mainstream dictionaries), except that all entries beginning +with nonalphabetic characters are sorted after Z. The +case-blindness is a feature, not a bug.</p> + +<p>The beginning of each entry is marked by a colon +(<code>:</code>) at the left margin. This convention helps out +tools like hypertext browsers that benefit from knowing where +entry boundaries are, but aren't as context-sensitive as +humans.</p> + +<p>In pure ASCII renderings of the Jargon File, you will see {} +used to bracket words which themselves have entries in the File. +This isn't done all the time for every such word, but it is done +everywhere that a reminder seems useful that the term has a +jargon meaning and one might wish to refer to its entry.</p> + +<p>In this all-ASCII version, headwords for topic entries are +distinguished from those for ordinary entries by being followed +by "::" rather than ":"; similarly, references are surrounded by +"{{" and "}}" rather than "{" and "}".</p> + +<p>Defining instances of terms and phrases appear in `slanted +type'. A defining instance is one which occurs near to or as part +of an explanation of it.</p> + +<p>Prefixed ** is used as linguists do; to mark examples of +incorrect usage.</p> + +<p>We follow the `logical' quoting convention described in the +Writing Style section above. In addition, we reserve double +quotes for actual excerpts of text or (sometimes invented) +speech. Scare quotes (which mark a word being used in a +nonstandard way), and philosopher's quotes (which turn an +utterance into the string of letters or words that name it) are +both rendered with single quotes.</p> + +<p>References such as <code>malloc(3)</code> and +<code>patch(1)</code> are to Unix facilities (some of which, such +as <code>patch(1)</code>, are actually freeware distributed over +Usenet). The Unix manuals use <code>foo(n)</code> to refer to +item foo in section (n) of the manual, where n=1 is utilities, +n=2 is system calls, n=3 is C library routines, n=6 is games, and +n=8 (where present) is system administration utilities. Sections +4, 5, and 7 of the manuals have changed roles frequently and in +any case are not referred to in any of the entries.</p> + +<p>Various abbreviations used frequently in the lexicon are +summarized here:</p> + +<dl> +<dt><i>abbrev.</i></dt> + +<dd>abbreviation</dd> + +<dt><i>adj.</i></dt> + +<dd>adjective</dd> + +<dt><i>adv.</i></dt> + +<dd>adverb</dd> + +<dt><i>alt.</i></dt> + +<dd>alternate</dd> + +<dt><i>cav.</i></dt> + +<dd>caveat</dd> + +<dt><i>conj.</i></dt> + +<dd>conjunction</dd> + +<dt><i>esp.</i></dt> + +<dd>especially</dd> + +<dt><i>excl.</i></dt> + +<dd>exclamation</dd> + +<dt><i>imp.</i></dt> + +<dd>imperative</dd> + +<dt><i>interj.</i></dt> + +<dd>interjection</dd> + +<dt><i>n.</i></dt> + +<dd>noun</dd> + +<dt><i>obs.</i></dt> + +<dd>obsolete</dd> + +<dt><i>pl.</i></dt> + +<dd>plural</dd> + +<dt><i>poss.</i></dt> + +<dd>possibly</dd> + +<dt><i>pref.</i></dt> + +<dd>prefix</dd> + +<dt><i>prob.</i></dt> + +<dd>probably</dd> + +<dt><i>prov.</i></dt> + +<dd>proverbial</dd> + +<dt><i>quant.</i></dt> + +<dd>quantifier</dd> + +<dt><i>suff.</i></dt> + +<dd>suffix</dd> + +<dt><i>syn.</i></dt> + +<dd>synonym (or synonymous with)</dd> + +<dt><i>v.</i></dt> + +<dd>verb (may be transitive or intransitive)</dd> + +<dt><i>var.</i></dt> + +<dd>variant</dd> + +<dt><i>vi.</i></dt> + +<dd>intransitive verb</dd> + +<dt><i>vt.</i></dt> + +<dd>transitive verb</dd> +</dl> + +<p>Where alternate spellings or pronunciations are given, +<i>alt.</i> separates two possibilities with nearly equal +distribution, while <i>var.</i> prefixes one that is markedly +less common than the primary.</p> + +<p>Where a term can be attributed to a particular subculture or +is known to have originated there, we have tried to so indicate. +Here is a list of abbreviations used in etymologies:</p> + +<dl> +<dt>Amateur Packet Radio</dt> + +<dd>A technical culture of ham-radio sites using AX.25 and TCP/IP +for wide-area networking and BBS systems.<br> +</dd> + +<dt>Berkeley</dt> + +<dd>University of California at Berkeley<br> +</dd> + +<dt>BBN</dt> + +<dd>Bolt, Beranek & Newman<br> +</dd> + +<dt>Cambridge</dt> + +<dd>the university in England (<i>not</i> the city in +Massachusetts where MIT happens to be located!)<br> +</dd> + +<dt>CMU</dt> + +<dd>Carnegie-Mellon University<br> +</dd> + +<dt>Commodore</dt> + +<dd>Commodore Business Machines<br> +</dd> + +<dt>DEC</dt> + +<dd>The Digital Equipment Corporation (now Compaq).<br> +</dd> + +<dt>Fairchild</dt> + +<dd>The Fairchild Instruments Palo Alto development group<br> +</dd> + +<dt>FidoNet</dt> + +<dd>See the <b><a href="#FidoNet">FidoNet</a></b> entry<br> +</dd> + +<dt>IBM</dt> + +<dd>International Business Machines<br> +</dd> + +<dt>MIT</dt> + +<dd>Massachusetts Institute of Technology; esp. the legendary MIT +AI Lab culture of roughly 1971 to 1983 and its feeder groups, +including the Tech Model Railroad Club<br> +</dd> + +<dt>NRL</dt> + +<dd>Naval Research Laboratories<br> +</dd> + +<dt>NYU</dt> + +<dd>New York University<br> +</dd> + +<dt>OED</dt> + +<dd>The Oxford English Dictionary<br> +</dd> + +<dt>Purdue</dt> + +<dd>Purdue University<br> +</dd> + +<dt>SAIL</dt> + +<dd>Stanford Artificial Intelligence Laboratory (at Stanford +University)<br> +</dd> + +<dt>SI</dt> + +<dd>From <i>Système International</i>, the name for the +standard conventions of metric nomenclature used in the +sciences<br> +</dd> + +<dt>Stanford</dt> + +<dd>Stanford University<br> +</dd> + +<dt>Sun</dt> + +<dd>Sun Microsystems<br> +</dd> + +<dt>TMRC</dt> + +<dd>Some MITisms go back as far as the Tech Model Railroad Club +(TMRC) at MIT c. 1960. Material marked TMRC is from "An Abridged +Dictionary of the TMRC Language", originally compiled by Pete +Samson in 1959<br> +</dd> + +<dt>UCLA</dt> + +<dd>University of California at Los Angeles<br> +</dd> + +<dt>UK</dt> + +<dd>the United Kingdom (England, Wales, Scotland, Northern +Ireland)<br> +</dd> + +<dt>Usenet</dt> + +<dd>See the <b><a href="#Usenet">Usenet</a></b> entry<br> +</dd> + +<dt>WPI</dt> + +<dd>Worcester Polytechnic Institute, site of a very active +community of PDP-10 hackers during the 1970s<br> +</dd> + +<dt>WWW</dt> + +<dd>The World-Wide-Web.<br> +</dd> + +<dt>XEROX PARC</dt> + +<dd>XEROX's Palo Alto Research Center, site of much pioneering +research in user interface design and networking<br> +</dd> + +<dt>Yale</dt> + +<dd>Yale University</dd> +</dl> + +<br> +<p>Some other etymology abbreviations such as <b><a href="#Unix">Unix</a></b> and <b><a href="#PDP-10">PDP-10</a></b> +refer to technical cultures surrounding specific operating +systems, processors, or other environments. The fact that a term +is labelled with any one of these abbreviations does not +necessarily mean its use is confined to that culture. In +particular, many terms labelled `MIT' and `Stanford' are in quite +general use. We have tried to give some indication of the +distribution of speakers in the usage notes; however, a number of +factors mentioned in the introduction conspire to make these +indications less definite than might be desirable.</p> + +<p>A few new definitions attached to entries are marked +[proposed]. These are usually generalizations suggested by +editors or Usenet respondents in the process of commenting on +previous definitions of those entries. These are <i>not</i> +represented as established jargon.</p> + +<hr> +Node:<a name="FormatforNewEntries">Format for New +Entries</a>, Next:<a rel="next" href="#TheJargonLexicon">The Jargon Lexicon</a>, Previous:<a +rel="previous" href="#OtherLexiconConventions">Other +Lexicon Conventions</a>, Up:<a rel="up" href="#Top">Top</a> <br> + + +<h2>Format For New Entries</h2> + +<p>You can mail submissions for the Jargon File to jargon@snark.thyrsus.com.</p> + +<p>We welcome new jargon, and corrections to or amplifications of +existing entries. You can improve your submission's chances of +being included by adding background information on user +population and years of currency. References to actual usage via +URLs and/or DejaNews pointers are particularly welcomed.</p> + +<p>All contributions and suggestions about the Jargon File will +be considered donations to be placed in the public domain as part +of this File, and may be used in subsequent paper editions. +Submissions may be edited for accuracy, clarity and +concision.</p> + +<p>We are looking to expand the File's range of technical +specialties covered. There are doubtless rich veins of jargon yet +untapped in the scientific computing, graphics, and networking +hacker communities; also in numerical analysis, computer +architectures and VLSI design, language design, and many other +related fields. Send us your jargon!</p> + +<p>We are <i>not</i> interested in straight technical terms +explained by textbooks or technical dictionaries unless an entry +illuminates `underground' meanings or aspects not covered by +official histories. We are also not interested in `joke' entries +-- there is a lot of humor in the file but it must flow naturally +out of the explanations of what hackers do and how they +think.</p> + +<p>It is OK to submit items of jargon you have originated if they +have spread to the point of being used by people who are not +personally acquainted with you. We prefer items to be attested by +independent submission from two different sites.</p> + +<p>An HTML version of the File is available at +http://www.tuxedo.org/jargon. Please send us URLs for materials +related to the entries, so we can enrich the File's link +structure.</p> + +<p>The Jargon File will be regularly maintained and made +available for browsing on the World Wide Web, and will include a +version number. Read it, pass it around, contribute -- this is +<i>your</i> monument!</p> + +<hr> +Node:<a name="TheJargonLexicon">The Jargon Lexicon</a>, +Next:<a rel="next" href="#AppendixA">Appendix A</a>, +Previous:<a rel="previous" href="#FormatforNewEntries">Format for New Entries</a>, Up:<a rel="up" href="#Top">Top</a> <br> + + +<h1>The Jargon Lexicon</h1> + +<ul> +<li><a href="#chap00">= 0 =</a>:</li> + +<li><a href="#chap01">= A =</a>:</li> + +<li><a href="#chap02">= B =</a>:</li> + +<li><a href="#chap03">= C =</a>:</li> + +<li><a href="#chap04">= D =</a>:</li> + +<li><a href="#chap05">= E =</a>:</li> + +<li><a href="#chap06">= F =</a>:</li> + +<li><a href="#chap07">= G =</a>:</li> + +<li><a href="#chap08">= H =</a>:</li> + +<li><a href="#chap09">= I =</a>:</li> + +<li><a href="#chap10">= J =</a>:</li> + +<li><a href="#chap11">= K =</a>:</li> + +<li><a href="#chap12">= L =</a>:</li> + +<li><a href="#chap13">= M =</a>:</li> + +<li><a href="#chap14">= N =</a>:</li> + +<li><a href="#chap15">= O =</a>:</li> + +<li><a href="#chap16">= P =</a>:</li> + +<li><a href="#chap17">= Q =</a>:</li> + +<li><a href="#chap18">= R =</a>:</li> + +<li><a href="#chap19">= S =</a>:</li> + +<li><a href="#chap20">= T =</a>:</li> + +<li><a href="#chap21">= U =</a>:</li> + +<li><a href="#chap22">= V =</a>:</li> + +<li><a href="#chap23">= W =</a>:</li> + +<li><a href="#chap24">= X =</a>:</li> + +<li><a href="#chap25">= Y =</a>:</li> + +<li><a href="#chap26">= Z =</a>:</li> +</ul> + +<hr> +Node:<a name="chap00">= 0 =</a>, Next:<a rel="next" href="#chap01">= A =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= 0 =</h2> + +<ul> +<li><a href="#0">0</a>:</li> + +<li><a href="#1TBS">1TBS</a>:</li> + +<li><a href="#120reset">120 reset</a>:</li> + +<li><a href="#2">2</a>:</li> + +<li><a href="#404">404</a>:</li> + +<li><a href="#404compliant">404 compliant</a>:</li> + +<li><a href="#4.2">4.2</a>:</li> + +<li><a href="#atparty">@-party</a>:</li> +</ul> + +<hr> +Node:<a name="0">0</a>, Next:<a rel="next" href="#1TBS">1TBS</a>, +Up:<a rel="up" href="#chap00">= 0 =</a> <br> + + +<p><b>0</b></p> + +<p>Numeric zero, as opposed to the letter `O' (the 15th letter of +the English alphabet). In their unmodified forms they look a lot +alike, and various kluges invented to make them visually distinct +have compounded the confusion. If your zero is center-dotted and +letter-O is not, or if letter-O looks almost rectangular but zero +looks more like an American football stood on end (or the +reverse), you're probably looking at a modern character display +(though the dotted zero seems to have originated as an option on +IBM 3270 controllers). If your zero is slashed but letter-O is +not, you're probably looking at an old-style ASCII graphic set +descended from the default typewheel on the venerable ASR-33 +Teletype (Scandinavians, for whom Ø is a letter, curse +this arrangement). (Interestingly, the slashed zero long predates +computers; Florian Cajori's monumental "A History of Mathematical +Notations" notes that it was used in the twelfth and thirteenth +centuries.) If letter-O has a slash across it and the zero does +not, your display is tuned for a very old convention used at IBM +and a few other early mainframe makers (Scandinavians curse +<i>this</i> arrangement even more, because it means two of +their letters collide). Some Burroughs/Unisys equipment displays +a zero with a <i>reversed</i> slash. Old CDC computers rendered +letter O as an unbroken oval and 0 as an oval broken at upper +right and lower left. And yet another convention common on early +line printers left zero unornamented but added a tail or hook to +the letter-O so that it resembled an inverted Q or cursive +capital letter-O (this was endorsed by a draft ANSI standard for +how to draw ASCII characters, but the final standard changed the +distinguisher to a tick-mark in the upper-left corner). Are we +sufficiently confused yet?</p> + +<hr> +Node:<a name="1TBS">1TBS</a>, Next:<a rel="next" href="#120reset">120 reset</a>, Previous:<a rel="previous" href="#0">0</a>, Up:<a rel="up" href="#chap00">= 0 =</a> <br> + + +<p><b>1TBS</b> // n.</p> + +<p>The "One True Brace Style"; see <b><a href="#indentstyle">indent style</a></b>.</p> + +<hr> +Node:<a name="120reset">120 reset</a>, Next:<a rel="next" +href="#2">2</a>, Previous:<a rel="previous" href="#1TBS">1TBS</a>, Up:<a rel="up" href="#chap00">= 0 =</a> +<br> + + +<p><b>120 reset</b> /wuhn-twen'tee ree'set/ n.</p> + +<p>[from 120 volts, U.S. wall voltage] To cycle power on a +machine in order to reset or unjam it. Compare <b><a href="#BigRedSwitch">Big Red Switch</a></b>, <b><a href="#powercycle">power cycle</a></b>.</p> + +<hr> +Node:<a name="2">2</a>, Next:<a rel="next" href="#404">404</a>, +Previous:<a rel="previous" href="#120reset">120 reset</a>, +Up:<a rel="up" href="#chap00">= 0 =</a> <br> + + +<p><b>2</b> infix.</p> + +<p>In translation software written by hackers, infix 2 often +represents the syllable <i>to</i> with the connotation +`translate to': as in dvi2ps (DVI to PostScript), int2string +(integer to string), and texi2roff (Texinfo to [nt]roff). Several +versions of a joke have floated around the internet in which some +idiot programmer fixes the Y2K bug by changing all the Y's in +something to K's, as in Januark, Februark, etc.</p> + +<hr> +Node:<a name="404">404</a>, Next:<a rel="next" href="#404compliant">404 compliant</a>, Previous:<a rel="previous" +href="#2">2</a>, Up:<a rel="up" href="#chap00">= 0 =</a> +<br> + + +<p><b>404</b> // n.</p> + +<p>[from the HTTP error "file not found on server"] Extended to +humans to convey that the subject has no idea or no clue - +sapience not found. May be used reflexively; "Uh, I'm 404ing" +means "I'm drawing a blank".</p> + +<hr> +Node:<a name="404compliant">404 compliant</a>, Next:<a rel="next" href="#4.2">4.2</a>, Previous:<a rel="previous" href="#404">404</a>, Up:<a rel="up" href="#chap00">= 0 =</a> +<br> + + +<p><b>404 compliant</b> adj.</p> + +<p>The status of a website which has been completely removed, +usually by the administrators of the hosting site as a result of +net abuse by the website operators. The term is a tongue-in-cheek +reference to the standard "301 compliant" Murkowski Bill +disclaimer used by spammers. See also: <b><a href="#spam">spam</a></b>, <b><a href="#spamvertize">spamvertize</a></b>.</p> + +<hr> +Node:<a name="4.2">4.2</a>, Next:<a rel="next" href="#atparty">@-party</a>, Previous:<a rel="previous" href="#404compliant">404 compliant</a>, Up:<a rel="up" href="#chap00">= 0 =</a> <br> + + +<p><b>4.2</b> /for' poynt too'/ n.</p> + +<p>Without a prefix, this almost invariably refers to <b><a href="#BSD">BSD</a></b> Unix release 4.2. Note that it is an +indication of cluelessness to say "version 4.2", and "release +4.2" is rare; the number stands on its own, or is used in the +more explicit forms 4.2BSD or (less commonly) BSD 4.2. Similar +remarks apply to "4.3", "4.4" and to earlier, less-widespread +releases 4.1 and 2.9.</p> + +<hr> +Node:<a name="atparty">@-party</a>, Next:<a rel="next" href="#abbrev">abbrev</a>, Previous:<a rel="previous" href="#4.2">4.2</a>, Up:<a rel="up" href="#chap00">= 0 =</a> +<br> + + +<p><b>@-party</b> /at'par`tee/ n.</p> + +<p>[from the @-sign in an Internet address] (alt. `@-sign party' +/at'si:n par`tee/) A semi-closed party thrown for hackers at a +science-fiction convention (esp. the annual World Science Fiction +Convention or "Worldcon"); one must have a <b><a href="#networkaddress">network address</a></b> to get in, or at +least be in company with someone who does. One of the most +reliable opportunities for hackers to meet face to face with +people who might otherwise be represented by mere phosphor dots +on their screens. Compare <b><a href="#boink">boink</a></b>.</p> + +<p>The first recorded @-party was held at the Westercon (a U.S. +western regional SF convention) over the July 4th weekend in +1980. It is not clear exactly when the canonical @-party venue +shifted to the Worldcon but it had certainly become established +by Constellation in 1983. Sadly, the @-party tradition has been +in decline since about 1996, mainly because having an @-address +no longer functions as an effective lodge pin.</p> + +<hr> +Node:<a name="chap01">= A =</a>, Next:<a rel="next" href="#chap02">= B =</a>, Previous:<a rel="previous" href="#chap00">= 0 =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= A =</h2> + +<ul> +<li><a href="#abbrev">abbrev</a>:</li> + +<li><a href="#ABEND">ABEND</a>:</li> + +<li><a href="#accumulator">accumulator</a>:</li> + +<li><a href="#ACK">ACK</a>:</li> + +<li><a href="#Acme">Acme</a>:</li> + +<li><a href="#acolyte">acolyte</a>:</li> + +<li><a href="#ad-hockery">ad-hockery</a>:</li> + +<li><a href="#Ada">Ada</a>:</li> + +<li><a href="#addressharvester">address harvester</a>:</li> + +<li><a href="#adger">adger</a>:</li> + +<li><a href="#admin">admin</a>:</li> + +<li><a href="#ADVENT">ADVENT</a>:</li> + +<li><a href="#AFAIK">AFAIK</a>:</li> + +<li><a href="#AFJ">AFJ</a>:</li> + +<li><a href="#AFK">AFK</a>:</li> + +<li><a href="#AI">AI</a>:</li> + +<li><a href="#AI-complete">AI-complete</a>:</li> + +<li><a href="#AIkoans">AI koans</a>:</li> + +<li><a href="#AIDS">AIDS</a>:</li> + +<li><a href="#AIDX">AIDX</a>:</li> + +<li><a href="#airplanerule">airplane rule</a>:</li> + +<li><a href="#Aldersonloop">Alderson loop</a>:</li> + +<li><a href="#aliasingbug">aliasing bug</a>:</li> + +<li><a href="#AliceandBob">Alice and Bob</a>:</li> + +<li><a href="#all-elbows">all-elbows</a>:</li> + +<li><a href="#alphageek">alpha geek</a>:</li> + +<li><a href="#alphaparticles">alpha particles</a>:</li> + +<li><a href="#alt">alt</a>:</li> + +<li><a href="#altbit">alt bit</a>:</li> + +<li><a href="#AluminumBook">Aluminum Book</a>:</li> + +<li><a href="#ambimouseterous">ambimouseterous</a>:</li> + +<li><a href="#Amiga">Amiga</a>:</li> + +<li><a href="#AmigaPersecutionComplex">Amiga Persecution +Complex</a>:</li> + +<li><a href="#amoeba">amoeba</a>:</li> + +<li><a href="#ampoff">amp off</a>:</li> + +<li><a href="#amper">amper</a>:</li> + +<li><a href="#Angband">Angband</a>:</li> + +<li><a href="#anglebrackets">angle brackets</a>:</li> + +<li><a href="#angryfruitsalad">angry fruit salad</a>:</li> + +<li><a href="#annoybot">annoybot</a>:</li> + +<li><a href="#annoyware">annoyware</a>:</li> + +<li><a href="#ANSI">ANSI</a>:</li> + +<li><a href="#ANSIstandard">ANSI standard</a>:</li> + +<li><a href="#ANSIstandardpizza">ANSI standard +pizza</a>:</li> + +<li><a href="#AOLexcl">AOL!</a>:</li> + +<li><a href="#app">app</a>:</li> + +<li><a href="#arena">arena</a>:</li> + +<li><a href="#arg">arg</a>:</li> + +<li><a href="#ARMM">ARMM</a>:</li> + +<li><a href="#armor-plated">armor-plated</a>:</li> + +<li><a href="#asbestos">asbestos</a>:</li> + +<li><a href="#asbestoscorkaward">asbestos cork +award</a>:</li> + +<li><a href="#asbestoslongjohns">asbestos longjohns</a>:</li> + +<li><a href="#ASCII">ASCII</a>:</li> + +<li><a href="#ASCIIart">ASCII art</a>:</li> + +<li><a href="#ASCIIbeticalorder">ASCIIbetical order</a>:</li> + +<li><a href="#astroturfing">astroturfing</a>:</li> + +<li><a href="#atomic">atomic</a>:</li> + +<li><a href="#attoparsec">attoparsec</a>:</li> + +<li><a href="#AUP">AUP</a>:</li> + +<li><a href="#autobogotiphobia">autobogotiphobia</a>:</li> + +<li><a href="#automagically">automagically</a>:</li> + +<li><a href="#avatar">avatar</a>:</li> + +<li><a href="#awk">awk</a>:</li> +</ul> + +<hr> +Node:<a name="abbrev">abbrev</a>, Next:<a rel="next" href="#ABEND">ABEND</a>, Previous:<a rel="previous" href="#atparty">@-party</a>, Up:<a rel="up" href="#chap01">= +A =</a> <br> + + +<p><b>abbrev</b> /*-breev'/, /*-brev'/ n.</p> + +<p>Common abbreviation for `abbreviation'.</p> + +<hr> +Node:<a name="ABEND">ABEND</a>, Next:<a rel="next" href="#accumulator">accumulator</a>, Previous:<a rel="previous" href="#abbrev">abbrev</a>, Up:<a rel="up" href="#chap01">= A +=</a> <br> + + +<p><b>ABEND</b> /a'bend/, /*-bend'/ n.</p> + +<p>[ABnormal END] 1. Abnormal termination (of software); <b><a +href="#crash">crash</a></b>; <b><a href="#lossage">lossage</a></b>. Derives from an error message on the +IBM 360; used jokingly by hackers but seriously mainly by <b><a +href="#codegrinder">code grinder</a></b>s. Usually +capitalized, but may appear as `abend'. Hackers will try to +persuade you that ABEND is called `abend' because it is what +system operators do to the machine late on Friday when they want +to call it a day, and hence is from the German `Abend' = +`Evening'. 2. [<i>alt.callahans</i>] Absent By Enforced Net +Deprivation - used in the subject lines of postings warning +friends of an imminent loss of Internet access. (This can be +because of computer downtime, loss of provider, moving or +illness.) Variants of this also appear: ABVND = `Absent By +Voluntary Net Deprivation' and ABSEND = `Absent By Self-Enforced +Net Deprivation' have been sighted.</p> + +<hr> +Node:<a name="accumulator">accumulator</a>, Next:<a rel="next" +href="#ACK">ACK</a>, Previous:<a rel="previous" href="#ABEND">ABEND</a>, Up:<a rel="up" href="#chap01">= A +=</a> <br> + + +<p><b>accumulator</b> n. obs.</p> + +<p>1. Archaic term for a register. On-line use of it as a synonym +for `register' is a fairly reliable indication that the user has +been around for quite a while and/or that the architecture under +discussion is quite old. The term in full is almost never used of +microprocessor registers, for example, though symbolic names for +arithmetic registers beginning in `A' derive from historical use +of the term `accumulator' (and not, actually, from `arithmetic'). +Confusingly, though, an `A' register name prefix may also stand +for `address', as for example on the Motorola 680x0 family. 2. A +register being used for arithmetic or logic (as opposed to +addressing or a loop index), especially one being used to +accumulate a sum or count of many items. This use is in context +of a particular routine or stretch of code. "The FOOBAZ routine +uses A3 as an accumulator." 3. One's in-basket (esp. among +old-timers who might use sense 1). "You want this reviewed? Sure, +just put it in the accumulator." (See <b><a href="#stack">stack</a></b>.)</p> + +<hr> +Node:<a name="ACK">ACK</a>, Next:<a rel="next" href="#Acme">Acme</a>, Previous:<a rel="previous" href="#accumulator">accumulator</a>, Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>ACK</b> /ak/ interj.</p> + +<p>1. [common; from the ASCII mnemonic for 0000110] Acknowledge. +Used to register one's presence (compare mainstream +<i>Yo!</i>). An appropriate response to <b><a href="#ping">ping</a></b> or <b><a href="#ENQ">ENQ</a></b>. 2. [from +the comic strip "Bloom County"] An exclamation of surprised +disgust, esp. in "Ack pffft!" Semi-humorous. Generally this sense +is not spelled in caps (ACK) and is distinguished by a following +exclamation point. 3. Used to politely interrupt someone to tell +them you understand their point (see <b><a href="#NAK">NAK</a></b>). Thus, for example, you might cut off an +overly long explanation with "Ack. Ack. Ack. I get it now". 4. An +affirmative. "Think we ought to ditch that damn NT server for a +Linux box?" "ACK!"</p> + +<p>There is also a usage "ACK?" (from sense 1) meaning "Are you +there?", often used in email when earlier mail has produced no +reply, or during a lull in <b><a href="#talkmode">talk +mode</a></b> to see if the person has gone away (the standard +humorous response is of course <b><a href="#NAK">NAK</a></b> +(sense 1), i.e., "I'm not here").</p> + +<hr> +Node:<a name="Acme">Acme</a>, Next:<a rel="next" href="#acolyte">acolyte</a>, Previous:<a rel="previous" href="#ACK">ACK</a>, Up:<a rel="up" href="#chap01">= A =</a> +<br> + + +<p><b>Acme</b> n.</p> + +<p>The canonical supplier of bizarre, elaborate, and +non-functional gadgetry - where Rube Goldberg and Heath Robinson +(two cartoonists who specialized in elaborate contraptions) shop. +The name has been humorously expanded as A (or American) Company +Making Everything. (In fact, Acme was a real brand sold from +Sears Roebuck catalogs in the early 1900s.) Describing some X as +an "Acme X" either means "This is <b><a href="#insanelygreat">insanely great</a></b>", or, more likely, +"This looks <b><a href="#insanelygreat">insanely great</a></b> +on paper, but in practice it's really easy to shoot yourself in +the foot with it." Compare <b><a href="#pistol">pistol</a></b>.</p> + +<p>This term, specially cherished by American hackers and +explained here for the benefit of our overseas brethren, comes +from the Warner Brothers' series of "Roadrunner" cartoons. In +these cartoons, the famished Wile E. Coyote was forever +attempting to catch up with, trap, and eat the Roadrunner. His +attempts usually involved one or more high-technology Rube +Goldberg devices - rocket jetpacks, catapults, magnetic traps, +high-powered slingshots, etc. These were usually delivered in +large cardboard boxes, labeled prominently with the Acme name. +These devices invariably malfunctioned in improbable and violent +ways.</p> + +<hr> +Node:<a name="acolyte">acolyte</a>, Next:<a rel="next" href="#ad-hockery">ad-hockery</a>, Previous:<a rel="previous" href="#Acme">Acme</a>, Up:<a rel="up" href="#chap01">= A =</a> +<br> + + +<p><b>acolyte</b> n. obs.</p> + +<p>[TMRC] An <b><a href="#OSU">OSU</a></b> privileged enough to +submit data and programs to a member of the <b><a href="#priesthood">priesthood</a></b>.</p> + +<hr> +Node:<a name="ad-hockery">ad-hockery</a>, Next:<a rel="next" +href="#Ada">Ada</a>, Previous:<a rel="previous" href="#acolyte">acolyte</a>, Up:<a rel="up" href="#chap01">= A +=</a> <br> + + +<p><b>ad-hockery</b> /ad-hok'*r-ee/ n.</p> + +<p>[Purdue] 1. Gratuitous assumptions made inside certain +programs, esp. expert systems, which lead to the appearance of +semi-intelligent behavior but are in fact entirely arbitrary. For +example, fuzzy-matching of input tokens that might be typing +errors against a symbol table can make it look as though a +program knows how to spell. 2. Special-case code to cope with +some awkward input that would otherwise cause a program to <b><a +href="#choke">choke</a></b>, presuming normal inputs are dealt +with in some cleaner and more regular way. Also called +`ad-hackery', `ad-hocity' (/ad-hos'*-tee/), `ad-crockery'. See +also <b><a href="#ELIZAeffect">ELIZA effect</a></b>.</p> + +<hr> +Node:<a name="Ada">Ada</a>, Next:<a rel="next" href="#addressharvester">address harvester</a>, Previous:<a rel="previous" href="#ad-hockery">ad-hockery</a>, Up:<a rel="up" +href="#chap01">= A =</a> <br> + + +<p><b>Ada</b> n.</p> + +<p>A <b><a href="#Pascal">Pascal</a></b>-descended language that +was at one time made mandatory for Department of Defense software +projects by the Pentagon. Hackers are nearly unanimous in +observing that, technically, it is precisely what one might +expect given that kind of endorsement by fiat; designed by +committee, crockish, difficult to use, and overall a disastrous, +multi-billion-dollar boondoggle (one common description wss "The +PL/I of the 1980s"). Hackers find Ada's exception-handling and +inter-process communication features particularly hilarious. Ada +Lovelace (the daughter of Lord Byron who became the world's first +programmer while cooperating with Charles Babbage on the design +of his mechanical computing engines in the mid-1800s) would +almost certainly blanch at the use to which her name has latterly +been put; the kindest thing that has been said about it is that +there is probably a good small language screaming to get out from +inside its vast, <b><a href="#elephantine">elephantine</a></b> +bulk.</p> + +<hr> +Node:<a name="addressharvester">address harvester</a>, Next:<a +rel="next" href="#adger">adger</a>, Previous:<a rel="previous" +href="#Ada">Ada</a>, Up:<a rel="up" href="#chap01">= A +=</a> <br> + + +<p><b>address harvester</b> n.</p> + +<p>A robot that searches web pages and/or filters netnews traffic +looking for valid email addresses. Some address harvesters are +benign, used only for compiling address directories. Most, +unfortunately, are run by miscreants compiling address lists to +<b><a href="#spam">spam</a></b>. Address harvesters can be foiled +by a <b><a href="#teergrube">teergrube</a></b>.</p> + +<hr> +Node:<a name="adger">adger</a>, Next:<a rel="next" href="#admin">admin</a>, Previous:<a rel="previous" href="#addressharvester">address harvester</a>, Up:<a rel="up" +href="#chap01">= A =</a> <br> + + +<p><b>adger</b> /aj'r/ vt.</p> + +<p>[UCLA mutant of <b><a href="#nadger">nadger</a></b>, poss. +also from the middle name of an infamous <b><a href="#tenuredgraduatestudent">tenured graduate student</a></b>] +To make a bonehead move with consequences that could have been +foreseen with even slight mental effort. E.g., "He started +removing files and promptly adgered the whole project". Compare +<b><a href="#dumbassattack">dumbass attack</a></b>.</p> + +<hr> +Node:<a name="admin">admin</a>, Next:<a rel="next" href="#ADVENT">ADVENT</a>, Previous:<a rel="previous" href="#adger">adger</a>, Up:<a rel="up" href="#chap01">= A +=</a> <br> + + +<p><b>admin</b> /ad-min'/ n.</p> + +<p>Short for `administrator'; very commonly used in speech or +on-line to refer to the systems person in charge on a computer. +Common constructions on this include `sysadmin' and `site admin' +(emphasizing the administrator's role as a site contact for email +and news) or `newsadmin' (focusing specifically on news). Compare +<b><a href="#postmaster">postmaster</a></b>, <b><a href="#sysop">sysop</a></b>, <b><a href="#systemmangler">system +mangler</a></b>.</p> + +<hr> +Node:<a name="ADVENT">ADVENT</a>, Next:<a rel="next" href="#AFAIK">AFAIK</a>, Previous:<a rel="previous" href="#admin">admin</a>, Up:<a rel="up" href="#chap01">= A +=</a> <br> + + +<p><b>ADVENT</b> /ad'vent/ n.</p> + +<p>The prototypical computer adventure game, first designed by +Will Crowther on the <b><a href="#PDP-10">PDP-10</a></b> in the +mid-1970s as an attempt at computer-refereed fantasy gaming, and +expanded into a puzzle-oriented game by Don Woods at Stanford in +1976. (Woods had been one of the authors of <b><a href="#INTERCAL">INTERCAL</a></b>.) Now better known as Adventure or +Colossal Cave Adventure, but the <b><a href="#TOPS-10">TOPS-10</a></b> operating system permitted only +six-letter filenames. See also <b><a href="#vadding">vadding</a></b>, <b><a href="#Zork">Zork</a></b>, and +<b><a href="#Infocom">Infocom</a></b>.</p> + +<p>This game defined the terse, dryly humorous style since +expected in text adventure games, and popularized several tag +lines that have become fixtures of hacker-speak: "A huge green +fierce snake bars the way!" "I see no X here" (for some noun X). +"You are in a maze of twisty little passages, all alike." "You +are in a little maze of twisty passages, all different." The +`magic words' <b><a href="#xyzzy">xyzzy</a></b> and <b><a href="#plugh">plugh</a></b> also derive from this game.</p> + +<p>Crowther, by the way, participated in the exploration of the +Mammoth & Flint Ridge cave system; it actually <i>has</i> a +`Colossal Cave' and a `Bedquilt' as in the game, and the `Y2' +that also turns up is cavers' jargon for a map reference to a +secondary entrance.</p> + +<p>ADVENT sources are available for FTP at <a href="ftp://ftp.wustl.edu/doc/misc/if-archive/games/source/advent.tar.Z"> +ftp://ftp.wustl.edu/doc/misc/if-archive/games/source/advent.tar.Z</a>. +</p> + +<hr> +Node:<a name="AFAIK">AFAIK</a>, Next:<a rel="next" href="#AFJ">AFJ</a>, Previous:<a rel="previous" href="#ADVENT">ADVENT</a>, Up:<a rel="up" href="#chap01">= A +=</a> <br> + + +<p><b>AFAIK</b> // n.</p> + +<p>[Usenet] Abbrev. for "As Far As I Know".</p> + +<hr> +Node:<a name="AFJ">AFJ</a>, Next:<a rel="next" href="#AFK">AFK</a>, Previous:<a rel="previous" href="#AFAIK">AFAIK</a>, Up:<a rel="up" href="#chap01">= A +=</a> <br> + + +<p><b>AFJ</b> // n.</p> + +<p>Written-only abbreviation for "April Fool's Joke". Elaborate +April Fool's hoaxes are a long-established tradition on Usenet +and Internet; see <b><a href="#kremvax">kremvax</a></b> for an +example. In fact, April Fool's Day is the <i>only</i> seasonal +holiday consistently marked by customary observances on Internet +and other hacker networks.</p> + +<hr> +Node:<a name="AFK">AFK</a>, Next:<a rel="next" href="#AI">AI</a>, +Previous:<a rel="previous" href="#AFJ">AFJ</a>, Up:<a rel="up" +href="#chap01">= A =</a> <br> + + +<p><b>AFK</b></p> + +<p>[MUD] Abbrev. for "Away From Keyboard". Used to notify others +that you will be momentarily unavailable online. eg. "Let's not +go kill that frost giant yet, I need to go AFK to make a phone +call". Often MUDs will have a command to politely inform others +of your absence when they try to talk with you. The term is not +restricted to MUDs, however, and has become common in many chat +situations, from IRC to Unix talk.</p> + +<hr> +Node:<a name="AI">AI</a>, Next:<a rel="next" href="#AI-complete">AI-complete</a>, Previous:<a rel="previous" href="#AFK">AFK</a>, Up:<a rel="up" href="#chap01">= A =</a> +<br> + + +<p><b>AI</b> /A-I/ n.</p> + +<p>Abbreviation for `Artificial Intelligence', so common that the +full form is almost never written or spoken among hackers.</p> + +<hr> +Node:<a name="AI-complete">AI-complete</a>, Next:<a rel="next" +href="#AIkoans">AI koans</a>, Previous:<a rel="previous" href="#AI">AI</a>, Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>AI-complete</b> /A-I k*m-pleet'/ adj.</p> + +<p>[MIT, Stanford: by analogy with `NP-complete' (see <b><a href="#NP-">NP-</a></b>)] Used to describe problems or subproblems in +AI, to indicate that the solution presupposes a solution to the +`strong AI problem' (that is, the synthesis of a human-level +intelligence). A problem that is AI-complete is, in other words, +just too hard.</p> + +<p>Examples of AI-complete problems are `The Vision Problem' +(building a system that can see as well as a human) and `The +Natural Language Problem' (building a system that can understand +and speak a natural language as well as a human). These may +appear to be modular, but all attempts so far (1999) to solve +them have foundered on the amount of context information and +`intelligence' they seem to require. See also <b><a href="#gedanken">gedanken</a></b>.</p> + +<hr> +Node:<a name="AIkoans">AI koans</a>, Next:<a rel="next" href="#AIDS">AIDS</a>, Previous:<a rel="previous" href="#AI-complete">AI-complete</a>, Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>AI koans</b> /A-I koh'anz/ pl.n.</p> + +<p>A series of pastiches of Zen teaching riddles created by Danny +Hillis at the MIT AI Lab around various major figures of the +Lab's culture (several are included under <b><a href="#SomeAIKoans">Some AI Koans</a></b> in Appendix A). See +also <b><a href="#hahaonlyserious">ha ha only +serious</a></b>, <b><a href="#mu">mu</a></b>, and <b><a href="#hackerhumor">hacker humor</a></b>.</p> + +<hr> +Node:<a name="AIDS">AIDS</a>, Next:<a rel="next" href="#AIDX">AIDX</a>, Previous:<a rel="previous" href="#AIkoans">AI koans</a>, Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>AIDS</b> /aydz/ n.</p> + +<p>Short for A* Infected Disk Syndrome (`A*' is a <b><a href="#glob">glob</a></b> pattern that matches, but is not limited to, +Apple or Amiga), this condition is quite often the result of +practicing unsafe <b><a href="#SEX">SEX</a></b>. See <b><a href="#virus">virus</a></b>, <b><a href="#worm">worm</a></b>, <b><a +href="#Trojanhorse">Trojan horse</a></b>, <b><a href="#virgin">virgin</a></b>.</p> + +<hr> +Node:<a name="AIDX">AIDX</a>, Next:<a rel="next" href="#airplanerule">airplane rule</a>, Previous:<a rel="previous" +href="#AIDS">AIDS</a>, Up:<a rel="up" href="#chap01">= A +=</a> <br> + + +<p><b>AIDX</b> /ayd'k*z/ n.</p> + +<p>Derogatory term for IBM's perverted version of Unix, AIX, +especially for the AIX 3.? used in the IBM RS/6000 series (some +hackers think it is funnier just to pronounce "AIX" as "aches"). +A victim of the dreaded "hybridism" disease, this attempt to +combine the two main currents of the Unix stream (<b><a href="#BSD">BSD</a></b> and <b><a href="#USGUnix">USG Unix</a></b>) +became a <b><a href="#monstrosity">monstrosity</a></b> to haunt +system administrators' dreams. For example, if new accounts are +created while many users are logged on, the load average jumps +quickly over 20 due to silly implementation of the user +databases. For a quite similar disease, compare <b><a href="#HP-SUX">HP-SUX</a></b>. Also, compare <b><a href="#Macintrash">Macintrash</a></b>, <b><a href="#NominalSemidestructor">Nominal Semidestructor</a></b>, <b><a +href="#ScumOS">ScumOS</a></b>, <b><a href="#sun-stools">sun-stools</a></b>.</p> + +<hr> +Node:<a name="airplanerule">airplane rule</a>, Next:<a rel="next" href="#Aldersonloop">Alderson loop</a>, Previous:<a +rel="previous" href="#AIDX">AIDX</a>, Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>airplane rule</b> n.</p> + +<p>"Complexity increases the possibility of failure; a +twin-engine airplane has twice as many engine problems as a +single-engine airplane." By analogy, in both software and +electronics, the rule that simplicity increases robustness. It is +correspondingly argued that the right way to build reliable +systems is to put all your eggs in one basket, after making sure +that you've built a really <i>good</i> basket. See also <b><a +href="#KISSPrinciple">KISS Principle</a></b>, <b><a href="#elegant">elegant</a></b>.</p> + +<hr> +Node:<a name="Aldersonloop">Alderson loop</a>, Next:<a rel="next" href="#aliasingbug">aliasing bug</a>, Previous:<a rel="previous" href="#airplanerule">airplane rule</a>, Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>Alderson loop</b> n.</p> + +<p>[Intel] A special version of an <b><a href="#infiniteloop">infinite loop</a></b> where there is an exit +condition available, but inaccessible in the current +implementation of the code. Typically this is created while +debugging user interface code. An example would be when there is +a menu stating, "Select 1-3 or 9 to quit" and 9 is not allowed by +the function that takes the selection from the user.</p> + +<p>This term received its name from a programmer who had coded a +modal message box in MSAccess with no Ok or Cancel buttons, +thereby disabling the entire program whenever the box came up. +The message box had the proper code for dismissal and even was +set up so that when the non-existent Ok button was pressed the +proper code would be called.</p> + +<hr> +Node:<a name="aliasingbug">aliasing bug</a>, Next:<a rel="next" href="#AliceandBob">Alice and Bob</a>, Previous:<a +rel="previous" href="#Aldersonloop">Alderson loop</a>, Up:<a +rel="up" href="#chap01">= A =</a> <br> + + +<p><b>aliasing bug</b> n.</p> + +<p>A class of subtle programming errors that can arise in code +that does dynamic allocation, esp. via <code>malloc(3)</code> or +equivalent. If several pointers address (`aliases for') a given +hunk of storage, it may happen that the storage is freed or +reallocated (and thus moved) through one alias and then +referenced through another, which may lead to subtle (and +possibly intermittent) lossage depending on the state and the +allocation history of the malloc <b><a href="#arena">arena</a></b>. Avoidable by use of allocation strategies +that never alias allocated core, or by use of higher-level +languages, such as <b><a href="#LISP">LISP</a></b>, which employ +a garbage collector (see <b><a href="#GC">GC</a></b>). Also +called a <b><a href="#stalepointerbug">stale pointer +bug</a></b>. See also <b><a href="#precedencelossage">precedence lossage</a></b>, <b><a href="#smashthestack">smash the stack</a></b>, <b><a href="#fandangooncore">fandango on core</a></b>, <b><a href="#memoryleak">memory leak</a></b>, <b><a href="#memorysmash">memory smash</a></b>, <b><a href="#overrunscrew">overrun screw</a></b>, <b><a href="#spam">spam</a></b>.</p> + +<p>Historical note: Though this term is nowadays associated with +C programming, it was already in use in a very similar sense in +the Algol-60 and FORTRAN communities in the 1960s.</p> + +<hr> +Node:<a name="AliceandBob">Alice and Bob</a>, Next:<a rel="next" href="#all-elbows">all-elbows</a>, Previous:<a rel="previous" href="#aliasingbug">aliasing bug</a>, Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>Alice and Bob</b> n.</p> + +<p>The archetypal individuals used as examples in discussions of +cryptographic protocols. Originally, theorists would say +something like: "A communicates with someone who claims to be B, +So to be sure, A tests that B knows a secret number K. So A sends +to B a random number X. B then forms Y by encrypting X under key +K and sends Y back to A" Because this sort of thing is is quite +hard to follow, theorists stopped using the unadorned letters A +and B to represent the main players and started calling them +Alice and Bob. So now we say "Alice communicates with someone +claiming to be Bob, and to be sure, So Alice tests that Bob knows +a secret number K. Alice sends to Bob a random number X. Bob then +forms Y by encrypting X under key K and sends Y back to Alice". A +whole mythology rapidly grew up around the metasyntactic names; +see http://www.conceptlabs.co.uk/alicebob.html.</p> + +<p>In Bruce Schneier's definitive introductory text "Applied +Cryptography" (2nd ed., 1996, John Wiley & Sons, ISBN +0-471-11709-9) he introduces a table of dramatis personae headed +by Alice and Bob. Others include Carol (a participant in three- +and four-party protocols), Dave (a participant in four-party +protocols), Eve (an eavesdropper), Mallory (a malicious active +attacker), Trent (a trusted arbitrator), Walter (a warden), Peggy +(a prover) and Victor (a verifier). These names for roles are +either already standard or, given the wide popularity of the +book, may be expected to quickly become so.</p> + +<hr> +Node:<a name="all-elbows">all-elbows</a>, Next:<a rel="next" +href="#alphageek">alpha geek</a>, Previous:<a rel="previous" +href="#AliceandBob">Alice and Bob</a>, Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>all-elbows</b> adj.</p> + +<p>[MS-DOS] Of a TSR (terminate-and-stay-resident) IBM PC +program, such as the N pop-up calendar and calculator utilities +that circulate on <b><a href="#BBS">BBS</a></b> systems: +unsociable. Used to describe a program that rudely steals the +resources that it needs without considering that other TSRs may +also be resident. One particularly common form of rudeness is +lock-up due to programs fighting over the keyboard interrupt. See +<b><a href="#rude">rude</a></b>, also <b><a href="#mess-dos">mess-dos</a></b>.</p> + +<hr> +Node:<a name="alphageek">alpha geek</a>, Next:<a rel="next" +href="#alphaparticles">alpha particles</a>, Previous:<a rel="previous" href="#all-elbows">all-elbows</a>, Up:<a rel="up" +href="#chap01">= A =</a> <br> + + +<p><b>alpha geek</b> n.</p> + +<p>[from animal ethologists' `alpha male'] The most technically +accomplished or skillful person in some implied context. "Ask +Larry, he's the alpha geek here."</p> + +<hr> +Node:<a name="alphaparticles">alpha particles</a>, Next:<a +rel="next" href="#alt">alt</a>, Previous:<a rel="previous" href="#alphageek">alpha geek</a>, Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>alpha particles</b> n.</p> + +<p>See <b><a href="#bitrot">bit rot</a></b>.</p> + +<hr> +Node:<a name="alt">alt</a>, Next:<a rel="next" href="#altbit">alt bit</a>, Previous:<a rel="previous" href="#alphaparticles">alpha particles</a>, Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>alt</b> /awlt/</p> + +<p>1. n. The alt shift key on an IBM PC or <b><a href="#clone">clone</a></b> keyboard; see <b><a href="#buckybits">bucky bits</a></b>, sense 2 (though typical PC +usage does not simply set the 0200 bit). 2. n. The `option' key +on a Macintosh; use of this term usually reveals that the speaker +hacked PCs before coming to the Mac (see also <b><a href="#featurekey">feature key</a></b>, which is sometimes +<i>incorrectly</i> called `alt'). 3. n.,obs. [PDP-10; often +capitalized to ALT] Alternate name for the ASCII ESC character +(ASCII 0011011), after the keycap labeling on some older +terminals; also `altmode' (/awlt'mohd/). This character was +almost never pronounced `escape' on an ITS system, in <b><a href="#TECO">TECO</a></b>, or under TOPS-10 -- always alt, as in "Type +alt alt to end a TECO command" or "alt-U onto the system" (for +"log onto the [ITS] system"). This usage probably arose because +alt is more convenient to say than `escape', especially when +followed by another alt or a character (or another alt +<i>and</i> a character, for that matter). 4. The <i>alt</i> +hierarchy on Usenet, the tree of newsgroups created by users +without a formal vote and approval procedure. There is a myth, +not entirely implausible, that <i>alt</i> is acronymic for +"anarchists, lunatics, and terrorists"; but in fact it is simply +short for "alternative".</p> + +<hr> +Node:<a name="altbit">alt bit</a>, Next:<a rel="next" href="#AluminumBook">Aluminum Book</a>, Previous:<a rel="previous" +href="#alt">alt</a>, Up:<a rel="up" href="#chap01">= A +=</a> <br> + + +<p><b>alt bit</b> /awlt bit/ [from alternate] adj.</p> + +<p>See <b><a href="#metabit">meta bit</a></b>.</p> + +<hr> +Node:<a name="AluminumBook">Aluminum Book</a>, Next:<a rel="next" href="#ambimouseterous">ambimouseterous</a>, Previous:<a +rel="previous" href="#altbit">alt bit</a>, Up:<a rel="up" +href="#chap01">= A =</a> <br> + + +<p><b>Aluminum Book</b> n.</p> + +<p>[MIT] "Common LISP: The Language", by Guy L. Steele Jr. +(Digital Press, first edition 1984, second edition 1990). Note +that due to a technical screwup some printings of the second +edition are actually of a color the author describes succinctly +as "yucky green". See also <b><a href="#booktitles">book +titles</a></b>.</p> + +<hr> +Node:<a name="ambimouseterous">ambimouseterous</a>, Next:<a rel="next" href="#Amiga">Amiga</a>, Previous:<a rel="previous" href="#AluminumBook">Aluminum Book</a>, Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>ambimouseterous</b> /am-b*-mows'ter-us/ or +/am-b*-mows'trus/ adj.</p> + +<p>[modeled on <i>ambidextrous</i>] Able to use a mouse with +either hand.</p> + +<hr> +Node:<a name="Amiga">Amiga</a>, Next:<a rel="next" href="#AmigaPersecutionComplex">Amiga Persecution Complex</a>, +Previous:<a rel="previous" href="#ambimouseterous">ambimouseterous</a>, Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>Amiga</b> n</p> + +<p>A series of personal computer models originally sold by +Commodore, based on 680x0 processors, custom support chips and an +operating system that combined some of the best features of +Macintosh and Unix with compatibility with neither.</p> + +<p>The Amiga was released just as the personal computing world +standardized on IBM-PC clones. This prevented it from gaining +serious market share, despite the fact that the first Amigas had +a substantial technological lead on the IBM XTs of the time. +Instead, it acquired a small but zealous population of +enthusiastic hackers who dreamt of one day unseating the clones +(see <b><a href="#AmigaPersecutionComplex">Amiga +Persecution Complex</a></b>). The traits of this culture are both +spoofed and illuminated in +The BLAZE Humor Viewer. The strength of the Amiga platform +seeded a small industry of companies building software and +hardware for the platform, especially in graphics and video +applications (see <b><a href="#videotoaster">video +toaster</a></b>).</p> + +<p>Due to spectacular mismanagement, Commodore did hardly any +R&D, allowing the competition to close Amiga's technological +lead. After Commodore went bankrupt in 1994 the technology passed +through several hands, none of whom did much with it. However, +the Amiga is still being produced in Europe under license and has +a substantial number of fans, which will probably extend the +platform's life considerably.</p> + +<hr> +Node:<a name="AmigaPersecutionComplex">Amiga Persecution +Complex</a>, Next:<a rel="next" href="#amoeba">amoeba</a>, +Previous:<a rel="previous" href="#Amiga">Amiga</a>, Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>Amiga Persecution Complex</b> n.</p> + +<p>The disorder suffered by a particularly egregious variety of +<b><a href="#bigot">bigot</a></b>, those who believe that the +marginality of their preferred machine is the result of some kind +of industry-wide conspiracy (for without a conspiracy of some +kind, the eminent superiority of their beloved shining jewel of a +platform would obviously win over all, market pressures be +damned!) Those afflicted are prone to engaging in <b><a href="#flamewarr">flame war</a></b>s and calling for boycotts and +mailbombings. Amiga Persecution Complex is by no means limited to +Amiga users; NeXT, <b><a href="#NeWS">NeWS</a></b>, <b><a href="#OSslash2">OS/2</a></b>, Macintosh, <b><a href="#LISP">LISP</a></b>, and <b><a href="#GNU">GNU</a></b> users are +also common victims. <b><a href="#Linux">Linux</a></b> users used +to display symptoms very frequently before Linux started winning; +some still do. See also <b><a href="#newbie">newbie</a></b>, +<b><a href="#troll">troll</a></b>, <b><a href="#holywars">holy +wars</a></b>, <b><a href="#weenie">weenie</a></b>, <b><a href="#Getalife">Get a life!</a></b>.</p> + +<hr> +Node:<a name="amoeba">amoeba</a>, Next:<a rel="next" href="#ampoff">amp off</a>, Previous:<a rel="previous" href="#AmigaPersecutionComplex">Amiga Persecution Complex</a>, +Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>amoeba</b> n.</p> + +<p>Humorous term for the Commodore Amiga personal computer.</p> + +<hr> +Node:<a name="ampoff">amp off</a>, Next:<a rel="next" href="#amper">amper</a>, Previous:<a rel="previous" href="#amoeba">amoeba</a>, Up:<a rel="up" href="#chap01">= A +=</a> <br> + + +<p><b>amp off</b> vt.</p> + +<p>[Purdue] To run in <b><a href="#background">background</a></b>. From the Unix shell `&' +operator.</p> + +<hr> +Node:<a name="amper">amper</a>, Next:<a rel="next" href="#Angband">Angband</a>, Previous:<a rel="previous" href="#ampoff">amp off</a>, Up:<a rel="up" href="#chap01">= +A =</a> <br> + + +<p><b>amper</b> n.</p> + +<p>Common abbreviation for the name of the ampersand (`&', +ASCII 0100110) character. See <b><a href="#ASCII">ASCII</a></b> +for other synonyms.</p> + +<hr> +Node:<a name="Angband">Angband</a>, Next:<a rel="next" href="#anglebrackets">angle brackets</a>, Previous:<a rel="previous" href="#amper">amper</a>, Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>Angband</b> n. /ang'band/</p> + +<p>Like <b><a href="#nethack">nethack</a></b>, <b><a href="#moria">moria</a></b>, and <b><a href="#rogue">rogue</a></b>, +one of the large freely distributed Dungeons-and-Dragons-like +simulation games, available for a wide range of machines and +operating systems. The name is from Tolkien's Pits of Angband +(compare <b><a href="#elderdays">elder days</a></b>, <b><a +href="#elvish">elvish</a></b>). Has been described as "Moria on +steroids"; but, unlike Moria, many aspects of the game are +customizable. This leads many hackers and would-be hackers into +fooling with these instead of doing productive work. There are +many Angband variants, of which the most notorious is probably +the rather whimsical Zangband. In this game, when a key that does +not correspond to a command is pressed, the game will display +"Type ? for help" 50% of the time. The other 50% of the time, +random error messages including "An error has occurred because an +error of type 42 has occurred" and "Windows 95 uninstalled +successfully" will be displayed. Zangband also allows the player +to kill Santa Claus (who has some really good stuff, but also has +a lot of friends), "Bull Gates", and Barney the Dinosaur (but be +watchful; Barney has a nasty case of halitosis). There is an +official angband home page at http://www.phial.com/angband +and a zangband one at http://thangorodrim.angband.org. +See also <b><a href="#RandomNumberGod">Random Number +God</a></b>.</p> + +<hr> +Node:<a name="anglebrackets">angle brackets</a>, Next:<a rel="next" href="#angryfruitsalad">angry fruit salad</a>, +Previous:<a rel="previous" href="#Angband">Angband</a>, Up:<a +rel="up" href="#chap01">= A =</a> <br> + + +<p><b>angle brackets</b> n.</p> + +<p>Either of the characters <code><</code> (ASCII 0111100) and +<code>></code> (ASCII 0111110) (ASCII less-than or +greater-than signs). Typographers in the <b><a href="#RealWorld">Real World</a></b> use angle brackets which are +either taller and slimmer (the ISO `Bra' and `Ket' characters), +or significantly smaller (single or double guillemets) than the +less-than and greater-than signs. See <b><a href="#broket">broket</a></b>, <b><a href="#ASCII">ASCII</a></b>.</p> + +<hr> +Node:<a name="angryfruitsalad">angry fruit salad</a>, +Next:<a rel="next" href="#annoybot">annoybot</a>, Previous:<a +rel="previous" href="#anglebrackets">angle brackets</a>, Up:<a +rel="up" href="#chap01">= A =</a> <br> + + +<p><b>angry fruit salad</b> n.</p> + +<p>A bad visual-interface design that uses too many colors. (This +term derives, of course, from the bizarre day-glo colors found in +canned fruit salad.) Too often one sees similar effects from +interface designers using color window systems such as <b><a +href="#X">X</a></b>; there is a tendency to create displays that +are flashy and attention-getting but uncomfortable for long-term +use.</p> + +<hr> +Node:<a name="annoybot">annoybot</a>, Next:<a rel="next" href="#annoyware">annoyware</a>, Previous:<a rel="previous" href="#angryfruitsalad">angry fruit salad</a>, Up:<a rel="up" +href="#chap01">= A =</a> <br> + + +<p><b>annoybot</b> /*-noy-bot/ n.</p> + +<p>[IRC] See <b><a href="#bot">bot</a></b>.</p> + +<hr> +Node:<a name="annoyware">annoyware</a>, Next:<a rel="next" href="#ANSI">ANSI</a>, Previous:<a rel="previous" href="#annoybot">annoybot</a>, Up:<a rel="up" href="#chap01">= +A =</a> <br> + + +<p><b>annoyware</b> n.</p> + +<p>A type of <b><a href="#shareware">shareware</a></b> that +frequently disrupts normal program operation to display requests +for payment to the author in return for the ability to disable +the request messages. (Also called `nagware') The requests +generally require user action to acknowledge the message before +normal operation is resumed and are often tied to the most +frequently used features of the software. See also <b><a href="#careware">careware</a></b>, <b><a href="#charityware">charityware</a></b>, <b><a href="#crippleware">crippleware</a></b>, <b><a href="#freeware">freeware</a></b>, <b><a href="#FRS">FRS</a></b>, +<b><a href="#guiltware">guiltware</a></b>, <b><a href="#postcardware">postcardware</a></b>, and <b><a href="#-ware">-ware</a></b>; compare <b><a href="#payware">payware</a></b>.</p> + +<hr> +Node:<a name="ANSI">ANSI</a>, Next:<a rel="next" href="#ANSIstandard">ANSI standard</a>, Previous:<a rel="previous" +href="#annoyware">annoyware</a>, Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>ANSI</b> /an'see/</p> + +<p>1. n. [techspeak] The American National Standards Institute. +ANSI, along with the International Organization for Standards +(ISO), standardized the C programming language (see <b><a href="#KandR">K&R</a></b>, <b><a href="#ClassicC">Classic +C</a></b>), and promulgates many other important software +standards. 2. n. [techspeak] A terminal may be said to be `ANSI' +if it meets the ANSI X.364 standard for terminal control. +Unfortunately, this standard was both over-complicated and too +permissive. It has been retired and replaced by the ECMA-48 +standard, which shares both flaws. 3. n. [BBS jargon] The set of +screen-painting codes that most MS-DOS and Amiga computers +accept. This comes from the ANSI.SYS device driver that must be +loaded on an MS-DOS computer to view such codes. Unfortunately, +neither DOS ANSI nor the BBS ANSIs derived from it exactly match +the ANSI X.364 terminal standard. For example, the ESC-[1m code +turns on the bold highlight on large machines, but in IBM +PC/MS-DOS ANSI, it turns on `intense' (bright) colors. Also, in +BBS-land, the term `ANSI' is often used to imply that a +particular computer uses or can emulate the IBM high-half +character set from MS-DOS. Particular use depends on context. +Occasionally, the vanilla ASCII character set is used with the +color codes, but on BBSs, ANSI and `IBM characters' tend to go +together.</p> + +<hr> +Node:<a name="ANSIstandard">ANSI standard</a>, Next:<a rel="next" href="#ANSIstandardpizza">ANSI standard pizza</a>, +Previous:<a rel="previous" href="#ANSI">ANSI</a>, Up:<a rel="up" +href="#chap01">= A =</a> <br> + + +<p><b>ANSI standard</b> /an'see stan'd*rd/</p> + +<p>The ANSI standard usage of `ANSI standard' refers to any +practice which is typical or broadly done. It's most +appropriately applied to things that everyone does that are not +quite regulation. For example: ANSI standard shaking of a laser +printer cartridge to get extra life from it, or the ANSI standard +word tripling in names of usenet alt groups.</p> + +<hr> +Node:<a name="ANSIstandardpizza">ANSI standard pizza</a>, +Next:<a rel="next" href="#AOLexcl">AOL!</a>, Previous:<a rel="previous" href="#ANSIstandard">ANSI standard</a>, Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>ANSI standard pizza</b> /an'see stan'd*rd peet'z*/</p> + +<p>[CMU] Pepperoni and mushroom pizza. Coined allegedly because +most pizzas ordered by CMU hackers during some period leading up +to mid-1990 were of that flavor. See also <b><a href="#rotarydebugger">rotary debugger</a></b>; compare <b><a href="#ISOstandardcupoftea">ISO standard cup of +tea</a></b>.</p> + +<hr> +Node:<a name="AOLexcl">AOL!</a>, Next:<a rel="next" href="#app">app</a>, Previous:<a rel="previous" href="#ANSIstandardpizza">ANSI standard pizza</a>, Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>AOL!</b> n.</p> + +<p>[Usenet] Common synonym for "Me, too!" alluding to the +legendary propensity of America Online users to utter contentless +"Me, too!" postings. The number of exclamation points following +varies from zero to five or so. The pseudo-HTML</p> + +<blockquote><AOL>Me, too!</AOL></blockquote> + +<p>is also frequently seen. See also <b><a href="#Septemberthatneverended">September that never +ended</a></b>.</p> + +<hr> +Node:<a name="app">app</a>, Next:<a rel="next" href="#arena">arena</a>, Previous:<a rel="previous" href="#AOLexcl">AOL!</a>, Up:<a rel="up" href="#chap01">= A =</a> +<br> + + +<p><b>app</b> /ap/ n.</p> + +<p>Short for `application program', as opposed to a systems +program. Apps are what systems vendors are forever chasing +developers to create for their environments so they can sell more +boxes. Hackers tend not to think of the things they themselves +run as apps; thus, in hacker parlance the term excludes +compilers, program editors, games, and messaging systems, though +a user would consider all those to be apps. (Broadly, an app is +often a self-contained environment for performing some +well-defined task such as `word processing'; hackers tend to +prefer more general-purpose tools.) See <b><a href="#killerapp">killer app</a></b>; oppose <b><a href="#tool">tool</a></b>, <b><a href="#operatingsystem">operating +system</a></b>.</p> + +<hr> +Node:<a name="arena">arena</a>, Next:<a rel="next" href="#arg">arg</a>, Previous:<a rel="previous" href="#app">app</a>, +Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>arena</b> n.</p> + +<p>[common; Unix] The area of memory attached to a process by +<code>brk(2)</code> and <code>sbrk(2)</code> and used by +<code>malloc(3)</code> as dynamic storage. So named from a +<code>malloc: corrupt arena</code> message emitted when some +early versions detected an impossible value in the free block +list. See <b><a href="#overrunscrew">overrun screw</a></b>, +<b><a href="#aliasingbug">aliasing bug</a></b>, <b><a href="#memoryleak">memory leak</a></b>, <b><a href="#memorysmash">memory smash</a></b>, <b><a href="#smashthestack">smash the stack</a></b>.</p> + +<hr> +Node:<a name="arg">arg</a>, Next:<a rel="next" href="#ARMM">ARMM</a>, Previous:<a rel="previous" href="#arena">arena</a>, Up:<a rel="up" href="#chap01">= A +=</a> <br> + + +<p><b>arg</b> /arg/ n.</p> + +<p>Abbreviation for `argument' (to a function), used so often as +to have become a new word (like `piano' from `pianoforte'). "The +sine function takes 1 arg, but the arc-tangent function can take +either 1 or 2 args." Compare <b><a href="#param">param</a></b>, +<b><a href="#parm">parm</a></b>, <b><a href="#var">var</a></b>.</p> + +<hr> +Node:<a name="ARMM">ARMM</a>, Next:<a rel="next" href="#armor-plated">armor-plated</a>, Previous:<a rel="previous" +href="#arg">arg</a>, Up:<a rel="up" href="#chap01">= A +=</a> <br> + + +<p><b>ARMM</b> n.</p> + +<p>[acronym, `Automated Retroactive Minimal Moderation'] A Usenet +<b><a href="#cancelbot">cancelbot</a></b> created by Dick Depew +of Munroe Falls, Ohio. ARMM was intended to automatically cancel +posts from anonymous-posting sites. Unfortunately, the robot's +recognizer for anonymous postings triggered on its own +automatically-generated control messages! Transformed by this +stroke of programming ineptitude into a monster of +Frankensteinian proportions, it broke loose on the night of March +31, 1993 and proceeded to <b><a href="#spam">spam</a></b> +<i>news.admin.policy</i> with a recursive explosion of over 200 +messages.</p> + +<p>ARMM's bug produced a recursive <b><a href="#cascade">cascade</a></b> of messages each of which mechanically +added text to the ID and Subject and some other headers of its +parent. This produced a flood of messages in which each header +took up several screens and each message ID and subject line got +longer and longer and longer.</p> + +<p>Reactions varied from amusement to outrage. The pathological +messages crashed at least one mail system, and upset people +paying line charges for their Usenet feeds. One poster described +the ARMM debacle as "instant Usenet history" (also establishing +the term <b><a href="#despew">despew</a></b>), and it has since +been widely cited as a cautionary example of the havoc the +combination of good intentions and incompetence can wreak on a +network. Compare <b><a href="#GreatWorm">Great Worm</a></b>; +<b><a href="#sorcerersapprenticemode">sorcerer's +apprentice mode</a></b>. See also <b><a href="#softwarelaser">software laser</a></b>, <b><a href="#networkmeltdown">network meltdown</a></b>.</p> + +<hr> +Node:<a name="armor-plated">armor-plated</a>, Next:<a rel="next" +href="#asbestos">asbestos</a>, Previous:<a rel="previous" href="#ARMM">ARMM</a>, Up:<a rel="up" href="#chap01">= A =</a> +<br> + + +<p><b>armor-plated</b> n.</p> + +<p>Syn. for <b><a href="#bulletproof">bulletproof</a></b>.</p> + +<hr> +Node:<a name="asbestos">asbestos</a>, Next:<a rel="next" href="#asbestoscorkaward">asbestos cork award</a>, Previous:<a +rel="previous" href="#armor-plated">armor-plated</a>, Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>asbestos</b> adj.</p> + +<p>[common] Used as a modifier to anything intended to protect +one from <b><a href="#flame">flame</a></b>s; also in other highly +<b><a href="#flame">flame</a></b>-suggestive usages. See, for +example, <b><a href="#asbestoslongjohns">asbestos +longjohns</a></b> and <b><a href="#asbestoscorkaward">asbestos cork award</a></b>.</p> + +<hr> +Node:<a name="asbestoscorkaward">asbestos cork award</a>, +Next:<a rel="next" href="#asbestoslongjohns">asbestos +longjohns</a>, Previous:<a rel="previous" href="#asbestos">asbestos</a>, Up:<a rel="up" href="#chap01">= +A =</a> <br> + + +<p><b>asbestos cork award</b> n.</p> + +<p>Once, long ago at MIT, there was a <b><a href="#flamer">flamer</a></b> so consistently obnoxious that another +hacker designed, had made, and distributed posters announcing +that said flamer had been nominated for the `asbestos cork +award'. (Any reader in doubt as to the intended application of +the cork should consult the etymology under <b><a href="#flame">flame</a></b>.) Since then, it is agreed that only a +select few have risen to the heights of bombast required to earn +this dubious dignity -- but there is no agreement on +<i>which</i> few.</p> + +<hr> +Node:<a name="asbestoslongjohns">asbestos longjohns</a>, +Next:<a rel="next" href="#ASCII">ASCII</a>, Previous:<a rel="previous" href="#asbestoscorkaward">asbestos cork +award</a>, Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>asbestos longjohns</b> n.</p> + +<p>Notional garments donned by <b><a href="#Usenet">Usenet</a></b> posters just before emitting a remark +they expect will elicit <b><a href="#flamage">flamage</a></b>. +This is the most common of the <b><a href="#asbestos">asbestos</a></b> coinages. Also `asbestos underwear', +`asbestos overcoat', etc.</p> + +<hr> +Node:<a name="ASCII">ASCII</a>, Next:<a rel="next" href="#ASCIIart">ASCII art</a>, Previous:<a rel="previous" href="#asbestoslongjohns">asbestos longjohns</a>, Up:<a rel="up" +href="#chap01">= A =</a> <br> + + +<p><b>ASCII</b> /as'kee/ n.</p> + +<p>[originally an acronym (American Standard Code for Information +Interchange) but now merely conventional] The predominant +character set encoding of present-day computers. The standard +version uses 7 bits for each character, whereas most earlier +codes (including early drafts of of ASCII prior to June 1961) +used fewer. This change allowed the inclusion of lowercase +letters -- a major <b><a href="#win">win</a></b> -- but it did +not provide for accented letters or any other letterforms not +used in English (such as the German sharp-S or the ae-ligature +which is a letter in, for example, Norwegian). It could be worse, +though. It could be much worse. See <b><a href="#EBCDIC">EBCDIC</a></b> to understand how. A history of ASCII +and its ancestors is at http://www.wps.com/texts/codes/index.html.</p> + +<p>Computers are much pickier and less flexible about spelling +than humans; thus, hackers need to be very precise when talking +about characters, and have developed a considerable amount of +verbal shorthand for them. Every character has one or more names +-- some formal, some concise, some silly. Common jargon names for +ASCII characters are collected here. See also individual entries +for <b><a href="#bang">bang</a></b>, <b><a href="#excl">excl</a></b>, <b><a href="#open">open</a></b>, <b><a +href="#ques">ques</a></b>, <b><a href="#semi">semi</a></b>, <b><a +href="#shriek">shriek</a></b>, <b><a href="#splat">splat</a></b>, +<b><a href="#twiddle">twiddle</a></b>, and <b><a href="#YuShiangWholeFish">Yu-Shiang Whole Fish</a></b>.</p> + +<p>This list derives from revision 2.3 of the Usenet ASCII +pronunciation guide. Single characters are listed in ASCII order; +character pairs are sorted in by first member. For each +character, common names are given in rough order of popularity, +followed by names that are reported but rarely seen; official +ANSI/CCITT names are surrounded by brokets: <>. Square +brackets mark the particularly silly names introduced by <b><a +href="#INTERCAL">INTERCAL</a></b>. The abbreviations "l/r" and +"o/c" stand for left/right and "open/close" respectively. +Ordinary parentheticals provide some usage information.</p> + +<dl> +<dt><tt>!</tt></dt> + +<dd>Common: <b><a href="#bang">bang</a></b>; pling; excl; shriek; +ball-bat; <exclamation mark>. Rare: factorial; exclam; +smash; cuss; boing; yell; wow; hey; wham; eureka; [spark-spot]; +soldier, control.<br> +</dd> + +<dt><tt>"</tt></dt> + +<dd>Common: double quote; quote. Rare: literal mark; +double-glitch; <quotation marks>; <dieresis>; dirk; +[rabbit-ears]; double prime.<br> +</dd> + +<dt><tt>#</tt></dt> + +<dd>Common: number sign; pound; pound sign; hash; sharp; <b><a +href="#crunch">crunch</a></b>; hex; [mesh]. Rare: grid; +crosshatch; octothorpe; flash; <square>, pig-pen; +tictactoe; scratchmark; thud; thump; <b><a href="#splat">splat</a></b>.<br> +</dd> + +<dt><tt>$</tt></dt> + +<dd>Common: dollar; <dollar sign>. Rare: currency symbol; +buck; cash; string (from BASIC); escape (when used as the echo of +ASCII ESC); ding; cache; [big money].<br> +</dd> + +<dt><tt>%</tt></dt> + +<dd>Common: percent; <percent sign>; mod; grapes. Rare: +[double-oh-seven].<br> +</dd> + +<dt><tt>&</tt></dt> + +<dd>Common: <ampersand>; amper; and, and sign. Rare: +address (from C); reference (from C++); andpersand; bitand; +background (from <code>sh(1)</code>); pretzel; amp. [INTERCAL +called this `ampersand'; what could be sillier?]<br> +</dd> + +<dt><tt>'</tt></dt> + +<dd>Common: single quote; quote; <apostrophe>. Rare: prime; +glitch; tick; irk; pop; [spark]; <closing single quotation +mark>; <acute accent>.<br> +</dd> + +<dt><tt>( )</tt></dt> + +<dd>Common: l/r paren; l/r parenthesis; left/right; open/close; +paren/thesis; o/c paren; o/c parenthesis; l/r parenthesis; l/r +banana. Rare: so/already; lparen/rparen; <opening/closing +parenthesis>; o/c round bracket, l/r round bracket, +[wax/wane]; parenthisey/unparenthisey; l/r ear.<br> +</dd> + +<dt><tt>*</tt></dt> + +<dd>Common: star; [<b><a href="#splat">splat</a></b>]; +<asterisk>. Rare: wildcard; gear; dingle; mult; spider; +aster; times; twinkle; glob (see <b><a href="#glob">glob</a></b>); <b><a href="#NathanHale">Nathan +Hale</a></b>.<br> +</dd> + +<dt><tt>+</tt></dt> + +<dd>Common: <plus>; add. Rare: cross; [intersection].<br> +</dd> + +<dt><tt>,</tt></dt> + +<dd>Common: <comma>. Rare: <cedilla>; [tail].<br> +</dd> + +<dt><tt>-</tt></dt> + +<dd>Common: dash; <hyphen>; <minus>. Rare: [worm]; +option; dak; bithorpe.<br> +</dd> + +<dt><tt>.</tt></dt> + +<dd>Common: dot; point; <period>; <decimal point>. +Rare: radix point; full stop; [spot].<br> +</dd> + +<dt><tt>/</tt></dt> + +<dd>Common: slash; stroke; <slant>; forward slash. Rare: +diagonal; solidus; over; slak; virgule; [slat].<br> +</dd> + +<dt><tt>:</tt></dt> + +<dd>Common: <colon>. Rare: dots; [two-spot].<br> +</dd> + +<dt><tt>;</tt></dt> + +<dd>Common: <semicolon>; semi. Rare: weenie; [hybrid], +pit-thwong.<br> +</dd> + +<dt><tt>< ></tt></dt> + +<dd>Common: <less/greater than>; bra/ket; l/r angle; l/r +angle bracket; l/r broket. Rare: from/{into, towards}; read +from/write to; suck/blow; comes-from/gozinta; in/out; crunch/zap +(all from UNIX); tic/tac; [angle/right angle].<br> +</dd> + +<dt><tt>=</tt></dt> + +<dd>Common: <equals>; gets; takes. Rare: quadrathorpe; +[half-mesh].<br> +</dd> + +<dt><tt>?</tt></dt> + +<dd>Common: query; <question mark>; <b><a href="#ques">ques</a></b>. Rare: whatmark; [what]; wildchar; huh; +hook; buttonhook; hunchback.<br> +</dd> + +<dt><tt>@</tt></dt> + +<dd>Common: at sign; at; strudel. Rare: each; vortex; whorl; +[whirlpool]; cyclone; snail; ape; cat; rose; cabbage; +<commercial at>.<br> +</dd> + +<dt><tt>V</tt></dt> + +<dd>Rare: [book].<br> +</dd> + +<dt><tt>[ ]</tt></dt> + +<dd>Common: l/r square bracket; l/r bracket; <opening/closing +bracket>; bracket/unbracket. Rare: square/unsquare; [U turn/U +turn back].<br> +</dd> + +<dt><tt>\</tt></dt> + +<dd>Common: backslash, hack, whack; escape (from C/UNIX); reverse +slash; slosh; backslant; backwhack. Rare: bash; <reverse +slant>; reversed virgule; [backslat].<br> +</dd> + +<dt><tt>^</tt></dt> + +<dd>Common: hat; control; uparrow; caret; <circumflex>. +Rare: xor sign, chevron; [shark (or shark-fin)]; to the (`to the +power of'); fang; pointer (in Pascal).<br> +</dd> + +<dt><tt>_</tt></dt> + +<dd>Common: <underline>; underscore; underbar; under. Rare: +score; backarrow; skid; [flatworm].<br> +</dd> + +<dt><tt>`</tt></dt> + +<dd>Common: backquote; left quote; left single quote; open quote; +<grave accent>; grave. Rare: backprime; [backspark]; +unapostrophe; birk; blugle; back tick; back glitch; push; +<opening single quotation mark>; quasiquote.<br> +</dd> + +<dt><tt>{ }</tt></dt> + +<dd>Common: o/c brace; l/r brace; l/r squiggly; l/r squiggly +bracket/brace; l/r curly bracket/brace; <opening/closing +brace>. Rare: brace/unbrace; curly/uncurly; leftit/rytit; l/r +squirrelly; [embrace/bracelet].<br> +</dd> + +<dt><tt>|</tt></dt> + +<dd>Common: bar; or; or-bar; v-bar; pipe; vertical bar. Rare: +<vertical line>; gozinta; thru; pipesinta (last three from +UNIX); [spike].<br> +</dd> + +<dt><tt>~</tt></dt> + +<dd>Common: <tilde>; squiggle; <b><a href="#twiddle">twiddle</a></b>; not. Rare: approx; wiggle; swung +dash; enyay; [sqiggle (sic)].</dd> +</dl> + +<br> +<p>The pronunciation of <code>#</code> as `pound' is common in +the U.S. but a bad idea; <b><a href="#CommonwealthHackish">Commonwealth Hackish</a></b> has its +own, rather more apposite use of `pound sign' (confusingly, on +British keyboards the pound graphic happens to replace +<code>#</code>; thus Britishers sometimes call <code>#</code> on +a U.S.-ASCII keyboard `pound', compounding the American error). +The U.S. usage derives from an old-fashioned commercial practice +of using a <code>#</code> suffix to tag pound weights on bills of +lading. The character is usually pronounced `hash' outside the +U.S. There are more culture wars over the correct pronunciation +of this character than any other, which has led to the <b><a +href="#hahaonlyserious">ha ha only serious</a></b> +suggestion that it be pronounced `shibboleth' (see Judges 12:6 in +an Old Testament or Tanakh).</p> + +<p>The `uparrow' name for circumflex and `leftarrow' name for +underline are historical relics from archaic ASCII (the 1963 +version), which had these graphics in those character positions +rather than the modern punctuation characters.</p> + +<p>The `swung dash' or `approximation' sign is not quite the same +as tilde in typeset material but the ASCII tilde serves for both +(compare <b><a href="#anglebrackets">angle +brackets</a></b>).</p> + +<p>Some other common usages cause odd overlaps. The +<code>#</code>, <code>$</code>, <code>></code>, and +<code>&</code> characters, for example, are all pronounced +"hex" in different communities because various assemblers use +them as a prefix tag for hexadecimal constants (in particular, +<code>#</code> in many assembler-programming cultures, +<code>$</code> in the 6502 world, <code>></code> at Texas +Instruments, and <code>&</code> on the BBC Micro, Sinclair, +and some Z80 machines). See also <b><a href="#splat">splat</a></b>.</p> + +<p>The inability of ASCII text to correctly represent any of the +world's other major languages makes the designers' choice of 7 +bits look more and more like a serious <b><a href="#misfeature">misfeature</a></b> as the use of international +networks continues to increase (see <b><a href="#softwarerot">software rot</a></b>). Hardware and software +from the U.S. still tends to embody the assumption that ASCII is +the universal character set and that characters have 7 bits; this +is a major irritant to people who want to use a character set +suited to their own languages. Perversely, though, efforts to +solve this problem by proliferating `national' character sets +produce an evolutionary pressure to use a <i>smaller</i> subset +common to all those in use.</p> + +<hr> +Node:<a name="ASCIIart">ASCII art</a>, Next:<a rel="next" +href="#ASCIIbeticalorder">ASCIIbetical order</a>, Previous:<a +rel="previous" href="#ASCII">ASCII</a>, Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>ASCII art</b> n.</p> + +<p>The fine art of drawing diagrams using the ASCII character set +(mainly <code>|</code>, <code>-</code>, <code>/</code>, +<code>\</code>, and <code>+</code>). Also known as `character +graphics' or `ASCII graphics'; see also <b><a href="#boxology">boxology</a></b>. Here is a serious example:</p> + +<pre> + o----)||(--+--|<----+ +---------o + D O + L )||( | | | C U + A I )||( +-->|-+ | +-\/\/-+--o - T + C N )||( | | | | P + E )||( +-->|-+--)---+--|(--+-o U + )||( | | | GND T + o----)||(--+--|<----+----------+ + + A power supply consisting of a full wave rectifier circuit + feeding a capacitor input filter circuit +</pre> + +<p>And here are some very silly examples:</p> + +<pre> + |\/\/\/| ____/| ___ |\_/| ___ + | | \ o.O| ACK! / \_ |` '| _/ \ + | | =(_)= THPHTH! / \/ \/ \ + | (o)(o) U / \ + C _) (__) \/\/\/\ _____ /\/\/\/ + | ,___| (oo) \/ \/ + | / \/-------\ U (__) + /____\ || | \ /---V `v'- oo ) +/ \ ||---W|| * * |--| || |`. |_/\ + + //-o-\\ + ____---=======---____ + ====___\ /.. ..\ /___==== Klingons rule OK! + // ---\__O__/--- \\ + \_\ /_/ +</pre> + +<p>There is an important subgenre of ASCII art that puns on the +standard character names in the fashion of a rebus.</p> + +<pre> ++--------------------------------------------------------+ +| ^^^^^^^^^^^^ | +| ^^^^^^^^^^^ ^^^^^^^^^ | +| ^^^^^^^^^^^^^ ^^^^^^^^^^^^^ | +| ^^^^^^^ B ^^^^^^^^^ | +| ^^^^^^^^^ ^^^ ^^^^^^^^^^^^^^ | ++--------------------------------------------------------+ + " A Bee in the Carrot Patch " +</pre> + +<p>Within humorous ASCII art, there is for some reason an entire +flourishing subgenre of pictures of silly cows. Four of these are +reproduced in the examples above, here are three more:</p> + +<pre> + (__) (__) (__) + (\/) ($$) (**) + /-------\/ /-------\/ /-------\/ + / | 666 || / |=====|| / | || +* ||----|| * ||----|| * ||----|| + ~~ ~~ ~~ ~~ ~~ ~~ +Satanic cow This cow is a Yuppie Cow in love +</pre> + +<p>Finally, here's a magnificent example of ASCII art depicting +an Edwardian train station in Dunedin, New Zealand:</p> + +<pre> + .-. + /___\ + |___| + |]_[| + / I \ + JL/ | \JL + .-. i () | () i .-. + |_| .^. /_\ LJ=======LJ /_\ .^. |_| +._/___\._./___\_._._._._.L_J_/.-. .-.\_L_J._._._._._/___\._./___\._._._ + ., |-,-| ., L_J |_| [I] |_| L_J ., |-,-| ., ., + JL |-O-| JL L_J%%%%%%%%%%%%%%%L_J JL |-O-| JL JL +IIIIII_HH_'-'-'_HH_IIIIII|_|=======H=======|_|IIIIII_HH_'-'-'_HH_IIIIII_HH_ +-------[]-------[]-------[_]----\.=I=./----[_]-------[]-------[]--------[]- + _/\_ ||\\_I_//|| _/\_ [_] []_/_L_J_\_[] [_] _/\_ ||\\_I_//|| _/\_ ||\ + |__| ||=/_|_\=|| |__|_|_| _L_L_J_J_ |_|_|__| ||=/_|_\=|| |__| ||- + |__| |||__|__||| |__[___]__--__===__--__[___]__| |||__|__||| |__| ||| +IIIIIII[_]IIIII[_]IIIIIL___J__II__|_|__II__L___JIIIII[_]IIIII[_]IIIIIIII[_] + \_I_/ [_]\_I_/[_] \_I_[_]\II/[]\_\I/_/[]\II/[_]\_I_/ [_]\_I_/[_] \_I_/ [_] +./ \.L_J/ \L_J./ L_JI I[]/ \[]I IL_J \.L_J/ \L_J./ \.L_J +| |L_J| |L_J| L_J| |[]| |[]| |L_J |L_J| |L_J| |L_J +|_____JL_JL___JL_JL____|-|| |[]| |[]| ||-|_____JL_JL___JL_JL_____JL_J +</pre> + +<p>There is a newsgroup, <i>alt.ascii-art</i>, devoted to this +genre; however, see also <b><a href="#warlording">warlording</a></b>.</p> + +<hr> +Node:<a name="ASCIIbeticalorder">ASCIIbetical order</a>, +Next:<a rel="next" href="#astroturfing">astroturfing</a>, +Previous:<a rel="previous" href="#ASCIIart">ASCII art</a>, +Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>ASCIIbetical order</b> /as'kee-be'-t*-kl or'dr/ adj.,n.</p> + +<p>Used to indicate that data is sorted in ASCII collated order +rather than alphabetical order. This lexicon is sorted in +something close to ASCIIbetical order, but with case ignored and +entries beginning with non-alphabetic characters moved to the +end. "At my video store, they used their computer to sort the +videos into ASCIIbetical order, so I couldn't find `"Crocodile" +Dundee' until I thought to look before `2001' and `48 HRS.'!"</p> + +<hr> +Node:<a name="astroturfing">astroturfing</a>, Next:<a rel="next" +href="#atomic">atomic</a>, Previous:<a rel="previous" href="#ASCIIbeticalorder">ASCIIbetical order</a>, Up:<a rel="up" +href="#chap01">= A =</a> <br> + + +<p><b>astroturfing</b> n.</p> + +<p>The use of paid shills to create the impression of a popular +movement, through means like letters to newspapers from +soi-disant `concerned citizens', paid opinion pieces, and the +formation of grass-roots lobbying groups that are actually funded +by a PR group (astroturf is fake grass; hence the term). This +term became common among hackers after it came to light in early +1998 that Microsoft had attempted to use such tactics to +forestall the U.S. Department of Justice's antitrust action +against the company.</p> + +<p>This backfired horribly, angering a number of state +attorneys-general enough to induce them to go public with plans +to join the Federal suit. It also set anybody defending Microsoft +on the net for the accusation "You're just astroturfing!".</p> + +<hr> +Node:<a name="atomic">atomic</a>, Next:<a rel="next" href="#attoparsec">attoparsec</a>, Previous:<a rel="previous" href="#astroturfing">astroturfing</a>, Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>atomic</b> adj.</p> + +<p>[from Gk. `atomos', indivisible] 1. Indivisible; cannot be +split up. For example, an instruction may be said to do several +things `atomically', i.e., all the things are done immediately, +and there is no chance of the instruction being half-completed or +of another being interspersed. Used esp. to convey that an +operation cannot be screwed up by interrupts. "This routine locks +the file and increments the file's semaphore atomically." 2. +[primarily techspeak] Guaranteed to complete successfully or not +at all, usu. refers to database transactions. If an error +prevents a partially-performed transaction from proceeding to +completion, it must be "backed out," as the database must not be +left in an inconsistent state.</p> + +<p>Computer usage, in either of the above senses, has none of the +connotations that `atomic' has in mainstream English (i.e. of +particles of matter, nuclear explosions etc.).</p> + +<hr> +Node:<a name="attoparsec">attoparsec</a>, Next:<a rel="next" +href="#AUP">AUP</a>, Previous:<a rel="previous" href="#atomic">atomic</a>, Up:<a rel="up" href="#chap01">= A +=</a> <br> + + +<p><b>attoparsec</b> n.</p> + +<p>About an inch. `atto-' is the standard SI prefix for +multiplication by 10^(-18). A parsec (parallax-second) is 3.26 +light-years; an attoparsec is thus 3.26 * 10^(-18) light years, +or about 3.1 cm (thus, 1 attoparsec/<b><a href="#microfortnight">microfortnight</a></b> equals about 1 +inch/sec). This unit is reported to be in use (though probably +not very seriously) among hackers in the U.K. See <b><a href="#micro-">micro-</a></b>.</p> + +<hr> +Node:<a name="AUP">AUP</a>, Next:<a rel="next" href="#autobogotiphobia">autobogotiphobia</a>, Previous:<a rel="previous" href="#attoparsec">attoparsec</a>, Up:<a rel="up" +href="#chap01">= A =</a> <br> + + +<p><b>AUP</b> /A-U-P/</p> + +<p>Abbreviation, "Acceptable Use Policy". The policy of a given +ISP which sets out what the ISP considers to be (un)acceptable +uses of its Internet resources.</p> + +<hr> +Node:<a name="autobogotiphobia">autobogotiphobia</a>, Next:<a +rel="next" href="#automagically">automagically</a>, Previous:<a +rel="previous" href="#AUP">AUP</a>, Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>autobogotiphobia</b> /aw'toh-boh-got`*-foh'bee-*/</p> + +<p>n. See <b><a href="#bogotify">bogotify</a></b>.</p> + +<hr> +Node:<a name="automagically">automagically</a>, Next:<a rel="next" href="#avatar">avatar</a>, Previous:<a rel="previous" +href="#autobogotiphobia">autobogotiphobia</a>, Up:<a rel="up" +href="#chap01">= A =</a> <br> + + +<p><b>automagically</b> /aw-toh-maj'i-klee/ adv.</p> + +<p>Automatically, but in a way that, for some reason (typically +because it is too complicated, or too ugly, or perhaps even too +trivial), the speaker doesn't feel like explaining to you. See +<b><a href="#magic">magic</a></b>. "The C-INTERCAL compiler +generates C, then automagically invokes <code>cc(1)</code> to +produce an executable."</p> + +<p>This term is quite old, going back at least to the mid-70s in +jargon and probably much earlier. The word `automagic' occurred +in advertising (for a shirt-ironing gadget) as far back as the +late 1940s.</p> + +<hr> +Node:<a name="avatar">avatar</a>, Next:<a rel="next" href="#awk">awk</a>, Previous:<a rel="previous" href="#automagically">automagically</a>, Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>avatar</b> n. Syn.</p> + +<p>[in Hindu mythology, the incarnation of a god] 1. Among people +working on virtual reality and <b><a href="#cyberspace">cyberspace</a></b> interfaces, an <dfn>avatar</dfn> +is an icon or representation of a user in a shared virtual +reality. The term is sometimes used on <b><a href="#MUD">MUD</a></b>s. 2. [CMU, Tektronix] <b><a href="#root">root</a></b>, <b><a href="#superuser">superuser</a></b>. +There are quite a few Unix machines on which the name of the +superuser account is `avatar' rather than `root'. This quirk was +originated by a CMU hacker who found the terms `root' and +`superuser' unimaginative, and thought `avatar' might better +impress people with the responsibility they were accepting.</p> + +<hr> +Node:<a name="awk">awk</a>, Next:<a rel="next" href="#B5">B5</a>, +Previous:<a rel="previous" href="#avatar">avatar</a>, Up:<a rel="up" href="#chap01">= A =</a> <br> + + +<p><b>awk</b> /awk/</p> + +<p>1. n. [Unix techspeak] An interpreted language for massaging +text data developed by Alfred Aho, Peter Weinberger, and Brian +Kernighan (the name derives from their initials). It is +characterized by C-like syntax, a declaration-free approach to +variable typing and declarations, associative arrays, and +field-oriented text processing. See also <b><a href="#Perl">Perl</a></b>. 2. n. Editing term for an expression +awkward to manipulate through normal <b><a href="#regexp">regexp</a></b> facilities (for example, one containing +a <b><a href="#newline">newline</a></b>). 3. vt. To process data +using <code>awk(1)</code>.</p> + +<hr> +Node:<a name="chap02">= B =</a>, Next:<a rel="next" href="#chap03">= C =</a>, Previous:<a rel="previous" href="#chap01">= A =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= B =</h2> + +<ul> +<li><a href="#B5">B5</a>:</li> + +<li><a href="#backdoor">back door</a>:</li> + +<li><a href="#backbonecabal">backbone cabal</a>:</li> + +<li><a href="#backbonesite">backbone site</a>:</li> + +<li><a href="#backgammon">backgammon</a>:</li> + +<li><a href="#background">background</a>:</li> + +<li><a href="#backreference">backreference</a>:</li> + +<li><a href="#backronym">backronym</a>:</li> + +<li><a href="#backspaceandoverstrike">backspace and +overstrike</a>:</li> + +<li><a href="#backwardcombatability">backward +combatability</a>:</li> + +<li><a href="#BAD">BAD</a>:</li> + +<li><a href="#BadandWrong">Bad and Wrong</a>:</li> + +<li><a href="#BadThing">Bad Thing</a>:</li> + +<li><a href="#bagontheside">bag on the side</a>:</li> + +<li><a href="#bagbiter">bagbiter</a>:</li> + +<li><a href="#bagbiting">bagbiting</a>:</li> + +<li><a href="#baggypantsing">baggy pantsing</a>:</li> + +<li><a href="#balloonianvariable">balloonian +variable</a>:</li> + +<li><a href="#bamf">bamf</a>:</li> + +<li><a href="#bananalabel">banana label</a>:</li> + +<li><a href="#bananaproblem">banana problem</a>:</li> + +<li><a href="#bannerad">banner ad</a>:</li> + +<li><a href="#bannersite">banner site</a>:</li> + +<li><a href="#barn">barn</a>:</li> + +<li><a href="#batbelt">batbelt</a>:</li> + +<li><a href="#Befunge">Befunge</a>:</li> + +<li><a href="#BI">BI</a>:</li> + +<li><a href="#binaryfour">binary four</a>:</li> + +<li><a href="#bandwidth">bandwidth</a>:</li> + +<li><a href="#bang">bang</a>:</li> + +<li><a href="#bangon">bang on</a>:</li> + +<li><a href="#bangpath">bang path</a>:</li> + +<li><a href="#banner">banner</a>:</li> + +<li><a href="#bar">bar</a>:</li> + +<li><a href="#baremetal">bare metal</a>:</li> + +<li><a href="#barf">barf</a>:</li> + +<li><a href="#barfmail">barfmail</a>:</li> + +<li><a href="#barfulation">barfulation</a>:</li> + +<li><a href="#barfulous">barfulous</a>:</li> + +<li><a href="#barney">barney</a>:</li> + +<li><a href="#baroque">baroque</a>:</li> + +<li><a href="#BASIC">BASIC</a>:</li> + +<li><a href="#batch">batch</a>:</li> + +<li><a href="#bathtubcurve">bathtub curve</a>:</li> + +<li><a href="#baud">baud</a>:</li> + +<li><a href="#baudbarf">baud barf</a>:</li> + +<li><a href="#baz">baz</a>:</li> + +<li><a href="#bazaar">bazaar</a>:</li> + +<li><a href="#bboard">bboard</a>:</li> + +<li><a href="#BBS">BBS</a>:</li> + +<li><a href="#BCPL">BCPL</a>:</li> + +<li><a href="#beam">beam</a>:</li> + +<li><a href="#beaniekey">beanie key</a>:</li> + +<li><a href="#beep">beep</a>:</li> + +<li><a href="#beigetoaster">beige toaster</a>:</li> + +<li><a href="#bellsandwhistles">bells and +whistles</a>:</li> + +<li><a href="#bellswhistlesandgongs">bells whistles and +gongs</a>:</li> + +<li><a href="#benchmark">benchmark</a>:</li> + +<li><a href="#BerkeleyQualitySoftware">Berkeley Quality +Software</a>:</li> + +<li><a href="#berklix">berklix</a>:</li> + +<li><a href="#Berzerkeley">Berzerkeley</a>:</li> + +<li><a href="#beta">beta</a>:</li> + +<li><a href="#BFI">BFI</a>:</li> + +<li><a href="#bible">bible</a>:</li> + +<li><a href="#BiCapitalization">BiCapitalization</a>:</li> + +<li><a href="#B1FF">B1FF</a>:</li> + +<li><a href="#biff">biff</a>:</li> + +<li><a href="#BigGrayWall">Big Gray Wall</a>:</li> + +<li><a href="#bigiron">big iron</a>:</li> + +<li><a href="#BigRedSwitch">Big Red Switch</a>:</li> + +<li><a href="#BigRoom">Big Room</a>:</li> + +<li><a href="#bigwin">big win</a>:</li> + +<li><a href="#big-endian">big-endian</a>:</li> + +<li><a href="#bignum">bignum</a>:</li> + +<li><a href="#bigot">bigot</a>:</li> + +<li><a href="#bit">bit</a>:</li> + +<li><a href="#bitbang">bit bang</a>:</li> + +<li><a href="#bitbashing">bit bashing</a>:</li> + +<li><a href="#bitbucket">bit bucket</a>:</li> + +<li><a href="#bitdecay">bit decay</a>:</li> + +<li><a href="#bitrot">bit rot</a>:</li> + +<li><a href="#bittwiddling">bit twiddling</a>:</li> + +<li><a href="#bit-pairedkeyboard">bit-paired +keyboard</a>:</li> + +<li><a href="#bitblt">bitblt</a>:</li> + +<li><a href="#BITNET">BITNET</a>:</li> + +<li><a href="#bits">bits</a>:</li> + +<li><a href="#bittybox">bitty box</a>:</li> + +<li><a href="#bixen">bixen</a>:</li> + +<li><a href="#bixie">bixie</a>:</li> + +<li><a href="#blackart">black art</a>:</li> + +<li><a href="#blackHole">black hole</a>:</li> + +<li><a href="#blackmagic">black magic</a>:</li> + +<li><a href="#BlackScreenofDeath">Black Screen of Death</a>:</li> + +<li><a href="#BlackThursday">Black Thursday</a>:</li> + +<li><a href="#blammo">blammo</a>:</li> + +<li><a href="#blargh">blargh</a>:</li> + +<li><a href="#blast">blast</a>:</li> + +<li><a href="#blat">blat</a>:</li> + +<li><a href="#bletch">bletch</a>:</li> + +<li><a href="#bletcherous">bletcherous</a>:</li> + +<li><a href="#blink">blink</a>:</li> + +<li><a href="#blinkenlights">blinkenlights</a>:</li> + +<li><a href="#blit">blit</a>:</li> + +<li><a href="#blitter">blitter</a>:</li> + +<li><a href="#blivet">blivet</a>:</li> + +<li><a href="#bloatware">bloatware</a>:</li> + +<li><a href="#BLOB">BLOB</a>:</li> + +<li><a href="#block">block</a>:</li> + +<li><a href="#blocktransfercomputations">block transfer +computations</a>:</li> + +<li><a href="#BloggsFamily">Bloggs Family</a>:</li> + +<li><a href="#blowanEPROM">blow an EPROM</a>:</li> + +<li><a href="#blowaway">blow away</a>:</li> + +<li><a href="#blowout">blow out</a>:</li> + +<li><a href="#blowpast">blow past</a>:</li> + +<li><a href="#blowup">blow up</a>:</li> + +<li><a href="#BLT">BLT</a>:</li> + +<li><a href="#BlueBook">Blue Book</a>:</li> + +<li><a href="#bluebox">blue box</a>:</li> + +<li><a href="#BlueGlue">Blue Glue</a>:</li> + +<li><a href="#bluegoo">blue goo</a>:</li> + +<li><a href="#BlueScreenofDeath">Blue Screen of +Death</a>:</li> + +<li><a href="#bluewire">blue wire</a>:</li> + +<li><a href="#blurgle">blurgle</a>:</li> + +<li><a href="#BNF">BNF</a>:</li> + +<li><a href="#boa">boa</a>:</li> + +<li><a href="#board">board</a>:</li> + +<li><a href="#boatanchor">boat anchor</a>:</li> + +<li><a href="#bob">bob</a>:</li> + +<li><a href="#bodysurfcode">bodysurf code</a>:</li> + +<li><a href="#BOF">BOF</a>:</li> + +<li><a href="#BOFH">BOFH</a>:</li> + +<li><a href="#bogo-sort">bogo-sort</a>:</li> + +<li><a href="#bogometer">bogometer</a>:</li> + +<li><a href="#BogoMIPS">BogoMIPS</a>:</li> + +<li><a href="#bogon">bogon</a>:</li> + +<li><a href="#bogonfilter">bogon filter</a>:</li> + +<li><a href="#bogonflux">bogon flux</a>:</li> + +<li><a href="#bogosity">bogosity</a>:</li> + +<li><a href="#bogotify">bogotify</a>:</li> + +<li><a href="#bogueout">bogue out</a>:</li> + +<li><a href="#bogus">bogus</a>:</li> + +<li><a href="#Bohrbug">Bohr bug</a>:</li> + +<li><a href="#boink">boink</a>:</li> + +<li><a href="#bomb">bomb</a>:</li> + +<li><a href="#bondage-and-disciplinelanguage">bondage-and-discipline language</a>:</li> + +<li><a href="#bonkfoif">bonk/oif</a>:</li> + +<li><a href="#booktitles">book titles</a>:</li> + +<li><a href="#boot">boot</a>:</li> + +<li><a href="#Borg">Borg</a>:</li> + +<li><a href="#borken">borken</a>:</li> + +<li><a href="#bot">bot</a>:</li> + +<li><a href="#botspot">bot spot</a>:</li> + +<li><a href="#bottomfeeder">bottom feeder</a>:</li> + +<li><a href="#bottom-upimplementation">bottom-up +implementation</a>:</li> + +<li><a href="#bounce">bounce</a>:</li> + +<li><a href="#bouncemessage">bounce message</a>:</li> + +<li><a href="#boustrophedon">boustrophedon</a>:</li> + +<li><a href="#box">box</a>:</li> + +<li><a href="#boxedcomments">boxed comments</a>:</li> + +<li><a href="#boxen">boxen</a>:</li> + +<li><a href="#boxology">boxology</a>:</li> + +<li><a href="#bozotic">bozotic</a>:</li> + +<li><a href="#BQS">BQS</a>:</li> + +<li><a href="#braindump">brain dump</a>:</li> + +<li><a href="#brainfart">brain fart</a>:</li> + +<li><a href="#brain-damaged">brain-damaged</a>:</li> + +<li><a href="#brain-dead">brain-dead</a>:</li> + +<li><a href="#braino">braino</a>:</li> + +<li><a href="#branchtoFishkill">branch to +Fishkill</a>:</li> + +<li><a href="#breadcrumbs">bread crumbs</a>:</li> + +<li><a href="#break">break</a>:</li> + +<li><a href="#break-evenpoint">break-even point</a>:</li> + +<li><a href="#breath-of-lifepacket">breath-of-life +packet</a>:</li> + +<li><a href="#breedle">breedle</a>:</li> + +<li><a href="#BreidbartIndex">Breidbart Index</a>:</li> + +<li><a href="#bringXtoitsknees">bring X to its +knees</a>:</li> + +<li><a href="#brittle">brittle</a>:</li> + +<li><a href="#broadcaststorm">broadcast storm</a>:</li> + +<li><a href="#brochureware">brochureware</a>:</li> + +<li><a href="#broken">broken</a>:</li> + +<li><a href="#brokenarrow">broken arrow</a>:</li> + +<li><a href="#BrokenWindows">BrokenWindows</a>:</li> + +<li><a href="#broket">broket</a>:</li> + +<li><a href="#BrookssLaw">Brooks's Law</a>:</li> + +<li><a href="#brown-paper-bagbug">brown-paper-bag +bug</a>:</li> + +<li><a href="#browser">browser</a>:</li> + +<li><a href="#BRS">BRS</a>:</li> + +<li><a href="#bruteforce">brute force</a>:</li> + +<li><a href="#bruteforceandignorance">brute force and +ignorance</a>:</li> + +<li><a href="#BSD">BSD</a>:</li> + +<li><a href="#BSOD">BSOD</a>:</li> + +<li><a href="#BUAF">BUAF</a>:</li> + +<li><a href="#BUAG">BUAG</a>:</li> + +<li><a href="#bubblesort">bubble sort</a>:</li> + +<li><a href="#buckybits">bucky bits</a>:</li> + +<li><a href="#bufferchuck">buffer chuck</a>:</li> + +<li><a href="#bufferoverflow">buffer overflow</a>:</li> + +<li><a href="#bug">bug</a>:</li> + +<li><a href="#bug-compatible">bug-compatible</a>:</li> + +<li><a href="#bug-for-bugcompatible">bug-for-bug +compatible</a>:</li> + +<li><a href="#bug-of-the-monthclub">bug-of-the-month +club</a>:</li> + +<li><a href="#buglix">buglix</a>:</li> + +<li><a href="#bulletproof">bulletproof</a>:</li> + +<li><a href="#bullschildt">bullschildt</a>:</li> + +<li><a href="#bum">bum</a>:</li> + +<li><a href="#bump">bump</a>:</li> + +<li><a href="#burble">burble</a>:</li> + +<li><a href="#buriedtreasure">buried treasure</a>:</li> + +<li><a href="#burn-inperiod">burn-in period</a>:</li> + +<li><a href="#burstpage">burst page</a>:</li> + +<li><a href="#busy-wait">busy-wait</a>:</li> + +<li><a href="#buzz">buzz</a>:</li> + +<li><a href="#BWQ">BWQ</a>:</li> + +<li><a href="#byhand">by hand</a>:</li> + +<li><a href="#byte">byte</a>:</li> + +<li><a href="#byteSex">byte sex</a>:</li> + +<li><a href="#bytesexual">bytesexual</a>:</li> + +<li><a href="#BzzztWrong.">Bzzzt! Wrong.</a>:</li> +</ul> + +<hr> +Node:<a name="B5">B5</a>, Next:<a rel="next" href="#backdoor">back door</a>, Previous:<a rel="previous" href="#awk">awk</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>B5</b> //</p> + +<p>[common] Abbreviation for "Babylon 5", a science-fiction TV +series as revered among hackers as was the original Star +Trek.</p> + +<hr> +Node:<a name="backdoor">back door</a>, Next:<a rel="next" +href="#backbonecabal">backbone cabal</a>, Previous:<a rel="previous" href="#B5">B5</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>back door</b> n.</p> + +<p>[common] A hole in the security of a system deliberately left +in place by designers or maintainers. The motivation for such +holes is not always sinister; some operating systems, for +example, come out of the box with privileged accounts intended +for use by field service technicians or the vendor's maintenance +programmers. Syn. <b><a href="#trapDoor">trap door</a></b>; +may also be called a `wormhole'. See also <b><a href="#ironbox">iron box</a></b>, <b><a href="#cracker">cracker</a></b>, <b><a href="#worm">worm</a></b>, +<b><a href="#logicbomb">logic bomb</a></b>.</p> + +<p>Historically, back doors have often lurked in systems longer +than anyone expected or planned, and a few have become widely +known. Ken Thompson's 1983 Turing Award lecture to the ACM +admitted the existence of a back door in early Unix versions that +may have qualified as the most fiendishly clever security hack of +all time. In this scheme, the C compiler contained code that +would recognize when the `login' command was being recompiled and +insert some code recognizing a password chosen by Thompson, +giving him entry to the system whether or not an account had been +created for him.</p> + +<p>Normally such a back door could be removed by removing it from +the source code for the compiler and recompiling the compiler. +But to recompile the compiler, you have to <i>use</i> the +compiler -- so Thompson also arranged that the compiler would +<i>recognize when it was compiling a version of itself</i>, and +insert into the recompiled compiler the code to insert into the +recompiled `login' the code to allow Thompson entry -- and, of +course, the code to recognize itself and do the whole thing again +the next time around! And having done this once, he was then able +to recompile the compiler from the original sources; the hack +perpetuated itself invisibly, leaving the back door in place and +active but with no trace in the sources.</p> + +<p>The talk that suggested this truly moby hack was published as +"Reflections on Trusting Trust", "Communications of the ACM 27", +8 (August 1984), pp. 761-763 (text available at http://www.acm.org/classics). +Ken Thompson has since confirmed that this hack was implemented +and that the Trojan Horse code did appear in the login binary of +a Unix Support group machine. Ken says the crocked compiler was +never distributed. Your editor has heard two separate reports +that suggest that the crocked login did make it out of Bell Labs, +notably to BBN, and that it enabled at least one late-night login +across the network by someone using the login name `kt'.</p> + +<hr> +Node:<a name="backbonecabal">backbone cabal</a>, Next:<a rel="next" href="#backbonesite">backbone site</a>, Previous:<a +rel="previous" href="#backdoor">back door</a>, Up:<a rel="up" +href="#chap02">= B =</a> <br> + + +<p><b>backbone cabal</b> n.</p> + +<p>A group of large-site administrators who pushed through the +<b><a href="#GreatRenaming">Great Renaming</a></b> and reined +in the chaos of <b><a href="#Usenet">Usenet</a></b> during most +of the 1980s. During most of its lifetime, the Cabal (as it was +sometimes capitalized) steadfastly denied its own existence; it +was almost obligatory for anyone privy to their secrets to +respond "There is no Cabal" whenever the existence or activities +of the group were speculated on in public.</p> + +<p>The result of this policy was an attractive aura of mystery. +Even a decade after the cabal <b><a href="#mailinglist">mailing list</a></b> disbanded in late 1988 +following a bitter internal catfight, many people believed (or +claimed to believe) that it had not actually disbanded but only +gone deeper underground with its power intact.</p> + +<p>This belief became a model for various paranoid theories about +various Cabals with dark nefarious objectives beginning with +taking over the Usenet or Internet. These paranoias were later +satirized in ways that took on a life of their own. See <b><a +href="#EricConspiracy">Eric Conspiracy</a></b> for one +example.</p> + +<p>See <b><a href="#NANA">NANA</a></b> for the subsequent history +of "the Cabal".</p> + +<hr> +Node:<a name="backbonesite">backbone site</a>, Next:<a rel="next" href="#backgammon">backgammon</a>, Previous:<a rel="previous" href="#backbonecabal">backbone cabal</a>, Up:<a +rel="up" href="#chap02">= B =</a> <br> + + +<p><b>backbone site</b> n.,obs.</p> + +<p>Formerly, a key Usenet and email site, one that processes a +large amount of third-party traffic, especially if it is the home +site of any of the regional coordinators for the Usenet maps. +Notable backbone sites as of early 1993, when this sense of the +term was beginning to pass out of general use due to wide +availability of cheap Internet connections, included <i>uunet</i> +and the mail machines at Rutgers University, UC Berkeley, <b><a +href="#DEC">DEC</a></b>'s Western Research Laboratories, Ohio +State University, and the University of Texas. Compare <b><a +href="#ribsite">rib site</a></b>, <b><a href="#leafsite">leaf site</a></b>.</p> + +<p>[1996 update: This term is seldom heard any more. The UUCP +network world that gave it meaning has nearly disappeared; +everyone is on the Internet now and network traffic is +distributed in very different patterns. Today one might see +references to a `backbone router' instead --ESR]</p> + +<hr> +Node:<a name="backgammon">backgammon</a>, Next:<a rel="next" +href="#background">background</a>, Previous:<a rel="previous" +href="#backbonesite">backbone site</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>backgammon</b></p> + +<p>See <b><a href="#bignum">bignum</a></b> (sense 3), <b><a href="#moby">moby</a></b> (sense 4), and <b><a href="#pseudoprime">pseudoprime</a></b>.</p> + +<hr> +Node:<a name="background">background</a>, Next:<a rel="next" +href="#backreference">backreference</a>, Previous:<a rel="previous" href="#backgammon">backgammon</a>, Up:<a rel="up" +href="#chap02">= B =</a> <br> + + +<p><b>background</b> n.,adj.,vt.</p> + +<p>[common] To do a task `in background' is to do it whenever +<b><a href="#foreground">foreground</a></b> matters are not +claiming your undivided attention, and `to background' something +means to relegate it to a lower priority. "For now, we'll just +print a list of nodes and links; I'm working on the +graph-printing problem in background." Note that this implies +ongoing activity but at a reduced level or in spare time, in +contrast to mainstream `back burner' (which connotes benign +neglect until some future resumption of activity). Some people +prefer to use the term for processing that they have queued up +for their unconscious minds (a tack that one can often fruitfully +take upon encountering an obstacle in creative work). Compare +<b><a href="#ampoff">amp off</a></b>, <b><a href="#slopsucker">slopsucker</a></b>.</p> + +<p>Technically, a task running in background is detached from the +terminal where it was started (and often running at a lower +priority); oppose <b><a href="#foreground">foreground</a></b>. +Nowadays this term is primarily associated with <b><a href="#Unix">Unix</a></b>, but it appears to have been first used in +this sense on OS/360.</p> + +<hr> +Node:<a name="backreference">backreference</a>, Next:<a rel="next" href="#backronym">backronym</a>, Previous:<a rel="previous" href="#background">background</a>, Up:<a rel="up" +href="#chap02">= B =</a> <br> + + +<p><b>backreference</b> n.</p> + +<p>1. In a regular expression or pattern match, the text which +was matched within grouping parentheses parentheses. 2. The part +of the pattern which refers back to the matched text. 3. By +extension, anything which refers back to something which has been +seen or discussed before. "When you said `she' just now, who were +you backreferencing?"</p> + +<hr> +Node:<a name="backronym">backronym</a>, Next:<a rel="next" href="#backspaceandoverstrike">backspace and overstrike</a>, +Previous:<a rel="previous" href="#backreference">backreference</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>backronym</b> n.</p> + +<p>[portmanteau of back + acronym] A word interpreted as an +acronym that was not originally so intended. This is a special +case of what linguists call `back formation'. Examples are given +under <b><a href="#BASIC">BASIC</a></b>, <b><a href="#recursiveacronym">recursive acronym</a></b> (Cygnus), <b><a +href="#Acme">Acme</a></b>, and <b><a href="#mung">mung</a></b>. +Discovering backronyms is a common form of wordplay among +hackers. Compare <b><a href="#retcon">retcon</a></b>.</p> + +<hr> +Node:<a name="backspaceandoverstrike">backspace and +overstrike</a>, Next:<a rel="next" href="#backwardcombatability">backward combatability</a>, +Previous:<a rel="previous" href="#backronym">backronym</a>, Up:<a +rel="up" href="#chap02">= B =</a> <br> + + +<p><b>backspace and overstrike</b> interj.</p> + +<p>[rare] Whoa! Back up. Used to suggest that someone just said +or did something wrong. Once common among APL programmers; may +now be obsolete.</p> + +<hr> +Node:<a name="backwardcombatability">backward +combatability</a>, Next:<a rel="next" href="#BAD">BAD</a>, +Previous:<a rel="previous" href="#backspaceandoverstrike">backspace and overstrike</a>, +Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>backward combatability</b> /bak'w*rd k*m-bat'*-bil'*-tee/ +n.</p> + +<p>[CMU, Tektronix: from `backward compatibility'] A property of +hardware or software revisions in which previous protocols, +formats, layouts, etc. are irrevocably discarded in favor of `new +and improved' protocols, formats, and layouts, leaving the +previous ones not merely deprecated but actively defeated. (Too +often, the old and new versions cannot definitively be +distinguished, such that lingering instances of the previous ones +yield crashes or other infelicitous effects, as opposed to a +simple "version mismatch" message.) A backwards compatible +change, on the other hand, allows old versions to coexist without +crashes or error messages, but too many major changes +incorporating elaborate backwards compatibility processing can +lead to extreme <b><a href="#softwarebloat">software +bloat</a></b>. See also <b><a href="#flagday">flag +day</a></b>.</p> + +<hr> +Node:<a name="BAD">BAD</a>, Next:<a rel="next" href="#BadandWrong">Bad and Wrong</a>, Previous:<a rel="previous" href="#backwardcombatability">backward +combatability</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>BAD</b> /B-A-D/ adj.</p> + +<p>[IBM: acronym, `Broken As Designed'] Said of a program that is +<b><a href="#bogus">bogus</a></b> because of bad design and +misfeatures rather than because of bugginess. See <b><a href="#workingasdesigned">working as designed</a></b>.</p> + +<hr> +Node:<a name="BadandWrong">Bad and Wrong</a>, Next:<a rel="next" href="#BadThing">Bad Thing</a>, Previous:<a rel="previous" href="#BAD">BAD</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>Bad and Wrong</b> adj.</p> + +<p>[Durham, UK] Said of something that is both badly designed and +wrongly executed. This common term is the prototype of, and is +used by contrast with, three less common terms - Bad and Right (a +kludge, something ugly but functional); Good and Wrong (an +overblown GUI or other attractive nuisance); and (rare praise) +Good and Right. These terms entered common use at Durham c.1994 +and may have been imported from elsewhere; they are also in use +at Oxford, and the emphatic form "Evil, Bad and Wrong" +(abbreviated EBW) is reported fromm there. There are standard +abbreviations: they start with B&R, a typo for "Bad and +Wrong". Consequently, B&W is actually "Bad and Right", +G&R = "Good and Wrong", and G&W = "Good and Right". +Compare <b><a href="#evilandrude">evil and rude</a></b>, +<b><a href="#GoodThing">Good Thing</a></b>, <b><a href="#BadThing">Bad Thing</a></b>.</p> + +<hr> +Node:<a name="BadThing">Bad Thing</a>, Next:<a rel="next" +href="#bagontheside">bag on the side</a>, Previous:<a +rel="previous" href="#BadandWrong">Bad and Wrong</a>, Up:<a +rel="up" href="#chap02">= B =</a> <br> + + +<p><b>Bad Thing</b> n.</p> + +<p>[very common; from the 1930 Sellar & Yeatman parody "1066 +And All That"] Something that can't possibly result in +improvement of the subject. This term is always capitalized, as +in "Replacing all of the 9600-baud modems with bicycle couriers +would be a Bad Thing". Oppose <b><a href="#GoodThing">Good +Thing</a></b>. British correspondents confirm that <b><a href="#BadThing">Bad Thing</a></b> and <b><a href="#GoodThing">Good Thing</a></b> (and prob. therefore <b><a +href="#RightThing">Right Thing</a></b> and <b><a href="#WrongThing">Wrong Thing</a></b>) come from the book +referenced in the etymology, which discusses rulers who were Good +Kings but Bad Things. This has apparently created a mainstream +idiom on the British side of the pond. It is very common among +American hackers, but not in mainstream usage here. Compare <b><a +href="#BadandWrong">Bad and Wrong</a></b>.</p> + +<hr> +Node:<a name="bagontheside">bag on the side</a>, Next:<a +rel="next" href="#bagbiter">bagbiter</a>, Previous:<a rel="previous" href="#BadThing">Bad Thing</a>, Up:<a rel="up" +href="#chap02">= B =</a> <br> + + +<p><b>bag on the side</b> n.</p> + +<p>[prob. originally related to a colostomy bag] An extension to +an established hack that is supposed to add some functionality to +the original. Usually derogatory, implying that the original was +being overextended and should have been thrown away, and the new +product is ugly, inelegant, or bloated. Also v. phrase, `to hang +a bag on the side [of]'. "C++? That's just a bag on the side of C +<small>...</small>." "They want me to hang a bag on the side of +the accounting system."</p> + +<hr> +Node:<a name="bagbiter">bagbiter</a>, Next:<a rel="next" href="#bagbiting">bagbiting</a>, Previous:<a rel="previous" href="#bagontheside">bag on the side</a>, Up:<a rel="up" +href="#chap02">= B =</a> <br> + + +<p><b>bagbiter</b> /bag'bi:t-*r/ n.</p> + +<p>1. Something, such as a program or a computer, that fails to +work, or works in a remarkably clumsy manner. "This text editor +won't let me make a file with a line longer than 80 characters! +What a bagbiter!" 2. A person who has caused you some trouble, +inadvertently or otherwise, typically by failing to program the +computer properly. Synonyms: <b><a href="#loser">loser</a></b>, +<b><a href="#cretin">cretin</a></b>, <b><a href="#chomper">chomper</a></b>. 3. `bite the bag' vi. To fail in some +manner. "The computer keeps crashing every five minutes." "Yes, +the disk controller is really biting the bag."</p> + +<p>The original loading of these terms was almost undoubtedly +obscene, possibly referring to a douche bag or the scrotum (we +have reports of "Bite the douche bag!" being used as a taunt at +MIT 1970-1976, and we have another report that "Bite the bag!" +was in common use at least as early as 1965), but in their +current usage they have become almost completely sanitized.</p> + +<p>ITS's <b><a href="#lexiphage">lexiphage</a></b> program was +the first and to date only known example of a program +<i>intended</i> to be a bagbiter.</p> + +<hr> +Node:<a name="bagbiting">bagbiting</a>, Next:<a rel="next" href="#baggypantsing">baggy pantsing</a>, Previous:<a rel="previous" href="#bagbiter">bagbiter</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bagbiting</b> adj.</p> + +<p>Having the quality of a <b><a href="#bagbiter">bagbiter</a></b>. "This bagbiting system won't let me +compute the factorial of a negative number." Compare <b><a href="#losing">losing</a></b>, <b><a href="#cretinous">cretinous</a></b>, <b><a href="#bletcherous">bletcherous</a></b>, `barfucious' (under <b><a +href="#barfulous">barfulous</a></b>) and `chomping' (under <b><a +href="#chomp">chomp</a></b>).</p> + +<hr> +Node:<a name="baggypantsing">baggy pantsing</a>, Next:<a rel="next" href="#balloonianvariable">balloonian variable</a>, +Previous:<a rel="previous" href="#bagbiting">bagbiting</a>, Up:<a +rel="up" href="#chap02">= B =</a> <br> + + +<p><b>baggy pantsing</b> v.</p> + +<p>[Georgia Tech] A "baggy pantsing" is used to reprimand hackers +who incautiously leave their terminals unlocked. The affected +user will come back to find a post from them on internal +newsgroups discussing exactly how baggy their pants are, an +accepted stand-in for "unattentive user who left their work +unprotected in the clusters". A properly-done baggy pantsing is +highly mocking and humorous (see examples below). It is +considered bad form to post a baggy pantsing to off-campus +newsgroups or the more technical, serious groups. A particularly +nice baggy pantsing may be "claimed" by immediately quoting the +message in full, followed by your sig; this has the added benefit +of keeping the embarassed victim from being able to delete the +post. Interesting baggy-pantsings have been done involving adding +commands to login scripts to repost the message every time the +unlucky user logs in; Unix boxes on the residential network, when +cracked, oftentimes have their homepages replaced (after being +politely backedup to another file) with a baggy-pants message; +.plan files are also occasionally targeted. Usage: "Prof. +Greenlee fell asleep in the Solaris cluster again; we +baggy-pantsed him to git.cc.class.2430.flame."</p> + +<hr> +Node:<a name="balloonianvariable">balloonian variable</a>, +Next:<a rel="next" href="#bamf">bamf</a>, Previous:<a rel="previous" href="#baggypantsing">baggy pantsing</a>, Up:<a +rel="up" href="#chap02">= B =</a> <br> + + +<p><b>balloonian variable</b> n.</p> + +<p>[Commodore users; perh. a deliberate phonetic mangling of +`boolean variable'?] Any variable that doesn't actually hold or +control state, but must nevertheless be declared, checked, or +set. A typical balloonian variable started out as a flag attached +to some environment feature that either became obsolete or was +planned but never implemented. Compatibility concerns (or +politics attached to same) may require that such a flag be +treated as though it were <b><a href="#live">live</a></b>.</p> + +<hr> +Node:<a name="bamf">bamf</a>, Next:<a rel="next" href="#bananalabel">banana label</a>, Previous:<a rel="previous" +href="#balloonianvariable">balloonian variable</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bamf</b> /bamf/</p> + +<p>1. [from X-Men comics; originally "bampf"] interj. Notional +sound made by a person or object teleporting in or out of the +hearer's vicinity. Often used in <b><a href="#virtualreality">virtual reality</a></b> (esp. <b><a href="#MUD">MUD</a></b>) electronic <b><a href="#fora">fora</a></b> +when a character wishes to make a dramatic entrance or exit. 2. +The sound of magical transformation, used in virtual reality +<b><a href="#fora">fora</a></b> like MUDs. 3. In MUD circles, +"bamf" is also used to refer to the act by which a MUD server +sends a special notification to the MUD client to switch its +connection to another server ("I'll set up the old site to just +bamf people over to our new location."). 4. Used by MUDders on +occasion in a more general sense related to sense 3, to refer to +directing someone to another location or resource ("A user was +asking about some technobabble so I bamfed them to http://www.tuxedo.org/jargon/".)</p> + +<hr> +Node:<a name="bananalabel">banana label</a>, Next:<a rel="next" href="#bananaproblem">banana problem</a>, Previous:<a +rel="previous" href="#bamf">bamf</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>banana label</b> n.</p> + +<p>The labels often used on the sides of <b><a href="#macrotape">macrotape</a></b> reels, so called because they are +shaped roughly like blunt-ended bananas. This term, like +macrotapes themselves, is still current but visibly headed for +obsolescence.</p> + +<hr> +Node:<a name="bananaproblem">banana problem</a>, Next:<a rel="next" href="#binaryfour">binary four</a>, Previous:<a rel="previous" href="#bananalabel">banana label</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>banana problem</b> n.</p> + +<p>[from the story of the little girl who said "I know how to +spell `banana', but I don't know when to stop"]. Not knowing +where or when to bring a production to a close (compare <b><a +href="#fenceposterror">fencepost error</a></b>). One may say +`there is a banana problem' of an algorithm with poorly defined +or incorrect termination conditions, or in discussing the +evolution of a design that may be succumbing to featuritis (see +also <b><a href="#creepingelegance">creeping elegance</a></b>, +<b><a href="#creepingfeaturitis">creeping featuritis</a></b>). +See item 176 under <b><a href="#HAKMEM">HAKMEM</a></b>, which +describes a banana problem in a <b><a href="#DissociatedPress">Dissociated Press</a></b> implementation. +Also, see <b><a href="#one-bananaproblem">one-banana +problem</a></b> for a superficially similar but unrelated +usage.</p> + +<hr> +Node:<a name="binaryfour">binary four</a>, Next:<a rel="next" +href="#bandwidth">bandwidth</a>, Previous:<a rel="previous" href="#bananaproblem">banana problem</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>binary four</b> n.</p> + +<p>[Usenet] The finger, in the sense of `digitus impudicus'. This +comes from an analogy between binary and the hand, i.e. +1=00001=thumb, 2=00010=index finger, 3=00011=index and thumb, +4=00100. Considered silly. Prob. from humorous derivative of +<b><a href="#finger">finger</a></b>, sense 4.</p> + +<hr> +Node:<a name="bandwidth">bandwidth</a>, Next:<a rel="next" href="#bang">bang</a>, Previous:<a rel="previous" href="#binaryfour">binary four</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bandwidth</b> n.</p> + +<p>1. [common] Used by hackers (in a generalization of its +technical meaning) as the volume of information per unit time +that a computer, person, or transmission medium can handle. +"Those are amazing graphics, but I missed some of the detail -- +not enough bandwidth, I guess." Compare <b><a href="#low-bandwidth">low-bandwidth</a></b>. This generalized usage +began to go mainstream after the Internet population explosion of +1993-1994. 2. Attention span. 3. On <b><a href="#Usenet">Usenet</a></b>, a measure of network capacity that is +often wasted by people complaining about how items posted by +others are a waste of bandwidth.</p> + +<hr> +Node:<a name="bang">bang</a>, Next:<a rel="next" href="#bangon">bang on</a>, Previous:<a rel="previous" href="#bandwidth">bandwidth</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bang</b></p> + +<p>1. n. Common spoken name for <code>!</code> (ASCII 0100001), +especially when used in pronouncing a <b><a href="#bangpath">bang path</a></b> in spoken hackish. In <b><a +href="#elderdays">elder days</a></b> this was considered a +CMUish usage, with MIT and Stanford hackers preferring <b><a +href="#excl">excl</a></b> or <b><a href="#shriek">shriek</a></b>; +but the spread of Unix has carried `bang' with it (esp. via the +term <b><a href="#bangpath">bang path</a></b>) and it is now +certainly the most common spoken name for <code>!</code>. Note +that it is used exclusively for non-emphatic written +<code>!</code>; one would not say "Congratulations bang" (except +possibly for humorous purposes), but if one wanted to specify the +exact characters `foo!' one would speak "Eff oh oh bang". See +<b><a href="#shriek">shriek</a></b>, <b><a href="#ASCII">ASCII</a></b>. 2. interj. An exclamation signifying +roughly "I have achieved enlightenment!", or "The dynamite has +cleared out my brain!" Often used to acknowledge that one has +perpetrated a <b><a href="#thinko">thinko</a></b> immediately +after one has been called on it.</p> + +<hr> +Node:<a name="bangon">bang on</a>, Next:<a rel="next" href="#bangpath">bang path</a>, Previous:<a rel="previous" href="#bang">bang</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>bang on</b> vt.</p> + +<p>To stress-test a piece of hardware or software: "I banged on +the new version of the simulator all day yesterday and it didn't +crash once. I guess it is ready for release." The term <b><a +href="#poundon">pound on</a></b> is synonymous.</p> + +<hr> +Node:<a name="bangpath">bang path</a>, Next:<a rel="next" +href="#banner">banner</a>, Previous:<a rel="previous" href="#bangon">bang on</a>, Up:<a rel="up" href="#chap02">= +B =</a> <br> + + +<p><b>bang path</b> n.</p> + +<p>[now historical] An old-style UUCP electronic-mail address +specifying hops to get from some assumed-reachable location to +the addressee, so called because each <b><a href="#hop">hop</a></b> is signified by a <b><a href="#bang">bang</a></b> sign. Thus, for example, the path +<i>...!bigsite!foovax!barbox!me</i> directs people to route their +mail to machine <i>bigsite</i> (presumably a well-known location +accessible to everybody) and from there through the machine +<i>foovax</i> to the account of user <i>me</i> on +<i>barbox</i>.</p> + +<p>In the bad old days of not so long ago, before autorouting +mailers became commonplace, people often published compound bang +addresses using the { } convention (see <b><a href="#glob">glob</a></b>) to give paths from <i>several</i> big +machines, in the hopes that one's correspondent might be able to +get mail to one of them reliably (example: <i>...!{seismo, +ut-sally, ihnp4}!rice!beta!gamma!me</i>). Bang paths of 8 to 10 +hops were not uncommon in 1981. Late-night dial-up UUCP links +would cause week-long transmission times. Bang paths were often +selected by both transmission time and reliability, as messages +would often get lost. See <b><a href="#Internetaddress">Internet address</a></b>, <b><a href="#thenetwork">the network</a></b>, and <b><a href="#sitename">sitename</a></b>.</p> + +<hr> +Node:<a name="banner">banner</a>, Next:<a rel="next" href="#bannerad">banner ad</a>, Previous:<a rel="previous" href="#bangpath">bang path</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>banner</b> n.</p> + +<p>1. The title page added to printouts by most print spoolers +(see <b><a href="#spool">spool</a></b>). Typically includes user +or account ID information in very large character-graphics +capitals. Also called a `burst page', because it indicates where +to burst (tear apart) fanfold paper to separate one user's +printout from the next. 2. A similar printout generated +(typically on multiple pages of fan-fold paper) from +user-specified text, e.g., by a program such as Unix's +<code>banner({1,6})</code>. 3. On interactive software, a first +screen containing a logo and/or author credits and/or a copyright +notice. This is probably now the commonest sense.</p> + +<hr> +Node:<a name="bannerad">banner ad</a>, Next:<a rel="next" +href="#bannersite">banner site</a>, Previous:<a rel="previous" +href="#banner">banner</a>, Up:<a rel="up" href="#chap02">= +B =</a> <br> + + +<p><b>banner ad</b> n.</p> + +<p>Any of the annoying graphical advertisements that span the +tops of way too many Web pages.</p> + +<hr> +Node:<a name="bannersite">banner site</a>, Next:<a rel="next" +href="#bar">bar</a>, Previous:<a rel="previous" href="#bannerad">banner ad</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>banner site</b> n.</p> + +<p>[warez d00dz] A FTP site storing pirated files where one must +first click on several banners and/or subscribe to various `free' +services, usually generating some form of revenues for the site +owner, to be able to access the site. More often than not, the +username/password painfully obtained by clicking on banners and +subscribing to bogus services or mailing lists turns out to be +non-working or gives access to a site that always responds busy. +See <b><a href="#ratiosite">ratio site</a></b>, <b><a href="#leechmode">leech mode</a></b>.</p> + +<hr> +Node:<a name="bar">bar</a>, Next:<a rel="next" href="#baremetal">bare metal</a>, Previous:<a rel="previous" href="#bannersite">banner site</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bar</b> /bar/ n.</p> + +<p>1. [very common] The second <b><a href="#metasyntacticvariable">metasyntactic variable</a></b>, after +<b><a href="#foo">foo</a></b> and before <b><a href="#baz">baz</a></b>. "Suppose we have two functions: FOO and BAR. +FOO calls BAR<small>...</small>." 2. Often appended to <b><a +href="#foo">foo</a></b> to produce <b><a href="#foobar">foobar</a></b>.</p> + +<hr> +Node:<a name="baremetal">bare metal</a>, Next:<a rel="next" +href="#barf">barf</a>, Previous:<a rel="previous" href="#bar">bar</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>bare metal</b> n.</p> + +<p>1. [common] New computer hardware, unadorned with such snares +and delusions as an <b><a href="#operatingsystem">operating +system</a></b>, an <b><a href="#HLL">HLL</a></b>, or even +assembler. Commonly used in the phrase `programming on the bare +metal', which refers to the arduous work of <b><a href="#bitbashing">bit bashing</a></b> needed to create these basic +tools for a new machine. Real bare-metal programming involves +things like building boot proms and BIOS chips, implementing +basic monitors used to test device drivers, and writing the +assemblers that will be used to write the compiler back ends that +will give the new machine a real development environment. 2. +`Programming on the bare metal' is also used to describe a style +of <b><a href="#hand-hacking">hand-hacking</a></b> that relies on +bit-level peculiarities of a particular hardware design, esp. +tricks for speed and space optimization that rely on crocks such +as overlapping instructions (or, as in the famous case described +in <b><a href="#TheStoryofMel">The Story of Mel</a></b> +(in Appendix A), interleaving of opcodes on a magnetic drum to +minimize fetch delays due to the device's rotational latency). +This sort of thing has become less common as the relative costs +of programming time and machine resources have changed, but is +still found in heavily constrained environments such as +industrial embedded systems, and in the code of hackers who just +can't let go of that low-level control. See <b><a href="#RealProgrammer">Real Programmer</a></b>.</p> + +<p>In the world of personal computing, bare metal programming +(especially in sense 1 but sometimes also in sense 2) is often +considered a <b><a href="#GoodThing">Good Thing</a></b>, or at +least a necessary evil (because these machines have often been +sufficiently slow and poorly designed to make it necessary; see +<b><a href="#ill-behaved">ill-behaved</a></b>). There, the term +usually refers to bypassing the BIOS or OS interface and writing +the application to directly access device registers and machine +addresses. "To get 19.2 kilobaud on the serial port, you need to +get down to the bare metal." People who can do this sort of thing +well are held in high regard.</p> + +<hr> +Node:<a name="barf">barf</a>, Next:<a rel="next" href="#barfmail">barfmail</a>, Previous:<a rel="previous" href="#baremetal">bare metal</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>barf</b> /barf/ n.,v.</p> + +<p>[common; from mainstream slang meaning `vomit'] 1. interj. +Term of disgust. This is the closest hackish equivalent of the +Valspeak "gag me with a spoon". (Like, euwww!) See <b><a href="#bletch">bletch</a></b>. 2. vi. To say "Barf!" or emit some +similar expression of disgust. "I showed him my latest hack and +he barfed" means only that he complained about it, not that he +literally vomited. 3. vi. To fail to work because of unacceptable +input, perhaps with a suitable error message, perhaps not. +Examples: "The division operation barfs if you try to divide by +0." (That is, the division operation checks for an attempt to +divide by zero, and if one is encountered it causes the operation +to fail in some unspecified, but generally obvious, manner.) "The +text editor barfs if you try to read in a new file before writing +out the old one." See <b><a href="#choke">choke</a></b>, <b><a +href="#gag">gag</a></b>. In Commonwealth Hackish, `barf' is +generally replaced by `puke' or `vom'. <b><a href="#barf">barf</a></b> is sometimes also used as a <b><a href="#metasyntacticvariable">metasyntactic variable</a></b>, like +<b><a href="#foo">foo</a></b> or <b><a href="#bar">bar</a></b>.</p> + +<hr> +Node:<a name="barfmail">barfmail</a>, Next:<a rel="next" href="#barfulation">barfulation</a>, Previous:<a rel="previous" href="#barf">barf</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>barfmail</b> n.</p> + +<p>Multiple <b><a href="#bouncemessage">bounce +message</a></b>s accumulating to the level of serious annoyance, +or worse. The sort of thing that happens when an inter-network +mail gateway goes down or wonky.</p> + +<hr> +Node:<a name="barfulation">barfulation</a>, Next:<a rel="next" +href="#barfulous">barfulous</a>, Previous:<a rel="previous" href="#barfmail">barfmail</a>, Up:<a rel="up" href="#chap02">= +B =</a> <br> + + +<p><b>barfulation</b> /bar`fyoo-lay'sh*n/ interj.</p> + +<p>Variation of <b><a href="#barf">barf</a></b> used around the +Stanford area. An exclamation, expressing disgust. On seeing some +particularly bad code one might exclaim, "Barfulation! Who wrote +this, Quux?"</p> + +<hr> +Node:<a name="barfulous">barfulous</a>, Next:<a rel="next" href="#barn">barn</a>, Previous:<a rel="previous" href="#barfulation">barfulation</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>barfulous</b> /bar'fyoo-l*s/ adj.</p> + +<p>(alt. `barfucious', /bar-fyoo-sh*s/) Said of something that +would make anyone barf, if only for esthetic reasons.</p> + +<hr> +Node:<a name="barn">barn</a>, Next:<a rel="next" href="#barney">barney</a>, Previous:<a rel="previous" href="#barfulous">barfulous</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>barn</b> n.</p> + +<p>[uncommon; prob. from the nuclear military] An unexpectedly +large quantity of something: a unit of measurement. "Why is +/var/adm taking up so much space?" "The logs have grown to +several barns." The source of this is clear: when physicists were +first studying nuclear interactions, the probability was thought +to be proportional to the cross-sectional area of the nucleus +(this probability is still called the cross-section). Upon +experimenting, they discovered the interactions were far more +probable than expected; the nuclei were `as big as a barn'. The +units for cross-sections were christened Barns, (10^-24 cm^2) and +the book containing cross-sections has a picture of a barn on the +cover.</p> + +<hr> +Node:<a name="barney">barney</a>, Next:<a rel="next" href="#baroque">baroque</a>, Previous:<a rel="previous" href="#barn">barn</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>barney</b> n.</p> + +<p>In Commonwealth hackish, `barney' is to <b><a href="#fred">fred</a></b> (sense #1) as <b><a href="#bar">bar</a></b> +is to <b><a href="#foo">foo</a></b>. That is, people who commonly +use `fred' as their first metasyntactic variable will often use +`barney' second. The reference is, of course, to Fred Flintstone +and Barney Rubble in the Flintstones cartoons.</p> + +<hr> +Node:<a name="baroque">baroque</a>, Next:<a rel="next" href="#BASIC">BASIC</a>, Previous:<a rel="previous" href="#barney">barney</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>baroque</b> adj.</p> + +<p>[common] Feature-encrusted; complex; gaudy; verging on +excessive. Said of hardware or (esp.) software designs, this has +many of the connotations of <b><a href="#elephantine">elephantine</a></b> or <b><a href="#monstrosity">monstrosity</a></b> but is less extreme and not +pejorative in itself. "Metafont even has features to introduce +random variations to its letterform output. Now <i>that</i> is +baroque!" See also <b><a href="#rococo">rococo</a></b>.</p> + +<hr> +Node:<a name="BASIC">BASIC</a>, Next:<a rel="next" href="#batbelt">batbelt</a>, Previous:<a rel="previous" href="#baroque">baroque</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>BASIC</b> /bay'-sic/ n.</p> + +<p>A programming language, originally designed for Dartmouth's +experimental timesharing system in the early 1960s, which for +many years was the leading cause of brain damage in +proto-hackers. Edsger W. Dijkstra observed in "Selected Writings +on Computing: A Personal Perspective" that "It is practically +impossible to teach good programming style to students that have +had prior exposure to BASIC: as potential programmers they are +mentally mutilated beyond hope of regeneration." This is another +case (like <b><a href="#Pascal">Pascal</a></b>) of the cascading +<b><a href="#lossage">lossage</a></b> that happens when a +language deliberately designed as an educational toy gets taken +too seriously. A novice can write short BASIC programs (on the +order of 10-20 lines) very easily; writing anything longer (a) is +very painful, and (b) encourages bad habits that will make it +harder to use more powerful languages well. This wouldn't be so +bad if historical accidents hadn't made BASIC so common on +low-end micros in the 1980s. As it is, it probably ruined tens of +thousands of potential wizards.</p> + +<p>[1995: Some languages called `BASIC' aren't quite this nasty +any more, having acquired Pascal- and C-like procedures and +control structures and shed their line numbers. --ESR]</p> + +<p>Note: the name is commonly parsed as Beginner's All-purpose +Symbolic Instruction Code, but this is a <b><a href="#backronym">backronym</a></b>. BASIC was originally named Basic, +simply because it was a simple and basic programming language. +Because most programming language names were in fact acronyms, +BASIC was often capitalized just out of habit or to be silly. No +acronym for BASIC originally existed or was intended (as one can +verify by reading texts through the early 1970s). Later, around +the mid-1970s, people began to make up backronyms for BASIC +because they weren't sure. Beginner's All-purpose Symbolic +Instruction Code is the one that caught on.</p> + +<hr> +Node:<a name="batbelt">batbelt</a>, Next:<a rel="next" href="#batch">batch</a>, Previous:<a rel="previous" href="#BASIC">BASIC</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>batbelt</b> n.</p> + +<p>Many hackers routinely hang numerous devices such as pagers, +cell-phones, personal organizers, leatherman multitools, pocket +knives, flashlights, walkie-talkies, even miniature computers +from their belts. When many of these devices are worn at once, +the hacker's belt somewhat resembles Batman's utility belt; hence +it is referred to as a batbelt.</p> + +<hr> +Node:<a name="batch">batch</a>, Next:<a rel="next" href="#bathtubcurve">bathtub curve</a>, Previous:<a rel="previous" +href="#batbelt">batbelt</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>batch</b> adj.</p> + +<p>1. Non-interactive. Hackers use this somewhat more loosely +than the traditional technical definitions justify; in +particular, switches on a normally interactive program that +prepare it to receive non-interactive command input are often +referred to as `batch mode' switches. A `batch file' is a series +of instructions written to be handed to an interactive program +running in batch mode. 2. Performance of dreary tasks all at one +sitting. "I finally sat down in batch mode and wrote out checks +for all those bills; I guess they'll turn the electricity back on +next week<small>...</small>" 3. `batching up': Accumulation of a +number of small tasks that can be lumped together for greater +efficiency. "I'm batching up those letters to send sometime" "I'm +batching up bottles to take to the recycling center."</p> + +<hr> +Node:<a name="bathtubcurve">bathtub curve</a>, Next:<a rel="next" href="#baud">baud</a>, Previous:<a rel="previous" href="#batch">batch</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>bathtub curve</b> n.</p> + +<p>Common term for the curve (resembling an end-to-end section of +one of those claw-footed antique bathtubs) that describes the +expected failure rate of electronics with time: initially high, +dropping to near 0 for most of the system's lifetime, then rising +again as it `tires out'. See also <b><a href="#burn-inperiod">burn-in period</a></b>, <b><a href="#infantmortality">infant mortality</a></b>.</p> + +<hr> +Node:<a name="baud">baud</a>, Next:<a rel="next" href="#baudbarf">baud barf</a>, Previous:<a rel="previous" href="#bathtubcurve">bathtub curve</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>baud</b> /bawd/ n.</p> + +<p>[simplified from its technical meaning] n. Bits per second. +Hence kilobaud or Kbaud, thousands of bits per second. The +technical meaning is `level transitions per second'; this +coincides with bps only for two-level modulation with no framing +or stop bits. Most hackers are aware of these nuances but +blithely ignore them.</p> + +<p>Historical note: `baud' was originally a unit of telegraph +signalling speed, set at one pulse per second. It was proposed at +the November, 1926 conference of the Comité Consultatif +International Des Communications Télégraphiques as +an improvement on the then standard practice of referring to line +speeds in terms of words per minute, and named for Jean Maurice +Emile Baudot (1845-1903), a French engineer who did a lot of +pioneering work in early teleprinters.</p> + +<hr> +Node:<a name="baudbarf">baud barf</a>, Next:<a rel="next" +href="#baz">baz</a>, Previous:<a rel="previous" href="#baud">baud</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>baud barf</b> /bawd barf/ n.</p> + +<p>The garbage one gets a terminal (or terminal emulator) when +using a modem connection with some protocol setting (esp. line +speed) incorrect, or when someone picks up a voice extension on +the same line, or when really bad line noise disrupts the +connection. Baud barf is not completely <b><a href="#random">random</a></b>, by the way; hackers with a lot of +serial-line experience can usually tell whether the device at the +other end is expecting a higher or lower speed than the terminal +is set to. <i>Really</i> experienced ones can identify +particular speeds.</p> + +<hr> +Node:<a name="baz">baz</a>, Next:<a rel="next" href="#bazaar">bazaar</a>, Previous:<a rel="previous" href="#baudbarf">baud barf</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>baz</b> /baz/ n.</p> + +<p>1. [common] The third <b><a href="#metasyntacticvariable">metasyntactic variable</a></b> +"Suppose we have three functions: FOO, BAR, and BAZ. FOO calls +BAR, which calls BAZ<small>...</small>." (See also <b><a href="#fum">fum</a></b>) 2. interj. A term of mild annoyance. In this +usage the term is often drawn out for 2 or 3 seconds, producing +an effect not unlike the bleating of a sheep; /baaaaaaz/. 3. +Occasionally appended to <b><a href="#foo">foo</a></b> to produce +`foobaz'.</p> + +<p>Earlier versions of this lexicon derived `baz' as a Stanford +corruption of <b><a href="#bar">bar</a></b>. However, Pete Samson +(compiler of the <b><a href="#TMRC">TMRC</a></b> lexicon) reports +it was already current when he joined TMRC in 1958. He says "It +came from "Pogo". Albert the Alligator, when vexed or outraged, +would shout `Bazz Fazz!' or `Rowrbazzle!' The club layout was +said to model the (mythical) New England counties of Rowrfolk and +Bassex (Rowrbazzle mingled with +(Norfolk/Suffolk/Middlesex/Essex)."</p> + +<hr> +Node:<a name="bazaar">bazaar</a>, Next:<a rel="next" href="#bboard">bboard</a>, Previous:<a rel="previous" href="#baz">baz</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + +<p><b>bazaar</b> n.,adj.</p> + +<p> +In 1997, after meditatating on the success of <b><a href="#Linux">Linux</a></b> +for three years, the Jargon File's own editor ESR wrote an analytical paper on +hacker culture and development models titled The Cathedral and the Bazaar. The +main argument of the paper was that <b><a href="#BrookssLaw">Brooks's +Law</a></b> is not the whole story; given the right social machinery, debugging +can be efficiently parallelized across large numbers of programmers. The title +metaphor caught on (see also <b><a href="#cathedral">cathedral</a></b>), and +the style of development typical in the Linux community is now often referred +to as the bazaar mode. Its characteristics include releasing code early and +often, and actively seeking the largest possible pool of peer reviewers. +</p> + +<hr> +Node:<a name="bboard">bboard</a>, Next:<a rel="next" href="#BBS">BBS</a>, Previous:<a rel="previous" href="#bazaar">bazaar</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>bboard</b> /bee'bord/ n.</p> + +<p>[contraction of `bulletin board'] 1. Any electronic bulletin +board; esp. used of <b><a href="#BBS">BBS</a></b> systems running +on personal micros, less frequently of a Usenet <b><a href="#newsgroup">newsgroup</a></b> (in fact, use of this term for a +newsgroup generally marks one either as a <b><a href="#newbie">newbie</a></b> fresh in from the BBS world or as a real +old-timer predating Usenet). 2. At CMU and other colleges with +similar facilities, refers to campus-wide electronic bulletin +boards. 3. The term `physical bboard' is sometimes used to refer +to an old-fashioned, non-electronic cork-and-thumbtack memo +board. At CMU, it refers to a particular one outside the CS +Lounge.</p> + +<p>In either of senses 1 or 2, the term is usually prefixed by +the name of the intended board (`the Moonlight Casino bboard' or +`market bboard'); however, if the context is clear, the +better-read bboards may be referred to by name alone, as in (at +CMU) "Don't post for-sale ads on general".</p> + +<hr> +Node:<a name="BBS">BBS</a>, Next:<a rel="next" href="#BCPL">BCPL</a>, Previous:<a rel="previous" href="#bboard">bboard</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>BBS</b> /B-B-S/ n.</p> + +<p>[common; abbreviation, `Bulletin Board System'] An electronic +bulletin board system; that is, a message database where people +can log in and leave broadcast messages for others grouped +(typically) into <b><a href="#topicgroup">topic +group</a></b>s. The term was especially applied to the thousands +of local BBS systems that operated during the pre-Internet +microcomputer era of roughly 1980 to 1995, typically run by +amateurs for fun out of their homes on MS-DOS boxes with a single +modem line each. Fans of Usenet and Internet or the big +commercial timesharing bboards such as CompuServe and GEnie +tended to consider local BBSes the low-rent district of the +hacker culture, but they served a valuable function by knitting +together lots of hackers and users in the personal-micro world +who would otherwise have been unable to exchange code at all. +Post-Internet, BBSs are likely to be local newsgroups on an ISP; +efficiency has increased but a certain flavor has been lost. See +also <b><a href="#bboard">bboard</a></b>.</p> + +<hr> +Node:<a name="BCPL">BCPL</a>, Next:<a rel="next" href="#beam">beam</a>, Previous:<a rel="previous" href="#BBS">BBS</a>, +Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>BCPL</b> // n.</p> + +<p>[abbreviation, `Basic Combined Programming Language') A +programming language developed by Martin Richards in Cambridge in +1967. It is remarkable for its rich syntax, small size of +compiler (it can be run in 16k) and extreme portability. It +reached break-even point at a very early stage, and was the +language in which the original <b><a href="#helloworld">hello +world</a></b> program was written. It has been ported to so many +different systems that its creator confesses to having lost +count. It has only one data type (a machine word) which can be +used as an integer, a character, a floating point number, a +pointer, or almost anything else, depending on context. BCPL was +a precursor of C, which inherited some of its features.</p> + +<hr> +Node:<a name="beam">beam</a>, Next:<a rel="next" href="#beaniekey">beanie key</a>, Previous:<a rel="previous" href="#BCPL">BCPL</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>beam</b> vt.</p> + +<p>[from Star Trek Classic's "Beam me up, Scotty!"] 1. To +transfer <b><a href="#softcopy">softcopy</a></b> of a file +electronically; most often in combining forms such as `beam me a +copy' or `beam that over to his site'. 2. Palm Pilot users very +commonly use this term for the act of exchanging bits via the +infrared links on their machines (this term seems to have +originated with the ill-fated Newton Message Pad). Compare <b><a +href="#blast">blast</a></b>, <b><a href="#snarf">snarf</a></b>, +<b><a href="#BLT">BLT</a></b>.</p> + +<hr> +Node:<a name="beaniekey">beanie key</a>, Next:<a rel="next" +href="#beep">beep</a>, Previous:<a rel="previous" href="#beam">beam</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>beanie key</b> n.</p> + +<p>[Mac users] See <b><a href="#commandkey">command +key</a></b>.</p> + +<hr> +Node:<a name="beep">beep</a>, Next:<a rel="next" href="#Befunge">Befunge</a>, Previous:<a rel="previous" href="#beaniekey">beanie key</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>beep</b> n.,v.</p> + +<p>Syn. <b><a href="#feep">feep</a></b>. This term is techspeak +under MS-DOS and OS/2, and seems to be generally preferred among +micro hobbyists.</p> + +<hr> +Node:<a name="Befunge">Befunge</a>, Next:<a rel="next" href="#beigetoaster">beige toaster</a>, Previous:<a rel="previous" +href="#beep">beep</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>Befunge</b> n.</p> + +<p>A worthy companion to <b><a href="#INTERCAL">INTERCAL</a></b>; +a computer language family which escapes the quotidian limitation +of linear control flow and embraces program counters flying +through multiple dimensions with exotic topologies. Sadly, the +Befunge home page has vanished, but a Befunge version of the +<b><a href="#helloworld">hello world</a></b> program is at <a +href="http://www.catseye.mb.ca/esoteric/befunge.html">http://www.catseye.mb.ca/esoteric/befunge.html</a>.</p> + +<hr> +Node:<a name="beigetoaster">beige toaster</a>, Next:<a rel="next" href="#bellsandwhistles">bells and whistles</a>, +Previous:<a rel="previous" href="#Befunge">Befunge</a>, Up:<a +rel="up" href="#chap02">= B =</a> <br> + + +<p><b>beige toaster</b> n.</p> + +<p>A Macintosh. See <b><a href="#toaster">toaster</a></b>; +compare <b><a href="#Macintrash">Macintrash</a></b>, <b><a href="#maggotbox">maggotbox</a></b>.</p> + +<hr> +Node:<a name="bellsandwhistles">bells and whistles</a>, +Next:<a rel="next" href="#bellswhistlesandgongs">bells +whistles and gongs</a>, Previous:<a rel="previous" href="#beigetoaster">beige toaster</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bells and whistles</b> n.</p> + +<p>[common] Features added to a program or system to make it more +<b><a href="#flavorful">flavorful</a></b> from a hacker's point +of view, without necessarily adding to its utility for its +primary function. Distinguished from <b><a href="#chrome">chrome</a></b>, which is intended to attract users. +"Now that we've got the basic program working, let's go back and +add some bells and whistles." No one seems to know what +distinguishes a bell from a whistle. The recognized emphatic form +is "bells, whistles, and gongs".</p> + +<p>It used to be thought that this term derived from the toyboxes +on theater organs. However, the "and gongs" strongly suggests a +different origin, at sea. Before powered horns, ships routinely +used bells, whistles, and gongs to signal each other over longer +distances than voice can carry.</p> + +<hr> +Node:<a name="bellswhistlesandgongs">bells whistles and +gongs</a>, Next:<a rel="next" href="#benchmark">benchmark</a>, +Previous:<a rel="previous" href="#bellsandwhistles">bells +and whistles</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>bells whistles and gongs</b> n.</p> + +<p>A standard elaborated form of <b><a href="#bellsandwhistles">bells and whistles</a></b>; typically +said with a pronounced and ironic accent on the `gongs'.</p> + +<hr> +Node:<a name="benchmark">benchmark</a>, Next:<a rel="next" href="#BerkeleyQualitySoftware">Berkeley Quality Software</a>, +Previous:<a rel="previous" href="#bellswhistlesandgongs">bells whistles and gongs</a>, +Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>benchmark</b> n.</p> + +<p>[techspeak] An inaccurate measure of computer performance. "In +the computer industry, there are three kinds of lies: lies, damn +lies, and benchmarks." Well-known ones include Whetstone, +Dhrystone, Rhealstone (see <b><a href="#h">h</a></b>), the +Gabriel LISP benchmarks (see <b><a href="#gabriel">gabriel</a></b>), the SPECmark suite, and LINPACK. See +also <b><a href="#machoflops">machoflops</a></b>, <b><a href="#MIPS">MIPS</a></b>, <b><a href="#smokeandmirrors">smoke +and mirrors</a></b>.</p> + +<hr> +Node:<a name="BerkeleyQualitySoftware">Berkeley Quality +Software</a>, Next:<a rel="next" href="#berklix">berklix</a>, +Previous:<a rel="previous" href="#benchmark">benchmark</a>, Up:<a +rel="up" href="#chap02">= B =</a> <br> + + +<p><b>Berkeley Quality Software</b> adj.</p> + +<p>(often abbreviated `BQS') Term used in a pejorative sense to +refer to software that was apparently created by rather +spaced-out hackers late at night to solve some unique problem. It +usually has nonexistent, incomplete, or incorrect documentation, +has been tested on at least two examples, and core dumps when +anyone else attempts to use it. This term was frequently applied +to early versions of the <code>dbx(1)</code> debugger. See also +<b><a href="#Berzerkeley">Berzerkeley</a></b>.</p> + +<p>Note to British and Commonwealth readers: that's /berk'lee/, +not /bark'lee/ as in British Received Pronunciation.</p> + +<hr> +Node:<a name="berklix">berklix</a>, Next:<a rel="next" href="#Berzerkeley">Berzerkeley</a>, Previous:<a rel="previous" href="#BerkeleyQualitySoftware">Berkeley Quality Software</a>, +Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>berklix</b> /berk'liks/ n.,adj.</p> + +<p>[contraction of `Berkeley Unix'] See <b><a href="#BSD">BSD</a></b>. Not used at Berkeley itself. May be more +common among <b><a href="#suit">suit</a></b>s attempting to sound +like cognoscenti than among hackers, who usually just say +`BSD'.</p> + +<hr> +Node:<a name="Berzerkeley">Berzerkeley</a>, Next:<a rel="next" +href="#beta">beta</a>, Previous:<a rel="previous" href="#berklix">berklix</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>Berzerkeley</b> /b*r-zer'klee/ n.</p> + +<p>[from `berserk', via the name of a now-deceased record label; +poss. originated by famed columnist Herb Caen] Humorous +distortion of `Berkeley' used esp. to refer to the practices or +products of the <b><a href="#BSD">BSD</a></b> Unix hackers. See +<b><a href="#softwarebloat">software bloat</a></b>, <b><a +href="#Missedem-five">Missed'em-five</a></b>, <b><a href="#BerkeleyQualitySoftware">Berkeley Quality +Software</a></b>.</p> + +<p>Mainstream use of this term in reference to the cultural and +political peculiarities of UC Berkeley as a whole has been +reported from as far back as the 1960s.</p> + +<hr> +Node:<a name="beta">beta</a>, Next:<a rel="next" href="#BFI">BFI</a>, Previous:<a rel="previous" href="#Berzerkeley">Berzerkeley</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>beta</b> /bay't*/, /be't*/ or (Commonwealth) /bee't*/ +n.</p> + +<p>1. Mostly working, but still under test; usu. used with `in': +`in beta'. In the <b><a href="#RealWorld">Real World</a></b>, +systems (hardware or software) software often go through two +stages of release testing: Alpha (in-house) and Beta +(out-house?). Beta releases are generally made to a group of +lucky (or unlucky) trusted customers. 2. Anything that is new and +experimental. "His girlfriend is in beta" means that he is still +testing for compatibility and reserving judgment. 3. Flaky; +dubious; suspect (since beta software is notoriously buggy).</p> + +<p>Historical note: More formally, to beta-test is to test a +pre-release (potentially unreliable) version of a piece of +software by making it available to selected (or self-selected) +customers and users. This term derives from early 1960s +terminology for product cycle checkpoints, first used at IBM but +later standard throughout the industry. `Alpha Test' was the +unit, module, or component test phase; `Beta Test' was initial +system test. These themselves came from earlier A- and B-tests +for hardware. The A-test was a feasibility and manufacturability +evaluation done before any commitment to design and development. +The B-test was a demonstration that the engineering model +functioned as specified. The C-test (corresponding to today's +beta) was the B-test performed on early samples of the production +design, and the D test was the C test repeated after the model +had been in production a while.</p> + +<hr> +Node:<a name="BFI">BFI</a>, Next:<a rel="next" href="#bible">bible</a>, Previous:<a rel="previous" href="#beta">beta</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>BFI</b> /B-F-I/ n.</p> + +<p>See <b><a href="#bruteforceandignorance">brute force +and ignorance</a></b>. Also encountered in the variants `BFMI', +`brute force and <i>massive</i> ignorance' and `BFBI' `brute +force and bloody ignorance'. In dome parts of the U.S. this +abbreviation was probably reinforced by a company called +Browning-Ferris Industries who used to be in the waste-management +business; a large BFI logo in white-on-blue could be seen on the +sides of garbage trucks.</p> + +<hr> +Node:<a name="bible">bible</a>, Next:<a rel="next" href="#BiCapitalization">BiCapitalization</a>, Previous:<a rel="previous" href="#BFI">BFI</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bible</b> n.</p> + +<p>1. One of a small number of fundamental source books such as +<b><a href="#Knuth">Knuth</a></b>, <b><a href="#KandR">K&R</a></b>, or the <b><a href="#CamelBook">Camel Book</a></b>. 2. The most detailed and +authoritative reference for a particular language, operating +system, or other complex software system.</p> + +<hr> +Node:<a name="BiCapitalization">BiCapitalization</a>, Next:<a +rel="next" href="#B1FF">B1FF</a>, Previous:<a rel="previous" +href="#bible">bible</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>BiCapitalization</b> n.</p> + +<p>The act said to have been performed on trademarks (such as +<b><a href="#PostScript">PostScript</a></b>, NeXT, <b><a href="#NeWS">NeWS</a></b>, VisiCalc, FrameMaker, TK!solver, +EasyWriter) that have been raised above the ruck of common +coinage by nonstandard capitalization. Too many <b><a href="#marketroid">marketroid</a></b> types think this sort of thing +is really cute, even the 2,317th time they do it. Compare <b><a +href="#studlycaps">studlycaps</a></b>.</p> + +<hr> +Node:<a name="B1FF">B1FF</a>, Next:<a rel="next" href="#BI">BI</a>, Previous:<a rel="previous" href="#BiCapitalization">BiCapitalization</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>B1FF</b> /bif/ [Usenet] (alt. `BIFF') n.</p> + +<p>The most famous <b><a href="#pseudo">pseudo</a></b>, and the +prototypical <b><a href="#newbie">newbie</a></b>. Articles from +B1FF feature all uppercase letters sprinkled liberally with +bangs, typos, `cute' misspellings (EVRY BUDY LUVS GOOD OLD BIFF +CUZ HE"S A K00L DOOD AN HE RITES REEL AWESUM THINGZ IN CAPITULL +LETTRS LIKE THIS!!!), use (and often misuse) of fragments of +<b><a href="#talkmode">talk mode</a></b> abbreviations, a long +<b><a href="#sigblock">sig block</a></b> (sometimes even a +<b><a href="#doubledsig">doubled sig</a></b>), and unbounded +naivete. B1FF posts articles using his elder brother's VIC-20. +B1FF's location is a mystery, as his articles appear to come from +a variety of sites. However, <b><a href="#BITNET">BITNET</a></b> +seems to be the most frequent origin. The theory that B1FF is a +denizen of BITNET is supported by B1FF's (unfortunately invalid) +electronic mail address: B1FF@BIT.NET.</p> + +<p>[1993: Now It Can Be Told! My spies inform me that B1FF was +originally created by Joe Talmadge <jat@cup.hp.com>, also +the author of the infamous and much-plagiarized "Flamer's Bible". +The BIFF filter he wrote was later passed to Richard Sexton, who +posted BIFFisms much more widely. Versions have since been posted +for the amusement of the net at large. See also <b><a href="#JeffK.">Jeff K.</a></b> --ESR]</p> + +<hr> +Node:<a name="BI">BI</a>, Next:<a rel="next" href="#biff">biff</a>, Previous:<a rel="previous" href="#B1FF">B1FF</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>BI</b> //</p> + +<p>Common written abbreviation for <b><a href="#BreidbartIndex">Breidbart Index</a></b>.</p> + +<hr> +Node:<a name="biff">biff</a>, Next:<a rel="next" href="#BigGrayWall">Big Gray Wall</a>, Previous:<a rel="previous" href="#BI">BI</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>biff</b> /bif/ vt.</p> + +<p>To notify someone of incoming mail. From the BSD utility +<code>biff(1)</code>, which was in turn named after a friendly +dog who used to chase frisbees in the halls at UCB while 4.2BSD +was in development. There was a legend that it had a habit of +barking whenever the mailman came, but the author of +<code>biff</code> says this is not true. No relation to <b><a +href="#B1FF">B1FF</a></b>.</p> + +<hr> +Node:<a name="BigGrayWall">Big Gray Wall</a>, Next:<a rel="next" href="#bigiron">big iron</a>, Previous:<a rel="previous" href="#biff">biff</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>Big Gray Wall</b> n.</p> + +<p>What faces a <b><a href="#VMS">VMS</a></b> user searching for +documentation. A full VMS kit comes on a pallet, the +documentation taking up around 15 feet of shelf space before the +addition of layered products such as compilers, databases, +multivendor networking, and programming tools. Recent (since VMS +version 5) documentation comes with gray binders; under VMS +version 4 the binders were orange (`big orange wall'), and under +version 3 they were blue. See <b><a href="#VMS">VMS</a></b>. +Often contracted to `Gray Wall'.</p> + +<hr> +Node:<a name="bigiron">big iron</a>, Next:<a rel="next" href="#BigRedSwitch">Big Red Switch</a>, Previous:<a rel="previous" href="#BigGrayWall">Big Gray Wall</a>, Up:<a +rel="up" href="#chap02">= B =</a> <br> + + +<p><b>big iron</b> n.</p> + +<p>[common] Large, expensive, ultra-fast computers. Used +generally of <b><a href="#number-crunching">number-crunching</a></b> supercomputers such +as Crays, but can include more conventional big commercial IBMish +mainframes. Term of approval; compare <b><a href="#heavymetal">heavy metal</a></b>, oppose <b><a href="#dinosaur">dinosaur</a></b>.</p> + +<hr> +Node:<a name="BigRedSwitch">Big Red Switch</a>, Next:<a +rel="next" href="#BigRoom">Big Room</a>, Previous:<a rel="previous" href="#bigiron">big iron</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>Big Red Switch</b> n.</p> + +<p>[IBM] The power switch on a computer, esp. the `Emergency +Pull' switch on an IBM <b><a href="#mainframe">mainframe</a></b> +or the power switch on an IBM PC where it really is large and +red. "This !@%$% <b><a href="#bittybox">bitty box</a></b> is +hung again; time to hit the Big Red Switch." Sources at IBM +report that, in tune with the company's passion for <b><a href="#TLA">TLA</a></b>s, this is often abbreviated as `BRS' (this has +also become established on FidoNet and in the PC <b><a href="#clone">clone</a></b> world). It is alleged that the emergency +pull switch on an IBM 360/91 actually fired a non-conducting bolt +into the main power feed; the BRSes on more recent mainframes +physically drop a block into place so that they can't be pushed +back in. People get fired for pulling them, especially +inappropriately (see also <b><a href="#molly-guard">molly-guard</a></b>). Compare <b><a href="#powercycle">power cycle</a></b>, <b><a href="#three-fingersalute">three-finger salute</a></b>, <b><a href="#120reset">120 reset</a></b>; see also <b><a href="#scramswitch">scram switch</a></b>.</p> + +<hr> +Node:<a name="BigRoom">Big Room</a>, Next:<a rel="next" href="#bigwin">big win</a>, Previous:<a rel="previous" href="#BigRedSwitch">Big Red Switch</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>Big Room</b> n.</p> + +<p>(Also `Big Blue Room') The extremely large room with the blue +ceiling and intensely bright light (during the day) or black +ceiling with lots of tiny night-lights (during the night) found +outside all computer installations. "He can't come to the phone +right now, he's somewhere out in the Big Room."</p> + +<hr> +Node:<a name="bigwin">big win</a>, Next:<a rel="next" href="#big-endian">big-endian</a>, Previous:<a rel="previous" href="#BigRoom">Big Room</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>big win</b> n.</p> + +<p>1. [common] Major success. 2. [MIT] Serendipity. "Yes, those +two physicists discovered high-temperature superconductivity in a +batch of ceramic that had been prepared incorrectly according to +their experimental schedule. Small mistake; big win!" See <b><a +href="#winbig">win big</a></b>.</p> + +<hr> +Node:<a name="big-endian">big-endian</a>, Next:<a rel="next" +href="#bignum">bignum</a>, Previous:<a rel="previous" href="#bigwin">big win</a>, Up:<a rel="up" href="#chap02">= +B =</a> <br> + + +<p><b>big-endian</b> adj.</p> + +<p>[common; From Swift's "Gulliver's Travels" via the famous +paper "On Holy Wars and a Plea for Peace" by Danny Cohen, USC/ISI +IEN 137, dated April 1, 1980] 1. Describes a computer +architecture in which, within a given multi-byte numeric +representation, the most significant byte has the lowest address +(the word is stored `big-end-first'). Most processors, including +the IBM 370 family, the <b><a href="#PDP-10">PDP-10</a></b>, the +Motorola microprocessor families, and most of the various RISC +designs are big-endian. Big-endian byte order is also sometimes +called `network order'. See <b><a href="#little-endian">little-endian</a></b>, <b><a href="#middle-endian">middle-endian</a></b>, <b><a href="#NUXIproblem">NUXI problem</a></b>, <b><a href="#swab">swab</a></b>. 2. An <b><a href="#Internetaddress">Internet address</a></b> the wrong way +round. Most of the world follows the Internet standard and writes +email addresses starting with the name of the computer and ending +up with the name of the country. In the U.K. the Joint Networking +Team had decided to do it the other way round before the Internet +domain standard was established. Most gateway sites have <b><a +href="#ad-hockery">ad-hockery</a></b> in their mailers to handle +this, but can still be confused. In particular, the address +<i>me@uk.ac.bris.pys.as</i> could be interpreted in JANET's +big-endian way as one in the U.K. (domain <i>uk</i>) or in the +standard little-endian way as one in the domain <i>as</i> +(American Samoa) on the opposite side of the world.</p> + +<hr> +Node:<a name="bignum">bignum</a>, Next:<a rel="next" href="#bigot">bigot</a>, Previous:<a rel="previous" href="#big-endian">big-endian</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bignum</b> /big'nuhm/ n.</p> + +<p>[common; orig. from MIT MacLISP] 1. [techspeak] A +multiple-precision computer representation for very large +integers. 2. More generally, any very large number. "Have you +ever looked at the United States Budget? There's bignums for +you!" 3. [Stanford] In backgammon, large numbers on the dice +especially a roll of double fives or double sixes (compare <b><a +href="#moby">moby</a></b>, sense 4). See also <b><a href="#ElCaminoBignum">El Camino Bignum</a></b>.</p> + +<p>Sense 1 may require some explanation. Most computer languages +provide a kind of data called `integer', but such computer +integers are usually very limited in size; usually they must be +smaller than 2^(31) (2,147,483,648) or (on a <b><a href="#bittybox">bitty box</a></b>) 2^(15) (32,768). If you want to +work with numbers larger than that, you have to use +floating-point numbers, which are usually accurate to only six or +seven decimal places. Computer languages that provide bignums can +perform exact calculations on very large numbers, such as 1000! +(the factorial of 1000, which is 1000 times 999 times 998 times +<small>...</small> times 2 times 1). For example, this value for +1000! was computed by the MacLISP system using bignums:</p> + +<pre> +40238726007709377354370243392300398571937486421071 +46325437999104299385123986290205920442084869694048 +00479988610197196058631666872994808558901323829669 +94459099742450408707375991882362772718873251977950 +59509952761208749754624970436014182780946464962910 +56393887437886487337119181045825783647849977012476 +63288983595573543251318532395846307555740911426241 +74743493475534286465766116677973966688202912073791 +43853719588249808126867838374559731746136085379534 +52422158659320192809087829730843139284440328123155 +86110369768013573042161687476096758713483120254785 +89320767169132448426236131412508780208000261683151 +02734182797770478463586817016436502415369139828126 +48102130927612448963599287051149649754199093422215 +66832572080821333186116811553615836546984046708975 +60290095053761647584772842188967964624494516076535 +34081989013854424879849599533191017233555566021394 +50399736280750137837615307127761926849034352625200 +01588853514733161170210396817592151090778801939317 +81141945452572238655414610628921879602238389714760 +88506276862967146674697562911234082439208160153780 +88989396451826324367161676217916890977991190375403 +12746222899880051954444142820121873617459926429565 +81746628302955570299024324153181617210465832036786 +90611726015878352075151628422554026517048330422614 +39742869330616908979684825901254583271682264580665 +26769958652682272807075781391858178889652208164348 +34482599326604336766017699961283186078838615027946 +59551311565520360939881806121385586003014356945272 +24206344631797460594682573103790084024432438465657 +24501440282188525247093519062092902313649327349756 +55139587205596542287497740114133469627154228458623 +77387538230483865688976461927383814900140767310446 +64025989949022222176590433990188601856652648506179 +97023561938970178600408118897299183110211712298459 +01641921068884387121855646124960798722908519296819 +37238864261483965738229112312502418664935314397013 +74285319266498753372189406942814341185201580141233 +44828015051399694290153483077644569099073152433278 +28826986460278986432113908350621709500259738986355 +42771967428222487575867657523442202075736305694988 +25087968928162753848863396909959826280956121450994 +87170124451646126037902930912088908694202851064018 +21543994571568059418727489980942547421735824010636 +77404595741785160829230135358081840096996372524230 +56085590370062427124341690900415369010593398383577 +79394109700277534720000000000000000000000000000000 +00000000000000000000000000000000000000000000000000 +00000000000000000000000000000000000000000000000000 +00000000000000000000000000000000000000000000000000 +00000000000000000000000000000000000000000000000000 +000000000000000000. +</pre> + +<hr> +Node:<a name="bigot">bigot</a>, Next:<a rel="next" href="#bit">bit</a>, Previous:<a rel="previous" href="#bignum">bignum</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>bigot</b> n.</p> + +<p>[common] A person who is religiously attached to a particular +computer, language, operating system, editor, or other tool (see +<b><a href="#religiousissues">religious issues</a></b>). +Usually found with a specifier; thus, `cray bigot', `ITS bigot', +`APL bigot', `VMS bigot', `Berkeley bigot'. Real bigots can be +distinguished from mere partisans or zealots by the fact that +they refuse to learn alternatives even when the march of time +and/or technology is threatening to obsolete the favored tool. It +is truly said "You can tell a bigot, but you can't tell him +much." Compare <b><a href="#weenie">weenie</a></b>, <b><a href="#AmigaPersecutionComplex">Amiga Persecution +Complex</a></b>.</p> + +<hr> +Node:<a name="bit">bit</a>, Next:<a rel="next" href="#bitbang">bit bang</a>, Previous:<a rel="previous" href="#bigot">bigot</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>bit</b> n.</p> + +<p>[from the mainstream meaning and `Binary digIT'] 1. +[techspeak] The unit of information; the amount of information +obtained by asking a yes-or-no question for which the two +outcomes are equally probable. 2. [techspeak] A computational +quantity that can take on one of two values, such as true and +false or 0 and 1. 3. A mental flag: a reminder that something +should be done eventually. "I have a bit set for you." (I haven't +seen you for a while, and I'm supposed to tell or ask you +something.) 4. More generally, a (possibly incorrect) mental +state of belief. "I have a bit set that says that you were the +last guy to hack on EMACS." (Meaning "I think you were the last +guy to hack on EMACS, and what I am about to say is predicated on +this, so please stop me if this isn't true.")</p> + +<p>"I just need one bit from you" is a polite way of indicating +that you intend only a short interruption for a question that can +presumably be answered yes or no.</p> + +<p>A bit is said to be `set' if its value is true or 1, and +`reset' or `clear' if its value is false or 0. One speaks of +setting and clearing bits. To <b><a href="#toggle">toggle</a></b> +or `invert' a bit is to change it, either from 0 to 1 or from 1 +to 0. See also <b><a href="#flag">flag</a></b>, <b><a href="#trit">trit</a></b>, <b><a href="#modebit">mode +bit</a></b>.</p> + +<p>The term `bit' first appeared in print in the computer-science +sense in a 1948 paper by information theorist Claude Shannon, and +was there credited to the early computer scientist John Tukey +(who also seems to have coined the term `software'). Tukey +records that `bit' evolved over a lunch table as a handier +alternative to `bigit' or `binit', at a conference in the winter +of 1943-44.</p> + +<hr> +Node:<a name="bitbang">bit bang</a>, Next:<a rel="next" href="#bitbashing">bit bashing</a>, Previous:<a rel="previous" +href="#bit">bit</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>bit bang</b> n.</p> + +<p>Transmission of data on a serial line, when accomplished by +rapidly tweaking a single output bit, in software, at the +appropriate times. The technique is a simple loop with eight OUT +and SHIFT instruction pairs for each byte. Input is more +interesting. And full duplex (doing input and output at the same +time) is one way to separate the real hackers from the <b><a +href="#wannabee">wannabee</a></b>s.</p> + +<p>Bit bang was used on certain early models of Prime computers, +presumably when UARTs were too expensive, and on archaic Z80 +micros with a Zilog PIO but no SIO. In an interesting instance of +the <b><a href="#cycleofreincarnation">cycle of +reincarnation</a></b>, this technique returned to use in the +early 1990s on some RISC architectures because it consumes such +an infinitesimal part of the processor that it actually makes +sense not to have a UART. Compare <b><a href="#cycleofreincarnation">cycle of reincarnation</a></b>.</p> + +<hr> +Node:<a name="bitbashing">bit bashing</a>, Next:<a rel="next" +href="#bitbucket">bit bucket</a>, Previous:<a rel="previous" +href="#bitbang">bit bang</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bit bashing</b> n.</p> + +<p>(alt. `bit diddling' or <b><a href="#bittwiddling">bit +twiddling</a></b>) Term used to describe any of several kinds of +low-level programming characterized by manipulation of <b><a +href="#bit">bit</a></b>, <b><a href="#flag">flag</a></b>, <b><a +href="#nybble">nybble</a></b>, and other +smaller-than-character-sized pieces of data; these include +low-level device control, encryption algorithms, checksum and +error-correcting codes, hash functions, some flavors of graphics +programming (see <b><a href="#bitblt">bitblt</a></b>), and +assembler/compiler code generation. May connote either tedium or +a real technical challenge (more usually the former). "The +command decoding for the new tape driver looks pretty solid but +the bit-bashing for the control registers still has bugs." See +also <b><a href="#bitbang">bit bang</a></b>, <b><a href="#modebit">mode bit</a></b>.</p> + +<hr> +Node:<a name="bitbucket">bit bucket</a>, Next:<a rel="next" +href="#bitdecay">bit decay</a>, Previous:<a rel="previous" +href="#bitbashing">bit bashing</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bit bucket</b> n.</p> + +<p>[very common] 1. The universal data sink (originally, the +mythical receptacle used to catch bits when they fall off the end +of a register during a shift instruction). Discarded, lost, or +destroyed data is said to have `gone to the bit bucket'. On <b><a +href="#Unix">Unix</a></b>, often used for <b><a href="#slashdevslashnull">/dev/null</a></b>. Sometimes amplified as `the +Great Bit Bucket in the Sky'. 2. The place where all lost mail +and news messages eventually go. The selection is performed +according to <b><a href="#FinaglesLaw">Finagle's Law</a></b>; +important mail is much more likely to end up in the bit bucket +than junk mail, which has an almost 100% probability of getting +delivered. Routing to the bit bucket is automatically performed +by mail-transfer agents, news systems, and the lower layers of +the network. 3. The ideal location for all unwanted mail +responses: "Flames about this article to the bit bucket." Such a +request is guaranteed to overflow one's mailbox with flames. 4. +Excuse for all mail that has not been sent. "I mailed you those +figures last week; they must have landed in the bit bucket." +Compare <b><a href="#blackHole">black hole</a></b>.</p> + +<p>This term is used purely in jest. It is based on the fanciful +notion that bits are objects that are not destroyed but only +misplaced. This appears to have been a mutation of an earlier +term `bit box', about which the same legend was current; old-time +hackers also report that trainees used to be told that when the +CPU stored bits into memory it was actually pulling them `out of +the bit box'. See also <b><a href="#chadbox">chad +box</a></b>.</p> + +<p>Another variant of this legend has it that, as a consequence +of the `parity preservation law', the number of 1 bits that go to +the bit bucket must equal the number of 0 bits. Any imbalance +results in bits filling up the bit bucket. A qualified computer +technician can empty a full bit bucket as part of scheduled +maintenance.</p> + +<hr> +Node:<a name="bitdecay">bit decay</a>, Next:<a rel="next" +href="#bitrot">bit rot</a>, Previous:<a rel="previous" href="#bitbucket">bit bucket</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bit decay</b> n.</p> + +<p>See <b><a href="#bitrot">bit rot</a></b>. People with a +physics background tend to prefer this variant for the analogy +with particle decay. See also <b><a href="#computron">computron</a></b>, <b><a href="#quantumbogodynamics">quantum bogodynamics</a></b>.</p> + +<hr> +Node:<a name="bitrot">bit rot</a>, Next:<a rel="next" href="#bittwiddling">bit twiddling</a>, Previous:<a rel="previous" +href="#bitdecay">bit decay</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bit rot</b> n.</p> + +<p>[common] Also <b><a href="#bitdecay">bit decay</a></b>. +Hypothetical disease the existence of which has been deduced from +the observation that unused programs or features will often stop +working after sufficient time has passed, even if `nothing has +changed'. The theory explains that bits decay as if they were +radioactive. As time passes, the contents of a file or the code +in a program will become increasingly garbled.</p> + +<p>There actually are physical processes that produce such +effects (alpha particles generated by trace radionuclides in +ceramic chip packages, for example, can change the contents of a +computer memory unpredictably, and various kinds of subtle media +failures can corrupt files in mass storage), but they are quite +rare (and computers are built with error-detecting circuitry to +compensate for them). The notion long favored among hackers that +cosmic rays are among the causes of such events turns out to be a +myth; see the <b><a href="#cosmicrays">cosmic rays</a></b> +entry for details.</p> + +<p>The term <b><a href="#softwarerot">software rot</a></b> is +almost synonymous. Software rot is the effect, bit rot the +notional cause.</p> + +<hr> +Node:<a name="bittwiddling">bit twiddling</a>, Next:<a rel="next" href="#bit-pairedkeyboard">bit-paired keyboard</a>, +Previous:<a rel="previous" href="#bitrot">bit rot</a>, Up:<a +rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bit twiddling</b> n.</p> + +<p>[very common] 1. (pejorative) An exercise in tuning (see <b><a +href="#tune">tune</a></b>) in which incredible amounts of time +and effort go to produce little noticeable improvement, often +with the result that the code becomes incomprehensible. 2. +Aimless small modification to a program, esp. for some pointless +goal. 3. Approx. syn. for <b><a href="#bitbashing">bit +bashing</a></b>; esp. used for the act of frobbing the device +control register of a peripheral in an attempt to get it back to +a known state.</p> + +<hr> +Node:<a name="bit-pairedkeyboard">bit-paired keyboard</a>, +Next:<a rel="next" href="#bitblt">bitblt</a>, Previous:<a rel="previous" href="#bittwiddling">bit twiddling</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bit-paired keyboard</b> n.,obs.</p> + +<p>(alt. `bit-shift keyboard') A non-standard keyboard layout +that seems to have originated with the Teletype ASR-33 and +remained common for several years on early computer equipment. +The ASR-33 was a mechanical device (see <b><a href="#EOU">EOU</a></b>), so the only way to generate the character +codes from keystrokes was by some physical linkage. The design of +the ASR-33 assigned each character key a basic pattern that could +be modified by flipping bits if the SHIFT or the CTRL key was +pressed. In order to avoid making the thing even more of a kluge +than it already was, the design had to group characters that +shared the same basic bit pattern on one key.</p> + +<p>Looking at the ASCII chart, we find:</p> + +<pre> +high low bits +bits 0000 0001 0010 0011 0100 0101 0110 0111 1000 1001 + 010 ! " # $ % & ' ( ) + 011 0 1 2 3 4 5 6 7 8 9 +</pre> + +<p>This is why the characters !"#$%&'() appear where they do +on a Teletype (thankfully, they didn't use shift-0 for space). +The Teletype Model 33 was actually designed before ASCII existed, +and was originally intended to use a code that contained these +two rows:</p> + +<pre> + low bits +high 0000 0010 0100 0110 1000 1010 1100 1110 +bits 0001 0011 0101 0111 1001 1011 1101 1111 + 10 ) ! bel # $ % wru & * ( " : ? _ , . + 11 0 1 2 3 4 5 6 7 8 9 ' ; / - esc del +</pre> + +<p>The result would have been something closer to a normal +keyboard. But as it happened, Teletype had to use a lot of +persuasion just to keep ASCII, and the Model 33 keyboard, from +looking like this instead:</p> + +<pre> + ! " ? $ ' & - ( ) ; : * / , . + 0 1 2 3 4 5 6 7 8 9 + ~ < > × | +</pre> + +<p>Teletype's was <i>not</i> the weirdest variant of the <b><a +href="#QWERTY">QWERTY</a></b> layout widely seen, by the way; +that prize should probably go to one of several (differing) +arrangements on IBM's even clunkier 026 and 029 card punches.</p> + +<p>When electronic terminals became popular, in the early 1970s, +there was no agreement in the industry over how the keyboards +should be laid out. Some vendors opted to emulate the Teletype +keyboard, while others used the flexibility of electronic +circuitry to make their product look like an office typewriter. +Either choice was supported by the ANSI computer keyboard +standard, X4.14-1971, which referred to the alternatives as +`logical bit pairing' and `typewriter pairing'. These +alternatives became known as `bit-paired' and `typewriter-paired' +keyboards. To a hacker, the bit-paired keyboard seemed far more +logical -- and because most hackers in those days had never +learned to touch-type, there was little pressure from the +pioneering users to adapt keyboards to the typewriter +standard.</p> + +<p>The doom of the bit-paired keyboard was the large-scale +introduction of the computer terminal into the normal office +environment, where out-and-out technophobes were expected to use +the equipment. The `typewriter-paired' standard became universal, +X4.14 was superseded by X4.23-1982, `bit-paired' hardware was +quickly junked or relegated to dusty corners, and both terms +passed into disuse.</p> + +<p>However, in countries without a long history of touch typing, +the argument against the bit-paired keyboard layout was weak or +nonexistent. As a result, the standard Japanese keyboard, used on +PCs, Unix boxen etc. still has all of the !"#$%&'() +characters above the numbers in the ASR-33 layout.</p> + +<hr> +Node:<a name="bitblt">bitblt</a>, Next:<a rel="next" href="#BITNET">BITNET</a>, Previous:<a rel="previous" href="#bit-pairedkeyboard">bit-paired keyboard</a>, Up:<a rel="up" +href="#chap02">= B =</a> <br> + + +<p><b>bitblt</b> /bit'blit/ n.</p> + +<p>[from <b><a href="#BLT">BLT</a></b>, q.v.] 1. [common] Any of +a family of closely related algorithms for moving and copying +rectangles of bits between main and display memory on a +bit-mapped device, or between two areas of either main or display +memory (the requirement to do the <b><a href="#RightThing">Right Thing</a></b> in the case of overlapping +source and destination rectangles is what makes BitBlt tricky). +2. Synonym for <b><a href="#blit">blit</a></b> or <b><a href="#BLT">BLT</a></b>. Both uses are borderline techspeak.</p> + +<hr> +Node:<a name="BITNET">BITNET</a>, Next:<a rel="next" href="#bits">bits</a>, Previous:<a rel="previous" href="#bitblt">bitblt</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>BITNET</b> /bit'net/ n., obs.</p> + +<p>[acronym: Because It's Time NETwork] Everybody's least +favorite piece of the network (see <b><a href="#thenetwork">the network</a></b>) - until AOL happened. The +BITNET hosts were a collection of IBM dinosaurs and VAXen (the +latter with lobotomized comm hardware) that communicate using +80-character <b><a href="#EBCDIC">EBCDIC</a></b> card images (see +<b><a href="#eighty-columnmind">eighty-column mind</a></b>); +thus, they tend to mangle the headers and text of third-party +traffic from the rest of the ASCII/<b><a href="#RFC">RFC</a></b>-822 world with annoying regularity. BITNET was +also notorious as the apparent home of <b><a href="#B1FF">B1FF</a></b>. By 1995 it had, much to everyone's relief, +been obsolesced and absorbed into the Internet. Unfortunately, +around this time we also got AOL.</p> + +<hr> +Node:<a name="bits">bits</a>, Next:<a rel="next" href="#bittybox">bitty box</a>, Previous:<a rel="previous" href="#BITNET">BITNET</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>bits</b> pl.n.</p> + +<p>1. Information. Examples: "I need some bits about file +formats." ("I need to know about file formats.") Compare <b><a +href="#coredump">core dump</a></b>, sense 4. 2. +Machine-readable representation of a document, specifically as +contrasted with paper: "I have only a photocopy of the Jargon +File; does anyone know where I can get the bits?". See <b><a +href="#softcopy">softcopy</a></b>, <b><a href="#sourceofallgoodbits">source of all good +bits</a></b> See also <b><a href="#bit">bit</a></b>.</p> + +<hr> +Node:<a name="bittybox">bitty box</a>, Next:<a rel="next" +href="#bixen">bixen</a>, Previous:<a rel="previous" href="#bits">bits</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>bitty box</b> /bit'ee boks/ n.</p> + +<p>1. A computer sufficiently small, primitive, or incapable as +to cause a hacker acute claustrophobia at the thought of +developing software on or for it. Especially used of small, +obsolescent, single-tasking-only personal machines such as the +Atari 800, Osborne, Sinclair, VIC-20, TRS-80, or IBM PC. 2. +[Pejorative] More generally, the opposite of `real computer' (see +<b><a href="#Getarealcomputer">Get a real +computer!</a></b>). See also <b><a href="#mess-dos">mess-dos</a></b>, <b><a href="#toaster">toaster</a></b>, and <b><a href="#toy">toy</a></b>.</p> + +<hr> +Node:<a name="bixen">bixen</a>, Next:<a rel="next" href="#bixie">bixie</a>, Previous:<a rel="previous" href="#bittybox">bitty box</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bixen</b> pl.n.</p> + +<p>Users of BIX (the BIX Information eXchange, formerly the Byte +Information eXchange). Parallels other plurals like boxen, <b><a +href="#VAXen">VAXen</a></b>, oxen.</p> + +<hr> +Node:<a name="bixie">bixie</a>, Next:<a rel="next" href="#blackart">black art</a>, Previous:<a rel="previous" href="#bixen">bixen</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>bixie</b> /bik'see/ n.</p> + +<p>Variant <b><a href="#emoticon">emoticon</a></b>s used on BIX +(the BIX Information eXchange). The most common (<b><a href="#smiley">smiley</a></b>) bixie is <@_@>, representing two +cartoon eyes and a mouth. These were originally invented in an SF +fanzine called APA-L and imported to BIX by one of the earliest +users.</p> + +<hr> +Node:<a name="blackart">black art</a>, Next:<a rel="next" +href="#blackHole">black hole</a>, Previous:<a rel="previous" +href="#bixie">bixie</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>black art</b> n.</p> + +<p>[common] A collection of arcane, unpublished, and (by +implication) mostly ad-hoc techniques developed for a particular +application or systems area (compare <b><a href="#blackmagic">black magic</a></b>). VLSI design and compiler +code optimization were (in their beginnings) considered classic +examples of black art; as theory developed they became <b><a +href="#deepmagic">deep magic</a></b>, and once standard +textbooks had been written, became merely <b><a href="#heavywizardry">heavy wizardry</a></b>. The huge +proliferation of formal and informal channels for spreading +around new computer-related technologies during the last twenty +years has made both the term `black art' and what it describes +less common than formerly. See also <b><a href="#voodooprogramming">voodoo programming</a></b>.</p> + +<hr> +Node:<a name="blackHole">black hole</a>, Next:<a rel="next" +href="#blackmagic">black magic</a>, Previous:<a rel="previous" +href="#blackart">black art</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>black hole</b> n.,vt.</p> + +<p>[common] What data (a piece of email or netnews, or a stream +of TCP/IP packets) has fallen into if it disappears mysteriously +between its origin and destination sites (that is, without +returning a <b><a href="#bouncemessage">bounce +message</a></b>). "I think there's a black hole at +<i>foovax</i>!" conveys suspicion that site <i>foovax</i> has +been dropping a lot of stuff on the floor lately (see <b><a href="#droponthefloor">drop on the floor</a></b>). The +implied metaphor of email as interstellar travel is interesting +in itself. Readily verbed as `blackhole': "That router is +blackholing IDP packets." Compare <b><a href="#bitbucket">bit +bucket</a></b> and see <b><a href="#RBL">RBL</a></b>.</p> + +<hr> +Node:<a name="blackmagic">black magic</a>, Next:<a rel="next" +href="#BlackScreenofDeath">Black Screen of Death</a>, +Previous:<a rel="previous" href="#blackHole">black hole</a>, +Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>black magic</b> n.</p> + +<p>[common] A technique that works, though nobody really +understands why. More obscure than <b><a href="#voodooprogramming">voodoo programming</a></b>, which may be +done by cookbook. Compare also <b><a href="#blackart">black +art</a></b>, <b><a href="#deepmagic">deep magic</a></b>, and +<b><a href="#magicnumber">magic number</a></b> (sense 2).</p> + +<hr> +Node:<a name="BlackScreenofDeath">Black Screen of +Death</a>, Next:<a rel="next" href="#BlackThursday">Black +Thursday</a>, Previous:<a rel="previous" href="#blackmagic">black magic</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>Black Screen of Death</b> n.</p> + +<p>[prob. related to the Floating Head of Death in a famous "Far +Side" cartoon.] A failure mode of <b><a href="#MicroslothWindows">Microsloth Windows</a></b>. On an attempt +to launch a DOS box, a networked Windows system not uncommonly +blanks the screen and locks up the PC so hard that it requires a +cold <b><a href="#boot">boot</a></b> to recover. This unhappy +phenomenon is known as The Black Screen of Death. See also <b><a +href="#BlueScreenofDeath">Blue Screen of Death</a></b>, +which has become rather more common.</p> + +<hr> +Node:<a name="BlackThursday">Black Thursday</a>, Next:<a rel="next" href="#blammo">blammo</a>, Previous:<a rel="previous" +href="#BlackScreenofDeath">Black Screen of Death</a>, +Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>Black Thursday</b> n.</p> + +<p>February 8th, 1996 - the day of the signing into law of the +<b><a href="#CDA">CDA</a></b>, so called by analogy with the +catastrophic "Black Friday" in 1929 that began the Great +Depression.</p> + +<hr> +Node:<a name="blammo">blammo</a>, Next:<a rel="next" href="#blargh">blargh</a>, Previous:<a rel="previous" href="#BlackThursday">Black Thursday</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>blammo</b> v.</p> + +<p>[Oxford Brookes University and alumni, UK] To forcibly remove +someone from any interactive system, especially talker systems. +The operators, who may remain hidden, may `blammo' a user who is +misbehaving. Very similar to MIT <b><a href="#gun">gun</a></b>; +in fact, the `blammo-gun' is a notional device used to `blammo' +someone. While in actual fact the only incarnation of the +blammo-gun is the command used to forcibly eject a user, +operators speak of different levels of blammo-gun fire; e.g., a +blammo-gun to `stun' will temporarily remove someone, but a +blammo-gun set to `maim' will stop someone coming back on for a +while.</p> + +<hr> +Node:<a name="blargh">blargh</a>, Next:<a rel="next" href="#blast">blast</a>, Previous:<a rel="previous" href="#blammo">blammo</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>blargh</b> /blarg/ n.</p> + +<p>[MIT; now common] The opposite of <b><a href="#ping">ping</a></b>, sense 5; an exclamation indicating that one +has absorbed or is emitting a quantum of unhappiness. Less common +than <b><a href="#ping">ping</a></b>.</p> + +<hr> +Node:<a name="blast">blast</a>, Next:<a rel="next" href="#blat">blat</a>, Previous:<a rel="previous" href="#blargh">blargh</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>blast</b> 1. v.,n.</p> + +<p>Synonym for <b><a href="#BLT">BLT</a></b>, used esp. for large +data sends over a network or comm line. Opposite of <b><a href="#snarf">snarf</a></b>. Usage: uncommon. The variant `blat' has +been reported. 2. vt. [HP/Apollo] Synonymous with <b><a href="#nuke">nuke</a></b> (sense 3). Sometimes the message +<code>Unable to kill all processes. Blast them (y/n)?</code> +would appear in the command window upon logout.</p> + +<hr> +Node:<a name="blat">blat</a>, Next:<a rel="next" href="#bletch">bletch</a>, Previous:<a rel="previous" href="#blast">blast</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>blat</b> n.</p> + +<p>1. Syn. <b><a href="#blast">blast</a></b>, sense 1. 2. See +<b><a href="#thud">thud</a></b>.</p> + +<hr> +Node:<a name="bletch">bletch</a>, Next:<a rel="next" href="#bletcherous">bletcherous</a>, Previous:<a rel="previous" href="#blat">blat</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>bletch</b> /blech/ interj.</p> + +<p>[very common; from Yiddish/German `brechen', to vomit, poss. +via comic-strip exclamation `blech'] Term of disgust. Often used +in "Ugh, bletch". Compare <b><a href="#barf">barf</a></b>.</p> + +<hr> +Node:<a name="bletcherous">bletcherous</a>, Next:<a rel="next" +href="#blink">blink</a>, Previous:<a rel="previous" href="#bletch">bletch</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>bletcherous</b> /blech'*-r*s/ adj.</p> + +<p>Disgusting in design or function; esthetically unappealing. +This word is seldom used of people. "This keyboard is +bletcherous!" (Perhaps the keys don't work very well, or are +misplaced.) See <b><a href="#losing">losing</a></b>, <b><a href="#cretinous">cretinous</a></b>, <b><a href="#bagbiting">bagbiting</a></b>, <b><a href="#bogus">bogus</a></b>, and <b><a href="#random">random</a></b>. +The term <b><a href="#bletcherous">bletcherous</a></b> applies to +the esthetics of the thing so described; similarly for <b><a +href="#cretinous">cretinous</a></b>. By contrast, something that +is `losing' or `bagbiting' may be failing to meet objective +criteria. See also <b><a href="#bogus">bogus</a></b> and <b><a +href="#random">random</a></b>, which have richer and wider shades +of meaning than any of the above.</p> + +<hr> +Node:<a name="blink">blink</a>, Next:<a rel="next" href="#blinkenlights">blinkenlights</a>, Previous:<a rel="previous" +href="#bletcherous">bletcherous</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>blink</b> vi.,n.</p> + +<p>To use a navigator or off-line message reader to minimize time +spent on-line to a commercial network service (a necessity in +many places outside the U.S. where the telecoms monopolies charge +per-minute for local calls). This term attained wide use in the +UK, but is rare or unknown in the US.</p> + +<hr> +Node:<a name="blinkenlights">blinkenlights</a>, Next:<a rel="next" href="#blit">blit</a>, Previous:<a rel="previous" href="#blink">blink</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>blinkenlights</b> /blink'*n-li:tz/ n.</p> + +<p>[common] Front-panel diagnostic lights on a computer, esp. a +<b><a href="#dinosaur">dinosaur</a></b>. Now that dinosaurs are +rare, this term usually refers to status lights on a modem, +network hub, or the like.</p> + +<p>This term derives from the last word of the famous +blackletter-Gothic sign in mangled pseudo-German that once graced +about half the computer rooms in the English-speaking world. One +version ran in its entirety as follows:<br> +</p> + +<p align="center">ACHTUNG! ALLES LOOKENSPEEPERS!</p> + +<blockquote>Das computermachine ist nicht fuer gefingerpoken und +mittengrabben. Ist easy schnappen der springenwerk, blowenfusen +und poppencorken mit spitzensparken. Ist nicht fuer gewerken bei +das dumpkopfen. Das rubbernecken sichtseeren keepen das +cotten-pickenen hans in das pockets muss; relaxen und watchen das +blinkenlichten.</blockquote> + +<br> +<p>This silliness dates back at least as far as 1959 at Stanford +University and had already gone international by the early 1960s, +when it was reported at London University's ATLAS computing site. +There are several variants of it in circulation, some of which +actually do end with the word `blinkenlights'.</p> + +<p>In an amusing example of turnabout-is-fair-play, German +hackers have developed their own versions of the blinkenlights +poster in fractured English, one of which is reproduced here:<br> +</p> + +<p align="center">ATTENTION</p> + +<blockquote>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.</blockquote> + +<br> +<p>See also <b><a href="#geef">geef</a></b>.</p> + +<p>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.</p> + +<p>Finally, a version updated for the Internet has been seen on +<i>news.admin.net-abuse.email</i>:<br> +</p> + +<p align="center">ACHTUNG! ALLES LOOKENSPEEPERS!</p> + +<blockquote>Das Internet is nicht fuer gefingerclicken und +giffengrabben. Ist easy droppenpacket der routers und overloaden +der backbone mit der spammen und der me-tooen. Ist nicht fuer +gewerken bei das dumpkopfen. Das mausklicken sichtseeren keepen +das bandwit-spewin hans in das pockets muss; relaxen und watchen +das cursorblinken.</blockquote> + +<p>This newest version partly reflects reports that the word +`blinkenlights' is (in 1999) undergoing something of a revival in +usage, but applied to networking equipment. The transmit and +receive lights on routers, activity lights on switches and hubs, +and other network equipment often blink in visually pleasing and +seemingly coordinated ways. Although this is different in some +ways from register readings, a tall stack of Cisco equipment or a +19-inch rack of ISDN terminals can provoke a similar feeling of +hypnotic awe, especially in a darkened network operations center +or server room.</p> + +<hr> +Node:<a name="blit">blit</a>, Next:<a rel="next" href="#blitter">blitter</a>, Previous:<a rel="previous" href="#blinkenlights">blinkenlights</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>blit</b> /blit/ vt.</p> + +<p>1. [common] 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 <b><a href="#bitblt">bitblt</a></b>, <b><a href="#BLT">BLT</a></b>, <b><a href="#dd">dd</a></b>, <b><a href="#cat">cat</a></b>, <b><a href="#blast">blast</a></b>, <b><a +href="#snarf">snarf</a></b>. More generally, to perform some +operation (such as toggling) on a large array of bits while +moving them. 2. [historical, rare] 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.)</p> + +<hr> +Node:<a name="blitter">blitter</a>, Next:<a rel="next" href="#blivet">blivet</a>, Previous:<a rel="previous" href="#blit">blit</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>blitter</b> /blit'r/ n.</p> + +<p>[common] A special-purpose chip or hardware system built to +perform <b><a href="#blit">blit</a></b> operations, esp. used for +fast implementation of bit-mapped graphics. The Commodore Amiga +and a few other micros have these, but since 1990 the trend has +been away from them (however, see <b><a href="#cycleofreincarnation">cycle of reincarnation</a></b>). +Syn. <b><a href="#rasterblaster">raster blaster</a></b>.</p> + +<hr> +Node:<a name="blivet">blivet</a>, Next:<a rel="next" href="#bloatware">bloatware</a>, Previous:<a rel="previous" href="#blitter">blitter</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>blivet</b> /bliv'*t/ n.</p> + +<p>[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).</p> + +<p>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 <b><a href="#frob">frob</a></b>). 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.</p> + +<hr> +Node:<a name="bloatware">bloatware</a>, Next:<a rel="next" href="#BLOB">BLOB</a>, Previous:<a rel="previous" href="#blivet">blivet</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>bloatware</b> n.</p> + +<p>[common] Software that provides minimal functionality while +requiring a disproportionate amount of diskspace and memory. +Especially used for application and OS upgrades. This term is +very common in the Windows/NT world. So is its cause.</p> + +<hr> +Node:<a name="BLOB">BLOB</a>, Next:<a rel="next" href="#block">block</a>, Previous:<a rel="previous" href="#bloatware">bloatware</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>BLOB</b></p> + +<p>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 <b><a href="#mailbomb">mailbomb</a></b> 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."</p> + +<hr> +Node:<a name="block">block</a>, Next:<a rel="next" href="#blocktransfercomputations">block transfer +computations</a>, Previous:<a rel="previous" href="#BLOB">BLOB</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>block</b> v.</p> + +<p>[common; 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 <b><a href="#busy-wait">busy-wait</a></b>. 2. `block on' vt. To block, +waiting for (something). "Lunch is blocked on Phil's +arrival."</p> + +<hr> +Node:<a name="blocktransfercomputations">block transfer +computations</a>, Next:<a rel="next" href="#BloggsFamily">Bloggs Family</a>, Previous:<a rel="previous" +href="#block">block</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>block transfer computations</b> n.</p> + +<p>[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.)</p> + +<hr> +Node:<a name="BloggsFamily">Bloggs Family</a>, Next:<a rel="next" href="#blowanEPROM">blow an EPROM</a>, Previous:<a +rel="previous" href="#blocktransfercomputations">block +transfer computations</a>, Up:<a rel="up" href="#chap02">= +B =</a> <br> + + +<p><b>Bloggs Family</b> n.</p> + +<p>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 +old <b><a href="#DEC">DEC</a></b> Telephone Directory. Compare +<b><a href="#DrFredMbogo">Dr. Fred Mbogo</a></b>; <b><a +href="#JRandomHacker">J. Random Hacker</a></b>; <b><a +href="#FredFoobar">Fred Foobar</a></b>.</p> + +<hr> +Node:<a name="blowanEPROM">blow an EPROM</a>, Next:<a rel="next" href="#blowaway">blow away</a>, Previous:<a rel="previous" href="#BloggsFamily">Bloggs Family</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>blow an EPROM</b> /bloh *n ee'prom/ v.</p> + +<p>(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.</p> + +<hr> +Node:<a name="blowaway">blow away</a>, Next:<a rel="next" +href="#blowout">blow out</a>, Previous:<a rel="previous" href="#blowanEPROM">blow an EPROM</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>blow away</b> vt.</p> + +<p>To remove (files and directories) from permanent storage, +generally by accident. "He reformatted the wrong partition and +blew away last night's netnews." Oppose <b><a href="#nuke">nuke</a></b>.</p> + +<hr> +Node:<a name="blowout">blow out</a>, Next:<a rel="next" href="#blowpast">blow past</a>, Previous:<a rel="previous" href="#blowaway">blow away</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>blow out</b> vi.</p> + +<p>[prob. from mining and tunneling jargon] Of software, to fail +spectacularly; almost as serious as <b><a href="#crashandburn">crash and burn</a></b>. See <b><a href="#blowpast">blow past</a></b>, <b><a href="#blowup">blow +up</a></b>, <b><a href="#diehorribly">die +horribly</a></b>.</p> + +<hr> +Node:<a name="blowpast">blow past</a>, Next:<a rel="next" +href="#blowup">blow up</a>, Previous:<a rel="previous" href="#blowout">blow out</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>blow past</b> vt.</p> + +<p>To <b><a href="#blowout">blow out</a></b> despite a +safeguard. "The server blew past the 5K reserve buffer."</p> + +<hr> +Node:<a name="blowup">blow up</a>, Next:<a rel="next" href="#BLT">BLT</a>, Previous:<a rel="previous" href="#blowpast">blow past</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>blow up</b> vi.</p> + +<p>1. [scientific computation] To become unstable. Suggests that +the computation is diverging so rapidly that it will soon +overflow or at least go <b><a href="#nonlinear">nonlinear</a></b>. 2. Syn. <b><a href="#blowout">blow out</a></b>.</p> + +<hr> +Node:<a name="BLT">BLT</a>, Next:<a rel="next" href="#BlueBook">Blue Book</a>, Previous:<a rel="previous" href="#blowup">blow up</a>, Up:<a rel="up" href="#chap02">= +B =</a> <br> + + +<p><b>BLT</b> /B-L-T/, /bl*t/ or (rarely) /belt/ n.,vt.</p> + +<p>Synonym for <b><a href="#blit">blit</a></b>. This is the +original form of <b><a href="#blit">blit</a></b> and the ancestor +of <b><a href="#bitblt">bitblt</a></b>. 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 <b><a href="#PDP-10">PDP-10</a></b> BLock Transfer instruction from which +<b><a href="#BLT">BLT</a></b> derives; nowadays, the assembler +mnemonic <b><a href="#BLT">BLT</a></b> almost always means +`Branch if Less Than zero'.</p> + +<hr> +Node:<a name="BlueBook">Blue Book</a>, Next:<a rel="next" +href="#bluebox">blue box</a>, Previous:<a rel="previous" href="#BLT">BLT</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>Blue Book</b> n.</p> + +<p>1. Informal name for one of the four standard references on +the page-layout and graphics-control language <b><a href="#PostScript">PostScript</a></b> ("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 <b><a href="#GreenBook">Green +Book</a></b>, the <b><a href="#RedBook">Red Book</a></b>, and +the <b><a href="#WhiteBook">White Book</a></b> (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 <b><a href="#booktitles">book titles</a></b>.</p> + +<hr> +Node:<a name="bluebox">blue box</a>, Next:<a rel="next" href="#BlueGlue">Blue Glue</a>, Previous:<a rel="previous" href="#BlueBook">Blue Book</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>blue box</b></p> + +<p>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 <b><a href="#phreaker">phreaker</a></b>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 <b><a href="#IBM">IBM</a></b> machine, especially a large +(non-PC) one.</p> + +<hr> +Node:<a name="BlueGlue">Blue Glue</a>, Next:<a rel="next" +href="#bluegoo">blue goo</a>, Previous:<a rel="previous" href="#bluebox">blue box</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>Blue Glue</b> n.</p> + +<p>[IBM] IBM's SNA (Systems Network Architecture), an incredibly +<b><a href="#losing">losing</a></b> and <b><a href="#bletcherous">bletcherous</a></b> 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 <b><a href="#fearandloathing">fear and +loathing</a></b>. 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 <b><a +href="#dinosaurpen">dinosaur pen</a></b>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'.</p> + +<hr> +Node:<a name="bluegoo">blue goo</a>, Next:<a rel="next" href="#BlueScreenofDeath">Blue Screen of Death</a>, +Previous:<a rel="previous" href="#BlueGlue">Blue Glue</a>, +Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>blue goo</b> n.</p> + +<p>Term for `police' <b><a href="#nanobot">nanobot</a></b>s +intended to prevent <b><a href="#graygoo">gray goo</a></b>, +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 <b><a +href="#nanotechnology">nanotechnology</a></b>.</p> + +<hr> +Node:<a name="BlueScreenofDeath">Blue Screen of +Death</a>, Next:<a rel="next" href="#bluewire">blue wire</a>, +Previous:<a rel="previous" href="#bluegoo">blue goo</a>, Up:<a +rel="up" href="#chap02">= B =</a> <br> + + +<p><b>Blue Screen of Death</b> n.</p> + +<p>[common] This term is closely related to the older <b><a href="#BlackScreenofDeath">Black Screen of Death</a></b> but +much more common (many non-hackers have picked it up). Due to the +extreme fragility and bugginess of Microsoft Windows misbehaving +applications can readily crash the OS (and the OS sometimes +crashes itself spontaneously). The Blue Screen of Death, +sometimes decorated with hex error codes, is what you get when +this happens. (Commonly abbreviated <b><a href="#BSOD">BSOD</a></b>.)</p> + +<p>The following entry from the Salon +Haiku Contest, seems to have predated popular use of the +term:</p> + +<pre> + Windows NT crashed. + I am the Blue Screen of Death + No one hears your screams. +</pre> + +<hr> +Node:<a name="bluewire">blue wire</a>, Next:<a rel="next" +href="#blurgle">blurgle</a>, Previous:<a rel="previous" href="#BlueScreenofDeath">Blue Screen of Death</a>, Up:<a +rel="up" href="#chap02">= B =</a> <br> + + +<p><b>blue wire</b> n.</p> + +<p>[IBM] Patch wires (esp. 30 AWG gauge) added to circuit boards +at the factory to correct design or fabrication problems. Blue +wire is not necessarily blue, the term describes function rather +than color. These may be necessary if there hasn't been time to +design and qualify another board version. In Great Britain this +can be `bodge wire', after mainstreanm slang `bodge' for a clumsy +improvisation or sloppy job of work. Compare <b><a href="#purplewire">purple wire</a></b>, <b><a href="#redwire">red wire</a></b>, <b><a href="#yellowwire">yellow wire</a></b>, <b><a href="#pinkwire">pink wire</a></b>.</p> + +<hr> +Node:<a name="blurgle">blurgle</a>, Next:<a rel="next" href="#BNF">BNF</a>, Previous:<a rel="previous" href="#bluewire">blue wire</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>blurgle</b> /bler'gl/ n.</p> + +<p>[UK] Spoken <b><a href="#metasyntacticvariable">metasyntactic variable</a></b>, 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 <b><a href="#mumble">mumble</a></b>, +sense 7.</p> + +<hr> +Node:<a name="BNF">BNF</a>, Next:<a rel="next" href="#boa">boa</a>, Previous:<a rel="previous" href="#blurgle">blurgle</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>BNF</b> /B-N-F/ n.</p> + +<p>1. [techspeak] Acronym for `Backus Normal Form' (later +retronymed to `Backus-Naur Form' because BNF was not in fact a +normal 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:</p> + +<pre> + <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> +</pre> + +<p>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 +<b><a href="#parse">parse</a></b>. 2. Any of a number of variants +and extensions of BNF proper, possibly containing some or all of +the <b><a href="#regexp">regexp</a></b> wildcards such as +<code>*</code> or <code>+</code>. In fact the example above isn't +the pure form invented for the Algol-60 report; it uses +<code>[]</code>, which was introduced a few years later in IBM's +PL/I definition but is now universally recognized. 3. In <b><a +href="#science-fictionfandom">science-fiction fandom</a></b>, +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.</p> + +<hr> +Node:<a name="boa">boa</a>, Next:<a rel="next" href="#board">board</a>, Previous:<a rel="previous" href="#BNF">BNF</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>boa</b> [IBM] n.</p> + +<p>Any one of the fat cables that lurk under the floor in a <b><a +href="#dinosaurpen">dinosaur pen</a></b>. 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'.</p> + +<hr> +Node:<a name="board">board</a>, Next:<a rel="next" href="#boatanchor">boat anchor</a>, Previous:<a rel="previous" +href="#boa">boa</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>board</b> n.</p> + +<p>1. In-context synonym for <b><a href="#bboard">bboard</a></b>; +sometimes used even for Usenet newsgroups (but see usage note +under <b><a href="#bboard">bboard</a></b>, sense 1). 2. An +electronic circuit board.</p> + +<hr> +Node:<a name="boatanchor">boat anchor</a>, Next:<a rel="next" +href="#bob">bob</a>, Previous:<a rel="previous" href="#board">board</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>boat anchor</b> n.</p> + +<p>[common; from ham radio] 1. Like <b><a href="#doorstop">doorstop</a></b> 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.</p> + +<hr> +Node:<a name="bob">bob</a>, Next:<a rel="next" href="#bodysurfcode">bodysurf code</a>, Previous:<a rel="previous" +href="#boatanchor">boat anchor</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + +<p><b>bob</b> n.</p> + +<p> +At Demon Internet, all tech support personnel are called "Bob". (Female support +personnel have an option on "Bobette"). This has nothing to do with Bob the +divine drilling-equipment salesman of the <b><a +href="#ChurchoftheSubGenius">Church of the SubGenius</a></b>. Nor is +it acronymized from "Brother Of <b><a href="#BOFH">BOFH</a></b>", though all +parties agree it could have been. Rather, it was triggered by an unusually +large draft of new tech-support people in 1995. It was observed that there +would be much duplication of names. To ease the confusion, it was decided that +all support techs would henceforth be known as "Bob", and identity badges were +created labelled "Bob 1" and "Bob 2". ("No, we never got any further" reports a +witness). +</p> + +<p>The reason for "Bob" rather than anything else is due to a +<b><a href="#luser">luser</a></b> calling and asking to speak to +"Bob", despite the fact that no "Bob" was currently working for +Tech Support. Since we all know "the customer is always right", +it was decided that there had to be at least one "Bob" on duty at +all times, just in case.</p> + +<p>This sillyness inexorably snowballed. Shift leaders and +managers began to refer to their groups of "bobs". Whole ranks of +support machines were set up (and still exist in the DNS as of +1999) as bob1 through bobN. Then came +<i>alt.tech-support.recovery</i>, and it was filled with Demon +support personnel. They all referred to themselves, and to +others, as `bob', and after a while it caught on. There is now a +Bob Code describing the Bob nature.</p> + +<hr> +Node:<a name="bodysurfcode">bodysurf code</a>, Next:<a rel="next" href="#BOF">BOF</a>, Previous:<a rel="previous" href="#bob">bob</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>bodysurf code</b> n.</p> + +<p>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.</p> + +<hr> +Node:<a name="BOF">BOF</a>, Next:<a rel="next" href="#BOFH">BOFH</a>, Previous:<a rel="previous" href="#bodysurfcode">bodysurf code</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>BOF</b> /B-O-F/ or /bof/ n.</p> + +<p>1. [common] 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. 2. Acronym, `Beginning of File'.</p> + +<hr> +Node:<a name="BOFH">BOFH</a>, Next:<a rel="next" href="#bogo-sort">bogo-sort</a>, Previous:<a rel="previous" href="#BOF">BOF</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>BOFH</b> // n.</p> + +<p>[common] Acronym, Bastard Operator From Hell. A system +administrator with absolutely no tolerance for <b><a href="#luser">luser</a></b>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 +<i>alt.sysadmin.recovery</i>, although there has also been +created a top-level newsgroup hierarchy (<i>bofh.*</i>) of their +own.</p> + +<p>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. BOFHs and BOFH wannabes hang out on <b><a href="#scarydevilmonastery">scary devil monastery</a></b> and +wield <b><a href="#LART">LART</a></b>s.</p> + +<hr> +Node:<a name="bogo-sort">bogo-sort</a>, Next:<a rel="next" href="#bogometer">bogometer</a>, Previous:<a rel="previous" href="#BOFH">BOFH</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>bogo-sort</b> /boh`goh-sort'/ n.</p> + +<p>(var. `stupid-sort') The archetypical perversely awful +algorithm (as opposed to <b><a href="#bubblesort">bubble +sort</a></b>, which is merely the generic <i>bad</i> +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." Esp. appropriate for algorithms with factorial or +super-exponential running time in the average case and +probabilistically infinite worst-case running time. Compare <b><a +href="#bogus">bogus</a></b>, <b><a href="#bruteforce">brute +force</a></b>, <b><a href="#lasherism">lasherism</a></b>.</p> + +<p>A spectacular variant of bogo-sort has been proposed which has +the interesting property that, if the Many Worlds interpretation +of quantum mechanics is true, it can sort an arbitrarily large +array in constant time. (In the Many-Worlds model, the result of +any quantum action is to split the universe-before into a sheaf +of universes-after, one for each possible way the state vector +can collapse; in any one of the universes-after the result +appears random.) The steps are: 1. Permute the array randomly +using a quantum process, 2. If the array is not sorted, destroy +the universe. Implementation of step 2 is left as an exercise for +the reader.</p> + +<hr> +Node:<a name="bogometer">bogometer</a>, Next:<a rel="next" href="#BogoMIPS">BogoMIPS</a>, Previous:<a rel="previous" href="#bogo-sort">bogo-sort</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bogometer</b> /boh-gom'-*t-er/ n.</p> + +<p>A notional instrument for measuring <b><a href="#bogosity">bogosity</a></b>. Compare the <b><a href="#Troll-O-Meter">Troll-O-Meter</a></b> and the `wankometer' +described in the <b><a href="#wank">wank</a></b> entry; see also +<b><a href="#bogus">bogus</a></b>.</p> + +<hr> +Node:<a name="BogoMIPS">BogoMIPS</a>, Next:<a rel="next" href="#bogon">bogon</a>, Previous:<a rel="previous" href="#bogometer">bogometer</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>BogoMIPS</b> /bo'go-mips/ n.</p> + +<p>The number of million times a second a processor can do +absolutely nothing. The <b><a href="#Linux">Linux</a></b> OS +measures BogoMIPS at startup in order to calibrate some soft +timing loops that will be used later on; details at the BogoMIPS mini-HOWTO. The +name Linus chose, of course, is an ironic comment on the +uselessness of all <i>other</i> <b><a href="#MIPS">MIPS</a></b> +figures.</p> + +<hr> +Node:<a name="bogon">bogon</a>, Next:<a rel="next" href="#bogonfilter">bogon filter</a>, Previous:<a rel="previous" +href="#BogoMIPS">BogoMIPS</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bogon</b> /boh'gon/ n.</p> + +<p>[very common; by analogy with proton/electron/neutron, but +doubtless reinforced after 1980 by the similarity to Douglas +Adams's `Vogons'; see the <b><a href="#Bibliography">Bibliography</a></b> in Appendix C and note that +Arthur Dent actually mispronounces `Vogons' as `Bogons' at one +point] 1. The elementary particle of bogosity (see <b><a href="#quantumbogodynamics">quantum bogodynamics</a></b>). 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 <b><a href="#bogosity">bogosity</a></b>, <b><a href="#bogus">bogus</a></b>; +compare <b><a href="#psyton">psyton</a></b>, <b><a href="#fatelectrons">fat electrons</a></b>, <b><a href="#magicsmoke">magic smoke</a></b>.</p> + +<p>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 <b><a href="#randomness">randomness</a></b>, 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 <b><a +href="#magicsmoke">magic smoke</a></b>.</p> + +<hr> +Node:<a name="bogonfilter">bogon filter</a>, Next:<a rel="next" href="#bogonflux">bogon flux</a>, Previous:<a rel="previous" href="#bogon">bogon</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bogon filter</b> /boh'gon fil'tr/ n.</p> + +<p>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 <b><a href="#bogosity">bogosity</a></b>, <b><a href="#bogus">bogus</a></b>.</p> + +<hr> +Node:<a name="bogonflux">bogon flux</a>, Next:<a rel="next" +href="#bogosity">bogosity</a>, Previous:<a rel="previous" href="#bogonfilter">bogon filter</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bogon flux</b> /boh'gon fluhks/ n.</p> + +<p>A measure of a supposed field of <b><a href="#bogosity">bogosity</a></b> emitted by a speaker, measured by a +<b><a href="#bogometer">bogometer</a></b>; as a speaker starts to +wander into increasing bogosity a listener might say "Warning, +warning, bogon flux is rising". See <b><a href="#quantumbogodynamics">quantum bogodynamics</a></b>.</p> + +<hr> +Node:<a name="bogosity">bogosity</a>, Next:<a rel="next" href="#bogotify">bogotify</a>, Previous:<a rel="previous" href="#bogonflux">bogon flux</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bogosity</b> /boh-go's*-tee/ n.</p> + +<p>1. [orig. CMU, now very common] The degree to which something +is <b><a href="#bogus">bogus</a></b>. Bogosity is measured with a +<b><a href="#bogometer">bogometer</a></b>; 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 <b><a href="#microLenat">microLenat</a></b>. 2. +The potential field generated by a <b><a href="#bogonflux">bogon flux</a></b>; see <b><a href="#quantumbogodynamics">quantum bogodynamics</a></b>. See also +<b><a href="#bogonflux">bogon flux</a></b>, <b><a href="#bogonfilter">bogon filter</a></b>, <b><a href="#bogus">bogus</a></b>.</p> + +<hr> +Node:<a name="bogotify">bogotify</a>, Next:<a rel="next" href="#bogueout">bogue out</a>, Previous:<a rel="previous" href="#bogosity">bogosity</a>, Up:<a rel="up" href="#chap02">= +B =</a> <br> + + +<p><b>bogotify</b> /boh-go't*-fi:/ vt.</p> + +<p>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 <b><a href="#bogosity">bogosity</a></b>, <b><a href="#bogus">bogus</a></b>.</p> + +<hr> +Node:<a name="bogueout">bogue out</a>, Next:<a rel="next" +href="#bogus">bogus</a>, Previous:<a rel="previous" href="#bogotify">bogotify</a>, Up:<a rel="up" href="#chap02">= +B =</a> <br> + + +<p><b>bogue out</b> /bohg owt/ vi.</p> + +<p>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 <b><a href="#flame">flame</a></b> afterwards." See also <b><a href="#bogosity">bogosity</a></b>, <b><a href="#bogus">bogus</a></b>.</p> + +<hr> +Node:<a name="bogus">bogus</a>, Next:<a rel="next" href="#Bohrbug">Bohr bug</a>, Previous:<a rel="previous" href="#bogueout">bogue out</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bogus</b> adj.</p> + +<p>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."</p> + +<p>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 <b><a href="#random">random</a></b> -- mostly the negative ones.)</p> + +<p>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 there about 1975-76. These coinages spread into +hackerdom from CMU and MIT. Most of them remained wordplay +objects rather than actual vocabulary items or live metaphors. +Examples: `amboguous' (having multiple bogus interpretations); +`bogotissimo' (in a gloriously bogus manner); `bogotophile' (one +who is pathologically fascinated by the bogus); `paleobogology' +(the study of primeval bogosity).</p> + +<p>Some bogowords, however, obtained sufficient live currency to +be listed elsewhere in this lexicon; see <b><a href="#bogometer">bogometer</a></b>, <b><a href="#bogon">bogon</a></b>, <b><a href="#bogotify">bogotify</a></b>, +and <b><a href="#quantumbogodynamics">quantum +bogodynamics</a></b> and the related but unlisted <b><a href="#DrFredMbogo">Dr. Fred Mbogo</a></b>.</p> + +<p>By the early 1980s `bogus' was also current in something like +hacker usage 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".</p> + +<hr> +Node:<a name="Bohrbug">Bohr bug</a>, Next:<a rel="next" href="#boink">boink</a>, Previous:<a rel="previous" href="#bogus">bogus</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>Bohr bug</b> /bohr buhg/ n.</p> + +<p>[from quantum physics] A repeatable <b><a href="#bug">bug</a></b>; one that manifests reliably under a possibly +unknown but well-defined set of conditions. Antonym of <b><a +href="#heisenbug">heisenbug</a></b>; see also <b><a href="#mandelbug">mandelbug</a></b>, <b><a href="#schroedinbug">schroedinbug</a></b>.</p> + +<hr> +Node:<a name="boink">boink</a>, Next:<a rel="next" href="#bomb">bomb</a>, Previous:<a rel="previous" href="#Bohrbug">Bohr bug</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>boink</b> /boynk/</p> + +<p>[Usenet: variously ascribed to the TV series "Cheers" +"Moonlighting", and "Soap"] 1. v. To have sex with; compare <b><a +href="#bounce">bounce</a></b>, sense 3. (This is mainstream +slang.) In Commonwealth hackish the variant `bonk' is more +common. 2. n. After the original Peter Korn `Boinkon' <b><a href="#Usenet">Usenet</a></b> 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 <b><a href="#atparty">@-party</a></b>. 3. Var +of `bonk'; see <b><a href="#bonkfoif">bonk/oif</a></b>.</p> + +<hr> +Node:<a name="bomb">bomb</a>, +Next:<a rel="next" href="#bondage-and-disciplinelanguage">bondage-and-discipline +language</a>, Previous:<a rel="previous" href="#boink">boink</a>, +Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bomb</b></p> + +<p>1. v. General synonym for <b><a href="#crash">crash</a></b> +(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 <b><a href="#gurumeditation">guru +meditation</a></b>, 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 <b><a href="#gurumeditation">guru +meditation</a></b> number. <b><a href="#MS-DOS">MS-DOS</a></b> +machines tend to get <b><a href="#lockedup">locked up</a></b> +in this situation.</p> + +<hr> +Node:<a name="bondage-and-disciplinelanguage">bondage-and-discipline +language</a>, Next:<a rel="next" href="#bonkfoif">bonk/oif</a>, +Previous:<a rel="previous" href="#bomb">bomb</a>, Up:<a rel="up" +href="#chap02">= B =</a> <br> + + +<p><b>bondage-and-discipline language</b> n.</p> + +<p>A language (such as <b><a href="#Pascal">Pascal</a></b>, <b><a +href="#Ada">Ada</a></b>, 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 <b><a href="#Pascal">Pascal</a></b>; oppose <b><a href="#languagesofchoice">languages of choice</a></b>.</p> + +<hr> +Node:<a name="bonkfoif">bonk/oif</a>, Next:<a rel="next" href="#booktitles">book titles</a>, Previous:<a rel="previous" +href="#bondage-and-disciplinelanguage">bondage-and-discipline +language</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bonk/oif</b> /bonk/, /oyf/ interj.</p> + +<p>In the U.S. <b><a href="#MUD">MUD</a></b> 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. Note: in parts of the U.K. +`bonk' is a sexually loaded slang term; care is advised in +transatlantic conversations (see <b><a href="#boink">boink</a></b>). Commonwealth hackers report a similar +convention involving the `fish/bang' balance. See also <b><a +href="#talkmode">talk mode</a></b>.</p> + +<hr> +Node:<a name="booktitles">book titles</a>, Next:<a rel="next" +href="#boot">boot</a>, Previous:<a rel="previous" href="#bonkfoif">bonk/oif</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>book titles</b></p> + +<p>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 <b><a href="#AluminumBook">Aluminum +Book</a></b>, <b><a href="#BlueBook">Blue Book</a></b>, <b><a +href="#CamelBook">Camel Book</a></b>, <b><a href="#CinderellaBook">Cinderella Book</a></b>, <b><a href="#DevilBook">Devil Book</a></b>, <b><a href="#DragonBook">Dragon Book</a></b>, <b><a href="#GreenBook">Green Book</a></b>, <b><a href="#OrangeBook">Orange Book</a></b>, <b><a href="#PurpleBook">Purple Book</a></b>, <b><a href="#RedBook">Red Book</a></b>, <b><a href="#SilverBook">Silver Book</a></b>, <b><a href="#WhiteBook">White Book</a></b>, <b><a href="#WizardBook">Wizard Book</a></b>, <b><a href="#YellowBook">Yellow Book</a></b>, and <b><a href="#bible">bible</a></b>; see also <b><a href="#rainbowseries">rainbow series</a></b>. Since about 1983 this +tradition has gotten a boost from the popular O'Reilly and +Associates line of technical books, which usually feature some +kind of exotic animal on the cover.</p> + +<hr> +Node:<a name="boot">boot</a>, Next:<a rel="next" href="#Borg">Borg</a>, Previous:<a rel="previous" href="#booktitles">book titles</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>boot</b> v.,n.</p> + +<p>[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.</p> + +<p>The derivative `reboot' implies that the machine hasn't been +down for long, or that the boot is a <b><a href="#bounce">bounce</a></b> (sense 4) intended to clear some state +of <b><a href="#wedgitude">wedgitude</a></b>. This is sometimes +used of human thought processes, as in the following exchange: +"You've lost me." "OK, reboot. Here's the +theory<small>...</small>."</p> + +<p>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).</p> + +<p>Another variant: `soft boot', reinitialization of only part of +a system, under control of other software still running: "If +you're running the <b><a href="#mess-dos">mess-dos</a></b> +emulator, control-alt-insert will cause a soft-boot of the +emulator, while leaving the rest of the system running."</p> + +<p>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 <b><a href="#powercycle">power cycle</a></b>.</p> + +<p>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.</p> + +<hr> +Node:<a name="Borg">Borg</a>, Next:<a rel="next" href="#borken">borken</a>, Previous:<a rel="previous" href="#boot">boot</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>Borg</b> n.</p> + +<p>In "Star Trek: The Next Generation" the Borg is a species of +cyborg that ruthlessly seeks to incorporate all sentient life +into itself; their slogan is "You will be assimilated. Resistance +is futile." In hacker parlance, the Borg is usually <b><a href="#Microsoft">Microsoft</a></b>, which is thought to be trying +just as ruthlessly to assimilate all computers and the entire +Internet to itself (there is a widely circulated image of Bill +Gates as a Borg). Being forced to use Windows or NT is often +referred to as being "Borged". Interestingly, the <b><a href="#HalloweenDocuments">Halloween Documents</a></b> reveal that +this jargon is live within Microsoft itself. (Other companies, +notably Intel and UUNet, have also occasionally been equated to +the Borg.) See also <b><a href="#EvilEmpire">Evil +Empire</a></b>, <b><a href="#InternetExploiter">Internet +Exploiter</a></b>.</p> + +<p>In IETF circles, where direct pressure from Microsoft is not a +daily reality, the Borg is sometimes Cisco. This usage +commemmorates their tendency to pay any price to hire talent away +from their competitors. In fact, at the Spring 1997 IETF, a large +number of ex-Cisco employees, all former members of Routing +Geeks, showed up with t-shirts printed with "Recovering +Borg".</p> + +<hr> +Node:<a name="borken">borken</a>, Next:<a rel="next" href="#bot">bot</a>, Previous:<a rel="previous" href="#Borg">Borg</a>, +Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>borken</b> adj.</p> + +<p>(also `borked') Common deliberate typo for `broken'.</p> + +<hr> +Node:<a name="bot">bot</a>, Next:<a rel="next" href="#botspot">bot spot</a>, Previous:<a rel="previous" href="#borken">borken</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>bot</b> n</p> + +<p>[common on IRC, MUD and among gamers; from `robot'] 1. An +<b><a href="#IRC">IRC</a></b> or <b><a href="#MUD">MUD</a></b> +user who is actually a program. On IRC, typically the robot +provides some useful service. Examples are NickServ, which tries +to prevent random users from adopting <b><a href="#nick">nick</a></b>s already claimed by others, and MsgServ, +which allows one to send asynchronous messages to be delivered +when the recipient signs on. Also common are `annoybots', such as +KissServ, which perform no useful function except to send cute +messages to other people. Service bots are less common on MUDs; +but some others, such as the `Julia' bot active in 1990-91, have +been remarkably impressive Turing-test experiments, able to pass +as human for as long as ten or fifteen minutes of conversation. +2. An AI-controlled player in a computer game (especially a +first-person shooter such as Quake) which, unlike ordinary +monsters, operates like a human-controlled player, with access to +a player's weapons and abilities. An example can be found at <a +href="http://www.telefragged.com/thefatal/">http://www.telefragged.com/thefatal/</a>. +3. Term used, though less commonly, for a web <b><a href="#spider">spider</a></b>. The file for controlling spider +behavior on your site is officially the "Robots Exclusion File" +and its URL is "http://<somehost>/robots.txt")</p> + +<p>Note that bots in all senses were `robots' when the terms +first appeared in the early 1990s, but the shortened form is now +habitual.</p> + +<hr> +Node:<a name="botspot">bot spot</a>, Next:<a rel="next" href="#bottomfeeder">bottom feeder</a>, Previous:<a rel="previous" +href="#bot">bot</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>bot spot</b> n.</p> + +<p>[MUD] The user on a MUD with the longest connect time. Derives +from the fact that <b><a href="#bot">bot</a></b>s on MUDS often +stay constantly connected and appear at the bottom of the +list.</p> + +<hr> +Node:<a name="bottomfeeder">bottom feeder</a>, Next:<a rel="next" href="#bottom-upimplementation">bottom-up +implementation</a>, Previous:<a rel="previous" href="#botspot">bot spot</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bottom feeder</b> n.</p> + +<p>1. An Internet user that leeches off ISPs - the sort you can +never provide good enough services for, always complains about +the price, no matter how low it may be, and will bolt off to +another service the moment there is even the slimmest price +difference. While most bottom feeders infest free or almost free +services such as AOL, MSN, and Hotmail, too many flock to +whomever happens to be the cheapest regional ISP at the time. +Bottom feeders are often the classic problem user, known for +unleashing spam, flamage, and other breaches of <b><a href="#netiquette">netiquette</a></b>. 2. Syn. for <b><a href="#slopsucker">slopsucker</a></b>, derived from the fishermen's +and naturalists' term for finny creatures who subsist on the +primordial ooze. (This sense is older.)</p> + +<hr> +Node:<a name="bottom-upimplementation">bottom-up +implementation</a>, Next:<a rel="next" href="#bounce">bounce</a>, +Previous:<a rel="previous" href="#bottomfeeder">bottom +feeder</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bottom-up implementation</b> n.</p> + +<p>Hackish opposite of the techspeak term `top-down design'. It +has been 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 <i>build</i> things in the opposite order, by +writing and testing a clean set of primitive operations and then +knitting them together. Naively applied, this leads to +hacked-together bottom-up implementations; a more sophisticated +response is `middle-out implementation', in which scratch code +within primitives at the mid-level of the system is gradually +replaced with a more polished version of the lowest level at the +same time the structure above the midlevel is being built.</p> + +<hr> +Node:<a name="bounce">bounce</a>, Next:<a rel="next" href="#bouncemessage">bounce message</a>, Previous:<a rel="previous" href="#bottom-upimplementation">bottom-up +implementation</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>bounce</b> v.</p> + +<p>1. [common; 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 +<b><a href="#bouncemessage">bounce message</a></b>. 2. +[Stanford] To play volleyball. The now-demolished <b><a href="#DCPowerLab">D. C. Power Lab</a></b> 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 <b><a href="#boink">boink</a></b>. 4. To casually reboot a system in order +to clear up a transient problem. Reported primarily among <b><a +href="#VMS">VMS</a></b> and <b><a href="#Unix">Unix</a></b> +users. 5. [VM/CMS programmers] <i>Automatic</i> 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 <b><a href="#powercycle">power cycle</a></b> a peripheral in order to +reset it.</p> + +<hr> +Node:<a name="bouncemessage">bounce message</a>, Next:<a rel="next" href="#boustrophedon">boustrophedon</a>, Previous:<a rel="previous" href="#bounce">bounce</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bounce message</b> n.</p> + +<p>[common] Notification message returned to sender by a site +unable to relay <b><a href="#email">email</a></b> to the intended +<b><a href="#Internetaddress">Internet address</a></b> +recipient or the next link in a <b><a href="#bangpath">bang +path</a></b> (see <b><a href="#bounce">bounce</a></b>, sense 1). +Reasons might include a nonexistent or misspelled username or a +<b><a href="#down">down</a></b> relay site. Bounce messages can +themselves fail, with occasionally ugly results; see <b><a href="#sorcerersapprenticemode">sorcerer's apprentice +mode</a></b> and <b><a href="#softwarelaser">software +laser</a></b>. The terms `bounce mail' and `barfmail' are also +common.</p> + +<hr> +Node:<a name="boustrophedon">boustrophedon</a>, Next:<a rel="next" href="#box">box</a>, Previous:<a rel="previous" href="#bouncemessage">bounce message</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>boustrophedon</b> n.</p> + +<p>[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).</p> + +<hr> +Node:<a name="box">box</a>, Next:<a rel="next" href="#boxedcomments">boxed comments</a>, Previous:<a rel="previous" href="#boustrophedon">boustrophedon</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>box</b> n.</p> + +<p>1. A computer; esp. in the construction `foo box' where +<i>foo</i> 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 <b><a href="#mainframe">mainframe</a></b> to +communicate beyond the limits of the <b><a href="#dinosaurpen">dinosaur pen</a></b>. Typically used in +expressions like the cry that goes up when an SNA network goes +down: "Looks like the <b><a href="#box">box</a></b> has fallen +over." (See <b><a href="#fallover">fall over</a></b>.) See +also <b><a href="#IBM">IBM</a></b>, <b><a href="#fearandloathing">fear and loathing</a></b>, <b><a href="#BlueGlue">Blue Glue</a></b>.</p> + +<hr> +Node:<a name="boxedcomments">boxed comments</a>, Next:<a rel="next" href="#boxen">boxen</a>, Previous:<a rel="previous" href="#box">box</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>boxed comments</b> n.</p> + +<p>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:<br> +</p> + +<pre> +/************************************************* + * + * This is a boxed comment in C style + * + *************************************************/ +</pre> + +<br> +<p>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 <b><a href="#wingedcomments">winged comments</a></b>.</p> + +<hr> +Node:<a name="boxen">boxen</a>, Next:<a rel="next" href="#boxology">boxology</a>, Previous:<a rel="previous" href="#boxedcomments">boxed comments</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>boxen</b> /bok'sn/ pl.n.</p> + +<p>[very common; by analogy with <b><a href="#VAXen">VAXen</a></b>] Fanciful plural of <b><a href="#box">box</a></b> often encountered in the phrase `Unix boxen', +used to describe commodity <b><a href="#Unix">Unix</a></b> +hardware. The connotation is that any two Unix boxen are +interchangeable.</p> + +<hr> +Node:<a name="boxology">boxology</a>, Next:<a rel="next" href="#bozotic">bozotic</a>, Previous:<a rel="previous" href="#boxen">boxen</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>boxology</b> /bok-sol'*-jee/ n.</p> + +<p>Syn. <b><a href="#ASCIIart">ASCII art</a></b>. This term +implies a more restricted domain, that of box-and-arrow drawings. +"His report has a lot of boxology in it." Compare <b><a href="#macrology">macrology</a></b>.</p> + +<hr> +Node:<a name="bozotic">bozotic</a>, Next:<a rel="next" href="#BQS">BQS</a>, Previous:<a rel="previous" href="#boxology">boxology</a>, Up:<a rel="up" href="#chap02">= +B =</a> <br> + + +<p><b>bozotic</b> /boh-zoh'tik/ or /boh-zo'tik/ adj.</p> + +<p>[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 +<b><a href="#wonky">wonky</a></b>, <b><a href="#demented">demented</a></b>. Note that the noun `bozo' occurs in +slang, but the mainstream adjectival form would be `bozo-like' or +(in New England) `bozoish'.</p> + +<hr> +Node:<a name="BQS">BQS</a>, Next:<a rel="next" href="#braindump">brain dump</a>, Previous:<a rel="previous" href="#bozotic">bozotic</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>BQS</b> /B-Q-S/ adj.</p> + +<p>Syn. <b><a href="#BerkeleyQualitySoftware">Berkeley +Quality Software</a></b>.</p> + +<hr> +Node:<a name="braindump">brain dump</a>, Next:<a rel="next" +href="#brainfart">brain fart</a>, Previous:<a rel="previous" +href="#BQS">BQS</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>brain dump</b> n.</p> + +<p>[common] 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 <b><a href="#coredump">core +dump</a></b> in that it saves a lot of useful <b><a href="#state">state</a></b> before an exit. "You'll have to give me a +brain dump on FOOBAR before you start your new job at +HackerCorp." See <b><a href="#coredump">core dump</a></b> +(sense 4). At Sun, this is also known as `TOI' (transfer of +information).</p> + +<hr> +Node:<a name="brainfart">brain fart</a>, Next:<a rel="next" +href="#brain-damaged">brain-damaged</a>, Previous:<a rel="previous" href="#braindump">brain dump</a>, Up:<a rel="up" +href="#chap02">= B =</a> <br> + + +<p><b>brain fart</b> n.</p> + +<p>The actual result of a <b><a href="#braino">braino</a></b>, as +opposed to the mental glitch that is the braino itself. E.g., +typing <code>dir</code> on a Unix box after a session with +DOS.</p> + +<hr> +Node:<a name="brain-damaged">brain-damaged</a>, Next:<a rel="next" href="#brain-dead">brain-dead</a>, Previous:<a rel="previous" href="#brainfart">brain fart</a>, Up:<a rel="up" +href="#chap02">= B =</a> <br> + + +<p><b>brain-damaged</b> adj.</p> + +<p>1. [common; generalization of `Honeywell Brain Damage' (HBD), +a theoretical disease invented to explain certain utter +cretinisms in Honeywell <b><a href="#Multics">Multics</a></b>] +adj. Obviously wrong; <b><a href="#cretinous">cretinous</a></b>; +<b><a href="#demented">demented</a></b>. 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 +<i>that's</i> 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 product it is +intended to sell. Syn. <b><a href="#crippleware">crippleware</a></b>.</p> + +<hr> +Node:<a name="brain-dead">brain-dead</a>, Next:<a rel="next" +href="#braino">braino</a>, Previous:<a rel="previous" href="#brain-damaged">brain-damaged</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>brain-dead</b> adj.</p> + +<p>[common] 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!"</p> + +<hr> +Node:<a name="braino">braino</a>, Next:<a rel="next" href="#branchtoFishkill">branch to Fishkill</a>, Previous:<a +rel="previous" href="#brain-dead">brain-dead</a>, Up:<a rel="up" +href="#chap02">= B =</a> <br> + + +<p><b>braino</b> /bray'no/ n.</p> + +<p>Syn. for <b><a href="#thinko">thinko</a></b>. See also <b><a +href="#brainfart">brain fart</a></b>.</p> + +<hr> +Node:<a name="branchtoFishkill">branch to Fishkill</a>, +Next:<a rel="next" href="#breadcrumbs">bread crumbs</a>, +Previous:<a rel="previous" href="#braino">braino</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>branch to Fishkill</b> n.</p> + +<p>[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 <b><a href="#jumpoffintoneverneverland">jump off into +never-never land</a></b>, <b><a href="#hyperspace">hyperspace</a></b>.</p> + +<hr> +Node:<a name="breadcrumbs">bread crumbs</a>, Next:<a rel="next" href="#break">break</a>, Previous:<a rel="previous" href="#branchtoFishkill">branch to Fishkill</a>, Up:<a rel="up" +href="#chap02">= B =</a> <br> + + +<p><b>bread crumbs</b> n.</p> + +<p>1. Debugging statements inserted into a program that emit +output or log indicators of the program's <b><a href="#state">state</a></b> 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 +or the older French folktale of Thumbelina; in several variants +of these, a character leaves a trail of bread crumbs so as not to +get lost in the woods. 2. In user-interface design, any feature +that allows some tracking of where you've been, like coloring +visited links purple rather than blue in Netscape (also called +`footrinting').</p> + +<hr> +Node:<a name="break">break</a>, Next:<a rel="next" href="#break-evenpoint">break-even point</a>, Previous:<a rel="previous" href="#breadcrumbs">bread crumbs</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>break</b></p> + +<p>1. vt. To cause to be <b><a href="#broken">broken</a></b> (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 <b><a +href="#control-C">control-C</a></b> 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.</p> + +<hr> +Node:<a name="break-evenpoint">break-even point</a>, Next:<a +rel="next" href="#breath-of-lifepacket">breath-of-life +packet</a>, Previous:<a rel="previous" href="#break">break</a>, +Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>break-even point</b> n.</p> + +<p>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 <b><a href="#MFTL">MFTL</a></b>.</p> + +<p>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 +<b><a href="#VAXen">VAXen</a></b> in the early and mid-1980s. A +FOOGOL implementation is available at the Retrocomputing Museum +http://www.ccil.org/retro.</p> + +<hr> +Node:<a name="breath-of-lifepacket">breath-of-life packet</a>, +Next:<a rel="next" href="#breedle">breedle</a>, Previous:<a rel="previous" href="#break-evenpoint">break-even point</a>, Up:<a +rel="up" href="#chap02">= B =</a> <br> + + +<p><b>breath-of-life packet</b> n.</p> + +<p>[XEROX PARC] An Ethernet packet that contains bootstrap (see +<b><a href="#boot">boot</a></b>) 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 <b><a href="#dicklessworkstation">dickless +workstation</a></b>.</p> + +<p>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.</p> + +<hr> +Node:<a name="breedle">breedle</a>, Next:<a rel="next" href="#BreidbartIndex">Breidbart Index</a>, Previous:<a rel="previous" href="#breath-of-lifepacket">breath-of-life +packet</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>breedle</b> n.</p> + +<p>See <b><a href="#feep">feep</a></b>.</p> + +<hr> +Node:<a name="BreidbartIndex">Breidbart Index</a>, Next:<a +rel="next" href="#bringXtoitsknees">bring X to its +knees</a>, Previous:<a rel="previous" href="#breedle">breedle</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>Breidbart Index</b> /bri:d'bart ind*ks/</p> + +<p>A measurement of the severity of spam invented by long-time +hacker Seth Breidbart, used for programming cancelbots. The +Breidbart Index takes into account the fact that excessive +multi-posting <b><a href="#EMP">EMP</a></b> is worse than +excessive cross-posting <b><a href="#ECP">ECP</a></b>. The +Breidbart Index is computed as follows: For each article in a +spam, take the square-root of the number of newsgroups to which +the article is posted. The Breidbart Index is the sum of the +square roots of all of the posts in the spam. For example, one +article posted to nine newsgroups and again to sixteen would have +BI = sqrt(9) + sqrt(16) = 7. It is generally agreed that a spam +is cancelable if the Breidbart Index exceeds 20.</p> + +<p>The Breidbart Index accumulates over a 45-day window. Ten +articles yesterday and ten articles today and ten articles +tomorrow add up to a 30-article spam. Spam fighters will often +reset the count if you can convince them that the spam was +accidental and/or you have seen the error of your ways and won't +repeat it. Breidbart Index can accumulate over multiple authors. +For example, the "Make Money Fast" pyramid scheme exceeded a BI +of 20 a long time ago, and is now considered "cancel on +sight".</p> + +<hr> +Node:<a name="bringXtoitsknees">bring X to its +knees</a>, Next:<a rel="next" href="#brittle">brittle</a>, +Previous:<a rel="previous" href="#BreidbartIndex">Breidbart +Index</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bring X to its knees</b> v.</p> + +<p>[common] To present a machine, operating system, piece of +software, or algorithm with a load so extreme or <b><a href="#pathological">pathological</a></b> that it grinds to a halt. +"To bring a MicroVAX to its knees, try twenty users running <b><a +href="#vi">vi</a></b> -- or four running <b><a href="#EMACS">EMACS</a></b>." Compare <b><a href="#hog">hog</a></b>.</p> + +<hr> +Node:<a name="brittle">brittle</a>, Next:<a rel="next" href="#broadcaststorm">broadcast storm</a>, Previous:<a rel="previous" href="#bringXtoitsknees">bring X to its +knees</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>brittle</b> adj.</p> + +<p>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 +commercial software, which (due to closed-source development) +displays the quality far more often than it ought to. Oppose +<b><a href="#robust">robust</a></b>.</p> + +<hr> +Node:<a name="broadcaststorm">broadcast storm</a>, Next:<a +rel="next" href="#brochureware">brochureware</a>, Previous:<a +rel="previous" href="#brittle">brittle</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>broadcast storm</b> n.</p> + +<p>[common] 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 <b><a href="#networkmeltdown">network meltdown</a></b>; compare <b><a +href="#mailstorm">mail storm</a></b>.</p> + +<hr> +Node:<a name="brochureware">brochureware</a>, Next:<a rel="next" +href="#broken">broken</a>, Previous:<a rel="previous" href="#broadcaststorm">broadcast storm</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>brochureware</b> n.</p> + +<p>Planned but non-existent product like <b><a href="#vaporware">vaporware</a></b>, 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.</p> + +<hr> +Node:<a name="broken">broken</a>, Next:<a rel="next" href="#brokenarrow">broken arrow</a>, Previous:<a rel="previous" +href="#brochureware">brochureware</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>broken</b> adj.</p> + +<p>1. Not working properly (of programs). 2. Behaving strangely; +especially (when used of people) exhibiting extreme +depression.</p> + +<hr> +Node:<a name="brokenarrow">broken arrow</a>, Next:<a rel="next" href="#BrokenWindows">BrokenWindows</a>, Previous:<a rel="previous" href="#broken">broken</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>broken arrow</b> n.</p> + +<p>[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 <b><a href="#down">down</a></b> computer). On a +PC, simulated with `->/_', with the two center characters +overstruck.</p> + +<p>Note: to appreciate this term fully, it helps to know that +`broken arrow' is also military jargon for an accident involving +nuclear weapons<small>...</small>.</p> + +<hr> +Node:<a name="BrokenWindows">BrokenWindows</a>, Next:<a rel="next" href="#broket">broket</a>, Previous:<a rel="previous" +href="#brokenarrow">broken arrow</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>BrokenWindows</b> n.</p> + +<p>Abusive hackerism for the <b><a href="#crufty">crufty</a></b> +and <b><a href="#elephantine">elephantine</a></b> <b><a href="#X">X</a></b> environment on Sun machines; properly called +`OpenWindows'.</p> + +<hr> +Node:<a name="broket">broket</a>, Next:<a rel="next" href="#BrookssLaw">Brooks's Law</a>, Previous:<a rel="previous" +href="#BrokenWindows">BrokenWindows</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>broket</b> /broh'k*t/ or /broh'ket`/ n.</p> + +<p>[rare; by analogy with `bracket': a `broken bracket'] Either +of the characters <code><</code> and <code>></code>, 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 <b><a +href="#RealWorld">Real World</a></b> as well, these are +usually called <b><a href="#anglebrackets">angle +brackets</a></b>.)</p> + +<hr> +Node:<a name="BrookssLaw">Brooks's Law</a>, Next:<a rel="next" href="#brown-paper-bagbug">brown-paper-bag bug</a>, +Previous:<a rel="previous" href="#broket">broket</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>Brooks's Law</b> prov.</p> + +<p>"Adding manpower to a late software project makes it later" -- +a result of the fact that the expected advantage from splitting +development 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 (though +it's not the whole story; see <b><a href="#bazaar">bazaar</a></b>); too often, <b><a href="#management">management</a></b> still does. See also <b><a href="#creationism">creationism</a></b>, <b><a href="#second-systemeffect">second-system effect</a></b>, <b><a +href="#optimism">optimism</a></b>.</p> + +<hr> +Node:<a name="brown-paper-bagbug">brown-paper-bag bug</a>, +Next:<a rel="next" href="#browser">browser</a>, Previous:<a rel="previous" href="#BrookssLaw">Brooks's Law</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>brown-paper-bag bug</b> n.</p> + +<p>A bug in a public software release that is so embarrassing +that the author notionally wears a brown paper bag over his head +for a while so he won't be recognized on the net. Entered popular +usage after the early-1999 release of the first Linux 2.2, which +had one. The phrase was used in Linus Torvalds's apology +posting.</p> + +<hr> +Node:<a name="browser">browser</a>, Next:<a rel="next" href="#BRS">BRS</a>, Previous:<a rel="previous" href="#brown-paper-bagbug">brown-paper-bag bug</a>, Up:<a rel="up" +href="#chap02">= B =</a> <br> + + +<p><b>browser</b> n.</p> + +<p>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 +techspeak 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.</p> + +<hr> +Node:<a name="BRS">BRS</a>, Next:<a rel="next" href="#bruteforce">brute force</a>, Previous:<a rel="previous" +href="#browser">browser</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>BRS</b> /B-R-S/ n.</p> + +<p>Syn. <b><a href="#BigRedSwitch">Big Red Switch</a></b>. +This abbreviation is fairly common on-line.</p> + +<hr> +Node:<a name="bruteforce">brute force</a>, Next:<a rel="next" +href="#bruteforceandignorance">brute force and +ignorance</a>, Previous:<a rel="previous" href="#BRS">BRS</a>, +Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>brute force</b> adj.</p> + +<p>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 <b><a +href="#bruteforceandignorance">brute force and +ignorance</a></b>).</p> + +<p>The <b><a href="#canonical">canonical</a></b> example of a +brute-force algorithm is associated with the `traveling salesman +problem' (TSP), a classical <b><a href="#NP-">NP-</a></b>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 <b><a +href="#bignum">bignum</a></b>). Sometimes, unfortunately, there +is no better general solution than brute force. See also <b><a +href="#NP-">NP-</a></b>.</p> + +<p>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.</p> + +<p>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.</p> + +<p>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 <b><a href="#hahaonlyserious">ha ha +only serious</a></b>, but the original Unix kernel's preference +for simple, robust, and portable algorithms over <b><a href="#brittle">brittle</a></b> `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.</p> + +<hr> +Node:<a name="bruteforceandignorance">brute force and +ignorance</a>, Next:<a rel="next" href="#BSD">BSD</a>, +Previous:<a rel="previous" href="#bruteforce">brute force</a>, +Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>brute force and ignorance</b> n.</p> + +<p>A popular design technique at many software houses -- <b><a +href="#bruteforce">brute force</a></b> 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 <b><a href="#larvalstage">larval stage</a></b> programming; +unfortunately, many never outgrow it. Often abbreviated BFI: +"Gak, they used a <b><a href="#bubblesort">bubble +sort</a></b>! That's strictly from BFI." Compare <b><a href="#bogosity">bogosity</a></b>.</p> + +<hr> +Node:<a name="BSD">BSD</a>, Next:<a rel="next" href="#BSOD">BSOD</a>, Previous:<a rel="previous" href="#bruteforceandignorance">brute force and ignorance</a>, +Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>BSD</b> /B-S-D/ n.</p> + +<p>[abbreviation for `Berkeley Software Distribution'] a family +of <b><a href="#Unix">Unix</a></b> versions for the <b><a href="#DEC">DEC</a></b> <b><a href="#VAX">VAX</a></b> and PDP-11 +developed by Bill Joy and others at <b><a href="#Berzerkeley">Berzerkeley</a></b> starting around 1977, +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; descendants including Free/Open/NetBSD, BSD/OS and +MacOS X are still widely popular. Note that BSD versions going +back to 2.9 are often referred to by their version numbers alone, +without the BSD prefix. See <b><a href="#4.2">4.2</a></b>, <b><a +href="#Unix">Unix</a></b>, <b><a href="#USGUnix">USG +Unix</a></b>.</p> + +<hr> +Node:<a name="BSOD">BSOD</a>, Next:<a rel="next" href="#BUAF">BUAF</a>, Previous:<a rel="previous" href="#BSD">BSD</a>, +Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>BSOD</b> /B-S-O-D/</p> + +<p>Very commmon abbreviation for <b><a href="#BlueScreenofDeath">Blue Screen of Death</a></b>. Both +spoken and written.</p> + +<hr> +Node:<a name="BUAF">BUAF</a>, Next:<a rel="next" href="#BUAG">BUAG</a>, Previous:<a rel="previous" href="#BSOD">BSOD</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>BUAF</b> // n.</p> + +<p>[abbreviation, from <i>alt.fan.warlord</i>] Big Ugly ASCII +Font -- a special form of <b><a href="#ASCIIart">ASCII +art</a></b>. 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 <b><a href="#banner">banner</a></b> +(sense 2) programs. These are sometimes used to render one's name +in a <b><a href="#sigblock">sig block</a></b>, and are +critically referred to as `BUAF's. See <b><a href="#warlording">warlording</a></b>.</p> + +<hr> +Node:<a name="BUAG">BUAG</a>, Next:<a rel="next" href="#bubblesort">bubble sort</a>, Previous:<a rel="previous" +href="#BUAF">BUAF</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>BUAG</b> // n.</p> + +<p>[abbreviation, from <i>alt.fan.warlord</i>] Big Ugly ASCII +Graphic. Pejorative term for ugly <b><a href="#ASCIIart">ASCII +art</a></b>, especially as found in <b><a href="#sigblock">sig +block</a></b>s. For some reason, mutations of the head of Bart +Simpson are particularly common in the least imaginative <b><a +href="#sigblock">sig block</a></b>s. See <b><a href="#warlording">warlording</a></b>.</p> + +<hr> +Node:<a name="bubblesort">bubble sort</a>, Next:<a rel="next" +href="#buckybits">bucky bits</a>, Previous:<a rel="previous" +href="#BUAG">BUAG</a>, Up:<a rel="up" href="#chap02">= B +=</a> <br> + + +<p><b>bubble sort</b> n.</p> + +<p>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 <b><a href="#naive">naive</a></b> and untutored programmers, hackers +consider it the <b><a href="#canonical">canonical</a></b> example +of a naive algorithm. (However, it's been shown by repeated +experiment that below about 5000 records bubble-sort is OK +anyway.) The canonical example of a really <i>bad</i> algorithm +is <b><a href="#bogo-sort">bogo-sort</a></b>. A bubble sort might +be used out of ignorance, but any use of bogo-sort could issue +only from brain damage or willful perversity.</p> + +<hr> +Node:<a name="buckybits">bucky bits</a>, Next:<a rel="next" +href="#bufferchuck">buffer chuck</a>, Previous:<a rel="previous" href="#bubblesort">bubble sort</a>, Up:<a rel="up" +href="#chap02">= B =</a> <br> + + +<p><b>bucky bits</b> /buh'kee bits/ n.</p> + +<p>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 <b><a +href="#space-cadetkeyboard">space-cadet keyboard</a></b>). 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.</p> + +<p>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 <i>he</i> 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.</p> + +<p>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 <b><a href="#doublebucky">double bucky</a></b>, <b><a +href="#quadruplebucky">quadruple bucky</a></b>.</p> + +<hr> +Node:<a name="bufferchuck">buffer chuck</a>, Next:<a rel="next" href="#bufferoverflow">buffer overflow</a>, Previous:<a +rel="previous" href="#buckybits">bucky bits</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>buffer chuck</b> n.</p> + +<p>Shorter and ruder syn. for <b><a href="#bufferoverflow">buffer overflow</a></b>.</p> + +<hr> +Node:<a name="bufferoverflow">buffer overflow</a>, Next:<a +rel="next" href="#bug">bug</a>, Previous:<a rel="previous" href="#bufferchuck">buffer chuck</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>buffer overflow</b> n.</p> + +<p>What happens when you try to stuff more data into a buffer +(holding area) than it can handle. This problem is commonly +exploited by <b><a href="#cracker">cracker</a></b>s to get +arbitrary commands executed by a program running with root +permissions. This may be due to a mismatch in the processing +rates of the producing and consuming processes (see <b><a href="#overrun">overrun</a></b> and <b><a href="#firehosesyndrome">firehose syndrome</a></b>), 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 <b><a href="#crunch">crunch</a></b>es +a line at a time, a short line buffer can result in <b><a href="#lossage">lossage</a></b> 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 <b><a href="#spam">spam</a></b>, <b><a href="#overrunscrew">overrun +screw</a></b>.</p> + +<hr> +Node:<a name="bug">bug</a>, Next:<a rel="next" href="#bug-compatible">bug-compatible</a>, Previous:<a rel="previous" +href="#bufferoverflow">buffer overflow</a>, Up:<a rel="up" +href="#chap02">= B =</a> <br> + + +<p><b>bug</b> n.</p> + +<p>An unwanted and unintended property of a program or piece of +hardware, esp. one that causes it to malfunction. Antonym of +<b><a href="#feature">feature</a></b>. 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).</p> + +<p>Historical note: Admiral Grace Hopper (an early computing +pioneer better known for inventing <b><a href="#COBOL">COBOL</a></b>) liked to tell a story in which a +technician solved a <b><a href="#glitch">glitch</a></b> 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 <b><a href="#bug">bug</a></b> 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.</p> + +<p>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.</p> + +<p>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."</p> + +<p>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 <i>telegraph</i> operators +more than a century ago!</p> + +<p>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 (and still do)! 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.</p> + +<p>Further, the term "bug" has long been used among radio +technicians to describe a device that converts electromagnetic +field variations into acoustic signals. It is used to trace radio +interference and look for dangerous radio emissions. Radio +community usage derives from the roach-like shape of the first +versions used by 19th century physicists. The first versions +consisted of a coil of wire (roach body), with the two wire ends +sticking out and bent back to nearly touch forming a spark gap +(roach antennae). The bug is to the radio technician what the +stethoscope is to the stereotype medical doctor. This sense is +almost certainly ancestral to modern use of "bug" for a covert +monitoring device, but may also have contributed to the use of +"bug" for the effects of radio interference itself.</p> + +<p>Actually, use of `bug' in the general sense of a disruptive +event goes back to Shakespeare! (Henry VI, part III - Act V, +Scene II: King Edward: "So, lie thou there. Die thou; and die our +fear; For Warwick was a bug that fear'd us all.") 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.</p> + +<p>In any case, in jargon the word almost never refers to +insects. Here is a plausible conversation that never actually +happened:</p> + +<p>"There is a bug in this ant farm!"</p> + +<p>"What do you mean? I don't see any ants in it."</p> + +<p>"That's the bug."</p> + +<p>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.</p> + +<p>[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 was not actually exhibited +years afterwards. Thus, the process of investigating the +original-computer-bug bug fixed it in an entirely unexpected way, +by making the myth true! --ESR]</p> + +<hr> +Node:<a name="bug-compatible">bug-compatible</a>, Next:<a rel="next" href="#bug-for-bugcompatible">bug-for-bug +compatible</a>, Previous:<a rel="previous" href="#bug">bug</a>, +Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bug-compatible</b> adj.</p> + +<p>[common] Said of a design or revision that has been badly +compromised by a requirement to be compatible with <b><a href="#fossil">fossil</a></b>s or <b><a href="#misfeature">misfeature</a></b>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."</p> + +<hr> +Node:<a name="bug-for-bugcompatible">bug-for-bug +compatible</a>, Next:<a rel="next" href="#bug-of-the-monthclub">bug-of-the-month club</a>, Previous:<a +rel="previous" href="#bug-compatible">bug-compatible</a>, Up:<a +rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bug-for-bug compatible</b> n.</p> + +<p>Same as <b><a href="#bug-compatible">bug-compatible</a></b>, +with the additional implication that much tedious effort went +into ensuring that each (known) bug was replicated.</p> + +<hr> +Node:<a name="bug-of-the-monthclub">bug-of-the-month club</a>, +Next:<a rel="next" href="#buglix">buglix</a>, Previous:<a rel="previous" href="#bug-for-bugcompatible">bug-for-bug +compatible</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>bug-of-the-month club</b> n.</p> + +<p>[from "book-of-the-month club", a time-honored +mail-order-marketing technique in the U.S.] A mythical club which +users of `sendmail(8)' (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 <b><a href="#cracker">cracker</a></b>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'. See also <b><a href="#kernel-of-the-weekclub">kernel-of-the-week club</a></b>.</p> + +<hr> +Node:<a name="buglix">buglix</a>, Next:<a rel="next" href="#bulletproof">bulletproof</a>, Previous:<a rel="previous" href="#bug-of-the-monthclub">bug-of-the-month club</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>buglix</b> /buhg'liks/ n.</p> + +<p>[uncommon] Pejorative term referring to <b><a href="#DEC">DEC</a></b>'s ULTRIX operating system in its earlier +<i>severely</i> buggy versions. Still used to describe ULTRIX, +but without nearly so much venom. Compare <b><a href="#AIDX">AIDX</a></b>, <b><a href="#HP-SUX">HP-SUX</a></b>, <b><a +href="#NominalSemidestructor">Nominal Semidestructor</a></b>, +<b><a href="#Telerat">Telerat</a></b>, <b><a href="#sun-stools">sun-stools</a></b>.</p> + +<hr> +Node:<a name="bulletproof">bulletproof</a>, Next:<a rel="next" +href="#bullschildt">bullschildt</a>, Previous:<a rel="previous" +href="#buglix">buglix</a>, Up:<a rel="up" href="#chap02">= +B =</a> <br> + + +<p><b>bulletproof</b> adj.</p> + +<p>Used of an algorithm or implementation considered extremely +<b><a href="#robust">robust</a></b>; lossage-resistant; capable +of correctly recovering from any imaginable exception condition +-- a rare and valued quality. Implies that the programmer has +thought of all possible errors, and added <b><a href="#code">code</a></b> to protect against each one. Thus, in some +cases, this can imply code that is too heavyweight, due to +excessive paranoia on the part of the programmer. Syn. <b><a +href="#armor-plated">armor-plated</a></b>.</p> + +<hr> +Node:<a name="bullschildt">bullschildt</a>, Next:<a rel="next" +href="#bum">bum</a>, Previous:<a rel="previous" href="#bulletproof">bulletproof</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bullschildt</b> /bul'shilt/ n.</p> + +<p>[comp.lang.c on USENET] A confident, but incorrect, statement +about a programming language. This immortalizes a very bad book +about <b><a href="#C">C</a></b>, Herbert Schildt's "C - The +Complete Reference". One reviewer commented "The naive errors in +this book would be embarassing even in a programming assignment +turned in by a computer science college sophomore."</p> + +<hr> +Node:<a name="bum">bum</a>, Next:<a rel="next" href="#bump">bump</a>, Previous:<a rel="previous" href="#bullschildt">bullschildt</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bum</b></p> + +<p>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 <b><a href="#elderdays">elder +days</a></b>, John McCarthy (inventor of <b><a href="#LISP">LISP</a></b>) 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 <b><a href="#featurectomy">featurectomy</a></b>). 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. <b><a href="#tune">tune</a></b> (and n. <b><a href="#tweak">tweak</a></b>, +<b><a href="#hack">hack</a></b>), though none of these exactly +capture sense 2. All these uses are rare in Commonwealth hackish, +because in the parent dialects of English the noun `bum' is a +rude synonym for `buttocks' and the verb `bum' for buggery.</p> + +<hr> +Node:<a name="bump">bump</a>, Next:<a rel="next" href="#burble">burble</a>, Previous:<a rel="previous" href="#bum">bum</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>bump</b> vt.</p> + +<p>Synonym for increment. Has the same meaning as C's ++ +operator. Used esp. of counter variables, pointers, and index +dummies in <code>for</code>, <code>while</code>, and +<code>do-while</code> loops.</p> + +<hr> +Node:<a name="burble">burble</a>, Next:<a rel="next" href="#buriedtreasure">buried treasure</a>, Previous:<a rel="previous" href="#bump">bump</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>burble</b> v.</p> + +<p>[from Lewis Carroll's "Jabberwocky"] Like <b><a href="#flame">flame</a></b>, 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.</p> + +<hr> +Node:<a name="buriedtreasure">buried treasure</a>, Next:<a +rel="next" href="#burn-inperiod">burn-in period</a>, +Previous:<a rel="previous" href="#burble">burble</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>buried treasure</b> n.</p> + +<p>A surprising piece of code found in some program. While +usually not wrong, it tends to vary from <b><a href="#crufty">crufty</a></b> to <b><a href="#bletcherous">bletcherous</a></b>, and has lain undiscovered +only because it was functionally correct, however horrible it is. +Used sarcastically, because what is found is anything +<i>but</i> treasure. Buried treasure almost always needs to be +dug up and removed. "I just found that the scheduler sorts its +queue using <b><a href="#bubblesort">bubble sort</a></b>! +Buried treasure!"</p> + +<hr> +Node:<a name="burn-inperiod">burn-in period</a>, Next:<a rel="next" href="#burstpage">burst page</a>, Previous:<a rel="previous" href="#buriedtreasure">buried treasure</a>, Up:<a +rel="up" href="#chap02">= B =</a> <br> + + +<p><b>burn-in period</b> n.</p> + +<p>1. A factory test designed to catch systems with <b><a href="#marginal">marginal</a></b> components before they get out the +door; the theory is that burn-in will protect customers by +outwaiting the steepest part of the <b><a href="#bathtubcurve">bathtub curve</a></b> (see <b><a href="#infantmortality">infant mortality</a></b>). 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 <b><a href="#hackmode">hack +mode</a></b>, <b><a href="#larvalstage">larval +stage</a></b>.</p> + +<p>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.</p> + +<hr> +Node:<a name="burstpage">burst page</a>, Next:<a rel="next" +href="#busy-wait">busy-wait</a>, Previous:<a rel="previous" href="#burn-inperiod">burn-in period</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>burst page</b> n.</p> + +<p>Syn. <b><a href="#banner">banner</a></b>, sense 1.</p> + +<hr> +Node:<a name="busy-wait">busy-wait</a>, Next:<a rel="next" href="#buzz">buzz</a>, Previous:<a rel="previous" href="#burstpage">burst page</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>busy-wait</b> vi.</p> + +<p>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."</p> + +<p>Technically, `busy-wait' means to wait on an event by <b><a +href="#spin">spin</a></b>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. In applications this is a wasteful technique, and best +avoided on time-sharing systems where a busy-waiting program may +<b><a href="#hog">hog</a></b> the processor. However, it is often +unavoidable in kernel programming. In the Linux world, kernel +busy-waits are usually referred to as `spinlocks'.</p> + +<hr> +Node:<a name="buzz">buzz</a>, Next:<a rel="next" href="#BWQ">BWQ</a>, Previous:<a rel="previous" href="#busy-wait">busy-wait</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>buzz</b> vi.</p> + +<p>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 <b><a href="#catatonic">catatonic</a></b>, 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 <b><a href="#spin">spin</a></b>; see also <b><a +href="#grovel">grovel</a></b>. 2. [ETA Systems] To test a wire or +printed circuit trace for continuity, esp. by applying an AC +rather than DC signal. Some wire faults will pass DC tests but +fail an AC 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."</p> + +<hr> +Node:<a name="BWQ">BWQ</a>, Next:<a rel="next" href="#byhand">by hand</a>, Previous:<a rel="previous" href="#buzz">buzz</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>BWQ</b> /B-W-Q/ n.</p> + +<p>[IBM: abbreviation, `Buzz Word Quotient'] The percentage of +buzzwords in a speech or documents. Usually roughly proportional +to <b><a href="#bogosity">bogosity</a></b>. See <b><a href="#TLA">TLA</a></b>.</p> + +<hr> +Node:<a name="byhand">by hand</a>, Next:<a rel="next" href="#byte">byte</a>, Previous:<a rel="previous" href="#BWQ">BWQ</a>, +Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>by hand</b> adv.</p> + +<p>[common] 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 <b><a href="#eyeballsearch">eyeball search</a></b>. 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."</p> + +<hr> +Node:<a name="byte">byte</a>, Next:<a rel="next" href="#byteSex">byte sex</a>, Previous:<a rel="previous" href="#byhand">by hand</a>, Up:<a rel="up" href="#chap02">= +B =</a> <br> + + +<p><b>byte</b> /bi:t/ n.</p> + +<p>[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.</p> + +<p>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 <b><a href="#bit">bit</a></b>. See +also <b><a href="#nybble">nybble</a></b>.</p> + +<hr> +Node:<a name="byteSex">byte sex</a>, Next:<a rel="next" href="#bytesexual">bytesexual</a>, Previous:<a rel="previous" href="#byte">byte</a>, Up:<a rel="up" href="#chap02">= B =</a> +<br> + + +<p><b>byte sex</b> n.</p> + +<p>[common] The byte sex of hardware is <b><a href="#big-endian">big-endian</a></b> or <b><a href="#little-endian">little-endian</a></b>; see those entries.</p> + +<hr> +Node:<a name="bytesexual">bytesexual</a>, Next:<a rel="next" +href="#BzzztWrong.">Bzzzt! Wrong.</a>, Previous:<a rel="previous" href="#byteSex">byte sex</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>bytesexual</b> /bi:t`sek'shu-*l/ adj.</p> + +<p>[rare] Said of hardware, denotes willingness to compute or +pass data in either <b><a href="#big-endian">big-endian</a></b> +or <b><a href="#little-endian">little-endian</a></b> format +(depending, presumably, on a <b><a href="#modebit">mode +bit</a></b> somewhere). See also <b><a href="#NUXIproblem">NUXI problem</a></b>.</p> + +<hr> +Node:<a name="BzzztWrong.">Bzzzt! Wrong.</a>, Next:<a rel="next" href="#C">C</a>, Previous:<a rel="previous" href="#bytesexual">bytesexual</a>, Up:<a rel="up" href="#chap02">= B =</a> <br> + + +<p><b>Bzzzt! Wrong.</b> /bzt rong/ excl.</p> + +<p>[common; Usenet/Internet; punctuation varies] From a Robin +Williams routine in the movie "Dead Poets Society" spoofing radio +or TV quiz programs, such as <i>Truth or Consequences</i>, +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.</p> + +<hr> +Node:<a name="chap03">= C =</a>, Next:<a rel="next" href="#chap04">= D =</a>, Previous:<a rel="previous" href="#chap02">= B =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= C =</h2> + +<ul> +<li><a href="#C">C</a>:</li> + +<li><a href="#CProgrammersDisease">C Programmer's +Disease</a>:</li> + +<li><a href="#CandC">C&C</a>:</li> + +<li><a href="#Cplusplus">C++</a>:</li> + +<li><a href="#calculator">calculator</a>:</li> + +<li><a href="#CamelBook">Camel Book</a>:</li> + +<li><a href="#can">can</a>:</li> + +<li><a href="#cannothappen">can't happen</a>:</li> + +<li><a href="#cancelbot">cancelbot</a>:</li> + +<li><a href="#Cancelmoosetm">Cancelmoose[tm]</a>:</li> + +<li><a href="#candygrammar">candygrammar</a>:</li> + +<li><a href="#canonical">canonical</a>:</li> + +<li><a href="#cardwalloper">card walloper</a>:</li> + +<li><a href="#careware">careware</a>:</li> + +<li><a href="#cargocultprogramming">cargo cult +programming</a>:</li> + +<li><a href="#cascade">cascade</a>:</li> + +<li><a href="#caseandpaste">case and paste</a>:</li> + +<li><a href="#casters-upmode">casters-up mode</a>:</li> + +<li><a href="#castingtherunes">casting the runes</a>:</li> + +<li><a href="#cat">cat</a>:</li> + +<li><a href="#catatonic">catatonic</a>:</li> + +<li><a href="#cathedral">cathedral</a>:</li> + +<li><a href="#cdtilde">cd tilde</a>:</li> + +<li><a href="#CDA">CDA</a>:</li> + +<li><a href="#cdr">cdr</a>:</li> + +<li><a href="#chad">chad</a>:</li> + +<li><a href="#chadbox">chad box</a>:</li> + +<li><a href="#chain">chain</a>:</li> + +<li><a href="#channel">channel</a>:</li> + +<li><a href="#channelhopping">channel hopping</a>:</li> + +<li><a href="#channelop">channel op</a>:</li> + +<li><a href="#chanop">chanop</a>:</li> + +<li><a href="#char">char</a>:</li> + +<li><a href="#charityware">charityware</a>:</li> + +<li><a href="#chasepointers">chase pointers</a>:</li> + +<li><a href="#chawmp">chawmp</a>:</li> + +<li><a href="#check">check</a>:</li> + +<li><a href="#cheerfully">cheerfully</a>:</li> + +<li><a href="#chemist">chemist</a>:</li> + +<li><a href="#Chernobylchicken">Chernobyl chicken</a>:</li> + +<li><a href="#Chernobylpacket">Chernobyl packet</a>:</li> + +<li><a href="#chickenHead">chicken head</a>:</li> + +<li><a href="#chicletkeyboard">chiclet keyboard</a>:</li> + +<li><a href="#ChineseArmytechnique">Chinese Army +technique</a>:</li> + +<li><a href="#choad">choad</a>:</li> + +<li><a href="#choke">choke</a>:</li> + +<li><a href="#chomp">chomp</a>:</li> + +<li><a href="#chomper">chomper</a>:</li> + +<li><a href="#CHOP">CHOP</a>:</li> + +<li><a href="#Christmastree">Christmas tree</a>:</li> + +<li><a href="#Christmastreepacket">Christmas tree +packet</a>:</li> + +<li><a href="#chrome">chrome</a>:</li> + +<li><a href="#chug">chug</a>:</li> + +<li><a href="#ChurchoftheSubGenius">Church of the +SubGenius</a>:</li> + +<li><a href="#CinderellaBook">Cinderella Book</a>:</li> + +<li><a href="#CIs">CI$</a>:</li> + +<li><a href="#ClassicC">Classic C</a>:</li> + +<li><a href="#clean">clean</a>:</li> + +<li><a href="#CLM">CLM</a>:</li> + +<li><a href="#clobber">clobber</a>:</li> + +<li><a href="#clock">clock</a>:</li> + +<li><a href="#clocks">clocks</a>:</li> + +<li><a href="#clone">clone</a>:</li> + +<li><a href="#clone-and-hackcoding">clone-and-hack +coding</a>:</li> + +<li><a href="#cloverkey">clover key</a>:</li> + +<li><a href="#clue-by-four">clue-by-four</a>:</li> + +<li><a href="#clustergeeking">clustergeeking</a>:</li> + +<li><a href="#co-lo">co-lo</a>:</li> + +<li><a href="#code">code</a>:</li> + +<li><a href="#coaster">coaster</a>:</li> + +<li><a href="#COBOL">COBOL</a>:</li> + +<li><a href="#COBOLfingers">COBOL fingers</a>:</li> + +<li><a href="#cobwebsite">cobweb site</a>:</li> + +<li><a href="#codegrinder">code grinder</a>:</li> + +<li><a href="#codemonkey">code monkey</a>:</li> + +<li><a href="#CodeoftheGeeks">Code of the +Geeks</a>:</li> + +<li><a href="#codepolice">code police</a>:</li> + +<li><a href="#codes">codes</a>:</li> + +<li><a href="#codewalker">codewalker</a>:</li> + +<li><a href="#coefficientofX">coefficient of X</a>:</li> + +<li><a href="#cokebottle">cokebottle</a>:</li> + +<li><a href="#coldboot">cold boot</a>:</li> + +<li><a href="#COMEFROM">COME FROM</a>:</li> + +<li><a href="#commmode">comm mode</a>:</li> + +<li><a href="#commandkey">command key</a>:</li> + +<li><a href="#commentout">comment out</a>:</li> + +<li><a href="#CommonwealthHackish">Commonwealth +Hackish</a>:</li> + +<li><a href="#compact">compact</a>:</li> + +<li><a href="#compilerjock">compiler jock</a>:</li> + +<li><a href="#compo">compo</a>:</li> + +<li><a href="#compress">compress</a>:</li> + +<li><a href="#Compuserve">Compu$erve</a>:</li> + +<li><a href="#computerconfetti">computer confetti</a>:</li> + +<li><a href="#computergeek">computer geek</a>:</li> + +<li><a href="#computron">computron</a>:</li> + +<li><a href="#con">con</a>:</li> + +<li><a href="#conditionout">condition out</a>:</li> + +<li><a href="#condom">condom</a>:</li> + +<li><a href="#confuser">confuser</a>:</li> + +<li><a href="#connectorconspiracy">connector +conspiracy</a>:</li> + +<li><a href="#cons">cons</a>:</li> + +<li><a href="#consideredharmful">considered harmful</a>:</li> + +<li><a href="#console">console</a>:</li> + +<li><a href="#consolejockey">console jockey</a>:</li> + +<li><a href="#content-free">content-free</a>:</li> + +<li><a href="#control-C">control-C</a>:</li> + +<li><a href="#control-O">control-O</a>:</li> + +<li><a href="#control-Q">control-Q</a>:</li> + +<li><a href="#control-S">control-S</a>:</li> + +<li><a href="#ConwaysLaw">Conway's Law</a>:</li> + +<li><a href="#cookbook">cookbook</a>:</li> + +<li><a href="#cookedmode">cooked mode</a>:</li> + +<li><a href="#cookie">cookie</a>:</li> + +<li><a href="#cookiebear">cookie bear</a>:</li> + +<li><a href="#cookiefile">cookie file</a>:</li> + +<li><a href="#cookiejar">cookie jar</a>:</li> + +<li><a href="#cookiemonster">cookie monster</a>:</li> + +<li><a href="#copiousfreetime">copious free time</a>:</li> + +<li><a href="#copper">copper</a>:</li> + +<li><a href="#copyprotection">copy protection</a>:</li> + +<li><a href="#copybroke">copybroke</a>:</li> + +<li><a href="#copycenter">copycenter</a>:</li> + +<li><a href="#copyleft">copyleft</a>:</li> + +<li><a href="#copyparty">copyparty</a>:</li> + +<li><a href="#copywronged">copywronged</a>:</li> + +<li><a href="#core">core</a>:</li> + +<li><a href="#corecancer">core cancer</a>:</li> + +<li><a href="#coredump">core dump</a>:</li> + +<li><a href="#coreleak">core leak</a>:</li> + +<li><a href="#CoreWars">Core Wars</a>:</li> + +<li><a href="#corge">corge</a>:</li> + +<li><a href="#cosmicrays">cosmic rays</a>:</li> + +<li><a href="#coughanddie">cough and die</a>:</li> + +<li><a href="#courier">courier</a>:</li> + +<li><a href="#coWorker">cow orker</a>:</li> + +<li><a href="#cowboy">cowboy</a>:</li> + +<li><a href="#CPM">CP/M</a>:</li> + +<li><a href="#CPUWars">CPU Wars</a>:</li> + +<li><a href="#crack">crack</a>:</li> + +<li><a href="#crackroot">crack root</a>:</li> + +<li><a href="#cracker">cracker</a>:</li> + +<li><a href="#cracking">cracking</a>:</li> + +<li><a href="#crank">crank</a>:</li> + +<li><a href="#crapplet">crapplet</a>:</li> + +<li><a href="#CrApTeX">CrApTeX</a>:</li> + +<li><a href="#crash">crash</a>:</li> + +<li><a href="#crashandburn">crash and burn</a>:</li> + +<li><a href="#crawlinghorror">crawling horror</a>:</li> + +<li><a href="#cray">cray</a>:</li> + +<li><a href="#crayinstability">cray instability</a>:</li> + +<li><a href="#crayola">crayola</a>:</li> + +<li><a href="#crayolabooks">crayola books</a>:</li> + +<li><a href="#crayon">crayon</a>:</li> + +<li><a href="#creationism">creationism</a>:</li> + +<li><a href="#creep">creep</a>:</li> + +<li><a href="#creepingelegance">creeping elegance</a>:</li> + +<li><a href="#creepingfeaturism">creeping featurism</a>:</li> + +<li><a href="#creepingfeaturitis">creeping +featuritis</a>:</li> + +<li><a href="#cretin">cretin</a>:</li> + +<li><a href="#cretinous">cretinous</a>:</li> + +<li><a href="#crippleware">crippleware</a>:</li> + +<li><a href="#criticalmass">critical mass</a>:</li> + +<li><a href="#crlf">crlf</a>:</li> + +<li><a href="#crock">crock</a>:</li> + +<li><a href="#cross-post">cross-post</a>:</li> + +<li><a href="#crossload">crossload</a>:</li> + +<li><a href="#crudware">crudware</a>:</li> + +<li><a href="#cruft">cruft</a>:</li> + +<li><a href="#crufttogether">cruft together</a>:</li> + +<li><a href="#cruftsmanship">cruftsmanship</a>:</li> + +<li><a href="#crufty">crufty</a>:</li> + +<li><a href="#crumb">crumb</a>:</li> + +<li><a href="#crunch">crunch</a>:</li> + +<li><a href="#cryppie">cryppie</a>:</li> + +<li><a href="#CTSS">CTSS</a>:</li> + +<li><a href="#cube">cube</a>:</li> + +<li><a href="#cubing">cubing</a>:</li> + +<li><a href="#cupHolder">cup holder</a>:</li> + +<li><a href="#cursordippedinX">cursor dipped in +X</a>:</li> + +<li><a href="#cuspy">cuspy</a>:</li> + +<li><a href="#cutatape">cut a tape</a>:</li> + +<li><a href="#cybercrud">cybercrud</a>:</li> + +<li><a href="#cyberpunk">cyberpunk</a>:</li> + +<li><a href="#cyberspace">cyberspace</a>:</li> + +<li><a href="#cycle">cycle</a>:</li> + +<li><a href="#cyclecrunch">cycle crunch</a>:</li> + +<li><a href="#cycledrought">cycle drought</a>:</li> + +<li><a href="#cycleofreincarnation">cycle of +reincarnation</a>:</li> + +<li><a href="#cycleserver">cycle server</a>:</li> + +<li><a href="#cypherpunk">cypherpunk</a>:</li> + +<li><a href="#CNK">C|N>K</a>:</li> +</ul> + +<hr> +Node:<a name="C">C</a>, Next:<a rel="next" href="#CProgrammersDisease">C Programmer's Disease</a>, +Previous:<a rel="previous" href="#BzzztWrong.">Bzzzt! +Wrong.</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>C</b> n.</p> + +<p>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 <b><a +href="#Unix">Unix</a></b>; so called because many features +derived from an earlier compiler named `B' in commemoration of +<i>its</i> parent, BCPL. (BCPL was in turn descended from an +earlier Algol-derived language, CPL.) Before Bjarne Stroustrup +settled the question by designing <b><a href="#Cplusplus">C++</a></b>, +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 <b><a href="#languagesofchoice">languages of choice</a></b>, <b><a +href="#indentstyle">indent style</a></b>.</p> + +<p>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".</p> + +<hr> +Node:<a name="CProgrammersDisease">C Programmer's +Disease</a>, Next:<a rel="next" href="#CandC">C&C</a>, +Previous:<a rel="previous" href="#C">C</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>C Programmer's Disease</b> n.</p> + +<p>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 <b><a href="#fandangooncore">fandango on core</a></b>. +In severe cases of the disease, the programmer cannot comprehend +why each fix of this kind seems only to further disgruntle the +user.</p> + +<hr> +Node:<a name="CandC">C&C</a>, Next:<a rel="next" href="#Cplusplus">C++</a>, Previous:<a rel="previous" href="#CProgrammersDisease">C Programmer's Disease</a>, Up:<a +rel="up" href="#chap03">= C =</a> <br> + + +<p><b>C&C</b> //</p> + +<p>[common, esp. on <i>news.admin.net-abuse.email</i>] +Contraction of "Coffee & Cats". This frequently occurs as a +warning label on USENET posts that are likely to cause you to +<b><a href="#snarf">snarf</a></b> coffee onto your keyboard and +startle the cat off your lap.</p> + +<hr> +Node:<a name="Cplusplus">C++</a>, Next:<a rel="next" href="#calculator">calculator</a>, Previous:<a rel="previous" href="#CandC">C&C</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>C++</b> /C'-pluhs-pluhs/ n.</p> + +<p>Designed by Bjarne Stroustrup of AT&T Bell Labs as a +successor to <b><a href="#C">C</a></b>. Now one of the <b><a +href="#languagesofchoice">languages of choice</a></b>, +although many hackers still grumble that it is the successor to +either Algol 68 or <b><a href="#Ada">Ada</a></b> (depending on +generation), and a prime example of <b><a href="#second-systemeffect">second-system effect</a></b>. Almost +anything that can be done in any language can be done in C++, but +it requires a <b><a href="#languagelawyer">language +lawyer</a></b> to know what is and what is not legal-- the design +is <i>almost</i> too large to hold in even hackers' heads. Much +of the <b><a href="#cruft">cruft</a></b> 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 <b><a href="#Java">Java</a></b>" --ESR]</p> + +<hr> +Node:<a name="calculator">calculator</a>, Next:<a rel="next" +href="#CamelBook">Camel Book</a>, Previous:<a rel="previous" +href="#Cplusplus">C++</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>calculator</b> [Cambridge] n.</p> + +<p>Syn. for <b><a href="#bittybox">bitty box</a></b>.</p> + +<hr> +Node:<a name="CamelBook">Camel Book</a>, Next:<a rel="next" +href="#can">can</a>, Previous:<a rel="previous" href="#calculator">calculator</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>Camel Book</b> n.</p> + +<p> +Universally recognized nickname for the book "Programming Perl", by Larry Wall +and Randal L. Schwartz, O'Reilly and Associates 1991, ISBN 0-937175-64-1 +(second edition 1996, ISBN 1-56592-149-6). The definitive reference on <b><a +href="#Perl">Perl</a></b>. +</p> + +<hr> + +Node:<a name="can">can</a>, +Next:<a rel="next" href="#cannothappen">can't happen</a>, +Previous:<a rel="previous" href="#CamelBook">Camel Book</a>, +Up:<a rel="up" href="#chap03">= C =</a> <br> + +<p><b>can</b> vt.</p> + +<p> +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 <b><a +href="#console">console</a></b>". Frequently used in an imperative sense, as in +"Can that print job, the LPT just popped a sprocket!" Synonymous with <b><a +href="#gun">gun</a></b>. 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. +</p> + +<hr> + +Node:<a name="cannothappen">can't happen</a>, +Next:<a rel="next" href="#cancelbot">cancelbot</a>, +Previous:<a rel="previous" href="#can">can</a>, +Up:<a rel="up" href="#chap03">= C =</a> <br> + +<p> +<b>can't happen</b> +</p> + +<p>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 <b><a +href="#firewallcode">firewall code</a></b> (sense 2).</p> + +<hr> +Node:<a name="cancelbot">cancelbot</a>, Next:<a rel="next" href="#Cancelmoosetm">Cancelmoose[tm]</a>, Previous:<a rel="previous" href="#cannothappen">can't happen</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cancelbot</b> /kan'sel-bot/</p> + +<p>[Usenet: compound, cancel + robot] 1. Mythically, a <b><a +href="#robocanceller">robocanceller</a></b> 2. In reality, most +cancelbots are manually operated by being fed lists of spam +message IDs.</p> + +<hr> +Node:<a name="Cancelmoosetm">Cancelmoose[tm]</a>, Next:<a +rel="next" href="#candygrammar">candygrammar</a>, Previous:<a +rel="previous" href="#cancelbot">cancelbot</a>, Up:<a rel="up" +href="#chap03">= C =</a> <br> + + +<p><b>Cancelmoose[tm]</b> /kan'sel-moos/</p> + +<p>[Usenet] The archetype and model of all good <b><a href="#spam">spam</a></b>-fighters. Once upon a time, the 'Moose would +send out spam-cancels and then post notice anonymously to +<i>news.admin.policy</i>, <i>news.admin.misc</i>, and +<i>alt.current-events.net-abuse</i>. The 'Moose stepped to the +fore on its own initiative, at a time (mid-1994) when +spam-cancels were irregular and disorganized, and behaved +altogether admirably - fair, even-handed, and quick to respond to +comments and criticism, all without self-aggrandizement or +martyrdom. Cancelmoose[tm] quickly gained near-unanimous support +from the readership of all three above-mentioned groups.</p> + +<p> +Nobody knows who Cancelmoose[tm] really is, and there aren't even any good +rumors. However, the 'Moose now has an e-mail address (moose@cm.org) and a web +site (http://www.cm.org.) +</p> + +<p>By early 1995, others had stepped into the spam-cancel +business, and appeared to be comporting themselves well, after +the 'Moose's manner. The 'Moose has now gotten out of the +business, and is more interested in ending spam (and cancels) +entirely.</p> + +<hr> +Node:<a name="candygrammar">candygrammar</a>, Next:<a rel="next" +href="#canonical">canonical</a>, Previous:<a rel="previous" href="#Cancelmoosetm">Cancelmoose[tm]</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>candygrammar</b> n.</p> + +<p>A programming-language grammar that is mostly <b><a href="#syntacticsugar">syntactic sugar</a></b>; the term is also a +play on `candygram'. <b><a href="#COBOL">COBOL</a></b>, 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.</p> + +<p>[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 similar gag in "Blazing Saddles" --ESR] +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]</p> + +<hr> +Node:<a name="canonical">canonical</a>, Next:<a rel="next" href="#cardwalloper">card walloper</a>, Previous:<a rel="previous" +href="#candygrammar">candygrammar</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>canonical</b> adj.</p> + +<p>[very common; 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 <b><a href="#KnightsoftheLambdaCalculus">Knights +of the Lambda Calculus</a></b>). Compare <b><a href="#vanilla">vanilla</a></b>.</p> + +<p>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). `<i>The</i> 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.</p> + +<p>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'.</p> + +<p>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."</p> + +<p>Of course, canonicality depends on context, but it is +implicitly defined as the way <i>hackers</i> normally expect +things to be. Thus, a hacker may claim with a straight face that +`according to religious law' is <i>not</i> the canonical +meaning of `canonical'.</p> + +<hr> +Node:<a name="cardwalloper">card walloper</a>, Next:<a rel="next" href="#careware">careware</a>, Previous:<a rel="previous" +href="#canonical">canonical</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>card walloper</b> n.</p> + +<p>An EDP programmer who grinds out batch programs that do stupid +things like print people's paychecks. Compare <b><a href="#codegrinder">code grinder</a></b>. See also <b><a href="#punchedcard">punched card</a></b>, <b><a href="#eighty-columnmind">eighty-column mind</a></b>.</p> + +<hr> +Node:<a name="careware">careware</a>, Next:<a rel="next" href="#cargocultprogramming">cargo cult programming</a>, +Previous:<a rel="previous" href="#cardwalloper">card +walloper</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>careware</b> /keir'weir/ n.</p> + +<p>A variety of <b><a href="#shareware">shareware</a></b> 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. <b><a href="#charityware">charityware</a></b>; compare <b><a href="#crippleware">crippleware</a></b>, sense 2.</p> + +<hr> +Node:<a name="cargocultprogramming">cargo cult +programming</a>, Next:<a rel="next" href="#cascade">cascade</a>, +Previous:<a rel="previous" href="#careware">careware</a>, Up:<a +rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cargo cult programming</b> n.</p> + +<p>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 <b><a href="#shotgundebugging">shotgun debugging</a></b>, <b><a href="#voodooprogramming">voodoo programming</a></b>).</p> + +<p>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).</p> + +<hr> +Node:<a name="cascade">cascade</a>, Next:<a rel="next" href="#caseandpaste">case and paste</a>, Previous:<a rel="previous" href="#cargocultprogramming">cargo cult +programming</a>, Up:<a rel="up" href="#chap03">= C =</a> +<br> + + +<p><b>cascade</b> n.</p> + +<p>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 <b><a href="#includewar">include war</a></b> in +which the object is to create a sort of communal graffito.</p> + +<hr> +Node:<a name="caseandpaste">case and paste</a>, Next:<a +rel="next" href="#casters-upmode">casters-up mode</a>, +Previous:<a rel="previous" href="#cascade">cascade</a>, Up:<a +rel="up" href="#chap03">= C =</a> <br> + + +<p><b>case and paste</b> n.</p> + +<p>[from `cut and paste'] 1. The addition of a new <b><a href="#feature">feature</a></b> 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 <code>case</code> statements. +Leads to <b><a href="#softwarebloat">software +bloat</a></b>.</p> + +<p>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.</p> + +<p>At <b><a href="#DEC">DEC</a></b> (now Compaq), this is +sometimes called `clone-and-hack' coding.</p> + +<hr> +Node:<a name="casters-upmode">casters-up mode</a>, Next:<a +rel="next" href="#castingtherunes">casting the runes</a>, +Previous:<a rel="previous" href="#caseandpaste">case and +paste</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>casters-up mode</b> n.</p> + +<p>[IBM, prob. fr. slang <i>belly up</i>] 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).</p> + +<hr> +Node:<a name="castingtherunes">casting the runes</a>, +Next:<a rel="next" href="#cat">cat</a>, Previous:<a rel="previous" href="#casters-upmode">casters-up mode</a>, Up:<a +rel="up" href="#chap03">= C =</a> <br> + + +<p><b>casting the runes</b> n.</p> + +<p>What a <b><a href="#guru">guru</a></b> 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 <b><a href="#incantation">incantation</a></b>, <b><a +href="#runes">runes</a></b>, <b><a href="#examiningtheentrails">examining the entrails</a></b>; +also see the AI koan about Tom Knight in "<b><a href="#SomeAIKoans">Some AI Koans</a></b>" (Appendix A).</p> + +<p>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 <b><a href="#fieldcircus">field +circus</a></b> 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.</p> + +<hr> +Node:<a name="cat">cat</a>, Next:<a rel="next" href="#catatonic">catatonic</a>, Previous:<a rel="previous" href="#castingtherunes">casting the runes</a>, Up:<a rel="up" +href="#chap03">= C =</a> <br> + + +<p><b>cat</b> [from `catenate' via <b><a href="#Unix">Unix</a></b> <code>cat(1)</code>] vt.</p> + +<p>1. [techspeak] To spew an entire file to the screen or some +other output sink without pause (syn. <b><a href="#blast">blast</a></b>). 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 <b><a href="#dd">dd</a></b>, <b><a href="#BLT">BLT</a></b>.</p> + +<p>Among Unix fans, <code>cat(1)</code> 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.</p> + +<p>Among Unix haters, <code>cat(1)</code> is considered the <b><a +href="#canonical">canonical</a></b> example of <i>bad</i> +user-interface design, because of its woefully unobvious name. It +is far more often used to <b><a href="#blast">blast</a></b> a +file to standard output than to concatenate two files. The name +<code>cat</code> for the former operation is just as unintuitive +as, say, LISP's <b><a href="#cdr">cdr</a></b>.</p> + +<p>Of such oppositions are <b><a href="#holywars">holy +wars</a></b> made<small>...</small>.</p> + +<hr> +Node:<a name="catatonic">catatonic</a>, Next:<a rel="next" href="#cathedral">cathedral</a>, Previous:<a rel="previous" href="#cat">cat</a>, Up:<a rel="up" href="#chap03">= C =</a> +<br> + + +<p><b>catatonic</b> adj.</p> + +<p>Describes a condition of suspended animation in which +something is so <b><a href="#wedged">wedged</a></b> or <b><a +href="#hung">hung</a></b> 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 <b><a href="#nethack">nethack</a></b> +and it went catatonic on me! Aaargh!" Compare <b><a href="#buzz">buzz</a></b>.</p> + +<hr> +Node:<a name="cathedral">cathedral</a>, Next:<a rel="next" href="#cdtilde">cd tilde</a>, Previous:<a rel="previous" href="#catatonic">catatonic</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cathedral</b> n.,adj.</p> + +<p>[see <b><a href="#bazaar">bazaar</a></b> for derivation] The +`classical' mode of software engineering long thought to be +necessarily implied by <b><a href="#BrookssLaw">Brooks's +Law</a></b>. Features small teams, tight project control, and +long release intervals. This term came into use after analysis of +the Linux experience suggested there might be something wrong (or +at least incomplete) in the classical assumptions.</p> + +<hr> +Node:<a name="cdtilde">cd tilde</a>, Next:<a rel="next" href="#CDA">CDA</a>, Previous:<a rel="previous" href="#cathedral">cathedral</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cd tilde</b> /C-D til-d*/ vi.</p> + +<p>To go home. From the Unix C-shell and Korn-shell command +<code>cd ~</code>, which takes one to one's <code>$HOME</code> +(<code>cd</code> with no arguments happens to do the same thing). +By extension, may be used with other arguments; thus, over an +electronic chat link, <code>cd ~coffee</code> would mean "I'm +going to the coffee machine."</p> + +<hr> +Node:<a name="CDA">CDA</a>, Next:<a rel="next" href="#cdr">cdr</a>, Previous:<a rel="previous" href="#cdtilde">cd +tilde</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>CDA</b> /C-D-A/</p> + +<p>The "Communications Decency Act" of 1996, passed on <b><a +href="#BlackThursday">Black Thursday</a></b> 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 threatened 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".</p> + +<p>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.</p> + +<p>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 +<b><a href="#homePage">home page</a></b>s black for 48 hours. +Several civil-rights groups and computing/telecommunications +companies mounted a constitutional challenge. The CDA was +demolished by a strongly-worded decision handed down on in +8th-circuit Federal court and subsequently affirmed by the U.S. +Supreme Court on 26 June 1997 (`White Thursday'). See also <b><a +href="#Exon">Exon</a></b>.</p> + +<hr> +Node:<a name="cdr">cdr</a>, Next:<a rel="next" href="#chad">chad</a>, Previous:<a rel="previous" href="#CDA">CDA</a>, +Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cdr</b> /ku'dr/ or /kuh'dr/ vt.</p> + +<p>[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 +<b><a href="#loopthrough">loop through</a></b>.</p> + +<p>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'.</p> + +<p>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.</p> + +<hr> +Node:<a name="chad">chad</a>, Next:<a rel="next" href="#chadbox">chad box</a>, Previous:<a rel="previous" href="#cdr">cdr</a>, Up:<a rel="up" href="#chap03">= C =</a> +<br> + + +<p><b>chad</b> /chad/ n.</p> + +<p>1. [common] The perforated edge strips on printer paper, after +they have been separated from the printed portion. Also called +<b><a href="#selvage">selvage</a></b>, <b><a href="#perf">perf</a></b>, and <b><a href="#ripoff">ripoff</a></b>. 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'. It's reported that this was very old Army +slang, and it may now be mainstream; it has been reported seen +(1993) in directions for a card-based voting machine in +California.</p> + +<p>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 <b><a +href="#backronym">backronym</a></b>.</p> + +<hr> +Node:<a name="chadbox">chad box</a>, Next:<a rel="next" href="#chain">chain</a>, Previous:<a rel="previous" href="#chad">chad</a>, Up:<a rel="up" href="#chap03">= C =</a> +<br> + + +<p><b>chad box</b> n.</p> + +<p>A metal box about the size of a lunchbox (or in some models a +large wastebasket), for collecting the <b><a href="#chad">chad</a></b> (sense 2) that accumulated in <b><a href="#IronAge">Iron Age</a></b> card punches. You had to open the +covers of the card punch periodically and empty the chad box. The +<b><a href="#bitbucket">bit bucket</a></b> was notionally the +equivalent device in the CPU enclosure, which was typically +across the room in another great gray-and-blue box.</p> + +<hr> +Node:<a name="chain">chain</a>, Next:<a rel="next" href="#channel">channel</a>, Previous:<a rel="previous" href="#chadbox">chad box</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>chain</b></p> + +<p>1. vi. [orig. from BASIC's <code>CHAIN</code> statement] To +hand off execution to a child or successor without going through +the <b><a href="#OS">OS</a></b> 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 <b><a +href="#exec">exec</a></b>. 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.</p> + +<hr> +Node:<a name="channel">channel</a>, Next:<a rel="next" href="#channelhopping">channel hopping</a>, Previous:<a rel="previous" href="#chain">chain</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>channel</b> n.</p> + +<p>[IRC] The basic unit of discussion on <b><a href="#IRC">IRC</a></b>. 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 +<code>#initgame</code>, <code>#hottub</code>, +<code>callahans</code>, and <code>#report</code>. At times of +international crisis, <code>#report</code> 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).</p> + +<hr> +Node:<a name="channelhopping">channel hopping</a>, Next:<a +rel="next" href="#channelop">channel op</a>, Previous:<a rel="previous" href="#channel">channel</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>channel hopping</b> n.</p> + +<p>[common; IRC, GEnie] To rapidly switch channels on <b><a href="#IRC">IRC</a></b>, 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'.</p> + +<hr> +Node:<a name="channelop">channel op</a>, Next:<a rel="next" +href="#chanop">chanop</a>, Previous:<a rel="previous" href="#channelhopping">channel hopping</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>channel op</b> /chan'l op/ n.</p> + +<p>[IRC] Someone who is endowed with privileges on a particular +<b><a href="#IRC">IRC</a></b> channel; commonly abbreviated +`chanop' or `CHOP' or just `op' (as of 2000 these short forms +have almost crowded out the parent usage). These privileges +include the right to <b><a href="#kick">kick</a></b> users, to +change various status bits, and to make others into CHOPs.</p> + +<hr> +Node:<a name="chanop">chanop</a>, Next:<a rel="next" href="#char">char</a>, Previous:<a rel="previous" href="#channelop">channel op</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>chanop</b> /chan'-op/ n.</p> + +<p>[IRC] See <b><a href="#channelop">channel op</a></b>.</p> + +<hr> +Node:<a name="char">char</a>, Next:<a rel="next" href="#charityware">charityware</a>, Previous:<a rel="previous" href="#chanop">chanop</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>char</b> /keir/ or /char/; rarely, /kar/ n.</p> + +<p>Shorthand for `character'. Esp. used by C programmers, as +`char' is C's typename for character data.</p> + +<hr> +Node:<a name="charityware">charityware</a>, Next:<a rel="next" +href="#chasepointers">chase pointers</a>, Previous:<a rel="previous" href="#char">char</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>charityware</b> /cha'rit-ee-weir`/ n.</p> + +<p>Syn. <b><a href="#careware">careware</a></b>.</p> + +<hr> +Node:<a name="chasepointers">chase pointers</a>, Next:<a rel="next" href="#chawmp">chawmp</a>, Previous:<a rel="previous" +href="#charityware">charityware</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>chase pointers</b></p> + +<p>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<small>...</small>." See <b><a href="#danglingpointer">dangling pointer</a></b> and <b><a href="#snap">snap</a></b>. 2. [Cambridge] `pointer chase' or `pointer +hunt': The process of going through a <b><a href="#coredump">core dump</a></b> (sense 1), interactively or on a +large piece of paper printed with hex <b><a href="#runes">runes</a></b>, following dynamic data-structures. Used +only in a debugging context.</p> + +<hr> +Node:<a name="chawmp">chawmp</a>, Next:<a rel="next" href="#check">check</a>, Previous:<a rel="previous" href="#chasepointers">chase pointers</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>chawmp</b> n.</p> + +<p>[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 <b><a href="#nybble">nybble</a></b>.</p> + +<hr> +Node:<a name="check">check</a>, Next:<a rel="next" href="#cheerfully">cheerfully</a>, Previous:<a rel="previous" href="#chawmp">chawmp</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>check</b> n.</p> + +<p>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 +<b><a href="#molly-guard">molly-guard</a></b>s).</p> + +<hr> +Node:<a name="cheerfully">cheerfully</a>, Next:<a rel="next" +href="#chemist">chemist</a>, Previous:<a rel="previous" href="#check">check</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>cheerfully</b> adv.</p> + +<p>See <b><a href="#happily">happily</a></b>.</p> + +<hr> +Node:<a name="chemist">chemist</a>, Next:<a rel="next" href="#Chernobylchicken">Chernobyl chicken</a>, Previous:<a rel="previous" href="#cheerfully">cheerfully</a>, Up:<a rel="up" +href="#chap03">= C =</a> <br> + + +<p><b>chemist</b> n.</p> + +<p>[Cambridge] Someone who wastes computer time on <b><a href="#number-crunching">number-crunching</a></b> 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 <b><a href="#life">life</a></b> patterns. May or may not +refer to someone who actually studies chemistry.</p> + +<hr> +Node:<a name="Chernobylchicken">Chernobyl chicken</a>, Next:<a +rel="next" href="#Chernobylpacket">Chernobyl packet</a>, +Previous:<a rel="previous" href="#chemist">chemist</a>, Up:<a +rel="up" href="#chap03">= C =</a> <br> + + +<p><b>Chernobyl chicken</b> n.</p> + +<p>See <b><a href="#laserchicken">laser chicken</a></b>.</p> + +<hr> +Node:<a name="Chernobylpacket">Chernobyl packet</a>, Next:<a +rel="next" href="#chickenHead">chicken head</a>, Previous:<a +rel="previous" href="#Chernobylchicken">Chernobyl chicken</a>, +Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>Chernobyl packet</b> /cher-noh'b*l pak'*t/ n.</p> + +<p>A network packet that induces a <b><a href="#broadcaststorm">broadcast storm</a></b> and/or <b><a href="#networkmeltdown">network meltdown</a></b>, 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 <b><a href="#Christmastreepacket">Christmas tree packet</a></b>.</p> + +<hr> +Node:<a name="chickenHead">chicken head</a>, Next:<a rel="next" href="#chicletkeyboard">chiclet keyboard</a>, +Previous:<a rel="previous" href="#Chernobylpacket">Chernobyl +packet</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>chicken head</b> n.</p> + +<p>[Commodore] The Commodore Business Machines logo, which +strongly resembles a poultry part (within Commodore itself the +logo was always called `chicken lips'). Rendered in ASCII as +`C='. With the arguable exception of the Amiga (see <b><a href="#amoeba">amoeba</a></b>), Commodore's machines were notoriously +crocky little <b><a href="#bittybox">bitty box</a></b>es (see +also <b><a href="#PETSCII">PETSCII</a></b>), albeit people have +written multitasking Unix-like operating systems with TCP/IP +networking for them. 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.</p> + +<hr> +Node:<a name="chicletkeyboard">chiclet keyboard</a>, Next:<a +rel="next" href="#ChineseArmytechnique">Chinese Army +technique</a>, Previous:<a rel="previous" href="#chickenHead">chicken head</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>chiclet keyboard</b> n.</p> + +<p>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.</p> + +<hr> +Node:<a name="ChineseArmytechnique">Chinese Army +technique</a>, Next:<a rel="next" href="#choad">choad</a>, +Previous:<a rel="previous" href="#chicletkeyboard">chiclet +keyboard</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>Chinese Army technique</b> n.</p> + +<p>Syn. <b><a href="#MongolianHordestechnique">Mongolian +Hordes technique</a></b>.</p> + +<hr> +Node:<a name="choad">choad</a>, Next:<a rel="next" href="#choke">choke</a>, Previous:<a rel="previous" href="#ChineseArmytechnique">Chinese Army technique</a>, Up:<a +rel="up" href="#chap03">= C =</a> <br> + + +<p><b>choad</b> /chohd/ n.</p> + +<p>Synonym for `penis' used in <i>alt.tasteless</i> 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.</p> + +<hr> +Node:<a name="choke">choke</a>, Next:<a rel="next" href="#chomp">chomp</a>, Previous:<a rel="previous" href="#choad">choad</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>choke</b> v.</p> + +<p>1. [common] To reject input, often ungracefully. "NULs make +System V's <code>lpr(1)</code> choke." "I tried building an <b><a +href="#EMACS">EMACS</a></b> binary to use <b><a href="#X">X</a></b>, but <code>cpp(1)</code> choked on all those +<code>#define</code>s." See <b><a href="#barf">barf</a></b>, +<b><a href="#gag">gag</a></b>, <b><a href="#vi">vi</a></b>. 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."</p> + +<hr> +Node:<a name="chomp">chomp</a>, Next:<a rel="next" href="#chomper">chomper</a>, Previous:<a rel="previous" href="#choke">choke</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>chomp</b> vi.</p> + +<p>1. To <b><a href="#lose">lose</a></b>; specifically, to chew +on something of which more was bitten off than one can. Probably +related to gnashing of teeth. 2. To bite the bag; See <b><a href="#bagbiter">bagbiter</a></b>.</p> + +<p>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 "<b><a href="#VerbDoubling">Verb +Doubling</a></b>" in the "<b><a href="#JargonConstruction">Jargon Construction</a></b>" 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.</p> + +<hr> +Node:<a name="chomper">chomper</a>, Next:<a rel="next" href="#CHOP">CHOP</a>, Previous:<a rel="previous" href="#chomp">chomp</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>chomper</b> n.</p> + +<p>Someone or something that is chomping; a loser. See <b><a +href="#loser">loser</a></b>, <b><a href="#bagbiter">bagbiter</a></b>, <b><a href="#chomp">chomp</a></b>.</p> + +<hr> +Node:<a name="CHOP">CHOP</a>, Next:<a rel="next" href="#Christmastree">Christmas tree</a>, Previous:<a rel="previous" href="#chomper">chomper</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>CHOP</b> /chop/ n.</p> + +<p>[IRC] See <b><a href="#channelop">channel op</a></b>.</p> + +<hr> +Node:<a name="Christmastree">Christmas tree</a>, Next:<a rel="next" href="#Christmastreepacket">Christmas tree +packet</a>, Previous:<a rel="previous" href="#CHOP">CHOP</a>, +Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>Christmas tree</b> n.</p> + +<p>A kind of RS-232 line tester or breakout box featuring rows of +blinking red and green LEDs suggestive of Christmas lights.</p> + +<hr> +Node:<a name="Christmastreepacket">Christmas tree +packet</a>, Next:<a rel="next" href="#chrome">chrome</a>, +Previous:<a rel="previous" href="#Christmastree">Christmas +tree</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>Christmas tree packet</b> n.</p> + +<p>A packet with every single option set for whatever protocol is +in use. See <b><a href="#kamikazepacket">kamikaze +packet</a></b>, <b><a href="#Chernobylpacket">Chernobyl +packet</a></b>. (The term doubtless derives from a fanciful image +of each little option bit being represented by a +different-colored light bulb, all turned on.) Compare <b><a href="#Godzillagram">Godzillagram</a></b>.</p> + +<hr> +Node:<a name="chrome">chrome</a>, Next:<a rel="next" href="#chug">chug</a>, Previous:<a rel="previous" href="#Christmastreepacket">Christmas tree packet</a>, Up:<a +rel="up" href="#chap03">= C =</a> <br> + + +<p><b>chrome</b> n.</p> + +<p>[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 <i>pretty</i> chrome!" Distinguished from <b><a +href="#bellsandwhistles">bells and whistles</a></b> by the +fact that the latter are usually added to gratify developers' own +desires for featurefulness. Often used as a term of contempt.</p> + +<hr> +Node:<a name="chug">chug</a>, Next:<a rel="next" href="#ChurchoftheSubGenius">Church of the SubGenius</a>, +Previous:<a rel="previous" href="#chrome">chrome</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>chug</b> vi.</p> + +<p>To run slowly; to <b><a href="#grind">grind</a></b> or <b><a +href="#grovel">grovel</a></b>. "The disk is chugging like +crazy."</p> + +<hr> +Node:<a name="ChurchoftheSubGenius">Church of the +SubGenius</a>, Next:<a rel="next" href="#CinderellaBook">Cinderella Book</a>, Previous:<a rel="previous" href="#chug">chug</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>Church of the SubGenius</b> n.</p> + +<p>A mutant offshoot of <b><a href="#Discordianism">Discordianism</a></b> 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 <b><a href="#slack">slack</a></b>. There is a home page at http://www.subgenius.com/.</p> + +<hr> +Node:<a name="CinderellaBook">Cinderella Book</a>, Next:<a +rel="next" href="#CIs">CI$</a>, Previous:<a rel="previous" href="#ChurchoftheSubGenius">Church of the SubGenius</a>, +Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>Cinderella Book</b> [CMU] n.</p> + +<p>"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 <b><a +href="#booktitles">book titles</a></b>.</p> + +<hr> +Node:<a name="CIs">CI$</a>, Next:<a rel="next" href="#ClassicC">Classic C</a>, Previous:<a rel="previous" href="#CinderellaBook">Cinderella Book</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>CI$</b> // n.</p> + +<p>Hackerism for `CIS', CompuServe Information Service. The +dollar sign refers to CompuServe's rather steep line charges. +Often used in <b><a href="#sigblock">sig block</a></b>s just +before a CompuServe address. Syn. <b><a href="#Compuserve">Compu$erve</a></b>.</p> + +<hr> +Node:<a name="ClassicC">Classic C</a>, Next:<a rel="next" +href="#clean">clean</a>, Previous:<a rel="previous" href="#CIs">CI$</a>, Up:<a rel="up" href="#chap03">= C =</a> +<br> + + +<p><b>Classic C</b> /klas'ik C/ n.</p> + +<p>[a play on `Coke Classic'] The C programming language as +defined in the first edition of <b><a href="#KandR">K&R</a></b>, 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'.</p> + +<p>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.</p> + +<hr> +Node:<a name="clean">clean</a>, Next:<a rel="next" href="#CLM">CLM</a>, Previous:<a rel="previous" href="#ClassicC">Classic C</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>clean</b> 1. adj.</p> + +<p>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 <b><a href="#crufty">crufty</a></b>. 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."</p> + +<hr> +Node:<a name="CLM">CLM</a>, Next:<a rel="next" href="#clobber">clobber</a>, Previous:<a rel="previous" href="#clean">clean</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>CLM</b> /C-L-M/</p> + +<p>[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!"</p> + +<hr> +Node:<a name="clobber">clobber</a>, Next:<a rel="next" href="#clock">clock</a>, Previous:<a rel="previous" href="#CLM">CLM</a>, Up:<a rel="up" href="#chap03">= C =</a> +<br> + + +<p><b>clobber</b> vt.</p> + +<p>To overwrite, usually unintentionally: "I walked off the end +of the array and clobbered the stack." Compare <b><a href="#mung">mung</a></b>, <b><a href="#scribble">scribble</a></b>, +<b><a href="#trash">trash</a></b>, and <b><a href="#smashthestack">smash the stack</a></b>.</p> + +<hr> +Node:<a name="clock">clock</a>, Next:<a rel="next" href="#clocks">clocks</a>, Previous:<a rel="previous" href="#clobber">clobber</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>clock</b></p> + +<p>1. n 1. [techspeak] The master oscillator that steps a CPU or +other digital circuit through its paces. This has nothing to do +with the time of day, although the software counter that keeps +track of the latter may be derived from the former. 2. vt. To run +a CPU or other digital circuit at a particular rate. "If you +clock it at 100MHz, it gets warm.". See <b><a href="#overclock">overclock</a></b>. 3. vt. To force a digital circuit +from one state to the next by applying a single clock pulse. "The +data must be stable 10ns before you clock the latch."</p> + +<hr> +Node:<a name="clocks">clocks</a>, Next:<a rel="next" href="#clone">clone</a>, Previous:<a rel="previous" href="#clock">clock</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>clocks</b> n.</p> + +<p>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 <b><a href="#cycle">cycle</a></b>, +<b><a href="#jiffy">jiffy</a></b>.</p> + +<hr> +Node:<a name="clone">clone</a>, Next:<a rel="next" href="#clone-and-hackcoding">clone-and-hack coding</a>, Previous:<a +rel="previous" href="#clocks">clocks</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>clone</b> n.</p> + +<p>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 <b><a href="#mung">mung</a></b> it".</p> + +<hr> +Node:<a name="clone-and-hackcoding">clone-and-hack coding</a>, +Next:<a rel="next" href="#cloverkey">clover key</a>, +Previous:<a rel="previous" href="#clone">clone</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>clone-and-hack coding</b> n.</p> + +<p>[DEC] Syn. <b><a href="#caseandpaste">case and +paste</a></b>.</p> + +<hr> +Node:<a name="cloverkey">clover key</a>, Next:<a rel="next" +href="#clue-by-four">clue-by-four</a>, Previous:<a rel="previous" +href="#clone-and-hackcoding">clone-and-hack coding</a>, Up:<a +rel="up" href="#chap03">= C =</a> <br> + + +<p><b>clover key</b> n.</p> + +<p>[Mac users] See <b><a href="#featurekey">feature +key</a></b>.</p> + +<hr> +Node:<a name="clue-by-four">clue-by-four</a>, Next:<a rel="next" +href="#clustergeeking">clustergeeking</a>, Previous:<a rel="previous" href="#cloverkey">clover key</a>, Up:<a rel="up" +href="#chap03">= C =</a> <br> + + +<p><b>clue-by-four</b></p> + +<p>[Usenet: portmanteau, clue + two-by-four] The notional stick +with which one whacks an aggressively clueless person. This term +derives from a western American folk saying about training a mule +"First, you got to hit him with a two-by-four. That's to get his +attention." The clue-by-four is a close relative of the <b><a +href="#LART">LART</a></b>. Syn. `clue stick'. This metaphor is +commonly elaborated; your editor once heard a hacker say "I +strike you with the great sword Clue-Bringer!"</p> + +<hr> +Node:<a name="clustergeeking">clustergeeking</a>, Next:<a rel="next" href="#co-lo">co-lo</a>, Previous:<a rel="previous" href="#clue-by-four">clue-by-four</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>clustergeeking</b> /kluh'st*r-gee`king/ n.</p> + +<p>[CMU] Spending more time at a computer cluster doing CS +homework than most people spend breathing.</p> + +<hr> +Node:<a name="co-lo">co-lo</a>, Next:<a rel="next" href="#coaster">coaster</a>, Previous:<a rel="previous" href="#clustergeeking">clustergeeking</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>co-lo</b> /koh'loh`/ n.</p> + +<p>[very common; first heard c.1995] Short for `co-location', +used of a machine you own that is physically sited on the +premises of an ISP in order to take advantage of the ISP's direct +access to lots of network bandwidthm. Often in the phrases `co-lo +box' or `co-lo machines'. Co-lo boxes are typically web and FTP +servers remote-administered by their owners, who may seldom or +never visit the actual site.</p> + +<hr> +Node:<a name="coaster">coaster</a>, Next:<a rel="next" href="#COBOL">COBOL</a>, Previous:<a rel="previous" href="#co-lo">co-lo</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>coaster</b> n.</p> + +<p>1. Unuseable CD produced during failed attempt at writing to +writeable or re-writeable CD media. Certainly related to the +coaster-like shape of a CD, and the relative value of these +failures. "I made a lot of coasters before I got a good CD." 2. +Useless CDs received in the mail from the likes of AOL, MSN, CI$, +Prodigy, ad nauseam.</p> + +<p>In the U.K., `beermat' is often used in these senses.</p> + +<hr> +Node:<a name="COBOL">COBOL</a>, Next:<a rel="next" href="#COBOLfingers">COBOL fingers</a>, Previous:<a rel="previous" +href="#coaster">coaster</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>COBOL</b> /koh'bol/ n.</p> + +<p>[COmmon Business-Oriented Language] (Synonymous with <b><a +href="#evil">evil</a></b>.) A weak, verbose, and flabby language +used by <b><a href="#cardwalloper">card walloper</a></b>s to +do boring mindless things on <b><a href="#dinosaur">dinosaur</a></b> mainframes. Hackers believe that all +COBOL programmers are <b><a href="#suit">suit</a></b>s or <b><a +href="#codegrinder">code grinder</a></b>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 <b><a href="#fearandloathing">fear +and loathing</a></b>, <b><a href="#softwarerot">software +rot</a></b>.</p> + +<hr> +Node:<a name="COBOLfingers">COBOL fingers</a>, Next:<a rel="next" href="#cobwebsite">cobweb site</a>, Previous:<a rel="previous" href="#COBOL">COBOL</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>COBOL fingers</b> /koh'bol fing'grz/ n.</p> + +<p>Reported from Sweden, a (hypothetical) disease one might get +from coding in COBOL. The language requires code verbose beyond +all reason (see <b><a href="#candygrammar">candygrammar</a></b>); +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!"</p> + +<hr> +Node:<a name="cobwebsite">cobweb site</a>, Next:<a rel="next" +href="#code">code</a>, Previous:<a rel="previous" href="#COBOLfingers">COBOL fingers</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cobweb site</b> n.</p> + +<p>A World Wide Web Site that hasn't been updated so long it has +figuratively grown cobwebs.</p> + +<hr> +Node:<a name="code">code</a>, Next:<a rel="next" href="#codegrinder">code grinder</a>, Previous:<a rel="previous" +href="#cobwebsite">cobweb site</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>code</b> n.</p> + +<p>The stuff that software writers write, either in source form +or after translation by a compiler or assembler. Often used in +opposition to "data", which is the stuff that code operates on. +This is a mass noun, as in "How much code does it take to do a +<b><a href="#bubblesort">bubble sort</a></b>?", or "The code +is loaded at the high end of RAM." Anyone referring to software +as "the software codes" is probably a <b><a href="#newbie">newbie</a></b> or a <b><a href="#suit">suit</a></b>.</p> + +<hr> +Node:<a name="codegrinder">code grinder</a>, Next:<a rel="next" href="#codemonkey">code monkey</a>, Previous:<a rel="previous" href="#code">code</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>code grinder</b> n.</p> + +<p>1. A <b><a href="#suit">suit</a></b>-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 <b><a href="#codegrinder">code grinder</a></b>'s milieu is about as far +from hackerdom as one can get and still touch a computer; the +term connotes pity. See <b><a href="#RealWorld">Real +World</a></b>, <b><a href="#suit">suit</a></b>. 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, <b><a href="#bruteforce">brute +force</a></b>, and utter lack of imagination. Compare <b><a href="#cardwalloper">card walloper</a></b>; contrast <b><a href="#hacker">hacker</a></b>, <b><a href="#RealProgrammer">Real +Programmer</a></b>.</p> + +<hr> +Node:<a name="codemonkey">code monkey</a>, Next:<a rel="next" +href="#CodeoftheGeeks">Code of the Geeks</a>, +Previous:<a rel="previous" href="#codegrinder">code +grinder</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>code monkey</b> n</p> + +<p>1. A person only capable of grinding out code, but unable to +perform the higher-primate tasks of software architecture, +analysis, and design. Mildly insulting. Often applied to the most +junior people on a programming team. 2. Anyone who writes code +for a living; a programmer. 3. A self-deprecating way of denying +responsibility for a <b><a href="#management">management</a></b> +decision, or of complaining about having to live with such +decisions. As in "Don't ask me why we need to write a compiler +in+COBOL, I'm just a code monkey."</p> + +<hr> +Node:<a name="CodeoftheGeeks">Code of the Geeks</a>, +Next:<a rel="next" href="#codepolice">code police</a>, +Previous:<a rel="previous" href="#codemonkey">code monkey</a>, +Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>Code of the Geeks</b> n.</p> + +<p>see <b><a href="#geekcode">geek code</a></b>.</p> + +<hr> +Node:<a name="codepolice">code police</a>, Next:<a rel="next" +href="#codes">codes</a>, Previous:<a rel="previous" href="#CodeoftheGeeks">Code of the Geeks</a>, Up:<a rel="up" +href="#chap03">= C =</a> <br> + + +<p><b>code police</b> n.</p> + +<p>[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 +<b><a href="#weenie">weenie</a></b>s. "Dike out that goto or the +code police will get you!" The ironic usage is perhaps more +common.</p> + +<hr> +Node:<a name="codes">codes</a>, Next:<a rel="next" href="#codewalker">codewalker</a>, Previous:<a rel="previous" href="#codepolice">code police</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>codes</b> n.</p> + +<p>[scientific computing] Programs. This usage is common in +people who hack supercomputers and heavy-duty <b><a href="#number-crunching">number-crunching</a></b>, rare to unknown +elsewhere (if you say "codes" to hackers outside scientific +computing, their first association is likely to be "and +cyphers").</p> + +<hr> +Node:<a name="codewalker">codewalker</a>, Next:<a rel="next" +href="#coefficientofX">coefficient of X</a>, Previous:<a +rel="previous" href="#codes">codes</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>codewalker</b> n.</p> + +<p>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 <code>vgrind</code> +feature would require a codewalker to implement."</p> + +<hr> +Node:<a name="coefficientofX">coefficient of X</a>, Next:<a +rel="next" href="#cokebottle">cokebottle</a>, Previous:<a rel="previous" href="#codewalker">codewalker</a>, Up:<a rel="up" +href="#chap03">= C =</a> <br> + + +<p><b>coefficient of X</b> n.</p> + +<p>Hackish speech makes heavy use of pseudo-mathematical +metaphors. Four particularly important ones involve the terms +`coefficient', `factor', `index of X', 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.</p> + +<p>`Foo factor' and `foo quotient' tend to describe something for +which the issue is one of presence or absence. The canonical +example is <b><a href="#fudgefactor">fudge factor</a></b>. +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 +<i>quotient</i> emphasizes that it was bad luck overpowering +good luck (or someone else's good luck overpowering your +own).</p> + +<p>`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'.</p> + +<hr> +Node:<a name="cokebottle">cokebottle</a>, Next:<a rel="next" +href="#coldboot">cold boot</a>, Previous:<a rel="previous" +href="#coefficientofX">coefficient of X</a>, Up:<a rel="up" +href="#chap03">= C =</a> <br> + + +<p><b>cokebottle</b> /kohk'bot-l/ n.</p> + +<p>Any very unusual character, particularly one you can't type +because 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 `escape-escape-cokebottle' +commands at MIT. After the demise of the <b><a href="#space-cadetkeyboard">space-cadet keyboard</a></b>, +`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, <code>mwm(1)</code>, 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 <b><a href="#bang">bang</a></b>). 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 <b><a href="#quadruplebucky">quadruple +bucky</a></b>.</p> + +<hr> +Node:<a name="coldboot">cold boot</a>, Next:<a rel="next" +href="#COMEFROM">COME FROM</a>, Previous:<a rel="previous" +href="#cokebottle">cokebottle</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cold boot</b> n.</p> + +<p>See <b><a href="#boot">boot</a></b>.</p> + +<hr> +Node:<a name="COMEFROM">COME FROM</a>, Next:<a rel="next" +href="#commmode">comm mode</a>, Previous:<a rel="previous" +href="#coldboot">cold boot</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>COME FROM</b> n.</p> + +<p>A semi-mythical language construct dual to the `go to'; +<code>COME FROM</code> <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 <b><a href="#automagically">automagically</a></b> be transferred to the +statement following the <code>COME FROM</code>. <code>COME +FROM</code> was first proposed in R. Lawrence Clark's "A +Linguistic Contribution to GOTO-less programming", which appeared +in a 1973 <b><a href="#Datamation">Datamation</a></b> issue (and +was reprinted in the April 1984 issue of "Communications of the +ACM"). This parodied the then-raging `structured programming' +<b><a href="#holywars">holy wars</a></b> (see <b><a href="#consideredharmful">considered harmful</a></b>). 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 +<code>COME FROM</code> statement coming from the same label.</p> + +<p>In some ways the FORTRAN <code>DO</code> looks like a +<code>COME FROM</code> statement. After the terminating statement +number/<code>CONTINUE</code> is reached, control continues at the +statement following the DO. Some generous FORTRANs would allow +arbitrary statements (other than <code>CONTINUE</code>) for the +statement, leading to examples like:</p> + +<pre> + 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) +</pre> + +<p>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!)</p> + +<p>While sufficiently astonishing to the unsuspecting reader, +this form of <code>COME FROM</code> 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 +<code>AT 100</code> would perform a <code>COME FROM 100</code>. +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 <code>ALTER</code> verb in <b><a href="#COBOL">COBOL</a></b>.</p> + +<p><code>COME FROM</code> was supported under its own name for +the first time 15 years later, in C-INTERCAL (see <b><a href="#INTERCAL">INTERCAL</a></b>, <b><a href="#retrocomputing">retrocomputing</a></b>); knowledgeable +observers are still reeling from the shock.</p> + +<hr> +Node:<a name="commmode">comm mode</a>, Next:<a rel="next" +href="#commandkey">command key</a>, Previous:<a rel="previous" +href="#COMEFROM">COME FROM</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>comm mode</b> /kom mohd/ n.</p> + +<p>[ITS: from the feature supporting on-line chat; the term may +spelled with one or two m's] Syn. for <b><a href="#talkmode">talk mode</a></b>.</p> + +<hr> +Node:<a name="commandkey">command key</a>, Next:<a rel="next" +href="#commentout">comment out</a>, Previous:<a rel="previous" +href="#commmode">comm mode</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>command key</b> n.</p> + +<p>[Mac users] Syn. <b><a href="#featurekey">feature +key</a></b>.</p> + +<hr> +Node:<a name="commentout">comment out</a>, Next:<a rel="next" +href="#CommonwealthHackish">Commonwealth Hackish</a>, +Previous:<a rel="previous" href="#commandkey">command key</a>, +Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>comment out</b> vt.</p> + +<p>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 <b><a href="#conditionout">condition out</a></b>, usually the preferred +technique in languages (such as <b><a href="#C">C</a></b>) that +make it possible.</p> + +<hr> +Node:<a name="CommonwealthHackish">Commonwealth Hackish</a>, +Next:<a rel="next" href="#compact">compact</a>, Previous:<a rel="previous" href="#commentout">comment out</a>, Up:<a rel="up" +href="#chap03">= C =</a> <br> + + +<p><b>Commonwealth Hackish</b> n.</p> + +<p>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 <b><a href="#newsgroup">newsgroup</a></b> names (especially two-component +names) tend to be pronounced more often (so soc.wibble is /sok +dot wib'l/ rather than /sohsh wib'l/).</p> + +<p>Preferred <b><a href="#metasyntacticvariable">metasyntactic +variable</a></b>s include <b><a href="#blurgle">blurgle</a></b>, +<code>eek</code>, <code>ook</code>, <code>frodo</code>, and +<code>bilbo</code>; <b><a href="#wibble">wibble</a></b>, +<code>wobble</code>, and in emergencies <code>wubble</code>; +<code>flob</code>, <code>banana</code>, <code>tom</code>, +<code>dick</code>, <code>harry</code>, <code>wombat</code>, +<code>frog</code>, <b><a href="#fish">fish</a></b>, <b><a href="#womble">womble</a></b> and so on and on (see <b><a href="#foo">foo</a></b>, 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!").</p> + +<p>All the generic differences within the anglophone world +inevitably show themselves in the associated hackish dialects. +The Greek letters beta and zeta are usually pronounced /bee't*/ +and /zee't*/; meta may also be pronounced /mee't*/. Various +punctuators (and even letters - Z is called `zed', not `zee') are +named differently: most crucially, for hackish, where Americans +use `parens', `brackets' and `braces' for (), [] and {}, +Commonwealth English uses `brackets', `square brackets' and +`curly brackets', though `parentheses' may be used for the first; +the exclamation mark, `!', is called pling rather than bang and +the pound sign, `#', is called hash; furthermore, the term `the +pound sign' is understood to mean the pound currency symbol (of +course).</p> + +<p>See also <b><a href="#attoparsec">attoparsec</a></b>, <b><a +href="#calculator">calculator</a></b>, <b><a href="#chemist">chemist</a></b>, <b><a href="#consolejockey">console jockey</a></b>, <b><a href="#fish">fish</a></b>, <b><a href="#gofasterstripes">go-faster +stripes</a></b>, <b><a href="#grunge">grunge</a></b>, <b><a href="#hakspek">hakspek</a></b>, <b><a href="#heavymetal">heavy +metal</a></b>, <b><a href="#leakyheap">leaky heap</a></b>, +<b><a href="#lordhighfixer">lord high fixer</a></b>, <b><a +href="#loosebytes">loose bytes</a></b>, <b><a href="#muddie">muddie</a></b>, <b><a href="#nadger">nadger</a></b>, +<b><a href="#noddy">noddy</a></b>, <b><a href="#psychedelicware">psychedelicware</a></b>, <b><a href="#plingnet">plingnet</a></b>, <b><a href="#rasterblaster">raster blaster</a></b>, <b><a href="#RTBM">RTBM</a></b>, <b><a href="#seggie">seggie</a></b>, <b><a +href="#spod">spod</a></b>, <b><a href="#sunlounge">sun +lounge</a></b>, <b><a href="#terminaljunkie">terminal +junkie</a></b>, <b><a href="#ticklistfeatures">tick-list +features</a></b>, <b><a href="#weeble">weeble</a></b>, <b><a +href="#weasel">weasel</a></b>, <b><a href="#YABA">YABA</a></b>, +and notes or definitions under <b><a href="#BadThing">Bad +Thing</a></b>, <b><a href="#barf">barf</a></b>, <b><a href="#bogus">bogus</a></b>, <b><a href="#bum">bum</a></b>, <b><a +href="#chasepointers">chase pointers</a></b>, <b><a href="#cosmicrays">cosmic rays</a></b>, <b><a href="#crippleware">crippleware</a></b>, <b><a href="#crunch">crunch</a></b>, <b><a href="#dodgy">dodgy</a></b>, +<b><a href="#gonk">gonk</a></b>, <b><a href="#hamster">hamster</a></b>, <b><a href="#hardwarily">hardwarily</a></b>, <b><a href="#mess-dos">mess-dos</a></b>, <b><a href="#nybble">nybble</a></b>, <b><a href="#proglet">proglet</a></b>, +<b><a href="#root">root</a></b>, <b><a href="#SEX">SEX</a></b>, +<b><a href="#tweak">tweak</a></b>, <b><a href="#womble">womble</a></b>, and <b><a href="#xyzzy">xyzzy</a></b>.</p> + +<hr> +Node:<a name="compact">compact</a>, Next:<a rel="next" href="#compilerjock">compiler jock</a>, Previous:<a rel="previous" +href="#CommonwealthHackish">Commonwealth Hackish</a>, Up:<a +rel="up" href="#chap03">= C =</a> <br> + + +<p><b>compact</b> adj.</p> + +<p>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 <b><a +href="#feature">feature</a></b>s and <b><a href="#cruft">cruft</a></b> that don't merge cleanly into the overall +design scheme (thus, some fans of <b><a href="#ClassicC">Classic C</a></b> maintain that ANSI C is no +longer compact).</p> + +<hr> +Node:<a name="compilerjock">compiler jock</a>, Next:<a rel="next" href="#compo">compo</a>, Previous:<a rel="previous" href="#compact">compact</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>compiler jock</b> n.</p> + +<p>See <b><a href="#jock">jock</a></b> (sense 2).</p> + +<hr> +Node:<a name="compo">compo</a>, Next:<a rel="next" href="#compress">compress</a>, Previous:<a rel="previous" href="#compilerjock">compiler jock</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>compo</b> n.</p> + +<p>[<b><a href="#demoscene">demoscene</a></b>] Finnish-originated +slang for `competition'. Demo compos are held at a <b><a href="#demoparty">demoparty</a></b>. The usual protocol is that +several groups make demos for a compo, they are shown on a big +screen, and then the party participants vote for the best one. +Prizes (from sponsors and party entrance fees) are given. +Standard compo formats include <b><a href="#intro">intro</a></b> +compos (4k or 64k demos), music compos, graphics compos, quick +<b><a href="#demo">demo</a></b> compos (build a demo within 4 +hours for example), etc.</p> + +<hr> +Node:<a name="compress">compress</a>, Next:<a rel="next" href="#Compuserve">Compu$erve</a>, Previous:<a rel="previous" href="#compo">compo</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>compress</b> [Unix] vt.</p> + +<p>When used without a qualifier, generally refers to <b><a href="#crunch">crunch</a></b>ing of a file using a particular C +implementation of compression by Joseph M. Orost et al. and +widely circulated via <b><a href="#Usenet">Usenet</a></b>; use of +<b><a href="#crunch">crunch</a></b> 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.</p> + +<hr> +Node:<a name="Compuserve">Compu$erve</a>, Next:<a rel="next" +href="#computerconfetti">computer confetti</a>, Previous:<a +rel="previous" href="#compress">compress</a>, Up:<a rel="up" +href="#chap03">= C =</a> <br> + + +<p><b>Compu$erve</b> n.</p> + +<p>See <b><a href="#CIs">CI$</a></b>. Synonyms CompuSpend and +Compu$pend are also reported.</p> + +<hr> +Node:<a name="computerconfetti">computer confetti</a>, Next:<a +rel="next" href="#computergeek">computer geek</a>, Previous:<a +rel="previous" href="#Compuserve">Compu$erve</a>, Up:<a rel="up" +href="#chap03">= C =</a> <br> + + +<p><b>computer confetti</b> n.</p> + +<p>Syn. <b><a href="#chad">chad</a></b>. 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.</p> + +<hr> +Node:<a name="computergeek">computer geek</a>, Next:<a rel="next" href="#computron">computron</a>, Previous:<a rel="previous" href="#computerconfetti">computer confetti</a>, +Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>computer geek</b> n.</p> + +<p>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 <b><a href="#larvalstage">larval stage</a></b>. Also called `turbo nerd', +`turbo geek'. See also <b><a href="#propellerhead">propeller +head</a></b>, <b><a href="#clustergeeking">clustergeeking</a></b>, <b><a href="#geekout">geek out</a></b>, <b><a href="#wannabee">wannabee</a></b>, <b><a href="#terminaljunkie">terminal junkie</a></b>, <b><a href="#spod">spod</a></b>, <b><a href="#weenie">weenie</a></b>. 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://www.darkwater.com/omni/geek.html. +See also <b><a href="#geekcode">geek code</a></b>.</p> + +<hr> +Node:<a name="computron">computron</a>, Next:<a rel="next" href="#con">con</a>, Previous:<a rel="previous" href="#computergeek">computer geek</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>computron</b> /kom'pyoo-tron`/</p> + +<p>n. 1. [common] 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 <b><a href="#bittybox">bitty box</a></b>, <b><a href="#Getarealcomputer">Get a real computer!</a></b>, <b><a +href="#toy">toy</a></b>, <b><a href="#crank">crank</a></b>. 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 <b><a href="#bogon">bogon</a></b>). 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. (The popularity of 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'.)</p> + +<hr> +Node:<a name="con">con</a>, Next:<a rel="next" href="#conditionout">condition out</a>, Previous:<a rel="previous" +href="#computron">computron</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>con</b> n.</p> + +<p>[from SF fandom] A science-fiction convention. Not used of +other sorts of conventions, such as professional meetings. This +term, unlike many others imported from SF-fan slang, is widely +recognized even by hackers who aren't <b><a href="#fan">fan</a></b>s. "We'd been corresponding on the net for +months, then we met face-to-face at a con."</p> + +<hr> +Node:<a name="conditionout">condition out</a>, Next:<a rel="next" href="#condom">condom</a>, Previous:<a rel="previous" +href="#con">con</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>condition out</b> vt.</p> + +<p>To prevent a section of code from being compiled by +surrounding it with a conditional-compilation directive whose +condition is always false. The <b><a href="#canonical">canonical</a></b> examples of these directives are +<code>#if 0</code> (or <code>#ifdef notdef</code>, though some +find the latter <b><a href="#bletcherous">bletcherous</a></b>) +and <code>#endif</code> in C. Compare <b><a href="#commentout">comment out</a></b>.</p> + +<hr> +Node:<a name="condom">condom</a>, Next:<a rel="next" href="#confuser">confuser</a>, Previous:<a rel="previous" href="#conditionout">condition out</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>condom</b> n.</p> + +<p>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 <b><a href="#SEX">SEX</a></b> 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 +<b><a href="#lightpipe">light pipe</a></b>. 3. `keyboard +condom': A flexible, transparent plastic cover for a keyboard, +designed to provide some protection against dust and <b><a href="#programmingfluid">programming fluid</a></b> 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 <code>/usr/tmp/sh</code>, created to foil the +<b><a href="#GreatWorm">Great Worm</a></b> by exploiting a +portability bug in one of its parts. So named in the title of a +<i>comp.risks</i> 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.</p> + +<hr> +Node:<a name="confuser">confuser</a>, Next:<a rel="next" href="#connectorconspiracy">connector conspiracy</a>, Previous:<a +rel="previous" href="#condom">condom</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>confuser</b> n.</p> + +<p>Common soundalike slang for `computer'. Usually encountered in +compounds such as `confuser room', `personal confuser', `confuser +guru'. Usage: silly.</p> + +<hr> +Node:<a name="connectorconspiracy">connector conspiracy</a>, +Next:<a rel="next" href="#cons">cons</a>, Previous:<a rel="previous" href="#confuser">confuser</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>connector conspiracy</b> n.</p> + +<p>[probably came into prominence with the appearance of the +KL-10 (one model of the <b><a href="#PDP-10">PDP-10</a></b>), +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 <i>patented</i> by <b><a href="#DEC">DEC</a></b>, +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.</p> + +<p>(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 long Torx screwdriver but a +specialized case-cracking tool to open the box.)</p> + +<p>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 <b><a href="#backwardcombatability">backward +combatability</a></b>.</p> + +<hr> +Node:<a name="cons">cons</a>, Next:<a rel="next" href="#consideredharmful">considered harmful</a>, Previous:<a rel="previous" href="#connectorconspiracy">connector +conspiracy</a>, Up:<a rel="up" href="#chap03">= C =</a> +<br> + + +<p><b>cons</b> /konz/ or /kons/</p> + +<p>[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".</p> + +<p>In LISP itself, <code>cons</code> 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.</p> + +<hr> +Node:<a name="consideredharmful">considered harmful</a>, +Next:<a rel="next" href="#console">console</a>, Previous:<a rel="previous" href="#cons">cons</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + +<p><b>considered harmful</b> adj.</p> + +<p>[very common] 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. (Years +afterwards, a contrary view was uttered in a CACM letter called, +inevitably, "`Goto considered harmful' considered harmful'"'. 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).</p> + +<hr> +Node:<a name="console">console</a>, Next:<a rel="next" href="#consolejockey">console jockey</a>, Previous:<a rel="previous" href="#consideredharmful">considered harmful</a>, +Up:<a rel="up" href="#chap03">= C =</a> <br> + +<p><b>console</b> n.</p> + +<p>1. The operator's station of a <b><a href="#mainframe">mainframe</a></b>. 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 <b><a href="#tty">tty</a></b> 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 <b><a href="#X">X</a></b>.</p> + +<hr> +Node:<a name="consolejockey">console jockey</a>, Next:<a rel="next" href="#content-free">content-free</a>, Previous:<a rel="previous" href="#console">console</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + +<p><b>console jockey</b> n.</p> + +<p>See <b><a href="#terminaljunkie">terminal +junkie</a></b>.</p> + +<hr> +Node:<a name="content-free">content-free</a>, Next:<a rel="next" +href="#control-C">control-C</a>, Previous:<a rel="previous" href="#consolejockey">console jockey</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>content-free</b> adj.</p> + +<p>[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 <b><a href="#flamage">flamage</a></b>, 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<small>...</small> that's anything printed on glossy paper." +(See also <b><a href="#fourcolorglossies">four-color +glossies</a></b>.) "He gave a talk on the implications of +electronic networks for postmodernism and the fin-de-siecle +aesthetic. It was content-free."</p> + +<hr> +Node:<a name="control-C">control-C</a>, Next:<a rel="next" href="#control-O">control-O</a>, Previous:<a rel="previous" href="#content-free">content-free</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>control-C</b> vi.</p> + +<p>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!"</p> + +<hr> +Node:<a name="control-O">control-O</a>, Next:<a rel="next" href="#control-Q">control-Q</a>, Previous:<a rel="previous" href="#control-C">control-C</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>control-O</b> vi.</p> + +<p>"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 +<b><a href="#control-S">control-S</a></b>.</p> + +<hr> +Node:<a name="control-Q">control-Q</a>, Next:<a rel="next" href="#control-S">control-S</a>, Previous:<a rel="previous" href="#control-O">control-O</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>control-Q</b> vi.</p> + +<p>"Resume." From the ASCII DC1 or <b><a href="#XON">XON</a></b> +character (the pronunciation /X-on/ is therefore also used), used +to undo a previous <b><a href="#control-S">control-S</a></b>.</p> + +<hr> +Node:<a name="control-S">control-S</a>, Next:<a rel="next" href="#ConwaysLaw">Conway's Law</a>, Previous:<a rel="previous" +href="#control-Q">control-Q</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>control-S</b> vi.</p> + +<p>"Stop talking for a second." From the ASCII DC3 or XOFF +character (the pronunciation /X-of/ is therefore also used). +Control-S differs from <b><a href="#control-O">control-O</a></b> +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.</p> + +<hr> +Node:<a name="ConwaysLaw">Conway's Law</a>, Next:<a rel="next" href="#cookbook">cookbook</a>, Previous:<a rel="previous" +href="#control-S">control-S</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>Conway's Law</b> prov.</p> + +<p>The rule that the organization of the software and the +organization of the software team will be congruent; commonly +stated as "If you have four groups working on a compiler, you'll +get a 4-pass compiler". The original statement was more general, +"Organizations which design systems are constrained to produce +designs which are copies of the communication structures of these +organizations." This first appeared in the April 1968 issue of +<b><a href="#Datamation">Datamation</a></b>. Compare <b><a href="#SNAFUprinciple">SNAFU principle</a></b>.</p> + +<p>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.)</p> + +<p>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."</p> + +<hr> +Node:<a name="cookbook">cookbook</a>, Next:<a rel="next" href="#cookedmode">cooked mode</a>, Previous:<a rel="previous" +href="#ConwaysLaw">Conway's Law</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cookbook</b> n.</p> + +<p>[from amateur electronics and radio] A book of small code +segments that the reader can use to do various <b><a href="#magic">magic</a></b> things in programs. One current example is +the "<b><a href="#PostScript">PostScript</a></b> Language +Tutorial and Cookbook" by Adobe Systems, Inc (Addison-Wesley, +ISBN 0-201-10179-3), also known as the <b><a href="#BlueBook">Blue Book</a></b> which has recipes for things +like wrapping text around arbitrary curves and making 3D fonts. +Cookbooks, slavishly followed, can lead one into <b><a href="#voodooprogramming">voodoo programming</a></b>, but are +useful for hackers trying to <b><a href="#monkeyup">monkey +up</a></b> small programs in unknown languages. This function is +analogous to the role of phrasebooks in human languages.</p> + +<hr> +Node:<a name="cookedmode">cooked mode</a>, Next:<a rel="next" +href="#cookie">cookie</a>, Previous:<a rel="previous" href="#cookbook">cookbook</a>, Up:<a rel="up" href="#chap03">= +C =</a> <br> + + +<p><b>cooked mode</b> n.</p> + +<p>[Unix, by opposition from <b><a href="#rawmode">raw +mode</a></b>] The normal character-input mode, with interrupts +enabled and with erase, kill and other special-character +interpretations performed directly by the tty driver. Oppose +<b><a href="#rawmode">raw mode</a></b>, <b><a href="#raremode">rare mode</a></b>. 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.</p> + +<hr> +Node:<a name="cookie">cookie</a>, Next:<a rel="next" href="#cookiebear">cookie bear</a>, Previous:<a rel="previous" +href="#cookedmode">cooked mode</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cookie</b> n.</p> + +<p>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 <b><a href="#magiccookie">magic +cookie</a></b>; see also <b><a href="#fortunecookie">fortune +cookie</a></b>. Now mainstream in the specific sense of +web-browser cookies.</p> + +<hr> +Node:<a name="cookiebear">cookie bear</a>, Next:<a rel="next" +href="#cookiefile">cookie file</a>, Previous:<a rel="previous" +href="#cookie">cookie</a>, Up:<a rel="up" href="#chap03">= +C =</a> <br> + + +<p><b>cookie bear</b> n. obs.</p> + +<p>Original term, pre-Sesame-Street, for what is now universally +called a <b><a href="#cookiemonster">cookie monster</a></b>. A +correspondent observes "In those days, hackers were actually +getting their yucks from<small>...</small>sit down +now<small>...</small>Andy Williams. Yes, <i>that</i> 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<small>...</small>NEVER!!!' And the bear would fall down. +Great stuff."</p> + +<hr> +Node:<a name="cookiefile">cookie file</a>, Next:<a rel="next" +href="#cookiejar">cookie jar</a>, Previous:<a rel="previous" +href="#cookiebear">cookie bear</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cookie file</b> n.</p> + +<p>A collection of <b><a href="#fortunecookie">fortune +cookie</a></b>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.</p> + +<hr> +Node:<a name="cookiejar">cookie jar</a>, Next:<a rel="next" +href="#cookiemonster">cookie monster</a>, Previous:<a rel="previous" href="#cookiefile">cookie file</a>, Up:<a rel="up" +href="#chap03">= C =</a> <br> + + +<p><b>cookie jar</b> n.</p> + +<p>An area of memory set aside for storing <b><a href="#cookie">cookie</a></b>s. Most commonly heard in the Atari ST +community; many useful ST programs record their presence by +storing a distinctive <b><a href="#magicnumber">magic +number</a></b> in the jar. Programs can inquire after the +presence or otherwise of other programs by searching the contents +of the jar.</p> + +<hr> +Node:<a name="cookiemonster">cookie monster</a>, Next:<a rel="next" href="#copiousfreetime">copious free time</a>, +Previous:<a rel="previous" href="#cookiejar">cookie jar</a>, +Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cookie monster</b> n.</p> + +<p>[from the children's TV program "Sesame Street"] Any of a +family of early (1970s) hacks reported on <b><a href="#TOPS-10">TOPS-10</a></b>, <b><a href="#ITS">ITS</a></b>, <b><a +href="#Multics">Multics</a></b>, and elsewhere that would lock up +either the victim's terminal (on a time-sharing machine) or the +<b><a href="#console">console</a></b> (on a batch <b><a href="#mainframe">mainframe</a></b>), repeatedly demanding "I WANT A +COOKIE". The required responses ranged in complexity from +"COOKIE" through "HAVE A COOKIE" and upward. Folklorist Jan +Brunvand (see <b><a href="#FOAF">FOAF</a></b>) has described +these programs as urban legends (implying they probably never +existed) but they existed, all right, in several different +versions. See also <b><a href="#wabbit">wabbit</a></b>. +Interestingly, the term `cookie monster' appears to be a <b><a +href="#retcon">retcon</a></b>; the original term was <b><a href="#cookiebear">cookie bear</a></b>.</p> + +<hr> +Node:<a name="copiousfreetime">copious free time</a>, +Next:<a rel="next" href="#copper">copper</a>, Previous:<a rel="previous" href="#cookiemonster">cookie monster</a>, Up:<a +rel="up" href="#chap03">= C =</a> <br> + + +<p><b>copious free time</b> n.</p> + +<p>[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 <b><a +href="#chrome">chrome</a></b>, or the stroking of <b><a href="#suit">suit</a></b>s. "I'll get back to him on that feature in +my copious free time."</p> + +<hr> +Node:<a name="copper">copper</a>, Next:<a rel="next" href="#copyprotection">copy protection</a>, Previous:<a rel="previous" href="#copiousfreetime">copious free time</a>, +Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>copper</b> n.</p> + +<p>Conventional electron-carrying network cable with a core +conductor of copper -- or aluminum! Opposed to <b><a href="#lightpipe">light pipe</a></b> or, say, a short-range +microwave link.</p> + +<hr> +Node:<a name="copyprotection">copy protection</a>, Next:<a +rel="next" href="#copybroke">copybroke</a>, Previous:<a rel="previous" href="#copper">copper</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>copy protection</b> n.</p> + +<p>A class of methods for preventing incompetent pirates from +stealing software and legitimate customers from using it. +Considered silly.</p> + +<hr> +Node:<a name="copybroke">copybroke</a>, Next:<a rel="next" href="#copycenter">copycenter</a>, Previous:<a rel="previous" href="#copyprotection">copy protection</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>copybroke</b> /kop'ee-brohk/ adj.</p> + +<p>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. <b><a href="#copywronged">copywronged</a></b>. 2. Copy-protected software +which is unusable because of some bit-rot or bug that has +confused the anti-piracy check. See also <b><a href="#copyprotection">copy protection</a></b>.</p> + +<hr> +Node:<a name="copycenter">copycenter</a>, Next:<a rel="next" +href="#copyleft">copyleft</a>, Previous:<a rel="previous" href="#copybroke">copybroke</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>copycenter</b> n.</p> + +<p>[play on `copyright' and `copyleft'] 1. The copyright notice +carried by the various flavors of freeware BSD. According to Kirk +McKusick at BSDCon 1999: "The way it was characterized +politically, you had copyright, which is what the big companies +use to lock everything up; you had copyleft, which is free +software's way of making sure they can't lock it up; and then +Berkeley had what we called "copycenter", which is "take it down +to the copy center and make as many copies as you want".</p> + +<hr> +Node:<a name="copyleft">copyleft</a>, Next:<a rel="next" href="#copyparty">copyparty</a>, Previous:<a rel="previous" href="#copycenter">copycenter</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>copyleft</b> /kop'ee-left/ n.</p> + +<p>[play on `copyright'] 1. The copyright notice (`General Public +License') carried by <b><a href="#GNU">GNU</a></b> <b><a href="#EMACS">EMACS</a></b> and other Free Software Foundation +software, granting reuse and reproduction rights to all comers +(but see also <b><a href="#GeneralPublicVirus">General +Public Virus</a></b>). 2. By extension, any copyright notice +intended to achieve similar aims.</p> + +<hr> +Node:<a name="copyparty">copyparty</a>, Next:<a rel="next" href="#copywronged">copywronged</a>, Previous:<a rel="previous" href="#copyleft">copyleft</a>, Up:<a rel="up" href="#chap03">= +C =</a> <br> + + +<p><b>copyparty</b> n.</p> + +<p>[C64/amiga <b><a href="#demoscene">demoscene</a></b> ]A +computer party organized so demosceners can meet other in real +life, and to facilitate software copying (mostly pirated +software). The copyparty has become less common as the Internet +makes communication easier. The demoscene has gradually evolved +the <b><a href="#demoparty">demoparty</a></b> to replace it.</p> + +<hr> +Node:<a name="copywronged">copywronged</a>, Next:<a rel="next" +href="#core">core</a>, Previous:<a rel="previous" href="#copyparty">copyparty</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>copywronged</b> /kop'ee-rongd/ adj.</p> + +<p>[play on `copyright'] Syn. for <b><a href="#copybroke">copybroke</a></b>.</p> + +<hr> +Node:<a name="core">core</a>, Next:<a rel="next" href="#corecancer">core cancer</a>, Previous:<a rel="previous" +href="#copywronged">copywronged</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>core</b> n.</p> + +<p>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 <b><a href="#coredump">core dump</a></b> +and the `core image' or `core file' produced by one are terms in +favor. Some varieties of Commonwealth hackish prefer <b><a href="#store">store</a></b>.</p> + +<hr> +Node:<a name="corecancer">core cancer</a>, Next:<a rel="next" +href="#coredump">core dump</a>, Previous:<a rel="previous" +href="#core">core</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>core cancer</b> n.</p> + +<p>[rare] A process that exhibits a slow but inexorable resource +<b><a href="#leak">leak</a></b> -- like a cancer, it kills by +crowding out productive `tissue'.</p> + +<hr> +Node:<a name="coredump">core dump</a>, Next:<a rel="next" +href="#coreleak">core leak</a>, Previous:<a rel="previous" +href="#corecancer">core cancer</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>core dump</b> n.</p> + +<p>[common <b><a href="#IronAge">Iron Age</a></b> jargon, +preserved by Unix] 1. [techspeak] A copy of the contents of <b><a +href="#core">core</a></b>, 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 <b><a +href="#bits">bits</a></b>, sense 1). Hence, spewing all one knows +about a topic (syn. <b><a href="#braindump">brain +dump</a></b>), 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 <b><a href="#core">core</a></b>.</p> + +<hr> +Node:<a name="coreleak">core leak</a>, Next:<a rel="next" +href="#CoreWars">Core Wars</a>, Previous:<a rel="previous" +href="#coredump">core dump</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>core leak</b> n.</p> + +<p>Syn. <b><a href="#memoryleak">memory leak</a></b>.</p> + +<hr> +Node:<a name="CoreWars">Core Wars</a>, Next:<a rel="next" +href="#corge">corge</a>, Previous:<a rel="previous" href="#coreleak">core leak</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>Core Wars</b> n.</p> + +<p>A game between `assembler' programs in a machine or machine +simulator, where the objective is to kill your opponent's program +by overwriting it. Popularized in the 1980s by A. K. Dewdney's +column in "Scientific American" magazine, but described in +"Software Practice And Experience" a decade earlier. The game was +actually devised and played by Victor Vyssotsky, Robert Morris +Sr., and Doug McIlroy in the early 1960s (Dennis Ritchie is +sometimes incorrectly cited as a co-author, but was not +involved). Their original game was called `Darwin' and ran on a +IBM 7090 at Bell Labs. See <b><a href="#core">core</a></b>. For +information on the modern game, do a web search for the +`rec.games.corewar FAQ' or surf to the King Of The Hill site.</p> + +<hr> +Node:<a name="corge">corge</a>, Next:<a rel="next" href="#cosmicrays">cosmic rays</a>, Previous:<a rel="previous" +href="#CoreWars">Core Wars</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>corge</b> /korj/ n.</p> + +<p>[originally, the name of a cat] Yet another <b><a href="#metasyntacticvariable">metasyntactic variable</a></b>, +invented by Mike Gallaher and propagated by the <b><a href="#GOSMACS">GOSMACS</a></b> documentation. See <b><a href="#grault">grault</a></b>.</p> + +<hr> +Node:<a name="cosmicrays">cosmic rays</a>, Next:<a rel="next" +href="#coughanddie">cough and die</a>, Previous:<a rel="previous" href="#corge">corge</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cosmic rays</b> n.</p> + +<p>Notionally, the cause of <b><a href="#bitrot">bit +rot</a></b>. However, this is a semi-independent usage that may +be invoked as a humorous way to <b><a href="#handwave">handwave</a></b> away any minor <b><a href="#randomness">randomness</a></b> that doesn't seem worth the +bother of investigating. "Hey, Eric -- I just got a burst of +garbage on my <b><a href="#tube">tube</a></b>, where did that +come from?" "Cosmic rays, I guess." Compare <b><a href="#sunspots">sunspots</a></b>, <b><a href="#phaseofthemoon">phase of the moon</a></b>. 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).</p> + +<p>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.</p> + +<hr> +Node:<a name="coughanddie">cough and die</a>, Next:<a rel="next" href="#courier">courier</a>, Previous:<a rel="previous" +href="#cosmicrays">cosmic rays</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cough and die</b> v.</p> + +<p>Syn. <b><a href="#barf">barf</a></b>. 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 <b><a href="#die">die</a></b>, <b><a href="#diehorribly">die horribly</a></b>, <b><a href="#screamanddie">scream and die</a></b>.</p> + +<hr> +Node:<a name="courier">courier</a>, Next:<a rel="next" href="#coWorker">cow orker</a>, Previous:<a rel="previous" href="#coughanddie">cough and die</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>courier</b></p> + +<p>[BBS & cracker cultures] A person who distributes newly +cracked <b><a href="#warez">warez</a></b>, as opposed to a <b><a +href="#server">server</a></b> who makes them available for +download or a <b><a href="#leech">leech</a></b> who merely +downloads them. Hackers recognize this term but don't use it +themselves, as the act is not part of their culture. See also +<b><a href="#warezd00dz">warez d00dz</a></b>, <b><a href="#cracker">cracker</a></b>, <b><a href="#elite">elite</a></b>.</p> + +<hr> +Node:<a name="coWorker">cow orker</a>, Next:<a rel="next" +href="#cowboy">cowboy</a>, Previous:<a rel="previous" href="#courier">courier</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>cow orker</b> n.</p> + +<p>[Usenet] n. fortuitous typo for co-worker, widely used in +Usenet, with perhaps a hint that orking cows is illegal. This +term was popularized by Scott Adams (the creator of <b><a href="#Dilbert">Dilbert</a></b>) but already appears in the January +1996 version of the <b><a href="#scarydevilmonastery">scary +devil monastery</a></b> FAQ. There are plausible reports that it +was in use on <i>talk.bizarre</i> as early as 1992. Compare <b><a +href="#hing">hing</a></b>, <b><a href="#grilf">grilf</a></b>, +<b><a href="#filk">filk</a></b>, <b><a href="#newsfroup">newsfroup</a></b>.</p> + +<hr> +Node:<a name="cowboy">cowboy</a>, Next:<a rel="next" href="#CPM">CP/M</a>, Previous:<a rel="previous" href="#coWorker">cow orker</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cowboy</b> n.</p> + +<p>[Sun, from William Gibson's <b><a href="#cyberpunk">cyberpunk</a></b> SF] Synonym for <b><a href="#hacker">hacker</a></b>. It is reported that at Sun this word is +often said with reverence.</p> + +<hr> +Node:<a name="CPM">CP/M</a>, Next:<a rel="next" href="#CPUWars">CPU Wars</a>, Previous:<a rel="previous" href="#cowboy">cowboy</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>CP/M</b> /C-P-M/ n.</p> + +<p>[Control Program/Monitor; later <b><a href="#retcon">retcon</a></b>ned to Control Program for +Microcomputers] An early microcomputer <b><a href="#OS">OS</a></b> 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 <b><a href="#DEC">DEC</a></b> +operating systems such as <b><a href="#TOPS-10">TOPS-10</a></b>, +OS/8, RSTS, and RSX-11. See <b><a href="#MS-DOS">MS-DOS</a></b>, +<b><a href="#operatingsystem">operating system</a></b>.</p> + +<hr> +Node:<a name="CPUWars">CPU Wars</a>, Next:<a rel="next" href="#crack">crack</a>, Previous:<a rel="previous" href="#CPM">CP/M</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>CPU Wars</b> /C-P-U worz/ n.</p> + +<p>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 <b><a href="#ADVENT">ADVENT</a></b> and the immortal line "Eat flaming +death, minicomputer mongrels!" (uttered, of course, by an IPM +stormtrooper). The whole shebang is now available on the Web.</p> + +<p>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 <b><a href="#eatflamingdeath">eat flaming +death</a></b>.</p> + +<hr> +Node:<a name="crack">crack</a>, Next:<a rel="next" href="#crackroot">crack root</a>, Previous:<a rel="previous" href="#CPUWars">CPU Wars</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>crack</b></p> + +<p>[warez d00dz] 1. v. To break into a system (compare <b><a +href="#cracker">cracker</a></b>). 2. v. Action of removing the +copy protection from a commercial program. People who write +cracks consider themselves challenged by the copy protection +measures. They will often do it as much to show that they are +smarter than the developper who designed the copy protection +scheme than to actually copy the program. 3. n. A program, +instructions or patch used to remove the copy protection of a +program or to uncripple features from a demo/time limited +program. 4. An <b><a href="#exploit">exploit</a></b>.</p> + +<hr> +Node:<a name="crackroot">crack root</a>, Next:<a rel="next" +href="#cracker">cracker</a>, Previous:<a rel="previous" href="#crack">crack</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>crack root</b> v.</p> + +<p>[very common] To defeat the security system of a Unix machine +and gain <b><a href="#root">root</a></b> privileges thereby; see +<b><a href="#cracking">cracking</a></b>.</p> + +<hr> +Node:<a name="cracker">cracker</a>, Next:<a rel="next" href="#cracking">cracking</a>, Previous:<a rel="previous" href="#crackroot">crack root</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cracker</b> n.</p> + +<p>One who breaks security on a system. Coined ca. 1985 by +hackers in defense against journalistic misuse of <b><a href="#hacker">hacker</a></b> (q.v., sense 8). An earlier attempt to +establish `worm' in this sense around 1981-82 on Usenet was +largely a failure.</p> + +<p>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 <b><a href="#larvalstage">larval stage</a></b> 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).</p> + +<p>Thus, there is far less overlap between hackerdom and +crackerdom than the <b><a href="#mundane">mundane</a></b> 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 +<i>themselves</i> as hackers, most true hackers consider them a +separate and lower form of life.</p> + +<p>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 <b><a href="#losing">losing</a></b>. Some other reasons crackers are looked +down on are discussed in the entries on <b><a href="#cracking">cracking</a></b> and <b><a href="#phreaking">phreaking</a></b>. See also <b><a href="#samurai">samurai</a></b>, <b><a href="#darksidehacker">dark-side hacker</a></b>, and <b><a href="#hackerethic">hacker ethic</a></b>. For a portrait of the +typical teenage cracker, see <b><a href="#warezd00dz">warez +d00dz</a></b>.</p> + +<hr> +Node:<a name="cracking">cracking</a>, Next:<a rel="next" href="#crank">crank</a>, Previous:<a rel="previous" href="#cracker">cracker</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>cracking</b> n.</p> + +<p>[very common] The act of breaking into a computer system; what +a <b><a href="#cracker">cracker</a></b> 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.</p> + +<hr> +Node:<a name="crank">crank</a>, Next:<a rel="next" href="#crapplet">crapplet</a>, Previous:<a rel="previous" href="#cracking">cracking</a>, Up:<a rel="up" href="#chap03">= +C =</a> <br> + + +<p><b>crank</b> vt.</p> + +<p>[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."</p> + +<hr> +Node:<a name="crapplet">crapplet</a>, Next:<a rel="next" href="#CrApTeX">CrApTeX</a>, Previous:<a rel="previous" href="#crank">crank</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>crapplet</b> n.</p> + +<p>[portmanteau, crap + applet] A worthless applet, esp. a Java +widget attached to a web page that doesn't work or even crashes +your browser. Also spelled `craplet'.</p> + +<hr> +Node:<a name="CrApTeX">CrApTeX</a>, Next:<a rel="next" href="#crash">crash</a>, Previous:<a rel="previous" href="#crapplet">crapplet</a>, Up:<a rel="up" href="#chap03">= +C =</a> <br> + + +<p><b>CrApTeX</b> /krap'tekh/ n.</p> + +<p>[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. <b><a href="#troff">troff</a></b>) and because +(particularly if the standard Computer Modern fonts are used) it +generates vast output files. See <b><a href="#religiousissues">religious issues</a></b>, <b><a href="#TeX">TeX</a></b>.</p> + +<hr> +Node:<a name="crash">crash</a>, Next:<a rel="next" href="#crashandburn">crash and burn</a>, Previous:<a rel="previous" href="#CrApTeX">CrApTeX</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>crash</b></p> + +<p>1. n. A sudden, usually drastic failure. Most often said of +the <b><a href="#system">system</a></b> (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 <b><a href="#luser">luser</a></b>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 <b><a href="#down">down</a></b>. Also used transitively to indicate the +cause of the crash (usually a person or a program, or both). +"Those idiots playing <b><a href="#SPACEWAR">SPACEWAR</a></b> +crashed the system." 3. vi. Sometimes said of people hitting the +sack after a long <b><a href="#hackingrun">hacking +run</a></b>; see <b><a href="#gronkout">gronk out</a></b>.</p> + +<hr> +Node:<a name="crashandburn">crash and burn</a>, Next:<a +rel="next" href="#crawlinghorror">crawling horror</a>, +Previous:<a rel="previous" href="#crash">crash</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>crash and burn</b> vi.,n.</p> + +<p>A spectacular crash, in the mode of the conclusion of the +car-chase scene in the movie "Bullitt" and many subsequent +imitators (compare <b><a href="#diehorribly">die +horribly</a></b>). 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 <b><a href="#beta">beta</a></b> 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.</p> + +<hr> +Node:<a name="crawlinghorror">crawling horror</a>, Next:<a +rel="next" href="#cray">cray</a>, Previous:<a rel="previous" +href="#crashandburn">crash and burn</a>, Up:<a rel="up" +href="#chap03">= C =</a> <br> + + +<p><b>crawling horror</b> n.</p> + +<p>Ancient crufty hardware or software that is kept obstinately +alive by forces beyond the control of the hackers at a site. Like +<b><a href="#dustydeck">dusty deck</a></b> or <b><a href="#gonkulator">gonkulator</a></b>, 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<small>...</small>." Compare <b><a href="#WOMBAT">WOMBAT</a></b>.</p> + +<hr> +Node:<a name="cray">cray</a>, Next:<a rel="next" href="#crayinstability">cray instability</a>, Previous:<a rel="previous" href="#crawlinghorror">crawling horror</a>, Up:<a +rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cray</b> /kray/ n.</p> + +<p>1. (properly, capitalized) One of the line of supercomputers +designed by Cray Research. 2. Any supercomputer at all. 3. The +<b><a href="#canonical">canonical</a></b> <b><a href="#number-crunching">number-crunching</a></b> machine.</p> + +<p>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.</p> + +<hr> +Node:<a name="crayinstability">cray instability</a>, Next:<a +rel="next" href="#crayola">crayola</a>, Previous:<a rel="previous" href="#cray">cray</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cray instability</b> n.</p> + +<p>1. A shortcoming of a program or algorithm that manifests +itself only when a large problem is being run on a powerful +machine (see <b><a href="#cray">cray</a></b>). 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 PDP-series machines) but +which break down badly when exposed to a Cray's unique `rounding' +rules.</p> + +<hr> +Node:<a name="crayola">crayola</a>, Next:<a rel="next" href="#crayolabooks">crayola books</a>, Previous:<a rel="previous" +href="#crayinstability">cray instability</a>, Up:<a rel="up" +href="#chap03">= C =</a> <br> + + +<p><b>crayola</b> /kray-oh'l*/ n.</p> + +<p>A super-mini or -micro computer that provides some reasonable +percentage of supercomputer performance for an unreasonably low +price. Might also be a <b><a href="#killermicro">killer +micro</a></b>.</p> + +<hr> +Node:<a name="crayolabooks">crayola books</a>, Next:<a rel="next" href="#crayon">crayon</a>, Previous:<a rel="previous" +href="#crayola">crayola</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>crayola books</b> n.</p> + +<p>The <b><a href="#rainbowseries">rainbow series</a></b> of +National Computer Security Center (NCSC) computer security +standards (see <b><a href="#OrangeBook">Orange Book</a></b>). +Usage: humorous and/or disparaging.</p> + +<hr> +Node:<a name="crayon">crayon</a>, Next:<a rel="next" href="#creationism">creationism</a>, Previous:<a rel="previous" href="#crayolabooks">crayola books</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>crayon</b> n.</p> + +<p>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. Formerly, anyone who worked for Cray +Research; since the buyout by SGI, anyone they inherited from +Cray. 3. A <b><a href="#computron">computron</a></b> (sense 2) +that participates only in <b><a href="#number-crunching">number-crunching</a></b>. 4. 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.</p> + +<hr> +Node:<a name="creationism">creationism</a>, Next:<a rel="next" +href="#creep">creep</a>, Previous:<a rel="previous" href="#crayon">crayon</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>creationism</b> n.</p> + +<p>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 <b><a href="#management">management</a></b>, they are +generally ignored.</p> + +<hr> +Node:<a name="creep">creep</a>, Next:<a rel="next" href="#creepingelegance">creeping elegance</a>, Previous:<a rel="previous" href="#creationism">creationism</a>, Up:<a rel="up" +href="#chap03">= C =</a> <br> + + +<p><b>creep</b> v.</p> + +<p>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.</p> + +<hr> +Node:<a name="creepingelegance">creeping elegance</a>, Next:<a +rel="next" href="#creepingfeaturism">creeping featurism</a>, +Previous:<a rel="previous" href="#creep">creep</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>creeping elegance</b> n.</p> + +<p>Describes a tendency for parts of a design to become <b><a +href="#elegant">elegant</a></b> 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 <b><a href="#RealWorld">Real +World</a></b>. See also <b><a href="#creepingfeaturism">creeping featurism</a></b>, <b><a href="#second-systemeffect">second-system effect</a></b>, <b><a +href="#tense">tense</a></b>.</p> + +<hr> +Node:<a name="creepingfeaturism">creeping featurism</a>, +Next:<a rel="next" href="#creepingfeaturitis">creeping +featuritis</a>, Previous:<a rel="previous" href="#creepingelegance">creeping elegance</a>, Up:<a rel="up" +href="#chap03">= C =</a> <br> + + +<p><b>creeping featurism</b> /kree'ping fee'chr-izm/ n.</p> + +<p>[common] 1. Describes a systematic tendency to load more <b><a +href="#chrome">chrome</a></b> and <b><a href="#feature">feature</a></b>s onto systems at the expense of +whatever elegance they may have possessed when originally +designed. See also <b><a href="#feepingcreaturism">feeping +creaturism</a></b>. "You know, the main problem with <b><a href="#BSD">BSD</a></b> 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 <b><a href="#feature">feature</a></b>.) 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 <small>...</small> and then +another <small>...</small> and another<small>...</small>. 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 <b><a href="#second-systemeffect">second-system +effect</a></b>. See also <b><a href="#creepingelegance">creeping elegance</a></b>.</p> + +<hr> +Node:<a name="creepingfeaturitis">creeping featuritis</a>, +Next:<a rel="next" href="#cretin">cretin</a>, Previous:<a rel="previous" href="#creepingfeaturism">creeping featurism</a>, +Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>creeping featuritis</b> /kree'ping fee'-chr-i:`t*s/ n.</p> + +<p>Variant of <b><a href="#creepingfeaturism">creeping +featurism</a></b>, 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'.)</p> + +<hr> +Node:<a name="cretin">cretin</a>, Next:<a rel="next" href="#cretinous">cretinous</a>, Previous:<a rel="previous" href="#creepingfeaturitis">creeping featuritis</a>, Up:<a rel="up" +href="#chap03">= C =</a> <br> + + +<p><b>cretin</b> /kret'in/ or /kree'tn/ n.</p> + +<p>Congenital <b><a href="#loser">loser</a></b>; 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.</p> + +<hr> +Node:<a name="cretinous">cretinous</a>, Next:<a rel="next" href="#crippleware">crippleware</a>, Previous:<a rel="previous" href="#cretin">cretin</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>cretinous</b> /kret'n-*s/ or /kreet'n-*s/ adj.</p> + +<p>Wrong; stupid; non-functional; very poorly designed. Also used +pejoratively of people. See <b><a href="#dreadhighbitdisease">dread high-bit disease</a></b> for +an example. Approximate synonyms: <b><a href="#bletcherous">bletcherous</a></b>, <b><a href="#bagbiting">bagbiting</a></b> <b><a href="#losing">losing</a></b>, <b><a href="#brain-damaged">brain-damaged</a></b>.</p> + +<hr> +Node:<a name="crippleware">crippleware</a>, Next:<a rel="next" +href="#criticalmass">critical mass</a>, Previous:<a rel="previous" href="#cretinous">cretinous</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>crippleware</b> n.</p> + +<p>1. [common] Software that has some important functionality +deliberately removed, so as to entice potential users to pay for +a working version. 2. [Cambridge] Variety of <b><a href="#guiltware">guiltware</a></b> that exhorts you to donate to some +charity (compare <b><a href="#careware">careware</a></b>, <b><a +href="#nagware">nagware</a></b>). 3. Hardware deliberately +crippled, which can be upgraded to a more expensive model by a +trivial change (e.g., cutting a jumper).</p> + +<p>An excellent example of crippleware (sense 3) is Intel's 486SX +chip, which is a standard 486DX chip with the co-processor diked +out (in some early versions it was present but disabled). To +upgrade, you buy a complete 486DX chip with <i>working</i> +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?</p> + +<hr> +Node:<a name="criticalmass">critical mass</a>, Next:<a rel="next" href="#crlf">crlf</a>, Previous:<a rel="previous" href="#crippleware">crippleware</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>critical mass</b> n.</p> + +<p>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 <b><a href="#epsilon">epsilon</a></b> bugs. +(This malady has many causes: <b><a href="#creepingfeaturism">creeping featurism</a></b>, 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.</p> + +<hr> +Node:<a name="crlf">crlf</a>, Next:<a rel="next" href="#crock">crock</a>, Previous:<a rel="previous" href="#criticalmass">critical mass</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>crlf</b> /ker'l*f/, sometimes /kru'l*f/ or /C-R-L-F/ n.</p> + +<p>(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 <b><a href="#newline">newline</a></b>, <b><a href="#terpri">terpri</a></b>. +Under <b><a href="#Unix">Unix</a></b> influence this usage has +become less common (Unix uses a bare line feed as its +`CRLF').</p> + +<hr> +Node:<a name="crock">crock</a>, Next:<a rel="next" href="#cross-post">cross-post</a>, Previous:<a rel="previous" href="#crlf">crlf</a>, Up:<a rel="up" href="#chap03">= C =</a> +<br> + + +<p><b>crock</b> n.</p> + +<p>[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 <code>make(1)</code>, which returns code 139 for a +process that dies due to <b><a href="#segfault">segfault</a></b>). 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 <b><a +href="#TheStoryofMel">The Story of Mel</a></b> in +Appendix A.) Many crocks have a tightly woven, almost completely +unmodifiable structure. See <b><a href="#kluge">kluge</a></b>, +<b><a href="#brittle">brittle</a></b>. The adjectives `crockish' +and `crocky', and the nouns `crockishness' and `crockitude', are +also used.</p> + +<hr> +Node:<a name="cross-post">cross-post</a>, Next:<a rel="next" +href="#crossload">crossload</a>, Previous:<a rel="previous" href="#crock">crock</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>cross-post</b> vi.</p> + +<p>[Usenet; very common] 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 <b><a href="#followup">followup</a></b> articles to go to inappropriate +newsgroups when people respond to only one part of the original +posting.</p> + +<hr> +Node:<a name="crossload">crossload</a>, Next:<a rel="next" href="#crudware">crudware</a>, Previous:<a rel="previous" href="#cross-post">cross-post</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>crossload</b> v.,n.</p> + +<p>[proposed, by analogy with <b><a href="#upload">upload</a></b> +and <b><a href="#download">download</a></b>] To move files +between machines on a peer-to-peer network of nodes that act as +both servers and clients for a distributed file store. Esp. +appropriate for ananonymized networks like Gnutella and +Freenet.</p> + +<hr> +Node:<a name="crudware">crudware</a>, Next:<a rel="next" href="#cruft">cruft</a>, Previous:<a rel="previous" href="#crossload">crossload</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>crudware</b> /kruhd'weir/ n.</p> + +<p>Pejorative term for the hundreds of megabytes of low-quality +<b><a href="#freeware">freeware</a></b> circulated by user's +groups and BBS systems in the micro-hobbyist world. "Yet +<i>another</i> set of disk catalog utilities for <b><a href="#MS-DOS">MS-DOS</a></b>? What crudware!"</p> + +<hr> +Node:<a name="cruft">cruft</a>, Next:<a rel="next" href="#crufttogether">cruft together</a>, Previous:<a rel="previous" href="#crudware">crudware</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cruft</b> /kruhft/</p> + +<p>[very common; back-formation from <b><a href="#crufty">crufty</a></b>] 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 <b><a +href="#hand-hacking">hand-hacking</a></b>). 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".</p> + +<hr> +Node:<a name="crufttogether">cruft together</a>, Next:<a rel="next" href="#cruftsmanship">cruftsmanship</a>, Previous:<a rel="previous" href="#cruft">cruft</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cruft together</b> vt.</p> + +<p>(also `cruft up') To throw together something ugly but +temporarily workable. Like vt. <b><a href="#klugeup">kluge +up</a></b>, 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 <b><a href="#hacktogether">hack together</a></b>, <b><a href="#hackup">hack up</a></b>, <b><a href="#klugeup">kluge +up</a></b>, <b><a href="#crufty">crufty</a></b>.</p> + +<hr> +Node:<a name="cruftsmanship">cruftsmanship</a>, Next:<a rel="next" href="#crufty">crufty</a>, Previous:<a rel="previous" +href="#crufttogether">cruft together</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cruftsmanship</b> /kruhfts'm*n-ship / n.</p> + +<p>[from <b><a href="#cruft">cruft</a></b>] The antithesis of +craftsmanship.</p> + +<hr> +Node:<a name="crufty">crufty</a>, Next:<a rel="next" href="#crumb">crumb</a>, Previous:<a rel="previous" href="#cruftsmanship">cruftsmanship</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>crufty</b> /kruhf'tee/ adj.</p> + +<p>[very common; origin unknown; poss. from `crusty' or `cruddy'] +1. Poorly built, possibly over-complex. The <b><a href="#canonical">canonical</a></b> example is "This is standard old +crufty <b><a href="#DEC">DEC</a></b> 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 <b><a href="#frob">frob</a></b>); 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, <b><a href="#random">random</a></b> +cruft)."</p> + +<p>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.</p> + +<hr> +Node:<a name="crumb">crumb</a>, Next:<a rel="next" href="#crunch">crunch</a>, Previous:<a rel="previous" href="#crufty">crufty</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>crumb</b> n.</p> + +<p>Two binary digits; a <b><a href="#quad">quad</a></b>. Larger +than a <b><a href="#bit">bit</a></b>, smaller than a <b><a href="#nybble">nybble</a></b>. Considered silly. Syn. <b><a href="#tayste">tayste</a></b>. General discussion of such terms is +under <b><a href="#nybble">nybble</a></b>.</p> + +<hr> +Node:<a name="crunch">crunch</a>, Next:<a rel="next" href="#cryppie">cryppie</a>, Previous:<a rel="previous" href="#crumb">crumb</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>crunch</b> 1. vi.</p> + +<p>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 <b><a href="#number-crunching">number-crunching</a></b>." +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 <b><a +href="#number-crunching">number-crunching</a></b>.) See <b><a +href="#compress">compress</a></b>. 3. n. The character +<code>#</code>. Used at XEROX and CMU, among other places. See +<b><a href="#ASCII">ASCII</a></b>. 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). <b><a href="#ObfuscatedCContest">Obfuscated C Contest</a></b> entries +are often crunched; see the first example under that entry.</p> + +<hr> +Node:<a name="cryppie">cryppie</a>, Next:<a rel="next" href="#CTSS">CTSS</a>, Previous:<a rel="previous" href="#crunch">crunch</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>cryppie</b> /krip'ee/ n.</p> + +<p>A cryptographer. One who hacks or implements cryptographic +software or hardware.</p> + +<hr> +Node:<a name="CTSS">CTSS</a>, Next:<a rel="next" href="#cube">cube</a>, Previous:<a rel="previous" href="#cryppie">cryppie</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>CTSS</b> /C-T-S-S/ n.</p> + +<p>Compatible Time-Sharing System. An early (1963) experiment in +the design of interactive time-sharing operating systems, +ancestral to <b><a href="#Multics">Multics</a></b>, <b><a href="#Unix">Unix</a></b>, and <b><a href="#ITS">ITS</a></b>. The name +<b><a href="#ITS">ITS</a></b> (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.</p> + +<hr> +Node:<a name="cube">cube</a>, Next:<a rel="next" href="#cubing">cubing</a>, Previous:<a rel="previous" href="#CTSS">CTSS</a>, Up:<a rel="up" href="#chap03">= C =</a> +<br> + + +<p><b>cube</b> n.</p> + +<p>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).</p> + +<hr> +Node:<a name="cubing">cubing</a>, Next:<a rel="next" href="#cupHolder">cup holder</a>, Previous:<a rel="previous" href="#cube">cube</a>, Up:<a rel="up" href="#chap03">= C =</a> +<br> + + +<p><b>cubing</b> vi.</p> + +<p>[parallel with `tubing'] 1. Hacking on an IPSC (Intel Personal +SuperComputer) hypercube. "Louella's gone cubing +<i>again</i>!!" 2. Hacking Rubik's Cube or related puzzles, +either physically or mathematically. 3. An indescribable form of +self-torture (see sense 1 or 2).</p> + +<hr> +Node:<a name="cupHolder">cup holder</a>, Next:<a rel="next" +href="#cursordippedinX">cursor dipped in X</a>, +Previous:<a rel="previous" href="#cubing">cubing</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cup holder</b> n.</p> + +<p>The tray of a CD-ROM drive, or by extension the CD drive +itself. So called because of a common tech support legend about +the idiot who called to complain that the cup holder on his +computer broke. A joke program was once distributed around the +net called "cupholder.exe", which when run simply extended the CD +drive tray. The humor of this was of course lost on people whose +drive had a slot or a caddy instead.</p> + +<hr> +Node:<a name="cursordippedinX">cursor dipped in X</a>, +Next:<a rel="next" href="#cuspy">cuspy</a>, Previous:<a rel="previous" href="#cupHolder">cup holder</a>, Up:<a rel="up" +href="#chap03">= C =</a> <br> + + +<p><b>cursor dipped in X</b> n.</p> + +<p>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 <b><a href="#nastygram">nastygram</a></b>! He must've had his cursor dipped +in acid when he wrote that one!"</p> + +<hr> +Node:<a name="cuspy">cuspy</a>, Next:<a rel="next" href="#cutatape">cut a tape</a>, Previous:<a rel="previous" +href="#cursordippedinX">cursor dipped in X</a>, Up:<a +rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cuspy</b> /kuhs'pee/ adj.</p> + +<p>[WPI: from the <b><a href="#DEC">DEC</a></b> 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 <b><a href="#rude">rude</a></b>. 3. [NYU] Said of an attractive woman, +especially one regarded as available. Implies a certain +curvaceousness.</p> + +<hr> +Node:<a name="cutatape">cut a tape</a>, Next:<a rel="next" +href="#cybercrud">cybercrud</a>, Previous:<a rel="previous" href="#cuspy">cuspy</a>, Up:<a rel="up" href="#chap03">= C +=</a> <br> + + +<p><b>cut a tape</b> vi.</p> + +<p>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'.</p> + +<p>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.</p> + +<hr> +Node:<a name="cybercrud">cybercrud</a>, Next:<a rel="next" href="#cyberpunk">cyberpunk</a>, Previous:<a rel="previous" href="#cutatape">cut a tape</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cybercrud</b> /si:'ber-kruhd/ n.</p> + +<p>1. [coined by Ted Nelson] Obfuscatory tech-talk. Verbiage with +a high <b><a href="#MEGO">MEGO</a></b> 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 radix-64 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.</p> + +<hr> +Node:<a name="cyberpunk">cyberpunk</a>, Next:<a rel="next" href="#cyberspace">cyberspace</a>, Previous:<a rel="previous" href="#cybercrud">cybercrud</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cyberpunk</b> /si:'ber-puhnk/ n.,adj.</p> + +<p>[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 <b><a href="#Bibliography">Bibliography</a></b> 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ïve and tremendously stimulating. Gibson's work was widely +imitated, in particular by the short-lived but innovative "Max +Headroom" TV series. See <b><a href="#cyberspace">cyberspace</a></b>, <b><a href="#ice">ice</a></b>, +<b><a href="#jackIn">jack in</a></b>, <b><a href="#goflatline">go flatline</a></b>.</p> + +<p>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 <i>doing</i> 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.</p> + +<hr> +Node:<a name="cyberspace">cyberspace</a>, Next:<a rel="next" +href="#cycle">cycle</a>, Previous:<a rel="previous" href="#cyberpunk">cyberpunk</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cyberspace</b> /si:'br-spays`/ n.</p> + +<p>1. Notional `information-space' loaded with visual cues and +navigable with brain-computer interfaces called `cyberspace +decks'; a characteristic prop of <b><a href="#cyberpunk">cyberpunk</a></b> SF. Serious efforts to construct +<b><a href="#virtualreality">virtual reality</a></b> +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 <b><a href="#thenetwork">the network</a></b>). 2. +The Internet or <b><a href="#Matrix">Matrix</a></b> (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 +<b><a href="#wannabee">wannabee</a></b> or outsider. Oppose <b><a +href="#meatspace">meatspace</a></b>. 3. Occasionally, the +metaphoric location of the mind of a person in <b><a href="#hackmode">hack mode</a></b>. 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.</p> + +<hr> +Node:<a name="cycle">cycle</a>, Next:<a rel="next" href="#cyclecrunch">cycle crunch</a>, Previous:<a rel="previous" +href="#cyberspace">cyberspace</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cycle</b></p> + +<p>1. n. The basic unit of computation. What every hacker wants +more of (noted hacker Bill Gosper described 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 <b><a href="#cycle">cycle</a></b>. 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 <i>human</i> 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. <b><a href="#bounce">bounce</a></b> (sense 4), <b><a href="#120reset">120 reset</a></b>; from the phrase `cycle power'. +"Cycle the machine again, that serial port's still hung."</p> + +<hr> +Node:<a name="cyclecrunch">cycle crunch</a>, Next:<a rel="next" href="#cycledrought">cycle drought</a>, Previous:<a +rel="previous" href="#cycle">cycle</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cycle crunch</b> n.,obs.</p> + +<p>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 <b><a href="#thrash">thrash</a></b>. 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, and are +far more likely to complain of `bandwidth crunch' on their shared +networks rather than cycle crunch.</p> + +<hr> +Node:<a name="cycledrought">cycle drought</a>, Next:<a rel="next" href="#cycleofreincarnation">cycle of +reincarnation</a>, Previous:<a rel="previous" href="#cyclecrunch">cycle crunch</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cycle drought</b> n.</p> + +<p>A scarcity of cycles. It may be due to a <b><a href="#cyclecrunch">cycle crunch</a></b>, but it could also occur +because part of the computer is temporarily not working, leaving +fewer cycles to go around. "The <b><a href="#highmoby">high +moby</a></b> is <b><a href="#down">down</a></b>, so we're running +with only half the usual amount of memory. There will be a cycle +drought until it's fixed."</p> + +<hr> +Node:<a name="cycleofreincarnation">cycle of +reincarnation</a>, Next:<a rel="next" href="#cycleserver">cycle server</a>, Previous:<a rel="previous" +href="#cycledrought">cycle drought</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cycle of reincarnation</b> n.</p> + +<p>See <b><a href="#wheelofreincarnation">wheel of +reincarnation</a></b>.</p> + +<hr> +Node:<a name="cycleserver">cycle server</a>, Next:<a rel="next" href="#cypherpunk">cypherpunk</a>, Previous:<a rel="previous" href="#cycleofreincarnation">cycle of +reincarnation</a>, Up:<a rel="up" href="#chap03">= C =</a> +<br> + + +<p><b>cycle server</b> n.</p> + +<p>A powerful machine that exists primarily for running large +compute-, disk-, or memory-intensive jobs (more formally called a +`compute server'). Implies that interactive tasks such as editing +are done on other machines on the network, such as +workstations.</p> + +<hr> +Node:<a name="cypherpunk">cypherpunk</a>, Next:<a rel="next" +href="#CNK">C|N>K</a>, Previous:<a rel="previous" href="#cycleserver">cycle server</a>, Up:<a rel="up" href="#chap03">= C =</a> <br> + + +<p><b>cypherpunk</b> n.</p> + +<p> +[from <b><a href="#cyberpunk">cyberpunk</a></b>] 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 <b><a +href="#tentacle">tentacle</a></b>. +</p> + +<hr> +Node:<a name="CNK">C|N>K</a>, Next:<a rel="next" href="#DCPowerLab">D. C. Power Lab</a>, Previous:<a rel="previous" href="#cypherpunk">cypherpunk</a>, Up:<a rel="up" +href="#chap03">= C =</a> <br> + + +<p><b>C|N>K</b> n.</p> + +<p>[Usenet] Coffee through Nose to Keyboard; that is, "I laughed +so hard I <b><a href="#snarf">snarf</a></b>ed my coffee onto my +keyboard.". Common on <i>alt.fan.pratchett</i> and <b><a href="#scarydevilmonastery">scary devil monastery</a></b>; +recognized elsewhere. The Acronymphomania +FAQ on <i>alt.fan.pratchett</i> recognizes variants such as +T|N>K = `Tea through Nose to Keyboard' and C|N>S = `Coffee +through Nose to Screen'.</p> + +<hr> +Node:<a name="chap04">= D =</a>, Next:<a rel="next" href="#chap05">= E =</a>, Previous:<a rel="previous" href="#chap03">= C =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= D =</h2> + +<ul> +<li><a href="#DCPowerLab">D. C. Power Lab</a>:</li> + +<li><a href="#daemon">daemon</a>:</li> + +<li><a href="#daemonbook">daemon book</a>:</li> + +<li><a href="#dahmum">dahmum</a>:</li> + +<li><a href="#dancingfrog">dancing frog</a>:</li> + +<li><a href="#danglingpointer">dangling pointer</a>:</li> + +<li><a href="#darksidehacker">dark-side hacker</a>:</li> + +<li><a href="#Datamation">Datamation</a>:</li> + +<li><a href="#DAU">DAU</a>:</li> + +<li><a href="#DavetheResurrector">Dave the +Resurrector</a>:</li> + +<li><a href="#daymode">day mode</a>:</li> + +<li><a href="#dd">dd</a>:</li> + +<li><a href="#DDT">DDT</a>:</li> + +<li><a href="#de-rezz">de-rezz</a>:</li> + +<li><a href="#dead">dead</a>:</li> + +<li><a href="#deadbeefattack">dead beef attack</a>:</li> + +<li><a href="#deadcode">dead code</a>:</li> + +<li><a href="#deadlink">dead link</a>:</li> + +<li><a href="#DEADBEEF">DEADBEEF</a>:</li> + +<li><a href="#deadlock">deadlock</a>:</li> + +<li><a href="#deadlyembrace">deadly embrace</a>:</li> + +<li><a href="#deathcode">death code</a>:</li> + +<li><a href="#DeathSquare">Death Square</a>:</li> + +<li><a href="#DeathStar">Death Star</a>:</li> + +<li><a href="#DEC">DEC</a>:</li> + +<li><a href="#DEC">DEC</a>:</li> + +<li><a href="#DECWars">DEC Wars</a>:</li> + +<li><a href="#decay">decay</a>:</li> + +<li><a href="#deckle">deckle</a>:</li> + +<li><a href="#DED">DED</a>:</li> + +<li><a href="#deephackmode">deep hack mode</a>:</li> + +<li><a href="#deepmagic">deep magic</a>:</li> + +<li><a href="#deepspace">deep space</a>:</li> + +<li><a href="#defenestration">defenestration</a>:</li> + +<li><a href="#definedas">defined as</a>:</li> + +<li><a href="#dehose">dehose</a>:</li> + +<li><a href="#deletia">deletia</a>:</li> + +<li><a href="#deliminator">deliminator</a>:</li> + +<li><a href="#delint">delint</a>:</li> + +<li><a href="#delta">delta</a>:</li> + +<li><a href="#demented">demented</a>:</li> + +<li><a href="#demigod">demigod</a>:</li> + +<li><a href="#demo">demo</a>:</li> + +<li><a href="#demomode">demo mode</a>:</li> + +<li><a href="#demoeffect">demoeffect</a>:</li> + +<li><a href="#demogroup">demogroup</a>:</li> + +<li><a href="#demon">demon</a>:</li> + +<li><a href="#demondialer">demon dialer</a>:</li> + +<li><a href="#demoparty">demoparty</a>:</li> + +<li><a href="#demoscene">demoscene</a>:</li> + +<li><a href="#dentro">dentro</a>:</li> + +<li><a href="#depeditate">depeditate</a>:</li> + +<li><a href="#deprecated">deprecated</a>:</li> + +<li><a href="#derf">derf</a>:</li> + +<li><a href="#deservestolose">deserves to lose</a>:</li> + +<li><a href="#deskcheck">desk check</a>:</li> + +<li><a href="#despew">despew</a>:</li> + +<li><a href="#DevilBook">Devil Book</a>:</li> + +<li><a href="#slashdevslashnull">/dev/null</a>:</li> + +<li><a href="#dicklessworkstation">dickless +workstation</a>:</li> + +<li><a href="#dictionaryflame">dictionary flame</a>:</li> + +<li><a href="#diddle">diddle</a>:</li> + +<li><a href="#die">die</a>:</li> + +<li><a href="#diehorribly">die horribly</a>:</li> + +<li><a href="#diff">diff</a>:</li> + +<li><a href="#digit">digit</a>:</li> + +<li><a href="#dike">dike</a>:</li> + +<li><a href="#Dilbert">Dilbert</a>:</li> + +<li><a href="#ding">ding</a>:</li> + +<li><a href="#dink">dink</a>:</li> + +<li><a href="#dinosaur">dinosaur</a>:</li> + +<li><a href="#dinosaurpen">dinosaur pen</a>:</li> + +<li><a href="#dinosaursmating">dinosaurs mating</a>:</li> + +<li><a href="#dirtball">dirtball</a>:</li> + +<li><a href="#dirtypower">dirty power</a>:</li> + +<li><a href="#disclaimer">disclaimer</a>:</li> + +<li><a href="#Discordianism">Discordianism</a>:</li> + +<li><a href="#diskfarm">disk farm</a>:</li> + +<li><a href="#displayhack">display hack</a>:</li> + +<li><a href="#dispress">dispress</a>:</li> + +<li><a href="#DissociatedPress">Dissociated Press</a>:</li> + +<li><a href="#distribution">distribution</a>:</li> + +<li><a href="#distro">distro</a>:</li> + +<li><a href="#disusered">disusered</a>:</li> + +<li><a href="#doprotocol">do protocol</a>:</li> + +<li><a href="#doc">doc</a>:</li> + +<li><a href="#documentation">documentation</a>:</li> + +<li><a href="#dodgy">dodgy</a>:</li> + +<li><a href="#dogcow">dogcow</a>:</li> + +<li><a href="#dogfood">dogfood</a>:</li> + +<li><a href="#dogpile">dogpile</a>:</li> + +<li><a href="#dogwash">dogwash</a>:</li> + +<li><a href="#domainist">domainist</a>:</li> + +<li><a href="#Dontdothatthen">Don't do that +then!</a>:</li> + +<li><a href="#dongle">dongle</a>:</li> + +<li><a href="#dongle-disk">dongle-disk</a>:</li> + +<li><a href="#donuts">donuts</a>:</li> + +<li><a href="#doorstop">doorstop</a>:</li> + +<li><a href="#DoSattack">DoS attack</a>:</li> + +<li><a href="#dotfile">dot file</a>:</li> + +<li><a href="#doublebucky">double bucky</a>:</li> + +<li><a href="#doubledsig">doubled sig</a>:</li> + +<li><a href="#down">down</a>:</li> + +<li><a href="#download">download</a>:</li> + +<li><a href="#DP">DP</a>:</li> + +<li><a href="#DPB">DPB</a>:</li> + +<li><a href="#DPer">DPer</a>:</li> + +<li><a href="#DrFredMbogo">Dr. Fred Mbogo</a>:</li> + +<li><a href="#dragon">dragon</a>:</li> + +<li><a href="#DragonBook">Dragon Book</a>:</li> + +<li><a href="#drain">drain</a>:</li> + +<li><a href="#dreadhighbitdisease">dread high-bit +disease</a>:</li> + +<li><a href="#DreadQuestionmarkDisease">Dread Questionmark +Disease</a>:</li> + +<li><a href="#DRECNET">DRECNET</a>:</li> + +<li><a href="#driver">driver</a>:</li> + +<li><a href="#droid">droid</a>:</li> + +<li><a href="#drone">drone</a>:</li> + +<li><a href="#droolproofpaper">drool-proof paper</a>:</li> + +<li><a href="#droponthefloor">drop on the +floor</a>:</li> + +<li><a href="#drop-ins">drop-ins</a>:</li> + +<li><a href="#drop-outs">drop-outs</a>:</li> + +<li><a href="#drugged">drugged</a>:</li> + +<li><a href="#drum">drum</a>:</li> + +<li><a href="#drunkmousesyndrome">drunk mouse +syndrome</a>:</li> + +<li><a href="#dubdubdub">dub dub dub</a>:</li> + +<li><a href="#Duffsdevice">Duff's device</a>:</li> + +<li><a href="#dumbterminal">dumb terminal</a>:</li> + +<li><a href="#dumbassattack">dumbass attack</a>:</li> + +<li><a href="#dumbeddown">dumbed down</a>:</li> + +<li><a href="#dump">dump</a>:</li> + +<li><a href="#dumpsterdiving">dumpster diving</a>:</li> + +<li><a href="#dupkiller">dup killer</a>:</li> + +<li><a href="#duploop">dup loop</a>:</li> + +<li><a href="#dustydeck">dusty deck</a>:</li> + +<li><a href="#DWIM">DWIM</a>:</li> + +<li><a href="#dynner">dynner</a>:</li> +</ul> + +<hr> +Node:<a name="DCPowerLab">D. C. Power Lab</a>, Next:<a +rel="next" href="#daemon">daemon</a>, Previous:<a rel="previous" +href="#CNK">C|N>K</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>D. C. Power Lab</b> n.</p> + +<p>The former site of <b><a href="#SAIL">SAIL</a></b>. 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 <b><a href="#MarginalHacks">Marginal +Hacks</a></b>.</p> + +<hr> +Node:<a name="daemon">daemon</a>, Next:<a rel="next" href="#daemonbook">daemon book</a>, Previous:<a rel="previous" +href="#DCPowerLab">D. C. Power Lab</a>, Up:<a rel="up" +href="#chap04">= D =</a> <br> + + +<p><b>daemon</b> /day'mn/ or /dee'mn/ n.</p> + +<p>[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 <b><a +href="#ITS">ITS</a></b> writing a file on the <b><a href="#LPT">LPT</a></b> 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 +<b><a href="#LPT">LPT</a></b>. 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.</p> + +<p>Daemon and <b><a href="#demon">demon</a></b> are often used +interchangeably, but seem to have distinct connotations. The term +`daemon' was introduced to computing by <b><a href="#CTSS">CTSS</a></b> people (who pronounced it /dee'mon/) and +used it to refer to what ITS called a <b><a href="#dragon">dragon</a></b>; the prototype was a program called +DAEMON that automatically made tape backups of the file system. +Although the meaning and the pronunciation have drifted, we think +this glossary reflects current (2000) usage.</p> + +<hr> +Node:<a name="daemonbook">daemon book</a>, Next:<a rel="next" +href="#dahmum">dahmum</a>, Previous:<a rel="previous" href="#daemon">daemon</a>, Up:<a rel="up" href="#chap04">= D +=</a> <br> + + +<p><b>daemon book</b> n.</p> + +<p>"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); or "The Design and Implementation of the 4.4 +BSD Operating System" by Marshall Kirk McKusick, Keith Bostic, +Michael J. Karels and John S. Quarterman (Addison-Wesley Longman, +1996, SBN 0-201-54979-4) Either of the standard reference books +on the internals of <b><a href="#BSD">BSD</a></b> Unix. So called +because the covers have a picture depicting a little devil (a +visual play on <b><a href="#daemon">daemon</a></b>) in sneakers, +holding a pitchfork (referring to one of the characteristic +features of Unix, the <code>fork(2)</code> system call). Also +known as the <b><a href="#DevilBook">Devil Book</a></b>.</p> + +<hr> +Node:<a name="dahmum">dahmum</a>, Next:<a rel="next" href="#dancingfrog">dancing frog</a>, Previous:<a rel="previous" +href="#daemonbook">daemon book</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dahmum</b> /dah'mum/ n.</p> + +<p>[Usenet] The material of which protracted <b><a href="#flamewarr">flame war</a></b>s, especially those about +operating systems, is composed. Homeomorphic to <b><a href="#spam">spam</a></b>. The term `dahmum' is derived from the name +of a militant <b><a href="#OSslash2">OS/2</a></b> advocate, and +originated when an extensively crossposted OS/2-versus-<b><a +href="#Linux">Linux</a></b> debate was fed through <b><a href="#DissociatedPress">Dissociated Press</a></b>.</p> + +<hr> +Node:<a name="dancingfrog">dancing frog</a>, Next:<a rel="next" href="#danglingpointer">dangling pointer</a>, +Previous:<a rel="previous" href="#dahmum">dahmum</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dancing frog</b> n.</p> + +<p>[Vancouver area] A problem that occurs on a computer that will +not reappear while anyone else is watching. From the classic +Warner Brothers cartoon "One Froggy Evening", featuring a dancing +and singing Michigan J. Frog that just croaks when anyone else is +around (now the WB network mascot).</p> + +<hr> +Node:<a name="danglingpointer">dangling pointer</a>, Next:<a +rel="next" href="#darksidehacker">dark-side hacker</a>, +Previous:<a rel="previous" href="#dancingfrog">dancing +frog</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dangling pointer</b> n.</p> + +<p>[common] 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 <b><a href="#deadlink">dead link</a></b>.</p> + +<hr> +Node:<a name="darksidehacker">dark-side hacker</a>, Next:<a +rel="next" href="#Datamation">Datamation</a>, Previous:<a rel="previous" href="#danglingpointer">dangling pointer</a>, Up:<a +rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dark-side hacker</b> n.</p> + +<p>A criminal or malicious hacker; a <b><a href="#cracker">cracker</a></b>. 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 <b><a href="#samurai">samurai</a></b>.</p> + +<hr> +Node:<a name="Datamation">Datamation</a>, Next:<a rel="next" +href="#DAU">DAU</a>, Previous:<a rel="previous" href="#darksidehacker">dark-side hacker</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>Datamation</b> /day`t*-may'sh*n/ n.</p> + +<p>A magazine that many hackers assume all <b><a href="#suit">suit</a></b>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 <b><a href="#COMEFROM">COME FROM</a></b> 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 <b><a href="#suit">suit</a></b>-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.</p> + +<p>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 <b><a href="#BOFH">BOFH</a></b>).</p> + +<hr> +Node:<a name="DAU">DAU</a>, Next:<a rel="next" href="#DavetheResurrector">Dave the Resurrector</a>, Previous:<a +rel="previous" href="#Datamation">Datamation</a>, Up:<a rel="up" +href="#chap04">= D =</a> <br> + + +<p><b>DAU</b> /dow/ n.</p> + +<p>[German FidoNet] German acronym for Dümmster +Anzunehmender User (stupidest imaginable user). From the +engineering-slang GAU for Grösster 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 <b><a href="#cretin">cretin</a></b>, +<b><a href="#fool">fool</a></b>, <b><a href="#loser">loser</a></b> and <b><a href="#weasel">weasel</a></b>.</p> + +<hr> +Node:<a name="DavetheResurrector">Dave the Resurrector</a>, +Next:<a rel="next" href="#daymode">day mode</a>, Previous:<a +rel="previous" href="#DAU">DAU</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>Dave the Resurrector</b> n.</p> + +<p>[Usenet; also abbreviated DtR] A <b><a href="#cancelbot">cancelbot</a></b> that cancels cancels. Dave the +Resurrector originated when some <b><a href="#spam">spam</a></b>-spewers decided to try to impede +spam-fighting by wholesale cancellation of anti-spam coordination +messages in the <i>news.admin.net-abuse.usenet</i> newsgroup.</p> + +<hr> +Node:<a name="daymode">day mode</a>, Next:<a rel="next" href="#dd">dd</a>, Previous:<a rel="previous" href="#DavetheResurrector">Dave the Resurrector</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>day mode</b> n.</p> + +<p>See <b><a href="#phase">phase</a></b> (sense 1). Used of +people only.</p> + +<hr> +Node:<a name="dd">dd</a>, Next:<a rel="next" href="#DDT">DDT</a>, +Previous:<a rel="previous" href="#daymode">day mode</a>, Up:<a +rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dd</b> /dee-dee/ vt.</p> + +<p>[Unix: from IBM <b><a href="#JCL">JCL</a></b>] Equivalent to +<b><a href="#cat">cat</a></b> or <b><a href="#BLT">BLT</a></b>. +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 <code>dd</code> the +root partition onto a tape, then use the boot PROM to load it +back on to a new disk". The Unix <code>dd(1)</code> 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 <code>dd(1)</code> has been <b><a +href="#deprecated">deprecated</a></b> for a long time (though it +has no exact replacement). The term has been displaced by <b><a +href="#BLT">BLT</a></b> or simple English `copy'.</p> + +<hr> +Node:<a name="DDT">DDT</a>, Next:<a rel="next" href="#de-rezz">de-rezz</a>, Previous:<a rel="previous" href="#dd">dd</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>DDT</b> /D-D-T/ n.</p> + +<p>[from the insecticide para-dichloro-diphenyl-trichloroethene] +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 <code>adb</code>, +<code>sdb</code>, <code>dbx</code>, or <code>gdb</code>. 2. [ITS] +Under MIT's fabled <b><a href="#ITS">ITS</a></b> operating +system, DDT (running under the alias HACTRN, a six-letterism for +`Hack Translator') was also used as the <b><a href="#shell">shell</a></b> or top level command language used to +execute other programs. 3. Any one of several specific DDTs +(sense 1) supported on early <b><a href="#DEC">DEC</a></b> +hardware and CP/M. The PDP-10 Reference Handbook (1969) contained +a footnote on the first page of the documentation for DDT that +illuminates the origin of the term:</p> + +<blockquote>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.</blockquote> + +<p>(The `tape' referred to was, incidentally, not magnetic but +paper.) Sadly, this quotation was removed from later editions of +the handbook after the <b><a href="#suit">suit</a></b>s took over +and <b><a href="#DEC">DEC</a></b> became much more +`businesslike'.</p> + +<p>The history above is known to many old-time hackers. But +there's more: Peter Samson, compiler of the original <b><a href="#TMRC">TMRC</a></b> 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).</p> + +<hr> +Node:<a name="de-rezz">de-rezz</a>, Next:<a rel="next" href="#dead">dead</a>, Previous:<a rel="previous" href="#DDT">DDT</a>, +Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>de-rezz</b> /dee-rez'/</p> + +<p>[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 +<i>fictional</i> 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.</p> + +<hr> +Node:<a name="dead">dead</a>, Next:<a rel="next" href="#deadbeefattack">dead beef attack</a>, Previous:<a rel="previous" href="#de-rezz">de-rezz</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dead</b> adj.</p> + +<p>1. Non-functional; <b><a href="#down">down</a></b>; <b><a +href="#crash">crash</a></b>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 <b><a href="#deadcode">dead code</a></b>.</p> + +<hr> +Node:<a name="deadbeefattack">dead beef attack</a>, Next:<a +rel="next" href="#deadcode">dead code</a>, Previous:<a rel="previous" href="#dead">dead</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dead beef attack</b> n.</p> + +<p>[cypherpunks list, 1996] An attack on a public-key +cryptosystem consisting of publishing a key having the same ID as +another key (thus making it possible to spoof a user's identity +if recipients aren't careful about verifying keys). In PGP and +GPG the key ID is the last eight hex digits of (for RSA keys) the +product of two primes. The attack was demonstrated by creating a +key whose ID was 0xdeadbeef (see <b><a href="#DEADBEEF">DEADBEEF</a></b>).</p> + +<hr> +Node:<a name="deadcode">dead code</a>, Next:<a rel="next" +href="#deadlink">dead link</a>, Previous:<a rel="previous" +href="#deadbeefattack">dead beef attack</a>, Up:<a rel="up" +href="#chap04">= D =</a> <br> + + +<p><b>dead code</b> n.</p> + +<p>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 <b><a href="#softwarerot">software +rot</a></b>); a good compiler should report dead code so a +maintainer can think about what it means. (Sometimes it simply +means that an <i>extremely</i> defensive programmer has +inserted <b><a href="#cannothappen">can't happen</a></b> tests +which really can't happen -- yet.) Syn. <b><a href="#grunge">grunge</a></b>. See also <b><a href="#dead">dead</a></b>, and <b><a href="#TheStoryofMel">The Story of Mel</a></b>.</p> + +<hr> +Node:<a name="deadlink">dead link</a>, Next:<a rel="next" +href="#DEADBEEF">DEADBEEF</a>, Previous:<a rel="previous" href="#deadcode">dead code</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dead link</b> n.</p> + +<p>[very common] 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 <b><a href="#danglingpointer">dangling pointer</a></b>, <b><a href="#linkrot">link rot</a></b>.</p> + +<hr> +Node:<a name="DEADBEEF">DEADBEEF</a>, Next:<a rel="next" href="#deadlock">deadlock</a>, Previous:<a rel="previous" href="#deadlink">dead link</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>DEADBEEF</b> /ded-beef/ n.</p> + +<p>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 <b><a href="#heisenbug">heisenbug</a></b>s into <b><a href="#Bohrbug">Bohr bug</a></b>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 <b><a href="#fool">fool</a></b> and <b><a +href="#deadbeefattack">dead beef attack</a></b>.</p> + +<hr> +Node:<a name="deadlock">deadlock</a>, Next:<a rel="next" href="#deadlyembrace">deadly embrace</a>, Previous:<a rel="previous" href="#DEADBEEF">DEADBEEF</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>deadlock</b> n.</p> + +<p>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 <b><a href="#deadlyembrace">deadly embrace</a></b>. 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.</p> + +<hr> +Node:<a name="deadlyembrace">deadly embrace</a>, Next:<a rel="next" href="#deathcode">death code</a>, Previous:<a rel="previous" href="#deadlock">deadlock</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>deadly embrace</b> n.</p> + +<p>Same as <b><a href="#deadlock">deadlock</a></b>, though +usually used only when exactly two processes are involved. This +is the more popular term in Europe, while <b><a href="#deadlock">deadlock</a></b> predominates in the United +States.</p> + +<hr> +Node:<a name="deathcode">death code</a>, Next:<a rel="next" +href="#DeathSquare">Death Square</a>, Previous:<a rel="previous" href="#deadlyembrace">deadly embrace</a>, Up:<a +rel="up" href="#chap04">= D =</a> <br> + + +<p><b>death code</b> n.</p> + +<p>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).</p> + +<p>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).</p> + +<hr> +Node:<a name="DeathSquare">Death Square</a>, Next:<a rel="next" href="#DeathStar">Death Star</a>, Previous:<a rel="previous" href="#deathcode">death code</a>, Up:<a rel="up" +href="#chap04">= D =</a> <br> + + +<p><b>Death Square</b> n.</p> + +<p>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 <b><a href="#DeathStar">Death Star</a></b>, because many people believed +Novell was bungling the lead in Unix systems exactly as AT&T +did for many years.</p> + +<hr> +Node:<a name="DeathStar">Death Star</a>, Next:<a rel="next" +href="#DEC">DEC</a>, Previous:<a rel="previous" href="#DeathSquare">Death Square</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>Death Star</b> n.</p> + +<p>[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 <b><a href="#BSD">BSD</a></b> 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.</p> + +<hr> +Node:<a name="DEC">DEC</a>, Next:<a rel="next" href="#DECWars">DEC Wars</a>, Previous:<a rel="previous" href="#DeathStar">Death Star</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>DEC</b> /dek/ n.</p> + +<p>1. v. Verbal (and only rarely written) shorthand for +<i>decrement</i>, i.e. `decrease by one'. Especially used by +assembly programmers, as many assembly languages have a +<code>dec</code> mnemonic. Antonym: <b><a href="#inc">inc</a></b>. 2. n. Commonly used abbreviation for Digital +Equipment Corporation, later deprecated by DEC itself in favor of +"Digital" and now entirely obsolete following the buyout by +Compaq. Before the <b><a href="#killermicro">killer +micro</a></b> 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 <b><a href="#TMRC">TMRC</a></b>). +Subsequently, the PDP-6, <b><a href="#PDP-10">PDP-10</a></b>, +<b><a href="#PDP-20">PDP-20</a></b>, PDP-11 and <b><a href="#VAX">VAX</a></b> 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 <b><a href="#silicon">silicon</a></b> got +cheap. Nevertheless, the microprocessor design tradition owes a +major 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 +was for many years still regarded with a certain wry affection +even among many hackers too young to have grown up on DEC +machines.</p> + +<p>DEC reclaimed some of its old reputation among techies in the +first half of the 1990s. The success of the Alpha, an +innovatively-designed and very high-performance <b><a href="#killermicro">killer micro</a></b>, helped a lot. So did +DEC's newfound receptiveness to Unix and open systems in general. +When Compaq acquired DEC at the end of 1998 there was some +concern that these gains would be lost along with the DEC +nameplate, but the merged company has so far turned out to be +culturally dominated by the ex-DEC side.</p> + +<hr> +Node:<a name="DECWars">DEC Wars</a>, Next:<a rel="next" href="#decay">decay</a>, Previous:<a rel="previous" href="#DEC">DEC</a>, Up:<a rel="up" href="#chap04">= D =</a> +<br> + + +<p><b>DEC Wars</b> n.</p> + +<p> +A 1983 <b><a href="#Usenet">Usenet</a></b> 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. +</p> + +<hr> +Node:<a name="decay">decay</a>, Next:<a rel="next" href="#deckle">deckle</a>, Previous:<a rel="previous" href="#DECWars">DEC Wars</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>decay</b> n.,vi</p> + +<p>[from nuclear physics] An automatic conversion which is +applied to most array-valued expressions in <b><a href="#C">C</a></b>; 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.</p> + +<hr> +Node:<a name="deckle">deckle</a>, Next:<a rel="next" href="#DED">DED</a>, Previous:<a rel="previous" href="#decay">decay</a>, Up:<a rel="up" href="#chap04">= D +=</a> <br> + + +<p><b>deckle</b> /dek'l/ n.</p> + +<p>[from dec- and <b><a href="#nybble">nybble</a></b>; the +original spelling seems to have been `decle'] Two <b><a href="#nickle">nickle</a></b>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 <b><a href="#nybble">nybble</a></b> for other such terms.</p> + +<hr> +Node:<a name="DED">DED</a>, Next:<a rel="next" href="#deephackmode">deep hack mode</a>, Previous:<a rel="previous" href="#deckle">deckle</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>DED</b> /D-E-D/ n.</p> + +<p>Dark-Emitting Diode (that is, a burned-out LED). Compare <b><a +href="#SED">SED</a></b>, <b><a href="#LER">LER</a></b>, <b><a +href="#write-onlymemory">write-only memory</a></b>. In the +early 1970s both Signetics and Texas instruments released DED +spec sheets as <b><a href="#AFJ">AFJ</a></b>s (suggested uses +included "as a power-off indicator").</p> + +<hr> +Node:<a name="deephackmode">deep hack mode</a>, Next:<a +rel="next" href="#deepmagic">deep magic</a>, Previous:<a rel="previous" href="#DED">DED</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>deep hack mode</b> n.</p> + +<p>See <b><a href="#hackmode">hack mode</a></b>.</p> + +<hr> +Node:<a name="deepmagic">deep magic</a>, Next:<a rel="next" +href="#deepspace">deep space</a>, Previous:<a rel="previous" +href="#deephackmode">deep hack mode</a>, Up:<a rel="up" +href="#chap04">= D =</a> <br> + + +<p><b>deep magic</b> n.</p> + +<p>[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 +<b><a href="#blackart">black art</a></b>); one that could only +have been composed by a true <b><a href="#wizard">wizard</a></b>. +Compiler optimization techniques and many aspects of <b><a href="#OS">OS</a></b> design used to be <b><a href="#deepmagic">deep magic</a></b>; many techniques in +cryptography, signal processing, graphics, and AI still are. +Compare <b><a href="#heavywizardry">heavy wizardry</a></b>. +Esp. found in comments of the form "Deep magic begins +here<small>...</small>". Compare <b><a href="#voodooprogramming">voodoo programming</a></b>.</p> + +<hr> +Node:<a name="deepspace">deep space</a>, Next:<a rel="next" +href="#defenestration">defenestration</a>, Previous:<a rel="previous" href="#deepmagic">deep magic</a>, Up:<a rel="up" +href="#chap04">= D =</a> <br> + + +<p><b>deep space</b> n.</p> + +<p>1. Describes the notional location of any program that has +gone <b><a href="#offthetrolley">off the trolley</a></b>. +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 <b><a href="#buzz">buzz</a></b>, <b><a href="#catatonic">catatonic</a></b>, <b><a href="#hyperspace">hyperspace</a></b>. 2. The metaphorical location of +a human so dazed and/or confused or caught up in some esoteric +form of <b><a href="#bogosity">bogosity</a></b> that he or she no +longer responds coherently to normal communication. Compare <b><a +href="#pageout">page out</a></b>.</p> + +<hr> +Node:<a name="defenestration">defenestration</a>, Next:<a rel="next" href="#definedas">defined as</a>, Previous:<a rel="previous" href="#deepspace">deep space</a>, Up:<a rel="up" +href="#chap04">= D =</a> <br> + + +<p><b>defenestration</b> n.</p> + +<p>[mythically from a traditional Czech assasination method, via +SF fandom] 1. Proper karmic retribution for an incorrigible +punster. "Oh, ghod, that was <i>awful</i>!" "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. The act of completely removing +Micro$oft Windows from a PC in favor of a better OS (typically +Linux).</p> + +<hr> +Node:<a name="definedas">defined as</a>, Next:<a rel="next" +href="#dehose">dehose</a>, Previous:<a rel="previous" href="#defenestration">defenestration</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>defined as</b> adj.</p> + +<p>In the role of, usually in an organization-chart sense. "Pete +is currently defined as bug prioritizer." Compare <b><a href="#logical">logical</a></b>.</p> + +<hr> +Node:<a name="dehose">dehose</a>, Next:<a rel="next" href="#deletia">deletia</a>, Previous:<a rel="previous" href="#definedas">defined as</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dehose</b> /dee-hohz/ vt.</p> + +<p>To clear a <b><a href="#hosed">hosed</a></b> condition.</p> + +<hr> +Node:<a name="deletia">deletia</a>, Next:<a rel="next" href="#deliminator">deliminator</a>, Previous:<a rel="previous" href="#dehose">dehose</a>, Up:<a rel="up" href="#chap04">= D +=</a> <br> + + +<p><b>deletia</b> n. /d*-lee'sha/</p> + +<p>[USENET; common] In an email reply, material omitted from the +quote of the original. Usually written rather than spoken; often +appears as a pseudo-tag or ellipsis in the body of the reply, as +"[deletia]" or "<deletia>".</p> + +<hr> +Node:<a name="deliminator">deliminator</a>, Next:<a rel="next" +href="#delint">delint</a>, Previous:<a rel="previous" href="#deletia">deletia</a>, Up:<a rel="up" href="#chap04">= D +=</a> <br> + + +<p><b>deliminator</b> /de-lim'-in-ay-t*r/ n.</p> + +<p>[portmanteau, delimiter + eliminate] A string or pattern used +to delimit text into fields, but which is itself eliminated from +the resulting list of fields. This jargon seems to have +originated among Perl hackers in connection with the Perl split() +function; however, it has been sighted in live use among Java and +even Visual Basic programmers.</p> + +<hr> +Node:<a name="delint">delint</a>, Next:<a rel="next" href="#delta">delta</a>, Previous:<a rel="previous" href="#deliminator">deliminator</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>delint</b> /dee-lint/ v. obs.</p> + +<p>To modify code to remove problems detected when <b><a href="#lint">lint</a></b>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.</p> + +<hr> +Node:<a name="delta">delta</a>, Next:<a rel="next" href="#demented">demented</a>, Previous:<a rel="previous" href="#delint">delint</a>, Up:<a rel="up" href="#chap04">= D +=</a> <br> + + +<p><b>delta</b> n.</p> + +<p>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 +<b><a href="#diff">diff</a></b>, especially a <b><a href="#diff">diff</a></b> 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 +<b><a href="#epsilon">epsilon</a></b>. The jargon usage of <b><a +href="#delta">delta</a></b> and <b><a href="#epsilon">epsilon</a></b> 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 <b><a href="#delta">delta</a></b> is often used, once <b><a href="#epsilon">epsilon</a></b> has been mentioned, to mean a quantity +that is slightly bigger than <b><a href="#epsilon">epsilon</a></b> 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'.</p> + +<hr> +Node:<a name="demented">demented</a>, Next:<a rel="next" href="#demigod">demigod</a>, Previous:<a rel="previous" href="#delta">delta</a>, Up:<a rel="up" href="#chap04">= D +=</a> <br> + + +<p><b>demented</b> adj.</p> + +<p>Yet another term of disgust used to describe a malfunctioning +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 <b><a href="#wonky">wonky</a></b>, <b><a href="#brain-damaged">brain-damaged</a></b>, <b><a href="#bozotic">bozotic</a></b>.</p> + +<hr> +Node:<a name="demigod">demigod</a>, Next:<a rel="next" href="#demo">demo</a>, Previous:<a rel="previous" href="#demented">demented</a>, Up:<a rel="up" href="#chap04">= +D =</a> <br> + + +<p><b>demigod</b> n.</p> + +<p>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 <b><a href="#Unix">Unix</a></b> and <b><a href="#C">C</a></b>), Richard M. Stallman (inventor of <b><a href="#EMACS">EMACS</a></b>), Larry Wall (inventor of <b><a href="#Perl">Perl</a></b>), Linus Torvalds (inventor of <b><a href="#Linux">Linux</a></b>), and most recently James Gosling +(inventor of Java, <b><a href="#NeWS">NeWS</a></b>, and <b><a +href="#GOSMACS">GOSMACS</a></b>) and Guido van Rossum (inventor +of <b><a href="#Python">Python</a></b>). 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 <b><a href="#net.god">net.god</a></b>, <b><a href="#true-hacker">true-hacker</a></b>.</p> + +<hr> +Node:<a name="demo">demo</a>, Next:<a rel="next" href="#demomode">demo mode</a>, Previous:<a rel="previous" href="#demigod">demigod</a>, Up:<a rel="up" href="#chap04">= D +=</a> <br> + + +<p><b>demo</b> /de'moh/</p> + +<p>[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 <b><a href="#test">test</a></b> 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 <i>exactly</i> 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. 4. [<b><a href="#demoscene">demoscene</a></b>] A sequence of <b><a href="#demoeffect">demoeffect</a></b>s (usually) combined with +self-composed music and hand-drawn ("pixelated") graphics. These +days (1997) usually built to attend a <b><a href="#compo">compo</a></b>. Often called `eurodemos' outside Europe, +as most of the <b><a href="#demoscene">demoscene</a></b> activity +seems to have gathered in northern Europe and especially +Scandinavia. See also <b><a href="#intro">intro</a></b>, <b><a +href="#dentro">dentro</a></b>.</p> + +<hr> +Node:<a name="demomode">demo mode</a>, Next:<a rel="next" +href="#demoeffect">demoeffect</a>, Previous:<a rel="previous" +href="#demo">demo</a>, Up:<a rel="up" href="#chap04">= D +=</a> <br> + + +<p><b>demo mode</b> n.</p> + +<p>1. [Sun] The state of being <b><a href="#headsdown">heads +down</a></b> in order to finish code in time for a <b><a href="#demo">demo</a></b>, 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 <b><a href="#app">app</a></b>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 <b><a href="#MicroslothWindows">Microsloth Windows</a></b>).</p> + +<hr> +Node:<a name="demoeffect">demoeffect</a>, Next:<a rel="next" +href="#demogroup">demogroup</a>, Previous:<a rel="previous" href="#demomode">demo mode</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>demoeffect</b> n.</p> + +<p>[<b><a href="#demoscene">demoscene</a></b>] What among hackers +is called a <b><a href="#displayhack">display hack</a></b>. +Classical effects include "plasma" (colorful mess), "keftales" +(x*x+y*y and other similar patterns, usually combined with +color-cycling), realtime fractals, realtime 3d graphics, etc. +Historically, demo effects have cheated as much as possible to +gain more speed and more complexity, using low-precision math and +masses of assembler code and building animation realtime are +three common tricks, but use of special hardware to fake effects +is a <b><a href="#GoodThing">Good Thing</a></b> on the +demoscene (though this is becoming less common as platforms like +the Amiga fade away).</p> + +<hr> +Node:<a name="demogroup">demogroup</a>, Next:<a rel="next" href="#demon">demon</a>, Previous:<a rel="previous" href="#demoeffect">demoeffect</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>demogroup</b> n.</p> + +<p>[<b><a href="#demoscene">demoscene</a></b>] A group of <b><a +href="#demo">demo</a></b> (sense 4) composers. Job titles within +a group include coders (the ones who write programs), graphicians +(the ones who painstakingly pixelate the fine art), musicians +(the music composers), <b><a href="#sysop">sysop</a></b>s, +traders/swappers (the ones who do the trading and other PR), and +organizers (in larger groups). It is not uncommon for one person +to do multiple jobs, but it has been observed that good coders +are rarely good composers and vice versa. [How odd. Musical +talent seems common among Internet/Unix hackers --ESR]</p> + +<hr> +Node:<a name="demon">demon</a>, Next:<a rel="next" href="#demondialer">demon dialer</a>, Previous:<a rel="previous" +href="#demogroup">demogroup</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>demon</b> n.</p> + +<p>1. [MIT] A portion of a program that is not invoked +explicitly, but that lies dormant waiting for some condition(s) +to occur. See <b><a href="#daemon">daemon</a></b>. 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 +<b><a href="#daemon">daemon</a></b> -- especially in the <b><a +href="#Unix">Unix</a></b> world, where the latter spelling and +pronunciation is considered mildly archaic.</p> + +<p>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.</p> + +<hr> +Node:<a name="demondialer">demon dialer</a>, Next:<a rel="next" href="#demoparty">demoparty</a>, Previous:<a rel="previous" href="#demon">demon</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>demon dialer</b> n.</p> + +<p>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 <b><a href="#BBS">BBS</a></b> line) or malign (that is, used as a prank or +denial-of-service attack). This term dates from the <b><a href="#bluebox">blue box</a></b> days of the 1970s and early 1980s +and is now semi-obsolescent among <b><a href="#phreaker">phreaker</a></b>s; see <b><a href="#wardialer">war +dialer</a></b> for its contemporary progeny.</p> + +<hr> +Node:<a name="demoparty">demoparty</a>, Next:<a rel="next" href="#demoscene">demoscene</a>, Previous:<a rel="previous" href="#demondialer">demon dialer</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>demoparty</b> n.</p> + +<p>[<b><a href="#demoscene">demoscene</a></b>] Aboveground +descendant of the <b><a href="#copyparty">copyparty</a></b>, with +emphasis shifted away from software piracy and towards <b><a +href="#compo">compo</a></b>s. Smaller demoparties, for 100 +persons or less, are held quite often, sometimes even once a +month, and usually last for one to two days. On the other end of +the scale, huge demo parties are held once a year (and four of +these have grown very large and occur annually - Assembly in +Finland, The Party in Denmark, The Gathering in Norway, and NAID +somewhere in north America). These parties usually last for three +to five days, have room for 3000-5000 people, and have a party +network with connection to the internet.</p> + +<hr> +Node:<a name="demoscene">demoscene</a>, Next:<a rel="next" href="#dentro">dentro</a>, Previous:<a rel="previous" href="#demoparty">demoparty</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>demoscene</b> /dem'oh-seen/</p> + +<p>[also `demo scene'] A culture of multimedia hackers located +primarily in Scandinavia and northern Europe. Demoscene folklore +recounts that when old-time <b><a href="#warezd00dz">warez +d00dz</a></b> cracked some piece of software they often added an +advertisement of in the beginning, usually containing colorful +<b><a href="#displayhack">display hack</a></b>s with greetings +to other cracking groups. The demoscene was born among people who +decided building these display hacks is more interesting than +hacking and began to build self-contained display hacks of +considerable elaboration and beauty (within the culture such a +hack is called a <b><a href="#demo">demo</a></b>). The split +seems to have happened at the end of the 1980s. As more of these +<b><a href="#demogroup">demogroup</a></b>s emerged, they started +to have <b><a href="#compo">compo</a></b>s at copying parties +(see <b><a href="#copyparty">copyparty</a></b>), which later +evolved to standalone events (see <b><a href="#demoparty">demoparty</a></b>). The demoscene has retained some +traits from the <b><a href="#warezd00dz">warez d00dz</a></b>, +including their style of handles and group names and some of +their jargon.</p> + +<p>Traditionally demos were written in assembly language, with +lots of smart tricks, self-modifying code, undocumented op-codes +and the like. Some time around 1995, people started coding demos +in C, and a couple of years after that, they also started using +Java.</p> + +<p>Ten years on (in 1998-1999), the demoscene is changing as its +original platforms (C64, Amiga, Spectrum, Atari ST, IBM PC under +DOS) die out and activity shifts towards Windows, Linux, and the +Internet. While deeply underground in the past, demoscene is +trying to get into the mainstream as accepted art form, and one +symptom of this is the commercialization of bigger demoparties. +Older demosceneers frown at this, but the majority think it's a +good direction. Many demosceneers end up working in the computer +game industry. Demoscene resource pages are available at http://www.oldskool.org/demos/explained/ +and http://www.scene.org/.</p> + +<hr> +Node:<a name="dentro">dentro</a>, Next:<a rel="next" href="#depeditate">depeditate</a>, Previous:<a rel="previous" href="#demoscene">demoscene</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dentro</b> /den'troh/</p> + +<p>[<b><a href="#demoscene">demoscene</a></b>] Combination of +<b><a href="#demo">demo</a></b> (sense 4) and <b><a href="#intro">intro</a></b>. Other name mixings include intmo, dentmo +etc. and are used usually when the authors are not quite sure +whether the program is a <b><a href="#demo">demo</a></b> or an +<b><a href="#intro">intro</a></b>. Special-purpose coinages like +wedtro (some member of a group got married), invtro (invitation +intro) etc. have also been sighted.</p> + +<hr> +Node:<a name="depeditate">depeditate</a>, Next:<a rel="next" +href="#deprecated">deprecated</a>, Previous:<a rel="previous" +href="#dentro">dentro</a>, Up:<a rel="up" href="#chap04">= +D =</a> <br> + + +<p><b>depeditate</b> /dee-ped'*-tayt/ n.</p> + +<p>[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.</p> + +<hr> +Node:<a name="deprecated">deprecated</a>, Next:<a rel="next" +href="#derf">derf</a>, Previous:<a rel="previous" href="#depeditate">depeditate</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>deprecated</b> adj.</p> + +<p>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 <b><a href="#dustydeck">dusty +deck</a></b>.</p> + +<p>[Usage note: don't confuse this word with `depreciate', or the +verb form `deprecate' with `depreciated`. They are different +words; see any dictionary for discussion.]</p> + +<hr> +Node:<a name="derf">derf</a>, Next:<a rel="next" href="#deservestolose">deserves to lose</a>, Previous:<a rel="previous" href="#deprecated">deprecated</a>, Up:<a rel="up" +href="#chap04">= D =</a> <br> + + +<p><b>derf</b> /derf/ v.,n.</p> + +<p>[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. It has been alleged that the term +originated as a reversal of the name of the gentleman who most +usually left himself vulnerable to it, who also happened to be +the head of the department that handled PLATO at the University +of Delaware.</p> + +<hr> +Node:<a name="deservestolose">deserves to lose</a>, Next:<a +rel="next" href="#deskcheck">desk check</a>, Previous:<a rel="previous" href="#derf">derf</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>deserves to lose</b> adj.</p> + +<p>[common] Said of someone who willfully does the <b><a href="#WrongThing">Wrong Thing</a></b>; humorously, if one uses a +feature known to be <b><a href="#marginal">marginal</a></b>. What +is meant is that one deserves the consequences of one's <b><a +href="#losing">losing</a></b> actions. "Boy, anyone who tries to +use <b><a href="#mess-dos">mess-dos</a></b> deserves to <b><a +href="#lose">lose</a></b>!" (<b><a href="#ITS">ITS</a></b> fans +used to say the same thing of <b><a href="#Unix">Unix</a></b>; +many still do.) See also <b><a href="#screw">screw</a></b>, <b><a +href="#chomp">chomp</a></b>, <b><a href="#bagbiter">bagbiter</a></b>.</p> + +<hr> +Node:<a name="deskcheck">desk check</a>, Next:<a rel="next" +href="#despew">despew</a>, Previous:<a rel="previous" href="#deservestolose">deserves to lose</a>, Up:<a rel="up" +href="#chap04">= D =</a> <br> + + +<p><b>desk check</b> n.,v.</p> + +<p>To <b><a href="#grovel">grovel</a></b> 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 <b><a href="#eyeballsearch">eyeball search</a></b>, <b><a href="#vdiff">vdiff</a></b>, <b><a href="#vgrep">vgrep</a></b>.</p> + +<hr> +Node:<a name="despew">despew</a>, Next:<a rel="next" href="#DevilBook">Devil Book</a>, Previous:<a rel="previous" href="#deskcheck">desk check</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>despew</b> /d*-spyoo'/ v.</p> + +<p>[Usenet] To automatically generate a large amount of garbage +to the net, esp. from an automated posting program gone wild. See +<b><a href="#ARMM">ARMM</a></b>.</p> + +<hr> +Node:<a name="DevilBook">Devil Book</a>, Next:<a rel="next" +href="#slashdevslashnull">/dev/null</a>, Previous:<a rel="previous" +href="#despew">despew</a>, Up:<a rel="up" href="#chap04">= +D =</a> <br> + + +<p><b>Devil Book</b> n.</p> + +<p>See <b><a href="#daemonbook">daemon book</a></b>, the term +preferred by its authors.</p> + +<hr> +Node:<a name="slashdevslashnull">/dev/null</a>, Next:<a rel="next" +href="#dicklessworkstation">dickless workstation</a>, +Previous:<a rel="previous" href="#DevilBook">Devil Book</a>, +Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>/dev/null</b> /dev-nuhl/ n.</p> + +<p>[from the Unix null device, used as a data sink] A notional +`black hole' in any information space being discussed, used, or +referred to. A controversial posting, for example, might end +"Kudos to rasputin@kremlin.org, flames to /dev/null". See <b><a +href="#bitbucket">bit bucket</a></b>.</p> + +<hr> +Node:<a name="dicklessworkstation">dickless workstation</a>, +Next:<a rel="next" href="#dictionaryflame">dictionary +flame</a>, Previous:<a rel="previous" href="#slashdevslashnull">/dev/null</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dickless workstation</b> n.</p> + +<p>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 <b><a href="#boot">boot</a></b> +themselves without help (in the form of some kind of <b><a href="#breath-of-lifepacket">breath-of-life packet</a></b>) from +the server.</p> + +<hr> +Node:<a name="dictionaryflame">dictionary flame</a>, Next:<a +rel="next" href="#diddle">diddle</a>, Previous:<a rel="previous" +href="#dicklessworkstation">dickless workstation</a>, Up:<a +rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dictionary flame</b> n.</p> + +<p>[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 <b><a href="#spellingflame">spelling +flame</a></b>.</p> + +<hr> +Node:<a name="diddle">diddle</a>, Next:<a rel="next" href="#die">die</a>, Previous:<a rel="previous" href="#dictionaryflame">dictionary flame</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>diddle</b></p> + +<p>1. vt. To work with or modify in a not particularly serious +manner. "I diddled a copy of <b><a href="#ADVENT">ADVENT</a></b> +so it didn't double-space all the time." "Let's diddle this piece +of code and see if the problem goes away." See <b><a href="#tweak">tweak</a></b> and <b><a href="#twiddle">twiddle</a></b>. +2. n. The action or result of diddling. See also <b><a href="#tweak">tweak</a></b>, <b><a href="#twiddle">twiddle</a></b>, +<b><a href="#frob">frob</a></b>.</p> + +<hr> +Node:<a name="die">die</a>, Next:<a rel="next" href="#diehorribly">die horribly</a>, Previous:<a rel="previous" +href="#diddle">diddle</a>, Up:<a rel="up" href="#chap04">= +D =</a> <br> + + +<p><b>die</b> v.</p> + +<p>Syn. <b><a href="#crash">crash</a></b>. Unlike <b><a href="#crash">crash</a></b>, which is used primarily of hardware, this +verb is used of both hardware and software. See also <b><a href="#goflatline">go flatline</a></b>, <b><a href="#casters-upmode">casters-up mode</a></b>.</p> + +<hr> +Node:<a name="diehorribly">die horribly</a>, Next:<a rel="next" href="#diff">diff</a>, Previous:<a rel="previous" href="#die">die</a>, Up:<a rel="up" href="#chap04">= D =</a> +<br> + + +<p><b>die horribly</b> v.</p> + +<p>The software equivalent of <b><a href="#crashandburn">crash and burn</a></b>, and the preferred +emphatic form of <b><a href="#die">die</a></b>. "The converter +choked on an FF in its input and died horribly".</p> + +<hr> +Node:<a name="diff">diff</a>, Next:<a rel="next" href="#digit">digit</a>, Previous:<a rel="previous" href="#diehorribly">die horribly</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>diff</b> /dif/ n.</p> + +<p>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 <b><a href="#vdiff">vdiff</a></b>. 2. +Specifically, such a listing produced by the <code>diff(1)</code> +command, esp. when used as specification input to the +<code>patch(1)</code> utility (which can actually perform the +modifications; see <b><a href="#patch">patch</a></b>). 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 <b><a href="#vdiff">vdiff</a></b>, <b><a href="#mod">mod</a></b>.</p> + +<hr> +Node:<a name="digit">digit</a>, Next:<a rel="next" href="#dike">dike</a>, Previous:<a rel="previous" href="#diff">diff</a>, Up:<a rel="up" href="#chap04">= D =</a> +<br> + + +<p><b>digit</b> n.,obs.</p> + +<p>An employee of Digital Equipment Corporation. See also <b><a +href="#VAX">VAX</a></b>, <b><a href="#VMS">VMS</a></b>, <b><a +href="#PDP-10">PDP-10</a></b>, <b><a href="#TOPS-10">TOPS-10</a></b>, <b><a href="#fieldcircus">field +circus</a></b>.</p> + +<hr> +Node:<a name="dike">dike</a>, Next:<a rel="next" href="#Dilbert">Dilbert</a>, Previous:<a rel="previous" href="#digit">digit</a>, Up:<a rel="up" href="#chap04">= D +=</a> <br> + + +<p><b>dike</b> vt.</p> + +<p>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.</p> + +<hr> +Node:<a name="Dilbert">Dilbert</a>, Next:<a rel="next" href="#ding">ding</a>, Previous:<a rel="previous" href="#dike">dike</a>, Up:<a rel="up" href="#chap04">= D =</a> +<br> + + +<p><b>Dilbert</b></p> + +<p>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 <b><a +href="#management">management</a></b> practices all too readily +recognized by hackers. Adams, who spent nine years in <b><a href="#cube">cube</a></b> 4S700R at Pacific Bell (not <b><a href="#DEC">DEC</a></b> 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 <b><a href="#pointy-haired">pointy-haired</a></b>, <b><a +href="#ratdance">rat dance</a></b>.</p> + +<hr> +Node:<a name="ding">ding</a>, Next:<a rel="next" href="#dink">dink</a>, Previous:<a rel="previous" href="#Dilbert">Dilbert</a>, Up:<a rel="up" href="#chap04">= D +=</a> <br> + + +<p><b>ding</b> n.,vi.</p> + +<p>1. Synonym for <b><a href="#feep">feep</a></b>. Usage: rare +among hackers, but more common in the <b><a href="#RealWorld">Real World</a></b>. 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."</p> + +<hr> +Node:<a name="dink">dink</a>, Next:<a rel="next" href="#dinosaur">dinosaur</a>, Previous:<a rel="previous" href="#ding">ding</a>, Up:<a rel="up" href="#chap04">= D =</a> +<br> + + +<p><b>dink</b> /dink/ adj.</p> + +<p>Said of a machine that has the <b><a href="#bittybox">bitty +box</a></b> 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 <b><a href="#macdink">macdink</a></b>.</p> + +<hr> +Node:<a name="dinosaur">dinosaur</a>, Next:<a rel="next" href="#dinosaurpen">dinosaur pen</a>, Previous:<a rel="previous" +href="#dink">dink</a>, Up:<a rel="up" href="#chap04">= D +=</a> <br> + + +<p><b>dinosaur</b> n.</p> + +<p>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 <b><a href="#bigiron">big iron</a></b>; see +also <b><a href="#mainframe">mainframe</a></b>. 2. [IBM] A very +conservative user; a <b><a href="#zipperhead">zipperhead</a></b>.</p> + +<hr> +Node:<a name="dinosaurpen">dinosaur pen</a>, Next:<a rel="next" href="#dinosaursmating">dinosaurs mating</a>, +Previous:<a rel="previous" href="#dinosaur">dinosaur</a>, Up:<a +rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dinosaur pen</b> n.</p> + +<p>A traditional <b><a href="#mainframe">mainframe</a></b> +computer room complete with raised flooring, special power, its +own ultra-heavy-duty air conditioning, and a side order of Halon +fire extinguishers. See <b><a href="#boa">boa</a></b>.</p> + +<hr> +Node:<a name="dinosaursmating">dinosaurs mating</a>, Next:<a +rel="next" href="#dirtball">dirtball</a>, Previous:<a rel="previous" href="#dinosaurpen">dinosaur pen</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dinosaurs mating</b> n.</p> + +<p>Said to occur when yet another <b><a href="#bigiron">big +iron</a></b> merger or buyout occurs; reflects a perception by +hackers that these signal another stage in the long, slow dying +of the <b><a href="#mainframe">mainframe</a></b> 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 +(but spat it back out a few years later). Control Data still +exists but is no longer in the mainframe business. More such +earth-shaking unions of doomed giants seem inevitable.</p> + +<hr> +Node:<a name="dirtball">dirtball</a>, Next:<a rel="next" href="#dirtypower">dirty power</a>, Previous:<a rel="previous" +href="#dinosaursmating">dinosaurs mating</a>, Up:<a rel="up" +href="#chap04">= D =</a> <br> + + +<p><b>dirtball</b> n.</p> + +<p>[XEROX PARC] A small, perhaps struggling outsider; not in the +major or even the minor leagues. For example, "Xerox is not a +dirtball company".</p> + +<p>[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]</p> + +<hr> +Node:<a name="dirtypower">dirty power</a>, Next:<a rel="next" +href="#disclaimer">disclaimer</a>, Previous:<a rel="previous" +href="#dirtball">dirtball</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dirty power</b> n.</p> + +<p>Electrical mains voltage that is unfriendly to the delicate +innards of computers. Spikes, <b><a href="#drop-outs">drop-outs</a></b>, 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 <b><a href="#powerhit">power hit</a></b>s).</p> + +<hr> +Node:<a name="disclaimer">disclaimer</a>, Next:<a rel="next" +href="#Discordianism">Discordianism</a>, Previous:<a rel="previous" href="#dirtypower">dirty power</a>, Up:<a rel="up" +href="#chap04">= D =</a> <br> + + +<p><b>disclaimer</b> n.</p> + +<p>[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.</p> + +<hr> +Node:<a name="Discordianism">Discordianism</a>, Next:<a rel="next" href="#diskfarm">disk farm</a>, Previous:<a rel="previous" href="#disclaimer">disclaimer</a>, Up:<a rel="up" +href="#chap04">= D =</a> <br> + + +<p><b>Discordianism</b> /dis-kor'di-*n-ism/ n.</p> + +<p>The veneration of <b><a href="#Eris">Eris</a></b>, 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 <b><a +href="#Religion">Religion</a></b> in Appendix B, <b><a href="#ChurchoftheSubGenius">Church of the SubGenius</a></b>, +and <b><a href="#hahaonlyserious">ha ha only +serious</a></b>.</p> + +<hr> +Node:<a name="diskfarm">disk farm</a>, Next:<a rel="next" +href="#displayhack">display hack</a>, Previous:<a rel="previous" href="#Discordianism">Discordianism</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>disk farm</b> n.</p> + +<p>(also <b><a href="#laundromat">laundromat</a></b>) A large +room or rooms filled with disk drives (esp. <b><a href="#washingmachine">washing machine</a></b>s).</p> + +<hr> +Node:<a name="displayhack">display hack</a>, Next:<a rel="next" href="#dispress">dispress</a>, Previous:<a rel="previous" +href="#diskfarm">disk farm</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>display hack</b> n.</p> + +<p>A program with the same approximate purpose as a kaleidoscope: +to make pretty pictures. Famous display hacks include <b><a href="#munchingsquares">munching squares</a></b>, <b><a href="#smokingclover">smoking clover</a></b>, the BSD Unix +<code>rain(6)</code> program, <code>worms(6)</code> on +miscellaneous Unixes, and the <b><a href="#X">X</a></b> +<code>kaleid(1)</code> program. Display hacks can also be +implemented 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 <b><a href="#hackvalue">hack value</a></b> 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. +<b><a href="#psychedelicware">psychedelicware</a></b>.</p> + +<hr> +Node:<a name="dispress">dispress</a>, Next:<a rel="next" href="#DissociatedPress">Dissociated Press</a>, Previous:<a rel="previous" href="#displayhack">display hack</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dispress</b> vt.</p> + +<p>[contraction of `Dissociated Press' due to eight-character +MS-DOS filenames] To apply the <b><a href="#DissociatedPress">Dissociated Press</a></b> algorithm to a +block of text. The resultant output is also referred to as a +'dispression'.</p> + +<hr> +Node:<a name="DissociatedPress">Dissociated Press</a>, Next:<a +rel="next" href="#distribution">distribution</a>, Previous:<a +rel="previous" href="#dispress">dispress</a>, Up:<a rel="up" +href="#chap04">= D =</a> <br> + + +<p><b>Dissociated Press</b> n.</p> + +<p>[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 <b><a href="#marketroid">marketroid</a></b>. 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. <b><a href="#EMACS">EMACS</a></b> 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:</p> + +<blockquote>wart: n. A small, crocky <b><a href="#feature">feature</a></b> 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.</blockquote> + +<p>Here is a short example of letter-based Dissociated Press +applied to the same source:</p> + +<blockquote>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!</blockquote> + +<p>A hackish idle pastime is to apply letter-based Dissociated +Press to a random body of text and <b><a href="#vgrep">vgrep</a></b> 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 <b><a href="#pseudo">pseudo</a></b>.</p> + +<hr> +Node:<a name="distribution">distribution</a>, Next:<a rel="next" +href="#distro">distro</a>, Previous:<a rel="previous" href="#DissociatedPress">Dissociated Press</a>, Up:<a rel="up" +href="#chap04">= D =</a> <br> + + +<p><b>distribution</b> n.</p> + +<p>1. A software source tree packaged for distribution; but see +<b><a href="#kit">kit</a></b>. Since about 1996 unqualified use +of this term often implies `<b><a href="#Linux">Linux</a></b> +distribution'. The short for <b><a href="#distro">distro</a></b> +is often used for this sense. 2. A vague term encompassing +mailing lists and Usenet newsgroups (but not <b><a href="#BBS">BBS</a></b> <b><a href="#fora">fora</a></b>); 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.</p> + +<hr> +Node:<a name="distro">distro</a>, Next:<a rel="next" href="#disusered">disusered</a>, Previous:<a rel="previous" href="#distribution">distribution</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>distro</b> n.</p> + +<p>Synonym for <b><a href="#distribution">distribution</a></b>, +sense 1.</p> + +<hr> +Node:<a name="disusered">disusered</a>, Next:<a rel="next" href="#doprotocol">do protocol</a>, Previous:<a rel="previous" +href="#distro">distro</a>, Up:<a rel="up" href="#chap04">= +D =</a> <br> + + +<p><b>disusered</b> adj.</p> + +<p>[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 +<b><a href="#starout">star out</a></b>.</p> + +<hr> +Node:<a name="doprotocol">do protocol</a>, Next:<a rel="next" +href="#doc">doc</a>, Previous:<a rel="previous" href="#disusered">disusered</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>do protocol</b> vi.</p> + +<p>[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 <b><a href="#protocol">protocol</a></b>.</p> + +<hr> +Node:<a name="doc">doc</a>, Next:<a rel="next" href="#documentation">documentation</a>, Previous:<a rel="previous" +href="#doprotocol">do protocol</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>doc</b> /dok/ n.</p> + +<p>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).</p> + +<hr> +Node:<a name="documentation">documentation</a>, Next:<a rel="next" href="#dodgy">dodgy</a>, Previous:<a rel="previous" href="#doc">doc</a>, Up:<a rel="up" href="#chap04">= D =</a> +<br> + + +<p><b>documentation</b> n.</p> + +<p>The multiple kilograms of macerated, pounded, steamed, +bleached, and pressed trees that accompany most modern software +or hardware products (see also <b><a href="#tree-killer">tree-killer</a></b>). 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 <b><a href="#grep">grep</a></b> dead +trees". See <b><a href="#droolproofpaper">drool-proof +paper</a></b>, <b><a href="#verbiage">verbiage</a></b>, <b><a +href="#treeware">treeware</a></b>.</p> + +<hr> +Node:<a name="dodgy">dodgy</a>, Next:<a rel="next" href="#dogcow">dogcow</a>, Previous:<a rel="previous" href="#documentation">documentation</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dodgy</b> adj.</p> + +<p>Syn. with <b><a href="#flaky">flaky</a></b>. Preferred outside +the U.S.</p> + +<hr> +Node:<a name="dogcow">dogcow</a>, Next:<a rel="next" href="#dogfood">dogfood</a>, Previous:<a rel="previous" href="#dodgy">dodgy</a>, Up:<a rel="up" href="#chap04">= D +=</a> <br> + + +<p><b>dogcow</b> /dog'kow/ n.</p> + +<p>See <b><a href="#Moof">Moof</a></b>. 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. +<i>Getting</i> 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: <b><a href="#rot13">rot13</a></b> is +involved. A dogcow also appears if you choose `Page +Setup<small>...</small>' with a LaserWriter selected and click on +the `Options' button. It also lurks in other Mac printer drivers, +notably those for the now-discontinued Style Writers. Sadly, +Apple has removed the pages that used to describe the dogcow.</p> + +<hr> +Node:<a name="dogfood">dogfood</a>, Next:<a rel="next" href="#dogpile">dogpile</a>, Previous:<a rel="previous" href="#dogcow">dogcow</a>, Up:<a rel="up" href="#chap04">= D +=</a> <br> + + +<p><b>dogfood</b> n.</p> + +<p>[Microsoft, Netscape] Interim software used internally for +testing. "To eat one's own dogfood" (from which the slang noun +derives) means to use the software one is developing, as part of +one's everyday development environment (the phrase is used +outside Microsoft and Netscape). The practice is normal in the +Linux community and elsewhere, but the term `dogfood' is seldom +used as open-source betas tend to be quite tasty and nourishing. +The idea is that developers who are using their own software will +quickly learn what's missing or broken. Dogfood is typically not +even of <b><a href="#beta">beta</a></b> quality.</p> + +<hr> +Node:<a name="dogpile">dogpile</a>, Next:<a rel="next" href="#dogwash">dogwash</a>, Previous:<a rel="previous" href="#dogfood">dogfood</a>, Up:<a rel="up" href="#chap04">= D +=</a> <br> + + +<p><b>dogpile</b> v.</p> + +<p>[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 <i>alt.atheism</i>, he +can expect to be dogpiled. It has been suggested that this +derives from U.S, football slang for a tackle involving three or +more people; among hackers, it seems at least as likely do derive +from an `autobiographical' Bugs Bunny cartoon in which a gang of +attacking canines actually yells "Dogpile on the rabbit!".</p> + +<hr> +Node:<a name="dogwash">dogwash</a>, Next:<a rel="next" href="#domainist">domainist</a>, Previous:<a rel="previous" href="#dogpile">dogpile</a>, Up:<a rel="up" href="#chap04">= D +=</a> <br> + + +<p><b>dogwash</b> /dog'wosh/</p> + +<p>[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 <b><a href="#freeware">freeware</a></b> get written this way.</p> + +<hr> +Node:<a name="domainist">domainist</a>, Next:<a rel="next" href="#Dontdothatthen">Don't do that then!</a>, Previous:<a +rel="previous" href="#dogwash">dogwash</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>domainist</b> /doh-mayn'ist/ adj.</p> + +<p>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 <i>aol.com</i>?" 2. Said of an <b><a href="#Internetaddress">Internet address</a></b> (as opposed to a +<b><a href="#bangpath">bang path</a></b>) because the part to +the right of the <code>@</code> specifies a nested series of +`domains'; for example, esr@snark.thyrsus.com +specifies the machine called <i>snark</i> in the subdomain called +<i>thyrsus</i> within the top-level domain called <i>com</i>. See +also <b><a href="#big-endian">big-endian</a></b>, sense 2.</p> + +<p>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 <b><a href="#bangpath">bang +path</a></b>s. These senses are now (1996) obsolete, as +effectively all sites have converted.</p> + +<hr> +Node:<a name="Dontdothatthen">Don't do that then!</a>, +Next:<a rel="next" href="#dongle">dongle</a>, Previous:<a rel="previous" href="#domainist">domainist</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>Don't do that then!</b> imp.</p> + +<p>[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 <b><a href="#RTFM">RTFM</a></b>.</p> + +<p>Here's a classic example of "Don't do that then!" from Neil +Stephenson's "In The Beginning Was The Command Line". A friend of +his built a network with a load of Macs and a few high-powered +database servers. He found that from time to time the whole +network would lock up for no apparent reason. The problem was +eventually tracked down to MacOS's cooperative multitasking: when +a user held down the mouse button for too long, the network stack +wouldn't get a chance to run...</p> + +<hr> +Node:<a name="dongle">dongle</a>, Next:<a rel="next" href="#dongle-disk">dongle-disk</a>, Previous:<a rel="previous" href="#Dontdothatthen">Don't do that then!</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dongle</b> /dong'gl/ n.</p> + +<p>1. [now obs.] A security or <b><a href="#copyprotection">copy protection</a></b> device for +proprietary software 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. By 1993, dongles +would typically pass data through the port and monitor for <b><a +href="#magic">magic</a></b> 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. These devices have +become rare 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 <b><a href="#dongle-disk">dongle-disk</a></b>. 3. An +adaptor cable mating a special edge-type connector on a PCMCIA or +on-board Ethernet card to a standard RJ45 Ethernet jack. This +usage seems to have surfaced in 1999 and is now dominant. Laptop +owners curse these things because they're notoriously easy to +lose and the vendors commonly charge extortionate prices for +replacements.</p> + +<p>[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]</p> + +<hr> +Node:<a name="dongle-disk">dongle-disk</a>, Next:<a rel="next" +href="#donuts">donuts</a>, Previous:<a rel="previous" href="#dongle">dongle</a>, Up:<a rel="up" href="#chap04">= D +=</a> <br> + + +<p><b>dongle-disk</b> /don'gl disk/ n.</p> + +<p>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 <i>are</i> 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 <b><a +href="#rootmode">root mode</a></b> with a special boot disk.) +Also called a `key disk'. See <b><a href="#dongle">dongle</a></b>.</p> + +<hr> +Node:<a name="donuts">donuts</a>, Next:<a rel="next" href="#doorstop">doorstop</a>, Previous:<a rel="previous" href="#dongle-disk">dongle-disk</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>donuts</b> n. obs.</p> + +<p>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-<b><a href="#core">core</a></b> memories in +which each bit was implemented by a doughnut-shaped magnetic +flip-flop.</p> + +<hr> +Node:<a name="doorstop">doorstop</a>, Next:<a rel="next" href="#DoSattack">DoS attack</a>, Previous:<a rel="previous" href="#donuts">donuts</a>, Up:<a rel="up" href="#chap04">= D +=</a> <br> + + +<p><b>doorstop</b> n.</p> + +<p>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 <b><a href="#boatanchor">boat anchor</a></b>.</p> + +<hr> +Node:<a name="DoSattack">DoS attack</a>, Next:<a rel="next" +href="#dotfile">dot file</a>, Previous:<a rel="previous" href="#doorstop">doorstop</a>, Up:<a rel="up" href="#chap04">= +D =</a> <br> + + +<p><b>DoS attack</b> //</p> + +<p>[Usenet,common; note that it's unrelated to `DOS' as name of +an operating system] Abbreviation for Denial-Of-Service attack. +This abbreviation is most often used of attempts to shut down +newsgroups with floods of <b><a href="#spam">spam</a></b>, or to +flood network links with large amounts of traffic, or to flood +network links with large amounts of traffic, often by abusing +network broadcast addresses Compare <b><a href="#slashdoteffect">slashdot effect</a></b>.</p> + +<hr> +Node:<a name="dotfile">dot file</a>, Next:<a rel="next" href="#doublebucky">double bucky</a>, Previous:<a rel="previous" +href="#DoSattack">DoS attack</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dot file</b> [Unix] n.</p> + +<p>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 <b><a href="#creep">creep</a></b> -- 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 <b><a +href="#profile">profile</a></b> (sense 1), <b><a href="#rcfile">rc file</a></b>.</p> + +<hr> +Node:<a name="doublebucky">double bucky</a>, Next:<a rel="next" href="#doubledsig">doubled sig</a>, Previous:<a rel="previous" href="#dotfile">dot file</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>double bucky</b> adj.</p> + +<p>Using both the CTRL and META keys. "The command to burn all +LEDs is double bucky F."</p> + +<p>This term originated on the Stanford extended-ASCII keyboard, +and was later taken up by users of the <b><a href="#space-cadetkeyboard">space-cadet keyboard</a></b> at MIT. A +typical MIT comment was that the Stanford <b><a href="#buckybits">bucky bits</a></b> (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:</p> + +<pre> + 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) +</pre> + +<br> +<p>[This, by the way, is an excellent example of computer <b><a +href="#filk">filk</a></b> --ESR] See also <b><a href="#metabit">meta bit</a></b>, <b><a href="#cokebottle">cokebottle</a></b>, and <b><a href="#quadruplebucky">quadruple bucky</a></b>.</p> + +<hr> +Node:<a name="doubledsig">doubled sig</a>, Next:<a rel="next" +href="#down">down</a>, Previous:<a rel="previous" href="#doublebucky">double bucky</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>doubled sig</b> [Usenet] n.</p> + +<p>A <b><a href="#sigblock">sig block</a></b> that has been +included twice in a <b><a href="#Usenet">Usenet</a></b> 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 <b><a href="#B1FF">B1FF</a></b>, <b><a href="#pseudo">pseudo</a></b>.</p> + +<hr> +Node:<a name="down">down</a>, Next:<a rel="next" href="#download">download</a>, Previous:<a rel="previous" href="#doubledsig">doubled sig</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>down</b></p> + +<p>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 <b><a href="#system">system</a></b>. The message from +the <b><a href="#console">console</a></b> 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 <b><a href="#PM">PM</a></b>. "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 <b><a href="#crash">crash</a></b>; oppose <b><a href="#up">up</a></b>.</p> + +<hr> +Node:<a name="download">download</a>, Next:<a rel="next" href="#DP">DP</a>, Previous:<a rel="previous" href="#down">down</a>, +Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>download</b> vt.</p> + +<p>To transfer data or (esp.) code from a far-away system +(especially a larger `host' system) over a digital communications +link to a nearby system (especially a smaller `client' system. +Oppose <b><a href="#upload">upload</a></b>.</p> + +<p>Historical use of these terms was at one time associated with +transfers from large timesharing machines to PCs or peripherals +(download) and vice-versa (upload). The modern usage relative to +the speaker (rather than as an indicator of the size and role of +the machines) evolved as machine categories lost most of their +former functional importance.</p> + +<hr> +Node:<a name="DP">DP</a>, Next:<a rel="next" href="#DPB">DPB</a>, +Previous:<a rel="previous" href="#download">download</a>, Up:<a +rel="up" href="#chap04">= D =</a> <br> + + +<p><b>DP</b> /D-P/ n.</p> + +<p>1. Data Processing. Listed here because, according to hackers, +use of the term marks one immediately as a <b><a href="#suit">suit</a></b>. See <b><a href="#DPer">DPer</a></b>. 2. +Common abbrev for <b><a href="#DissociatedPress">Dissociated +Press</a></b>.</p> + +<hr> +Node:<a name="DPB">DPB</a>, Next:<a rel="next" href="#DPer">DPer</a>, Previous:<a rel="previous" href="#DP">DP</a>, +Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>DPB</b> /d*-pib'/ vt.</p> + +<p>[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.</p> + +<hr> +Node:<a name="DPer">DPer</a>, Next:<a rel="next" href="#DrFredMbogo">Dr. Fred Mbogo</a>, Previous:<a rel="previous" href="#DPB">DPB</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>DPer</b> /dee-pee-er/ n.</p> + +<p>Data Processor. Hackers are absolutely amazed that <b><a href="#suit">suit</a></b>s use this term self-referentially. +<i>Computers</i> process data, not people! See <b><a href="#DP">DP</a></b>.</p> + +<hr> +Node:<a name="DrFredMbogo">Dr. Fred Mbogo</a>, Next:<a +rel="next" href="#dragon">dragon</a>, Previous:<a rel="previous" +href="#DPer">DPer</a>, Up:<a rel="up" href="#chap04">= D +=</a> <br> + + +<p><b>Dr. Fred Mbogo</b> /*m-boh'goh, dok'tr fred/ n.</p> + +<p>[Stanford] The archetypal man you don't want to see about a +problem, esp. an incompetent professional; a shyster. "Do you +know a good eye doctor?" "Sure, try Mbogo Eye Care and +Professional Dry Cleaning." The name comes from synergy between +<b><a href="#bogus">bogus</a></b> and the original Dr. Mbogo, a +witch doctor who was Gomez Addams' physician on the old "Addams +Family" TV show. Interestingly enough, it turns out that under +the rules for Swahili noun classes, `m-' is the characteristic +prefix of "nouns referring to human beings". As such, "mbogo" is +quite plausible as a Swahili coinage for a person having the +nature of a <b><a href="#bogon">bogon</a></b>. Compare <b><a +href="#BloggsFamily">Bloggs Family</a></b> and <b><a href="#JRandomHacker">J. Random Hacker</a></b>; see also <b><a +href="#FredFoobar">Fred Foobar</a></b> and <b><a href="#fred">fred</a></b>.</p> + +<hr> +Node:<a name="dragon">dragon</a>, Next:<a rel="next" href="#DragonBook">Dragon Book</a>, Previous:<a rel="previous" +href="#DrFredMbogo">Dr. Fred Mbogo</a>, Up:<a rel="up" +href="#chap04">= D =</a> <br> + + +<p><b>dragon</b> n.</p> + +<p>[MIT] A program similar to a <b><a href="#daemon">daemon</a></b>, 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 <b><a href="#daemon">daemon</a></b>. The best-known Unix example of a dragon +is <code>cron(1)</code>. At SAIL, they called this sort of thing +a `phantom'.</p> + +<hr> +Node:<a name="DragonBook">Dragon Book</a>, Next:<a rel="next" +href="#drain">drain</a>, Previous:<a rel="previous" href="#dragon">dragon</a>, Up:<a rel="up" href="#chap04">= D +=</a> <br> + + +<p><b>Dragon Book</b> n.</p> + +<p>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 <b><a href="#booktitles">book titles</a></b>.</p> + +<hr> +Node:<a name="drain">drain</a>, Next:<a rel="next" href="#dreadhighbitdisease">dread high-bit disease</a>, +Previous:<a rel="previous" href="#DragonBook">Dragon Book</a>, +Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>drain</b> v.</p> + +<p>[IBM] Syn. for <b><a href="#flush">flush</a></b> (sense 2). +Has a connotation of finality about it; one speaks of draining a +device before taking it offline.</p> + +<hr> +Node:<a name="dreadhighbitdisease">dread high-bit +disease</a>, Next:<a rel="next" href="#DreadQuestionmarkDisease">Dread Questionmark Disease</a>, +Previous:<a rel="previous" href="#drain">drain</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dread high-bit disease</b> n.</p> + +<p>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.</p> + +<p>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 <b><a href="#cretinous">cretinous</a></b> design tradeoffs +ever made. See <b><a href="#metabit">meta bit</a></b>.</p> + +<hr> +Node:<a name="DreadQuestionmarkDisease">Dread Questionmark +Disease</a>, Next:<a rel="next" href="#DRECNET">DRECNET</a>, +Previous:<a rel="previous" href="#dreadhighbitdisease">dread high-bit disease</a>, Up:<a +rel="up" href="#chap04">= D =</a> <br> + + +<p><b>Dread Questionmark Disease</b></p> + +<p>n. The result of saving HTML from Microsoft Word or some other +program that uses the nonstandard Microsoft variant of Latin-1; +the symptom is that various of those nonstandard characters in +positions 128-160 show up as questionmarks. The usual culprit is +the misnamed `smart quotes' feature in Microsoft Word. For more +details (and a program called `demoroniser' that cleans up the +mess) see http://www.fourmilab.ch/webtools/demoroniser/.</p> + +<hr> +Node:<a name="DRECNET">DRECNET</a>, Next:<a rel="next" href="#driver">driver</a>, Previous:<a rel="previous" href="#DreadQuestionmarkDisease">Dread Questionmark Disease</a>, +Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>DRECNET</b> /drek'net/ n.</p> + +<p>[from Yiddish/German `dreck', meaning filth] Deliberate +distortion of DECNET, a networking protocol used in the <b><a +href="#VMS">VMS</a></b> community. So called because <b><a href="#DEC">DEC</a></b> 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 <b><a href="#connectorconspiracy">connector conspiracy</a></b>.</p> + +<hr> +Node:<a name="driver">driver</a>, Next:<a rel="next" href="#droid">droid</a>, Previous:<a rel="previous" href="#DRECNET">DRECNET</a>, Up:<a rel="up" href="#chap04">= D +=</a> <br> + + +<p><b>driver</b> n.</p> + +<p>1. The <b><a href="#mainloop">main loop</a></b> 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.</p> + +<hr> +Node:<a name="droid">droid</a>, Next:<a rel="next" href="#drone">drone</a>, Previous:<a rel="previous" href="#driver">driver</a>, Up:<a rel="up" href="#chap04">= D +=</a> <br> + + +<p><b>droid</b> n.</p> + +<p>[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.</p> + +<p>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 <b><a href="#suit">suit</a></b>, <b><a href="#marketroid">marketroid</a></b>; see <b><a href="#-oid">-oid</a></b>.</p> + +<p>In England there is equivalent mainstream slang; a `jobsworth' +is an obstructive, rule-following bureaucrat, often of the +uniformed or suited variety. Named for the habit of denying a +reasonable request by sucking his teeth and saying "Oh no, guv, +sorry I can't help you: that's more than my job's worth".</p> + +<hr> +Node:<a name="drone">drone</a>, Next:<a rel="next" href="#droolproofpaper">drool-proof paper</a>, Previous:<a rel="previous" href="#droid">droid</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>drone</b> n.</p> + +<p>Ignorant sales or customer service personnel in computer or +electronics superstores. Characterized by a lack of even +superficial knowledge about the products they sell, yet possessed +of the conviction that they are more competent than their hacker +customers. Usage: "That video board probably sucks, it was +recommended by a drone at Fry's" In the year 2000, their natural +habitats include Fry's Electronics, Best Buy, and CompUSA.</p> + +<hr> +Node:<a name="droolproofpaper">drool-proof paper</a>, Next:<a +rel="next" href="#droponthefloor">drop on the floor</a>, +Previous:<a rel="previous" href="#drone">drone</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>drool-proof paper</b> n.</p> + +<p>Documentation that has been obsessively <b><a href="#dumbeddown">dumbed down</a></b>, to the point where only a +<b><a href="#cretin">cretin</a></b> 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." The SGI Indy manual is said +to include the line "Do not dangle the mouse by the cord or throw +it at coworkers.", but this sounds like parody.</p> + +<hr> +Node:<a name="droponthefloor">drop on the floor</a>, +Next:<a rel="next" href="#drop-ins">drop-ins</a>, Previous:<a +rel="previous" href="#droolproofpaper">drool-proof paper</a>, +Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>drop on the floor</b> vt.</p> + +<p>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 <b><a href="#blackHole">black hole</a></b>, <b><a href="#bitbucket">bit bucket</a></b>.</p> + +<hr> +Node:<a name="drop-ins">drop-ins</a>, Next:<a rel="next" href="#drop-outs">drop-outs</a>, Previous:<a rel="previous" href="#droponthefloor">drop on the floor</a>, Up:<a rel="up" +href="#chap04">= D =</a> <br> + + +<p><b>drop-ins</b> n.</p> + +<p>[prob. by analogy with <b><a href="#drop-outs">drop-outs</a></b>] 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 <b><a href="#drop-outs">drop-outs</a></b>, sense 2.</p> + +<hr> +Node:<a name="drop-outs">drop-outs</a>, Next:<a rel="next" href="#drugged">drugged</a>, Previous:<a rel="previous" href="#drop-ins">drop-ins</a>, Up:<a rel="up" href="#chap04">= +D =</a> <br> + + +<p><b>drop-outs</b> n.</p> + +<p>1. A variety of `power glitch' (see <b><a href="#glitch">glitch</a></b>); 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 <b><a href="#screamingtty">screaming tty</a></b>). 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 <b><a href="#glitch">glitch</a></b>, <b><a href="#fried">fried</a></b>.</p> + +<hr> +Node:<a name="drugged">drugged</a>, Next:<a rel="next" href="#drum">drum</a>, Previous:<a rel="previous" href="#drop-outs">drop-outs</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>drugged</b> adj.</p> + +<p>(also `on drugs') 1. Conspicuously stupid, heading toward +<b><a href="#brain-damaged">brain-damaged</a></b>. Often +accompanied by a pantomime of toking a joint. 2. Of hardware, +very slow relative to normal performance.</p> + +<hr> +Node:<a name="drum">drum</a>, Next:<a rel="next" href="#drunkmousesyndrome">drunk mouse syndrome</a>, Previous:<a +rel="previous" href="#drugged">drugged</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>drum</b> adj, n.</p> + +<p>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 +<code>/dev/drum</code>; this has led to considerable humor and +not a few straight-faced but utterly bogus `explanations' getting +foisted on <b><a href="#newbie">newbie</a></b>s. See also "<b><a +href="#TheStoryofMel">The Story of Mel</a></b>" in +Appendix A.</p> + +<hr> +Node:<a name="drunkmousesyndrome">drunk mouse syndrome</a>, +Next:<a rel="next" href="#dubdubdub">dub dub dub</a>, +Previous:<a rel="previous" href="#drum">drum</a>, Up:<a rel="up" +href="#chap04">= D =</a> <br> + + +<p><b>drunk mouse syndrome</b> n.</p> + +<p>(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.</p> + +<p>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 <b><a href="#cruft">cruft</a></b> 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.</p> + +<hr> +Node:<a name="dubdubdub">dub dub dub</a>, Next:<a rel="next" href="#Duffsdevice">Duff's device</a>, Previous:<a +rel="previous" href="#drunkmousesyndrome">drunk mouse +syndrome</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dub dub dub</b></p> + +<p>[common] Spoken-only shorthand for the "www" (double-u +double-u double-u) in many web host names. Nothing to do with the +style of reggae music called `dub'.</p> + +<hr> +Node:<a name="Duffsdevice">Duff's device</a>, Next:<a rel="next" href="#dumbterminal">dumb terminal</a>, Previous:<a +rel="previous" href="#dubdubdub">dub dub dub</a>, Up:<a +rel="up" href="#chap04">= D =</a> <br> + + +<p><b>Duff's device</b> n.</p> + +<p>The most dramatic use yet seen of <b><a href="#fallThrough">fall through</a></b> in C, invented by Tom Duff +when he was at Lucasfilm. Trying to <b><a href="#bum">bum</a></b> +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 +<i>interlacing</i> the structures of a switch and a loop:</p> + +<pre> + 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); + } +</pre> + +<br> +<p>Shocking though it appears to all who encounter it for the +first time, the device is actually perfectly valid, legal C. C's +default <b><a href="#fallThrough">fall through</a></b> 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." Duff has +discussed the device in detail at http://www.lysator.liu.se/c/duffs-device.html. +Note that the omission of postfix <code>++</code> from +<code>*to</code> was intentional (though confusing). Duff's +device can be used to implement memory copy, but the original aim +was to copy values serially into a magic IO register.</p> + +<p>[For maximal obscurity, the outermost pair of braces above +could actually be removed -- GLS]</p> + +<hr> +Node:<a name="dumbterminal">dumb terminal</a>, Next:<a rel="next" href="#dumbassattack">dumbass attack</a>, Previous:<a +rel="previous" href="#Duffsdevice">Duff's device</a>, Up:<a +rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dumb terminal</b> n.</p> + +<p>A terminal that is one step above a <b><a href="#glasstty">glass tty</a></b>, having a minimally addressable +cursor but no on-screen editing or other features normally +supported by a <b><a href="#smartterminal">smart +terminal</a></b>. 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.</p> + +<hr> +Node:<a name="dumbassattack">dumbass attack</a>, Next:<a rel="next" href="#dumbeddown">dumbed down</a>, Previous:<a rel="previous" href="#dumbterminal">dumb terminal</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dumbass attack</b> /duhm'as *-tak'/ n.</p> + +<p>[Purdue] Notional cause of a novice's mistake made by the +experienced, especially one made while running as <b><a href="#root">root</a></b> under Unix, e.g., typing <code>rm -r +*</code> or <code>mkfs</code> on a mounted file system. Compare +<b><a href="#adger">adger</a></b>.</p> + +<hr> +Node:<a name="dumbeddown">dumbed down</a>, Next:<a rel="next" +href="#dump">dump</a>, Previous:<a rel="previous" href="#dumbassattack">dumbass attack</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dumbed down</b> adj.</p> + +<p>Simplified, with a strong connotation of +<i>over</i>simplified. Often, a <b><a href="#marketroid">marketroid</a></b> 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 <b><a href="#user-friendly">user-friendly</a></b>.</p> + +<hr> +Node:<a name="dump">dump</a>, Next:<a rel="next" href="#dumpsterdiving">dumpster diving</a>, Previous:<a rel="previous" href="#dumbeddown">dumbed down</a>, Up:<a rel="up" +href="#chap04">= D =</a> <br> + + +<p><b>dump</b> n.</p> + +<p>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 <b><a href="#coredump">core dump</a></b>), and most especially one +consisting of hex or octal <b><a href="#runes">runes</a></b> +describing the byte-by-byte state of memory, mass storage, or +some file. In <b><a href="#elderdays">elder days</a></b>, +debugging was generally done by `groveling over' a dump (see +<b><a href="#grovel">grovel</a></b>); 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.</p> + +<hr> +Node:<a name="dumpsterdiving">dumpster diving</a>, Next:<a +rel="next" href="#dupkiller">dup killer</a>, Previous:<a rel="previous" href="#dump">dump</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dumpster diving</b> /dump'-ster di:'-ving/ n.</p> + +<p>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 <b><a href="#phreaking">phreaking</a></b>) 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) <b><a href="#cruft">cruft</a></b>.</p> + +<hr> +Node:<a name="dupkiller">dup killer</a>, Next:<a rel="next" +href="#duploop">dup loop</a>, Previous:<a rel="previous" href="#dumpsterdiving">dumpster diving</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dup killer</b> /d[y]oop kill'r/ n.</p> + +<p>[FidoNet] Software that is supposed to detect and delete +duplicates of a message that may have reached the FidoNet system +via different routes.</p> + +<hr> +Node:<a name="duploop">dup loop</a>, Next:<a rel="next" href="#dustydeck">dusty deck</a>, Previous:<a rel="previous" href="#dupkiller">dup killer</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dup loop</b> /d[y]oop loop/ (also `dupe loop') n.</p> + +<p>[FidoNet] An infinite stream of duplicated, near-identical +messages on a FidoNet <b><a href="#echo">echo</a></b>, the only +difference being unique or mangled identification information +applied by a faulty or incorrectly configured system or network +gateway, thus rendering <b><a href="#dupkiller">dup +killer</a></b>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 <b><a href="#duploop">dup loop</a></b>.</p> + +<hr> +Node:<a name="dustydeck">dusty deck</a>, Next:<a rel="next" +href="#DWIM">DWIM</a>, Previous:<a rel="previous" href="#duploop">dup loop</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>dusty deck</b> n.</p> + +<p>Old software (especially applications) which one is obliged to +remain compatible with, or to maintain (<b><a href="#DP">DP</a></b> 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 <b><a href="#number-crunching">number-crunching</a></b> software, much of +which was written in FORTRAN and very poorly documented but is +believed to be too expensive to replace. See <b><a href="#fossil">fossil</a></b>; compare <b><a href="#crawlinghorror">crawling horror</a></b>.</p> + +<hr> +Node:<a name="DWIM">DWIM</a>, Next:<a rel="next" href="#dynner">dynner</a>, Previous:<a rel="previous" href="#dustydeck">dusty deck</a>, Up:<a rel="up" href="#chap04">= D =</a> <br> + + +<p><b>DWIM</b> /dwim/</p> + +<p>[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 <b><a href="#hairy">hairy</a></b>. 3. +Occasionally, an interjection hurled at a balky computer, esp. +when one senses one might be tripping over legalisms (see <b><a +href="#legalese">legalese</a></b>). 4. Of a person, someone whose +directions are incomprehensible and vague, but who nevertheless +has the expectation that you will solve the problem using the +specific method he/she has in mind.</p> + +<p>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!'.</p> + +<p>In one notorious incident, Warren added a DWIM feature to the +command interpreter used at Xerox PARC. One day another hacker +there typed <code>delete *$</code> to free up some disk space. +(The editor there named backup files by appending <code>$</code> +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 +<code>*$ not found, assuming you meant 'delete *'.</code> It then +started to delete all the files on the disk! The hacker managed +to stop it with a <b><a href="#Vulcannervepinch">Vulcan +nerve pinch</a></b> after only a half dozen or so files were +lost.</p> + +<p>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 <code>delete *$</code> +twice.</p> + +<p>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 <b><a href="#RightThing">Right Thing</a></b>.</p> + +<hr> +Node:<a name="dynner">dynner</a>, Next:<a rel="next" href="#earthquake">earthquake</a>, Previous:<a rel="previous" href="#DWIM">DWIM</a>, Up:<a rel="up" href="#chap04">= D =</a> +<br> + + +<p><b>dynner</b> /din'r/ n.</p> + +<p>32 bits, by analogy with <b><a href="#nybble">nybble</a></b> +and <b><a href="#byte">byte</a></b>. Usage: rare and extremely +silly. See also <b><a href="#playte">playte</a></b>, <b><a href="#tayste">tayste</a></b>, <b><a href="#crumb">crumb</a></b>. +General discussion of such terms is under <b><a href="#nybble">nybble</a></b>.</p> + +<hr> +Node:<a name="chap05">= E =</a>, Next:<a rel="next" href="#chap06">= F =</a>, Previous:<a rel="previous" href="#chap04">= D =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= E =</h2> + +<ul> +<li><a href="#earthquake">earthquake</a>:</li> + +<li><a href="#Easteregg">Easter egg</a>:</li> + +<li><a href="#Easteregging">Easter egging</a>:</li> + +<li><a href="#eatflamingdeath">eat flaming death</a>:</li> + +<li><a href="#EBCDIC">EBCDIC</a>:</li> + +<li><a href="#echo">echo</a>:</li> + +<li><a href="#ECP">ECP</a>:</li> + +<li><a href="#ed">ed</a>:</li> + +<li><a href="#egosurf">egosurf</a>:</li> + +<li><a href="#eighty-columnmind">eighty-column mind</a>:</li> + +<li><a href="#ElCaminoBignum">El Camino Bignum</a>:</li> + +<li><a href="#elderdays">elder days</a>:</li> + +<li><a href="#elegant">elegant</a>:</li> + +<li><a href="#elephantine">elephantine</a>:</li> + +<li><a href="#elevatorcontroller">elevator +controller</a>:</li> + +<li><a href="#elite">elite</a>:</li> + +<li><a href="#ELIZAeffect">ELIZA effect</a>:</li> + +<li><a href="#elvish">elvish</a>:</li> + +<li><a href="#EMACS">EMACS</a>:</li> + +<li><a href="#email">email</a>:</li> + +<li><a href="#emoticon">emoticon</a>:</li> + +<li><a href="#EMP">EMP</a>:</li> + +<li><a href="#empire">empire</a>:</li> + +<li><a href="#engine">engine</a>:</li> + +<li><a href="#English">English</a>:</li> + +<li><a href="#enhancement">enhancement</a>:</li> + +<li><a href="#ENQ">ENQ</a>:</li> + +<li><a href="#EOF">EOF</a>:</li> + +<li><a href="#EOL">EOL</a>:</li> + +<li><a href="#EOU">EOU</a>:</li> + +<li><a href="#epoch">epoch</a>:</li> + +<li><a href="#epsilon">epsilon</a>:</li> + +<li><a href="#epsilonsquared">epsilon squared</a>:</li> + +<li><a href="#erathe">era the</a>:</li> + +<li><a href="#EricConspiracy">Eric Conspiracy</a>:</li> + +<li><a href="#Eris">Eris</a>:</li> + +<li><a href="#erotics">erotics</a>:</li> + +<li><a href="#error33">error 33</a>:</li> + +<li><a href="#eurodemo">eurodemo</a>:</li> + +<li><a href="#evil">evil</a>:</li> + +<li><a href="#evilandrude">evil and rude</a>:</li> + +<li><a href="#EvilEmpire">Evil Empire</a>:</li> + +<li><a href="#exa-">exa-</a>:</li> + +<li><a href="#examiningtheentrails">examining the +entrails</a>:</li> + +<li><a href="#EXCH">EXCH</a>:</li> + +<li><a href="#excl">excl</a>:</li> + +<li><a href="#EXE">EXE</a>:</li> + +<li><a href="#exec">exec</a>:</li> + +<li><a href="#exerciseleftasan">exercise left as +an</a>:</li> + +<li><a href="#Exon">Exon</a>:</li> + +<li><a href="#Exploder">Exploder</a>:</li> + +<li><a href="#exploit">exploit</a>:</li> + +<li><a href="#externalmemory">external memory</a>:</li> + +<li><a href="#eyecandy">eye candy</a>:</li> + +<li><a href="#eyeballsearch">eyeball search</a>:</li> +</ul> + +<hr> +Node:<a name="earthquake">earthquake</a>, Next:<a rel="next" +href="#Easteregg">Easter egg</a>, Previous:<a rel="previous" +href="#dynner">dynner</a>, Up:<a rel="up" href="#chap05">= +E =</a> <br> + + +<p><b>earthquake</b> n.</p> + +<p>[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.</p> + +<hr> +Node:<a name="Easteregg">Easter egg</a>, Next:<a rel="next" +href="#Easteregging">Easter egging</a>, Previous:<a rel="previous" href="#earthquake">earthquake</a>, Up:<a rel="up" +href="#chap05">= E =</a> <br> + + +<p><b>Easter egg</b> n.</p> + +<p>[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 <code>make love</code> with <code>not war?</code>. +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.</p> + +<hr> +Node:<a name="Easteregging">Easter egging</a>, Next:<a rel="next" href="#eatflamingdeath">eat flaming death</a>, +Previous:<a rel="previous" href="#Easteregg">Easter egg</a>, +Up:<a rel="up" href="#chap05">= E =</a> <br> + + +<p><b>Easter egging</b> n.</p> + +<p>[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 <b><a href="#fieldcircus">field circus</a></b> techs and do not love them +for it. See also the jokes under <b><a href="#fieldcircus">field circus</a></b>. Compare <b><a href="#shotgundebugging">shotgun debugging</a></b>.</p> + +<hr> +Node:<a name="eatflamingdeath">eat flaming death</a>, +Next:<a rel="next" href="#EBCDIC">EBCDIC</a>, Previous:<a rel="previous" href="#Easteregging">Easter egging</a>, Up:<a rel="up" href="#chap05">= E =</a> <br> + + +<p><b>eat flaming death</b> imp.</p> + +<p>A construction popularized among hackers by the infamous <b><a +href="#CPUWars">CPU Wars</a></b> 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 +Theatre's 1975 album "In The Next World, You're On Your Own" a +character won the right to scream "Eat flaming death, fascist +media pigs" in the middle of Oscar night on a game show; this may +have been an influence). Used in humorously overblown expressions +of hostility. "Eat flaming death, <b><a href="#EBCDIC">EBCDIC</a></b> users!"</p> + +<hr> +Node:<a name="EBCDIC">EBCDIC</a>, Next:<a rel="next" href="#echo">echo</a>, Previous:<a rel="previous" href="#eatflamingdeath">eat flaming death</a>, Up:<a rel="up" +href="#chap05">= E =</a> <br> + + +<p><b>EBCDIC</b> /eb's*-dik/, /eb'see`dik/, or /eb'k*-dik/ n.</p> + +<p>[abbreviation, Extended Binary Coded Decimal Interchange Code] +An alleged character set used on IBM <b><a href="#dinosaur">dinosaur</a></b>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 <b><a href="#punchedcard">punched card</a></b> code in +the early 1960s and promulgated it as a customer-control tactic +(see <b><a href="#connectorconspiracy">connector +conspiracy</a></b>), 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 <i>name</i> of +EBCDIC and consider it a manifestation of purest <b><a href="#evil">evil</a></b>. See also <b><a href="#fearandloathing">fear and loathing</a></b>.</p> + +<hr> +Node:<a name="echo">echo</a>, Next:<a rel="next" href="#ECP">ECP</a>, Previous:<a rel="previous" href="#EBCDIC">EBCDIC</a>, Up:<a rel="up" href="#chap05">= E +=</a> <br> + + +<p><b>echo</b> [FidoNet] n.</p> + +<p>A <b><a href="#topicgroup">topic group</a></b> on <b><a +href="#FidoNet">FidoNet</a></b>'s echomail system. Compare <b><a +href="#newsgroup">newsgroup</a></b>.</p> + +<hr> +Node:<a name="ECP">ECP</a>, Next:<a rel="next" href="#ed">ed</a>, +Previous:<a rel="previous" href="#echo">echo</a>, Up:<a rel="up" +href="#chap05">= E =</a> <br> + + +<p><b>ECP</b> /E-C-P/ n.</p> + +<p>See <b><a href="#spam">spam</a></b> and <b><a href="#velveeta">velveeta</a></b>.</p> + +<hr> +Node:<a name="ed">ed</a>, Next:<a rel="next" href="#egosurf">egosurf</a>, Previous:<a rel="previous" href="#ECP">ECP</a>, Up:<a rel="up" href="#chap05">= E =</a> +<br> + + +<p><b>ed</b> n.</p> + +<p>"ed is the standard text editor." Line taken from original the +<b><a href="#Unix">Unix</a></b> manual page on ed, an ancient +line-oriented editor that is by now used only by a few <b><a +href="#RealProgrammer">Real Programmer</a></b>s, and even then +only for batch operations. The original line is sometimes uttered +near the beginning of an emacs vs. vi holy war on <b><a href="#Usenet">Usenet</a></b>, with the (vain) hope to quench the +discussion before it really takes off. Often followed by a +standard text describing the many virtues of ed (such as the +small memory <b><a href="#footprint">footprint</a></b> on a Timex +Sinclair, and the consistent (because nearly non-existent) user +interface).</p> + +<hr> +Node:<a name="egosurf">egosurf</a>, Next:<a rel="next" href="#eighty-columnmind">eighty-column mind</a>, Previous:<a rel="previous" href="#ed">ed</a>, Up:<a rel="up" href="#chap05">= E =</a> <br> + + +<p><b>egosurf</b> vi.</p> + +<p>To search the net for your name or links to your web pages. +Perhaps connected to long-established SF-fan slang `egoscan', to +search for one's name in a fanzine.</p> + +<hr> +Node:<a name="eighty-columnmind">eighty-column mind</a>, +Next:<a rel="next" href="#ElCaminoBignum">El Camino +Bignum</a>, Previous:<a rel="previous" href="#egosurf">egosurf</a>, Up:<a rel="up" href="#chap05">= E +=</a> <br> + + +<p><b>eighty-column mind</b> n.</p> + +<p>[IBM] The sort said to be possessed by persons for whom the +transition from <b><a href="#punchedcard">punched card</a></b> +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:</p> + +<pre> + He died at the console + Of hunger and thirst. + Next day he was buried, + Face down, 9-edge first. +</pre> + +<p>The eighty-column mind was thought by most hackers to dominate +IBM's customer base and its thinking. This only began to change +in the mid-1990s when IBM began to reinvent itself after the +triumph of the <b><a href="#killermicro">killer micro</a></b>. +See <b><a href="#IBM">IBM</a></b>, <b><a href="#fearandloathing">fear and loathing</a></b>, <b><a href="#cardwalloper">card walloper</a></b>. A copy of "The Last +Bug" lives on the the GNU site at http://www.gnu.org/fun/jokes/last.bug.html.</p> + +<hr> +Node:<a name="ElCaminoBignum">El Camino Bignum</a>, Next:<a +rel="next" href="#elderdays">elder days</a>, Previous:<a rel="previous" href="#eighty-columnmind">eighty-column mind</a>, +Up:<a rel="up" href="#chap05">= E =</a> <br> + + +<p><b>El Camino Bignum</b> /el' k*-mee'noh big'nuhm/ n.</p> + +<p>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 <b><a href="#logical">logical</a></b> 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.</p> + +<p>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).</p> + +<p>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 +<b><a href="#bignum">bignum</a></b>.)</p> + +<p>[GLS has since let slip that the unnamed hacker in this story +was in fact himself --ESR]</p> + +<p>In recent years, the synonym `El Camino Virtual' has been +reported as an alternate at IBM and Amdahl sites in the Valley. +Mathematically literate hackers in the Valley have also been +heard to refer to some major cross-street intersecting El Camino +Real as "El Camino Imaginary". One popular theory is that the +intersection is located near Moffett Field - where they keep all +those complex planes.</p> + +<hr> +Node:<a name="elderdays">elder days</a>, Next:<a rel="next" +href="#elegant">elegant</a>, Previous:<a rel="previous" href="#ElCaminoBignum">El Camino Bignum</a>, Up:<a rel="up" +href="#chap05">= E =</a> <br> + + +<p><b>elder days</b> n.</p> + +<p>The heroic age of hackerdom (roughly, pre-1980); the era of +the <b><a href="#PDP-10">PDP-10</a></b>, <b><a href="#TECO">TECO</a></b>, <b><a href="#ITS">ITS</a></b>, and the +ARPANET. This term has been rather consciously adopted from J. R. +R. Tolkien's fantasy epic "The Lord of the Rings". Compare <b><a +href="#IronAge">Iron Age</a></b>; see also <b><a href="#elvish">elvish</a></b> and <b><a href="#GreatWorm">Great +Worm</a></b>.</p> + +<hr> +Node:<a name="elegant">elegant</a>, Next:<a rel="next" href="#elephantine">elephantine</a>, Previous:<a rel="previous" href="#elderdays">elder days</a>, Up:<a rel="up" href="#chap05">= E =</a> <br> + + +<p><b>elegant</b> adj.</p> + +<p>[common; from mathematical usage] Combining simplicity, power, +and a certain ineffable grace of design. Higher praise than +`clever', `winning', or even <b><a href="#cuspy">cuspy</a></b>.</p> + +<p>The French aviator, adventurer, and author Antoine de +Saint-Exupéry, 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."</p> + +<hr> +Node:<a name="elephantine">elephantine</a>, Next:<a rel="next" +href="#elevatorcontroller">elevator controller</a>, +Previous:<a rel="previous" href="#elegant">elegant</a>, Up:<a +rel="up" href="#chap05">= E =</a> <br> + + +<p><b>elephantine</b> adj.</p> + +<p>Used of programs or systems that are both conspicuous <b><a +href="#hog">hog</a></b>s (owing perhaps to poor design founded on +<b><a href="#bruteforceandignorance">brute force and +ignorance</a></b>) and exceedingly <b><a href="#hairy">hairy</a></b> 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 <b><a href="#monstrosity">monstrosity</a></b>. See also <b><a href="#second-systemeffect">second-system effect</a></b> and <b><a +href="#baroque">baroque</a></b>.</p> + +<hr> +Node:<a name="elevatorcontroller">elevator controller</a>, +Next:<a rel="next" href="#elite">elite</a>, Previous:<a rel="previous" href="#elephantine">elephantine</a>, Up:<a rel="up" +href="#chap05">= E =</a> <br> + + +<p><b>elevator controller</b> n.</p> + +<p>An archetypal dumb embedded-systems application, like <b><a +href="#toaster">toaster</a></b> (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 <code>printf(3)</code> 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 <b><a href="#holywars">holy wars</a></b>.</p> + +<hr> +Node:<a name="elite">elite</a>, Next:<a rel="next" href="#ELIZAeffect">ELIZA effect</a>, Previous:<a rel="previous" +href="#elevatorcontroller">elevator controller</a>, Up:<a rel="up" href="#chap05">= E =</a> <br> + + +<p><b>elite</b> adj.</p> + +<p>Clueful. Plugged-in. One of the cognoscenti. Also used as a +general positive adjective. This term is not actually native +hacker slang; it is used primarily by crackers and <b><a href="#warezd00dz">warez d00dz</a></b>, for which reason hackers +use it only with heavy irony. The term used to refer to the folks +allowed in to the "hidden" or "privileged" sections of BBSes in +the early 1980s (which, typically, contained pirated software). +Frequently, early boards would only let you post, or even see, a +certain subset of the sections (or `boards') on a BBS. Those who +got to the frequently legendary `triple super secret' boards were +elite. Misspellings of this term in warez d00dz style abound; the +forms `eleet', and `31337' (among others) have been sighted.</p> + +<p>A true hacker would be more likely to use `wizardly'. Oppose +<b><a href="#lamer">lamer</a></b>.</p> + +<hr> +Node:<a name="ELIZAeffect">ELIZA effect</a>, Next:<a rel="next" href="#elvish">elvish</a>, Previous:<a rel="previous" +href="#elite">elite</a>, Up:<a rel="up" href="#chap05">= E +=</a> <br> + + +<p><b>ELIZA effect</b> /*-li:'z* *-fekt'/ n.</p> + +<p>[AI community] The tendency of humans to attach associations +to terms from prior experience. For example, there is nothing +magic about the symbol <code>+</code> that makes it well-suited +to indicate addition; it's just that people associate it with +addition. Using <code>+</code> or `plus' to mean addition in a +computer language is taking advantage of the ELIZA effect.</p> + +<p>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 <b><a +href="#GoodThing">Good Thing</a></b> when writing a +programming language, but it can blind you to serious +shortcomings when analyzing an Artificial Intelligence system. +Compare <b><a href="#ad-hockery">ad-hockery</a></b>; see also +<b><a href="#AI-complete">AI-complete</a></b>. Sources for a +clone of the original Eliza are available at <a href="ftp://ftp.cc.utexas.edu/pub/AI_ATTIC/Programs/Classic/Eliza/Eliza.c"> +ftp://ftp.cc.utexas.edu/pub/AI_ATTIC/Programs/Classic/Eliza/Eliza.c</a>.</p> + +<hr> +Node:<a name="elvish">elvish</a>, Next:<a rel="next" href="#EMACS">EMACS</a>, Previous:<a rel="previous" href="#ELIZAeffect">ELIZA effect</a>, Up:<a rel="up" href="#chap05">= E =</a> <br> + + +<p><b>elvish</b> n.</p> + +<p>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 <b><a href="#elegant">elegant</a></b>) 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 <b><a href="#elderdays">elder days</a></b>. 2. +By extension, any odd or unreadable typeface produced by a +graphics device. 3. The typeface mundanely called `Böcklin', +an art-Noveau display font.</p> + +<hr> +Node:<a name="EMACS">EMACS</a>, Next:<a rel="next" href="#email">email</a>, Previous:<a rel="previous" href="#elvish">elvish</a>, Up:<a rel="up" href="#chap05">= E +=</a> <br> + + +<p><b>EMACS</b> /ee'maks/ n.</p> + +<p>[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 <b><a href="#TECO">TECO</a></b> under <b><a href="#ITS">ITS</a></b> 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 "<b><a href="#GNU">GNU</a></b> +EMACS" or <b><a href="#GNUMACS">GNUMACS</a></b>, runs principally +under Unix. (Its close relative XEmacs is the second most popular +version.) It includes facilities to run compilation subprocesses +and send and receive mail or news; many hackers spend up to 80% +of their <b><a href="#tubetime">tube time</a></b> inside it. +Other variants include <b><a href="#GOSMACS">GOSMACS</a></b>, CCA +EMACS, UniPress EMACS, Montgomery EMACS, jove, epsilon, and +MicroEMACS. (Though we use the original all-caps spelling here, +it is nowadays very commonly `Emacs'.)</p> + +<p>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 <b><a href="#heavyweight">heavyweight</a></b> and <b><a +href="#baroque">baroque</a></b> for their taste, and expand the +name as `Escape Meta Alt Control Shift' to spoof its heavy +reliance on keystrokes decorated with <b><a href="#buckybits">bucky bits</a></b>. Other spoof expansions +include `Eight Megabytes And Constantly Swapping' (from when that +was a lot of <b><a href="#core">core</a></b>), `Eventually +<code>malloc()</code>s All Computer Storage', and `EMACS Makes A +Computer Slow' (see <b><a href="#recursiveacronym">recursive +acronym</a></b>). See also <b><a href="#vi">vi</a></b>.</p> + +<hr> +Node:<a name="email">email</a>, Next:<a rel="next" href="#emoticon">emoticon</a>, Previous:<a rel="previous" href="#EMACS">EMACS</a>, Up:<a rel="up" href="#chap05">= E +=</a> <br> + + +<p><b>email</b> /ee'mayl/</p> + +<p>(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 <b><a href="#snail-mail">snail-mail</a></b>, <b><a href="#paper-net">paper-net</a></b>, <b><a href="#voice-net">voice-net</a></b>. See <b><a href="#networkaddress">network address</a></b>. 2. vt. To send +electronic mail.</p> + +<p>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 `émaillé' (enameled) +and related to Old French `emmailleüre' (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).</p> + +<p>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.</p> + +<hr> +Node:<a name="emoticon">emoticon</a>, Next:<a rel="next" href="#EMP">EMP</a>, Previous:<a rel="previous" href="#email">email</a>, Up:<a rel="up" href="#chap05">= E +=</a> <br> + + +<p><b>emoticon</b> /ee-moh'ti-kon/ n.</p> + +<p>[common] 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 <b><a +href="#newbie">newbie</a></b>s), resulting in arguments and <b><a +href="#flamewarr">flame war</a></b>s.</p> + +<p>Hundreds of emoticons have been proposed, but only a few are +in common use. These include:</p> + +<blockquote> +<dl> +<dt><tt>:-)</tt></dt> + +<dd>`smiley face' (for humor, laughter, friendliness, +occasionally sarcasm)</dd> + +<dt><tt>:-(</tt></dt> + +<dd>`frowney face' (for sadness, anger, or upset)</dd> + +<dt><tt>;-)</tt></dt> + +<dd>`half-smiley' (<b><a href="#hahaonlyserious">ha ha +only serious</a></b>); also known as `semi-smiley' or `winkey +face'.</dd> + +<dt><tt>:-/</tt></dt> + +<dd>`wry face'</dd> +</dl> +</blockquote> + +<p>(These may become more comprehensible if you tilt your head +sideways, to the left.)</p> + +<p>The first two listed are by far the most frequently +encountered. Hyphenless forms of them are common on CompuServe, +GEnie, and BIX; see also <b><a href="#bixie">bixie</a></b>. On +<b><a href="#Usenet">Usenet</a></b>, `smiley' is often used as a +generic term synonymous with <b><a href="#emoticon">emoticon</a></b>, as well as specifically for the +happy-face emoticon.</p> + +<p>It appears that the emoticon was invented by one Scott Fahlman +on the CMU <b><a href="#bboard">bboard</a></b> systems sometime +between early 1981 and mid-1982. 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].</p> + +<p>Note for the <b><a href="#newbie">newbie</a></b>: 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.</p> + +<hr> +Node:<a name="EMP">EMP</a>, Next:<a rel="next" href="#empire">empire</a>, Previous:<a rel="previous" href="#emoticon">emoticon</a>, Up:<a rel="up" href="#chap05">= +E =</a> <br> + + +<p><b>EMP</b> /E-M-P/</p> + +<p>See <b><a href="#spam">spam</a></b>.</p> + +<hr> +Node:<a name="empire">empire</a>, Next:<a rel="next" href="#engine">engine</a>, Previous:<a rel="previous" href="#EMP">EMP</a>, Up:<a rel="up" href="#chap05">= E =</a> +<br> + + +<p><b>empire</b> n.</p> + +<p>Any of a family of military simulations derived from a game +written by Peter Langston many years ago. A number of +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. Of various commercial derivatives the best +known is probably "Empire Deluxe" on PCs and Amigas.</p> + +<p>Modern empire is a real-time wargame played over the internet +by up to 120 players. Typical games last from 24 hours (blitz) to +a couple of months (long term). The amount of sleep you can get +while playing is a function of the rate at which updates occur +and the number of co-rulers of your country. Empire server +software is available for unix-like machines, and clients for +Unix and other platforms. A comprehensive history of the game is +available at http://www.empire.cx/infopages/History.html. +The Empire resource site is at http://www.empire.cx/.</p> + +<hr> +Node:<a name="engine">engine</a>, Next:<a rel="next" href="#English">English</a>, Previous:<a rel="previous" href="#empire">empire</a>, Up:<a rel="up" href="#chap05">= E +=</a> <br> + + +<p><b>engine</b> n.</p> + +<p>1. A piece of hardware that encapsulates some function but +can't be used without some kind of <b><a href="#frontend">front end</a></b>. 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'.</p> + +<p>The hacker 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'.</p> + +<hr> +Node:<a name="English">English</a>, Next:<a rel="next" href="#enhancement">enhancement</a>, Previous:<a rel="previous" href="#engine">engine</a>, Up:<a rel="up" href="#chap05">= E +=</a> <br> + + +<p><b>English</b></p> + +<p>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. Today the +prefereed shorthand is sinply <b><a href="#source">source</a></b>. 2. The official name of the database +language used by the old Pick Operating System, actually a sort +of crufty, brain-damaged SQL with delusions of grandeur. The name +permitted <b><a href="#marketroid">marketroid</a></b>s to say +"Yes, and you can program our computers in English!" to ignorant +<b><a href="#suit">suit</a></b>s without quite running afoul of +the truth-in-advertising laws.</p> + +<hr> +Node:<a name="enhancement">enhancement</a>, Next:<a rel="next" +href="#ENQ">ENQ</a>, Previous:<a rel="previous" href="#English">English</a>, Up:<a rel="up" href="#chap05">= E +=</a> <br> + + +<p><b>enhancement</b> n.</p> + +<p>Common <b><a href="#marketroid">marketroid</a></b>-speak for a +bug <b><a href="#fix">fix</a></b>. 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 <b><a +href="#feature">feature</a></b> -- or perhaps save some effort by +declaring the bug itself to be a feature.</p> + +<hr> +Node:<a name="ENQ">ENQ</a>, Next:<a rel="next" href="#EOF">EOF</a>, Previous:<a rel="previous" href="#enhancement">enhancement</a>, Up:<a rel="up" href="#chap05">= E =</a> <br> + + +<p><b>ENQ</b> /enkw/ or /enk/</p> + +<p>[from the ASCII mnemonic ENQuire for 0000101] An on-line +convention for querying someone's availability. After opening a +<b><a href="#talkmode">talk mode</a></b> connection to someone +apparently in heavy hack mode, one might type <code>SYN SYN +ENQ?</code> (the SYNs representing notional synchronization +bytes), and expect a return of <b><a href="#ACK">ACK</a></b> or +<b><a href="#NAK">NAK</a></b> depending on whether or not the +person felt interruptible. Compare <b><a href="#ping">ping</a></b>, <b><a href="#finger">finger</a></b>, and +the usage of <code>FOO?</code> listed under <b><a href="#talkmode">talk mode</a></b>.</p> + +<hr> +Node:<a name="EOF">EOF</a>, Next:<a rel="next" href="#EOL">EOL</a>, Previous:<a rel="previous" href="#ENQ">ENQ</a>, +Up:<a rel="up" href="#chap05">= E =</a> <br> + + +<p><b>EOF</b> /E-O-F/ n.</p> + +<p>[abbreviation, `End Of File'] 1. [techspeak] The <b><a href="#out-of-band">out-of-band</a></b> 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 usually -1 under C libraries postdating V6 Unix, but was +originally 0. DOS hackers think EOF is ^Z, and a few Amiga +hackers think it's ^\. 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 <b><a +href="#JCL">JCL</a></b> manual." See also <b><a href="#EOL">EOL</a></b>.</p> + +<hr> +Node:<a name="EOL">EOL</a>, Next:<a rel="next" href="#EOU">EOU</a>, Previous:<a rel="previous" href="#EOF">EOF</a>, +Up:<a rel="up" href="#chap05">= E =</a> <br> + + +<p><b>EOL</b> /E-O-L/ n.</p> + +<p>[End Of Line] Syn. for <b><a href="#newline">newline</a></b>, +derived perhaps from the original CDC6600 Pascal. Now rare, but +widely recognized and occasionally used for brevity. Used in the +example entry under <b><a href="#BNF">BNF</a></b>. See also <b><a +href="#EOF">EOF</a></b>.</p> + +<hr> +Node:<a name="EOU">EOU</a>, Next:<a rel="next" href="#epoch">epoch</a>, Previous:<a rel="previous" href="#EOL">EOL</a>, Up:<a rel="up" href="#chap05">= E =</a> +<br> + + +<p><b>EOU</b> /E-O-U/ n.</p> + +<p>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 <b><a href="#tube">tube</a></b> or flatscreen today.</p> + +<hr> +Node:<a name="epoch">epoch</a>, Next:<a rel="next" href="#epsilon">epsilon</a>, Previous:<a rel="previous" href="#EOU">EOU</a>, Up:<a rel="up" href="#chap05">= E =</a> +<br> + + +<p><b>epoch</b> n.</p> + +<p>[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 <b><a href="#tick">tick</a></b>s +past the epoch. Weird problems may ensue when the clock wraps +around (see <b><a href="#wrapAround">wrap around</a></b>), +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 <b><a href="#walltime">wall time</a></b>. Microsoft +Windows, on the other hand, has an epoch problem every 49.7 days +- but this is seldom noticed as Windows is almost incapable of +staying up continuously for that long.</p> + +<hr> +Node:<a name="epsilon">epsilon</a>, Next:<a rel="next" href="#epsilonsquared">epsilon squared</a>, Previous:<a rel="previous" href="#epoch">epoch</a>, Up:<a rel="up" href="#chap05">= E =</a> <br> + + +<p><b>epsilon</b></p> + +<p>[see <b><a href="#delta">delta</a></b>] 1. n. A small quantity +of anything. "The cost is epsilon." 2. adj. Very small, +negligible; less than <b><a href="#marginal">marginal</a></b>. +"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."</p> + +<hr> +Node:<a name="epsilonsquared">epsilon squared</a>, Next:<a +rel="next" href="#erathe">era the</a>, Previous:<a rel="previous" href="#epsilon">epsilon</a>, Up:<a rel="up" href="#chap05">= E =</a> <br> + + +<p><b>epsilon squared</b> n.</p> + +<p>A quantity even smaller than <b><a href="#epsilon">epsilon</a></b>, 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 <b><a href="#epsilon">epsilon</a></b>, and the cost of the ten-dollar cable +to connect them is epsilon squared. Compare <b><a href="#lostintheunderflow">lost in the underflow</a></b>, +<b><a href="#lostinthenoise">lost in the +noise</a></b>.</p> + +<hr> +Node:<a name="erathe">era the</a>, Next:<a rel="next" href="#EricConspiracy">Eric Conspiracy</a>, Previous:<a rel="previous" href="#epsilonsquared">epsilon squared</a>, Up:<a +rel="up" href="#chap05">= E =</a> <br> + + +<p><b>era</b> n.</p> + +<p>Syn. <b><a href="#epoch">epoch</a></b>. 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 <b><a href="#epoch">epoch</a></b>. The <b><a +href="#epoch">epoch</a></b> usage is recommended.</p> + +<hr> +Node:<a name="EricConspiracy">Eric Conspiracy</a>, Next:<a +rel="next" href="#Eris">Eris</a>, Previous:<a rel="previous" +href="#erathe">era the</a>, Up:<a rel="up" href="#chap05">= E =</a> <br> + + +<p><b>Eric Conspiracy</b> n.</p> + +<p>A shadowy group of mustachioed hackers named Eric first +pinpointed as a sinister conspiracy by an infamous +<i>talk.bizarre</i> 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 <b><a href="#indentstyle">indent +style</a></b>) and Erik Fair (co-author of NNTP); your editor has +heard from more than sixty 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 <a +href="http://www.ccil.org/~esr/ecsl/">http://www.ccil.org/~esr/ecsl/</a> +for full details.</p> + +<hr> +Node:<a name="Eris">Eris</a>, Next:<a rel="next" href="#erotics">erotics</a>, Previous:<a rel="previous" href="#EricConspiracy">Eric Conspiracy</a>, Up:<a rel="up" href="#chap05">= E =</a> <br> + + +<p><b>Eris</b> /e'ris/ n.</p> + +<p>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 <b><a href="#Discordianism">Discordianism</a></b> +and has since been a semi-serious subject of veneration in +several `fringe' cultures, including hackerdom. See <b><a href="#Discordianism">Discordianism</a></b>, <b><a href="#ChurchoftheSubGenius">Church of the +SubGenius</a></b>.</p> + +<hr> +Node:<a name="erotics">erotics</a>, Next:<a rel="next" href="#error33">error 33</a>, Previous:<a rel="previous" href="#Eris">Eris</a>, Up:<a rel="up" href="#chap05">= E =</a> +<br> + + +<p><b>erotics</b> /ee-ro'tiks/ n.</p> + +<p>[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.</p> + +<hr> +Node:<a name="error33">error 33</a>, Next:<a rel="next" href="#eurodemo">eurodemo</a>, Previous:<a rel="previous" href="#erotics">erotics</a>, Up:<a rel="up" href="#chap05">= E +=</a> <br> + + +<p><b>error 33</b> [XEROX PARC] n.</p> + +<p>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).</p> + +<hr> +Node:<a name="eurodemo">eurodemo</a>, Next:<a rel="next" href="#evil">evil</a>, Previous:<a rel="previous" href="#error33">error 33</a>, Up:<a rel="up" href="#chap05">= E =</a> <br> + + +<p><b>eurodemo</b> /yoor'o-dem`-o/</p> + +<p>a <b><a href="#demo">demo</a></b>, sense 4</p> + +<hr> +Node:<a name="evil">evil</a>, Next:<a rel="next" href="#evilandrude">evil and rude</a>, Previous:<a rel="previous" href="#eurodemo">eurodemo</a>, Up:<a rel="up" href="#chap05">= E =</a> <br> + + +<p><b>evil</b> adj.</p> + +<p>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 <b><a href="#cretinous">cretinous</a></b>/<b><a href="#losing">losing</a></b>/<b><a href="#brain-damaged">brain-damaged</a></b> 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 <b><a +href="#BlueGlue">Blue Glue</a></b> interface but decided it +was too evil to deal with." "<b><a href="#TECO">TECO</a></b> 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 <b><a href="#evilandrude">evil and +rude</a></b>.</p> + +<hr> +Node:<a name="evilandrude">evil and rude</a>, Next:<a rel="next" href="#EvilEmpire">Evil Empire</a>, Previous:<a rel="previous" href="#evil">evil</a>, Up:<a rel="up" href="#chap05">= E =</a> <br> + + +<p><b>evil and rude</b> adj.</p> + +<p>Both <b><a href="#evil">evil</a></b> and <b><a href="#rude">rude</a></b>, but with the additional connotation that +the rudeness was due to malice rather than incompetence. Thus, +for example: Microsoft's Windows NT is <i>evil</i> because it's a +competent implementation of a bad design; it's <i>rude</i> +because it's gratuitously incompatible with Unix in places where +compatibility would have been as easy and effective to do; but +it's <i>evil and rude</i> 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 <i>evil and rude</i> is close to the mainstream sense of +`evil'.</p> + +<hr> +Node:<a name="EvilEmpire">Evil Empire</a>, Next:<a rel="next" +href="#exa-">exa-</a>, Previous:<a rel="previous" href="#evilandrude">evil and rude</a>, Up:<a rel="up" href="#chap05">= E =</a> <br> + + +<p><b>Evil Empire</b> n.</p> + +<p>[from Ronald Reagan's famous characterization of the communist +Soviet Union] Formerly <b><a href="#IBM">IBM</a></b>, now <b><a +href="#Microsoft">Microsoft</a></b>. Functionally, the company +most hackers love to hate at any given time. Hackers like to see +themselves as romantic rebels against the Evil Empire, and +frequently adopt this role to the point of ascribing rather more +power and malice to the Empire than it actually has. See also +<b><a href="#Borg">Borg</a></b> and search for Evil Empire +pages on the Web.</p> + +<hr> +Node:<a name="exa-">exa-</a>, Next:<a rel="next" href="#examiningtheentrails">examining the entrails</a>, +Previous:<a rel="previous" href="#EvilEmpire">Evil Empire</a>, +Up:<a rel="up" href="#chap05">= E =</a> <br> + + +<p><b>exa-</b> /ek's*/ pref.</p> + +<p>[SI] See <b><a href="#quantifiers">quantifiers</a></b>.</p> + +<hr> +Node:<a name="examiningtheentrails">examining the +entrails</a>, Next:<a rel="next" href="#EXCH">EXCH</a>, +Previous:<a rel="previous" href="#exa-">exa-</a>, Up:<a rel="up" +href="#chap05">= E =</a> <br> + + +<p><b>examining the entrails</b> n.</p> + +<p>The process of <b><a href="#grovel">grovel</a></b>ling through +a <b><a href="#coredump">core dump</a></b> 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 <b><a href="#runes">runes</a></b>, +<b><a href="#incantation">incantation</a></b>, <b><a href="#blackart">black art</a></b>, <b><a href="#deskcheck">desk +check</a></b>.</p> + +<hr> +Node:<a name="EXCH">EXCH</a>, Next:<a rel="next" href="#excl">excl</a>, Previous:<a rel="previous" href="#examiningtheentrails">examining the entrails</a>, Up:<a +rel="up" href="#chap05">= E =</a> <br> + + +<p><b>EXCH</b> /eks'ch*/ or /eksch/ vt.</p> + +<p>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 <b><a href="#PostScript">PostScript</a></b> exchange operator (which is +usually written in lowercase).</p> + +<hr> +Node:<a name="excl">excl</a>, Next:<a rel="next" href="#EXE">EXE</a>, Previous:<a rel="previous" href="#EXCH">EXCH</a>, +Up:<a rel="up" href="#chap05">= E =</a> <br> + + +<p><b>excl</b> /eks'kl/ n.</p> + +<p>Abbreviation for `exclamation point'. See <b><a href="#bang">bang</a></b>, <b><a href="#shriek">shriek</a></b>, <b><a +href="#ASCII">ASCII</a></b>.</p> + +<hr> +Node:<a name="EXE">EXE</a>, Next:<a rel="next" href="#exec">exec</a>, Previous:<a rel="previous" href="#excl">excl</a>, Up:<a rel="up" href="#chap05">= E =</a> +<br> + + +<p><b>EXE</b> /eks'ee/ or /eek'see/ or /E-X-E/ n.</p> + +<p>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.</p> + +<hr> +Node:<a name="exec">exec</a>, Next:<a rel="next" href="#exerciseleftasan">exercise left as an</a>, Previous:<a +rel="previous" href="#EXE">EXE</a>, Up:<a rel="up" href="#chap05">= E =</a> <br> + + +<p><b>exec</b> /eg-zek'/ or /eks'ek/ vt., n.</p> + +<p>1. [Unix: from `execute'] Synonym for <b><a href="#chain">chain</a></b>, derives from the <code>exec(2)</code> +call. 2. [from `executive'] obs. The command interpreter for an +<b><a href="#OS">OS</a></b> (see <b><a href="#shell">shell</a></b>); 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).</p> + +<p>The mainstream `exec' as an abbreviation for (human) executive +is <i>not</i> used. To a hacker, an `exec' is a always a +program, never a person.</p> + +<hr> +Node:<a name="exerciseleftasan">exercise left as an</a>, +Next:<a rel="next" href="#Exon">Exon</a>, Previous:<a rel="previous" href="#exec">exec</a>, Up:<a rel="up" href="#chap05">= E =</a> <br> + + +<p><b>exercise, left as an</b> adj.</p> + +<p>[from technical books] Used to complete a proof when one +doesn't mind a <b><a href="#handwave">handwave</a></b>, or to +avoid one entirely. The complete phrase is: "The proof [or `the +rest'] is left as an exercise for the reader." This comment +<i>has</i> 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.</p> + +<hr> +Node:<a name="Exon">Exon</a>, Next:<a rel="next" href="#Exploder">Exploder</a>, Previous:<a rel="previous" href="#exerciseleftasan">exercise left as an</a>, Up:<a rel="up" href="#chap05">= E =</a> <br> + + +<p><b>Exon</b> /eks'on/ excl.</p> + +<p>A generic obscenity that quickly entered wide use on the +Internet and Usenet after <b><a href="#BlackThursday">Black +Thursday</a></b>. From the last name of Senator James Exon +(Democrat-Nebraska), primary author of the <b><a href="#CDA">CDA</a></b>.</p> + +<hr> +Node:<a name="Exploder">Exploder</a>, Next:<a rel="next" href="#exploit">exploit</a>, Previous:<a rel="previous" href="#Exon">Exon</a>, Up:<a rel="up" href="#chap05">= E =</a> +<br> + + +<p><b>Exploder</b> n.</p> + +<p>Used within Microsoft to refer to the Windows Explorer, the +interface component of Windows 95 and WinNT 4. Our spies report +that most of the heavy guns at MS came from a Unix background and +use command line utilities; even they are scornful of the +over-gingerbreaded <b><a href="#WIMPenvironment">WIMP +environment</a></b>s that they have been called upon to +create.</p> + +<hr> +Node:<a name="exploit">exploit</a>, Next:<a rel="next" href="#externalmemory">external memory</a>, Previous:<a rel="previous" href="#Exploder">Exploder</a>, Up:<a rel="up" href="#chap05">= E =</a> <br> + + +<p><b>exploit</b> n.</p> + +<p>[originally cracker slang] 1. A vulnerability in software that +can be used for breaking security or otherwise attacking an +Internet host over the network. The <b><a href="#PingODeath">Ping O' Death</a></b> is a famous exploit. +2. More grammatically, a program that exploits an exploit in +sense 1,</p> + +<hr> +Node:<a name="externalmemory">external memory</a>, Next:<a +rel="next" href="#eyecandy">eye candy</a>, Previous:<a rel="previous" href="#exploit">exploit</a>, Up:<a rel="up" href="#chap05">= E =</a> <br> + + +<p><b>external memory</b> n.</p> + +<p>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.</p> + +<hr> +Node:<a name="eyecandy">eye candy</a>, Next:<a rel="next" +href="#eyeballsearch">eyeball search</a>, Previous:<a rel="previous" href="#externalmemory">external memory</a>, Up:<a +rel="up" href="#chap05">= E =</a> <br> + + +<p><b>eye candy</b> /i:' kand`ee/ n.</p> + +<p>[from mainstream slang "ear candy"] A display of some sort +that's presented to <b><a href="#luser">luser</a></b>s to keep +them distracted while the program performs necessary background +tasks. "Give 'em some eye candy while the back-end <b><a href="#slurp">slurp</a></b>s that <b><a href="#BLOB">BLOB</a></b> into +core." Reported as mainstream usage among players of +graphics-heavy computer games. We're also told this term is +mainstream slang for soft pornography, but that sense does not +appear to be live among hackers.</p> + +<hr> +Node:<a name="eyeballsearch">eyeball search</a>, Next:<a rel="next" href="#facetime">face time</a>, Previous:<a rel="previous" href="#eyecandy">eye candy</a>, Up:<a rel="up" +href="#chap05">= E =</a> <br> + + +<p><b>eyeball search</b> n.,v.</p> + +<p>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 <b><a href="#grep">grep</a></b> or any +other automated search tool. Also called a <b><a href="#vgrep">vgrep</a></b>; compare <b><a href="#vdiff">vdiff</a></b>, <b><a href="#deskcheck">desk +check</a></b>.</p> + +<hr> +Node:<a name="chap06">= F =</a>, Next:<a rel="next" href="#chap07">= G =</a>, Previous:<a rel="previous" href="#chap05">= E =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= F =</h2> + +<ul> +<li><a href="#facetime">face time</a>:</li> + +<li><a href="#factor">factor</a>:</li> + +<li><a href="#fairings">fairings</a>:</li> + +<li><a href="#fallover">fall over</a>:</li> + +<li><a href="#fallThrough">fall through</a>:</li> + +<li><a href="#fan">fan</a>:</li> + +<li><a href="#fandangooncore">fandango on core</a>:</li> + +<li><a href="#FAQ">FAQ</a>:</li> + +<li><a href="#FAQlist">FAQ list</a>:</li> + +<li><a href="#FAQL">FAQL</a>:</li> + +<li><a href="#faradize">faradize</a>:</li> + +<li><a href="#farkled">farkled</a>:</li> + +<li><a href="#farming">farming</a>:</li> + +<li><a href="#fascist">fascist</a>:</li> + +<li><a href="#fatelectrons">fat electrons</a>:</li> + +<li><a href="#fat-finger">fat-finger</a>:</li> + +<li><a href="#faulty">faulty</a>:</li> + +<li><a href="#fdleak">fd leak</a>:</li> + +<li><a href="#fearandloathing">fear and loathing</a>:</li> + +<li><a href="#feature">feature</a>:</li> + +<li><a href="#featurecreature">feature creature</a>:</li> + +<li><a href="#featurecreep">feature creep</a>:</li> + +<li><a href="#featurekey">feature key</a>:</li> + +<li><a href="#featureshock">feature shock</a>:</li> + +<li><a href="#featurectomy">featurectomy</a>:</li> + +<li><a href="#feep">feep</a>:</li> + +<li><a href="#feeper">feeper</a>:</li> + +<li><a href="#feepingcreature">feeping creature</a>:</li> + +<li><a href="#feepingcreaturism">feeping creaturism</a>:</li> + +<li><a href="#feetchfeetch">feetch feetch</a>:</li> + +<li><a href="#fence">fence</a>:</li> + +<li><a href="#fenceposterror">fencepost error</a>:</li> + +<li><a href="#fiber-seekingbackhoe">fiber-seeking +backhoe</a>:</li> + +<li><a href="#FidoNet">FidoNet</a>:</li> + +<li><a href="#fieldcircus">field circus</a>:</li> + +<li><a href="#fieldservoid">field servoid</a>:</li> + +<li><a href="#Fight-o-net">Fight-o-net</a>:</li> + +<li><a href="#FileAttach">File Attach</a>:</li> + +<li><a href="#FileRequest">File Request</a>:</li> + +<li><a href="#filesignature">file signature</a>:</li> + +<li><a href="#filk">filk</a>:</li> + +<li><a href="#filmat11">film at 11</a>:</li> + +<li><a href="#filter">filter</a>:</li> + +<li><a href="#FinaglesLaw">Finagle's Law</a>:</li> + +<li><a href="#fine">fine</a>:</li> + +<li><a href="#finger">finger</a>:</li> + +<li><a href="#fingertrouble">finger trouble</a>:</li> + +<li><a href="#finger-pointingsyndrome">finger-pointing +syndrome</a>:</li> + +<li><a href="#finn">finn</a>:</li> + +<li><a href="#firebottle">firebottle</a>:</li> + +<li><a href="#firefighting">firefighting</a>:</li> + +<li><a href="#firehosesyndrome">firehose syndrome</a>:</li> + +<li><a href="#firewallcode">firewall code</a>:</li> + +<li><a href="#firewallmachine">firewall machine</a>:</li> + +<li><a href="#fireworksmode">fireworks mode</a>:</li> + +<li><a href="#firmware">firmware</a>:</li> + +<li><a href="#firmy">firmy</a>:</li> + +<li><a href="#fish">fish</a>:</li> + +<li><a href="#FISHqueue">FISH queue</a>:</li> + +<li><a href="#FITNR">FITNR</a>:</li> + +<li><a href="#fix">fix</a>:</li> + +<li><a href="#FIXME">FIXME</a>:</li> + +<li><a href="#flag">flag</a>:</li> + +<li><a href="#flagday">flag day</a>:</li> + +<li><a href="#flaky">flaky</a>:</li> + +<li><a href="#flamage">flamage</a>:</li> + +<li><a href="#flame">flame</a>:</li> + +<li><a href="#flamebait">flame bait</a>:</li> + +<li><a href="#flameon">flame on</a>:</li> + +<li><a href="#flamewarr">flame war</a>:</li> + +<li><a href="#flamer">flamer</a>:</li> + +<li><a href="#flap">flap</a>:</li> + +<li><a href="#flarp">flarp</a>:</li> + +<li><a href="#flashcrowd">flash crowd</a>:</li> + +<li><a href="#flat">flat</a>:</li> + +<li><a href="#flat-ASCII">flat-ASCII</a>:</li> + +<li><a href="#flat-file">flat-file</a>:</li> + +<li><a href="#flatten">flatten</a>:</li> + +<li><a href="#flavor">flavor</a>:</li> + +<li><a href="#flavorful">flavorful</a>:</li> + +<li><a href="#flippy">flippy</a>:</li> + +<li><a href="#flood">flood</a>:</li> + +<li><a href="#flowchart">flowchart</a>:</li> + +<li><a href="#flowerkey">flower key</a>:</li> + +<li><a href="#flush">flush</a>:</li> + +<li><a href="#flypage">flypage</a>:</li> + +<li><a href="#Flyspeck3">Flyspeck 3</a>:</li> + +<li><a href="#flytrap">flytrap</a>:</li> + +<li><a href="#FM">FM</a>:</li> + +<li><a href="#fnord">fnord</a>:</li> + +<li><a href="#FOAF">FOAF</a>:</li> + +<li><a href="#FOD">FOD</a>:</li> + +<li><a href="#foldcase">fold case</a>:</li> + +<li><a href="#followup">followup</a>:</li> + +<li><a href="#fontology">fontology</a>:</li> + +<li><a href="#foo">foo</a>:</li> + +<li><a href="#foobar">foobar</a>:</li> + +<li><a href="#fool">fool</a>:</li> + +<li><a href="#foolfile">fool file</a>:</li> + +<li><a href="#Foonly">Foonly</a>:</li> + +<li><a href="#footprint">footprint</a>:</li> + +<li><a href="#forfree">for free</a>:</li> + +<li><a href="#fortherestofus">for the rest of +us</a>:</li> + +<li><a href="#forvaluesof">for values of</a>:</li> + +<li><a href="#fora">fora</a>:</li> + +<li><a href="#foreground">foreground</a>:</li> + +<li><a href="#fork">fork</a>:</li> + +<li><a href="#forkbomb">fork bomb</a>:</li> + +<li><a href="#forked">forked</a>:</li> + +<li><a href="#Fortrash">Fortrash</a>:</li> + +<li><a href="#fortunecookie">fortune cookie</a>:</li> + +<li><a href="#forum">forum</a>:</li> + +<li><a href="#fossil">fossil</a>:</li> + +<li><a href="#fourcolorglossies">four-color glossies</a>:</li> + +<li><a href="#frag">frag</a>:</li> + +<li><a href="#fragile">fragile</a>:</li> + +<li><a href="#fred">fred</a>:</li> + +<li><a href="#FredFoobar">Fred Foobar</a>:</li> + +<li><a href="#frednet">frednet</a>:</li> + +<li><a href="#freesoftware">free software</a>:</li> + +<li><a href="#freeware">freeware</a>:</li> + +<li><a href="#freeze">freeze</a>:</li> + +<li><a href="#fried">fried</a>:</li> + +<li><a href="#frink">frink</a>:</li> + +<li><a href="#friode">friode</a>:</li> + +<li><a href="#fritterware">fritterware</a>:</li> + +<li><a href="#frob">frob</a>:</li> + +<li><a href="#frobnicate">frobnicate</a>:</li> + +<li><a href="#frobnitz">frobnitz</a>:</li> + +<li><a href="#frog">frog</a>:</li> + +<li><a href="#frogging">frogging</a>:</li> + +<li><a href="#frontend">front end</a>:</li> + +<li><a href="#frotz">frotz</a>:</li> + +<li><a href="#frotzed">frotzed</a>:</li> + +<li><a href="#frowney">frowney</a>:</li> + +<li><a href="#FRS">FRS</a>:</li> + +<li><a href="#fry">fry</a>:</li> + +<li><a href="#fscking">fscking</a>:</li> + +<li><a href="#FSF">FSF</a>:</li> + +<li><a href="#FTP">FTP</a>:</li> + +<li><a href="#-fu">-fu</a>:</li> + +<li><a href="#FUBAR">FUBAR</a>:</li> + +<li><a href="#fuckmeharder">fuck me harder</a>:</li> + +<li><a href="#FUD">FUD</a>:</li> + +<li><a href="#FUDwars">FUD wars</a>:</li> + +<li><a href="#fudge">fudge</a>:</li> + +<li><a href="#fudgefactor">fudge factor</a>:</li> + +<li><a href="#fuelup">fuel up</a>:</li> + +<li><a href="#FullMonty">Full Monty</a>:</li> + +<li><a href="#fum">fum</a>:</li> + +<li><a href="#functino">functino</a>:</li> + +<li><a href="#funky">funky</a>:</li> + +<li><a href="#funnymoney">funny money</a>:</li> + +<li><a href="#furrfu">furrfu</a>:</li> + +<li><a href="#fuzzball">fuzzball</a>:</li> +</ul> + +<hr> +Node:<a name="facetime">face time</a>, Next:<a rel="next" +href="#factor">factor</a>, Previous:<a rel="previous" href="#eyeballsearch">eyeball search</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>face time</b> n.</p> + +<p>[common] 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."</p> + +<hr> +Node:<a name="factor">factor</a>, Next:<a rel="next" href="#fairings">fairings</a>, Previous:<a rel="previous" href="#facetime">face time</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>factor</b> n.</p> + +<p>See <b><a href="#coefficientofX">coefficient of +X</a></b>.</p> + +<hr> +Node:<a name="fairings">fairings</a>, Next:<a rel="next" href="#fallover">fall over</a>, Previous:<a rel="previous" href="#factor">factor</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>fairings</b> n. /fer'ingz/</p> + +<p>[FreeBSD; orig. a typo for `fairness'] A term thrown out in +discussion whenever a completely and transparently nonsensical +argument in one's favor(?) seems called for, e,g. at the end of a +really long thread for which the outcome is no longer even cared +about since everyone is now so sick of it; or in rebuttal to +another nonsensical argument ("Change the loader to look for +/kernel.pl? What about fairings?")</p> + +<hr> +Node:<a name="fallover">fall over</a>, Next:<a rel="next" +href="#fallThrough">fall through</a>, Previous:<a rel="previous" href="#fairings">fairings</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>fall over</b> vi.</p> + +<p>[IBM] Yet another synonym for <b><a href="#crash">crash</a></b> or <b><a href="#lose">lose</a></b>. `Fall +over hard' equates to <b><a href="#crashandburn">crash and +burn</a></b>.</p> + +<hr> +Node:<a name="fallThrough">fall through</a>, Next:<a rel="next" href="#fan">fan</a>, Previous:<a rel="previous" href="#fallover">fall over</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>fall through</b> v.</p> + +<p>(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 <i>really</i> 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 <code>case</code> label +other than by jumping there from the switch header, passing a +point where one would normally expect to find a +<code>break</code>. A trivial example:</p> + +<pre> +switch (color) +{ +case GREEN: + do_green(); + break; +case PINK: + do_pink(); + /* FALL THROUGH */ +case RED: + do_red(); + break; +default: + do_blue(); + break; +} +</pre> + +<p>The variant spelling <code>/* FALL THRU */</code> is also +common.</p> + +<p>The effect of the above code is to <code>do_green()</code> +when color is <code>GREEN</code>, <code>do_red()</code> when +color is <code>RED</code>, <code>do_blue()</code> on any other +color other than <code>PINK</code>, and (and this is the +important part) <code>do_pink()</code> <i>and then</i> +<code>do_red()</code> when color is <code>PINK</code>. +Fall-through is <b><a href="#consideredharmful">considered +harmful</a></b> 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 +<b><a href="#Duffsdevice">Duff's device</a></b>.</p> + +<hr> +Node:<a name="fan">fan</a>, Next:<a rel="next" href="#fandangooncore">fandango on core</a>, Previous:<a rel="previous" href="#fallThrough">fall through</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>fan</b> n.</p> + +<p>Without qualification, indicates a fan of science fiction, +especially one who goes to <b><a href="#con">con</a></b>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."</p> + +<hr> +Node:<a name="fandangooncore">fandango on core</a>, Next:<a +rel="next" href="#FAQ">FAQ</a>, Previous:<a rel="previous" href="#fan">fan</a>, Up:<a rel="up" href="#chap06">= F =</a> +<br> + + +<p><b>fandango on core</b> n.</p> + +<p>[Unix/C hackers, from the Iberian dance] In C, a wild pointer +that runs out of bounds, causing a <b><a href="#coredump">core +dump</a></b>, or corrupts the <code>malloc(3)</code> <b><a href="#arena">arena</a></b> 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 (or Windows +boxes, which have an MMU but use it incompetently), this can +corrupt the OS itself, causing massive lossage. Other frenetic +dances such as the cha-cha or the watusi, may be substituted. See +<b><a href="#aliasingbug">aliasing bug</a></b>, <b><a href="#precedencelossage">precedence lossage</a></b>, <b><a href="#smashthestack">smash the stack</a></b>, <b><a href="#memoryleak">memory leak</a></b>, <b><a href="#memorysmash">memory smash</a></b>, <b><a href="#overrunscrew">overrun screw</a></b>, <b><a href="#core">core</a></b>.</p> + +<hr> +Node:<a name="FAQ">FAQ</a>, Next:<a rel="next" href="#FAQlist">FAQ list</a>, Previous:<a rel="previous" href="#fandangooncore">fandango on core</a>, Up:<a rel="up" +href="#chap06">= F =</a> <br> + + +<p><b>FAQ</b> /F-A-Q/ or /fak/ n.</p> + +<p>[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.</p> + +<p>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 <code>#</code> character?" are both +Frequently Asked Questions. Several FAQs refer readers to this +file.</p> + +<hr> +Node:<a name="FAQlist">FAQ list</a>, Next:<a rel="next" href="#FAQL">FAQL</a>, Previous:<a rel="previous" href="#FAQ">FAQ</a>, +Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>FAQ list</b> /F-A-Q list/ or /fak list/ n.</p> + +<p>[common; Usenet] Syn <b><a href="#FAQ">FAQ</a></b>, sense +2.</p> + +<hr> +Node:<a name="FAQL">FAQL</a>, Next:<a rel="next" href="#faradize">faradize</a>, Previous:<a rel="previous" href="#FAQlist">FAQ list</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>FAQL</b> /fa'kl/ n.</p> + +<p>Syn. <b><a href="#FAQlist">FAQ list</a></b>.</p> + +<hr> +Node:<a name="faradize">faradize</a>, Next:<a rel="next" href="#farkled">farkled</a>, Previous:<a rel="previous" href="#FAQL">FAQL</a>, Up:<a rel="up" href="#chap06">= F =</a> +<br> + + +<p><b>faradize</b> /far'*-di:z/ v.</p> + +<p>[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.</p> + +<hr> +Node:<a name="farkled">farkled</a>, Next:<a rel="next" href="#farming">farming</a>, Previous:<a rel="previous" href="#faradize">faradize</a>, Up:<a rel="up" href="#chap06">= +F =</a> <br> + + +<p><b>farkled</b> /far'kld/ adj.</p> + +<p>[DeVry Institute of Technology, Atlanta] Syn. <b><a href="#hosed">hosed</a></b>. 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.</p> + +<hr> +Node:<a name="farming">farming</a>, Next:<a rel="next" href="#fascist">fascist</a>, Previous:<a rel="previous" href="#farkled">farkled</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>farming</b> n.</p> + +<p>[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 <b><a href="#crash">crash</a></b>. Typically used as follows: "Oh no, the +machine has just crashed; I hope the hard drive hasn't gone <b><a +href="#farming">farming</a></b> again." No longer common; modern +drives automatically park their heads in a safe zone on +power-down, so it takes a real mechanical problem to induce +this.</p> + +<hr> +Node:<a name="fascist">fascist</a>, Next:<a rel="next" href="#fatelectrons">fat electrons</a>, Previous:<a rel="previous" +href="#farming">farming</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>fascist</b> adj.</p> + +<p>1. [common] 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 <b><a href="#tourist">tourist</a></b> or under the influence +of German/Yiddish `faschistisch'). 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 <b><a href="#bondage-and-disciplinelanguage">bondage-and-discipline +language</a></b>, although that term is global rather than +local.</p> + +<hr> +Node:<a name="fatelectrons">fat electrons</a>, Next:<a rel="next" href="#fat-finger">fat-finger</a>, Previous:<a rel="previous" href="#fascist">fascist</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>fat electrons</b> n.</p> + +<p>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 <i>bottom</i> 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 <b><a href="#bogon">bogon</a></b> absorption --ESR] Compare <b><a href="#bogon">bogon</a></b>, <b><a href="#magicsmoke">magic +smoke</a></b>.</p> + +<hr> +Node:<a name="fat-finger">fat-finger</a>, Next:<a rel="next" +href="#faulty">faulty</a>, Previous:<a rel="previous" href="#fatelectrons">fat electrons</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>fat-finger</b> vt.</p> + +<p>1. To introduce a typo while editing in such a way that the +resulting manglification of a configuration file does something +useless, damaging, or wildly unexpected. "NSI fat-fingered their +DNS zone file and took half the net down again." 2. More +generally, any typo that produces dramatically bad results.</p> + +<hr> +Node:<a name="faulty">faulty</a>, Next:<a rel="next" href="#fdleak">fd leak</a>, Previous:<a rel="previous" href="#fat-finger">fat-finger</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>faulty</b> adj.</p> + +<p>Non-functional; buggy. Same denotation as <b><a href="#bletcherous">bletcherous</a></b>, <b><a href="#losing">losing</a></b>, q.v., but the connotation is much +milder.</p> + +<hr> +Node:<a name="fdleak">fd leak</a>, Next:<a rel="next" href="#fearandloathing">fear and loathing</a>, Previous:<a rel="previous" href="#faulty">faulty</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>fd leak</b> /F-D leek/ n.</p> + +<p>A kind of programming bug analogous to a <b><a href="#coreleak">core leak</a></b>, in which a program fails to +close file descriptors (`fd's) after file operations are +completed, and thus eventually runs out of them. See <b><a href="#leak">leak</a></b>.</p> + +<hr> +Node:<a name="fearandloathing">fear and loathing</a>, +Next:<a rel="next" href="#feature">feature</a>, Previous:<a rel="previous" href="#fdleak">fd leak</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>fear and loathing</b> n.</p> + +<p>[from Hunter S. Thompson] A state inspired by the prospect of +dealing with certain real-world systems and standards that are +totally <b><a href="#brain-damaged">brain-damaged</a></b> but +ubiquitous -- Intel 8086s, or <b><a href="#COBOL">COBOL</a></b>, +or <b><a href="#EBCDIC">EBCDIC</a></b>, or any <b><a href="#IBM">IBM</a></b> machine bigger than a workstation. "Ack! They +want PCs to be able to talk to the AI machine. Fear and loathing +time!"</p> + +<hr> +Node:<a name="feature">feature</a>, Next:<a rel="next" href="#featurecreature">feature creature</a>, Previous:<a rel="previous" href="#fearandloathing">fear and loathing</a>, +Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>feature</b> n.</p> + +<p>1. [common] A good property or behavior (as of a program). +Whether it was intended or not is immaterial. 2. [common] An +intended property or behavior (as of a program). Whether it is +good or not is immaterial (but if bad, it is also a <b><a href="#misfeature">misfeature</a></b>). 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 <b><a href="#feature">feature</a></b> and not a <b><a +href="#bug">bug</a></b>. This kind of feature is sometimes called +a <b><a href="#miswart">miswart</a></b>; 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 <code>format</code> function is the +ability to print numbers in two different Roman-numeral formats +(see <b><a href="#bellswhistlesandgongs">bells whistles +and gongs</a></b>). 5. A property or behavior that was put in to +help someone else but that happens to be in your way. 6. [common] +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 <b><a href="#feature">feature</a></b> +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 <b><a href="#feetchfeetch">feetch +feetch</a></b>, <b><a href="#creepingfeaturism">creeping +featurism</a></b>, <b><a href="#wart">wart</a></b>, <b><a href="#greenlightning">green lightning</a></b>.</p> + +<p>The relationship among bugs, features, misfeatures, warts, and +miswarts might be clarified by the following hypothetical +exchange between two hackers on an airliner:</p> + +<p>A: "This seat doesn't recline."</p> + +<p>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."</p> + +<p>A: "Oh. Then it's a misfeature; they should have increased the +spacing between rows here."</p> + +<p>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."</p> + +<p>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."</p> + +<p>B: "Indeed."</p> + +<p>`Undocumented feature' is a common, allegedly humorous +euphemism for a <b><a href="#bug">bug</a></b>. 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 <b><a href="#computergeek">computer +geek</a></b>, sense 2).</p> + +<hr> +Node:<a name="featurecreature">feature creature</a>, Next:<a +rel="next" href="#featurecreep">feature creep</a>, Previous:<a +rel="previous" href="#feature">feature</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>feature creature</b> n.</p> + +<p>[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 <b><a href="#taste">taste</a></b>. 2. Alternately, a mythical being that +induces otherwise rational programmers to perpetrate such crocks. +See also <b><a href="#feepingcreaturism">feeping +creaturism</a></b>, <b><a href="#creepingfeaturism">creeping +featurism</a></b>.</p> + +<hr> +Node:<a name="featurecreep">feature creep</a>, Next:<a rel="next" href="#featurekey">feature key</a>, Previous:<a rel="previous" href="#featurecreature">feature creature</a>, Up:<a +rel="up" href="#chap06">= F =</a> <br> + + +<p><b>feature creep</b> n.</p> + +<p>[common] The result of <b><a href="#creepingfeaturism">creeping featurism</a></b>, as in "Emacs +has a bad case of feature creep".</p> + +<hr> +Node:<a name="featurekey">feature key</a>, Next:<a rel="next" +href="#featureshock">feature shock</a>, Previous:<a rel="previous" href="#featurecreep">feature creep</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>feature key</b> n.</p> + +<p>[common] 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), <b><a href="#splat">splat</a></b>, +`open-apple' or (officially, in Mac documentation) the `command +key'. In French, the term `papillon' (butterfly) has been +reported. The proliferation of terms for this creature may +illustrate one subtle peril of iconic interfaces.</p> + +<p>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"!</p> + +<p>There is some dispute as to the proper (Swedish) name of this +symbol. It technically stands for the word `sevärdhet' +(thing worth seeing); many of these are old churches. Some Swedes +report as an idiom for the sign the word `kyrka', cognate to +English `church' and pronounced (roughly) /chur'ka/ in modern +Swedish. Others say this is nonsense. Other idioms reported for +the sign are `runa' (rune) or `runsten' /roon'stn/ (runestone), +derived from the fact that many of the interesting features are +Viking rune-stones. The term `fornminne' /foorn'min'*/ (relic of +antiquity, ancient monument) is also reported, especially among +those who think that the Mac itself is a relic of antiquity.</p> + +<hr> +Node:<a name="featureshock">feature shock</a>, Next:<a rel="next" href="#featurectomy">featurectomy</a>, Previous:<a rel="previous" href="#featurekey">feature key</a>, Up:<a rel="up" +href="#chap06">= F =</a> <br> + + +<p><b>feature shock</b> n.</p> + +<p>[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.</p> + +<hr> +Node:<a name="featurectomy">featurectomy</a>, Next:<a rel="next" +href="#feep">feep</a>, Previous:<a rel="previous" href="#featureshock">feature shock</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>featurectomy</b> /fee`ch*r-ek't*-mee/ n.</p> + +<p>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 +<b><a href="#misfeature">misfeature</a></b>.) Reluctant +featurectomies are performed to satisfy some external constraint +such as code size or execution speed.</p> + +<hr> +Node:<a name="feep">feep</a>, Next:<a rel="next" href="#feeper">feeper</a>, Previous:<a rel="previous" href="#featurectomy">featurectomy</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>feep</b> /feep/</p> + +<p>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 <b><a href="#beep">beep</a></b>). 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: +<b><a href="#beep">beep</a></b>, `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 <b><a href="#ding">ding</a></b>.</p> + +<hr> +Node:<a name="feeper">feeper</a>, Next:<a rel="next" href="#feepingcreature">feeping creature</a>, Previous:<a rel="previous" href="#feep">feep</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>feeper</b> /fee'pr/ n.</p> + +<p>The device in a terminal or workstation (usually a loudspeaker +of some kind) that makes the <b><a href="#feep">feep</a></b> +sound.</p> + +<hr> +Node:<a name="feepingcreature">feeping creature</a>, Next:<a +rel="next" href="#feepingcreaturism">feeping creaturism</a>, +Previous:<a rel="previous" href="#feeper">feeper</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>feeping creature</b> n.</p> + +<p>[from <b><a href="#feepingcreaturism">feeping +creaturism</a></b>] An unnecessary feature; a bit of <b><a href="#chrome">chrome</a></b> that, in the speaker's judgment, is the +camel's nose for a whole horde of new features.</p> + +<hr> +Node:<a name="feepingcreaturism">feeping creaturism</a>, +Next:<a rel="next" href="#feetchfeetch">feetch feetch</a>, +Previous:<a rel="previous" href="#feepingcreature">feeping +creature</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>feeping creaturism</b> /fee'ping kree`ch*r-izm/ n.</p> + +<p>A deliberate spoonerism for <b><a href="#creepingfeaturism">creeping featurism</a></b>, 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.</p> + +<hr> +Node:<a name="feetchfeetch">feetch feetch</a>, Next:<a rel="next" href="#fence">fence</a>, Previous:<a rel="previous" href="#feepingcreaturism">feeping creaturism</a>, Up:<a rel="up" +href="#chap06">= F =</a> <br> + + +<p><b>feetch feetch</b> /feech feech/ interj.</p> + +<p>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".</p> + +<hr> +Node:<a name="fence">fence</a>, Next:<a rel="next" href="#fenceposterror">fencepost error</a>, Previous:<a rel="previous" href="#feetchfeetch">feetch feetch</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>fence</b> n. 1.</p> + +<p>A sequence of one or more distinguished (<b><a href="#out-of-band">out-of-band</a></b>) 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 <b><a href="#zigamorph">zigamorph</a></b>. 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".</p> + +<hr> +Node:<a name="fenceposterror">fencepost error</a>, Next:<a +rel="next" href="#fiber-seekingbackhoe">fiber-seeking +backhoe</a>, Previous:<a rel="previous" href="#fence">fence</a>, +Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>fencepost error</b> n.</p> + +<p>1. [common] 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 <b><a href="#zeroth">zeroth</a></b> and <b><a href="#offbyoneerror">off-by-one error</a></b>, 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.)</p> + +<hr> +Node:<a name="fiber-seekingbackhoe">fiber-seeking backhoe</a>, +Next:<a rel="next" href="#FidoNet">FidoNet</a>, Previous:<a rel="previous" href="#fenceposterror">fencepost error</a>, Up:<a +rel="up" href="#chap06">= F =</a> <br> + + +<p><b>fiber-seeking backhoe</b></p> + +<p>[common among backbone ISP personnel] Any of a genus of large, +disruptive machines which routinely cut critical backbone links, +creating Internet outages and <b><a href="#packetoverair">packet over air</a></b> problems.</p> + +<hr> +Node:<a name="FidoNet">FidoNet</a>, Next:<a rel="next" href="#fieldcircus">field circus</a>, Previous:<a rel="previous" +href="#fiber-seekingbackhoe">fiber-seeking backhoe</a>, Up:<a +rel="up" href="#chap06">= F =</a> <br> + + +<p><b>FidoNet</b> n.</p> + +<p>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. For years FidoNet actually grew faster than +Usenet, but the advent of cheap Internet access probably means +its days are numbered. In early 1999 Fidonet has approximately +30,000 nodes, down from 38K in 1996.</p> + +<hr> +Node:<a name="fieldcircus">field circus</a>, Next:<a rel="next" href="#fieldservoid">field servoid</a>, Previous:<a +rel="previous" href="#FidoNet">FidoNet</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>field circus</b> n.</p> + +<p>[a derogatory pun on `field service'] The field service +organization of any hardware manufacturer, but originally <b><a +href="#DEC">DEC</a></b>. There is an entire genre of jokes about +field circus engineers:</p> + +<pre> +Q: How can you recognize a 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 field circus engineer + who is out of gas? +A: He's changing one tire at a time to see which one is flat. + +Q: How can you tell it's <i>your</i> field circus engineer? +A: The spare is flat, too. +</pre> + +<p>[See <b><a href="#Easteregging">Easter egging</a></b> for +additional insight on these jokes.]</p> + +<p>There is also the `Field Circus Cheer' (from the old <b><a +href="#planfile">plan file</a></b> for DEC on MIT-AI):</p> + +<pre> +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. +</pre> + +<p>(DEC's service HQ, still extant under the Compaq regime, is +located in Maynard, Massachusetts.)</p> + +<hr> +Node:<a name="fieldservoid">field servoid</a>, Next:<a rel="next" href="#Fight-o-net">Fight-o-net</a>, Previous:<a rel="previous" href="#fieldcircus">field circus</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>field servoid</b> [play on `android'] /fee'ld ser'voyd/ +n.</p> + +<p>Representative of a field service organization (see <b><a +href="#fieldcircus">field circus</a></b>). This has many of +the implications of <b><a href="#droid">droid</a></b>.</p> + +<hr> +Node:<a name="Fight-o-net">Fight-o-net</a>, Next:<a rel="next" +href="#FileAttach">File Attach</a>, Previous:<a rel="previous" +href="#fieldservoid">field servoid</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>Fight-o-net</b> n.</p> + +<p>[FidoNet] Deliberate distortion of <b><a href="#FidoNet">FidoNet</a></b>, often applied after a flurry of <b><a +href="#flamage">flamage</a></b> in a particular <b><a href="#echo">echo</a></b>, especially the SYSOP echo or Fidonews (see +<b><a href="#Snooze">'Snooze</a></b>).</p> + +<hr> +Node:<a name="FileAttach">File Attach</a>, Next:<a rel="next" +href="#FileRequest">File Request</a>, Previous:<a rel="previous" href="#Fight-o-net">Fight-o-net</a>, Up:<a rel="up" +href="#chap06">= F =</a> <br> + + +<p><b>File Attach</b> [FidoNet]</p> + +<p>1. n. A file sent along with a mail message from one FidoNet +to another. 2. vt. Sending someone a file by using the File +Attach option in a FidoNet mailer.</p> + +<hr> +Node:<a name="FileRequest">File Request</a>, Next:<a rel="next" href="#filesignature">file signature</a>, Previous:<a +rel="previous" href="#FileAttach">File Attach</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>File Request</b> [FidoNet]</p> + +<p>1. n. The <b><a href="#FidoNet">FidoNet</a></b> equivalent of +<b><a href="#FTP">FTP</a></b>, in which one FidoNet system +automatically dials another and <b><a href="#snarf">snarf</a></b>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 FidoNet +mailer.</p> + +<hr> +Node:<a name="filesignature">file signature</a>, Next:<a rel="next" href="#filk">filk</a>, Previous:<a rel="previous" href="#FileRequest">File Request</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>file signature</b> n.</p> + +<p>A <b><a href="#magicnumber">magic number</a></b>, sense +3.</p> + +<hr> +Node:<a name="filk">filk</a>, Next:<a rel="next" href="#filmat11">film at 11</a>, Previous:<a rel="previous" +href="#filesignature">file signature</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>filk</b> /filk/ n.,v.</p> + +<p>[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 and/or music, 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 <b><a href="#doublebucky">double bucky</a></b> for +an example. Compare <b><a href="#grilf">grilf</a></b>, <b><a +href="#hing">hing</a></b>, <b><a href="#pr0n">pr0n</a></b>, and +<b><a href="#newsfroup">newsfroup</a></b>.</p> + +<hr> +Node:<a name="filmat11">film at 11</a>, Next:<a rel="next" +href="#filter">filter</a>, Previous:<a rel="previous" href="#filk">filk</a>, Up:<a rel="up" href="#chap06">= F =</a> +<br> + + +<p><b>film at 11</b></p> + +<p>[MIT: in parody of TV newscasters] 1. Used in conversation to +announce ordinary events, with a sarcastic implication that these +events are earth-shattering. "<b><a href="#ITS">ITS</a></b> +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, +<i>without</i> 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.</p> + +<p>The variant "MPEGs at 11" has recently been cited (MPEG is a +digital-video format.)</p> + +<hr> +Node:<a name="filter">filter</a>, Next:<a rel="next" href="#FinaglesLaw">Finagle's Law</a>, Previous:<a rel="previous" +href="#filmat11">film at 11</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>filter</b> n.</p> + +<p>[very common; orig. <b><a href="#Unix">Unix</a></b>, now also +in <b><a href="#MS-DOS">MS-DOS</a></b>] 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 <b><a href="#plumbing">plumbing</a></b>). +Compare <b><a href="#sponge">sponge</a></b>.</p> + +<hr> +Node:<a name="FinaglesLaw">Finagle's Law</a>, Next:<a rel="next" href="#fine">fine</a>, Previous:<a rel="previous" href="#filter">filter</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>Finagle's Law</b> n.</p> + +<p>The generalized or `folk' version of <b><a href="#MurphysLaw">Murphy's Law</a></b>, 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 +<b><a href="#HanlonsRazor">Hanlon's Razor</a></b>). 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.</p> + +<hr> +Node:<a name="fine">fine</a>, Next:<a rel="next" href="#finger">finger</a>, Previous:<a rel="previous" href="#FinaglesLaw">Finagle's Law</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>fine</b> adj.</p> + +<p>[WPI] Good, but not good enough to be <b><a href="#cuspy">cuspy</a></b>. The word `fine' is used elsewhere, of +course, but without the implicit comparison to the higher level +implied by <b><a href="#cuspy">cuspy</a></b>.</p> + +<hr> +Node:<a name="finger">finger</a>, Next:<a rel="next" href="#fingertrouble">finger trouble</a>, Previous:<a rel="previous" href="#fine">fine</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>finger</b></p> + +<p>[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 <b><a href="#planfile">plan +file</a></b> left by the user (see also <b><a href="#HackingXforY">Hacking X for Y</a></b>). 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 <b><a href="#flamer">flamer</a></b>s.</p> + +<hr> +Node:<a name="fingertrouble">finger trouble</a>, Next:<a rel="next" href="#finger-pointingsyndrome">finger-pointing +syndrome</a>, Previous:<a rel="previous" href="#finger">finger</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>finger trouble</b> n.</p> + +<p>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?".</p> + +<hr> +Node:<a name="finger-pointingsyndrome">finger-pointing +syndrome</a>, Next:<a rel="next" href="#finn">finn</a>, +Previous:<a rel="previous" href="#fingertrouble">finger +trouble</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>finger-pointing syndrome</b> n.</p> + +<p>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.</p> + +<hr> +Node:<a name="finn">finn</a>, Next:<a rel="next" href="#firebottle">firebottle</a>, Previous:<a rel="previous" href="#finger-pointingsyndrome">finger-pointing syndrome</a>, Up:<a +rel="up" href="#chap06">= F =</a> <br> + + +<p><b>finn</b> v.</p> + +<p>[IRC] To pull rank on somebody based on the amount of time one +has spent on <b><a href="#IRC">IRC</a></b>. 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!"</p> + +<hr> +Node:<a name="firebottle">firebottle</a>, Next:<a rel="next" +href="#firefighting">firefighting</a>, Previous:<a rel="previous" +href="#finn">finn</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>firebottle</b> n.obs.</p> + +<p>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 <b><a href="#glassfet">glassfet</a></b>.</p> + +<hr> +Node:<a name="firefighting">firefighting</a>, Next:<a rel="next" +href="#firehosesyndrome">firehose syndrome</a>, Previous:<a +rel="previous" href="#firebottle">firebottle</a>, Up:<a rel="up" +href="#chap06">= F =</a> <br> + + +<p><b>firefighting</b> n.</p> + +<p>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 <b><a href="#gangbang">gang +bang</a></b>, <b><a href="#MongolianHordestechnique">Mongolian Hordes +technique</a></b>; however, the term `firefighting' connotes that +the effort is going into chasing bugs rather than adding +features.</p> + +<hr> +Node:<a name="firehosesyndrome">firehose syndrome</a>, Next:<a +rel="next" href="#firewallcode">firewall code</a>, Previous:<a +rel="previous" href="#firefighting">firefighting</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>firehose syndrome</b> n.</p> + +<p>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 <b><a href="#overrun">overrun</a></b>, <b><a href="#bufferoverflow">buffer overflow</a></b>.</p> + +<hr> +Node:<a name="firewallcode">firewall code</a>, Next:<a rel="next" href="#firewallmachine">firewall machine</a>, +Previous:<a rel="previous" href="#firehosesyndrome">firehose +syndrome</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>firewall code</b> n.</p> + +<p>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 <b><a href="#cannothappen">can't happen</a></b> 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.</p> + +<hr> +Node:<a name="firewallmachine">firewall machine</a>, Next:<a +rel="next" href="#fireworksmode">fireworks mode</a>, +Previous:<a rel="previous" href="#firewallcode">firewall +code</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>firewall machine</b> n.</p> + +<p>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 <b><a href="#cracker">cracker</a></b>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 <b><a href="#ironbox">iron box</a></b> +keyable to particular incoming IDs or activity patterns. Syn. +<b><a href="#flytrap">flytrap</a></b>, <b><a href="#Venusflytrap">Venus flytrap</a></b>.</p> + +<p>[When first coined in the mid-1980s this term was pure jargon. +Now (1999) it is techspeak, and has been retained only as an +example of uptake --ESR]</p> + +<hr> +Node:<a name="fireworksmode">fireworks mode</a>, Next:<a rel="next" href="#firmware">firmware</a>, Previous:<a rel="previous" +href="#firewallmachine">firewall machine</a>, Up:<a rel="up" +href="#chap06">= F =</a> <br> + + +<p><b>fireworks mode</b> n.</p> + +<p>1. The mode a machine is sometimes said to be in when it is +performing a <b><a href="#crashandburn">crash and +burn</a></b> operation. 2. There is (or was) a more specific +meaning of this term in the Amiga community. The word fireworks +described the effects of a particularly serious crash which +prevented the video pointer(s) from getting reset at the start of +the vertical blank. This caused the DAC to scroll through the +entire contents of CHIP (video or video+CPU) memory. Since each +bit plane would scroll separately this was quite a spectacular +effect.</p> + +<hr> +Node:<a name="firmware">firmware</a>, Next:<a rel="next" href="#firmy">firmy</a>, Previous:<a rel="previous" href="#fireworksmode">fireworks mode</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>firmware</b> /ferm'weir/ n.</p> + +<p>Embedded software contained in EPROM or flash memory. It isn't +quite hardware, but at least doesn't have to be loaded from a +disk like regular software. Hacker usage differs from straight +techspeak in that hackers don't normally apply it to stuff that +you can't possibly get at, such as the program that runs a pocket +calculator. Instead, it implies that the firmware could be +changed, even if doing so would mean opening a box and plugging +in a new chip. A computer's BIOS is the classic example, although +nowadays there is firmware in disk controllers, modems, video +cards and even CD-ROM drives.</p> + +<hr> +Node:<a name="firmy">firmy</a>, Next:<a rel="next" href="#fish">fish</a>, Previous:<a rel="previous" href="#firmware">firmware</a>, Up:<a rel="up" href="#chap06">= +F =</a> <br> + + +<p><b>firmy</b> /fer'mee/ n.</p> + +<p>Syn. <b><a href="#stiffy">stiffy</a></b> (a 3.5-inch floppy +disk).</p> + +<hr> +Node:<a name="fish">fish</a>, Next:<a rel="next" href="#FISHqueue">FISH queue</a>, Previous:<a rel="previous" href="#firmy">firmy</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>fish</b> n.</p> + +<p>[Adelaide University, Australia] 1. Another <b><a href="#metasyntacticvariable">metasyntactic variable</a></b>. See +<b><a href="#foo">foo</a></b>. 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'.</p> + +<hr> +Node:<a name="FISHqueue">FISH queue</a>, Next:<a rel="next" +href="#FITNR">FITNR</a>, Previous:<a rel="previous" href="#fish">fish</a>, Up:<a rel="up" href="#chap06">= F =</a> +<br> + + +<p><b>FISH queue</b> n.</p> + +<p>[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.</p> + +<hr> +Node:<a name="FITNR">FITNR</a>, Next:<a rel="next" href="#fix">fix</a>, Previous:<a rel="previous" href="#FISHqueue">FISH queue</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>FITNR</b> // adj.</p> + +<p>[Thinking Machines, Inc.] Fixed In The Next Release. A +written-only notation attached to bug reports. Often wishful +thinking.</p> + +<hr> +Node:<a name="fix">fix</a>, Next:<a rel="next" href="#FIXME">FIXME</a>, Previous:<a rel="previous" href="#FITNR">FITNR</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>fix</b> n.,v.</p> + +<p>What one does when a problem has been reported too many times +to be ignored.</p> + +<hr> +Node:<a name="FIXME">FIXME</a>, Next:<a rel="next" href="#flag">flag</a>, Previous:<a rel="previous" href="#fix">fix</a>, +Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>FIXME</b> imp.</p> + +<p>[common] A standard tag often put in C comments near a piece +of code that needs work. The point of doing so is that a +<code>grep</code> or a similar pattern-matching tool can find all +such places quickly.</p> + +<pre> +/* FIXME: note this is common in <b><a href="#GNU">GNU</a></b> code. */ +</pre> + +<p>Compare <b><a href="#XXX">XXX</a></b>.</p> + +<hr> +Node:<a name="flag">flag</a>, Next:<a rel="next" href="#flagday">flag day</a>, Previous:<a rel="previous" href="#FIXME">FIXME</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>flag</b> n.</p> + +<p>[very common] 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 <b><a href="#bit">bit</a></b>. See also <b><a href="#hiddenflag">hidden +flag</a></b>, <b><a href="#modebit">mode bit</a></b>.</p> + +<hr> +Node:<a name="flagday">flag day</a>, Next:<a rel="next" href="#flaky">flaky</a>, Previous:<a rel="previous" href="#flag">flag</a>, Up:<a rel="up" href="#chap06">= F =</a> +<br> + + +<p><b>flag day</b> n.</p> + +<p>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 +<b><a href="#flag">flag</a></b> to mean a variable that has two +values. It came into use when a massive change was made to the +<b><a href="#Multics">Multics</a></b> timesharing system to +convert from the short-lived 1965 version of the ASCII code to +the 1967 version (in draft at the time); this was scheduled for +Flag Day (a U.S. holiday), June 14, 1966. The actual change moved +the code point for the ASCII newline character; this required +that all of the Multics source code, documentation, and device +drivers be changed simultaneously. See also <b><a href="#backwardcombatability">backward combatability</a></b>.</p> + +<hr> +Node:<a name="flaky">flaky</a>, Next:<a rel="next" href="#flamage">flamage</a>, Previous:<a rel="previous" href="#flagday">flag day</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>flaky</b> adj.</p> + +<p>(var sp. `flakey') Subject to frequent <b><a href="#lossage">lossage</a></b>. 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 <b><a href="#dodgy">dodgy</a></b> or <b><a href="#wonky">wonky</a></b>.</p> + +<hr> +Node:<a name="flamage">flamage</a>, Next:<a rel="next" href="#flame">flame</a>, Previous:<a rel="previous" href="#flaky">flaky</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>flamage</b> /flay'm*j/ n.</p> + +<p>[very common] Flaming verbiage, esp. high-noise, low-signal +postings to <b><a href="#Usenet">Usenet</a></b> or other +electronic <b><a href="#fora">fora</a></b>. Often in the phrase +`the usual flamage'. `Flaming' is the act itself; `flamage' the +content; a `flame' is a single flaming message. See <b><a href="#flame">flame</a></b>, also <b><a href="#dahmum">dahmum</a></b>.</p> + +<hr> +Node:<a name="flame">flame</a>, Next:<a rel="next" href="#flamebait">flame bait</a>, Previous:<a rel="previous" href="#flamage">flamage</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>flame</b></p> + +<p>[at MIT, orig. from the phrase `flaming asshole'] 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).</p> + +<p>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, and +from the University of Virginia in the early 1960s.</p> + +<p>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.</p> + +<hr> +Node:<a name="flamebait">flame bait</a>, Next:<a rel="next" +href="#flameon">flame on</a>, Previous:<a rel="previous" href="#flame">flame</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>flame bait</b> n.</p> + +<p>[common] A posting intended to trigger a <b><a href="#flamewarr">flame war</a></b>, or one that invites flames in +reply. See also <b><a href="#troll">troll</a></b>.</p> + +<hr> +Node:<a name="flameon">flame on</a>, Next:<a rel="next" href="#flamewarr">flame war</a>, Previous:<a rel="previous" href="#flamebait">flame bait</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>flame on</b> vi.,interj.</p> + +<p>1. To begin to <b><a href="#flame">flame</a></b>. The punning +reference to Marvel Comics's Human Torch is no longer widely +recognized. 2. To continue to flame. See <b><a href="#rave">rave</a></b>, <b><a href="#burble">burble</a></b>.</p> + +<hr> +Node:<a name="flamewarr">flame war</a>, Next:<a rel="next" +href="#flamer">flamer</a>, Previous:<a rel="previous" href="#flameon">flame on</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>flame war</b> n.</p> + +<p>[common] (var. `flamewar') An acrimonious dispute, especially +when conducted on a public electronic forum such as <b><a href="#Usenet">Usenet</a></b>.</p> + +<hr> +Node:<a name="flamer">flamer</a>, Next:<a rel="next" href="#flap">flap</a>, Previous:<a rel="previous" href="#flamewarr">flame war</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>flamer</b> n.</p> + +<p>[common] One who habitually <b><a href="#flame">flame</a></b>s. Said esp. of obnoxious <b><a href="#Usenet">Usenet</a></b> personalities.</p> + +<hr> +Node:<a name="flap">flap</a>, Next:<a rel="next" href="#flarp">flarp</a>, Previous:<a rel="previous" href="#flamer">flamer</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>flap</b> vt.</p> + +<p>1. [obs.] To unload a DECtape (so it goes flap, flap, +flap<small>...</small>). Old-time hackers at MIT tell of the days +when the disk was device 0 and DEC microtapes were 1, +2,<small>...</small> 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 <b><a href="#macrotape">macrotape</a></b>. 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.)</p> + +<hr> +Node:<a name="flarp">flarp</a>, Next:<a rel="next" href="#flashcrowd">flash crowd</a>, Previous:<a rel="previous" +href="#flap">flap</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>flarp</b> /flarp/ n.</p> + +<p>[Rutgers University] Yet another <b><a href="#metasyntacticvariable">metasyntactic variable</a></b> (see +<b><a href="#foo">foo</a></b>). 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 <i>do</i> contain the +magic word.</p> + +<hr> +Node:<a name="flashcrowd">flash crowd</a>, Next:<a rel="next" +href="#flat">flat</a>, Previous:<a rel="previous" href="#flarp">flarp</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>flash crowd</b></p> + +<p>Larry Niven's 1973 SF short story "Flash Crowd" predicted that +one consequence of cheap teleportation would be huge crowds +materializing almost instantly at the sites of interesting news +stories. Twenty years later the term passed into common use on +the Internet to describe exponential spikes in website or server +usage when one passes a certain threshold of popular interest +(this may also be called <b><a href="#slashdoteffect">slashdot +effect</a></b>).</p> + +<hr> +Node:<a name="flat">flat</a>, Next:<a rel="next" href="#flat-ASCII">flat-ASCII</a>, Previous:<a rel="previous" href="#flashcrowd">flash crowd</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>flat</b> adj.</p> + +<p>1. [common] Lacking any complex internal structure. "That +<b><a href="#bittybox">bitty box</a></b> has only a flat +filesystem, not a hierarchical one." The verb form is <b><a href="#flatten">flatten</a></b>. 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 <b><a href="#cretinous">cretinous</a></b>).</p> + +<p>Note that sense 1 (at least with respect to filesystems) is +usually used pejoratively, while sense 2 is a <b><a href="#GoodThing">Good Thing</a></b>.</p> + +<hr> +Node:<a name="flat-ASCII">flat-ASCII</a>, Next:<a rel="next" +href="#flat-file">flat-file</a>, Previous:<a rel="previous" href="#flat">flat</a>, Up:<a rel="up" href="#chap06">= F =</a> +<br> + + +<p><b>flat-ASCII</b> adj.</p> + +<p>[common] 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 <b><a href="#meta">meta</a></b>-characters). Syn. <b><a href="#plain-ASCII">plain-ASCII</a></b>. Compare <b><a href="#flat-file">flat-file</a></b>.</p> + +<hr> +Node:<a name="flat-file">flat-file</a>, Next:<a rel="next" href="#flatten">flatten</a>, Previous:<a rel="previous" href="#flat-ASCII">flat-ASCII</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>flat-file</b> adj.</p> + +<p>A <b><a href="#flatten">flatten</a></b>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 +<b><a href="#flat-ASCII">flat-ASCII</a></b> form. See also <b><a +href="#sharchive">sharchive</a></b>.</p> + +<hr> +Node:<a name="flatten">flatten</a>, Next:<a rel="next" href="#flavor">flavor</a>, Previous:<a rel="previous" href="#flat-file">flat-file</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>flatten</b> vt.</p> + +<p>[common] 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 <b><a href="#flat-ASCII">flat-ASCII</a></b>. "This code flattens an +expression with parentheses into an equivalent <b><a href="#canonical">canonical</a></b> form."</p> + +<hr> +Node:<a name="flavor">flavor</a>, Next:<a rel="next" href="#flavorful">flavorful</a>, Previous:<a rel="previous" href="#flatten">flatten</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>flavor</b> n.</p> + +<p>1. [common] Variety, type, kind. "DDT commands come in two +flavors." "These lights come in two flavors, big red ones and +small green ones." "Linux is a flavor of Unix" See <b><a href="#vanilla">vanilla</a></b>. 2. The attribute that causes +something to be <b><a href="#flavorful">flavorful</a></b>. +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 <b><a href="#vanilla">vanilla</a></b>. 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.</p> + +<hr> +Node:<a name="flavorful">flavorful</a>, Next:<a rel="next" href="#flippy">flippy</a>, Previous:<a rel="previous" href="#flavor">flavor</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>flavorful</b> adj.</p> + +<p>Full of <b><a href="#flavor">flavor</a></b> (sense 2); +esthetically pleasing. See <b><a href="#random">random</a></b> +and <b><a href="#losing">losing</a></b> for antonyms. See also +the entries for <b><a href="#taste">taste</a></b> and <b><a href="#elegant">elegant</a></b>.</p> + +<hr> +Node:<a name="flippy">flippy</a>, Next:<a rel="next" href="#flood">flood</a>, Previous:<a rel="previous" href="#flavorful">flavorful</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>flippy</b> /flip'ee/ n.</p> + +<p>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.</p> + +<hr> +Node:<a name="flood">flood</a>, Next:<a rel="next" href="#flowchart">flowchart</a>, Previous:<a rel="previous" href="#flippy">flippy</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>flood</b> v.</p> + +<p>[common] 1. To overwhelm a network channel with +mechanically-generated traffic; especially used of IP, TCP/IP, +UDP, or ICMP denial-of-service attacks. 2. To dump large amounts +of text onto an <b><a href="#IRC">IRC</a></b> channel. This is +especially rude when the text is uninteresting and the other +users are trying to carry on a serious conversation. Also used in +a similar sense on Usenet. 3. [Usenet] To post an unusually large +number or volume of files on a related topic.</p> + +<hr> +Node:<a name="flowchart">flowchart</a>, Next:<a rel="next" href="#flowerkey">flower key</a>, Previous:<a rel="previous" href="#flood">flood</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>flowchart</b> n.</p> + +<p>[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 <b><a href="#COBOL">COBOL</a></b> +programmers, <b><a href="#cardwalloper">card +walloper</a></b>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 <b><a +href="#PDL">PDL</a></b>, sense 1.</p> + +<hr> +Node:<a name="flowerkey">flower key</a>, Next:<a rel="next" +href="#flush">flush</a>, Previous:<a rel="previous" href="#flowchart">flowchart</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>flower key</b> n.</p> + +<p>[Mac users] See <b><a href="#featurekey">feature +key</a></b>.</p> + +<hr> +Node:<a name="flush">flush</a>, Next:<a rel="next" href="#flypage">flypage</a>, Previous:<a rel="previous" href="#flowerkey">flower key</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>flush</b> v.</p> + +<p>1. [common] 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 +<code>fflush(3)</code> call. This is <i>not</i> 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.</p> + +<p>`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 <code>fflush(3)</code> call in C's +standard I/O library (though it is reported to have been in use +among BLISS programmers at <b><a href="#DEC">DEC</a></b> and on +Honeywell and IBM machines as far back as 1965). Unix/C hackers +found the ITS usage confusing, and vice versa.</p> + +<hr> +Node:<a name="flypage">flypage</a>, Next:<a rel="next" href="#Flyspeck3">Flyspeck 3</a>, Previous:<a rel="previous" href="#flush">flush</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>flypage</b> /fli:'payj/ n.</p> + +<p>(alt. `fly page') A <b><a href="#banner">banner</a></b>, sense +1.</p> + +<hr> +Node:<a name="Flyspeck3">Flyspeck 3</a>, Next:<a rel="next" +href="#flytrap">flytrap</a>, Previous:<a rel="previous" href="#flypage">flypage</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>Flyspeck 3</b> n.</p> + +<p>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.</p> + +<hr> +Node:<a name="flytrap">flytrap</a>, Next:<a rel="next" href="#FM">FM</a>, Previous:<a rel="previous" href="#Flyspeck3">Flyspeck 3</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>flytrap</b> n.</p> + +<p>[rare] See <b><a href="#firewallmachine">firewall +machine</a></b>.</p> + +<hr> +Node:<a name="FM">FM</a>, Next:<a rel="next" href="#fnord">fnord</a>, Previous:<a rel="previous" href="#flytrap">flytrap</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>FM</b> /F-M/ n.</p> + +<p>1. [common] <i>Not</i> `Frequency Modulation' but rather an +abbreviation for `Fucking Manual', the back-formation from <b><a +href="#RTFM">RTFM</a></b>. Used to refer to the manual itself in +the <b><a href="#RTFM">RTFM</a></b>. "Have you seen the +Networking FM lately?" 2. Abbreviation for "Fucking Magic", used +in the sense of <b><a href="#blackmagic">black +magic</a></b>.</p> + +<hr> +Node:<a name="fnord">fnord</a>, Next:<a rel="next" href="#FOAF">FOAF</a>, Previous:<a rel="previous" href="#FM">FM</a>, +Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>fnord</b> n.</p> + +<p>[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 <b><a href="#Discordianism">Discordianism</a></b> 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 <b><a href="#metasyntacticvariable">metasyntactic variable</a></b>, +commonly used by hackers with ties to <b><a href="#Discordianism">Discordianism</a></b> or the <b><a href="#ChurchoftheSubGenius">Church of the +SubGenius</a></b>.</p> + +<hr> +Node:<a name="FOAF">FOAF</a>, Next:<a rel="next" href="#FOD">FOD</a>, Previous:<a rel="previous" href="#fnord">fnord</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>FOAF</b> // n.</p> + +<p>[Usenet; common] 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.</p> + +<hr> +Node:<a name="FOD">FOD</a>, Next:<a rel="next" href="#foldcase">fold case</a>, Previous:<a rel="previous" href="#FOAF">FOAF</a>, Up:<a rel="up" href="#chap06">= F =</a> +<br> + + +<p><b>FOD</b> /fod/ v.</p> + +<p>[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 <b><a href="#MUD">MUD</a></b>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 <b><a href="#gun">gun</a></b>.</p> + +<p>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.</p> + +<hr> +Node:<a name="foldcase">fold case</a>, Next:<a rel="next" +href="#followup">followup</a>, Previous:<a rel="previous" href="#FOD">FOD</a>, Up:<a rel="up" href="#chap06">= F =</a> +<br> + + +<p><b>fold case</b> v.</p> + +<p>See <b><a href="#smashcase">smash case</a></b>. 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.</p> + +<hr> +Node:<a name="followup">followup</a>, Next:<a rel="next" href="#fontology">fontology</a>, Previous:<a rel="previous" href="#foldcase">fold case</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>followup</b> n.</p> + +<p>[common] On Usenet, a <b><a href="#posting">posting</a></b> +generated in response to another posting (as opposed to a <b><a +href="#reply">reply</a></b>, which goes by email rather than +being broadcast). Followups include the ID of the <b><a href="#parentmessage">parent message</a></b> in their headers; +smart news-readers can use this information to present Usenet +news in `conversation' sequence rather than order-of-arrival. See +<b><a href="#thread">thread</a></b>.</p> + +<hr> +Node:<a name="fontology">fontology</a>, Next:<a rel="next" href="#foo">foo</a>, Previous:<a rel="previous" href="#followup">followup</a>, Up:<a rel="up" href="#chap06">= +F =</a> <br> + + +<p><b>fontology</b> n.</p> + +<p>[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.</p> + +<p>[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]</p> + +<hr> +Node:<a name="foo">foo</a>, Next:<a rel="next" href="#foobar">foobar</a>, Previous:<a rel="previous" href="#fontology">fontology</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>foo</b> /foo/</p> + +<p>1. interj. Term of disgust. 2. [very common] Used very +generally as a sample name for absolutely anything, esp. programs +and files (esp. scratch files). 3. First on the standard list of +<b><a href="#metasyntacticvariable">metasyntactic +variable</a></b>s used in syntax examples. See also <b><a href="#bar">bar</a></b>, <b><a href="#baz">baz</a></b>, <b><a href="#qux">qux</a></b>, <b><a href="#quux">quux</a></b>, <b><a href="#corge">corge</a></b>, <b><a href="#grault">grault</a></b>, +<b><a href="#garply">garply</a></b>, <b><a href="#waldo">waldo</a></b>, <b><a href="#fred">fred</a></b>, <b><a +href="#plugh">plugh</a></b>, <b><a href="#xyzzy">xyzzy</a></b>, +<b><a href="#thud">thud</a></b>.</p> + +<p>When `foo' is used in connection with `bar' it has generally +traced to the WWII-era Army slang acronym <b><a href="#FUBAR">FUBAR</a></b> (`Fucked Up Beyond All Repair'), later +modified to <b><a href="#foobar">foobar</a></b>. Early versions +of the Jargon File interpreted this change as a post-war +bowdlerization, but it it now seems more likely that FUBAR was +itself a derivative of `foo' perhaps influenced by German +`furchtbar' (terrible) - `foobar' may actually have been the +<i>original</i> form.</p> + +<p>For, it seems, the word `foo' itself had an immediate prewar +history in comic strips and cartoons. The earliest documented +uses were in the "Smokey Stover" comic strip popular in the +1930s, which frequently included the word "foo". Bill Holman, the +author of the strip, filled it with odd jokes and personal +contrivances, including other nonsense phrases such as "Notary +Sojac" and "1506 nix nix". According to the Warner Brothers Cartoon +Companion Holman claimed to have found the word "foo" on the +bottom of a Chinese figurine. This is plausible; Chinese +statuettes often have apotropaic inscriptions, and this may have +been 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"). English speakers' reception of +Holman's `foo' nonsense word was undoubtedly influenced by +Yiddish `feh' and English `fooey' and `fool'.</p> + +<p>Holman's strip featured a firetruck called the Foomobile that +rode on two wheels. The comic strip was tremendously popular in +the late 1930s, and legend has it that a manufacturer in Indiana +even produced an operable version of Holman's Foomobile. +According to the Encyclopedia of American Comics, `Foo' fever +swept the U.S., finding its way into popular songs and generating +over 500 `Foo Clubs.' The fad left `foo' references embedded in +popular culture (including a couple of appearances in Warner +Brothers cartoons of 1938-39) but with their origins rapidly +forgotten.</p> + +<p>One place they are known to have remained live is in the U.S. +military during the WWII years. In 1944-45, the term `foo +fighters' was in use by radar operators 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). Informants +connected the term to the Smokey Stover strip.</p> + +<p>The U.S. and British militaries frequently swapped slang terms +during the war (see <b><a href="#kluge">kluge</a></b> and <b><a +href="#kludge">kludge</a></b> for another important example) +Period sources reported that `FOO' became 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, but this (like the contemporaneous "FUBAR") was probably +a <b><a href="#backronym">backronym</a></b> . Forty years later, +Paul Dickson's excellent book "Words" (Dell, 1982, ISBN +0-440-52260-7) traced "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."</p> + +<p>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. The Crumbs may also have been influenced by a +short-lived Canadian parody magazine named `Foo' published in +1951-52.</p> + +<p>An old-time member reports that in the 1959 "Dictionary of the +TMRC Language", compiled at <b><a href="#TMRC">TMRC</a></b>, +there was an entry that went something like this:</p> + +<blockquote>FOO: The first syllable of the sacred chant phrase +"FOO MANE PADME HUM." Our first obligation is to keep the foo +counters turning.</blockquote> + +<p>(For more about the legendary foo counters, see <b><a href="#TMRC">TMRC</a></b>.) This definition used Bill Holman's +nonsense word, only then two decades old and demonstrably still +live in popular culture and slang, to a <b><a href="#hahaonlyserious">ha ha only serious</a></b> analogy +with esoteric Tibetan Buddhism. Today's hackers would find it +difficult to resist elaborating a joke like that, and it is not +likely 1959's were any less susceptible. Almost the entire staff +of what later became the MIT AI Lab was involved with TMRC, and +the word spread from there.</p> + +<hr> +Node:<a name="foobar">foobar</a>, Next:<a rel="next" href="#fool">fool</a>, Previous:<a rel="previous" href="#foo">foo</a>, +Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>foobar</b> n.</p> + +<p>[very common] Another widely used <b><a href="#metasyntacticvariable">metasyntactic variable</a></b>; see +<b><a href="#foo">foo</a></b> for etymology. Probably originally +propagated through DECsystem manuals by Digital Equipment +Corporation (<b><a href="#DEC">DEC</a></b>) in 1960s and early +1970s; confirmed sightings there go back to 1972. Hackers do +<i>not</i> generally use this to mean <b><a href="#FUBAR">FUBAR</a></b> in either the slang or jargon sense. See +also <b><a href="#FredFoobar">Fred Foobar</a></b>. In RFC1639, +"FOOBAR" was made an abbreviation for "FTP Operation Over Big +Address Records", but this was an obvious <b><a href="#backronym">backronym</a></b>.</p> + +<hr> +Node:<a name="fool">fool</a>, Next:<a rel="next" href="#foolfile">fool file</a>, Previous:<a rel="previous" href="#foobar">foobar</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>fool</b> n.</p> + +<p>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 <b><a +href="#cretin">cretin</a></b>, <b><a href="#loser">loser</a></b>, +<b><a href="#foolfile">fool file</a></b>.</p> + +<p>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 <b><a href="#DEADBEEF">DEADBEEF</a></b>.</p> + +<hr> +Node:<a name="foolfile">fool file</a>, Next:<a rel="next" +href="#Foonly">Foonly</a>, Previous:<a rel="previous" href="#fool">fool</a>, Up:<a rel="up" href="#chap06">= F =</a> +<br> + + +<p><b>fool file</b> n.</p> + +<p>[Usenet] A notional repository of all the most dramatically +and abysmally stupid utterances ever. An entire subgenre of <b><a +href="#sigblock">sig block</a></b>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.</p> + +<hr> +Node:<a name="Foonly">Foonly</a>, Next:<a rel="next" href="#footprint">footprint</a>, Previous:<a rel="previous" href="#foolfile">fool file</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>Foonly</b> n.</p> + +<p>1. The <b><a href="#PDP-10">PDP-10</a></b> 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 name itself came from FOO NLI, an error message +emitted by a PDP-10 assembler at SAIL meaning "FOO is Not a Legal +Identifier". The intention was to leapfrog from the old <b><a +href="#DEC">DEC</a></b> 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 <b><a href="#TOPS-20">TOPS-20</a></b> 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 +<b><a href="#Mars">Mars</a></b>, and the company never quite +recovered. See the <b><a href="#Mars">Mars</a></b> entry for the +continuation and moral of this story.</p> + +<hr> +Node:<a name="footprint">footprint</a>, Next:<a rel="next" href="#forfree">for free</a>, Previous:<a rel="previous" href="#Foonly">Foonly</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>footprint</b> n.</p> + +<p>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 <b><a href="#toeprint">toeprint</a></b>. 3. <dfn>RAM footprint</dfn>: The +minimum amount of RAM which an OS or other program takes; this +figure gives 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]</p> + +<hr> +Node:<a name="forfree">for free</a>, Next:<a rel="next" href="#fortherestofus">for the rest of us</a>, Previous:<a +rel="previous" href="#footprint">footprint</a>, Up:<a rel="up" +href="#chap06">= F =</a> <br> + + +<p><b>for free</b> adj.</p> + +<p>[common] Said of a capability of a programming language or +hardware that is available by its design without needing +cleverness to implement: "In APL, we get the matrix operations +for free." "And owing to the way revisions are stored in this +system, you get revision trees for free." The term usually refers +to a serendipitous feature of doing things a certain way (compare +<b><a href="#bigwin">big win</a></b>), but it may refer to an +intentional but secondary feature.</p> + +<hr> +Node:<a name="fortherestofus">for the rest of us</a>, +Next:<a rel="next" href="#forvaluesof">for values of</a>, +Previous:<a rel="previous" href="#forfree">for free</a>, Up:<a +rel="up" href="#chap06">= F =</a> <br> + + +<p><b>for the rest of us</b> adj.</p> + +<p>[from the Mac slogan "The computer for the rest of us"] 1. +Used to describe a <b><a href="#spiffy">spiffy</a></b> product +whose affordability shames other comparable products, or (more +often) used sarcastically to describe <b><a href="#spiffy">spiffy</a></b> but very overpriced products. 2. +Describes a program with a limited interface, deliberately +limited capabilities, non-orthogonality, inability to compose +primitives, or any other limitation designed to not `confuse' a +naive user. This places an upper bound on how far that user can +go before the program begins to get in the way of the task +instead of helping accomplish it. Used in reference to Macintosh +software which doesn't provide obvious capabilities because it is +thought that the poor lusers might not be able to handle them. +Becomes `the rest of <i>them</i>' when used in third-party +reference; thus, "Yes, it is an attractive program, but it's +designed for The Rest Of Them" means a program that superficially +looks neat but has no depth beyond the surface flash. See also +<b><a href="#WIMPenvironment">WIMP environment</a></b>, <b><a +href="#Macintrash">Macintrash</a></b>, <b><a href="#pointanddroolinterface">point-and-drool interface</a></b>, +<b><a href="#user-friendly">user-friendly</a></b>.</p> + +<hr> +Node:<a name="forvaluesof">for values of</a>, Next:<a rel="next" href="#fora">fora</a>, Previous:<a rel="previous" href="#fortherestofus">for the rest of us</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>for values of</b></p> + +<p>[MIT] A common rhetorical maneuver at MIT is to use any of the +canonical <b><a href="#randomnumbers">random numbers</a></b> +as placeholders for variables. "The max function takes 42 +arguments, for arbitrary values of 42." "There are 69 ways to +leave your lover, for 69 = 50." This is especially likely when +the speaker has uttered a random number and realizes that it was +not recognized as such, but even `non-random' numbers are +occasionally used in this fashion. A related joke is that pi +equals 3 -- for small values of pi and large values of 3.</p> + +<p>Historical note: at MIT this usage has traditionally been +traced to the programming language MAD (Michigan Algorithm +Decoder), an Algol-58-like language that was the most common +choice among mainstream (non-hacker) users at MIT in the mid-60s. +It inherited from Algol-58 a control structure FOR VALUES OF X = +3, 7, 99 DO ... that would repeat the indicated instructions for +each value in the list (unlike the usual FOR that only works for +arithmetic sequences of values). MAD is long extinct, but similar +for-constructs still flourish (e.g., in Unix's shell +languages).</p> + +<hr> +Node:<a name="fora">fora</a>, Next:<a rel="next" href="#foreground">foreground</a>, Previous:<a rel="previous" href="#forvaluesof">for values of</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>fora</b> pl.n.</p> + +<p>Plural of <b><a href="#forum">forum</a></b>.</p> + +<hr> +Node:<a name="foreground">foreground</a>, Next:<a rel="next" +href="#fork">fork</a>, Previous:<a rel="previous" href="#fora">fora</a>, Up:<a rel="up" href="#chap06">= F =</a> +<br> + + +<p><b>foreground</b> vt.</p> + +<p>[Unix; common] To bring a task to the top of one's <b><a href="#stack">stack</a></b> for immediate processing, and hackers +often use it in this sense for non-computer tasks. "If your +presentation is due next week, I guess I'd better foreground +writing up the design document."</p> + +<p>Technically, on a time-sharing system, a task executing in +foreground is one able to accept input from and return output to +the user; oppose <b><a href="#background">background</a></b>. +Nowadays this term is primarily associated with <b><a href="#Unix">Unix</a></b>, but it appears first to have been used in +this sense on OS/360. Normally, there is only one foreground task +per terminal (or terminal window); having multiple processes +simultaneously reading the keyboard is a good way to <b><a href="#lose">lose</a></b>.</p> + +<hr> +Node:<a name="fork">fork</a>, Next:<a rel="next" href="#forkbomb">fork bomb</a>, Previous:<a rel="previous" href="#foreground">foreground</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>fork</b></p> + +<p>In the open-source community, a fork is what occurs when two +(or more) versions of a software package's source code are being +developed in parallel which once shared a common code base, and +these multiple versions of the source code have irreconcilable +differences between them. This should not be confused with a +development branch, which may later be folded back into the +original source code base. Nor should it be confused with what +happens when a new distribution of Linux or some other +distribution is created, because that largely assembles pieces +than can and will be used in other distributions without +conflict.</p> + +<p> +Forking is uncommon; in fact, it is so uncommon that individual instances loom +large in hacker folklore. Notable in this class were the GCC/EGCS fork (later +healed by a merger) and the forks among the FreeBSD, NetBSD, and OpenBSD +operating systems. +</p> + +<hr> +Node:<a name="forkbomb">fork bomb</a>, Next:<a rel="next" +href="#forked">forked</a>, Previous:<a rel="previous" href="#fork">fork</a>, Up:<a rel="up" href="#chap06">= F =</a> +<br> + + +<p><b>fork bomb</b> n.</p> + +<p>[Unix] A particular species of <b><a href="#wabbit">wabbit</a></b> that can be written in one line of C +(<code>main() {for(;;)fork();}</code>) or shell (<code>$0 & +$0 &</code>) on any Unix system, or occasionally created by +an egregious coding bug. A fork bomb process `explodes' by +recursively spawning copies of itself (using the Unix system call +<code>fork(2)</code>). Eventually it eats all the process table +entries and effectively wedges the system. Fortunately, fork +bombs are relatively easy to spot and kill, so creating one +deliberately seldom accomplishes more than to bring the just +wrath of the gods down upon the perpetrator. See also <b><a href="#logicbomb">logic bomb</a></b>.</p> + +<hr> +Node:<a name="forked">forked</a>, Next:<a rel="next" href="#Fortrash">Fortrash</a>, Previous:<a rel="previous" href="#forkbomb">fork bomb</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>forked</b> adj.,vi.</p> + +<p>1. [common after 1997, esp. in the Linux community] An +open-source software project is said to have forked or be forked +when the project group fissions into two or more parts pursuing +separate lines of development (or, less commonly, when a third +party unconnected to the project group ). Forking is considered a +<b><a href="#BadThing">Bad Thing</a></b> - not merely because +it implies a lot of wasted effort in the future, but because +forks tend to be accompanied by a great deal of strife and +acrimony between the successor groups over issues of legitimacy, +succession, and design direction. There is serious social +pressure against forking. As a result, major forks (such as the +Gnu-Emacs/XEmacs split, the fissionings of the 386BSD group into +three daughter project, and the short-lived GCC/EGCS split) are +rare enough that they are remembered individually in hacker +folklore. 2. [Unix; uncommon; prob. influenced by a mainstream +expletive] Terminally slow, or dead. Originated when one system +was slowed to a snail's pace by an inadvertent <b><a href="#forkbomb">fork bomb</a></b>.</p> + +<hr> +Node:<a name="Fortrash">Fortrash</a>, Next:<a rel="next" href="#fortunecookie">fortune cookie</a>, Previous:<a rel="previous" href="#forked">forked</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>Fortrash</b> /for'trash/ n.</p> + +<p>Hackerism for the FORTRAN (FORmula TRANslator) language, +referring to its primitive design, gross and irregular syntax, +limited control constructs, and slippery, exception-filled +semantics.</p> + +<hr> +Node:<a name="fortunecookie">fortune cookie</a>, Next:<a rel="next" href="#forum">forum</a>, Previous:<a rel="previous" href="#Fortrash">Fortrash</a>, Up:<a rel="up" href="#chap06">= +F =</a> <br> + + +<p><b>fortune cookie</b> n.</p> + +<p>[WAITS, via Unix; common] A random quote, item of trivia, +joke, or maxim printed to the user's tty at login time or (less +commonly) at logout time. Items from this lexicon have often been +used as fortune cookies. See <b><a href="#cookiefile">cookie +file</a></b>.</p> + +<hr> +Node:<a name="forum">forum</a>, Next:<a rel="next" href="#fossil">fossil</a>, Previous:<a rel="previous" href="#fortunecookie">fortune cookie</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>forum</b> n.</p> + +<p>[Usenet, GEnie, CI$; pl. `fora' or `forums'] Any discussion +group accessible through a dial-in <b><a href="#BBS">BBS</a></b>, +a <b><a href="#mailinglist">mailing list</a></b>, or a <b><a +href="#newsgroup">newsgroup</a></b> (see <b><a href="#thenetwork">the network</a></b>). A forum functions much +like a bulletin board; users submit <b><a href="#posting">posting</a></b>s for all to read and discussion +ensues. Contrast real-time chat via <b><a href="#talkmode">talk mode</a></b> or point-to-point personal <b><a +href="#email">email</a></b>.</p> + +<hr> +Node:<a name="fossil">fossil</a>, Next:<a rel="next" href="#fourcolorglossies">four-color glossies</a>, Previous:<a +rel="previous" href="#forum">forum</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>fossil</b> n.</p> + +<p>1. In software, a misfeature that becomes understandable only +in historical context, as a remnant of times past retained so as +not to break compatibility. Example: the retention of octal as +default base for string escapes in <b><a href="#C">C</a></b>, in +spite of the better match of hexadecimal to ASCII and modern +byte-addressable architectures. See <b><a href="#dustydeck">dusty deck</a></b>. 2. More restrictively, a +feature with past but no present utility. Example: the +force-all-caps (LCASE) bits in the V7 and <b><a href="#BSD">BSD</a></b> Unix tty driver, designed for use with +monocase terminals. (In a perversion of the usual +backward-compatibility goal, this functionality has actually been +expanded and renamed in some later <b><a href="#USGUnix">USG +Unix</a></b> releases as the IUCLC and OLCUC bits.) 3. The FOSSIL +(Fido/Opus/Seadog Standard Interface Level) driver specification +for serial-port access to replace the <b><a href="#brain-dead">brain-dead</a></b> routines in the IBM PC ROMs. +Fossils are used by most MS-DOS <b><a href="#BBS">BBS</a></b> +software in preference to the `supported' ROM routines, which do +not support interrupt-driven operation or setting speeds above +9600; the use of a semistandard FOSSIL library is preferable to +the <b><a href="#baremetal">bare metal</a></b> serial port +programming otherwise required. Since the FOSSIL specification +allows additional functionality to be hooked in, drivers that use +the <b><a href="#hook">hook</a></b> but do not provide +serial-port access themselves are named with a modifier, as in +`video fossil'.</p> + +<hr> +Node:<a name="fourcolorglossies">four-color glossies</a>, +Next:<a rel="next" href="#frag">frag</a>, Previous:<a rel="previous" href="#fossil">fossil</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>four-color glossies</b> n.</p> + +<p>1. Literature created by <b><a href="#marketroid">marketroid</a></b>s that allegedly contains +technical specs but which is in fact as superficial as possible +without being totally <b><a href="#content-free">content-free</a></b>. "Forget the four-color +glossies, give me the tech ref manuals." Often applied as an +indication of superficiality even when the material is printed on +ordinary paper in black and white. Four-color-glossy manuals are +<i>never</i> useful for solving a problem. 2. [rare] Applied by +extension to manual pages that don't contain enough information +to diagnose why the program doesn't produce the expected or +desired output.</p> + +<hr> +Node:<a name="frag">frag</a>, Next:<a rel="next" href="#fragile">fragile</a>, Previous:<a rel="previous" href="#fourcolorglossies">four-color glossies</a>, Up:<a rel="up" +href="#chap06">= F =</a> <br> + + +<p><b>frag</b> n.,v.</p> + +<p>[from Vietnam-era U.S. military slang via the games Doom and +Quake] 1. To kill another player's <b><a href="#avatar">avatar</a></b> in a multiuser game. "I hold the office +Quake record with 40 frags." 2. To completely ruin something. +"Forget that power supply, the lightning strike fragged it. See +also <b><a href="#gib">gib</a></b>.</p> + +<hr> +Node:<a name="fragile">fragile</a>, Next:<a rel="next" href="#fred">fred</a>, Previous:<a rel="previous" href="#frag">frag</a>, Up:<a rel="up" href="#chap06">= F =</a> +<br> + + +<p><b>fragile</b> adj.</p> + +<p>Syn <b><a href="#brittle">brittle</a></b>.</p> + +<hr> +Node:<a name="fred">fred</a>, Next:<a rel="next" href="#FredFoobar">Fred Foobar</a>, Previous:<a rel="previous" +href="#fragile">fragile</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>fred</b> n.</p> + +<p>1. The personal name most frequently used as a <b><a href="#metasyntacticvariable">metasyntactic variable</a></b> (see +<b><a href="#foo">foo</a></b>). Allegedly popular because it's +easy for a non-touch-typist to type on a standard QWERTY +keyboard. In Great Britain, `fred', `jim' and `sheila' are common +metasyntactic variables because their uppercase versions were +<i>official</i> names given to the 3 memory areas that held I/O +status registers on the lovingly-remembered BBC Microcomputer! +(It is reported that SHEILA was poked the most often.) Unlike +<b><a href="#JRandomHacker">J. Random Hacker</a></b> or +`J. Random Loser', the name `fred' has no positive or negative +loading (but see <b><a href="#DrFredMbogo">Dr. Fred +Mbogo</a></b>). See also <b><a href="#barney">barney</a></b>. 2. +An acronym for `Flipping Ridiculous Electronic Device'; other +F-verbs may be substituted for `flipping'.</p> + +<hr> +Node:<a name="FredFoobar">Fred Foobar</a>, Next:<a rel="next" +href="#frednet">frednet</a>, Previous:<a rel="previous" href="#fred">fred</a>, Up:<a rel="up" href="#chap06">= F =</a> +<br> + + +<p><b>Fred Foobar</b> n.</p> + +<p><b><a href="#JRandomHacker">J. Random Hacker</a></b>'s +cousin. Any typical human being, more or less synomous with +`someone' except that Fred Foobar can be <b><a href="#backreference">backreference</a></b>d by name later on. "So +Fred Foobar will enter his phone number into the database, and +it'll be archived with the others. Months later, when Fred +searches..." See also <b><a href="#BloggsFamily">Bloggs +Family</a></b> and <b><a href="#DrFredMbogo">Dr. Fred +Mbogo</a></b></p> + +<hr> +Node:<a name="frednet">frednet</a>, Next:<a rel="next" href="#freesoftware">free software</a>, Previous:<a rel="previous" +href="#FredFoobar">Fred Foobar</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>frednet</b> /fred'net/ n.</p> + +<p>Used to refer to some <b><a href="#random">random</a></b> and +uncommon protocol encountered on a network. "We're implementing +bridging in our router to solve the frednet problem."</p> + +<hr> +Node:<a name="freesoftware">free software</a>, Next:<a rel="next" href="#freeware">freeware</a>, Previous:<a rel="previous" +href="#frednet">frednet</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>free software</b> n.</p> + +<p>As defined by Richard M. Stallman and used by the Free +Software movement, this means software that gives users enough +freedom to be used by the free software community. Specifically, +users must be free to modify the software for their private use, +and free to redistribute it either with or without modifications, +either commercially or noncommercially, either gratis or charging +a distribution fee. Free software has existed since the dawn of +computing; Free Software as a movement began in 1984 with the GNU +Project. See also <b><a href="#opensource">open +source</a></b>.</p> + +<hr> +Node:<a name="freeware">freeware</a>, Next:<a rel="next" href="#freeze">freeze</a>, Previous:<a rel="previous" href="#freesoftware">free software</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>freeware</b> n.</p> + +<p>[common] Free software, often written by enthusiasts and +distributed by users' groups, or via electronic mail, local +bulletin boards, <b><a href="#Usenet">Usenet</a></b>, or other +electronic media. At one time, `freeware' was a trademark of +Andrew Fluegelman, the author of the well-known MS-DOS comm +program PC-TALK III. It wasn't enforced after his mysterious +disappearance and presumed death in 1984. See <b><a href="#shareware">shareware</a></b>, <b><a href="#FRS">FRS</a></b>.</p> + +<hr> +Node:<a name="freeze">freeze</a>, Next:<a rel="next" href="#fried">fried</a>, Previous:<a rel="previous" href="#freeware">freeware</a>, Up:<a rel="up" href="#chap06">= +F =</a> <br> + + +<p><b>freeze</b> v.</p> + +<p>To lock an evolving software distribution or document against +changes so it can be released with some hope of stability. +Carries the strong implication that the item in question will +`unfreeze' at some future date. "OK, fix that bug and we'll +freeze for release."</p> + +<p>There are more specific constructions on this term. A `feature +freeze', for example, locks out modifications intended to +introduce new features but still allows bugfixes and completion +of existing features; a `code freeze' connotes no more changes at +all. At Sun Microsystems and elsewhere, one may also hear +references to `code slush' -- that is, an almost-but-not-quite +frozen state.</p> + +<hr> +Node:<a name="fried">fried</a>, Next:<a rel="next" href="#frink">frink</a>, Previous:<a rel="previous" href="#freeze">freeze</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>fried</b> adj.</p> + +<p>1. [common] Non-working due to hardware failure; burnt out. +Especially used of hardware brought down by a `power glitch' (see +<b><a href="#glitch">glitch</a></b>), <b><a href="#drop-outs">drop-outs</a></b>, a short, or some other electrical +event. (Sometimes this literally happens to electronic circuits! +In particular, resistors can burn out and transformers can melt +down, emitting noxious smoke -- see <b><a href="#friode">friode</a></b>, <b><a href="#SED">SED</a></b> and <b><a +href="#LER">LER</a></b>. However, this term is also used +metaphorically.) Compare <b><a href="#frotzed">frotzed</a></b>. +2. [common] Of people, exhausted. Said particularly of those who +continue to work in such a state. Often used as an explanation or +excuse. "Yeah, I know that fix destroyed the file system, but I +was fried when I put it in." Esp. common in conjunction with +`brain': "My brain is fried today, I'm very short on sleep."</p> + +<hr> +Node:<a name="frink">frink</a>, Next:<a rel="next" href="#friode">friode</a>, Previous:<a rel="previous" href="#fried">fried</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>frink</b> /frink/ v.</p> + +<p>The unknown ur-verb, fill in your own meaning. Found esp. on +the Usenet newsgroup <i>alt.fan.lemurs</i>, where it is said that +the lemurs know what `frink' means, but they aren't telling. +Compare <b><a href="#gorets">gorets</a></b>.</p> + +<hr> +Node:<a name="friode">friode</a>, Next:<a rel="next" href="#fritterware">fritterware</a>, Previous:<a rel="previous" href="#frink">frink</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>friode</b> /fri:'ohd/ n.</p> + +<p>[TMRC] A reversible (that is, fused or blown) diode. Compare +<b><a href="#fried">fried</a></b>; see also <b><a href="#SED">SED</a></b>, <b><a href="#LER">LER</a></b>.</p> + +<hr> +Node:<a name="fritterware">fritterware</a>, Next:<a rel="next" +href="#frob">frob</a>, Previous:<a rel="previous" href="#friode">friode</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>fritterware</b> n.</p> + +<p>An excess of capability that serves no productive end. The +canonical example is font-diddling software on the Mac (see <b><a +href="#macdink">macdink</a></b>); the term describes anything +that eats huge amounts of time for quite marginal gains in +function but seduces people into using it anyway. See also <b><a +href="#windowshopping">window shopping</a></b>.</p> + +<hr> +Node:<a name="frob">frob</a>, Next:<a rel="next" href="#frobnicate">frobnicate</a>, Previous:<a rel="previous" href="#fritterware">fritterware</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>frob</b> /frob/ 1. n.</p> + +<p>[MIT; very common] The <b><a href="#TMRC">TMRC</a></b> +definition was "FROB = a protruding arm or trunnion"; by +metaphoric extension, a `frob' is any random small thing; an +object that you can comfortably hold in one hand; something you +can frob (sense 2). See <b><a href="#frobnitz">frobnitz</a></b>. +2. vt. Abbreviated form of <b><a href="#frobnicate">frobnicate</a></b>. 3. [from the <b><a href="#MUD">MUD</a></b> world] A command on some MUDs that changes a +player's experience level (this can be used to make wizards); +also, to request <b><a href="#wizard">wizard</a></b> privileges +on the `professional courtesy' grounds that one is a wizard +elsewhere. The command is actually `frobnicate' but is +universally abbreviated to the shorter form.</p> + +<hr> +Node:<a name="frobnicate">frobnicate</a>, Next:<a rel="next" +href="#frobnitz">frobnitz</a>, Previous:<a rel="previous" href="#frob">frob</a>, Up:<a rel="up" href="#chap06">= F =</a> +<br> + + +<p><b>frobnicate</b> /frob'ni-kayt/ vt.</p> + +<p>[Poss. derived from <b><a href="#frobnitz">frobnitz</a></b>, +and usually abbreviated to <b><a href="#frob">frob</a></b>, but +`frobnicate' is recognized as the official full form.] To +manipulate or adjust, to tweak. One frequently frobs bits or +other 2-state devices. Thus: "Please frob the light switch" (that +is, flip it), but also "Stop frobbing that clasp; you'll break +it". One also sees the construction `to frob a frob'. See <b><a +href="#tweak">tweak</a></b> and <b><a href="#twiddle">twiddle</a></b>.</p> + +<p>Usage: frob, twiddle, and tweak sometimes connote points along +a continuum. `Frob' connotes aimless manipulation; `twiddle' +connotes gross manipulation, often a coarse search for a proper +setting; `tweak' connotes fine-tuning. If someone is turning a +knob on an oscilloscope, then if he's carefully adjusting it, he +is probably tweaking it; if he is just turning it but looking at +the screen, he is probably twiddling it; but if he's just doing +it because turning a knob is fun, he's frobbing it. The variant +`frobnosticate' has been recently reported.</p> + +<hr> +Node:<a name="frobnitz">frobnitz</a>, Next:<a rel="next" href="#frog">frog</a>, Previous:<a rel="previous" href="#frobnicate">frobnicate</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>frobnitz</b> /frob'nits/, pl. `frobnitzem' /frob'nit-zm/ or +`frobni' /frob'ni:/ n.</p> + +<p>[TMRC] An unspecified physical object, a widget. Also refers +to electronic black boxes. This rare form is usually abbreviated +to `frotz', or more commonly to <b><a href="#frob">frob</a></b>. +Also used are `frobnule' (/frob'n[y]ool/) and `frobule' +(/frob'yool/). Starting perhaps in 1979, `frobozz' /fr*-boz'/ +(plural: `frobbotzim' /fr*-bot'zm/) has also become very popular, +largely through its exposure as a name via <b><a href="#Zork">Zork</a></b>. These variants can also be applied to +nonphysical objects, such as data structures.</p> + +<p>Pete Samson, compiler of the original <b><a href="#TMRC">TMRC</a></b> lexicon, adds, "Under the TMRC [railroad] +layout were many storage boxes, managed (in 1958) by David R. +Sawyer. Several had fanciful designations written on them, such +as `Frobnitz Coil Oil'. Perhaps DRS intended Frobnitz to be a +proper name, but the name was quickly taken for the thing". This +was almost certainly the origin of the term.</p> + +<hr> +Node:<a name="frog">frog</a>, Next:<a rel="next" href="#frogging">frogging</a>, Previous:<a rel="previous" href="#frobnitz">frobnitz</a>, Up:<a rel="up" href="#chap06">= +F =</a> <br> + + +<p><b>frog</b> alt. `phrog'</p> + +<p>1. interj. Term of disgust (we seem to have a lot of them). 2. +Used as a name for just about anything. See <b><a href="#foo">foo</a></b>. 3. n. Of things, a crock. 4. n. Of people, +somewhere in between a turkey and a toad. 5. `froggy': adj. +Similar to <b><a href="#bagbiting">bagbiting</a></b>, but milder. +"This froggy program is taking forever to run!"</p> + +<hr> +Node:<a name="frogging">frogging</a>, Next:<a rel="next" href="#frontend">front end</a>, Previous:<a rel="previous" href="#frog">frog</a>, Up:<a rel="up" href="#chap06">= F =</a> +<br> + + +<p><b>frogging</b> [University of Waterloo] v.</p> + +<p>1. Partial corruption of a text file or input stream by some +bug or consistent glitch, as opposed to random events like line +noise or media failures. Might occur, for example, if one bit of +each incoming character on a tty were stuck, so that some +characters were correct and others were not. See <b><a href="#terminak">terminak</a></b> for a historical example and compare +<b><a href="#dreadhighbitdisease">dread high-bit +disease</a></b>. 2. By extension, accidental display of text in a +mode where the output device emits special symbols or mnemonics +rather than conventional ASCII. This often happens, for example, +when using a terminal or comm program on a device like an IBM PC +with a special `high-half' character set and with the bit-parity +assumption wrong. A hacker sufficiently familiar with ASCII bit +patterns might be able to read the display anyway.</p> + +<hr> +Node:<a name="frontend">front end</a>, Next:<a rel="next" +href="#frotz">frotz</a>, Previous:<a rel="previous" href="#frogging">frogging</a>, Up:<a rel="up" href="#chap06">= +F =</a> <br> + + +<p><b>front end</b> n.</p> + +<p>1. An intermediary computer that does set-up and filtering for +another (usually more powerful but less friendly) machine (a +`back end'). 2. What you're talking to when you have a +conversation with someone who is making replies without paying +attention. "Look at the dancing elephants!" "Uh-huh." "Do you +know what I just said?" "Sorry, you were talking to the front +end." 3. Software that provides an interface to another program +`behind' it, which may not be as user-friendly. Probably from +analogy with hardware front-ends (see sense 1) that interfaced +with mainframes.</p> + +<hr> +Node:<a name="frotz">frotz</a>, Next:<a rel="next" href="#frotzed">frotzed</a>, Previous:<a rel="previous" href="#frontend">front end</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>frotz</b> /frots/</p> + +<p>1. n. See <b><a href="#frobnitz">frobnitz</a></b>. 2. `mumble +frotz': An interjection of mildest disgust.</p> + +<hr> +Node:<a name="frotzed">frotzed</a>, Next:<a rel="next" href="#frowney">frowney</a>, Previous:<a rel="previous" href="#frotz">frotz</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>frotzed</b> /frotst/ adj.</p> + +<p><b><a href="#down">down</a></b> because of hardware problems. +Compare <b><a href="#fried">fried</a></b>. A machine that is +merely frotzed may be fixable without replacing parts, but a +fried machine is more seriously damaged.</p> + +<hr> +Node:<a name="frowney">frowney</a>, Next:<a rel="next" href="#FRS">FRS</a>, Previous:<a rel="previous" href="#frotzed">frotzed</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>frowney</b> n.</p> + +<p>(alt. `frowney face') See <b><a href="#emoticon">emoticon</a></b>.</p> + +<hr> +Node:<a name="FRS">FRS</a>, Next:<a rel="next" href="#fry">fry</a>, Previous:<a rel="previous" href="#frowney">frowney</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>FRS</b> // n.,obs.</p> + +<p>Abbreviation for "Freely Redistributable Software" which +entered general use on the Internet in 1995 after years of +low-level confusion over what exactly to call software written to +be passed around and shared (contending terms including <b><a +href="#freeware">freeware</a></b>, <b><a href="#shareware">shareware</a></b>, and `sourceware' were never +universally felt to be satisfactory for various subtle reasons). +The first formal conference on freely redistributable software +was held in Cambridge, Massachussetts, in February 1996 +(sponsored by the Free Software Foundation). The conference +organizers used the FRS abbreviation heavily in its calls for +papers and other literature during 1995. The term was in steady +though not common use until 1998 and the invention of <b><a href="#opensource">open source</a></b>.</p> + +<hr> +Node:<a name="fry">fry</a>, Next:<a rel="next" href="#fscking">fscking</a>, Previous:<a rel="previous" href="#FRS">FRS</a>, Up:<a rel="up" href="#chap06">= F =</a> +<br> + + +<p><b>fry</b></p> + +<p>1. vi. To fail. Said especially of smoke-producing hardware +failures. More generally, to become non-working. Usage: never +said of software, only of hardware and humans. See <b><a href="#fried">fried</a></b>, <b><a href="#magicsmoke">magic +smoke</a></b>. 2. vt. To cause to fail; to <b><a href="#roach">roach</a></b>, <b><a href="#toast">toast</a></b>, or +<b><a href="#hose">hose</a></b> a piece of hardware. Never used +of software or humans, but compare <b><a href="#fried">fried</a></b>.</p> + +<hr> +Node:<a name="fscking">fscking</a>, Next:<a rel="next" href="#FSF">FSF</a>, Previous:<a rel="previous" href="#fry">fry</a>, +Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>fscking</b> /fus'-king/ or /eff'-seek-ing/ adj.</p> + +<p>[Usenet; common] Fucking, in the expletive sense (it refers to +the Unix filesystem-repair command fsck(1), of which it can be +said that if you have to use it at all you are having a bad day). +Originated on <b><a href="#scarydevilmonastery">scary devil +monastery</a></b> and the <i>bofh.net</i> newsgroups, but became +much more widespread following the passage of <b><a href="#CDA">CDA</a></b>. Also occasionally seen in the variant "What +the fsck?"</p> + +<hr> +Node:<a name="FSF">FSF</a>, Next:<a rel="next" href="#FTP">FTP</a>, Previous:<a rel="previous" href="#fscking">fscking</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>FSF</b> /F-S-F/ abbrev.</p> + +<p>Common abbreviation (both spoken and written) for the name of +the Free Software Foundation, a nonprofit educational association +formed to support the <b><a href="#GNU">GNU</a></b> project.</p> + +<hr> +Node:<a name="FTP">FTP</a>, Next:<a rel="next" href="#-fu">-fu</a>, Previous:<a rel="previous" href="#FSF">FSF</a>, +Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>FTP</b> /F-T-P/, <i>not</i> /fit'ip/</p> + +<p>1. [techspeak] n. The File Transfer Protocol for transmitting +files between systems on the Internet. 2. vt. To <b><a href="#beam">beam</a></b> a file using the File Transfer Protocol. 3. +Sometimes used as a generic even for file transfers not using +<b><a href="#FTP">FTP</a></b>. "Lemme get a copy of "Wuthering +Heights" ftp'd from uunet."</p> + +<hr> +Node:<a name="-fu">-fu</a>, Next:<a rel="next" href="#FUBAR">FUBAR</a>, Previous:<a rel="previous" href="#FTP">FTP</a>, Up:<a rel="up" href="#chap06">= F =</a> +<br> + + +<p><b>-fu</b></p> + +<p>[common; generalized from `kung-fu'] Combining form denoting +expert practice of a skill. "That's going to take some serious +code-fu." First sighted in connection with the GIMP's +remote-scripting facility, script-fu, in 1998.</p> + +<hr> +Node:<a name="FUBAR">FUBAR</a>, Next:<a rel="next" href="#fuckmeharder">fuck me harder</a>, Previous:<a rel="previous" href="#-fu">-fu</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>FUBAR</b> n.</p> + +<p>The Failed UniBus Address Register in a VAX. A good example of +how jargon can occasionally be snuck past the <b><a href="#suit">suit</a></b>s; see <b><a href="#foobar">foobar</a></b>, +and <b><a href="#foo">foo</a></b> for a fuller etymology.</p> + +<hr> +Node:<a name="fuckmeharder">fuck me harder</a>, Next:<a +rel="next" href="#FUD">FUD</a>, Previous:<a rel="previous" href="#FUBAR">FUBAR</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>fuck me harder</b> excl.</p> + +<p>Sometimes uttered in response to egregious misbehavior, esp. +in software, and esp. of misbehaviors which seem unfairly +persistent (as though designed in by the imp of the perverse). +Often theatrically elaborated: "Aiighhh! Fuck me with a +piledriver and 16 feet of curare-tipped wrought-iron fence +<i>and no lubricants</i>!" The phrase is sometimes heard +abbreviated `FMH' in polite company.</p> + +<p>[This entry is an extreme example of the hackish habit of +coining elaborate and evocative terms for lossage. Here we see a +quite self-conscious parody of mainstream expletives that has +become a running gag in part of the hacker culture; it +illustrates the hackish tendency to turn any situation, even one +of extreme frustration, into an intellectual game (the point +being, in this case, to creatively produce a long-winded +description of the most anatomically absurd mental image possible +-- the short forms implicitly allude to all the ridiculous long +forms ever spoken). Scatological language is actually relatively +uncommon among hackers, and there was some controversy over +whether this entry ought to be included at all. As it reflects a +live usage recognizably peculiar to the hacker culture, we feel +it is in the hackish spirit of truthfulness and opposition to all +forms of censorship to record it here. --ESR & GLS]</p> + +<hr> +Node:<a name="FUD">FUD</a>, Next:<a rel="next" href="#FUDwars">FUD wars</a>, Previous:<a rel="previous" href="#fuckmeharder">fuck me harder</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>FUD</b> /fuhd/ n.</p> + +<p>Defined by Gene Amdahl after he left IBM to found his own +company: "FUD is the fear, uncertainty, and doubt that IBM sales +people instill in the minds of potential customers who might be +considering [Amdahl] products." The idea, of course, was to +persuade them to go with safe IBM gear rather than with +competitors' equipment. This implicit coercion was traditionally +accomplished by promising that Good Things would happen to people +who stuck with IBM, but Dark Shadows loomed over the future of +competitors' equipment or software. See <b><a href="#IBM">IBM</a></b>. After 1990 the term FUD was associated +increasingly frequently with <b><a href="#Microsoft">Microsoft</a></b>, and has become generalized to +refer to any kind of disinformation used as a competitive +weapon.</p> + +<hr> +Node:<a name="FUDwars">FUD wars</a>, Next:<a rel="next" href="#fudge">fudge</a>, Previous:<a rel="previous" href="#FUD">FUD</a>, Up:<a rel="up" href="#chap06">= F =</a> +<br> + + +<p><b>FUD wars</b> /fuhd worz/ n.</p> + +<p>[from <b><a href="#FUD">FUD</a></b>] Political posturing +engaged in by hardware and software vendors ostensibly committed +to standardization but actually willing to fragment the market to +protect their own shares. The Unix International vs. OSF conflict +about Unix standards was one outstanding example; Microsoft vs. +Netscape vs. W3C about HTML standards is another.</p> + +<hr> +Node:<a name="fudge">fudge</a>, Next:<a rel="next" href="#fudgefactor">fudge factor</a>, Previous:<a rel="previous" +href="#FUDwars">FUD wars</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>fudge</b></p> + +<p>1. vt. To perform in an incomplete but marginally acceptable +way, particularly with respect to the writing of a program. "I +didn't feel like going through that pain and suffering, so I +fudged it -- I'll fix it later." 2. n. The resulting code.</p> + +<hr> +Node:<a name="fudgefactor">fudge factor</a>, Next:<a rel="next" href="#fuelup">fuel up</a>, Previous:<a rel="previous" +href="#fudge">fudge</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>fudge factor</b> n.</p> + +<p>[common] A value or parameter that is varied in an ad hoc way +to produce the desired result. The terms `tolerance' and <b><a +href="#slop">slop</a></b> are also used, though these usually +indicate a one-sided leeway, such as a buffer that is made larger +than necessary because one isn't sure exactly how large it needs +to be, and it is better to waste a little space than to lose +completely for not having enough. A fudge factor, on the other +hand, can often be tweaked in more than one direction. A good +example is the `fuzz' typically allowed in floating-point +calculations: two numbers being compared for equality must be +allowed to differ by a small amount; if that amount is too small, +a computation may never terminate, while if it is too large, +results will be needlessly inaccurate. Fudge factors are +frequently adjusted incorrectly by programmers who don't fully +understand their import. See also <b><a href="#coefficientofX">coefficient of X</a></b>.</p> + +<hr> +Node:<a name="fuelup">fuel up</a>, Next:<a rel="next" href="#FullMonty">Full Monty</a>, Previous:<a rel="previous" href="#fudgefactor">fudge factor</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>fuel up</b> vi.</p> + +<p>To eat or drink hurriedly in order to get back to hacking. +"Food-p?" "Yeah, let's fuel up." "Time for a <b><a href="#great-wall">great-wall</a></b>!" See also <b><a href="#orientalfood">oriental food</a></b>.</p> + +<hr> +Node:<a name="FullMonty">Full Monty</a>, Next:<a rel="next" +href="#fum">fum</a>, Previous:<a rel="previous" href="#fuelup">fuel up</a>, Up:<a rel="up" href="#chap06">= +F =</a> <br> + + +<p><b>Full Monty</b> n.</p> + +<p>See <b><a href="#monty">monty</a></b>, sense 2.</p> + +<hr> +Node:<a name="fum">fum</a>, Next:<a rel="next" href="#functino">functino</a>, Previous:<a rel="previous" href="#FullMonty">Full Monty</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>fum</b> n.</p> + +<p>[XEROX PARC] At PARC, often the third of the standard <b><a +href="#metasyntacticvariable">metasyntactic variable</a></b>s +(after <b><a href="#foo">foo</a></b> and <b><a href="#bar">bar</a></b>). Competes with <b><a href="#baz">baz</a></b>, +which is more common outside PARC.</p> + +<hr> +Node:<a name="functino">functino</a>, Next:<a rel="next" href="#funky">funky</a>, Previous:<a rel="previous" href="#fum">fum</a>, Up:<a rel="up" href="#chap06">= F =</a> +<br> + + +<p><b>functino</b> n.</p> + +<p>[uncommon, U.K.; originally a serendipitous typo in 1994] A +pointer to a function in C and C++. By association with +sub-atomic particles such as the neutrino, it accurately conveys +an impression of smallness (one pointer is four bytes on most +systems) and speed (hackers can and do use arrays of functinos to +replace a switch() statement).</p> + +<hr> +Node:<a name="funky">funky</a>, Next:<a rel="next" href="#funnymoney">funny money</a>, Previous:<a rel="previous" +href="#functino">functino</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>funky</b> adj.</p> + +<p>Said of something that functions, but in a slightly strange, +klugey way. It does the job and would be difficult to change, so +its obvious non-optimality is left alone. Often used to describe +interfaces. The more bugs something has that nobody has bothered +to fix because workarounds are easier, the funkier it is. <b><a +href="#TECO">TECO</a></b> and UUCP are funky. The Intel i860's +exception handling is extraordinarily funky. Most standards +acquire funkiness as they age. "The new mailer is installed, but +is still somewhat funky; if it bounces your mail for no reason, +try resubmitting it." "This UART is pretty funky. The data ready +line is active-high in interrupt mode and active-low in DMA +mode."</p> + +<hr> +Node:<a name="funnymoney">funny money</a>, Next:<a rel="next" +href="#furrfu">furrfu</a>, Previous:<a rel="previous" href="#funky">funky</a>, Up:<a rel="up" href="#chap06">= F +=</a> <br> + + +<p><b>funny money</b> n.</p> + +<p>1. Notional `dollar' units of computing time and/or storage +handed to students at the beginning of a computer course; also +called `play money' or `purple money' (in implicit opposition to +real or `green' money). In New Zealand and Germany the odd usage +`paper money' has been recorded; in Germany, the particularly +amusing synonym `transfer ruble' commemmorates the funny money +used for trade between COMECON countries back when the Soviet +Bloc still existed. When your funny money ran out, your account +froze and you needed to go to a professor to get more. +Fortunately, the plunging cost of timesharing cycles has made +this less common. The amounts allocated were almost invariably +too small, even for the non-hackers who wanted to slide by with +minimum work. In extreme cases, the practice led to small-scale +black markets in bootlegged computer accounts. 2. By extension, +phantom money or quantity tickets of any kind used as a +resource-allocation hack within a system. Antonym: `real +money'.</p> + +<hr> +Node:<a name="furrfu">furrfu</a>, Next:<a rel="next" href="#fuzzball">fuzzball</a>, Previous:<a rel="previous" href="#funnymoney">funny money</a>, Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>furrfu</b> excl.</p> + +<p>[Usenet; written, only rarely spoken] Written-only equivalent +of "Sheesh!"; it is, in fact, "sheesh" modified by <b><a href="#rot13">rot13</a></b>. Evolved in mid-1992 as a response to +notably silly postings repeating urban myths on the Usenet +newsgroup <i>alt.folklore.urban</i>, after some posters +complained that "Sheesh!" as a response to <b><a href="#newbie">newbie</a></b>s was being overused. See also <b><a +href="#FOAF">FOAF</a></b>.</p> + +<hr> +Node:<a name="fuzzball">fuzzball</a>, Next:<a rel="next" href="#G">G</a>, Previous:<a rel="previous" href="#furrfu">furrfu</a>, +Up:<a rel="up" href="#chap06">= F =</a> <br> + + +<p><b>fuzzball</b> n.</p> + +<p>[TCP/IP hackers] A DEC LSI-11 running a particular suite of +homebrewed software written by Dave Mills and assorted +co-conspirators, used in the early 1980s for Internet protocol +testbedding and experimentation. These were used as NSFnet +backbone sites in its early 56kb-line days; a few were still +active on the Internet as late as mid-1993, doing odd jobs such +as network time service.</p> + +<hr> +Node:<a name="chap07">= G =</a>, Next:<a rel="next" href="#chap08">= H =</a>, Previous:<a rel="previous" href="#chap06">= F =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= G =</h2> + +<ul> +<li><a href="#G">G</a>:</li> + +<li><a href="#g-file">g-file</a>:</li> + +<li><a href="#gabriel">gabriel</a>:</li> + +<li><a href="#gag">gag</a>:</li> + +<li><a href="#gangbang">gang bang</a>:</li> + +<li><a href="#garbagecollect">garbage collect</a>:</li> + +<li><a href="#garply">garply</a>:</li> + +<li><a href="#gas">gas</a>:</li> + +<li><a href="#gaseous">gaseous</a>:</li> + +<li><a href="#GatessLaw">Gates's Law</a>:</li> + +<li><a href="#gawble">gawble</a>:</li> + +<li><a href="#GC">GC</a>:</li> + +<li><a href="#GCOS">GCOS</a>:</li> + +<li><a href="#GECOS">GECOS</a>:</li> + +<li><a href="#gedanken">gedanken</a>:</li> + +<li><a href="#geef">geef</a>:</li> + +<li><a href="#geekcode">geek code</a>:</li> + +<li><a href="#geekout">geek out</a>:</li> + +<li><a href="#gen">gen</a>:</li> + +<li><a href="#gendermender">gender mender</a>:</li> + +<li><a href="#GeneralPublicVirus">General Public +Virus</a>:</li> + +<li><a href="#generate">generate</a>:</li> + +<li><a href="#GeniusFromMarsTechnique">Genius From Mars +Technique</a>:</li> + +<li><a href="#gensym">gensym</a>:</li> + +<li><a href="#Getalife">Get a life!</a>:</li> + +<li><a href="#Getarealcomputer">Get a real +computer!</a>:</li> + +<li><a href="#GFR">GFR</a>:</li> + +<li><a href="#gib">gib</a>:</li> + +<li><a href="#GIFsat11">GIFs at 11</a>:</li> + +<li><a href="#gig">gig</a>:</li> + +<li><a href="#giga-">giga-</a>:</li> + +<li><a href="#GIGO">GIGO</a>:</li> + +<li><a href="#gilley">gilley</a>:</li> + +<li><a href="#gillion">gillion</a>:</li> + +<li><a href="#ginger">ginger</a>:</li> + +<li><a href="#GIPS">GIPS</a>:</li> + +<li><a href="#glark">glark</a>:</li> + +<li><a href="#glass">glass</a>:</li> + +<li><a href="#glasstty">glass tty</a>:</li> + +<li><a href="#glassfet">glassfet</a>:</li> + +<li><a href="#glitch">glitch</a>:</li> + +<li><a href="#glob">glob</a>:</li> + +<li><a href="#glork">glork</a>:</li> + +<li><a href="#glue">glue</a>:</li> + +<li><a href="#gnarly">gnarly</a>:</li> + +<li><a href="#GNU">GNU</a>:</li> + +<li><a href="#gnubie">gnubie</a>:</li> + +<li><a href="#GNUMACS">GNUMACS</a>:</li> + +<li><a href="#goflatline">go flatline</a>:</li> + +<li><a href="#goRoot">go root</a>:</li> + +<li><a href="#gofasterstripes">go-faster stripes</a>:</li> + +<li><a href="#GoAT">GoAT</a>:</li> + +<li><a href="#gobble">gobble</a>:</li> + +<li><a href="#GodwinsLaw">Godwin's Law</a>:</li> + +<li><a href="#Godzillagram">Godzillagram</a>:</li> + +<li><a href="#golden">golden</a>:</li> + +<li><a href="#golfballprinter">golf-ball printer</a>:</li> + +<li><a href="#gonk">gonk</a>:</li> + +<li><a href="#gonkulator">gonkulator</a>:</li> + +<li><a href="#gonzo">gonzo</a>:</li> + +<li><a href="#GoodThing">Good Thing</a>:</li> + +<li><a href="#gopher">gopher</a>:</li> + +<li><a href="#gopherhole">gopher hole</a>:</li> + +<li><a href="#gorets">gorets</a>:</li> + +<li><a href="#gorillaarm">gorilla arm</a>:</li> + +<li><a href="#gorp">gorp</a>:</li> + +<li><a href="#GOSMACS">GOSMACS</a>:</li> + +<li><a href="#Gosperism">Gosperism</a>:</li> + +<li><a href="#gotcha">gotcha</a>:</li> + +<li><a href="#GPL">GPL</a>:</li> + +<li><a href="#GPV">GPV</a>:</li> + +<li><a href="#grault">grault</a>:</li> + +<li><a href="#graygoo">gray goo</a>:</li> + +<li><a href="#GreatRenaming">Great Renaming</a>:</li> + +<li><a href="#GreatRunes">Great Runes</a>:</li> + +<li><a href="#GreatWorm">Great Worm</a>:</li> + +<li><a href="#great-wall">great-wall</a>:</li> + +<li><a href="#GreenBook">Green Book</a>:</li> + +<li><a href="#greenbytes">green bytes</a>:</li> + +<li><a href="#greencard">green card</a>:</li> + +<li><a href="#greenlightning">green lightning</a>:</li> + +<li><a href="#greenmachine">green machine</a>:</li> + +<li><a href="#GreensTheorem">Green's Theorem</a>:</li> + +<li><a href="#greenbar">greenbar</a>:</li> + +<li><a href="#grep">grep</a>:</li> + +<li><a href="#gribble">gribble</a>:</li> + +<li><a href="#grilf">grilf</a>:</li> + +<li><a href="#grind">grind</a>:</li> + +<li><a href="#grindcrank">grind crank</a>:</li> + +<li><a href="#gripenet">gripenet</a>:</li> + +<li><a href="#gritch">gritch</a>:</li> + +<li><a href="#grok">grok</a>:</li> + +<li><a href="#gronk">gronk</a>:</li> + +<li><a href="#gronkout">gronk out</a>:</li> + +<li><a href="#gronked">gronked</a>:</li> + +<li><a href="#grovel">grovel</a>:</li> + +<li><a href="#grue">grue</a>:</li> + +<li><a href="#grunge">grunge</a>:</li> + +<li><a href="#gubbish">gubbish</a>:</li> + +<li><a href="#Guido">Guido</a>:</li> + +<li><a href="#guiltware">guiltware</a>:</li> + +<li><a href="#gumby">gumby</a>:</li> + +<li><a href="#gun">gun</a>:</li> + +<li><a href="#gunch">gunch</a>:</li> + +<li><a href="#gunpowderchicken">gunpowder chicken</a>:</li> + +<li><a href="#gurfle">gurfle</a>:</li> + +<li><a href="#guru">guru</a>:</li> + +<li><a href="#gurumeditation">guru meditation</a>:</li> + +<li><a href="#gweep">gweep</a>:</li> +</ul> + +<hr> +Node:<a name="G">G</a>, Next:<a rel="next" href="#g-file">g-file</a>, Previous:<a rel="previous" href="#fuzzball">fuzzball</a>, Up:<a rel="up" href="#chap07">= +G =</a> <br> + + +<p><b>G</b> pref.,suff.</p> + +<p>[SI] See <b><a href="#quantifiers">quantifiers</a></b>.</p> + +<hr> +Node:<a name="g-file">g-file</a>, Next:<a rel="next" href="#gabriel">gabriel</a>, Previous:<a rel="previous" href="#G">G</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>g-file</b> n.</p> + +<p>[Commodore BBS culture] Any file that is written with the +intention of being read by a human rather than a machine, such as +the Jargon File, documentation, humor files, hacker lore, and +technical materials.</p> + +<p>This term survives from the nearly forgotten Commodore 64 +underground and BBS community. In the early 80s, C-Net had +emerged as the most popular C64 BBS software for systems which +encouraged messaging (as opposed to file transfer). There were +three main options for files: Program files (p-files), which +served the same function as `doors' in today's systems, UD files +(the user upload/download section), and g-files. Anything that +was meant to be read was included in g-files.</p> + +<hr> +Node:<a name="gabriel">gabriel</a>, Next:<a rel="next" href="#gag">gag</a>, Previous:<a rel="previous" href="#g-file">g-file</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>gabriel</b> /gay'bree-*l/ n.</p> + +<p>[for Dick Gabriel, SAIL LISP hacker and volleyball fanatic] An +unnecessary (in the opinion of the opponent) stalling tactic, +e.g., tying one's shoelaces or combing one's hair repeatedly, +asking the time, etc. Also used to refer to the perpetrator of +such tactics. Also, `pulling a Gabriel', `Gabriel mode'.</p> + +<hr> +Node:<a name="gag">gag</a>, Next:<a rel="next" href="#gangbang">gang bang</a>, Previous:<a rel="previous" href="#gabriel">gabriel</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>gag</b> vi.</p> + +<p>Equivalent to <b><a href="#choke">choke</a></b>, but connotes +more disgust. "Hey, this is FORTRAN code. No wonder the C +compiler gagged." See also <b><a href="#barf">barf</a></b>.</p> + +<hr> +Node:<a name="gangbang">gang bang</a>, Next:<a rel="next" +href="#garbagecollect">garbage collect</a>, Previous:<a rel="previous" href="#gag">gag</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>gang bang</b> n.</p> + +<p>The use of large numbers of loosely coupled programmers in an +attempt to wedge a great many features into a product in a short +time. Though there have been memorable gang bangs (e.g., that +over-the-weekend assembler port mentioned in Steven Levy's +"Hackers"), most are perpetrated by large companies trying to +meet deadlines; the inevitable result is enormous buggy masses of +code entirely lacking in <b><a href="#orthogonal">orthogonal</a></b>ity. When market-driven managers +make a list of all the features the competition has and assign +one programmer to implement each, the probability of maintaining +a coherent (or even functional) design goes infinitesimal. See +also <b><a href="#firefighting">firefighting</a></b>, <b><a href="#MongolianHordestechnique">Mongolian Hordes +technique</a></b>, <b><a href="#ConwaysLaw">Conway's +Law</a></b>.</p> + +<hr> +Node:<a name="garbagecollect">garbage collect</a>, Next:<a +rel="next" href="#garply">garply</a>, Previous:<a rel="previous" +href="#gangbang">gang bang</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>garbage collect</b> vi.</p> + +<p>(also `garbage collection', n.) See <b><a href="#GC">GC</a></b>.</p> + +<hr> +Node:<a name="garply">garply</a>, Next:<a rel="next" href="#gas">gas</a>, Previous:<a rel="previous" href="#garbagecollect">garbage collect</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>garply</b> /gar'plee/ n.</p> + +<p>[Stanford] Another metasyntactic variable (see <b><a href="#foo">foo</a></b>); once popular among SAIL hackers.</p> + +<hr> +Node:<a name="gas">gas</a>, Next:<a rel="next" href="#gaseous">gaseous</a>, Previous:<a rel="previous" href="#garply">garply</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>gas</b></p> + +<p>[as in `gas chamber'] 1. interj. A term of disgust and hatred, +implying that gas should be dispensed in generous quantities, +thereby exterminating the source of irritation. "Some loser just +reloaded the system for no reason! Gas!" 2. interj. A suggestion +that someone or something ought to be flushed out of mercy. "The +system's getting <b><a href="#wedged">wedged</a></b> every few +minutes. Gas!" 3. vt. To <b><a href="#flush">flush</a></b> (sense +1). "You should gas that old crufty software." 4. [IBM] n. Dead +space in nonsequentially organized files that was occupied by +data that has since been deleted; the compression operation that +removes it is called `degassing' (by analogy, perhaps, with the +use of the same term in vacuum technology). 5. [IBM] n. Empty +space on a disk that has been clandestinely allocated against +future need.</p> + +<hr> +Node:<a name="gaseous">gaseous</a>, Next:<a rel="next" href="#GatessLaw">Gates's Law</a>, Previous:<a rel="previous" +href="#gas">gas</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>gaseous</b> adj.</p> + +<p>Deserving of being <b><a href="#gas">gas</a></b>sed. +Disseminated by Geoff Goodfellow while at SRI; became +particularly popular after the Moscone-Milk killings in San +Francisco, when it was learned that the defendant Dan White (a +politician who had supported Proposition 7) would get the gas +chamber under Proposition 7 if convicted of first-degree murder +(he was eventually convicted of manslaughter).</p> + +<hr> +Node:<a name="GatessLaw">Gates's Law</a>, Next:<a rel="next" +href="#gawble">gawble</a>, Previous:<a rel="previous" href="#gaseous">gaseous</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>Gates's Law</b></p> + +<p>"The speed of software halves every 18 months." This oft-cited +law is an ironic comment on the tendency of software bloat to +outpace the every-18-month doubling in hardware caopacity per +dollar predicted by <b><a href="#MooresLaw">Moore's +Law</a></b>. The reference is to Bill Gates; Microsoft is widely +considered among the worst if not the worst of the perpetrators +of bloat.</p> + +<hr> +Node:<a name="gawble">gawble</a>, Next:<a rel="next" href="#GC">GC</a>, Previous:<a rel="previous" href="#GatessLaw">Gates's Law</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>gawble</b> /gaw'bl/ n.</p> + +<p>See <b><a href="#chawmp">chawmp</a></b>.</p> + +<hr> +Node:<a name="GC">GC</a>, Next:<a rel="next" href="#GCOS">GCOS</a>, Previous:<a rel="previous" href="#gawble">gawble</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>GC</b> /G-C/</p> + +<p>[from LISP terminology; `Garbage Collect'] 1. vt. To clean up +and throw away useless things. "I think I'll GC the top of my +desk today." When said of files, this is equivalent to <b><a +href="#GFR">GFR</a></b>. 2. vt. To recycle, reclaim, or put to +another use. 3. n. An instantiation of the garbage collector +process.</p> + +<p>`Garbage collection' is computer-science techspeak for a +particular class of strategies for dynamically but transparently +reallocating computer memory (i.e., without requiring explicit +allocation and deallocation by higher-level software). One such +strategy involves periodically scanning all the data in memory +and determining what is no longer accessible; useless data items +are then discarded so that the memory they occupy can be recycled +and used for another purpose. Implementations of the LISP +language usually use garbage collection.</p> + +<p>In jargon, the full phrase is sometimes heard but the <b><a +href="#abbrev">abbrev</a></b> GC is more frequently used because +it is shorter. Note that there is an ambiguity in usage that has +to be resolved by context: "I'm going to garbage-collect my desk" +usually means to clean out the drawers, but it could also mean to +throw away or recycle the desk itself.</p> + +<hr> +Node:<a name="GCOS">GCOS</a>, Next:<a rel="next" href="#GECOS">GECOS</a>, Previous:<a rel="previous" href="#GC">GC</a>, +Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>GCOS</b> /jee'kohs/ n.</p> + +<p>A <b><a href="#quick-and-dirty">quick-and-dirty</a></b> <b><a +href="#clone">clone</a></b> of System/360 DOS that emerged from +GE around 1970; originally called GECOS (the General Electric +Comprehensive Operating System). Later kluged to support +primitive timesharing and transaction processing. After the +buyout of GE's computer division by Honeywell, the name was +changed to General Comprehensive Operating System (GCOS). Other +OS groups at Honeywell began referring to it as `God's Chosen +Operating System', allegedly in reaction to the GCOS crowd's +uninformed and snotty attitude about the superiority of their +product. All this might be of zero interest, except for two +facts: (1) The GCOS people won the political war, and this led in +the orphaning and eventual death of Honeywell <b><a href="#Multics">Multics</a></b>, and (2) GECOS/GCOS left one permanent +mark on Unix. Some early Unix systems at Bell Labs used GCOS +machines for print spooling and various other services; the field +added to <code>/etc/passwd</code> to carry GCOS ID information +was called the `GECOS field' and survives today as the +<code>pw_gecos</code> member used for the user's full name and +other human-ID information. GCOS later played a major role in +keeping Honeywell a dismal also-ran in the mainframe market, and +was itself mostly ditched for Unix in the late 1980s when +Honeywell began to retire its aging <b><a href="#bigiron">big +iron</a></b> designs.</p> + +<hr> +Node:<a name="GECOS">GECOS</a>, Next:<a rel="next" href="#gedanken">gedanken</a>, Previous:<a rel="previous" href="#GCOS">GCOS</a>, Up:<a rel="up" href="#chap07">= G =</a> +<br> + + +<p><b>GECOS</b> /jee'kohs/ n.</p> + +<p>See <b><a href="#GCOS">GCOS</a></b>.</p> + +<hr> +Node:<a name="gedanken">gedanken</a>, Next:<a rel="next" href="#geef">geef</a>, Previous:<a rel="previous" href="#GECOS">GECOS</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>gedanken</b> /g*-dahn'kn/ adj.</p> + +<p>Ungrounded; impractical; not well-thought-out; untried; +untested.</p> + +<p>`Gedanken' is a German word for `thought'. A thought +experiment is one you carry out in your head. In physics, the +term `gedanken experiment' is used to refer to an experiment that +is impractical to carry out, but useful to consider because it +can be reasoned about theoretically. (A classic gedanken +experiment of relativity theory involves thinking about a man in +an elevator accelerating through space.) Gedanken experiments are +very useful in physics, but must be used with care. It's too easy +to idealize away some important aspect of the real world in +constructing the `apparatus'.</p> + +<p>Among hackers, accordingly, the word has a pejorative +connotation. It is typically used of a project, especially one in +artificial intelligence research, that is written up in grand +detail (typically as a Ph.D. thesis) without ever being +implemented to any great extent. Such a project is usually +perpetrated by people who aren't very good hackers or find +programming distasteful or are just in a hurry. A `gedanken +thesis' is usually marked by an obvious lack of intuition about +what is programmable and what is not, and about what does and +does not constitute a clear specification of an algorithm. See +also <b><a href="#AI-complete">AI-complete</a></b>, <b><a href="#DWIM">DWIM</a></b>.</p> + +<hr> +Node:<a name="geef">geef</a>, Next:<a rel="next" href="#geekcode">geek code</a>, Previous:<a rel="previous" href="#gedanken">gedanken</a>, Up:<a rel="up" href="#chap07">= +G =</a> <br> + + +<p><b>geef</b> v.</p> + +<p>[ostensibly from `gefingerpoken'] vt. Syn. <b><a href="#mung">mung</a></b>. See also <b><a href="#blinkenlights">blinkenlights</a></b>.</p> + +<hr> +Node:<a name="geekcode">geek code</a>, Next:<a rel="next" +href="#geekout">geek out</a>, Previous:<a rel="previous" href="#geef">geef</a>, Up:<a rel="up" href="#chap07">= G =</a> +<br> + + +<p><b>geek code</b> n.</p> + +<p>(also "Code of the Geeks"). A set of codes commonly used in +<b><a href="#sigblock">sig block</a></b>s to broadcast the +interests, skills, and aspirations of the poster. Features a G at +the left margin followed by numerous letter codes, often suffixed +with plusses or minuses. Because many net users are involved in +computer science, the most common prefix is `GCS'. To see a copy +of the current code, browse http://www.geekcode.com. Here is a +sample geek code (that of Robert Hayden, the code's inventor) +from that page:</p> + +<pre> +-----BEGIN GEEK CODE BLOCK----- +Version: 3.1 +GED/J d-- s:++>: a- C++(++++)$ ULUO++ P+>+++ L++ !E---- W+(---) N+++ +o+ K+++ w+(---) O- M+$>++ V-- PS++(+++)>$ PE++(+)>$ Y++ PGP++ t- 5+++ +X++ R+++>$ tv+ b+ DI+++ D+++ G+++++>$ e++$>++++ h r-- y+** +------END GEEK CODE BLOCK------ +</pre> + +<p>The geek code originated in 1993; it was inspired (according +to the inventor) by previous "bear", "smurf" and "twink" +style-and-sexual-preference codes from lesbian and gay <b><a +href="#newsgroup">newsgroup</a></b>s. It has in turn spawned +imitators; there is now even a "Saturn geek code" for owners of +the Saturn car. See also <b><a href="#computergeek">computer +geek</a></b>.</p> + +<hr> +Node:<a name="geekout">geek out</a>, Next:<a rel="next" href="#gen">gen</a>, Previous:<a rel="previous" href="#geekcode">geek code</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>geek out</b> vi.</p> + +<p>To temporarily enter techno-nerd mode while in a non-hackish +context, for example at parties held near computer equipment. +Especially used when you need to do or say something highly +technical and don't have time to explain: "Pardon me while I geek +out for a moment." See <b><a href="#computergeek">computer +geek</a></b>; see also <b><a href="#propellerhead">propeller +head</a></b>.</p> + +<hr> +Node:<a name="gen">gen</a>, Next:<a rel="next" href="#gendermender">gender mender</a>, Previous:<a rel="previous" +href="#geekout">geek out</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>gen</b> /jen/ n.,v.</p> + +<p>Short for <b><a href="#generate">generate</a></b>, used +frequently in both spoken and written contexts.</p> + +<hr> +Node:<a name="gendermender">gender mender</a>, Next:<a rel="next" href="#GeneralPublicVirus">General Public Virus</a>, +Previous:<a rel="previous" href="#gen">gen</a>, Up:<a rel="up" +href="#chap07">= G =</a> <br> + + +<p><b>gender mender</b> n.</p> + +<p>[common] A cable connector shell with either two male or two +female connectors on it, used to correct the mismatches that +result when some <b><a href="#loser">loser</a></b> didn't +understand the RS232C specification and the distinction between +DTE and DCE. Used esp. for RS-232C parts in either the original +D-25 or the IBM PC's bogus D-9 format. Also called `gender +bender', `gender blender', `sex changer', and even `homosexual +adapter;' however, there appears to be some confusion as to +whether a `male homosexual adapter' has pins on both sides (is +doubly male) or sockets on both sides (connects two males).</p> + +<hr> +Node:<a name="GeneralPublicVirus">General Public Virus</a>, +Next:<a rel="next" href="#generate">generate</a>, Previous:<a +rel="previous" href="#gendermender">gender mender</a>, Up:<a +rel="up" href="#chap07">= G =</a> <br> + + +<p><b>General Public Virus</b> n.</p> + +<p>Pejorative name for some versions of the <b><a href="#GNU">GNU</a></b> project <b><a href="#copyleft">copyleft</a></b> or General Public License (GPL), +which requires that any tools or <b><a href="#app">app</a></b>s +incorporating copylefted code must be source-distributed on the +same anti-proprietary terms as GNU stuff. Thus it is alleged that +the copyleft `infects' software generated with GNU tools, which +may in turn infect other software that reuses any of its code. +The Free Software Foundation's official position as of January +1991 is that copyright law limits the scope of the GPL to +"programs textually incorporating significant amounts of GNU +code", and that the `infection' is not passed on to third parties +unless actual GNU source is transmitted. Nevertheless, widespread +suspicion that the <b><a href="#copyleft">copyleft</a></b> +language is `boobytrapped' has caused many developers to avoid +using GNU tools and the GPL. Changes in the language of the +version 2.0 GPL did not eliminate this problem.</p> + +<hr> +Node:<a name="generate">generate</a>, Next:<a rel="next" href="#GeniusFromMarsTechnique">Genius From Mars +Technique</a>, Previous:<a rel="previous" href="#GeneralPublicVirus">General Public Virus</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>generate</b> vt.</p> + +<p>To produce something according to an algorithm or program or +set of rules, or as a (possibly unintended) side effect of the +execution of an algorithm or program. The opposite of <b><a href="#parse">parse</a></b>. This term retains its mechanistic +connotations (though often humorously) when used of human +behavior. "The guy is rational most of the time, but mention +nuclear energy around him and he'll generate <b><a href="#infinite">infinite</a></b> flamage."</p> + +<hr> +Node:<a name="GeniusFromMarsTechnique">Genius From Mars +Technique</a>, Next:<a rel="next" href="#gensym">gensym</a>, +Previous:<a rel="previous" href="#generate">generate</a>, Up:<a +rel="up" href="#chap07">= G =</a> <br> + + +<p><b>Genius From Mars Technique</b> n.</p> + +<p>[TMRC] A visionary quality which enables one to ignore the +standard approach and come up with a totally unexpected new +algorithm. An attack on a problem from an offbeat angle that no +one has ever thought of before, but that in retrospect makes +total sense. Compare <b><a href="#grok">grok</a></b>, <b><a href="#zen">zen</a></b>.</p> + +<hr> +Node:<a name="gensym">gensym</a>, Next:<a rel="next" href="#Getalife">Get a life!</a>, Previous:<a rel="previous" +href="#GeniusFromMarsTechnique">Genius From Mars +Technique</a>, Up:<a rel="up" href="#chap07">= G =</a> +<br> + + +<p><b>gensym</b> /jen'sim/</p> + +<p>[from MacLISP for `generated symbol'] 1. v. To invent a new +name for something temporary, in such a way that the name is +almost certainly not in conflict with one already in use. 2. n. +The resulting name. The canonical form of a gensym is `Gnnnn' +where nnnn represents a number; any LISP hacker would recognize +G0093 (for example) as a gensym. 3. A freshly generated data +structure with a gensymmed name. Gensymmed names are useful for +storing or uniquely identifying crufties (see <b><a href="#cruft">cruft</a></b>).</p> + +<hr> +Node:<a name="Getalife">Get a life!</a>, Next:<a rel="next" href="#Getarealcomputer">Get a real +computer!</a>, Previous:<a rel="previous" href="#gensym">gensym</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>Get a life!</b> imp.</p> + +<p>Hacker-standard way of suggesting that the person to whom it +is directed has succumbed to terminal geekdom (see <b><a href="#computergeek">computer geek</a></b>). Often heard on <b><a +href="#Usenet">Usenet</a></b>, esp. as a way of suggesting that +the target is taking some obscure issue of <b><a href="#theology">theology</a></b> too seriously. This exhortation was +popularized by William Shatner on a 1987 "Saturday Night Live" +episode in a speech that ended "Get a <i>life</i>!", but some +respondents believe it to have been in use before then. It was +certainly in wide use among hackers for years before achieving +mainstream currency via the sitcom "Get A Life" in 1990.</p> + +<hr> +Node:<a name="Getarealcomputer">Get a real +computer!</a>, Next:<a rel="next" href="#GFR">GFR</a>, +Previous:<a rel="previous" href="#Getalife">Get a +life!</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>Get a real computer!</b> imp.</p> + +<p>Typical hacker response to news that somebody is having +trouble getting work done on a system that (a) is single-tasking, +(b) has no hard disk, or (c) has an address space smaller than 16 +megabytes. This is as of early 1996; note that the threshold for +`real computer' rises with time. See <b><a href="#bittybox">bitty box</a></b> and <b><a href="#toy">toy</a></b>.</p> + +<hr> +Node:<a name="GFR">GFR</a>, Next:<a rel="next" href="#gib">gib</a>, Previous:<a rel="previous" href="#Getarealcomputer">Get a real computer!</a>, Up:<a +rel="up" href="#chap07">= G =</a> <br> + + +<p><b>GFR</b> /G-F-R/ vt.</p> + +<p>[ITS: from `Grim File Reaper', an ITS and LISP Machine +utility] To remove a file or files according to some +program-automated or semi-automatic manual procedure, especially +one designed to reclaim mass storage space or reduce name-space +clutter (the original GFR actually moved files to tape). Often +generalized to pieces of data below file level. "I used to have +his phone number, but I guess I <b><a href="#GFR">GFR</a></b>ed +it." See also <b><a href="#prowler">prowler</a></b>, <b><a href="#reaper">reaper</a></b>. Compare <b><a href="#GC">GC</a></b>, +which discards only provably worthless stuff.</p> + +<hr> +Node:<a name="gib">gib</a>, Next:<a rel="next" href="#GIFsat11">GIFs at 11</a>, Previous:<a rel="previous" +href="#GFR">GFR</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>gib</b> /jib/</p> + +<p>1. vi. To destroy utterly. Like <b><a href="#frag">frag</a></b>, but much more violent and final. "There's +no trace left. You definitely gibbed that bug". 2. n. Remnants +after total obliteration.</p> + +<p>Originated first by id software in the game Quake. It's short +for giblets (thus pronounced "jib"), and referred to the bloody +remains of slain opponents. Eventually the word was verbed, and +leaked into general usage afterward.</p> + +<hr> +Node:<a name="GIFsat11">GIFs at 11</a>, Next:<a rel="next" +href="#gig">gig</a>, Previous:<a rel="previous" href="#gib">gib</a>, Up:<a rel="up" href="#chap07">= G =</a> +<br> + + +<p><b>GIFs at 11</b></p> + +<p>[Fidonet] Fidonet alternative to <b><a href="#filmat11">film at 11</a></b>, especially in echoes +(Fidonet topic areas) where uuencoded GIFs are permitted. Other +formats, especially JPEG and MPEG, may be referenced instead.</p> + +<hr> +Node:<a name="gig">gig</a>, Next:<a rel="next" href="#giga-">giga-</a>, Previous:<a rel="previous" href="#GIFsat11">GIFs at 11</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>gig</b> /jig/ or /gig/ n.</p> + +<p>[SI] See <b><a href="#quantifiers">quantifiers</a></b>.</p> + +<hr> +Node:<a name="giga-">giga-</a>, Next:<a rel="next" href="#GIGO">GIGO</a>, Previous:<a rel="previous" href="#gig">gig</a>, +Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>giga-</b> /ji'ga/ or /gi'ga/ pref.</p> + +<p>[SI] See <b><a href="#quantifiers">quantifiers</a></b>.</p> + +<hr> +Node:<a name="GIGO">GIGO</a>, Next:<a rel="next" href="#gilley">gilley</a>, Previous:<a rel="previous" href="#giga-">giga-</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>GIGO</b> /gi:'goh/ [acronym]</p> + +<p>1. `Garbage In, Garbage Out' -- usually said in response to +<b><a href="#luser">luser</a></b>s who complain that a program +didn't "do the right thing" when given imperfect input or +otherwise mistreated in some way. Also commonly used to describe +failures in human decision making due to faulty, incomplete, or +imprecise data. 2. `Garbage In, Gospel Out': this more recent +expansion is a sardonic comment on the tendency human beings have +to put excessive trust in `computerized' data.</p> + +<hr> +Node:<a name="gilley">gilley</a>, Next:<a rel="next" href="#gillion">gillion</a>, Previous:<a rel="previous" href="#GIGO">GIGO</a>, Up:<a rel="up" href="#chap07">= G =</a> +<br> + + +<p><b>gilley</b> n.</p> + +<p>[Usenet] The unit of analogical <b><a href="#bogosity">bogosity</a></b>. According to its originator, the +standard for one gilley was "the act of bogotoficiously comparing +the shutting down of 1000 machines for a day with the killing of +one person". The milligilley has been found to suffice for most +normal conversational exchanges.</p> + +<hr> +Node:<a name="gillion">gillion</a>, Next:<a rel="next" href="#ginger">ginger</a>, Previous:<a rel="previous" href="#gilley">gilley</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>gillion</b> /gil'y*n/ or /jil'y*n/ n.</p> + +<p>[formed from <b><a href="#giga-">giga-</a></b> by analogy with +mega/million and tera/trillion] 10^9. Same as an American billion +or a British `milliard'. How one pronounces this depends on +whether one speaks <b><a href="#giga-">giga-</a></b> with a hard +or soft `g'.</p> + +<hr> +Node:<a name="ginger">ginger</a>, Next:<a rel="next" href="#GIPS">GIPS</a>, Previous:<a rel="previous" href="#gillion">gillion</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>ginger</b> n.</p> + +<p>See <b><a href="#saga">saga</a></b>.</p> + +<hr> +Node:<a name="GIPS">GIPS</a>, Next:<a rel="next" href="#glark">glark</a>, Previous:<a rel="previous" href="#ginger">ginger</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>GIPS</b> /gips/ or /jips/ n.</p> + +<p>[analogy with <b><a href="#MIPS">MIPS</a></b>] +Giga-Instructions per Second (also possibly `Gillions of +Instructions per Second'; see <b><a href="#gillion">gillion</a></b>). In 1991, this is used of only a +handful of highly parallel machines, but this is expected to +change. Compare <b><a href="#KIPS">KIPS</a></b>.</p> + +<hr> +Node:<a name="glark">glark</a>, Next:<a rel="next" href="#glass">glass</a>, Previous:<a rel="previous" href="#GIPS">GIPS</a>, Up:<a rel="up" href="#chap07">= G =</a> +<br> + + +<p><b>glark</b> /glark/ vt.</p> + +<p>To figure something out from context. "The System III manuals +are pretty poor, but you can generally glark the meaning from +context." Interestingly, the word was originally `glork'; the +context was "This gubblick contains many nonsklarkish English +flutzpahs, but the overall pluggandisp can be glorked [sic] from +context" (David Moser, quoted by Douglas Hofstadter in his +"Metamagical Themas" column in the January 1981 "Scientific +American"). It is conjectured that hacker usage mutated the verb +to `glark' because <b><a href="#glork">glork</a></b> was already +an established jargon term (some hackers do report using the +original term). Compare <b><a href="#grok">grok</a></b>, <b><a +href="#zen">zen</a></b>.</p> + +<hr> +Node:<a name="glass">glass</a>, Next:<a rel="next" href="#glasstty">glass tty</a>, Previous:<a rel="previous" href="#glark">glark</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>glass</b> n.</p> + +<p>[IBM] Synonym for <b><a href="#silicon">silicon</a></b>.</p> + +<hr> +Node:<a name="glasstty">glass tty</a>, Next:<a rel="next" +href="#glassfet">glassfet</a>, Previous:<a rel="previous" href="#glass">glass</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>glass tty</b> /glas T-T-Y/ or /glas ti'tee/ n.</p> + +<p>A terminal that has a display screen but which, because of +hardware or software limitations, behaves like a teletype or some +other printing terminal, thereby combining the disadvantages of +both: like a printing terminal, it can't do fancy display hacks, +and like a display terminal, it doesn't produce hard copy. An +example is the early `dumb' version of Lear-Siegler ADM 3 +(without cursor control). See <b><a href="#tube">tube</a></b>, +<b><a href="#tty">tty</a></b>; compare <b><a href="#dumbterminal">dumb terminal</a></b>, <b><a href="#smartterminal">smart terminal</a></b>. See "<b><a href="#TVTypewriters">TV Typewriters</a></b>" (Appendix A) for an +interesting true story about a glass tty.</p> + +<hr> +Node:<a name="glassfet">glassfet</a>, Next:<a rel="next" href="#glitch">glitch</a>, Previous:<a rel="previous" href="#glasstty">glass tty</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>glassfet</b> /glas'fet/ n.</p> + +<p>[by analogy with MOSFET, the acronym for +`Metal-Oxide-Semiconductor Field-Effect Transistor'] Syn. <b><a +href="#firebottle">firebottle</a></b>, a humorous way to refer to +a vacuum tube.</p> + +<hr> +Node:<a name="glitch">glitch</a>, Next:<a rel="next" href="#glob">glob</a>, Previous:<a rel="previous" href="#glassfet">glassfet</a>, Up:<a rel="up" href="#chap07">= +G =</a> <br> + + +<p><b>glitch</b> /glich/</p> + +<p>[very common; from German `glitschig' to slip, via Yiddish +`glitshen', to slide or skid] 1. n. A sudden interruption in +electric service, sanity, continuity, or program function. +Sometimes recoverable. An interruption in electric service is +specifically called a `power glitch' (also <b><a href="#powerhit">power hit</a></b>), of grave concern because it +usually crashes all the computers. In jargon, though, a hacker +who got to the middle of a sentence and then forgot how he or she +intended to complete it might say, "Sorry, I just glitched". 2. +vi. To commit a glitch. See <b><a href="#gritch">gritch</a></b>. +3. vt. [Stanford] To scroll a display screen, esp. several lines +at a time. <b><a href="#WAITS">WAITS</a></b> terminals used to do +this in order to avoid continuous scrolling, which is distracting +to the eye. 4. obs. Same as <b><a href="#magiccookie">magic +cookie</a></b>, sense 2.</p> + +<p>All these uses of `glitch' derive from the specific technical +meaning the term has in the electronic hardware world, where it +is now techspeak. A glitch can occur when the inputs of a circuit +change, and the outputs change to some <b><a href="#random">random</a></b> value for some very brief time before +they settle down to the correct value. If another circuit +inspects the output at just the wrong time, reading the random +value, the results can be very wrong and very hard to debug (a +glitch is one of many causes of electronic <b><a href="#heisenbug">heisenbug</a></b>s).</p> + +<hr> +Node:<a name="glob">glob</a>, Next:<a rel="next" href="#glork">glork</a>, Previous:<a rel="previous" href="#glitch">glitch</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>glob</b> /glob/, <i>not</i> /glohb/ v.,n.</p> + +<p>[Unix; common] To expand special characters in a wildcarded +name, or the act of so doing (the action is also called +`globbing'). The Unix conventions for filename wildcarding have +become sufficiently pervasive that many hackers use some of them +in written English, especially in email or news on technical +topics. Those commonly encountered include the following:</p> + +<blockquote> +<dl> +<dt><tt>*</tt></dt> + +<dd>wildcard for any string (see also <b><a href="#UNX">UNX</a></b>)</dd> + +<dt><tt>?</tt></dt> + +<dd>wildcard for any single character (generally read this way +only at the beginning or in the middle of a word)</dd> + +<dt><tt>[]</tt></dt> + +<dd>delimits a wildcard matching any of the enclosed +characters</dd> + +<dt><tt>{}</tt></dt> + +<dd>alternation of comma-separated alternatives; thus, +`foo{baz,qux}' would be read as `foobaz' or `fooqux'</dd> +</dl> +</blockquote> + +<br> +<p>Some examples: "He said his name was [KC]arl" (expresses +ambiguity). "I don't read talk.politics.*" (any of the +talk.politics subgroups on <b><a href="#Usenet">Usenet</a></b>). +Other examples are given under the entry for <b><a href="#X">X</a></b>. Note that glob patterns are similar, but not +identical, to those used in <b><a href="#regexp">regexp</a></b>s.</p> + +<p>Historical note: The jargon usage derives from +<code>glob</code>, the name of a subprogram that expanded +wildcards in archaic pre-Bourne versions of the Unix shell.</p> + +<hr> +Node:<a name="glork">glork</a>, Next:<a rel="next" href="#glue">glue</a>, Previous:<a rel="previous" href="#glob">glob</a>, Up:<a rel="up" href="#chap07">= G =</a> +<br> + + +<p><b>glork</b> /glork/</p> + +<p>1. interj. Term of mild surprise, usually tinged with outrage, +as when one attempts to save the results of two hours of editing +and finds that the system has just crashed. 2. Used as a name for +just about anything. See <b><a href="#foo">foo</a></b>. 3. vt. +Similar to <b><a href="#glitch">glitch</a></b>, but usually used +reflexively. "My program just glorked itself." 4. Syn. for <b><a +href="#glark">glark</a></b>, which see.</p> + +<hr> +Node:<a name="glue">glue</a>, Next:<a rel="next" href="#gnarly">gnarly</a>, Previous:<a rel="previous" href="#glork">glork</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>glue</b> n.</p> + +<p>Generic term for any interface logic or protocol that connects +two component blocks. For example, <b><a href="#BlueGlue">Blue +Glue</a></b> is IBM's SNA protocol, and hardware designers call +anything used to connect large VLSI's or circuit blocks `glue +logic'.</p> + +<hr> +Node:<a name="gnarly">gnarly</a>, Next:<a rel="next" href="#GNU">GNU</a>, Previous:<a rel="previous" href="#glue">glue</a>, +Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>gnarly</b> /nar'lee/ adj.</p> + +<p>Both <b><a href="#obscure">obscure</a></b> and <b><a href="#hairy">hairy</a></b> (sense 1). "<b><a href="#Yowx">Yow!</a></b> -- the tuned assembler implementation of +BitBlt is really gnarly!" From a similar but less specific usage +in surfer slang.</p> + +<hr> +Node:<a name="GNU">GNU</a>, Next:<a rel="next" href="#gnubie">gnubie</a>, Previous:<a rel="previous" href="#gnarly">gnarly</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>GNU</b> /gnoo/, <i>not</i> /noo/</p> + +<p> +1. [acronym: `GNU's Not Unix!', see <b><a href="#recursiveacronym">recursive +acronym</a></b>] A Unix-workalike development effort of the Free Software +Foundation headed by Richard Stallman. GNU EMACS and the GNU C compiler, two +tools designed for this project, have become very popular in hackerdom and +elsewhere. The GNU project was designed partly to proselytize for RMS's +position that information is community property and all software source should +be shared. One of its slogans is "Help stamp out software hoarding!" Though +this remains controversial (because it implicitly denies any right of designers +to own, assign, and sell the results of their labors), many hackers who +disagree with RMS have nevertheless cooperated to produce large amounts of +high-quality software for free redistribution under the Free Software +Foundation's imprimatur. The GNU project has a web page at <a +href="http://www.gnu.org">http://www.gnu.org</a>. See <b><a +href="#EMACS">EMACS</a></b>, <b><a href="#copyleft">copyleft</a></b>, <b><a +href="#GeneralPublicVirus">General Public Virus</a></b>, <b><a +href="#Linux">Linux</a></b>. 2. Noted Unix hacker John Gilmore, founder of +Usenet's anarchic alt.* hierarchy. +</p> + +<hr> +Node:<a name="gnubie">gnubie</a>, Next:<a rel="next" href="#GNUMACS">GNUMACS</a>, Previous:<a rel="previous" href="#GNU">GNU</a>, Up:<a rel="up" href="#chap07">= G =</a> +<br> + + +<p><b>gnubie</b> /noo'bee/ n.</p> + +<p>Written-only variant of <b><a href="#newbie">newbie</a></b> in +common use on IRC channels, which implies specifically someone +who is new to the Linux/open source/free software world.</p> + +<hr> +Node:<a name="GNUMACS">GNUMACS</a>, Next:<a rel="next" href="#goflatline">go flatline</a>, Previous:<a rel="previous" +href="#gnubie">gnubie</a>, Up:<a rel="up" href="#chap07">= +G =</a> <br> + + +<p><b>GNUMACS</b> /gnoo'maks/ n.</p> + +<p>[contraction of `GNU EMACS'] Often-heard abbreviated name for +the <b><a href="#GNU">GNU</a></b> project's flagship tool, <b><a +href="#EMACS">EMACS</a></b>. Used esp. in contrast with +<b>GOSMACS</b>.</p> + +<hr> +Node:<a name="goflatline">go flatline</a>, Next:<a rel="next" +href="#goRoot">go root</a>, Previous:<a rel="previous" href="#GNUMACS">GNUMACS</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>go flatline</b> v.</p> + +<p>[from cyberpunk SF, refers to flattening of EEG traces upon +brain-death] (also adjectival `flatlined'). 1. To <b><a href="#die">die</a></b>, terminate, or fail, esp. irreversibly. In +hacker parlance, this is used of machines only, human death being +considered somewhat too serious a matter to employ jargon-jokes +about. 2. To go completely quiescent; said of machines undergoing +controlled shutdown. "You can suffer file damage if you shut down +Unix but power off before the system has gone flatline." 3. Of a +video tube, to fail by losing vertical scan, so all one sees is a +bright horizontal line bisecting the screen.</p> + +<hr> +Node:<a name="goRoot">go root</a>, Next:<a rel="next" href="#gofasterstripes">go-faster stripes</a>, Previous:<a rel="previous" href="#goflatline">go flatline</a>, Up:<a rel="up" +href="#chap07">= G =</a> <br> + + +<p><b>go root</b> vi.</p> + +<p>[Unix; common] To temporarily enter <b><a href="#rootmode">root mode</a></b> in order to perform a privileged +operation. This use is deprecated in Australia, where v. `root' +is a synonym for "fuck".</p> + +<hr> +Node:<a name="gofasterstripes">go-faster stripes</a>, Next:<a +rel="next" href="#GoAT">GoAT</a>, Previous:<a rel="previous" +href="#goRoot">go root</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>go-faster stripes</b> n.</p> + +<p>[UK] Syn. <b><a href="#chrome">chrome</a></b>. Mainstream in +some parts of UK.</p> + +<hr> +Node:<a name="GoAT">GoAT</a>, Next:<a rel="next" href="#gobble">gobble</a>, Previous:<a rel="previous" href="#gofasterstripes">go-faster stripes</a>, Up:<a rel="up" +href="#chap07">= G =</a> <br> + + +<p><b>GoAT</b> //</p> + +<p>[Usenet] Abbreviation: "Go Away, Troll". See <b><a href="#troll">troll</a></b>.</p> + +<hr> +Node:<a name="gobble">gobble</a>, Next:<a rel="next" href="#GodwinsLaw">Godwin's Law</a>, Previous:<a rel="previous" +href="#GoAT">GoAT</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>gobble</b> vt.</p> + +<p>1. To consume, usu. used with `up'. "The output spy gobbles +characters out of a <b><a href="#tty">tty</a></b> output buffer." +2. To obtain, usu. used with `down'. "I guess I'll gobble down a +copy of the documentation tomorrow." See also <b><a href="#snarf">snarf</a></b>.</p> + +<hr> +Node:<a name="GodwinsLaw">Godwin's Law</a>, Next:<a rel="next" href="#Godzillagram">Godzillagram</a>, Previous:<a rel="previous" href="#gobble">gobble</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>Godwin's Law</b> prov.</p> + +<p>[Usenet] "As a Usenet discussion grows longer, the probability +of a comparison involving Nazis or Hitler approaches one." There +is a tradition in many groups that, once this occurs, that thread +is over, and whoever mentioned the Nazis has automatically lost +whatever argument was in progress. Godwin's Law thus practically +guarantees the existence of an upper bound on thread length in +those groups. However there is also a widely- recognized codicil +that any <i>intentional</i> triggering of Godwin's Law in order +to invoke its thread-ending effects will be unsuccessful.</p> + +<hr> +Node:<a name="Godzillagram">Godzillagram</a>, Next:<a rel="next" +href="#golden">golden</a>, Previous:<a rel="previous" href="#GodwinsLaw">Godwin's Law</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>Godzillagram</b> /god-zil'*-gram/ n.</p> + +<p>[from Japan's national hero] 1. A network packet that in +theory is a broadcast to every machine in the universe. The +typical case is an IP datagram whose destination IP address is +[255.255.255.255]. Fortunately, few gateways are foolish enough +to attempt to implement this case! 2. A network packet of maximum +size. An IP Godzillagram has 65,536 octets. Compare <b><a href="#supersourcequench">super source quench</a></b>, <b><a +href="#Christmastreepacket">Christmas tree packet</a></b>, +<b><a href="#martian">martian</a></b>.</p> + +<hr> +Node:<a name="golden">golden</a>, Next:<a rel="next" href="#golfballprinter">golf-ball printer</a>, Previous:<a rel="previous" href="#Godzillagram">Godzillagram</a>, Up:<a rel="up" +href="#chap07">= G =</a> <br> + + +<p><b>golden</b> adj.</p> + +<p>[prob. from folklore's `golden egg'] When used to describe a +magnetic medium (e.g., `golden disk', `golden tape'), describes +one containing a tested, up-to-spec, ready-to-ship software +version. Compare <b><a href="#platinum-iridium">platinum-iridium</a></b>.</p> + +<hr> +Node:<a name="golfballprinter">golf-ball printer</a>, Next:<a +rel="next" href="#gonk">gonk</a>, Previous:<a rel="previous" +href="#golden">golden</a>, Up:<a rel="up" href="#chap07">= +G =</a> <br> + + +<p><b>golf-ball printer</b> n. obs.</p> + +<p>The IBM 2741, a slow but letter-quality printing device and +terminal based on the IBM Selectric typewriter. The `golf ball' +was a little spherical frob bearing reversed embossed images of +88 different characters arranged on four parallels of latitude; +one could change the font by swapping in a different golf ball. +The print element spun and jerked alarmingly in action and when +in motion was sometimes described as an `infuriated golf ball'. +This was the technology that enabled APL to use a non-EBCDIC, +non-ASCII, and in fact completely non-standard character set. +This put it 10 years ahead of its time -- where it stayed, firmly +rooted, for the next 20, until character displays gave way to +programmable bit-mapped devices with the flexibility to support +other character sets.</p> + +<hr> +Node:<a name="gonk">gonk</a>, Next:<a rel="next" href="#gonkulator">gonkulator</a>, Previous:<a rel="previous" href="#golfballprinter">golf-ball printer</a>, Up:<a rel="up" +href="#chap07">= G =</a> <br> + + +<p><b>gonk</b> /gonk/ vi.,n.</p> + +<p>1. To prevaricate or to embellish the truth beyond any +reasonable recognition. In German the term is (mythically) +`gonken'; in Spanish the verb becomes `gonkar'. "You're gonking +me. That story you just told me is a bunch of gonk." In German, +for example, "Du gonkst mich" (You're pulling my leg). See also +<b><a href="#gonkulator">gonkulator</a></b>. 2. [British] To grab +some sleep at an odd time; compare <b><a href="#gronkout">gronk out</a></b>.</p> + +<hr> +Node:<a name="gonkulator">gonkulator</a>, Next:<a rel="next" +href="#gonzo">gonzo</a>, Previous:<a rel="previous" href="#gonk">gonk</a>, Up:<a rel="up" href="#chap07">= G =</a> +<br> + + +<p><b>gonkulator</b> /gon'kyoo-lay-tr/ n.</p> + +<p>[common; from the 1960s "Hogan's Heroes" TV series] A +pretentious piece of equipment that actually serves no useful +purpose. Usually used to describe one's least favorite piece of +computer hardware. See <b><a href="#gonk">gonk</a></b>.</p> + +<hr> +Node:<a name="gonzo">gonzo</a>, Next:<a rel="next" href="#GoodThing">Good Thing</a>, Previous:<a rel="previous" href="#gonkulator">gonkulator</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>gonzo</b> /gon'zoh/ adj.</p> + +<p>[from Hunter S. Thompson] 1. With total commitment, total +concentration, and a mad sort of panache. (Thompson's original +sense.) 2. More loosely: Overwhelming; outrageous; over the top; +very large, esp. used of collections of source code, source +files, or individual functions. Has some of the connotations of +<b><a href="#moby">moby</a></b> and <b><a href="#hairy">hairy</a></b>, but without the implication of obscurity +or complexity.</p> + +<hr> +Node:<a name="GoodThing">Good Thing</a>, Next:<a rel="next" +href="#gopher">gopher</a>, Previous:<a rel="previous" href="#gonzo">gonzo</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>Good Thing</b> n.,adj.</p> + +<p>[very common; often capitalized; always pronounced as if +capitalized.] 1. Self-evidently wonderful to anyone in a position +to notice: "A language that manages dynamic memory automatically +for you is a Good Thing." 2. Something that can't possibly have +any ill side-effects and may save considerable grief later: +"Removing the self-modifying code from that shared library would +be a Good Thing." 3. When said of software tools or libraries, as +in "YACC is a Good Thing", specifically connotes that the thing +has drastically reduced a programmer's work load. Oppose <b><a +href="#BadThing">Bad Thing</a></b>.</p> + +<hr> +Node:<a name="gopher">gopher</a>, Next:<a rel="next" href="#gopherhole">gopher hole</a>, Previous:<a rel="previous" +href="#GoodThing">Good Thing</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>gopher</b> n.</p> + +<p>A type of Internet service first floated around 1991 and +obsolesced around 1995 by the World Wide Web. Gopher presents a +menuing interface to a tree or graph of links; the links can be +to documents, runnable programs, or other gopher menus +arbitrarily far across the net.</p> + +<p>Some claim that the gopher software, which was originally +developed at the University of Minnesota, was named after the +Minnesota Gophers (a sports team). Others claim the word derives +from American slang `gofer' (from "go for", dialectal "go fer"), +one whose job is to run and fetch things. Finally, observe that +gophers dig long tunnels, and the idea of tunneling through the +net to find information was a defining metaphor for the +developers. Probably all three things were true, but with the +first two coming first and the gopher-tunnel metaphor +serendipitously adding flavor and impetus to the project as it +developed out of its concept stage.</p> + +<hr> +Node:<a name="gopherhole">gopher hole</a>, Next:<a rel="next" +href="#gorets">gorets</a>, Previous:<a rel="previous" href="#gopher">gopher</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>gopher hole</b> n.</p> + +<p>1. Any access to a <b><a href="#gopher">gopher</a></b>. 2. +[Amateur Packet Radio] The terrestrial analog of a <b><a href="#wormhole">wormhole</a></b> (sense 2), from which this term was +coined. A gopher hole links two amateur packet relays through +some non-ham radio medium.</p> + +<hr> +Node:<a name="gorets">gorets</a>, Next:<a rel="next" href="#gorillaarm">gorilla arm</a>, Previous:<a rel="previous" +href="#gopherhole">gopher hole</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>gorets</b> /gor'ets/ n.</p> + +<p>The unknown ur-noun, fill in your own meaning. Found esp. on +the Usenet newsgroup <i>alt.gorets</i>, which seems to be a +running contest to redefine the word by implication in the +funniest and most peculiar way, with the understanding that no +definition is ever final. [A correspondent from the Former Soviet +Union informs me that `gorets' is Russian for `mountain dweller'. +Another from France informs me that `goret' is archaic French for +a young pig --ESR] Compare <b><a href="#frink">frink</a></b>.</p> + +<hr> +Node:<a name="gorillaarm">gorilla arm</a>, Next:<a rel="next" +href="#gorp">gorp</a>, Previous:<a rel="previous" href="#gorets">gorets</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>gorilla arm</b> n.</p> + +<p>The side-effect that destroyed touch-screens as a mainstream +input technology despite a promising start in the early 1980s. It +seems the designers of all those <b><a href="#spiffy">spiffy</a></b> touch-menu systems failed to notice that +humans aren't designed to hold their arms in front of their faces +making small motions. After more than a very few selections, the +arm begins to feel sore, cramped, and oversized -- the operator +looks like a gorilla while using the touch screen and feels like +one afterwards. This is now considered a classic cautionary tale +to human-factors designers; "Remember the gorilla arm!" is +shorthand for "How is this going to fly in <i>real</i> +use?".</p> + +<hr> +Node:<a name="gorp">gorp</a>, Next:<a rel="next" href="#GOSMACS">GOSMACS</a>, Previous:<a rel="previous" href="#gorillaarm">gorilla arm</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>gorp</b> /gorp/ n.</p> + +<p>[CMU: perhaps from the canonical hiker's food, Good Old +Raisins and Peanuts] Another <b><a href="#metasyntacticvariable">metasyntactic variable</a></b>, like +<b><a href="#foo">foo</a></b> and <b><a href="#bar">bar</a></b>.</p> + +<hr> +Node:<a name="GOSMACS">GOSMACS</a>, Next:<a rel="next" href="#Gosperism">Gosperism</a>, Previous:<a rel="previous" href="#gorp">gorp</a>, Up:<a rel="up" href="#chap07">= G =</a> +<br> + + +<p><b>GOSMACS</b> /goz'maks/ n.</p> + +<p>[contraction of `Gosling EMACS'] The first <b><a href="#EMACS">EMACS</a></b>-in-C implementation, predating but now +largely eclipsed by <b><a href="#GNUMACS">GNUMACS</a></b>. +Originally freeware; a commercial version was modestly popular as +`UniPress EMACS' during the 1980s. The author, James Gosling, +went on to invent <b><a href="#NeWS">NeWS</a></b> and the +programming language Java; the latter earned him <b><a href="#demigod">demigod</a></b> status.</p> + +<hr> +Node:<a name="Gosperism">Gosperism</a>, Next:<a rel="next" href="#gotcha">gotcha</a>, Previous:<a rel="previous" href="#GOSMACS">GOSMACS</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>Gosperism</b> /gos'p*r-izm/ n.</p> + +<p>A hack, invention, or saying due to <b><a href="#elderdays">elder days</a></b> arch-hacker R. William (Bill) +Gosper. This notion merits its own term because there are so many +of them. Many of the entries in <b><a href="#HAKMEM">HAKMEM</a></b> are Gosperisms; see also <b><a href="#life">life</a></b>.</p> + +<hr> +Node:<a name="gotcha">gotcha</a>, Next:<a rel="next" href="#GPL">GPL</a>, Previous:<a rel="previous" href="#Gosperism">Gosperism</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>gotcha</b> n.</p> + +<p>A <b><a href="#misfeature">misfeature</a></b> of a system, +especially a programming language or environment, that tends to +breed bugs or mistakes because it both enticingly easy to invoke +and completely unexpected and/or unreasonable in its outcome. For +example, a classic gotcha in <b><a href="#C">C</a></b> is the +fact that <code>if (a=b) {code;}</code> is syntactically valid +and sometimes even correct. It puts the value of <code>b</code> +into <code>a</code> and then executes <code>code</code> if +<code>a</code> is non-zero. What the programmer probably meant +was <code>if (a==b) {code;}</code>, which executes +<code>code</code> if <code>a</code> and <code>b</code> are +equal.</p> + +<hr> +Node:<a name="GPL">GPL</a>, Next:<a rel="next" href="#GPV">GPV</a>, Previous:<a rel="previous" href="#gotcha">gotcha</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>GPL</b> /G-P-L/ n.</p> + +<p>Abbreviation for `General Public License' in widespread use; +see <b><a href="#copyleft">copyleft</a></b>, <b><a href="#GeneralPublicVirus">General Public Virus</a></b>. Often +mis-expanded as `GNU Public License'.</p> + +<hr> +Node:<a name="GPV">GPV</a>, Next:<a rel="next" href="#grault">grault</a>, Previous:<a rel="previous" href="#GPL">GPL</a>, Up:<a rel="up" href="#chap07">= G =</a> +<br> + + +<p><b>GPV</b> /G-P-V/ n.</p> + +<p>Abbrev. for <b><a href="#GeneralPublicVirus">General +Public Virus</a></b> in widespread use.</p> + +<hr> +Node:<a name="grault">grault</a>, Next:<a rel="next" href="#graygoo">gray goo</a>, Previous:<a rel="previous" href="#GPV">GPV</a>, Up:<a rel="up" href="#chap07">= G =</a> +<br> + + +<p><b>grault</b> /grawlt/ n.</p> + +<p>Yet another <b><a href="#metasyntacticvariable">metasyntactic variable</a></b>, +invented by Mike Gallaher and propagated by the <b><a href="#GOSMACS">GOSMACS</a></b> documentation. See <b><a href="#corge">corge</a></b>.</p> + +<hr> +Node:<a name="graygoo">gray goo</a>, Next:<a rel="next" href="#GreatRenaming">Great Renaming</a>, Previous:<a rel="previous" href="#grault">grault</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>gray goo</b> n.</p> + +<p>A hypothetical substance composed of <b><a href="#sagan">sagan</a></b>s of sub-micron-sized self-replicating +robots programmed to make copies of themselves out of whatever is +available. The image that goes with the term is one of the entire +biosphere of Earth being eventually converted to robot goo. This +is the simplest of the <b><a href="#nanotechnology">nanotechnology</a></b> disaster scenarios, +easily refuted by arguments from energy requirements and +elemental abundances. Compare <b><a href="#bluegoo">blue +goo</a></b>.</p> + +<hr> +Node:<a name="GreatRenaming">Great Renaming</a>, Next:<a rel="next" href="#GreatRunes">Great Runes</a>, Previous:<a rel="previous" href="#graygoo">gray goo</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>Great Renaming</b> n.</p> + +<p>The <b><a href="#flagday">flag day</a></b> in 1987 on which +all of the non-local groups on the <b><a href="#Usenet">Usenet</a></b> had their names changed from the net.- +format to the current multiple-hierarchies scheme. Used esp. in +discussing the history of newsgroup names. "The oldest sources +group is <i>comp.sources.misc</i>; before the Great Renaming, it +was <i>net.sources</i>." There is a Great Renaming +FAQ on the Web.</p> + +<hr> +Node:<a name="GreatRunes">Great Runes</a>, Next:<a rel="next" +href="#GreatWorm">Great Worm</a>, Previous:<a rel="previous" +href="#GreatRenaming">Great Renaming</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>Great Runes</b> n.</p> + +<p>Uppercase-only text or display messages. Some archaic +operating systems still emit these. See also <b><a href="#runes">runes</a></b>, <b><a href="#smashcase">smash +case</a></b>, <b><a href="#foldcase">fold case</a></b>.</p> + +<p>There is a widespread legend (repeated by earlier versions of +this entry, though tagged as folklore) that the uppercase-only +support of various old character codes and I/O equipment was +chosen by a religious person in a position of power at the +Teletype Company because supporting both upper and lower cases +was too expensive and supporting lower case only would have made +it impossible to spell `God' correctly. Not true; the upper-case +interpretation of teleprinter codes was well established by 1870, +long before Teletype was even founded.</p> + +<hr> +Node:<a name="GreatWorm">Great Worm</a>, Next:<a rel="next" +href="#great-wall">great-wall</a>, Previous:<a rel="previous" +href="#GreatRunes">Great Runes</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>Great Worm</b> n.</p> + +<p>The 1988 Internet <b><a href="#worm">worm</a></b> perpetrated +by <b><a href="#RTM">RTM</a></b>. This is a play on Tolkien +(compare <b><a href="#elvish">elvish</a></b>, <b><a href="#elderdays">elder days</a></b>). In the fantasy history of +his Middle Earth books, there were dragons powerful enough to lay +waste to entire regions; two of these (Scatha and Glaurung) were +known as "the Great Worms". This usage expresses the connotation +that the RTM crack was a sort of devastating watershed event in +hacker history; certainly it did more to make non-hackers nervous +about the Internet than anything before or since.</p> + +<hr> +Node:<a name="great-wall">great-wall</a>, Next:<a rel="next" +href="#GreenBook">Green Book</a>, Previous:<a rel="previous" +href="#GreatWorm">Great Worm</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>great-wall</b> vi.,n.</p> + +<p>[from SF fandom] A mass expedition to an oriental restaurant, +esp. one where food is served family-style and shared. There is a +common heuristic about the amount of food to order, expressed as +"Get N - 1 entrees"; the value of N, which is the number of +people in the group, can be inferred from context (see <b><a +href="#N">N</a></b>). See <b><a href="#orientalfood">oriental +food</a></b>, <b><a href="#ravs">ravs</a></b>, <b><a href="#stirfriedrandom">stir-fried random</a></b>.</p> + +<hr> +Node:<a name="GreenBook">Green Book</a>, Next:<a rel="next" +href="#greenbytes">green bytes</a>, Previous:<a rel="previous" +href="#great-wall">great-wall</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>Green Book</b> n.</p> + +<p>1. One of the three standard <b><a href="#PostScript">PostScript</a></b> references: "PostScript Language +Program Design", bylined `Adobe Systems' (Addison-Wesley, 1988; +QA76.73.P67P66 ISBN 0-201-14396-8); see also <b><a href="#RedBook">Red Book</a></b>, <b><a href="#BlueBook">Blue +Book</a></b>, and the <b><a href="#WhiteBook">White +Book</a></b> (sense 2). 2. Informal name for one of the three +standard references on SmallTalk: "Smalltalk-80: Bits of History, +Words of Advice", by Glenn Krasner (Addison-Wesley, 1983; +QA76.8.S635S58; ISBN 0-201-11669-3) (this, too, is associated +with blue and red books). 3. The "X/Open Compatibility Guide", +which defines an international standard <b><a href="#Unix">Unix</a></b> environment that is a proper superset of +POSIX/SVID; also includes descriptions of a standard utility +toolkit, systems administrations features, and the like. This +grimoire is taken with particular seriousness in Europe. See +<b><a href="#PurpleBook">Purple Book</a></b>. 4. The IEEE +1003.1 POSIX Operating Systems Interface standard has been dubbed +"The Ugly Green Book". 5. Any of the 1992 standards issued by the +CCITT's tenth plenary assembly. These include, among other +things, the X.400 email standard and the Group 1 through 4 fax +standards. See also <b><a href="#booktitles">book +titles</a></b>.</p> + +<hr> +Node:<a name="greenbytes">green bytes</a>, Next:<a rel="next" +href="#greencard">green card</a>, Previous:<a rel="previous" +href="#GreenBook">Green Book</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>green bytes</b> n.</p> + +<p>(also `green words') 1. Meta-information embedded in a file, +such as the length of the file or its name; as opposed to keeping +such information in a separate description file or record. The +term comes from an IBM user's group meeting (ca. 1962) at which +these two approaches were being debated and the diagram of the +file on the blackboard had the `green bytes' drawn in green. 2. +By extension, the non-data bits in any self-describing format. "A +GIF file contains, among other things, green bytes describing the +packing method for the image." Compare <b><a href="#out-of-band">out-of-band</a></b>, <b><a href="#zigamorph">zigamorph</a></b>, <b><a href="#fence">fence</a></b> +(sense 1).</p> + +<hr> +Node:<a name="greencard">green card</a>, Next:<a rel="next" +href="#greenlightning">green lightning</a>, Previous:<a rel="previous" href="#greenbytes">green bytes</a>, Up:<a rel="up" +href="#chap07">= G =</a> <br> + + +<p><b>green card</b> n.</p> + +<p>[after the "IBM System/360 Reference Data" card] A summary of +an assembly language, even if the color is not green and not a +card. Less frequently used now because of the decrease in the use +of assembly language. "I'll go get my green card so I can check +the addressing mode for that instruction."</p> + +<p>The original green card became a yellow card when the +System/370 was introduced, and later a yellow booklet. An +anecdote from IBM refers to a scene that took place in a +programmers' terminal room at Yorktown in 1978. A <b><a href="#luser">luser</a></b> overheard one of the programmers ask +another "Do you have a green card?" The other grunted and passed +the first a thick yellow booklet. At this point the luser turned +a delicate shade of olive and rapidly left the room, never to +return.</p> + +<p>In fall 2000 it was reported from Electronic Data Systems that +the green card for 370 machines has been a blue-green booklet +since 1989.</p> + +<hr> +Node:<a name="greenlightning">green lightning</a>, Next:<a +rel="next" href="#greenmachine">green machine</a>, Previous:<a +rel="previous" href="#greencard">green card</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>green lightning</b> n.</p> + +<p>[IBM] 1. Apparently random flashing streaks on the face of +3278-9 terminals while a new symbol set is being downloaded. This +hardware bug was left deliberately unfixed, as some genius within +IBM suggested it would let the user know that `something is +happening'. That, it certainly does. Later microprocessor-driven +IBM color graphics displays were actually <i>programmed</i> to +produce green lightning! 2. [proposed] Any bug perverted into an +alleged feature by adroit rationalization or marketing. "Motorola +calls the CISC cruft in the 88000 architecture `compatibility +logic', but I call it green lightning". See also <b><a href="#feature">feature</a></b> (sense 6).</p> + +<hr> +Node:<a name="greenmachine">green machine</a>, Next:<a rel="next" href="#GreensTheorem">Green's Theorem</a>, Previous:<a +rel="previous" href="#greenlightning">green lightning</a>, +Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>green machine</b> n.</p> + +<p>A computer or peripheral device that has been designed and +built to military specifications for field equipment (that is, to +withstand mechanical shock, extremes of temperature and humidity, +and so forth). Comes from the olive-drab `uniform' paint used for +military equipment.</p> + +<hr> +Node:<a name="GreensTheorem">Green's Theorem</a>, Next:<a +rel="next" href="#greenbar">greenbar</a>, Previous:<a rel="previous" href="#greenmachine">green machine</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>Green's Theorem</b> prov.</p> + +<p>[TMRC] For any story, in any group of people there will be at +least one person who has not heard the story. A refinement of the +theorem states that there will be <i>exactly</i> one person (if +there were more than one, it wouldn't be as bad to re-tell the +story). [The name of this theorem is a play on a fundamental +theorem in calculus. --ESR]</p> + +<hr> +Node:<a name="greenbar">greenbar</a>, Next:<a rel="next" href="#grep">grep</a>, Previous:<a rel="previous" href="#GreensTheorem">Green's Theorem</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>greenbar</b> n.</p> + +<p>A style of fanfolded continuous-feed paper with alternating +green and white bars on it, especially used in old-style line +printers. This slang almost certainly dates way back to mainframe +days.</p> + +<hr> +Node:<a name="grep">grep</a>, Next:<a rel="next" href="#gribble">gribble</a>, Previous:<a rel="previous" href="#greenbar">greenbar</a>, Up:<a rel="up" href="#chap07">= +G =</a> <br> + + +<p><b>grep</b> /grep/ vi.</p> + +<p>[from the qed/ed editor idiom g/<i>re</i>/p, where <i>re</i> +stands for a regular expression, to Globally search for the +Regular Expression and Print the lines containing matches to it, +via <b><a href="#Unix">Unix</a></b> <code>grep(1)</code>] To +rapidly scan a file or set of files looking for a particular +string or pattern (when browsing through a large set of files, +one may speak of `grepping around'). By extension, to look for +something by pattern. "Grep the bulletin board for the system +backup schedule, would you?" See also <b><a href="#vgrep">vgrep</a></b>.</p> + +<p>[It has also been alleged that the source is from the title of +a paper "A General Regular Expression Parser" -ESR]</p> + +<hr> +Node:<a name="gribble">gribble</a>, Next:<a rel="next" href="#grilf">grilf</a>, Previous:<a rel="previous" href="#grep">grep</a>, Up:<a rel="up" href="#chap07">= G =</a> +<br> + + +<p><b>gribble</b> n.</p> + +<p>Random binary data rendered as unreadable text. Noise +characters in a data stream are displayed as gribble. Modems with +mismatched bitrates usually generate gribble (more specifically, +<b><a href="#baudbarf">baud barf</a></b>). Dumping a binary +file to the screen is an excellent source of gribble, and (if the +bell/speaker is active) headaches.</p> + +<hr> +Node:<a name="grilf">grilf</a>, Next:<a rel="next" href="#grind">grind</a>, Previous:<a rel="previous" href="#gribble">gribble</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>grilf</b> // n.</p> + +<p>Girlfriend. Like <b><a href="#newsfroup">newsfroup</a></b> and +<b><a href="#filk">filk</a></b>, a typo reincarnated as a new +word. Seems to have originated sometime in 1992 on <b><a href="#Usenet">Usenet</a></b>. [A friend tells me there was a Lloyd +Biggle SF novel "Watchers Of The Dark", in which alien species +after species goes insane and begins to chant "Grilf! Grilf!". A +human detective eventually determines that the word means "Liar!" +I hope this has nothing to do with the popularity of the Usenet +term. --ESR]</p> + +<hr> +Node:<a name="grind">grind</a>, Next:<a rel="next" href="#grindcrank">grind crank</a>, Previous:<a rel="previous" +href="#grilf">grilf</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>grind</b> vt.</p> + +<p>1. [MIT and Berkeley; now rare] To prettify hardcopy of code, +especially LISP code, by reindenting lines, printing keywords and +comments in distinct fonts (if available), etc. This usage was +associated with the MacLISP community and is now rare; +<b>prettyprint</b> was and is the generic term for such +operations. 2. [Unix] To generate the formatted version of a +document from the <b><a href="#nroff">nroff</a></b>, <b><a href="#troff">troff</a></b>, <b><a href="#TeX">TeX</a></b>, or Scribe +source. 3. [common] To run seemingly interminably, esp. (but not +necessarily) if performing some tedious and inherently useless +task. Similar to <b><a href="#crunch">crunch</a></b> or <b><a +href="#grovel">grovel</a></b>. Grinding has a connotation of +using a lot of CPU time, but it is possible to grind a disk, +network, etc. See also <b><a href="#hog">hog</a></b>. 4. To make +the whole system slow. "Troff really grinds a PDP-11." 5. `grind +grind' excl. Roughly, "Isn't the machine slow today!"</p> + +<hr> +Node:<a name="grindcrank">grind crank</a>, Next:<a rel="next" +href="#gripenet">gripenet</a>, Previous:<a rel="previous" href="#grind">grind</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>grind crank</b> n. //</p> + +<p>A mythical accessory to a terminal. A crank on the side of a +monitor, which when operated makes a zizzing noise and causes the +computer to run faster. Usually one does not refer to a grind +crank out loud, but merely makes the appropriate gesture and +noise. See <b><a href="#grind">grind</a></b>.</p> + +<p>Historical note: At least one real machine actually had a +grind crank -- the R1, a research machine built toward the end of +the days of the great vacuum tube computers, in 1959. R1 (also +known as `The Rice Institute Computer' (TRIC) and later as `The +Rice University Computer' (TRUC)) had a single-step/free-run +switch for use when debugging programs. Since single-stepping +through a large program was rather tedious, there was also a +crank with a cam and gear arrangement that repeatedly pushed the +single-step button. This allowed one to `crank' through a lot of +code, then slow down to single-step for a bit when you got near +the code of interest, poke at some registers using the console +typewriter, and then keep on cranking.</p> + +<hr> +Node:<a name="gripenet">gripenet</a>, Next:<a rel="next" href="#gritch">gritch</a>, Previous:<a rel="previous" href="#grindcrank">grind crank</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>gripenet</b> n.</p> + +<p>[IBM] A wry (and thoroughly unofficial) name for IBM's +internal VNET system, deriving from its common use by IBMers to +voice pointed criticism of IBM management that would be taboo in +more formal channels.</p> + +<hr> +Node:<a name="gritch">gritch</a>, Next:<a rel="next" href="#grok">grok</a>, Previous:<a rel="previous" href="#gripenet">gripenet</a>, Up:<a rel="up" href="#chap07">= +G =</a> <br> + + +<p><b>gritch</b> /grich/</p> + +<p>[MIT] 1. n. A complaint (often caused by a <b><a href="#glitch">glitch</a></b>). 2. vi. To complain. Often +verb-doubled: "Gritch gritch". 3. A synonym for <b><a href="#glitch">glitch</a></b> (as verb or noun).</p> + +<p>Interestingly, this word seems to have a separate history from +<b><a href="#glitch">glitch</a></b>, with which it is often +confused. Back in the early 1960s, when `glitch' was strictly a +hardware-tech's term of art, the Burton House dorm at M.I.T. +maintained a "Gritch Book", a blank volume, into which the +residents hand-wrote complaints, suggestions, and witticisms. +Previous years' volumes of this tradition were maintained, dating +back to antiquity. The word "gritch" was described as a +portmanteau of "gripe" and "bitch". Thus, sense 3 above is at +least historically incorrect.</p> + +<hr> +Node:<a name="grok">grok</a>, Next:<a rel="next" href="#gronk">gronk</a>, Previous:<a rel="previous" href="#gritch">gritch</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>grok</b> /grok/, var. /grohk/ vt.</p> + +<p>[from the novel "Stranger in a Strange Land", by Robert A. +Heinlein, where it is a Martian word meaning literally `to drink' +and metaphorically `to be one with'] The emphatic form is `grok +in fullness'. 1. To understand, usually in a global sense. +Connotes intimate and exhaustive knowledge. Contrast <b><a href="#zen">zen</a></b>, which is similar supernal understanding +experienced as a single brief flash. See also <b><a href="#glark">glark</a></b>. 2. Used of programs, may connote merely +sufficient understanding. "Almost all C compilers grok the +<code>void</code> type these days."</p> + +<hr> +Node:<a name="gronk">gronk</a>, Next:<a rel="next" href="#gronkout">gronk out</a>, Previous:<a rel="previous" href="#grok">grok</a>, Up:<a rel="up" href="#chap07">= G =</a> +<br> + + +<p><b>gronk</b> /gronk/ vt.</p> + +<p>[popularized by Johnny Hart's comic strip "B.C." but the word +apparently predates that] 1. To clear the state of a wedged +device and restart it. More severe than `to <b><a href="#frob">frob</a></b>' (sense 2). 2. [TMRC] To cut, sever, smash, +or similarly disable. 3. The sound made by many 3.5-inch diskette +drives. In particular, the microfloppies on a Commodore Amiga go +"grink, gronk".</p> + +<hr> +Node:<a name="gronkout">gronk out</a>, Next:<a rel="next" +href="#gronked">gronked</a>, Previous:<a rel="previous" href="#gronk">gronk</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>gronk out</b> vi.</p> + +<p>To cease functioning. Of people, to go home and go to sleep. +"I guess I'll gronk out now; see you all tomorrow."</p> + +<hr> +Node:<a name="gronked">gronked</a>, Next:<a rel="next" href="#grovel">grovel</a>, Previous:<a rel="previous" href="#gronkout">gronk out</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>gronked</b> adj.</p> + +<p>1. Broken. "The teletype scanner was gronked, so we took the +system down." 2. Of people, the condition of feeling very tired +or (less commonly) sick. "I've been chasing that bug for 17 hours +now and I am thoroughly gronked!" Compare <b><a href="#broken">broken</a></b>, which means about the same as <b><a +href="#gronk">gronk</a></b> used of hardware, but connotes +depression or mental/emotional problems in people.</p> + +<hr> +Node:<a name="grovel">grovel</a>, Next:<a rel="next" href="#grue">grue</a>, Previous:<a rel="previous" href="#gronked">gronked</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>grovel</b> vi.</p> + +<p>1. To work interminably and without apparent progress. Often +used transitively with `over' or `through'. "The file scavenger +has been groveling through the /usr directories for 10 minutes +now." Compare <b><a href="#grind">grind</a></b> and <b><a href="#crunch">crunch</a></b>. Emphatic form: `grovel obscenely'. 2. +To examine minutely or in complete detail. "The compiler grovels +over the entire source program before beginning to translate it." +"I grovelled through all the documentation, but I still couldn't +find the command I wanted."</p> + +<hr> +Node:<a name="grue">grue</a>, Next:<a rel="next" href="#grunge">grunge</a>, Previous:<a rel="previous" href="#grovel">grovel</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>grue</b> n.</p> + +<p>[from archaic English verb for `shudder', as with fear] The +grue was originated in the game <b><a href="#Zork">Zork</a></b> +(Dave Lebling took the name from Jack Vance's "Dying Earth" +fantasies) and used in several other <b><a href="#Infocom">Infocom</a></b> games as a hint that you should +perhaps look for a lamp, torch or some type of light source. +Wandering into a dark area would cause the game to prompt you, +"It is very dark. If you continue you are likely to be eaten by a +grue." If you failed to locate a light source within the next +couple of moves this would indeed be the case.</p> + +<p>The grue, according to scholars of the Great Underground +Empire, is a sinister, lurking presence in the dark places of the +earth. Its favorite diet is either adventurers or enchanters, but +its insatiable appetite is tempered by its extreme fear of light. +No grues have ever been seen by the light of day, and only a few +have been observed in their underground lairs. Of those who have +seen grues, few have survived their fearsome jaws to tell the +tale. Grues have sharp claws and fangs, and an uncontrollable +tendency to slaver and gurgle. They are certainly the most +evil-tempered of all creatures; to say they are touchy is a +dangerous understatement. "Sour as a grue" is a common +expression, even among themselves.</p> + +<p>All this folklore is widely known among hackers.</p> + +<hr> +Node:<a name="grunge">grunge</a>, Next:<a rel="next" href="#gubbish">gubbish</a>, Previous:<a rel="previous" href="#grue">grue</a>, Up:<a rel="up" href="#chap07">= G =</a> +<br> + + +<p><b>grunge</b> /gruhnj/ n.</p> + +<p>1. That which is grungy, or that which makes it so. 2. +[Cambridge] Code which is inaccessible due to changes in other +parts of the program. The preferred term in North America is +<b><a href="#deadcode">dead code</a></b>.</p> + +<hr> +Node:<a name="gubbish">gubbish</a>, Next:<a rel="next" href="#Guido">Guido</a>, Previous:<a rel="previous" href="#grunge">grunge</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>gubbish</b> /guhb'*sh/ n.</p> + +<p>[a portmanteau of `garbage' and `rubbish'; may have originated +with SF author Philip K. Dick] Garbage; crap; nonsense. "What is +all this gubbish?" The opposite portmanteau `rubbage' is also +reported; in fact, it was British slang during the 19th century +and appears in Dickens.</p> + +<hr> +Node:<a name="Guido">Guido</a>, Next:<a rel="next" href="#guiltware">guiltware</a>, Previous:<a rel="previous" href="#gubbish">gubbish</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>Guido</b> /gwee'do/ or /khwee'do/</p> + +<p>Without qualification, Guido van Rossum (author of <b><a href="#Python">Python</a></b>). Note that Guido answers to English +/gwee'do/ but in Dutch it's /khwee'do/.</p> + +<hr> +Node:<a name="guiltware">guiltware</a>, Next:<a rel="next" href="#gumby">gumby</a>, Previous:<a rel="previous" href="#Guido">Guido</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>guiltware</b> /gilt'weir/ n.</p> + +<p>1. A piece of <b><a href="#freeware">freeware</a></b> +decorated with a message telling one how long and hard the author +worked on it and intimating that one is a no-good freeloader if +one does not immediately send the poor suffering martyr gobs of +money. 2. A piece of <b><a href="#shareware">shareware</a></b> +that works.</p> + +<hr> +Node:<a name="gumby">gumby</a>, Next:<a rel="next" href="#gun">gun</a>, Previous:<a rel="previous" href="#guiltware">guiltware</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>gumby</b> /guhm'bee/ n.</p> + +<p>[from a class of Monty Python characters, poss. with some +influence from the 1960s claymation character] 1. An act of minor +but conspicuous stupidity, often in `gumby maneuver' or `pull a +gumby'. 2. [NRL] n. A bureaucrat, or other technical incompetent +who impedes the progress of real work. 3. adj. Relating to things +typically associated with people in sense 2. (e.g. "Ran would be +writing code, but Richard gave him gumby work that's due on +Friday", or, "Dammit! Travel screwed up my plane tickets. I have +to go out on gumby patrol.")</p> + +<hr> +Node:<a name="gun">gun</a>, Next:<a rel="next" href="#gunch">gunch</a>, Previous:<a rel="previous" href="#gumby">gumby</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>gun</b> vt.</p> + +<p>[ITS, now rare: from the <code>:GUN</code> command] To +forcibly terminate a program or job (computer, not career). "Some +idiot left a background process running soaking up half the +cycles, so I gunned it." Usage: now rare. Compare <b><a href="#can">can</a></b>, <b><a href="#blammo">blammo</a></b>.</p> + +<hr> +Node:<a name="gunch">gunch</a>, Next:<a rel="next" href="#gunpowderchicken">gunpowder chicken</a>, Previous:<a rel="previous" href="#gun">gun</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>gunch</b> /guhnch/ vt.</p> + +<p>[TMRC] To push, prod, or poke at a device that has almost (but +not quite) produced the desired result. Implies a threat to <b><a +href="#mung">mung</a></b>.</p> + +<hr> +Node:<a name="gunpowderchicken">gunpowder chicken</a>, Next:<a +rel="next" href="#gurfle">gurfle</a>, Previous:<a rel="previous" +href="#gunch">gunch</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>gunpowder chicken</b> n.</p> + +<p>Same as <b><a href="#laserchicken">laser +chicken</a></b>.</p> + +<hr> +Node:<a name="gurfle">gurfle</a>, Next:<a rel="next" href="#guru">guru</a>, Previous:<a rel="previous" href="#gunpowderchicken">gunpowder chicken</a>, Up:<a rel="up" +href="#chap07">= G =</a> <br> + + +<p><b>gurfle</b> /ger'fl/ interj.</p> + +<p>An expression of shocked disbelief. "He said we have to recode +this thing in FORTRAN by next week. Gurfle!" Compare <b><a href="#weeble">weeble</a></b>.</p> + +<hr> +Node:<a name="guru">guru</a>, Next:<a rel="next" href="#gurumeditation">guru meditation</a>, Previous:<a rel="previous" href="#gurfle">gurfle</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>guru</b> n.</p> + +<p>[Unix] An expert. Implies not only <b><a href="#wizard">wizard</a></b> skill but also a history of being a +knowledge resource for others. Less often, used (with a +qualifier) for other experts on other systems, as in `VMS guru'. +See <b><a href="#sourceofallgoodbits">source of all +good bits</a></b>.</p> + +<hr> +Node:<a name="gurumeditation">guru meditation</a>, Next:<a +rel="next" href="#gweep">gweep</a>, Previous:<a rel="previous" +href="#guru">guru</a>, Up:<a rel="up" href="#chap07">= G +=</a> <br> + + +<p><b>guru meditation</b> n.</p> + +<p>Amiga equivalent of `panic' in Unix (sometimes just called a +`guru' or `guru event'). When the system crashes, a cryptic +message of the form "GURU MEDITATION #XXXXXXXX.YYYYYYYY" may +appear, indicating what the problem was. An Amiga guru can figure +things out from the numbers. Sometimes a <b><a href="#guru">guru</a></b> event must be followed by a <b><a href="#Vulcannervepinch">Vulcan nerve pinch</a></b>.</p> + +<p>This term is (no surprise) an in-joke from the earliest days +of the Amiga. An earlier product of the Amiga corporation was a +device called a `Joyboard' which was basically a plastic board +built onto a joystick-like device; it was sold with a skiing game +cartridge for the Atari game machine. It is said that whenever +the prototype OS crashed, the system programmer responsible would +calm down by concentrating on a solution while sitting +cross-legged on a Joyboard trying to keep the board in balance. +This position resembled that of a meditating guru. Sadly, the +joke was removed fairly early on (but there's a well-known patch +to restore it in more recent versions).</p> + +<hr> +Node:<a name="gweep">gweep</a>, Next:<a rel="next" href="#h">h</a>, Previous:<a rel="previous" href="#gurumeditation">guru meditation</a>, Up:<a rel="up" href="#chap07">= G =</a> <br> + + +<p><b>gweep</b> /gweep/</p> + +<p>[WPI] 1. v. To <b><a href="#hack">hack</a></b>, usually at +night. At WPI, from 1975 onwards, one who gweeped could often be +found at the College Computing Center punching cards or crashing +the <b><a href="#PDP-10">PDP-10</a></b> or, later, the DEC-20. A +correspondent who was there at the time opines that the term was +originally onomatopoetic, describing the keyclick sound of the +Datapoint terminals long connected to the PDP-10. The term has +survived the demise of those technologies, however, and was still +alive in early 1999. "I'm going to go gweep for a while. See you +in the morning." "I gweep from 8 PM till 3 AM during the week." +2. n. One who habitually gweeps in sense 1; a <b><a href="#hacker">hacker</a></b>. "He's a hard-core gweep, mumbles code +in his sleep."</p> + +<hr> +Node:<a name="chap08">= H =</a>, Next:<a rel="next" href="#chap09">= I =</a>, Previous:<a rel="previous" href="#chap07">= G =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= H =</h2> + +<ul> +<li><a href="#h">h</a>:</li> + +<li><a href="#hahaonlyserious">ha ha only +serious</a>:</li> + +<li><a href="#hack">hack</a>:</li> + +<li><a href="#hackattack">hack attack</a>:</li> + +<li><a href="#hackmode">hack mode</a>:</li> + +<li><a href="#hackon">hack on</a>:</li> + +<li><a href="#hacktogether">hack together</a>:</li> + +<li><a href="#hackup">hack up</a>:</li> + +<li><a href="#hackvalue">hack value</a>:</li> + +<li><a href="#hackedoff">hacked off</a>:</li> + +<li><a href="#hackedup">hacked up</a>:</li> + +<li><a href="#hacker">hacker</a>:</li> + +<li><a href="#hackerethic">hacker ethic</a>:</li> + +<li><a href="#hackerhumor">hacker humor</a>:</li> + +<li><a href="#Hackersthemovie">Hackers (the +movie)</a>:</li> + +<li><a href="#hackingrun">hacking run</a>:</li> + +<li><a href="#HackingXforY">Hacking X for Y</a>:</li> + +<li><a href="#Hackintosh">Hackintosh</a>:</li> + +<li><a href="#hackish">hackish</a>:</li> + +<li><a href="#hackishness">hackishness</a>:</li> + +<li><a href="#hackitude">hackitude</a>:</li> + +<li><a href="#hair">hair</a>:</li> + +<li><a href="#hairball">hairball</a>:</li> + +<li><a href="#hairy">hairy</a>:</li> + +<li><a href="#HAKMEM">HAKMEM</a>:</li> + +<li><a href="#hakspek">hakspek</a>:</li> + +<li><a href="#HalloweenDocuments">Halloween +Documents</a>:</li> + +<li><a href="#hammer">hammer</a>:</li> + +<li><a href="#hamster">hamster</a>:</li> + +<li><a href="#HAND">HAND</a>:</li> + +<li><a href="#handcruft">hand cruft</a>:</li> + +<li><a href="#hand-hacking">hand-hacking</a>:</li> + +<li><a href="#handle">handle</a>:</li> + +<li><a href="#handle">handle</a>:</li> + +<li><a href="#hand-roll">hand-roll</a>:</li> + +<li><a href="#handshaking">handshaking</a>:</li> + +<li><a href="#handwave">handwave</a>:</li> + +<li><a href="#hang">hang</a>:</li> + +<li><a href="#HanlonsRazor">Hanlon's Razor</a>:</li> + +<li><a href="#happily">happily</a>:</li> + +<li><a href="#haque">haque</a>:</li> + +<li><a href="#hardboot">hard boot</a>:</li> + +<li><a href="#hardcoded">hardcoded</a>:</li> + +<li><a href="#hardwarily">hardwarily</a>:</li> + +<li><a href="#hardwired">hardwired</a>:</li> + +<li><a href="#hastheXnature">has the X nature</a>:</li> + +<li><a href="#hashbucket">hash bucket</a>:</li> + +<li><a href="#hashcollision">hash collision</a>:</li> + +<li><a href="#hat">hat</a>:</li> + +<li><a href="#HCF">HCF</a>:</li> + +<li><a href="#headsdown">heads down</a>:</li> + +<li><a href="#heartbeat">heartbeat</a>:</li> + +<li><a href="#heatseeker">heatseeker</a>:</li> + +<li><a href="#heavymetal">heavy metal</a>:</li> + +<li><a href="#heavywizardry">heavy wizardry</a>:</li> + +<li><a href="#heavyweight">heavyweight</a>:</li> + +<li><a href="#heisenbug">heisenbug</a>:</li> + +<li><a href="#HelenKellermode">Helen Keller mode</a>:</li> + +<li><a href="#hellosailor">hello sailor!</a>:</li> + +<li><a href="#hellowall">hello wall!</a>:</li> + +<li><a href="#helloworld">hello world</a>:</li> + +<li><a href="#hex">hex</a>:</li> + +<li><a href="#hexadecimal">hexadecimal</a>:</li> + +<li><a href="#hexit">hexit</a>:</li> + +<li><a href="#HHOK">HHOK</a>:</li> + +<li><a href="#HHOS">HHOS</a>:</li> + +<li><a href="#hiddenflag">hidden flag</a>:</li> + +<li><a href="#highBit">high bit</a>:</li> + +<li><a href="#highmoby">high moby</a>:</li> + +<li><a href="#highly">highly</a>:</li> + +<li><a href="#hing">hing</a>:</li> + +<li><a href="#hiredgun">hired gun</a>:</li> + +<li><a href="#hirsute">hirsute</a>:</li> + +<li><a href="#HLL">HLL</a>:</li> + +<li><a href="#hoarding">hoarding</a>:</li> + +<li><a href="#hobbit">hobbit</a>:</li> + +<li><a href="#hog">hog</a>:</li> + +<li><a href="#hole">hole</a>:</li> + +<li><a href="#hollised">hollised</a>:</li> + +<li><a href="#holywars">holy wars</a>:</li> + +<li><a href="#homebox">home box</a>:</li> + +<li><a href="#homemachine">home machine</a>:</li> + +<li><a href="#homePage">home page</a>:</li> + +<li><a href="#honeypot">honey pot</a>:</li> + +<li><a href="#hook">hook</a>:</li> + +<li><a href="#hop">hop</a>:</li> + +<li><a href="#hose">hose</a>:</li> + +<li><a href="#hosed">hosed</a>:</li> + +<li><a href="#hotchat">hot chat</a>:</li> + +<li><a href="#hotspot">hot spot</a>:</li> + +<li><a href="#hotlink">hotlink</a>:</li> + +<li><a href="#housewizard">house wizard</a>:</li> + +<li><a href="#HP-SUX">HP-SUX</a>:</li> + +<li><a href="#HTH">HTH</a>:</li> + +<li><a href="#huff">huff</a>:</li> + +<li><a href="#humma">humma</a>:</li> + +<li><a href="#hung">hung</a>:</li> + +<li><a href="#hungrypuppy">hungry puppy</a>:</li> + +<li><a href="#hungus">hungus</a>:</li> + +<li><a href="#hyperspace">hyperspace</a>:</li> + +<li><a href="#hystericalreasons">hysterical reasons</a>:</li> +</ul> + +<hr> +Node:<a name="h">h</a>, Next:<a rel="next" href="#hahaonlyserious">ha ha only serious</a>, Previous:<a +rel="previous" href="#gweep">gweep</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>h</b></p> + +<p>[from SF fandom] A method of `marking' common words, i.e., +calling attention to the fact that they are being used in a +nonstandard, ironic, or humorous way. Originated in the fannish +catchphrase "Bheer is the One True Ghod!" from decades ago. +H-infix marking of `Ghod' and other words spread into the 1960s +counterculture via underground comix, and into early hackerdom +either from the counterculture or from SF fandom (the three +overlapped heavily at the time). More recently, the h infix has +become an expected feature of benchmark names (Dhrystone, +Rhealstone, etc.); this is probably patterning on the original +Whetstone (the name of a laboratory) but influenced by the +fannish/counterculture h infix.</p> + +<hr> +Node:<a name="hahaonlyserious">ha ha only serious</a>, +Next:<a rel="next" href="#hack">hack</a>, Previous:<a rel="previous" href="#h">h</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>ha ha only serious</b></p> + +<p>[from SF fandom, orig. as mutation of HHOK, `Ha Ha Only +Kidding'] A phrase (often seen abbreviated as HHOS) that aptly +captures the flavor of much hacker discourse. Applied especially +to parodies, absurdities, and ironic jokes that are both intended +and perceived to contain a possibly disquieting amount of truth, +or truths that are constructed on in-joke and self-parody. This +lexicon contains many examples of ha-ha-only-serious in both form +and content. Indeed, the entirety of hacker culture is often +perceived as ha-ha-only-serious by hackers themselves; to take it +either too lightly or too seriously marks a person as an +outsider, a <b><a href="#wannabee">wannabee</a></b>, or in <b><a +href="#larvalstage">larval stage</a></b>. For further +enlightenment on this subject, consult any Zen master. See also +<b><a href="#hackerhumor">hacker humor</a></b>, and <b><a +href="#AIkoans">AI koans</a></b>.</p> + +<hr> +Node:<a name="hack">hack</a>, Next:<a rel="next" href="#hackattack">hack attack</a>, Previous:<a rel="previous" +href="#hahaonlyserious">ha ha only serious</a>, Up:<a +rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hack</b></p> + +<p>[very common] 1. n. Originally, a quick job that produces what +is needed, but not well. 2. n. An incredibly good, and perhaps +very time-consuming, piece of work that produces exactly what is +needed. 3. vt. To bear emotionally or physically. "I can't hack +this heat!" 4. vt. To work on something (typically a program). In +an immediate sense: "What are you doing?" "I'm hacking TECO." In +a general (time-extended) sense: "What do you do around here?" "I +hack TECO." More generally, "I hack `foo'" is roughly equivalent +to "`foo' is my major interest (or project)". "I hack solid-state +physics." See <b><a href="#HackingXforY">Hacking X for +Y</a></b>. 5. vt. To pull a prank on. See sense 2 and <b><a href="#hacker">hacker</a></b> (sense 5). 6. vi. To interact with a +computer in a playful and exploratory rather than goal-directed +way. "Whatcha up to?" "Oh, just hacking." 7. n. Short for <b><a +href="#hacker">hacker</a></b>. 8. See <b><a href="#nethack">nethack</a></b>. 9. [MIT] v. To explore the basements, +roof ledges, and steam tunnels of a large, institutional +building, to the dismay of Physical Plant workers and (since this +is usually performed at educational institutions) the Campus +Police. This activity has been found to be eerily similar to +playing adventure games such as Dungeons and Dragons and <b><a +href="#Zork">Zork</a></b>. See also <b><a href="#vadding">vadding</a></b>.</p> + +<p>Constructions on this term abound. They include `happy +hacking' (a farewell), `how's hacking?' (a friendly greeting +among hackers) and `hack, hack' (a fairly content-free but +friendly comment, often used as a temporary farewell). For more +on this totipotent term see "<b><a href="#TheMeaningofHack">The Meaning of Hack</a></b>". See +also <b><a href="#neathack">neat hack</a></b>, <b><a href="#realhack">real hack</a></b>.</p> + +<hr> +Node:<a name="hackattack">hack attack</a>, Next:<a rel="next" +href="#hackmode">hack mode</a>, Previous:<a rel="previous" +href="#hack">hack</a>, Up:<a rel="up" href="#chap08">= H +=</a> <br> + + +<p><b>hack attack</b> n.</p> + +<p>[poss. by analogy with `Big Mac Attack' from ads for the +McDonald's fast-food chain; the variant `big hack attack' is +reported] Nearly synonymous with <b><a href="#hackingrun">hacking run</a></b>, though the latter more +strongly implies an all-nighter.</p> + +<hr> +Node:<a name="hackmode">hack mode</a>, Next:<a rel="next" +href="#hackon">hack on</a>, Previous:<a rel="previous" href="#hackattack">hack attack</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hack mode</b> n.</p> + +<p>1. What one is in when hacking, of course. 2. More +specifically, a Zen-like state of total focus on The Problem that +may be achieved when one is hacking (this is why every good +hacker is part mystic). Ability to enter such concentration at +will correlates strongly with wizardliness; it is one of the most +important skills learned during <b><a href="#larvalstage">larval stage</a></b>. Sometimes amplified as +`deep hack mode'.</p> + +<p>Being yanked out of hack mode (see <b><a href="#priorityinterrupt">priority interrupt</a></b>) may be +experienced as a physical shock, and the sensation of being in +hack mode is more than a little habituating. The intensity of +this experience is probably by itself sufficient explanation for +the existence of hackers, and explains why many resist being +promoted out of positions where they can code. See also <b><a +href="#cyberspace">cyberspace</a></b> (sense 2).</p> + +<p>Some aspects of hacker etiquette will appear quite odd to an +observer unaware of the high value placed on hack mode. For +example, if someone appears at your door, it is perfectly okay to +hold up a hand (without turning one's eyes away from the screen) +to avoid being interrupted. One may read, type, and interact with +the computer for quite some time before further acknowledging the +other's presence (of course, he or she is reciprocally free to +leave without a word). The understanding is that you might be in +<b><a href="#hackmode">hack mode</a></b> with a lot of +delicate <b><a href="#state">state</a></b> (sense 2) in your +head, and you dare not <b><a href="#swap">swap</a></b> that +context out until you have reached a good point to pause. See +also <b><a href="#jugglingeggs">juggling eggs</a></b>.</p> + +<hr> +Node:<a name="hackon">hack on</a>, Next:<a rel="next" href="#hacktogether">hack together</a>, Previous:<a rel="previous" +href="#hackmode">hack mode</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hack on</b> vt.</p> + +<p>[very common] To <b><a href="#hack">hack</a></b>; implies that +the subject is some pre-existing hunk of code that one is +evolving, as opposed to something one might <b><a href="#hackup">hack up</a></b>.</p> + +<hr> +Node:<a name="hacktogether">hack together</a>, Next:<a rel="next" href="#hackup">hack up</a>, Previous:<a rel="previous" +href="#hackon">hack on</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hack together</b> vt.</p> + +<p>[common] To throw something together so it will work. Unlike +`kluge together' or <b><a href="#crufttogether">cruft +together</a></b>, this does not necessarily have negative +connotations.</p> + +<hr> +Node:<a name="hackup">hack up</a>, Next:<a rel="next" href="#hackvalue">hack value</a>, Previous:<a rel="previous" href="#hacktogether">hack together</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hack up</b> vt.</p> + +<p>To <b><a href="#hack">hack</a></b>, but generally implies that +the result is a hack in sense 1 (a quick hack). Contrast this +with <b><a href="#hackon">hack on</a></b>. To `hack up on' +implies a <b><a href="#quick-and-dirty">quick-and-dirty</a></b> +modification to an existing system. Contrast <b><a href="#hackedup">hacked up</a></b>; compare <b><a href="#klugeup">kluge up</a></b>, <b><a href="#monkeyup">monkey +up</a></b>, <b><a href="#crufttogether">cruft +together</a></b>.</p> + +<hr> +Node:<a name="hackvalue">hack value</a>, Next:<a rel="next" +href="#hackedoff">hacked off</a>, Previous:<a rel="previous" +href="#hackup">hack up</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hack value</b> n.</p> + +<p>Often adduced as the reason or motivation for expending effort +toward a seemingly useless goal, the point being that the +accomplished goal is a hack. For example, MacLISP had features +for reading and printing Roman numerals, which were installed +purely for hack value. See <b><a href="#displayhack">display +hack</a></b> for one method of computing hack value, but this +cannot really be explained, only experienced. As Louis Armstrong +once said when asked to explain jazz: "Man, if you gotta ask +you'll never know." (Feminists please note Fats Waller's +explanation of rhythm: "Lady, if you got to ask, you ain't got +it.")</p> + +<hr> +Node:<a name="hackedoff">hacked off</a>, Next:<a rel="next" +href="#hackedup">hacked up</a>, Previous:<a rel="previous" +href="#hackvalue">hack value</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hacked off</b> adj.</p> + +<p>[analogous to `pissed off'] Said of system administrators who +have become annoyed, upset, or touchy owing to suspicions that +their sites have been or are going to be victimized by crackers, +or used for inappropriate, technically illegal, or even overtly +criminal activities. For example, having unreadable files in your +home directory called `worm', `lockpick', or `goroot' would +probably be an effective (as well as impressively obvious and +stupid) way to get your sysadmin hacked off at you.</p> + +<p>It has been pointed out that there is precedent for this usage +in U.S. Navy slang, in which officers under discipline are +sometimes said to be "in hack" and one may speak of "hacking off +the C.O.".</p> + +<hr> +Node:<a name="hackedup">hacked up</a>, Next:<a rel="next" +href="#hacker">hacker</a>, Previous:<a rel="previous" href="#hackedoff">hacked off</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hacked up</b> adj.</p> + +<p>Sufficiently patched, kluged, and tweaked that the surgical +scars are beginning to crowd out normal tissue (compare <b><a +href="#criticalmass">critical mass</a></b>). Not all programs +that are hacked become `hacked up'; if modifications are done +with some eye to coherence and continued maintainability, the +software may emerge better for the experience. Contrast <b><a +href="#hackup">hack up</a></b>.</p> + +<hr> +Node:<a name="hacker">hacker</a>, Next:<a rel="next" href="#hackerethic">hacker ethic</a>, Previous:<a rel="previous" +href="#hackedup">hacked up</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hacker</b> n.</p> + +<p>[originally, someone who makes furniture with an axe] 1. A +person who enjoys exploring the details of programmable systems +and how to stretch their capabilities, as opposed to most users, +who prefer to learn only the minimum necessary. 2. One who +programs enthusiastically (even obsessively) or who enjoys +programming rather than just theorizing about programming. 3. A +person capable of appreciating <b><a href="#hackvalue">hack +value</a></b>. 4. A person who is good at programming quickly. 5. +An expert at a particular program, or one who frequently does +work using it or on it; as in `a Unix hacker'. (Definitions 1 +through 5 are correlated, and people who fit them congregate.) 6. +An expert or enthusiast of any kind. One might be an astronomy +hacker, for example. 7. One who enjoys the intellectual challenge +of creatively overcoming or circumventing limitations. 8. +[deprecated] A malicious meddler who tries to discover sensitive +information by poking around. Hence `password hacker', `network +hacker'. The correct term for this sense is <b><a href="#cracker">cracker</a></b>.</p> + +<p>The term `hacker' also tends to connote membership in the +global community defined by the net (see <b><a href="#thenetwork">the network</a></b> and <b><a href="#Internetaddress">Internet address</a></b>). For discussion +of some of the basics of this culture, see the How To Become +A Hacker FAQ. It also implies that the person described is +seen to subscribe to some version of the hacker ethic (see <b><a +href="#hackerethic">hacker ethic</a></b>).</p> + +<p>It is better to be described as a hacker by others than to +describe oneself that way. Hackers consider themselves something +of an elite (a meritocracy based on ability), though one to which +new members are gladly welcome. There is thus a certain ego +satisfaction to be had in identifying yourself as a hacker (but +if you claim to be one and are not, you'll quickly be labeled +<b><a href="#bogus">bogus</a></b>). See also <b><a href="#wannabee">wannabee</a></b>.</p> + +<p>This term seems to have been first adopted as a badge in the +1960s by the hacker culture surrounding TMRC and the MIT AI Lab. +We have a report that it was used in a sense close to this +entry's by teenage radio hams and electronics tinkerers in the +mid-1950s.</p> + +<hr> +Node:<a name="hackerethic">hacker ethic</a>, Next:<a rel="next" href="#hackerhumor">hacker humor</a>, Previous:<a rel="previous" href="#hacker">hacker</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hacker ethic</b> n.</p> + +<p>1. The belief that information-sharing is a powerful positive +good, and that it is an ethical duty of hackers to share their +expertise by writing open-source and facilitating access to +information and to computing resources wherever possible. 2. The +belief that system-cracking for fun and exploration is ethically +OK as long as the cracker commits no theft, vandalism, or breach +of confidentiality.</p> + +<p>Both of these normative ethical principles are widely, but by +no means universally, accepted among hackers. Most hackers +subscribe to the hacker ethic in sense 1, and many act on it by +writing and giving away open-source software. A few go further +and assert that <i>all</i> information should be free and +<i>any</i> proprietary control of it is bad; this is the +philosophy behind the <b><a href="#GNU">GNU</a></b> project.</p> + +<p>Sense 2 is more controversial: some people consider the act of +cracking itself to be unethical, like breaking and entering. But +the belief that `ethical' cracking excludes destruction at least +moderates the behavior of people who see themselves as `benign' +crackers (see also <b><a href="#samurai">samurai</a></b>). On +this view, it may be one of the highest forms of hackerly +courtesy to (a) break into a system, and then (b) explain to the +sysop, preferably by email from a <b><a href="#superuser">superuser</a></b> account, exactly how it was done +and how the hole can be plugged -- acting as an unpaid (and +unsolicited) <b><a href="#tigerteam">tiger team</a></b>.</p> + +<p>The most reliable manifestation of either version of the +hacker ethic is that almost all hackers are actively willing to +share technical tricks, software, and (where possible) computing +resources with other hackers. Huge cooperative networks such as +<b><a href="#Usenet">Usenet</a></b>, <b><a href="#FidoNet">FidoNet</a></b> and Internet (see <b><a href="#Internetaddress">Internet address</a></b>) can function +without central control because of this trait; they both rely on +and reinforce a sense of community that may be hackerdom's most +valuable intangible asset.</p> + +<hr> +Node:<a name="hackerhumor">hacker humor</a>, Next:<a rel="next" href="#Hackersthemovie">Hackers (the movie)</a>, +Previous:<a rel="previous" href="#hackerethic">hacker +ethic</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hacker humor</b></p> + +<p>A distinctive style of shared intellectual humor found among +hackers, having the following marked characteristics:</p> + +<p>1. Fascination with form-vs.-content jokes, paradoxes, and +humor having to do with confusion of metalevels (see <b><a href="#meta">meta</a></b>). One way to make a hacker laugh: hold a red +index card in front of him/her with "GREEN" written on it, or +vice-versa (note, however, that this is funny only the first +time).</p> + +<p>2. Elaborate deadpan parodies of large intellectual +constructs, such as specifications (see <b><a href="#write-onlymemory">write-only memory</a></b>), standards +documents, language descriptions (see <b><a href="#INTERCAL">INTERCAL</a></b>), and even entire scientific +theories (see <b><a href="#quantumbogodynamics">quantum +bogodynamics</a></b>, <b><a href="#computron">computron</a></b>).</p> + +<p>3. Jokes that involve screwily precise reasoning from bizarre, +ludicrous, or just grossly counter-intuitive premises.</p> + +<p>4. Fascination with puns and wordplay.</p> + +<p>5. A fondness for apparently mindless humor with subversive +currents of intelligence in it -- for example, old Warner +Brothers and Rocky & Bullwinkle cartoons, the Marx brothers, +the early B-52s, and Monty Python's Flying Circus. Humor that +combines this trait with elements of high camp and slapstick is +especially favored.</p> + +<p>6. References to the symbol-object antinomies and associated +ideas in Zen Buddhism and (less often) Taoism. See <b><a href="#hastheXnature">has the X nature</a></b>, <b><a href="#Discordianism">Discordianism</a></b>, <b><a href="#zen">zen</a></b>, <b><a href="#hahaonlyserious">ha ha +only serious</a></b>, <b><a href="#koan">koan</a></b>, <b><a +href="#AIkoans">AI koans</a></b>.</p> + +<p>See also <b><a href="#filk">filk</a></b>, <b><a href="#retrocomputing">retrocomputing</a></b>, and the Portrait of J. +Random Hacker in <b><a href="#AppendixB">Appendix B</a></b>. +If you have an itchy feeling that all six of these traits are +really aspects of one thing that is incredibly difficult to talk +about exactly, you are (a) correct and (b) responding like a +hacker. These traits are also recognizable (though in a less +marked form) throughout <b><a href="#science-fictionfandom">science-fiction fandom</a></b>.</p> + +<hr> +Node:<a name="Hackersthemovie">Hackers (the movie)</a>, +Next:<a rel="next" href="#hackingrun">hacking run</a>, +Previous:<a rel="previous" href="#hackerhumor">hacker +humor</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>Hackers (the movie)</b> n.</p> + +<p>A notable bomb from 1995. Should have been titled "Crackers", +because cracking is what the movie was about. It's understandable +that they didn't however; titles redolent of snack food are +probably a tough sell in Hollywood.</p> + +<hr> +Node:<a name="hackingrun">hacking run</a>, Next:<a rel="next" +href="#HackingXforY">Hacking X for Y</a>, Previous:<a +rel="previous" href="#Hackersthemovie">Hackers (the +movie)</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hacking run</b> n.</p> + +<p>[analogy with `bombing run' or `speed run'] A hack session +extended long outside normal working times, especially one longer +than 12 hours. May cause you to `change phase the hard way' (see +<b><a href="#phase">phase</a></b>).</p> + +<hr> +Node:<a name="HackingXforY">Hacking X for Y</a>, Next:<a +rel="next" href="#Hackintosh">Hackintosh</a>, Previous:<a rel="previous" href="#hackingrun">hacking run</a>, Up:<a rel="up" +href="#chap08">= H =</a> <br> + + +<p><b>Hacking X for Y</b> n.</p> + +<p>[ITS] Ritual phrasing of part of the information which ITS +made publicly available about each user. This information (the +INQUIR record) was a sort of form in which the user could fill +out various fields. On display, two of these fields were always +combined into a project description of the form "Hacking X for Y" +(e.g., <code>"Hacking perceptrons for Minsky"</code>). This form +of description became traditional and has since been carried over +to other systems with more general facilities for +self-advertisement (such as Unix <b><a href="#planfile">plan +file</a></b>s).</p> + +<hr> +Node:<a name="Hackintosh">Hackintosh</a>, Next:<a rel="next" +href="#hackish">hackish</a>, Previous:<a rel="previous" href="#HackingXforY">Hacking X for Y</a>, Up:<a rel="up" +href="#chap08">= H =</a> <br> + + +<p><b>Hackintosh</b> n.</p> + +<p>1. An Apple Lisa that has been hacked into emulating a +Macintosh (also called a `Mac XL'). 2. A Macintosh assembled from +parts theoretically belonging to different models in the +line.</p> + +<hr> +Node:<a name="hackish">hackish</a>, Next:<a rel="next" href="#hackishness">hackishness</a>, Previous:<a rel="previous" href="#Hackintosh">Hackintosh</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hackish</b> /hak'ish/ adj.</p> + +<p>(also <b><a href="#hackishness">hackishness</a></b> n.) 1. +Said of something that is or involves a hack. 2. Of or pertaining +to hackers or the hacker subculture. See also <b><a href="#true-hacker">true-hacker</a></b>.</p> + +<hr> +Node:<a name="hackishness">hackishness</a>, Next:<a rel="next" +href="#hackitude">hackitude</a>, Previous:<a rel="previous" href="#hackish">hackish</a>, Up:<a rel="up" href="#chap08">= H +=</a> <br> + + +<p><b>hackishness</b> n.</p> + +<p>The quality of being or involving a hack. This term is +considered mildly silly. Syn. <b><a href="#hackitude">hackitude</a></b>.</p> + +<hr> +Node:<a name="hackitude">hackitude</a>, Next:<a rel="next" href="#hair">hair</a>, Previous:<a rel="previous" href="#hackishness">hackishness</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hackitude</b> n.</p> + +<p>Syn. <b><a href="#hackishness">hackishness</a></b>; this word +is considered sillier.</p> + +<hr> +Node:<a name="hair">hair</a>, Next:<a rel="next" href="#hairball">hairball</a>, Previous:<a rel="previous" href="#hackitude">hackitude</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hair</b> n.</p> + +<p>[back-formation from <b><a href="#hairy">hairy</a></b>] The +complications that make something hairy. "Decoding <b><a href="#TECO">TECO</a></b> commands requires a certain amount of hair." +Often seen in the phrase `infinite hair', which connotes extreme +complexity. Also in `hairiferous' (tending to promote hair +growth): "GNUMACS elisp encourages lusers to write complex +editing modes." "Yeah, it's pretty hairiferous all right." (or +just: "Hair squared!")</p> + +<hr> +Node:<a name="hairball">hairball</a>, Next:<a rel="next" href="#hairy">hairy</a>, Previous:<a rel="previous" href="#hair">hair</a>, Up:<a rel="up" href="#chap08">= H =</a> +<br> + + +<p><b>hairball</b> n.</p> + +<p>1. [Fidonet] A large batch of messages that a +store-and-forward network is failing to forward when it should. +Often used in the phrase "Fido coughed up a hairball today", +meaning that the stuck messages have just come unstuck, producing +a flood of mail where there had previously been drought. 2. An +unmanageably huge mass of source code. "JWZ thought the Mozilla +effort bogged down because the code was a huge hairball." 3. Any +large amount of garbage coming out suddenly. "Sendmail is +coughing up a hairball, so expect some slowness accessing the +Internet."</p> + +<hr> +Node:<a name="hairy">hairy</a>, Next:<a rel="next" href="#HAKMEM">HAKMEM</a>, Previous:<a rel="previous" href="#hairball">hairball</a>, Up:<a rel="up" href="#chap08">= +H =</a> <br> + + +<p><b>hairy</b> adj.</p> + +<p>1. Annoyingly complicated. "<b><a href="#DWIM">DWIM</a></b> is +incredibly hairy." 2. Incomprehensible. "<b><a href="#DWIM">DWIM</a></b> is incredibly hairy." 3. Of people, +high-powered, authoritative, rare, expert, and/or +incomprehensible. Hard to explain except in context: "He knows +this hairy lawyer who says there's nothing to worry about." See +also <b><a href="#hirsute">hirsute</a></b>.</p> + +<p>A well-known result in topology called the Brouwer Fixed-Point +Theorem states that any continuous transformation of a 2-sphere +into itself has at least one fixed point. Mathematically literate +hackers tend to associate the term `hairy' with the informal +version of this theorem; "You can't comb a hairy ball +smooth."</p> + +<p>The adjective `long-haired' is well-attested to have been in +slang use among scientists and engineers during the early 1950s; +it was equivalent to modern `hairy' senses 1 and 2, and was very +likely ancestral to the hackish use. In fact the noun `long-hair' +was at the time used to describe a person satisfying sense 3. +Both senses probably passed out of use when long hair was adopted +as a signature trait by the 1960s counterculture, leaving hackish +`hairy' as a sort of stunted mutant relic.</p> + +<p>In British mainstream use, "hairy" means "dangerous", and +consequently, in British programming terms, "hairy" may be used +to denote complicated and/or incomprehensible code, but only if +that complexity or incomprehesiveness is also considered +dangerous.</p> + +<hr> +Node:<a name="HAKMEM">HAKMEM</a>, Next:<a rel="next" href="#hakspek">hakspek</a>, Previous:<a rel="previous" href="#hairy">hairy</a>, Up:<a rel="up" href="#chap08">= H +=</a> <br> + + +<p><b>HAKMEM</b> /hak'mem/ n.</p> + +<p>MIT AI Memo 239 (February 1972). A legendary collection of +neat mathematical and programming hacks contributed by many +people at MIT and elsewhere. (The title of the memo really is +"HAKMEM", which is a 6-letterism for `hacks memo'.) Some of them +are very useful techniques, powerful theorems, or interesting +unsolved problems, but most fall into the category of +mathematical and computer trivia. Here is a sampling of the +entries (with authors), slightly paraphrased:</p> + +<p>Item 41 (Gene Salamin): There are exactly 23,000 prime numbers +less than 2^(18).</p> + +<p>Item 46 (Rich Schroeppel): The most <i>probable</i> suit +distribution in bridge hands is 4-4-3-2, as compared to 4-3-3-3, +which is the most <i>evenly</i> distributed. This is because +the world likes to have unequal numbers: a thermodynamic effect +saying things will not be in the state of lowest energy, but in +the state of lowest disordered energy.</p> + +<p>Item 81 (Rich Schroeppel): Count the magic squares of order 5 +(that is, all the 5-by-5 arrangements of the numbers from 1 to 25 +such that all rows, columns, and diagonals add up to the same +number). There are about 320 million, not counting those that +differ only by rotation and reflection.</p> + +<p>Item 154 (Bill Gosper): The myth that any given programming +language is machine independent is easily exploded by computing +the sum of powers of 2. If the result loops with period = 1 with +sign +, you are on a sign-magnitude machine. If the result loops +with period = 1 at -1, you are on a twos-complement machine. If +the result loops with period greater than 1, including the +beginning, you are on a ones-complement machine. If the result +loops with period greater than 1, not including the beginning, +your machine isn't binary -- the pattern should tell you the +base. If you run out of memory, you are on a string or bignum +system. If arithmetic overflow is a fatal error, some fascist pig +with a read-only mind is trying to enforce machine independence. +But the very ability to trap overflow is machine dependent. By +this strategy, consider the universe, or, more precisely, +algebra: Let X = the sum of many powers of 2 = +<small>...</small>111111 (base 2). Now add X to itself: X + X = +<small>...</small>111110. Thus, 2X = X - 1, so X = -1. Therefore +algebra is run on a machine (the universe) that is +two's-complement.</p> + +<p>Item 174 (Bill Gosper and Stuart Nelson): 21963283741 is the +only number such that if you represent it on the <b><a href="#PDP-10">PDP-10</a></b> as both an integer and a floating-point +number, the bit patterns of the two representations are +identical.</p> + +<p>Item 176 (Gosper): The "banana phenomenon" was encountered +when processing a character string by taking the last 3 letters +typed out, searching for a random occurrence of that sequence in +the text, taking the letter following that occurrence, typing it +out, and iterating. This ensures that every 4-letter string +output occurs in the original. The program typed +BANANANANANANANA<small>...</small>. We note an ambiguity in the +phrase, "the Nth occurrence of." In one sense, there are five +00's in 0000000000; in another, there are nine. The editing +program TECO finds five. Thus it finds only the first ANA in +BANANA, and is thus obligated to type N next. By Murphy's Law, +there is but one NAN, thus forcing A, and thus a loop. An option +to find overlapped instances would be useful, although it would +require backing up N - 1 characters before seeking the next +N-character string.</p> + +<p>Note: This last item refers to a <b><a href="#DissociatedPress">Dissociated Press</a></b> implementation. +See also <b><a href="#bananaproblem">banana +problem</a></b>.</p> + +<p>HAKMEM also contains some rather more complicated mathematical +and technical items, but these examples show some of its fun +flavor.</p> + +<p>An HTML transcription of the entire document is available at +http://www.inwap.com/pdp10/hbaker/hakmem/hakmem.html.</p> + +<hr> +Node:<a name="hakspek">hakspek</a>, Next:<a rel="next" href="#HalloweenDocuments">Halloween Documents</a>, Previous:<a +rel="previous" href="#HAKMEM">HAKMEM</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hakspek</b> /hak'speek/ n.</p> + +<p>A shorthand method of spelling found on many British academic +bulletin boards and <b><a href="#talkersystem">talker +system</a></b>s. Syllables and whole words in a sentence are +replaced by single ASCII characters the names of which are +phonetically similar or equivalent, while multiple letters are +usually dropped. Hence, `for' becomes `4'; `two', `too', and `to' +become `2'; `ck' becomes `k'. "Before I see you tomorrow" becomes +"b4 i c u 2moro". First appeared in London about 1986, and was +probably caused by the slowness of available talker systems, +which operated on archaic machines with outdated operating +systems and no standard methods of communication. Has become +rarer since. See also <b><a href="#talkmode">talk +mode</a></b>.</p> + +<hr> +Node:<a name="HalloweenDocuments">Halloween Documents</a>, +Next:<a rel="next" href="#hammer">hammer</a>, Previous:<a rel="previous" href="#hakspek">hakspek</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>Halloween Documents</b> n.</p> + +<p>A pair of Microsoft internal strategy memoranda leaked to ESR +in late 1998 that confirmed everybody's paranoia about the +current <b><a href="#EvilEmpire">Evil Empire</a></b>. These documents +praised the technical excellence of <b><a href="#Linux">Linux</a></b> and outlined a counterstrategy of +attempting to lock in customers by "de-commoditizing" Internet +protocols and services. They were extensively cited on the +Internet and in the press and proved so embarrassing that +Microsoft PR barely said a word in public for six months +afterwards.</p> + +<hr> +Node:<a name="hammer">hammer</a>, Next:<a rel="next" href="#hamster">hamster</a>, Previous:<a rel="previous" href="#HalloweenDocuments">Halloween Documents</a>, Up:<a rel="up" +href="#chap08">= H =</a> <br> + + +<p><b>hammer</b> vt.</p> + +<p>Commonwealth hackish syn. for <b><a href="#bangon">bang +on</a></b>.</p> + +<hr> +Node:<a name="hamster">hamster</a>, Next:<a rel="next" href="#HAND">HAND</a>, Previous:<a rel="previous" href="#hammer">hammer</a>, Up:<a rel="up" href="#chap08">= H +=</a> <br> + + +<p><b>hamster</b> n.</p> + +<p>1. [Fairchild] A particularly slick little piece of code that +does one thing well; a small, self-contained hack. The image is +of a hamster <b><a href="#happily">happily</a></b> spinning its +exercise wheel. 2. A tailless mouse; that is, one with an +infrared link to a receiver on the machine, as opposed to the +conventional cable. 3. [UK] Any item of hardware made by Amstrad, +a company famous for its cheap plastic PC-almost-compatibles.</p> + +<hr> +Node:<a name="HAND">HAND</a>, Next:<a rel="next" href="#handcruft">hand cruft</a>, Previous:<a rel="previous" href="#hamster">hamster</a>, Up:<a rel="up" href="#chap08">= H +=</a> <br> + + +<p><b>HAND</b> //</p> + +<p>[Usenet: very common] Abbreviation: Have A Nice Day. Typically +used to close a <b><a href="#Usenet">Usenet</a></b> posting, but +also used to informally close emails; often preceded by <b><a +href="#HTH">HTH</a></b>.</p> + +<hr> +Node:<a name="handcruft">hand cruft</a>, Next:<a rel="next" +href="#hand-hacking">hand-hacking</a>, Previous:<a rel="previous" +href="#HAND">HAND</a>, Up:<a rel="up" href="#chap08">= H +=</a> <br> + + +<p><b>hand cruft</b> vt.</p> + +<p>[pun on `hand craft'] See <b><a href="#cruft">cruft</a></b>, +sense 3.</p> + +<hr> +Node:<a name="hand-hacking">hand-hacking</a>, Next:<a rel="next" +href="#hand-roll">hand-roll</a>, Previous:<a rel="previous" href="#handcruft">hand cruft</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hand-hacking</b> n.</p> + +<p>1. [rare] The practice of translating <b><a href="#hotspot">hot spot</a></b>s from an <b><a href="#HLL">HLL</a></b> into hand-tuned assembler, as opposed to +trying to coerce the compiler into generating better code. Both +the term and the practice are becoming uncommon. See <b><a href="#tune">tune</a></b>, <b><a href="#bum">bum</a></b>, <b><a href="#byhand">by hand</a></b>; syn. with v. <b><a href="#cruft">cruft</a></b>. 2. [common] More generally, manual +construction or patching of data sets that would normally be +generated by a translation utility and interpreted by another +program, and aren't really designed to be read or modified by +humans.</p> + +<hr> +Node:<a name="hand-roll">hand-roll</a>, Next:<a rel="next" href="#handle">handle</a>, Previous:<a rel="previous" href="#hand-hacking">hand-hacking</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hand-roll</b> v.</p> + +<p>[from obs. mainstream slang `hand-rolled' in opposition to +`ready-made', referring to cigarettes] To perform a normally +automated software installation or configuration process <b><a +href="#byhand">by hand</a></b>; implies that the normal +process failed due to bugs in the configurator or was defeated by +something exceptional in the local environment. "The worst thing +about being a gateway between four different nets is having to +hand-roll a new sendmail configuration every time any of them +upgrades."</p> + +<hr> +Node:<a name="handle">handle</a>, Next:<a rel="next" href="#handshaking">handshaking</a>, Previous:<a rel="previous" href="#hand-roll">hand-roll</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>handle</b> n.</p> + +<p>1. [from CB slang] An electronic pseudonym; a `nom de guerre' +intended to conceal the user's true identity. Network and BBS +handles function as the same sort of simultaneous concealment and +display one finds on Citizen's Band radio, from which the term +was adopted. Use of grandiose handles is characteristic of <b><a +href="#warezd00dz">warez d00dz</a></b>, <b><a href="#cracker">cracker</a></b>s, <b><a href="#weenie">weenie</a></b>s, <b><a href="#spod">spod</a></b>s, and +other lower forms of network life; true hackers travel on their +own reputations rather than invented legendry. Compare <b><a +href="#nick">nick</a></b>, <b><a href="#screenname">screen +name</a></b>. 2. A <b><a href="#magiccookie">magic +cookie</a></b>, often in the form of a numeric index into some +array somewhere, through which you can manipulate an object like +a file or window. The form `file handle' is especially common. 3. +[Mac] A pointer to a pointer to dynamically-allocated memory; the +extra level of indirection allows on-the-fly memory compaction +(to cut down on fragmentation) or aging out of unused resources, +with minimal impact on the (possibly multiple) parts of the +larger program containing references to the allocated memory. +Compare <b><a href="#snap">snap</a></b> (to snap a handle would +defeat its purpose); see also <b><a href="#aliasingbug">aliasing bug</a></b>, <b><a href="#danglingpointer">dangling pointer</a></b>.</p> + +<hr> +Node:<a name="handshaking">handshaking</a>, Next:<a rel="next" +href="#handwave">handwave</a>, Previous:<a rel="previous" href="#handle">handle</a>, Up:<a rel="up" href="#chap08">= H +=</a> <br> + + +<p><b>handshaking</b> n.</p> + +<p>[very common] Hardware or software activity designed to start +or keep two machines or programs in synchronization as they <b><a +href="#doprotocol">do protocol</a></b>. Often applied to human +activity; thus, a hacker might watch two people in conversation +nodding their heads to indicate that they have heard each others' +points and say "Oh, they're handshaking!". See also <b><a href="#protocol">protocol</a></b>.</p> + +<hr> +Node:<a name="handwave">handwave</a>, Next:<a rel="next" href="#hang">hang</a>, Previous:<a rel="previous" href="#handshaking">handshaking</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>handwave</b></p> + +<p>[poss. from gestures characteristic of stage magicians] 1. v. +To gloss over a complex point; to distract a listener; to support +a (possibly actually valid) point with blatantly faulty logic. 2. +n. The act of handwaving. "Boy, what a handwave!"</p> + +<p>If someone starts a sentence with "Clearly<small>...</small>" +or "Obviously<small>...</small>" or "It is self-evident +that<small>...</small>", it is a good bet he is about to handwave +(alternatively, use of these constructions in a sarcastic tone +before a paraphrase of someone else's argument suggests that it +is a handwave). The theory behind this term is that if you wave +your hands at the right moment, the listener may be sufficiently +distracted to not notice that what you have said is <b><a href="#bogus">bogus</a></b>. Failing that, if a listener does object, +you might try to dismiss the objection with a wave of your +hand.</p> + +<p>The use of this word is often accompanied by gestures: both +hands up, palms forward, swinging the hands in a vertical plane +pivoting at the elbows and/or shoulders (depending on the +magnitude of the handwave); alternatively, holding the forearms +in one position while rotating the hands at the wrist to make +them flutter. In context, the gestures alone can suffice as a +remark; if a speaker makes an outrageously unsupported +assumption, you might simply wave your hands in this way, as an +accusation, far more eloquent than words could express, that his +logic is faulty.</p> + +<hr> +Node:<a name="hang">hang</a>, Next:<a rel="next" href="#HanlonsRazor">Hanlon's Razor</a>, Previous:<a rel="previous" href="#handwave">handwave</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hang</b> v.</p> + +<p>1. [very common] To wait for an event that will never occur. +"The system is hanging because it can't read from the crashed +drive". See <b><a href="#wedged">wedged</a></b>, <b><a href="#hung">hung</a></b>. 2. To wait for some event to occur; to hang +around until something happens. "The program displays a menu and +then hangs until you type a character." Compare <b><a href="#block">block</a></b>. 3. To attach a peripheral device, esp. in +the construction `hang off': "We're going to hang another tape +drive off the file server." Implies a device attached with +cables, rather than something that is strictly inside the +machine's chassis.</p> + +<hr> +Node:<a name="HanlonsRazor">Hanlon's Razor</a>, Next:<a rel="next" href="#happily">happily</a>, Previous:<a rel="previous" +href="#hang">hang</a>, Up:<a rel="up" href="#chap08">= H +=</a> <br> + + +<p><b>Hanlon's Razor</b> prov.</p> + +<p>A corollary of <b><a href="#FinaglesLaw">Finagle's +Law</a></b>, similar to Occam's Razor, that reads "Never +attribute to malice that which can be adequately explained by +stupidity." The derivation of the Hanlon eponym is not definitely +known, but a very similar remark ("You have attributed conditions +to villainy that simply result from stupidity.") appears in +"Logic of Empire", a classic 1941 SF story by Robert A. Heinlein, +who calls it the `devil theory' of sociology. Heinlein's +popularity in the hacker culture makes plausible the supposition +that `Hanlon' is derived from `Heinlein' by phonetic corruption. +A similar epigram has been attributed to William James, but +Heinlein more probably got the idea from Alfred Korzybski and +other practitioners of General Semantics. Quoted here because it +seems to be a particular favorite of hackers, often showing up in +<b><a href="#sigblock">sig block</a></b>s, <b><a href="#fortunecookie">fortune cookie</a></b> files and the login +banners of BBS systems and commercial networks. This probably +reflects the hacker's daily experience of environments created by +well-intentioned but short-sighted people. Compare <b><a href="#SturgeonsLaw">Sturgeon's Law</a></b>, <b><a href="#NinetyNinetyRule">Ninety-Ninety Rule</a></b>.</p> + +<hr> +Node:<a name="happily">happily</a>, Next:<a rel="next" href="#haque">haque</a>, Previous:<a rel="previous" href="#HanlonsRazor">Hanlon's Razor</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>happily</b> adv.</p> + +<p>Of software, used to emphasize that a program is unaware of +some important fact about its environment, either because it has +been fooled into believing a lie, or because it doesn't care. The +sense of `happy' here is not that of elation, but rather that of +blissful ignorance. "The program continues to run, happily +unaware that its output is going to /dev/null." Also used to +suggest that a program or device would really rather be doing +something destructive, and is being given an opportunity to do +so. "If you enter an O here instead of a zero, the program will +happily erase all your data." Neverheless, use of this term +implies a basically benign attitude towards the program: It +didn't mean any harm, it was just eager to do its job. We'd like +to be angry at it but we shouldn't, we should try to understand +it instead. The adjective "cheerfully" is often used in exactly +the same way.</p> + +<hr> +Node:<a name="haque">haque</a>, Next:<a rel="next" href="#hardboot">hard boot</a>, Previous:<a rel="previous" href="#happily">happily</a>, Up:<a rel="up" href="#chap08">= H +=</a> <br> + + +<p><b>haque</b> /hak/ n.</p> + +<p>[Usenet] Variant spelling of <b><a href="#hack">hack</a></b>, +used only for the noun form and connoting an <b><a href="#elegant">elegant</a></b> hack. that is a <b><a href="#hack">hack</a></b> in sense 2.</p> + +<hr> +Node:<a name="hardboot">hard boot</a>, Next:<a rel="next" +href="#hardcoded">hardcoded</a>, Previous:<a rel="previous" href="#haque">haque</a>, Up:<a rel="up" href="#chap08">= H +=</a> <br> + + +<p><b>hard boot</b> n.</p> + +<p>See <b><a href="#boot">boot</a></b>.</p> + +<hr> +Node:<a name="hardcoded">hardcoded</a>, Next:<a rel="next" href="#hardwarily">hardwarily</a>, Previous:<a rel="previous" href="#hardboot">hard boot</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hardcoded</b> adj.</p> + +<p>1. [common] Said of data inserted directly into a program, +where it cannot be easily modified, as opposed to data in some +<b><a href="#profile">profile</a></b>, resource (see <b><a href="#de-rezz">de-rezz</a></b> sense 2), or environment variable that +a <b><a href="#user">user</a></b> or hacker can easily modify. 2. +In C, this is esp. applied to use of a literal instead of a +<code>#define</code> macro (see <b><a href="#magicnumber">magic number</a></b>).</p> + +<hr> +Node:<a name="hardwarily">hardwarily</a>, Next:<a rel="next" +href="#hardwired">hardwired</a>, Previous:<a rel="previous" href="#hardcoded">hardcoded</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hardwarily</b> /hard-weir'*-lee/ adv.</p> + +<p>In a way pertaining to hardware. "The system is hardwarily +unreliable." The adjective `hardwary' is <i>not</i> +traditionally used, though it has recently been reported from the +U.K. See <b><a href="#softwarily">softwarily</a></b>.</p> + +<hr> +Node:<a name="hardwired">hardwired</a>, Next:<a rel="next" href="#hastheXnature">has the X nature</a>, Previous:<a rel="previous" href="#hardwarily">hardwarily</a>, Up:<a rel="up" +href="#chap08">= H =</a> <br> + + +<p><b>hardwired</b> adj.</p> + +<p>1. In software, syn. for <b><a href="#hardcoded">hardcoded</a></b>. 2. By extension, anything that is +not modifiable, especially in the sense of customizable to one's +particular needs or tastes.</p> + +<hr> +Node:<a name="hastheXnature">has the X nature</a>, +Next:<a rel="next" href="#hashbucket">hash bucket</a>, +Previous:<a rel="previous" href="#hardwired">hardwired</a>, Up:<a +rel="up" href="#chap08">= H =</a> <br> + + +<p><b>has the X nature</b></p> + +<p>[seems to derive from Zen Buddhist koans of the form "Does an +X have the Buddha-nature?"] adj. Common hacker construction for +`is an X', used for humorous emphasis. "Anyone who can't even use +a program with on-screen help embedded in it truly has the <b><a +href="#loser">loser</a></b> nature!" See also <b><a href="#theXthatcanbeYisnotthetrueX">the +X that can be Y is not the true X</a></b>. See also <b><a href="#mu">mu</a></b>.</p> + +<hr> +Node:<a name="hashbucket">hash bucket</a>, Next:<a rel="next" +href="#hashcollision">hash collision</a>, Previous:<a rel="previous" href="#hastheXnature">has the X nature</a>, +Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hash bucket</b> n.</p> + +<p>A notional receptacle, a set of which might be used to +apportion data items for sorting or lookup purposes. When you +look up a name in the phone book (for example), you typically +hash it by extracting its first letter; the hash buckets are the +alphabetically ordered letter sections. This term is used as +techspeak with respect to code that uses actual hash functions; +in jargon, it is used for human associative memory as well. Thus, +two things `in the same hash bucket' are more difficult to +discriminate, and may be confused. "If you hash English words +only by length, you get too many common grammar words in the +first couple of hash buckets." Compare <b><a href="#hashcollision">hash collision</a></b>.</p> + +<hr> +Node:<a name="hashcollision">hash collision</a>, Next:<a rel="next" href="#hat">hat</a>, Previous:<a rel="previous" href="#hashbucket">hash bucket</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hash collision</b> n.</p> + +<p>[from the techspeak] (var. `hash clash') When used of people, +signifies a confusion in associative memory or imagination, +especially a persistent one (see <b><a href="#thinko">thinko</a></b>). True story: One of us [ESR] was once +on the phone with a friend about to move out to Berkeley. When +asked what he expected Berkeley to be like, the friend replied: +"Well, I have this mental picture of naked women throwing Molotov +cocktails, but I think that's just a collision in my hash +tables." Compare <b><a href="#hashbucket">hash +bucket</a></b>.</p> + +<hr> +Node:<a name="hat">hat</a>, Next:<a rel="next" href="#HCF">HCF</a>, Previous:<a rel="previous" href="#hashcollision">hash collision</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hat</b> n.</p> + +<p>Common (spoken) name for the circumflex (`^', ASCII 1011110) +character. See <b><a href="#ASCII">ASCII</a></b> for other +synonyms.</p> + +<hr> +Node:<a name="HCF">HCF</a>, Next:<a rel="next" href="#headsdown">heads down</a>, Previous:<a rel="previous" href="#hat">hat</a>, Up:<a rel="up" href="#chap08">= H =</a> +<br> + + +<p><b>HCF</b> /H-C-F/ n.</p> + +<p>Mnemonic for `Halt and Catch Fire', any of several +undocumented and semi-mythical machine instructions with +destructive side-effects, supposedly included for test purposes +on several well-known architectures going as far back as the IBM +360. The MC6800 microprocessor was the first for which an HCF +opcode became widely known. This instruction caused the processor +to <b><a href="#toggle">toggle</a></b> a subset of the bus lines +as rapidly as it could; in some configurations this could +actually cause lines to burn up. Compare <b><a href="#killerpoke">killer poke</a></b>.</p> + +<hr> +Node:<a name="headsdown">heads down</a>, Next:<a rel="next" +href="#heartbeat">heartbeat</a>, Previous:<a rel="previous" href="#HCF">HCF</a>, Up:<a rel="up" href="#chap08">= H =</a> +<br> + + +<p><b>heads down</b> [Sun] adj.</p> + +<p>Concentrating, usually so heavily and for so long that +everything outside the focus area is missed. See also <b><a href="#hackmode">hack mode</a></b> and <b><a href="#larvalstage">larval stage</a></b>, although this mode is +hardly confined to fledgling hackers.</p> + +<hr> +Node:<a name="heartbeat">heartbeat</a>, Next:<a rel="next" href="#heatseeker">heatseeker</a>, Previous:<a rel="previous" href="#headsdown">heads down</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>heartbeat</b> n.</p> + +<p>1. The signal emitted by a Level 2 Ethernet transceiver at the +end of every packet to show that the collision-detection circuit +is still connected. 2. A periodic synchronization signal used by +software or hardware, such as a bus clock or a periodic +interrupt. 3. The `natural' oscillation frequency of a computer's +clock crystal, before frequency division down to the machine's +clock rate. 4. A signal emitted at regular intervals by software +to demonstrate that it is still alive. Sometimes hardware is +designed to reboot the machine if it stops hearing a heartbeat. +See also <b><a href="#breath-of-lifepacket">breath-of-life +packet</a></b>.</p> + +<hr> +Node:<a name="heatseeker">heatseeker</a>, Next:<a rel="next" +href="#heavymetal">heavy metal</a>, Previous:<a rel="previous" +href="#heartbeat">heartbeat</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>heatseeker</b> n.</p> + +<p>[IBM] A customer who can be relied upon to buy, without fail, +the latest version of an existing product (not quite the same as +a member of the <b><a href="#lunaticfringe">lunatic +fringe</a></b>). A 1993 example of a heatseeker was someone who, +owning a 286 PC and Windows 3.0, went out and bought Windows 3.1 +(which offers no worthwhile benefits unless you have a 386). If +all customers were heatseekers, vast amounts of money could be +made by just fixing some of the bugs in each release (n) and +selling it to them as release (n+1). Microsoft in fact seems to +have mastered this technique.</p> + +<hr> +Node:<a name="heavymetal">heavy metal</a>, Next:<a rel="next" +href="#heavywizardry">heavy wizardry</a>, Previous:<a rel="previous" href="#heatseeker">heatseeker</a>, Up:<a rel="up" +href="#chap08">= H =</a> <br> + + +<p><b>heavy metal</b> n.</p> + +<p>[Cambridge] Syn. <b><a href="#bigiron">big +iron</a></b>.</p> + +<hr> +Node:<a name="heavywizardry">heavy wizardry</a>, Next:<a rel="next" href="#heavyweight">heavyweight</a>, Previous:<a rel="previous" href="#heavymetal">heavy metal</a>, Up:<a rel="up" +href="#chap08">= H =</a> <br> + + +<p><b>heavy wizardry</b> n.</p> + +<p>Code or designs that trade on a particularly intimate +knowledge or experience of a particular operating system or +language or complex application interface. Distinguished from +<b><a href="#deepmagic">deep magic</a></b>, which trades more +on arcane <i>theoretical</i> knowledge. Writing device drivers +is heavy wizardry; so is interfacing to <b><a href="#X">X</a></b> +(sense 2) without a toolkit. Esp. found in source-code comments +of the form "Heavy wizardry begins here". Compare <b><a href="#voodooprogramming">voodoo programming</a></b>.</p> + +<hr> +Node:<a name="heavyweight">heavyweight</a>, Next:<a rel="next" +href="#heisenbug">heisenbug</a>, Previous:<a rel="previous" href="#heavywizardry">heavy wizardry</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>heavyweight</b> adj.</p> + +<p>[common] High-overhead; <b><a href="#baroque">baroque</a></b>; +code-intensive; featureful, but costly. Esp. used of +communication protocols, language designs, and any sort of +implementation in which maximum generality and/or ease of +implementation has been pushed at the expense of mundane +considerations such as speed, memory utilization, and startup +time. <b><a href="#EMACS">EMACS</a></b> is a heavyweight editor; +<b><a href="#X">X</a></b> is an <i>extremely</i> heavyweight +window system. This term isn't pejorative, but one hacker's +heavyweight is another's <b><a href="#elephantine">elephantine</a></b> and a third's <b><a href="#monstrosity">monstrosity</a></b>. Oppose `lightweight'. Usage: +now borders on techspeak, especially in the compound `heavyweight +process'.</p> + +<hr> +Node:<a name="heisenbug">heisenbug</a>, Next:<a rel="next" href="#HelenKellermode">Helen Keller mode</a>, Previous:<a rel="previous" href="#heavyweight">heavyweight</a>, Up:<a rel="up" +href="#chap08">= H =</a> <br> + + +<p><b>heisenbug</b> /hi:'zen-buhg/ n.</p> + +<p>[from Heisenberg's Uncertainty Principle in quantum physics] A +bug that disappears or alters its behavior when one attempts to +probe or isolate it. (This usage is not even particularly +fanciful; the use of a debugger sometimes alters a program's +operating environment significantly enough that buggy code, such +as that which relies on the values of uninitialized memory, +behaves quite differently.) Antonym of <b><a href="#Bohrbug">Bohr bug</a></b>; see also <b><a href="#mandelbug">mandelbug</a></b>, <b><a href="#schroedinbug">schroedinbug</a></b>. In C, nine out of ten +heisenbugs result from uninitialized auto variables, <b><a href="#fandangooncore">fandango on core</a></b> phenomena (esp. +lossage related to corruption of the malloc <b><a href="#arena">arena</a></b>) or errors that <b><a href="#smashthestack">smash the stack</a></b>.</p> + +<hr> +Node:<a name="HelenKellermode">Helen Keller mode</a>, +Next:<a rel="next" href="#hellosailor">hello sailor!</a>, +Previous:<a rel="previous" href="#heisenbug">heisenbug</a>, Up:<a +rel="up" href="#chap08">= H =</a> <br> + + +<p><b>Helen Keller mode</b> n.</p> + +<p>1. State of a hardware or software system that is deaf, dumb, +and blind, i.e., accepting no input and generating no output, +usually due to an infinite loop or some other excursion into +<b><a href="#deepspace">deep space</a></b>. (Unfair to the +real Helen Keller, whose success at learning speech was +triumphant.) See also <b><a href="#goflatline">go +flatline</a></b>, <b><a href="#catatonic">catatonic</a></b>. 2. +On IBM PCs under DOS, refers to a specific failure mode in which +a screen saver has kicked in over an <b><a href="#ill-behaved">ill-behaved</a></b> application which bypasses the +very interrupts the screen saver watches for activity. Your +choices are to try to get from the program's current state +through a successful save-and-exit without being able to see what +you're doing, or to re-boot the machine. This isn't (strictly +speaking) a crash.</p> + +<hr> +Node:<a name="hellosailor">hello sailor!</a>, Next:<a rel="next" href="#hellowall">hello wall!</a>, Previous:<a rel="previous" href="#HelenKellermode">Helen Keller mode</a>, +Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hello sailor!</b> interj.</p> + +<p>Occasional West Coast equivalent of <b><a href="#helloworld">hello world</a></b>; seems to have originated at +SAIL, later associated with the game <b><a href="#Zork">Zork</a></b> (which also included "hello, aviator" and +"hello, implementor"). Originally from the traditional hooker's +greeting to a swabbie fresh off the boat, of course. The standard +response is "Nothing happens here."; of all the Zork/Dungeon +games, only in Infocom's Zork 3 is "Hello, Sailor" actually +useful (excluding the unique situation where _knowing_ this fact +is important in Dungeon...).</p> + +<hr> +Node:<a name="hellowall">hello wall!</a>, Next:<a rel="next" +href="#helloworld">hello world</a>, Previous:<a rel="previous" +href="#hellosailor">hello sailor!</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hello, wall!</b> excl.</p> + +<p>See <b><a href="#wall">wall</a></b>.</p> + +<hr> +Node:<a name="helloworld">hello world</a>, Next:<a rel="next" +href="#hex">hex</a>, Previous:<a rel="previous" href="#hellowall">hello wall!</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hello world</b> interj.</p> + +<p>1. The canonical minimal test message in the C/Unix universe. +2. Any of the minimal programs that emit this message. +Traditionally, the first program a C coder is supposed to write +in a new environment is one that just prints "hello, world" to +standard output (and indeed it is the first example program in +<b><a href="#KandR">K&R</a></b>). Environments that +generate an unreasonably large executable for this trivial test +or which require a <b><a href="#hairy">hairy</a></b> +compiler-linker invocation to generate it are considered to <b><a +href="#lose">lose</a></b> (see <b><a href="#X">X</a></b>). 3. +Greeting uttered by a hacker making an entrance or requesting +information from anyone present. "Hello, world! Is the LAN back +up yet?"</p> + +<hr> +Node:<a name="hex">hex</a>, Next:<a rel="next" href="#hexadecimal">hexadecimal</a>, Previous:<a rel="previous" href="#helloworld">hello world</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hex</b> n.</p> + +<p>1. Short for <b><a href="#hexadecimal">hexadecimal</a></b>, +base 16. 2. A 6-pack of anything (compare <b><a href="#quad">quad</a></b>, sense 2). Neither usage has anything to do +with <b><a href="#magic">magic</a></b> or <b><a href="#blackart">black art</a></b>, though the pun is appreciated +and occasionally used by hackers. True story: As a joke, some +hackers once offered some surplus ICs for sale to be worn as +protective amulets against hostile magic. The chips were, of +course, hex inverters.</p> + +<hr> +Node:<a name="hexadecimal">hexadecimal</a>, Next:<a rel="next" +href="#hexit">hexit</a>, Previous:<a rel="previous" href="#hex">hex</a>, Up:<a rel="up" href="#chap08">= H =</a> +<br> + + +<p><b>hexadecimal</b> n.</p> + +<p>Base 16. Coined in the early 1960s to replace earlier +`sexadecimal', which was too racy and amusing for stuffy IBM, and +later adopted by the rest of the industry.</p> + +<p>Actually, neither term is etymologically pure. If we take +`binary' to be paradigmatic, the most etymologically correct term +for base 10, for example, is `denary', which comes from `deni' +(ten at a time, ten each), a Latin `distributive' number; the +corresponding term for base-16 would be something like +`sendenary'. `Decimal' is from an ordinal number; the +corresponding prefix for 6 would imply something like +`sextidecimal'. The `sexa-' prefix is Latin but incorrect in this +context, and `hexa-' is Greek. The word `octal' is similarly +incorrect; a correct form would be `octaval' (to go with +decimal), or `octonary' (to go with binary). If anyone ever +implements a base-3 computer, computer scientists will be faced +with the unprecedented dilemma of a choice between two +<i>correct</i> forms; both `ternary' and `trinary' have a claim +to this throne.</p> + +<hr> +Node:<a name="hexit">hexit</a>, Next:<a rel="next" href="#HHOK">HHOK</a>, Previous:<a rel="previous" href="#hexadecimal">hexadecimal</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hexit</b> /hek'sit/ n.</p> + +<p>A hexadecimal digit (0-9, and A-F or a-f). Used by people who +claim that there are only <i>ten</i> digits, dammit; +sixteen-fingered human beings are rather rare, despite what some +keyboard designs might seem to imply (see <b><a href="#space-cadetkeyboard">space-cadet keyboard</a></b>).</p> + +<hr> +Node:<a name="HHOK">HHOK</a>, Next:<a rel="next" href="#HHOS">HHOS</a>, Previous:<a rel="previous" href="#hexit">hexit</a>, Up:<a rel="up" href="#chap08">= H +=</a> <br> + + +<p><b>HHOK</b></p> + +<p>See <b><a href="#hahaonlyserious">ha ha only +serious</a></b>.</p> + +<hr> +Node:<a name="HHOS">HHOS</a>, Next:<a rel="next" href="#hiddenflag">hidden flag</a>, Previous:<a rel="previous" +href="#HHOK">HHOK</a>, Up:<a rel="up" href="#chap08">= H +=</a> <br> + + +<p><b>HHOS</b></p> + +<p>See <b><a href="#hahaonlyserious">ha ha only +serious</a></b>.</p> + +<hr> +Node:<a name="hiddenflag">hidden flag</a>, Next:<a rel="next" +href="#highBit">high bit</a>, Previous:<a rel="previous" href="#HHOS">HHOS</a>, Up:<a rel="up" href="#chap08">= H =</a> +<br> + + +<p><b>hidden flag</b> n.</p> + +<p>[scientific computation] An extra option added to a routine +without changing the calling sequence. For example, instead of +adding an explicit input variable to instruct a routine to give +extra diagnostic output, the programmer might just add a test for +some otherwise meaningless feature of the existing inputs, such +as a negative mass. The use of hidden flags can make a program +very hard to debug and understand, but is all too common wherever +programs are hacked on in a hurry.</p> + +<hr> +Node:<a name="highBit">high bit</a>, Next:<a rel="next" href="#highmoby">high moby</a>, Previous:<a rel="previous" href="#hiddenflag">hidden flag</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>high bit</b> n.</p> + +<p>[from `high-order bit'] 1. The most significant bit in a byte. +2. [common] By extension, the most significant part of something +other than a data byte: "Spare me the whole <b><a href="#saga">saga</a></b>, just give me the high bit." See also <b><a +href="#metabit">meta bit</a></b>, <b><a href="#hobbit">hobbit</a></b>, <b><a href="#dreadhighbitdisease">dread high-bit disease</a></b>, and +compare the mainstream slang `bottom line'.</p> + +<hr> +Node:<a name="highmoby">high moby</a>, Next:<a rel="next" +href="#highly">highly</a>, Previous:<a rel="previous" href="#highBit">high bit</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>high moby</b> /hi:' mohb'ee/ n.</p> + +<p>The high half of a 512K <b><a href="#PDP-10">PDP-10</a></b>'s +physical address space; the other half was of course the low +moby. This usage has been generalized in a way that has outlasted +the <b><a href="#PDP-10">PDP-10</a></b>; for example, at the 1990 +Washington D.C. Area Science Fiction Conclave (Disclave), when a +miscommunication resulted in two separate wakes being held in +commemoration of the shutdown of MIT's last <b><a href="#ITS">ITS</a></b> machines, the one on the upper floor was +dubbed the `high moby' and the other the `low moby'. All parties +involved <b><a href="#grok">grok</a></b>ked this instantly. See +<b><a href="#moby">moby</a></b>.</p> + +<hr> +Node:<a name="highly">highly</a>, Next:<a rel="next" href="#hing">hing</a>, Previous:<a rel="previous" href="#highmoby">high moby</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>highly</b> adv.</p> + +<p>[scientific computation] The preferred modifier for +overstating an understatement. As in: `highly nonoptimal', the +worst possible way to do something; `highly nontrivial', either +impossible or requiring a major research project; `highly +nonlinear', completely erratic and unpredictable; `highly +nontechnical', drivel written for <b><a href="#luser">luser</a></b>s, oversimplified to the point of being +misleading or incorrect (compare <b><a href="#droolproofpaper">drool-proof paper</a></b>). In other +computing cultures, postfixing of <b><a href="#intheextreme">in the extreme</a></b> might be +preferred.</p> + +<hr> +Node:<a name="hing">hing</a>, Next:<a rel="next" href="#hiredgun">hired gun</a>, Previous:<a rel="previous" href="#highly">highly</a>, Up:<a rel="up" href="#chap08">= H +=</a> <br> + + +<p><b>hing</b> // n.</p> + +<p>[IRC] Fortuitous typo for `hint', now in wide intentional use +among players of <b><a href="#initgame">initgame</a></b>. Compare +<b><a href="#newsfroup">newsfroup</a></b>, <b><a href="#filk">filk</a></b>.</p> + +<hr> +Node:<a name="hiredgun">hired gun</a>, Next:<a rel="next" +href="#hirsute">hirsute</a>, Previous:<a rel="previous" href="#hing">hing</a>, Up:<a rel="up" href="#chap08">= H =</a> +<br> + + +<p><b>hired gun</b> n.</p> + +<p>A contract programmer, as opposed to a full-time staff member. +All the connotations of this term suggested by innumerable +spaghetti Westerns are intentional.</p> + +<hr> +Node:<a name="hirsute">hirsute</a>, Next:<a rel="next" href="#HLL">HLL</a>, Previous:<a rel="previous" href="#hiredgun">hired gun</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hirsute</b> adj.</p> + +<p>Occasionally used humorously as a synonym for <b><a href="#hairy">hairy</a></b>.</p> + +<hr> +Node:<a name="HLL">HLL</a>, Next:<a rel="next" href="#hoarding">hoarding</a>, Previous:<a rel="previous" href="#hirsute">hirsute</a>, Up:<a rel="up" href="#chap08">= H +=</a> <br> + + +<p><b>HLL</b> /H-L-L/ n.</p> + +<p>[High-Level Language (as opposed to assembler)] Found +primarily in email and news rather than speech. Rarely, the +variants `VHLL' and `MLL' are found. VHLL stands for +`Very-High-Level Language' and is used to describe a <b><a href="#bondage-and-disciplinelanguage">bondage-and-discipline +language</a></b> that the speaker happens to like; Prolog and +Backus's FP are often called VHLLs. `MLL' stands for +`Medium-Level Language' and is sometimes used half-jokingly to +describe <b><a href="#C">C</a></b>, alluding to its +`structured-assembler' image. See also <b><a href="#languagesofchoice">languages of choice</a></b>.</p> + +<hr> +Node:<a name="hoarding">hoarding</a>, Next:<a rel="next" href="#hobbit">hobbit</a>, Previous:<a rel="previous" href="#HLL">HLL</a>, Up:<a rel="up" href="#chap08">= H =</a> +<br> + + +<p><b>hoarding</b> n.</p> + +<p>See <b><a href="#softwarehoarding">software +hoarding</a></b>.</p> + +<hr> +Node:<a name="hobbit">hobbit</a>, Next:<a rel="next" href="#hog">hog</a>, Previous:<a rel="previous" href="#hoarding">hoarding</a>, Up:<a rel="up" href="#chap08">= +H =</a> <br> + + +<p><b>hobbit</b> n.</p> + +<p> +1. [rare] The High Order BIT of a byte; same as the <b><a +href="#metabit">meta bit</a></b> or <b><a href="#highBit">high +bit</a></b>. 2. The non-ITS name of vad@ai.mit.edu (*Hobbit*), master of +lasers. +</p> + +<hr> +Node:<a name="hog">hog</a>, Next:<a rel="next" href="#hole">hole</a>, Previous:<a rel="previous" href="#hobbit">hobbit</a>, Up:<a rel="up" href="#chap08">= H +=</a> <br> + + +<p><b>hog</b> n.,vt.</p> + +<p>1. Favored term to describe programs or hardware that seem to +eat far more than their share of a system's resources, esp. those +which noticeably degrade interactive response. <i>Not</i> used +of programs that are simply extremely large or complex or that +are merely painfully slow themselves. More often than not +encountered in qualified forms, e.g., `memory hog', `core hog', +`hog the processor', `hog the disk'. "A controller that never +gives up the I/O bus gets killed after the bus-hog timer +expires." 2. Also said of <i>people</i> who use more than their +fair share of resources (particularly disk, where it seems that +10% of the people use 90% of the disk, no matter how big the disk +is or how many people use it). Of course, once disk hogs fill up +one filesystem, they typically find some other new one to infect, +claiming to the sysadmin that they have an important new project +to complete.</p> + +<hr> +Node:<a name="hole">hole</a>, Next:<a rel="next" href="#hollised">hollised</a>, Previous:<a rel="previous" href="#hog">hog</a>, Up:<a rel="up" href="#chap08">= H =</a> +<br> + + +<p><b>hole</b> n.</p> + +<p>A region in an otherwise <b><a href="#flat">flat</a></b> +entity which is not actually present. For example, some Unix +filesystems can store large files with holes so that unused +regions of the file are never actually stored on disk. (In +techspeak, these are referred to as `sparse' files.) As another +example, the region of memory in IBM PCs reserved for +memory-mapped I/O devices which may not actually be present is +called `the I/O hole', since memory-management systems must skip +over this area when filling user requests for memory.</p> + +<hr> +Node:<a name="hollised">hollised</a>, Next:<a rel="next" href="#holywars">holy wars</a>, Previous:<a rel="previous" href="#hole">hole</a>, Up:<a rel="up" href="#chap08">= H =</a> +<br> + + +<p><b>hollised</b> /hol'ist/ adj.</p> + +<p>[Usenet: <i>sci.space</i>] To be hollised is to have been +ordered by one's employer not to post any even remotely +job-related material to Usenet (or, by extension, to other +Internet media). The original and most notorious case of this +involved one Ken Hollis, a Lockheed employee and space-program +enthusiast who posted publicly available material on access to +Space Shuttle launches to <i>sci.space</i>. He was gagged under +threat of being fired in 1994 at the behest of NASA +public-relations officers. The result was, of course, a huge +publicity black eye for NASA. Nevertheless several other NASA +contractor employees were subsequently hollised for similar +activities. Use of this term carries the strong connotation that +the persons doing the gagging are bureaucratic idiots blinded to +their own best interests by territorial reflexes.</p> + +<hr> +Node:<a name="holywars">holy wars</a>, Next:<a rel="next" +href="#homebox">home box</a>, Previous:<a rel="previous" href="#hollised">hollised</a>, Up:<a rel="up" href="#chap08">= +H =</a> <br> + + +<p><b>holy wars</b> n.</p> + +<p>[from <b><a href="#Usenet">Usenet</a></b>, but may predate it; +common] n. <b><a href="#flamewarr">flame war</a></b>s over +<b><a href="#religiousissues">religious issues</a></b>. The +paper by Danny Cohen that popularized the terms <b><a href="#big-endian">big-endian</a></b> and <b><a href="#little-endian">little-endian</a></b> in connection with the +LSB-first/MSB-first controversy was entitled "On Holy Wars and a +Plea for Peace".</p> + +<p>Great holy wars of the past have included <b><a href="#ITS">ITS</a></b> vs. <b><a href="#Unix">Unix</a></b>, <b><a +href="#Unix">Unix</a></b> vs. <b><a href="#VMS">VMS</a></b>, +<b><a href="#BSD">BSD</a></b> Unix vs. <b><a href="#USGUnix">USG Unix</a></b>, <b><a href="#C">C</a></b> vs. +<b><a href="#Pascal">Pascal</a></b>, <b><a href="#C">C</a></b> +vs. FORTRAN, etc. In the year 2000, popular favorites of the day +are KDE vs, GNOME, vim vs. elvis, Linux vs. [Free|Net|Open]BSD. +Hardy perennials include <b><a href="#EMACS">EMACS</a></b> vs. +<b><a href="#vi">vi</a></b>, my personal computer vs. everyone +else's personal computer, ad nauseam. The characteristic that +distinguishes holy wars from normal technical disputes is that in +a holy war most of the participants spend their time trying to +pass off personal value choices and cultural attachments as +objective technical evaluations. This happens precisely because +in a true holy war, the actual substantive differences between +the sides are relatively minor. See also <b><a href="#theology">theology</a></b>.</p> + +<hr> +Node:<a name="homebox">home box</a>, Next:<a rel="next" href="#homemachine">home machine</a>, Previous:<a rel="previous" +href="#holywars">holy wars</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>home box</b> n.</p> + +<p>A hacker's personal machine, especially one he or she owns. +"Yeah? Well, <i>my</i> home box runs a full 4.4 BSD, so +there!"</p> + +<hr> +Node:<a name="homemachine">home machine</a>, Next:<a rel="next" href="#homePage">home page</a>, Previous:<a rel="previous" href="#homebox">home box</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>home machine</b> n.</p> + +<p>1. Syn. <b><a href="#homebox">home box</a></b>. 2. The +machine that receives your email. These senses might be distinct, +for example, for a hacker who owns one computer at home, but +reads email at work.</p> + +<hr> +Node:<a name="homePage">home page</a>, Next:<a rel="next" +href="#honeypot">honey pot</a>, Previous:<a rel="previous" +href="#homemachine">home machine</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>home page</b> n.</p> + +<p>1. One's personal billboard on the World Wide Web. The term +`home page' is perhaps a bit misleading because home directories +and physical homes in <b><a href="#RL">RL</a></b> are private, +but home pages are designed to be very public. 2. By extension, a +WWW repository for information and links related to a project or +organization. Compare <b><a href="#homebox">home +box</a></b>.</p> + +<hr> +Node:<a name="honeypot">honey pot</a>, Next:<a rel="next" +href="#hook">hook</a>, Previous:<a rel="previous" href="#homePage">home page</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>honey pot</b> n.</p> + +<p>A box designed to attract <b><a href="#cracker">cracker</a></b>s so that they can be observed in +action. It is usually well isolated from the rest of the network, +but has extensive logging (usually network layer, on a different +machine). Different from an <b><a href="#ironbox">iron +box</a></b> in that it's purpose is to attract, not merely +observe. Sometimes, it is also a defensive network security +tactic - you set up an easy-to-crack box so that your real +servers don't get messed with. The concept was presented in +Cheswick & Bellovin's book "Firewalls and Internet +Security".</p> + +<hr> +Node:<a name="hook">hook</a>, Next:<a rel="next" href="#hop">hop</a>, Previous:<a rel="previous" href="#honeypot">honey pot</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hook</b> n.</p> + +<p>A software or hardware feature included in order to simplify +later additions or changes by a user. For example, a simple +program that prints numbers might always print them in base 10, +but a more flexible version would let a variable determine what +base to use; setting the variable to 5 would make the program +print numbers in base 5. The variable is a simple hook. An even +more flexible program might examine the variable and treat a +value of 16 or less as the base to use, but treat any other +number as the address of a user-supplied routine for printing a +number. This is a <b><a href="#hairy">hairy</a></b> but powerful +hook; one can then write a routine to print numbers as Roman +numerals, say, or as Hebrew characters, and plug it into the +program through the hook. Often the difference between a good +program and a superb one is that the latter has useful hooks in +judiciously chosen places. Both may do the original job about +equally well, but the one with the hooks is much more flexible +for future expansion of capabilities (<b><a href="#EMACS">EMACS</a></b>, for example, is <i>all</i> hooks). The +term `user exit' is synonymous but much more formal and less +hackish.</p> + +<hr> +Node:<a name="hop">hop</a>, Next:<a rel="next" href="#hose">hose</a>, Previous:<a rel="previous" href="#hook">hook</a>, Up:<a rel="up" href="#chap08">= H =</a> +<br> + + +<p><b>hop</b></p> + +<p>1. n. [common] One file transmission in a series required to +get a file from point A to point B on a store-and-forward +network. On such networks (including <b><a href="#UUCPNET">UUCPNET</a></b> and <b><a href="#FidoNet">FidoNet</a></b>), an important inter-machine metric is +the number of hops in the shortest path between them, which can +be more significant than their geographical separation. See <b><a +href="#bangpath">bang path</a></b>. 2. v. [rare] To log in to +a remote machine, esp. via rlogin or telnet. "I'll hop over to +foovax to FTP that."</p> + +<hr> +Node:<a name="hose">hose</a>, Next:<a rel="next" href="#hosed">hosed</a>, Previous:<a rel="previous" href="#hop">hop</a>, Up:<a rel="up" href="#chap08">= H =</a> +<br> + + +<p><b>hose</b></p> + +<p>1. vt. [common] To make non-functional or greatly degraded in +performance. "That big ray-tracing program really hoses the +system." See <b><a href="#hosed">hosed</a></b>. 2. n. A narrow +channel through which data flows under pressure. Generally +denotes data paths that represent performance bottlenecks. 3. n. +Cabling, especially thick Ethernet cable. This is sometimes +called `bit hose' or `hosery' (play on `hosiery') or `etherhose'. +See also <b><a href="#washingmachine">washing +machine</a></b>.</p> + +<hr> +Node:<a name="hosed">hosed</a>, Next:<a rel="next" href="#hotchat">hot chat</a>, Previous:<a rel="previous" href="#hose">hose</a>, Up:<a rel="up" href="#chap08">= H =</a> +<br> + + +<p><b>hosed</b> adj.</p> + +<p>Same as <b><a href="#down">down</a></b>. Used primarily by +Unix hackers. Humorous: also implies a condition thought to be +relatively easy to reverse. Probably derived from the Canadian +slang `hoser' popularized by the Bob and Doug Mackenzie skits on +SCTV, but this usage predated SCTV by years in hackerdom (it was +certainly already live at CMU in the 1970s). See <b><a href="#hose">hose</a></b>. It is also widely used of people in the +mainstream sense of `in an extremely unfortunate situation'.</p> + +<p>Once upon a time, a Cray that had been experiencing periodic +difficulties crashed, and it was announced to have been hosed. It +was discovered that the crash was due to the disconnection of +some coolant hoses. The problem was corrected, and users were +then assured that everything was OK because the system had been +rehosed. See also <b><a href="#dehose">dehose</a></b>.</p> + +<hr> +Node:<a name="hotchat">hot chat</a>, Next:<a rel="next" href="#hotspot">hot spot</a>, Previous:<a rel="previous" href="#hosed">hosed</a>, Up:<a rel="up" href="#chap08">= H +=</a> <br> + + +<p><b>hot chat</b> n.</p> + +<p>Sexually explicit one-on-one chat. See <b><a href="#teledildonics">teledildonics</a></b>.</p> + +<hr> +Node:<a name="hotspot">hot spot</a>, Next:<a rel="next" href="#hotlink">hotlink</a>, Previous:<a rel="previous" href="#hotchat">hot chat</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hot spot</b> n.</p> + +<p>1. [primarily used by C/Unix programmers, but spreading] It is +received wisdom that in most programs, less than 10% of the code +eats 90% of the execution time; if one were to graph instruction +visits versus code addresses, one would typically see a few huge +spikes amidst a lot of low-level noise. Such spikes are called +`hot spots' and are good candidates for heavy optimization or +<b><a href="#hand-hacking">hand-hacking</a></b>. The term is +especially used of tight loops and recursions in the code's +central algorithm, as opposed to (say) initial set-up costs or +large but infrequent I/O operations. See <b><a href="#tune">tune</a></b>, <b><a href="#bum">bum</a></b>, <b><a href="#hand-hacking">hand-hacking</a></b>. 2. The active location of a +cursor on a bit-map display. "Put the mouse's hot spot on the +`ON' widget and click the left button." 3. A screen region that +is sensitive to mouse gestures, which trigger some action. World +Wide Web pages now provide the <b><a href="#canonical">canonical</a></b> examples; WWW browsers present +hypertext links as hot spots which, when clicked on, point the +browser at another document (these are specifically called <b><a +href="#hotlink">hotlink</a></b>s). 4. In a massively parallel +computer with shared memory, the one location that all 10,000 +processors are trying to read or write at once (perhaps because +they are all doing a <b><a href="#busy-wait">busy-wait</a></b> on +the same lock). 5. More generally, any place in a hardware design +that turns into a performance bottleneck due to resource +contention.</p> + +<hr> +Node:<a name="hotlink">hotlink</a>, Next:<a rel="next" href="#housewizard">house wizard</a>, Previous:<a rel="previous" +href="#hotspot">hot spot</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hotlink</b> /hot'link/ n.</p> + +<p>A <b><a href="#hotspot">hot spot</a></b> on a World Wide +Web page; an area, which, when clicked or selected, chases a URL. +Also spelled `hot link'. Use of this term focuses on the link's +role as an immediate part of your display, as opposed to the +timeless sense of logical connection suggested by <b><a href="#webpointer">web pointer</a></b>. Your screen shows hotlinks +but your document has web pointers, not (in normal usage) the +other way around.</p> + +<hr> +Node:<a name="housewizard">house wizard</a>, Next:<a rel="next" href="#HP-SUX">HP-SUX</a>, Previous:<a rel="previous" +href="#hotlink">hotlink</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>house wizard</b> n.</p> + +<p>[prob. from ad-agency tradetalk, `house freak'] A hacker +occupying a technical-specialist, R&D, or systems position at +a commercial shop. A really effective house wizard can have +influence out of all proportion to his/her ostensible rank and +still not have to wear a suit. Used esp. of Unix wizards. The +term `house guru' is equivalent.</p> + +<hr> +Node:<a name="HP-SUX">HP-SUX</a>, Next:<a rel="next" href="#HTH">HTH</a>, Previous:<a rel="previous" href="#housewizard">house wizard</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>HP-SUX</b> /H-P suhks/ n.</p> + +<p>Unflattering hackerism for HP-UX, Hewlett-Packard's Unix port, +which features some truly unique bogosities in the filesystem +internals and elsewhere (these occasionally create portability +problems). HP-UX is often referred to as `hockey-pux' inside HP, +and one respondent claims that the proper pronunciation is /H-P +ukkkhhhh/ as though one were about to spit. Another such +alternate spelling and pronunciation is "H-PUX" /H-puhks/. +Hackers at HP/Apollo (the former Apollo Computers which was +swallowed by HP in 1989) have been heard to complain that Mr. +Packard should have pushed to have his name first, if for no +other reason than the greater eloquence of the resulting acronym. +Compare <b><a href="#AIDX">AIDX</a></b>, <b><a href="#buglix">buglix</a></b>. See also <b><a href="#NominalSemidestructor">Nominal Semidestructor</a></b>, <b><a +href="#Telerat">Telerat</a></b>, <b><a href="#ScumOS">ScumOS</a></b>, <b><a href="#sun-stools">sun-stools</a></b>, <b><a href="#Slowlaris">Slowlaris</a></b>.</p> + +<hr> +Node:<a name="HTH">HTH</a>, Next:<a rel="next" href="#huff">huff</a>, Previous:<a rel="previous" href="#HP-SUX">HP-SUX</a>, Up:<a rel="up" href="#chap08">= H +=</a> <br> + + +<p><b>HTH</b> //</p> + +<p>[Usenet: very common] Abbreviation: Hope This Helps (e.g. +following a response to a technical question). Often used just +before <b><a href="#HAND">HAND</a></b>. See also <b><a href="#YHBT">YHBT</a></b>.</p> + +<hr> +Node:<a name="huff">huff</a>, Next:<a rel="next" href="#humma">humma</a>, Previous:<a rel="previous" href="#HTH">HTH</a>, Up:<a rel="up" href="#chap08">= H =</a> +<br> + + +<p><b>huff</b> v.</p> + +<p>To compress data using a Huffman code. Various programs that +use such methods have been called `HUFF' or some variant thereof. +Oppose <b><a href="#puff">puff</a></b>. Compare <b><a href="#crunch">crunch</a></b>, <b><a href="#compress">compress</a></b>.</p> + +<hr> +Node:<a name="humma">humma</a>, Next:<a rel="next" href="#hung">hung</a>, Previous:<a rel="previous" href="#huff">huff</a>, Up:<a rel="up" href="#chap08">= H =</a> +<br> + + +<p><b>humma</b> // excl.</p> + +<p>A filler word used on various `chat' and `talk' programs when +you had nothing to say but felt that it was important to say +something. The word apparently originated (at least with this +definition) on the MECC Timeshare System (MTS, a now-defunct +educational time-sharing system running in Minnesota during the +1970s and the early 1980s) but was later sighted on early Unix +systems. Compare the U.K's <b><a href="#wibble">wibble</a></b>.</p> + +<hr> +Node:<a name="hung">hung</a>, Next:<a rel="next" href="#hungrypuppy">hungry puppy</a>, Previous:<a rel="previous" +href="#humma">humma</a>, Up:<a rel="up" href="#chap08">= H +=</a> <br> + + +<p><b>hung</b> adj.</p> + +<p>[from `hung up'; common] Equivalent to <b><a href="#wedged">wedged</a></b>, but more common at Unix/C sites. Not +generally used of people. Syn. with <b><a href="#lockedup">locked up</a></b>, <b><a href="#wedged">wedged</a></b>; compare <b><a href="#hosed">hosed</a></b>. See also <b><a href="#hang">hang</a></b>. +A hung state is distinguished from <b><a href="#crash">crash</a></b>ed or <b><a href="#down">down</a></b>, +where the program or system is also unusable but because it is +not running rather than because it is waiting for something. +However, the recovery from both situations is often the same. It +is also distinguished from the similar but more drastic state +<b><a href="#wedged">wedged</a></b> - hung software can be woken +up with easy things like interrupt keys, but wedged will need a +kill -9 or even reboot.</p> + +<hr> +Node:<a name="hungrypuppy">hungry puppy</a>, Next:<a rel="next" href="#hungus">hungus</a>, Previous:<a rel="previous" +href="#hung">hung</a>, Up:<a rel="up" href="#chap08">= H +=</a> <br> + + +<p><b>hungry puppy</b> n.</p> + +<p>Syn. <b><a href="#slopsucker">slopsucker</a></b>.</p> + +<hr> +Node:<a name="hungus">hungus</a>, Next:<a rel="next" href="#hyperspace">hyperspace</a>, Previous:<a rel="previous" href="#hungrypuppy">hungry puppy</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hungus</b> /huhng'g*s/ adj.</p> + +<p>[perhaps related to slang `humongous'] Large, unwieldy, +usually unmanageable. "TCP is a hungus piece of code." "This is a +hungus set of modifications." The <b><a href="#Infocom">Infocom</a></b> text adventure game "Beyond Zork" +included two monsters called hunguses.</p> + +<hr> +Node:<a name="hyperspace">hyperspace</a>, Next:<a rel="next" +href="#hystericalreasons">hysterical reasons</a>, Previous:<a +rel="previous" href="#hungus">hungus</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hyperspace</b> /hi:'per-spays/ n.</p> + +<p>A memory location that is <i>far</i> away from where the +program counter should be pointing, especially a place that is +inaccessible because it is not even mapped in by the +virtual-memory system. "Another core dump -- looks like the +program jumped off to hyperspace somehow." (Compare <b><a href="#jumpoffintoneverneverland">jump off into +never-never land</a></b>.) This usage is from the SF notion of a +spaceship jumping `into hyperspace', that is, taking a shortcut +through higher-dimensional space -- in other words, bypassing +this universe. The variant `east hyperspace' is recorded among +CMU and Bliss hackers.</p> + +<hr> +Node:<a name="hystericalreasons">hysterical reasons</a>, +Next:<a rel="next" href="#Ididntchangeanything">I +didn't change anything!</a>, Previous:<a rel="previous" href="#hyperspace">hyperspace</a>, Up:<a rel="up" href="#chap08">= H =</a> <br> + + +<p><b>hysterical reasons</b> n.</p> + +<p>(also `hysterical raisins') A variant on the stock phrase "for +historical reasons", indicating specifically that something must +be done in some stupid way for backwards compatibility, and +moreover that the feature it must be compatible with was the +result of a bad design in the first place. "All IBM PC video +adapters have to support MDA text mode for hysterical reasons." +Compare <b><a href="#bug-for-bugcompatible">bug-for-bug +compatible</a></b>.</p> + +<hr> +Node:<a name="chap09">= I =</a>, Next:<a rel="next" href="#chap10">= J =</a>, Previous:<a rel="previous" href="#chap08">= H =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= I =</h2> + +<ul> +<li><a href="#Ididntchangeanything">I didn't change +anything!</a>:</li> + +<li><a href="#IseenoXhere">I see no X +here.</a>:</li> + +<li><a href="#IANAL">IANAL</a>:</li> + +<li><a href="#IBM">IBM</a>:</li> + +<li><a href="#IBMdiscount">IBM discount</a>:</li> + +<li><a href="#ICBMaddress">ICBM address</a>:</li> + +<li><a href="#ice">ice</a>:</li> + +<li><a href="#ID10Terror">ID10T error</a>:</li> + +<li><a href="#idempotent">idempotent</a>:</li> + +<li><a href="#IDP">IDP</a>:</li> + +<li><a href="#IfyouwantXyouknowwheretofindit.">If +you want X you know where to find it.</a>:</li> + +<li><a href="#ifdefout">ifdef out</a>:</li> + +<li><a href="#IIRC">IIRC</a>:</li> + +<li><a href="#ill-behaved">ill-behaved</a>:</li> + +<li><a href="#IMHO">IMHO</a>:</li> + +<li><a href="#ImminentDeathOfTheNetPredicted">Imminent Death +Of The Net Predicted!</a>:</li> + +<li><a href="#intheextreme">in the extreme</a>:</li> + +<li><a href="#inc">inc</a>:</li> + +<li><a href="#incantation">incantation</a>:</li> + +<li><a href="#include">include</a>:</li> + +<li><a href="#includewar">include war</a>:</li> + +<li><a href="#indentstyle">indent style</a>:</li> + +<li><a href="#indexofX">index of X</a>:</li> + +<li><a href="#infantmortality">infant mortality</a>:</li> + +<li><a href="#infinite">infinite</a>:</li> + +<li><a href="#infiniteloop">infinite loop</a>:</li> + +<li><a href="#InfiniteMonkeyTheorem">Infinite-Monkey +Theorem</a>:</li> + +<li><a href="#infinity">infinity</a>:</li> + +<li><a href="#inflate">inflate</a>:</li> + +<li><a href="#Infocom">Infocom</a>:</li> + +<li><a href="#initgame">initgame</a>:</li> + +<li><a href="#insanelygreat">insanely great</a>:</li> + +<li><a href="#installfest">installfest</a>:</li> + +<li><a href="#INTERCAL">INTERCAL</a>:</li> + +<li><a href="#interesting">interesting</a>:</li> + +<li><a href="#Internet">Internet</a>:</li> + +<li><a href="#Internetaddress">Internet address</a>:</li> + +<li><a href="#InternetDeathPenalty">Internet Death +Penalty</a>:</li> + +<li><a href="#InternetExploder">Internet Exploder</a>:</li> + +<li><a href="#InternetExploiter">Internet Exploiter</a>:</li> + +<li><a href="#interrupt">interrupt</a>:</li> + +<li><a href="#interruptlist">interrupt list</a>:</li> + +<li><a href="#interruptslockedout">interrupts locked +out</a>:</li> + +<li><a href="#intro">intro</a>:</li> + +<li><a href="#IRC">IRC</a>:</li> + +<li><a href="#iron">iron</a>:</li> + +<li><a href="#IronAge">Iron Age</a>:</li> + +<li><a href="#ironbox">iron box</a>:</li> + +<li><a href="#ironmonger">ironmonger</a>:</li> + +<li><a href="#ISOstandardcupoftea">ISO standard cup +of tea</a>:</li> + +<li><a href="#ISP">ISP</a>:</li> + +<li><a href="#ITS">ITS</a>:</li> + +<li><a href="#IWBNI">IWBNI</a>:</li> + +<li><a href="#IYFEG">IYFEG</a>:</li> +</ul> + +<hr> +Node:<a name="Ididntchangeanything">I didn't change +anything!</a>, Next:<a rel="next" href="#IseenoXhere">I see no X here.</a>, Previous:<a +rel="previous" href="#hystericalreasons">hysterical +reasons</a>, Up:<a rel="up" href="#chap09">= I =</a> <br> + + +<p><b>I didn't change anything!</b> interj.</p> + +<p>An aggrieved cry often heard as bugs manifest during a +regression test. The <b><a href="#canonical">canonical</a></b> +reply to this assertion is "Then it works just the same as it did +before, doesn't it?" See also <b><a href="#onelinefix">one-line fix</a></b>. This is also heard from +applications programmers trying to blame an obvious applications +problem on an unrelated systems software change, for example a +divide-by-0 fault after terminals were added to a network. +Usually, their statement is found to be false. Upon close +questioning, they will admit some major restructuring of the +program that shouldn't have broken anything, in their opinion, +but which actually <b><a href="#hosed">hosed</a></b> the code +completely.</p> + +<hr> +Node:<a name="IseenoXhere">I see no X here.</a>, +Next:<a rel="next" href="#IANAL">IANAL</a>, Previous:<a rel="previous" href="#Ididntchangeanything">I didn't +change anything!</a>, Up:<a rel="up" href="#chap09">= I +=</a> <br> + + +<p><b>I see no X here.</b></p> + +<p>Hackers (and the interactive computer games they write) +traditionally favor this slightly marked usage over other +possible equivalents such as "There's no X here!" or "X is +missing." or "Where's the X?". This goes back to the original +PDP-10 <b><a href="#ADVENT">ADVENT</a></b>, which would respond +in this wise if you asked it to do something involving an object +not present at your location in the game.</p> + +<hr> +Node:<a name="IANAL">IANAL</a>, Next:<a rel="next" href="#IBM">IBM</a>, Previous:<a rel="previous" href="#IseenoXhere">I see no X here.</a>, Up:<a rel="up" +href="#chap09">= I =</a> <br> + + +<p><b>IANAL</b> //</p> + +<p>[Usenet] Abbreviation, "I Am Not A Lawyer". Usually precedes +legal advice.</p> + +<hr> +Node:<a name="IBM">IBM</a>, Next:<a rel="next" href="#IBMdiscount">IBM discount</a>, Previous:<a rel="previous" +href="#IANAL">IANAL</a>, Up:<a rel="up" href="#chap09">= I +=</a> <br> + + +<p><b>IBM</b> /I-B-M/</p> + +<p>Inferior But Marketable; It's Better Manually; Insidious Black +Magic; It's Been Malfunctioning; Incontinent Bowel Movement; and +a near-<b><a href="#infinite">infinite</a></b> number of even +less complimentary expansions, including `International Business +Machines'. See <b><a href="#TLA">TLA</a></b>. These abbreviations +illustrate the considerable antipathy most hackers long felt +toward the `industry leader' (see <b><a href="#fearandloathing">fear and loathing</a></b>).</p> + +<p>What galled hackers about most IBM machines above the PC level +wasn't so much that they were underpowered and overpriced (though +that does count against them), but that the designs are +incredibly archaic, <b><a href="#crufty">crufty</a></b>, and +<b><a href="#elephantine">elephantine</a></b> <small>...</small> +and you can't <i>fix</i> them -- source code is locked up +tight, and programming tools are expensive, hard to find, and +bletcherous to use once you've found them. For many years, before +Microsoft, IBM was the company hackers loved to hate.</p> + +<p>But everything changes. In the 1980s IBM had its own troubles +with Microsoft. In the late 1990s IBM re-invented itself as a +services company, began to release open-source software through +its AlphaWorks group, and began shipping <b><a href="#Linux">Linux</a></b> systems and building ties to the Linux +community. To the astonishment of all parties, IBM emerged as a +friend of the hacker community</p> + +<p>This lexicon includes a number of entries attributed to `IBM'; +these derive from some rampantly unofficial jargon lists +circulated within IBM's own beleaguered hacker underground.</p> + +<hr> +Node:<a name="IBMdiscount">IBM discount</a>, Next:<a rel="next" href="#ICBMaddress">ICBM address</a>, Previous:<a rel="previous" href="#IBM">IBM</a>, Up:<a rel="up" href="#chap09">= I =</a> <br> + + +<p><b>IBM discount</b> n.</p> + +<p>A price increase. Outside IBM, this derives from the common +perception that IBM products are generally overpriced (see <b><a +href="#clone">clone</a></b>); inside, it is said to spring from a +belief that large numbers of IBM employees living in an area +cause prices to rise.</p> + +<hr> +Node:<a name="ICBMaddress">ICBM address</a>, Next:<a rel="next" href="#ice">ice</a>, Previous:<a rel="previous" href="#IBMdiscount">IBM discount</a>, Up:<a rel="up" href="#chap09">= I =</a> <br> + + +<p><b>ICBM address</b> n.</p> + +<p>(Also `missile address') The form used to register a site with +the Usenet mapping project, back before the day of pervasive +Internet, included a blank for longitude and latitude, preferably +to seconds-of-arc accuracy. This was actually used for generating +geographically-correct maps of Usenet links on a plotter; +however, it became traditional to refer to this as one's `ICBM +address' or `missile address', and some people include it in +their <b><a href="#sigblock">sig block</a></b> with that name. +(A real missile address would include target elevation.)</p> + +<hr> +Node:<a name="ice">ice</a>, Next:<a rel="next" href="#ID10Terror">ID10T error</a>, Previous:<a rel="previous" +href="#ICBMaddress">ICBM address</a>, Up:<a rel="up" href="#chap09">= I =</a> <br> + + +<p><b>ice</b> n.</p> + +<p>[coined by Usenetter Tom Maddox, popularized by William +Gibson's cyberpunk SF novels: a contrived acronym for `Intrusion +Countermeasure Electronics'] Security software (in Gibson's +novels, software that responds to intrusion by attempting to +immobilize or even literally kill the intruder). Hence, +`icebreaker': a program designed for cracking security on a +system.</p> + +<p>Neither term is in serious use yet as of early 1999, but many +hackers find the metaphor attractive, and each may develop a +denotation in the future. In the meantime, the speculative usage +could be confused with `ICE', an acronym for "in-circuit +emulator".</p> + +<p>In ironic reference to the speculative usage, however, some +hackers and computer scientists formed ICE (International +Cryptographic Experiment) in 1994. ICE is a consortium to promote +uniform international access to strong cryptography.</p> + +<hr> +Node:<a name="ID10Terror">ID10T error</a>, Next:<a rel="next" +href="#idempotent">idempotent</a>, Previous:<a rel="previous" +href="#ice">ice</a>, Up:<a rel="up" href="#chap09">= I +=</a> <br> + + +<p><b>ID10T error</b> /I-D-ten-T er'*r/</p> + +<p>Synonym for <b><a href="#PEBKAC">PEBKAC</a></b>, e.g. "The +user is being an idiot". Tech-support people passing a problem +report to someone higher up the food chain (and presumably better +equipped to deal with idiots) may ask the user to convey that +there seems to be an I-D-ten-T error. Users never twig.</p> + +<hr> +Node:<a name="idempotent">idempotent</a>, Next:<a rel="next" +href="#IDP">IDP</a>, Previous:<a rel="previous" href="#ID10Terror">ID10T error</a>, Up:<a rel="up" href="#chap09">= I =</a> <br> + + +<p><b>idempotent</b> adj.</p> + +<p>[from mathematical techspeak] Acting as if used only once, +even if used multiple times. This term is often used with respect +to <b><a href="#C">C</a></b> header files, which contain common +definitions and declarations to be included by several source +files. If a header file is ever included twice during the same +compilation (perhaps due to nested #include files), compilation +errors can result unless the header file has protected itself +against multiple inclusion; a header file so protected is said to +be idempotent. The term can also be used to describe an +initialization subroutine that is arranged to perform some +critical action exactly once, even if the routine is called +several times.</p> + +<hr> +Node:<a name="IDP">IDP</a>, Next:<a rel="next" href="#IfyouwantXyouknowwheretofindit.">If +you want X you know where to find it.</a>, Previous:<a rel="previous" href="#idempotent">idempotent</a>, Up:<a rel="up" +href="#chap09">= I =</a> <br> + + +<p><b>IDP</b> /I-D-P/ v.,n.</p> + +<p>[Usenet] Abbreviation for <b><a href="#InternetDeathPenalty">Internet Death Penalty</a></b>. +Common (probably now more so than the full form), and frequently +verbed. Compare <b><a href="#UDP">UDP</a></b>.</p> + +<hr> +Node:<a name="IfyouwantXyouknowwheretofindit.">If +you want X you know where to find it.</a>, Next:<a rel="next" +href="#ifdefout">ifdef out</a>, Previous:<a rel="previous" +href="#IDP">IDP</a>, Up:<a rel="up" href="#chap09">= I +=</a> <br> + + +<p><b>If you want X, you know where to find it.</b></p> + +<p>There is a legend that Dennis Ritchie, inventor of <b><a href="#C">C</a></b>, once responded to demands for features resembling +those of what at the time was a much more popular language by +observing "If you want PL/I, you know where to find it." Ever +since, this has been hackish standard form for fending off +requests to alter a new design to mimic some older (and, by +implication, inferior and <b><a href="#baroque">baroque</a></b>) +one. The case X = <b><a href="#Pascal">Pascal</a></b> manifests +semi-regularly on Usenet's <i>comp.lang.c</i> newsgroup. Indeed, +the case X = X has been reported in discussions of graphics +software (see <b><a href="#X">X</a></b>).</p> + +<hr> +Node:<a name="ifdefout">ifdef out</a>, Next:<a rel="next" +href="#IIRC">IIRC</a>, Previous:<a rel="previous" href="#IfyouwantXyouknowwheretofindit.">If +you want X you know where to find it.</a>, Up:<a rel="up" href="#chap09">= I =</a> <br> + + +<p><b>ifdef out</b> /if'def owt/ v.</p> + +<p>Syn. for <b><a href="#conditionout">condition out</a></b>, +specific to <b><a href="#C">C</a></b>.</p> + +<hr> +Node:<a name="IIRC">IIRC</a>, Next:<a rel="next" href="#ill-behaved">ill-behaved</a>, Previous:<a rel="previous" href="#ifdefout">ifdef out</a>, Up:<a rel="up" href="#chap09">= I =</a> <br> + + +<p><b>IIRC</b> //</p> + +<p>Common abbreviation for "If I Recall Correctly".</p> + +<hr> +Node:<a name="ill-behaved">ill-behaved</a>, Next:<a rel="next" +href="#IMHO">IMHO</a>, Previous:<a rel="previous" href="#IIRC">IIRC</a>, Up:<a rel="up" href="#chap09">= I =</a> +<br> + + +<p><b>ill-behaved</b> adj.</p> + +<p>1. [numerical analysis] Said of an algorithm or computational +method that tends to blow up because of accumulated roundoff +error or poor convergence properties. 2. Software that bypasses +the defined <b><a href="#OS">OS</a></b> interfaces to do things +(like screen, keyboard, and disk I/O) itself, often in a way that +depends on the hardware of the machine it is running on or which +is nonportable or incompatible with other pieces of software. In +the IBM PC/MS-DOS world, there is a folk theorem (nearly true) to +the effect that (owing to gross inadequacies and performance +penalties in the OS interface) all interesting applications are +ill-behaved. See also <b><a href="#baremetal">bare +metal</a></b>. Oppose <b><a href="#well-behaved">well-behaved</a></b>, compare <b><a href="#PC-ism">PC-ism</a></b>. See <b><a href="#mess-dos">mess-dos</a></b>.</p> + +<hr> +Node:<a name="IMHO">IMHO</a>, Next:<a rel="next" href="#ImminentDeathOfTheNetPredicted">Imminent Death +Of The Net Predicted!</a>, Previous:<a rel="previous" href="#ill-behaved">ill-behaved</a>, Up:<a rel="up" href="#chap09">= I =</a> <br> + + +<p><b>IMHO</b> // abbrev.</p> + +<p>[from SF fandom via Usenet; abbreviation for `In My Humble +Opinion'] "IMHO, mixed-case C names should be avoided, as +mistyping something in the wrong case can cause hard-to-detect +errors -- and they look too Pascalish anyhow." Also seen in +variant forms such as IMNSHO (In My Not-So-Humble Opinion) and +IMAO (In My Arrogant Opinion).</p> + +<hr> +Node:<a name="ImminentDeathOfTheNetPredicted">Imminent Death +Of The Net Predicted!</a>, Next:<a rel="next" href="#intheextreme">in the extreme</a>, Previous:<a rel="previous" href="#IMHO">IMHO</a>, Up:<a rel="up" href="#chap09">= I =</a> <br> + + +<p><b>Imminent Death Of The Net Predicted!</b> prov.</p> + +<p>[Usenet] Since <b><a href="#Usenet">Usenet</a></b> first got +off the ground in 1980-81, it has grown exponentially, +approximately doubling in size every year. On the other hand, +most people feel the <b><a href="#signaltonoiseratio">signal-to-noise ratio</a></b> of +Usenet has dropped steadily. These trends led, as far back as +mid-1983, to predictions of the imminent collapse (or death) of +the net. Ten years and numerous doublings later, enough of these +gloomy prognostications have been confounded that the phrase +"Imminent Death Of The Net Predicted!" has become a running joke, +hauled out any time someone grumbles about the <b><a href="#SfNratio">S/N ratio</a></b> or the huge and steadily +increasing volume, or the possible loss of a key node or link, or +the potential for lawsuits when ignoramuses post copyrighted +material, etc., etc., etc.</p> + +<hr> +Node:<a name="intheextreme">in the extreme</a>, Next:<a +rel="next" href="#inc">inc</a>, Previous:<a rel="previous" href="#ImminentDeathOfTheNetPredicted">Imminent Death +Of The Net Predicted!</a>, Up:<a rel="up" href="#chap09">= +I =</a> <br> + + +<p><b>in the extreme</b> adj.</p> + +<p>A preferred superlative suffix for many hackish terms. See, +for example, `obscure in the extreme' under <b><a href="#obscure">obscure</a></b>, and compare <b><a href="#highly">highly</a></b>.</p> + +<hr> +Node:<a name="inc">inc</a>, Next:<a rel="next" href="#incantation">incantation</a>, Previous:<a rel="previous" href="#intheextreme">in the extreme</a>, Up:<a rel="up" href="#chap09">= I =</a> <br> + + +<p><b>inc</b> /ink/ v.</p> + +<p>Verbal (and only rarely written) shorthand for +<i>increment</i>, i.e. `increase by one'. Especially used by +assembly programmers, as many assembly languages have an +<code>inc</code> mnemonic. Antonym: dec (see <b><a href="#DEC">DEC</a></b>).</p> + +<hr> +Node:<a name="incantation">incantation</a>, Next:<a rel="next" +href="#include">include</a>, Previous:<a rel="previous" href="#inc">inc</a>, Up:<a rel="up" href="#chap09">= I =</a> +<br> + + +<p><b>incantation</b> n.</p> + +<p>Any particularly arbitrary or obscure command that one must +mutter at a system to attain a desired result. Not used of +passwords or other explicit security features. Especially used of +tricks that are so poorly documented that they must be learned +from a <b><a href="#wizard">wizard</a></b>. "This compiler +normally locates initialized data in the data segment, but if you +<b><a href="#mutter">mutter</a></b> the right incantation they +will be forced into text space."</p> + +<hr> +Node:<a name="include">include</a>, Next:<a rel="next" href="#includewar">include war</a>, Previous:<a rel="previous" +href="#incantation">incantation</a>, Up:<a rel="up" href="#chap09">= I =</a> <br> + + +<p><b>include</b> vt.</p> + +<p>[Usenet] 1. To duplicate a portion (or whole) of another's +message (typically with attribution to the source) in a reply or +followup, for clarifying the context of one's response. See the +discussion of inclusion styles under "Hacker Writing Style". 2. +[from <b><a href="#C">C</a></b>] <code>#include +<disclaimer.h></code> has appeared in <b><a href="#sigblock">sig block</a></b>s to refer to a notional +`standard <b><a href="#disclaimer">disclaimer</a></b> file'.</p> + +<hr> +Node:<a name="includewar">include war</a>, Next:<a rel="next" +href="#indentstyle">indent style</a>, Previous:<a rel="previous" href="#include">include</a>, Up:<a rel="up" href="#chap09">= I =</a> <br> + + +<p><b>include war</b> n.</p> + +<p>Excessive multi-leveled inclusion within a discussion <b><a +href="#thread">thread</a></b>, a practice that tends to annoy +readers. In a forum with high-traffic newsgroups, such as Usenet, +this can lead to <b><a href="#flame">flame</a></b>s and the urge +to start a <b><a href="#killfile">kill file</a></b>.</p> + +<hr> +Node:<a name="indentstyle">indent style</a>, Next:<a rel="next" href="#indexofX">index of X</a>, Previous:<a rel="previous" href="#includewar">include war</a>, Up:<a rel="up" +href="#chap09">= I =</a> <br> + + +<p><b>indent style</b> n.</p> + +<p>[C, C++, and Java programmers] The rules one uses to indent +code in a readable fashion. There are four major C indent styles, +described below; all have the aim of making it easier for the +reader to visually track the scope of control constructs. They +have been inherited by C++ and Java, which have C-like syntaxes. +The significant variable is the placement of <code>{</code> and +<code>}</code> with respect to the statement(s) they enclose and +to the guard or controlling statement (<code>if</code>, +<code>else</code>, <code>for</code>, <code>while</code>, or +<code>do</code>) on the block, if any.</p> + +<p>`K&R style' -- Named after Kernighan & Ritchie, +because the examples in <b><a href="#KandR">K&R</a></b> are +formatted this way. Also called `kernel style' because the Unix +kernel is written in it, and the `One True Brace Style' (abbrev. +1TBS) by its partisans. In C code, the body is typically indented +by eight spaces (or one tab) per level, as shown here. Four +spaces are occasionally seen in C, but in C++ and Java four tends +to be the rule rather than the exception.</p> + +<pre> +if (<cond>) { + <body> +} +</pre> + +<p>`Allman style' -- Named for Eric Allman, a Berkeley hacker who +wrote a lot of the BSD utilities in it (it is sometimes called +`BSD style'). Resembles normal indent style in Pascal and Algol. +It is the only style other than K&R in widespread use among +Java programmers. Basic indent per level shown here is eight +spaces, but four (or sometimes three) spaces are generally +preferred by C++ and Java programmers.</p> + +<pre> +if (<cond>) +{ + <body> +} +</pre> + +<p>`Whitesmiths style' -- popularized by the examples that came +with Whitesmiths C, an early commercial C compiler. Basic indent +per level shown here is eight spaces, but four spaces are +occasionally seen.</p> + +<pre> +if (<cond>) + { + <body> + } +</pre> + +<p>`GNU style' -- Used throughout GNU EMACS and the Free Software +Foundation code, and just about nowhere else. Indents are always +four spaces per level, with <code>{</code> and <code>}</code> +halfway between the outer and inner indent levels.</p> + +<pre> +if (<cond>) + { + <body> + } +</pre> + +<p>Surveys have shown the Allman and Whitesmiths styles to be the +most common, with about equal mind shares. K&R/1TBS used to +be nearly universal, but is now much less common in C (the +opening brace tends to get lost against the right paren of the +guard part in an <code>if</code> or <code>while</code>, which is +a <b><a href="#BadThing">Bad Thing</a></b>). Defenders of 1TBS +argue that any putative gain in readability is less important +than their style's relative economy with vertical space, which +enables one to see more code on one's screen at once.</p> + +<p>The Java Language Specification legislates not only the +capitalization of identifiers, but where nouns, adjectives, and +verbs should be in method, class, interface, and variable names +(section 6.8). While the specification stops short of also +standardizing on a bracing style, all source code originating +from Sun Laboratories uses the K&R style. This has set a +precedent for Java programmers, which most follow.</p> + +<p>Doubtless these issues will continue to be the subject of +<b><a href="#holywars">holy wars</a></b>.</p> + +<hr> +Node:<a name="indexofX">index of X</a>, Next:<a rel="next" +href="#infantmortality">infant mortality</a>, Previous:<a rel="previous" href="#indentstyle">indent style</a>, Up:<a rel="up" href="#chap09">= I =</a> <br> + + +<p><b>index of X</b> n.</p> + +<p>See <b><a href="#coefficientofX">coefficient of +X</a></b>.</p> + +<hr> +Node:<a name="infantmortality">infant mortality</a>, Next:<a +rel="next" href="#infinite">infinite</a>, Previous:<a rel="previous" href="#indexofX">index of X</a>, Up:<a rel="up" +href="#chap09">= I =</a> <br> + + +<p><b>infant mortality</b> n.</p> + +<p>It is common lore among hackers (and in the electronics +industry at large; this term is possibly techspeak by now) that +the chances of sudden hardware failure drop off exponentially +with a machine's time since first use (that is, until the +relatively distant time at which enough mechanical wear in I/O +devices and thermal-cycling stress in components has accumulated +for the machine to start going senile). Up to half of all chip +and wire failures happen within a new system's first few weeks; +such failures are often referred to as `infant mortality' +problems (or, occasionally, as `sudden infant death syndrome'). +See <b><a href="#bathtubcurve">bathtub curve</a></b>, <b><a +href="#burn-inperiod">burn-in period</a></b>.</p> + +<hr> +Node:<a name="infinite">infinite</a>, Next:<a rel="next" href="#infiniteloop">infinite loop</a>, Previous:<a rel="previous" +href="#infantmortality">infant mortality</a>, Up:<a rel="up" +href="#chap09">= I =</a> <br> + + +<p><b>infinite</b> adj.</p> + +<p>[common] Consisting of a large number of objects; extreme. +Used very loosely as in: "This program produces infinite +garbage." "He is an infinite loser." The word most likely to +follow `infinite', though, is <b><a href="#hair">hair</a></b>. +(It has been pointed out that fractals are an excellent example +of infinite hair.) These uses are abuses of the word's +mathematical meaning. The term `semi-infinite', denoting an +immoderately large amount of some resource, is also heard. "This +compiler is taking a semi-infinite amount of time to optimize my +program." See also <b><a href="#semi">semi</a></b>.</p> + +<hr> +Node:<a name="infiniteloop">infinite loop</a>, Next:<a rel="next" href="#InfiniteMonkeyTheorem">Infinite-Monkey +Theorem</a>, Previous:<a rel="previous" href="#infinite">infinite</a>, Up:<a rel="up" href="#chap09">= +I =</a> <br> + + +<p><b>infinite loop</b> n.</p> + +<p>One that never terminates (that is, the machine <b><a href="#spin">spin</a></b>s or <b><a href="#buzz">buzz</a></b>es +forever and goes <b><a href="#catatonic">catatonic</a></b>). +There is a standard joke that has been made about each +generation's exemplar of the ultra-fast machine: "The Cray-3 is +so fast it can execute an infinite loop in under 2 seconds!"</p> + +<hr> +Node:<a name="InfiniteMonkeyTheorem">Infinite-Monkey +Theorem</a>, Next:<a rel="next" href="#infinity">infinity</a>, +Previous:<a rel="previous" href="#infiniteloop">infinite +loop</a>, Up:<a rel="up" href="#chap09">= I =</a> <br> + + +<p><b>Infinite-Monkey Theorem</b> n.</p> + +<p>"If you put an <b><a href="#infinite">infinite</a></b> number +of monkeys at typewriters, eventually one will bash out the +script for Hamlet." (One may also hypothesize a small number of +monkeys and a very long period of time.) This theorem asserts +nothing about the intelligence of the one <b><a href="#random">random</a></b> monkey that eventually comes up with the +script (and note that the mob will also type out all the possible +<i>incorrect</i> versions of Hamlet). It may be referred to +semi-seriously when justifying a <b><a href="#bruteforce">brute force</a></b> method; the implication is +that, with enough resources thrown at it, any technical challenge +becomes a <b><a href="#one-bananaproblem">one-banana +problem</a></b>. This argument gets more respect since <b><a +href="#Linux">Linux</a></b> justified the <b><a href="#bazaar">bazaar</a></b> mode of development.</p> + +<p> +This theorem was first popularized by the astronomer Sir Arthur Eddington. It +became part of the idiom of techies via the classic SF short story "Inflexible +Logic" by Russell Maloney, and many younger hackers know it through a reference +in Douglas Adams's "Hitchhiker's Guide to the Galaxy". On 1 April 2000 the +usage acquired its own Internet standard, (Infinite Monkey Protocol Suite). +</p> + +<hr> +Node:<a name="infinity">infinity</a>, Next:<a rel="next" href="#inflate">inflate</a>, Previous:<a rel="previous" href="#InfiniteMonkeyTheorem">Infinite-Monkey Theorem</a>, Up:<a +rel="up" href="#chap09">= I =</a> <br> + + +<p><b>infinity</b> n.</p> + +<p>1. The largest value that can be represented in a particular +type of variable (register, memory location, data type, +whatever). 2. `minus infinity': The smallest such value, not +necessarily or even usually the simple negation of plus infinity. +In N-bit twos-complement arithmetic, infinity is 2^(N-1) - 1 but +minus infinity is - (2^(N-1)), not -(2^(N-1) - 1). Note also that +this is different from <dfn>time T equals minus infinity</dfn>, +which is closer to a mathematician's usage of infinity.</p> + +<hr> +Node:<a name="inflate">inflate</a>, Next:<a rel="next" href="#Infocom">Infocom</a>, Previous:<a rel="previous" href="#infinity">infinity</a>, Up:<a rel="up" href="#chap09">= +I =</a> <br> + + +<p><b>inflate</b> vt.</p> + +<p>To decompress or <b><a href="#puff">puff</a></b> a file. Rare +among Internet hackers, used primarily by MS-DOS/Windows +types.</p> + +<hr> +Node:<a name="Infocom">Infocom</a>, Next:<a rel="next" href="#initgame">initgame</a>, Previous:<a rel="previous" href="#inflate">inflate</a>, Up:<a rel="up" href="#chap09">= I +=</a> <br> + + +<p><b>Infocom</b> n.</p> + +<p>A now-legendary games company, active from 1979 to 1989, that +commercialized the MDL parser technology used for <b><a href="#Zork">Zork</a></b> to produce a line of text adventure games +that remain favorites among hackers. Infocom's games were +intelligent, funny, witty, erudite, irreverent, challenging, +satirical, and most thoroughly hackish in spirit. The physical +game packages from Infocom are now prized collector's items. +After being acquired by Activision in 1989 they did a few more +"modern" (e.g. graphics-intensive) games which were less +successful than reissues of their classics.</p> + +<p>The software, thankfully, is still extant; Infocom games were +written in a kind of P-code and distributed with a P-code +interpreter core, and not only freeware emulators for that +interpreter but an actual compiler as well have been written to +permit the P-code to be run on platforms the games never +originally graced. In fact, new games written in this P-code are +still bering written. (Emulators that can run Infocom game ZIPs, +and new games, are available at <a href="ftp://wuarchive.wustl.edu:/doc/misc/if-archive/infocom">ftp://wuarchive.wustl.edu:/doc/misc/if-archive/infocom</a>.)</p> + +<hr> +Node:<a name="initgame">initgame</a>, Next:<a rel="next" href="#insanelygreat">insanely great</a>, Previous:<a rel="previous" href="#Infocom">Infocom</a>, Up:<a rel="up" href="#chap09">= I =</a> <br> + + +<p><b>initgame</b> /in-it'gaym/ n.</p> + +<p>[IRC] An <b><a href="#IRC">IRC</a></b> version of the trivia +game "Botticelli", in which one user changes his <b><a href="#nick">nick</a></b> to the initials of a famous person or other +named entity, and the others on the channel ask yes or no +questions, with the one to guess the person getting to be "it" +next. As a courtesy, the one picking the initials starts by +providing a 4-letter hint of the form sex, nationality, +life-status, reality-status. For example, MAAR means "Male, +American, Alive, Real" (as opposed to "fictional"). Initgame can +be surprisingly addictive. See also <b><a href="#hing">hing</a></b>.</p> + +<p>[1996 update: a recognizable version of the initgame has +become a staple of some radio talk shows in the U.S. We had it +first! - ESR]</p> + +<hr> +Node:<a name="insanelygreat">insanely great</a>, Next:<a rel="next" href="#installfest">installfest</a>, Previous:<a rel="previous" href="#initgame">initgame</a>, Up:<a rel="up" href="#chap09">= I =</a> <br> + + +<p><b>insanely great</b> adj.</p> + +<p>[Mac community, from Steve Jobs; also BSD Unix people via Bill +Joy] Something so incredibly <b><a href="#elegant">elegant</a></b> that it is imaginable only to someone +possessing the most puissant of <b><a href="#hacker">hacker</a></b>-natures.</p> + +<hr> +Node:<a name="installfest">installfest</a>, Next:<a rel="next" +href="#INTERCAL">INTERCAL</a>, Previous:<a rel="previous" href="#insanelygreat">insanely great</a>, Up:<a rel="up" href="#chap09">= I =</a> <br> + + +<p><b>installfest</b></p> + +<p>[Linux community since c.1998] Common portmanteau word for +"installation festival"; Linux user groups frequently run these. +Computer users are invited to bring their machines to have Linux +installed on their machines. The idea is to get them painlessly +over the biggest hump in migrating to Linux, which is initially +installing and configuring it for the user's machine.</p> + +<hr> +Node:<a name="INTERCAL">INTERCAL</a>, Next:<a rel="next" href="#interesting">interesting</a>, Previous:<a rel="previous" href="#installfest">installfest</a>, Up:<a rel="up" href="#chap09">= I =</a> <br> + + +<p><b>INTERCAL</b> /in't*r-kal/ n.</p> + +<p>[said by the authors to stand for `Compiler Language With No +Pronounceable Acronym'] A computer language designed by Don Woods +and James Lyons in 1972. INTERCAL is purposely different from all +other computer languages in all ways but one; it is purely a +written language, being totally unspeakable. An excerpt from the +INTERCAL Reference Manual will make the style of the language +clear:</p> + +<blockquote>It is a well-known and oft-demonstrated fact that a +person whose work is incomprehensible is held in high esteem. For +example, if one were to state that the simplest way to store a +value of 65536 in a 32-bit INTERCAL variable is: + +<pre> +DO :1 <- #0$#256 +</pre> + +<p>any sensible programmer would say that that was absurd. Since +this is indeed the simplest method, the programmer would be made +to look foolish in front of his boss, who would of course have +happened to turn up, as bosses are wont to do. The effect would +be no less devastating for the programmer having been +correct.</p> +</blockquote> + +<p>INTERCAL has many other peculiar features designed to make it +even more unspeakable. The Woods-Lyons implementation was +actually used by many (well, at least several) people at +Princeton. The language has been recently reimplemented as +C-INTERCAL and is consequently enjoying an unprecedented level of +unpopularity; there is even an <i>alt.lang.intercal</i> newsgroup +devoted to the study and <small>...</small> appreciation of the +language on Usenet.</p> + +<p>Inevitably, INTERCAL has a home page on the Web: http://www.tuxedo.org/~esr/intercal/. +An extended version, implemented in (what else?) <b><a href="#Perl">Perl</a></b> and adding object-oriented features, is +available at http://dd-sh.assurdo.com/INTERCAL. +See also <b><a href="#Befunge">Befunge</a></b>.</p> + +<hr> +Node:<a name="interesting">interesting</a>, Next:<a rel="next" +href="#Internet">Internet</a>, Previous:<a rel="previous" href="#INTERCAL">INTERCAL</a>, Up:<a rel="up" href="#chap09">= +I =</a> <br> + + +<p><b>interesting</b> adj.</p> + +<p>In hacker parlance, this word has strong connotations of +`annoying', or `difficult', or both. Hackers relish a challenge, +and enjoy wringing all the irony possible out of the ancient +Chinese curse "May you live in interesting times". Oppose <b><a +href="#trivial">trivial</a></b>, <b><a href="#uninteresting">uninteresting</a></b>.</p> + +<hr> +Node:<a name="Internet">Internet</a>, Next:<a rel="next" href="#Internetaddress">Internet address</a>, Previous:<a rel="previous" href="#interesting">interesting</a>, Up:<a rel="up" +href="#chap09">= I =</a> <br> + + +<p><b>Internet</b> n.</p> + +<p>The mother of all networks. First incarnated beginning in 1969 +as the ARPANET, a U.S. Department of Defense research testbed. +Though it has been widely believed that the goal was to develop a +network architecture for military command-and-control that could +survive disruptions up to and including nuclear war, this is a +myth; in fact, ARPANET was conceived from the start as a way to +get most economical use out of then-scarce large-computer +resources.</p> + +<p>As originally imagined, ARPANET's major use would have been to +support what is now called remote login and more sophisticated +forms of distributed computing, but the infant technology of +electronic mail quickly grew to dominate actual usage. +Universities, research labs and defense contractors early +discovered the Internet's potential as a medium of communication +between <i>humans</i> and linked up in steadily increasing +numbers, connecting together a quirky mix of academics, techies, +hippies, SF fans, hackers, and anarchists. The roots of this +lexicon lie in those early years.</p> + +<p>Over the next quarter-century the Internet evolved in many +ways. The typical machine/OS combination moved from <b><a href="#DEC">DEC</a></b> <b><a href="#PDP-10">PDP-10</a></b>s and <b><a +href="#PDP-20">PDP-20</a></b>s, running <b><a href="#TOPS-10">TOPS-10</a></b> and <b><a href="#TOPS-20">TOPS-20</a></b>, to PDP-11s and VAXes and Suns running +<b><a href="#Unix">Unix</a></b>, and in the 1990s to Unix on +Intel microcomputers. The Internet's protocols grew more capable, +most notably in the move from NCP/IP to <b><a href="#TCPIP">TCP/IP</a></b> in 1982 and the implementation of +Domain Name Service in 1983. It was around this time that people +began referring to the collection of interconnected networks with +ARPANET at its core as "the Internet".</p> + +<p>The ARPANET had a fairly strict set of participation +guidelines - connected institutions had to be involved with a +DOD-related research project. By the mid-80s, many of the +organizations clamoring to join didn't fit this profile. In 1986, +the National Science Foundation built NSFnet to open up access to +its five regional supercomputing centers; NSFnet became the +backbone of the Internet, replacing the original ARPANET pipes +(which were formally shut down in 1990). Between 1990 and late +1994 the pieces of NSFnet were sold to major telecommunications +companies until the Internet backbone had gone completely +commercial.</p> + +<p>That year, 1994, was also the year the mainstream culture +discovered the Internet. Once again, the <b><a href="#killerapp">killer app</a></b> was not the anticipated one - +rather, what caught the public imagination was the hypertext and +multimedia features of the World Wide Web. Subsequently the +Internet has seen off its only serious challenger (the OSI +protocol stack favored by European telecom monopolies) and is in +the process of absorbing into itself many of the proprietary +networks built during the second wave of wide-area networking +after 1980. It is now (1996) a commonplace even in mainstream +media to predict that a globally-extended Internet will become +the key unifying communications technology of the next century. +See also <b><a href="#thenetwork">the network</a></b> and +<b><a href="#Internetaddress">Internet address</a></b>.</p> + +<hr> +Node:<a name="Internetaddress">Internet address</a>, Next:<a +rel="next" href="#InternetDeathPenalty">Internet Death +Penalty</a>, Previous:<a rel="previous" href="#Internet">Internet</a>, Up:<a rel="up" href="#chap09">= +I =</a> <br> + + +<p><b>Internet address</b> n.</p> + +<p>1. [techspeak] An absolute network address of the form +<i>foo@bar.baz</i>, where foo is a user name, bar is a <b><a +href="#sitename">sitename</a></b>, and baz is a `domain' name, +possibly including periods itself. Contrast with <b><a href="#bangpath">bang path</a></b>; see also <b><a href="#thenetwork">the network</a></b> and <b><a href="#networkaddress">network address</a></b>. All Internet +machines and most UUCP sites can now resolve these addresses, +thanks to a large amount of behind-the-scenes magic and <b><a +href="#PD">PD</a></b> software written since 1980 or so. See also +<b><a href="#bangpath">bang path</a></b>, <b><a href="#domainist">domainist</a></b>. 2. More loosely, any network +address reachable through Internet; this includes <b><a href="#bangpath">bang path</a></b> addresses and some internal +corporate and government networks.</p> + +<p>Reading Internet addresses is something of an art. Here are +the four most important top-level functional Internet domains +followed by a selection of geographical domains:</p> + +<blockquote> +<dl> +<dt><i>com</i></dt> + +<dd>commercial organizations</dd> + +<dt><i>edu</i></dt> + +<dd>educational institutions</dd> + +<dt><i>gov</i></dt> + +<dd>U.S. government civilian sites</dd> + +<dt><i>mil</i></dt> + +<dd>U.S. military sites</dd> +</dl> +</blockquote> + +<br> +<p>Note that most of the sites in the <i>com</i> and <i>edu</i> +domains are in the U.S. or Canada.<br> +</p> + +<blockquote> +<dl> +<dt><i>us</i></dt> + +<dd>sites in the U.S. outside the functional domains</dd> + +<dt><i>su</i></dt> + +<dd>sites in the ex-Soviet Union (see <b><a href="#kremvax">kremvax</a></b>).</dd> + +<dt><i>uk</i></dt> + +<dd>sites in the United Kingdom</dd> +</dl> +</blockquote> + +<p>Within the <i>us</i> domain, there are subdomains for the +fifty states, each generally with a name identical to the state's +postal abbreviation. Within the <i>uk</i> domain, there is an +<i>ac</i> subdomain for academic sites and a <i>co</i> domain for +commercial ones. Other top-level domains may be divided up in +similar ways.</p> + +<hr> +Node:<a name="InternetDeathPenalty">Internet Death +Penalty</a>, Next:<a rel="next" href="#InternetExploder">Internet Exploder</a>, Previous:<a rel="previous" href="#Internetaddress">Internet address</a>, Up:<a +rel="up" href="#chap09">= I =</a> <br> + + +<p><b>Internet Death Penalty</b></p> + +<p>[Usenet] (often abbreviated IDP) The ultimate sanction against +<b><a href="#spam">spam</a></b>-emitting sites - complete +shunning at the router level of all mail and packets, as well as +Usenet messages, from the offending domain(s). Compare <b><a +href="#UsenetDeathPenalty">Usenet Death Penalty</a></b>, +with which it is sometimes confused.</p> + +<hr> +Node:<a name="InternetExploder">Internet Exploder</a>, Next:<a +rel="next" href="#InternetExploiter">Internet Exploiter</a>, +Previous:<a rel="previous" href="#InternetDeathPenalty">Internet Death Penalty</a>, Up:<a +rel="up" href="#chap09">= I =</a> <br> + + +<p><b>Internet Exploder</b></p> + +<p>[very common] Pejorative hackerism for Microsoft's "Internet +Explorer" web browser (also "Internet Exploiter"). Compare <b><a +href="#HP-SUX">HP-SUX</a></b>, <b><a href="#AIDX">AIDX</a></b>, +<b><a href="#buglix">buglix</a></b>, <b><a href="#Macintrash">Macintrash</a></b>, <b><a href="#Telerat">Telerat</a></b>, <b><a href="#ScumOS">ScumOS</a></b>, +<b><a href="#sun-stools">sun-stools</a></b>, <b><a href="#Slowlaris">Slowlaris</a></b>.</p> + +<hr> +Node:<a name="InternetExploiter">Internet Exploiter</a>, +Next:<a rel="next" href="#interrupt">interrupt</a>, Previous:<a +rel="previous" href="#InternetExploder">Internet Exploder</a>, +Up:<a rel="up" href="#chap09">= I =</a> <br> + + +<p><b>Internet Exploiter</b> n.</p> + +<p>Another common name-of-insult for Internet Explorer, +Microsoft's overweight Web Browser; more hostile than <b><a href="#InternetExploder">Internet Exploder</a></b>. Reflects +widespread hostility to Microsoft and a sense that it is seeking +to hijack, monopolize, and corrupt the Internet. Compare <b><a +href="#Exploder">Exploder</a></b> and the less pejorative <b><a +href="#Netscrape">Netscrape</a></b>.</p> + +<hr> +Node:<a name="interrupt">interrupt</a>, Next:<a rel="next" href="#interruptlist">interrupt list</a>, Previous:<a rel="previous" href="#InternetExploiter">Internet Exploiter</a>, +Up:<a rel="up" href="#chap09">= I =</a> <br> + + +<p><b>interrupt</b></p> + +<p>1. [techspeak] n. On a computer, an event that interrupts +normal processing and temporarily diverts flow-of-control through +an "interrupt handler" routine. See also <b><a href="#trap">trap</a></b>. 2. interj. A request for attention from a +hacker. Often explicitly spoken. "Interrupt -- have you seen Joe +recently?" See <b><a href="#priorityinterrupt">priority +interrupt</a></b>. 3. Under MS-DOS, nearly synonymous with +`system call', because the OS and BIOS routines are both called +using the INT instruction (see <b><a href="#interruptlist">interrupt list</a></b>) and because +programmers so often have to bypass the OS (going directly to a +BIOS interrupt) to get reasonable performance.</p> + +<hr> +Node:<a name="interruptlist">interrupt list</a>, Next:<a rel="next" href="#interruptslockedout">interrupts locked +out</a>, Previous:<a rel="previous" href="#interrupt">interrupt</a>, Up:<a rel="up" href="#chap09">= I =</a> <br> + + +<p><b>interrupt list</b> n.</p> + +<p> +[MS-DOS] The list of all known software interrupt calls (both documented and +undocumented) for IBM PCs and compatibles, maintained and made available for +free redistribution by Ralf Brown. As of late 1992, it had grown to +approximately two megabytes in length. +</p> + +<hr> +Node:<a name="interruptslockedout">interrupts locked +out</a>, Next:<a rel="next" href="#intro">intro</a>, Previous:<a +rel="previous" href="#interruptlist">interrupt list</a>, Up:<a +rel="up" href="#chap09">= I =</a> <br> + + +<p><b>interrupts locked out</b> adj.</p> + +<p>When someone is ignoring you. In a restaurant, after several +fruitless attempts to get the waitress's attention, a hacker +might well observe "She must have interrupts locked out". The +synonym `interrupts disabled' is also common. Variations abound; +"to have one's interrupt mask bit set" and "interrupts masked +out" are also heard. See also <b><a href="#spl">spl</a></b>.</p> + +<hr> +Node:<a name="intro">intro</a>, Next:<a rel="next" href="#IRC">IRC</a>, Previous:<a rel="previous" href="#interruptslockedout">interrupts locked out</a>, Up:<a +rel="up" href="#chap09">= I =</a> <br> + + +<p><b>intro</b> n.</p> + +<p>[<b><a href="#demoscene">demoscene</a></b>] Introductory <b><a +href="#screen">screen</a></b> of some production. 2. A short +<b><a href="#demo">demo</a></b>, usually showing just one or two +<b><a href="#screen">screen</a></b>s. 3. Small, usually 64k, 40k +or 4k <b><a href="#demo">demo</a></b>. Sizes are generally +dictated by <b><a href="#compo">compo</a></b> rules. See also +<b><a href="#dentro">dentro</a></b>, <b><a href="#demo">demo</a></b>.</p> + +<hr> +Node:<a name="IRC">IRC</a>, Next:<a rel="next" href="#iron">iron</a>, Previous:<a rel="previous" href="#intro">intro</a>, Up:<a rel="up" href="#chap09">= I +=</a> <br> + + +<p><b>IRC</b> /I-R-C/ n.</p> + +<p>[Internet Relay Chat] A worldwide "party line" network that +allows one to converse with others in real time. IRC is +structured as a network of Internet servers, each of which +accepts connections from client programs, one per user. The IRC +community and the <b><a href="#Usenet">Usenet</a></b> and <b><a +href="#MUD">MUD</a></b> communities overlap to some extent, +including both hackers and regular folks who have discovered the +wonders of computer networks. Some Usenet jargon has been adopted +on IRC, as have some conventions such as <b><a href="#emoticon">emoticon</a></b>s. There is also a vigorous native +jargon, represented in this lexicon by entries marked `[IRC]'. +See also <b><a href="#talkmode">talk mode</a></b>.</p> + +<hr> +Node:<a name="iron">iron</a>, Next:<a rel="next" href="#IronAge">Iron Age</a>, Previous:<a rel="previous" href="#IRC">IRC</a>, Up:<a rel="up" href="#chap09">= I =</a> +<br> + + +<p><b>iron</b> n.</p> + +<p>Hardware, especially older and larger hardware of <b><a href="#mainframe">mainframe</a></b> class with big metal cabinets +housing relatively low-density electronics (but the term is also +used of modern supercomputers). Often in the phrase <b><a href="#bigiron">big iron</a></b>. Oppose <b><a href="#silicon">silicon</a></b>. See also <b><a href="#dinosaur">dinosaur</a></b>.</p> + +<hr> +Node:<a name="IronAge">Iron Age</a>, Next:<a rel="next" href="#ironbox">iron box</a>, Previous:<a rel="previous" href="#iron">iron</a>, Up:<a rel="up" href="#chap09">= I =</a> +<br> + + +<p><b>Iron Age</b> n.</p> + +<p>In the history of computing, 1961-1971 -- the formative era of +commercial <b><a href="#mainframe">mainframe</a></b> technology, +when ferrite-core <b><a href="#dinosaur">dinosaur</a></b>s ruled +the earth. The Iron Age began, ironically enough, with the +delivery of the first minicomputer (the PDP-1) and ended with the +introduction of the first commercial microprocessor (the Intel +4004) in 1971. See also <b><a href="#StoneAge">Stone +Age</a></b>; compare <b><a href="#elderdays">elder +days</a></b>.</p> + +<hr> +Node:<a name="ironbox">iron box</a>, Next:<a rel="next" href="#ironmonger">ironmonger</a>, Previous:<a rel="previous" href="#IronAge">Iron Age</a>, Up:<a rel="up" href="#chap09">= I =</a> <br> + + +<p><b>iron box</b> n.</p> + +<p>[Unix/Internet] A special environment set up to trap a <b><a +href="#cracker">cracker</a></b> logging in over remote +connections long enough to be traced. May include a modified +<b><a href="#shell">shell</a></b> restricting the cracker's +movements in unobvious ways, and `bait' files designed to keep +him interested and logged on. See also <b><a href="#backdoor">back door</a></b>, <b><a href="#firewallmachine">firewall machine</a></b>, <b><a href="#Venusflytrap">Venus flytrap</a></b>, and Clifford Stoll's +account in "<b><a href="#TheCuckoosEgg">The Cuckoo's +Egg</a></b>" of how he made and used one (see the <b><a href="#Bibliography">Bibliography</a></b> in Appendix C). Compare +<b><a href="#paddedcell">padded cell</a></b>, <b><a href="#honeypot">honey pot</a></b>.</p> + +<hr> +Node:<a name="ironmonger">ironmonger</a>, Next:<a rel="next" +href="#ISOstandardcupoftea">ISO standard cup of +tea</a>, Previous:<a rel="previous" href="#ironbox">iron +box</a>, Up:<a rel="up" href="#chap09">= I =</a> <br> + + +<p><b>ironmonger</b> n.</p> + +<p>[IBM] A hardware specialist (derogatory). Compare <b><a href="#sandbender">sandbender</a></b>, <b><a href="#polygonpusher">polygon pusher</a></b>.</p> + +<hr> +Node:<a name="ISOstandardcupoftea">ISO standard cup +of tea</a>, Next:<a rel="next" href="#ISP">ISP</a>, Previous:<a +rel="previous" href="#ironmonger">ironmonger</a>, Up:<a rel="up" +href="#chap09">= I =</a> <br> + + +<p><b>ISO standard cup of tea</b> n.</p> + +<p>[South Africa] A cup of tea with milk and one teaspoon of +sugar, where the milk is poured into the cup before the tea. +Variations are ISO 0, with no sugar; ISO 2, with two spoons of +sugar; and so on. This may derive from the "NATO standard" cup of +coffee and tea (milk and two sugars), military slang going back +to the late 1950s and parodying NATO's relentless bureacratic +drive to standardize parts across European and U.S. +militaries.</p> + +<p>Like many ISO standards, this one has a faintly alien ring in +North America, where hackers generally shun the decadent British +practice of adulterating perfectly good tea with dairy products +and prefer instead to add a wedge of lemon, if anything. If one +were feeling extremely silly, one might hypothesize an analogous +`ANSI standard cup of tea' and wind up with a political situation +distressingly similar to several that arise in much more serious +technical contexts. (Milk and lemon don't mix very well.)</p> + +<p>[2000 update: There is now, in fact, a `British Standard +BS6008: How to make a standard cup of tea.' - ESR]</p> + +<hr> +Node:<a name="ISP">ISP</a>, Next:<a rel="next" href="#ITS">ITS</a>, Previous:<a rel="previous" href="#ISOstandardcupoftea">ISO standard cup of tea</a>, +Up:<a rel="up" href="#chap09">= I =</a> <br> + + +<p><b>ISP</b> /I-S-P/</p> + +<p>Common abbreviation for Internet Service Provider, a kind of +company that barely existed before 1993. ISPs sell Internet +access to the mass market. While the big nationwide commercial +BBSs with Internet access (like America Online, CompuServe, +GEnie, Netcom, etc.) are technically ISPs, the term is usually +reserved for local or regional small providers (often run by +hackers turned entrepreneurs) who resell Internet access cheaply +without themselves being information providers or selling +advertising. Compare <b><a href="#NSP">NSP</a></b>.</p> + +<hr> +Node:<a name="ITS">ITS</a>, Next:<a rel="next" href="#IWBNI">IWBNI</a>, Previous:<a rel="previous" href="#ISP">ISP</a>, Up:<a rel="up" href="#chap09">= I =</a> +<br> + + +<p><b>ITS</b> /I-T-S/ n.</p> + +<p>1. Incompatible Time-sharing System, an influential though +highly idiosyncratic operating system written for PDP-6s and +PDP-10s at MIT and long used at the MIT AI Lab. Much AI-hacker +jargon derives from ITS folklore, and to have been `an ITS +hacker' qualifies one instantly as an old-timer of the most +venerable sort. ITS pioneered many important innovations, +including transparent file sharing between machines and +terminal-independent I/O. After about 1982, most actual work was +shifted to newer machines, with the remaining ITS boxes run +essentially as a hobby and service to the hacker community. The +shutdown of the lab's last ITS machine in May 1990 marked the end +of an era and sent old-time hackers into mourning nationwide (see +<b><a href="#highmoby">high moby</a></b>). 2. A mythical image +of operating-system perfection worshiped by a bizarre, fervent +retro-cult of old-time hackers and ex-users (see <b><a href="#troglodyte">troglodyte</a></b>, sense 2). ITS worshipers manage +somehow to continue believing that an OS maintained by +assembly-language hand-hacking that supported only monocase +6-character filenames in one directory per account remains +superior to today's state of commercial art (their venom against +<b><a href="#Unix">Unix</a></b> is particularly intense). See +also <b><a href="#holywars">holy wars</a></b>, <b><a href="#Weenix">Weenix</a></b>.</p> + +<hr> +Node:<a name="IWBNI">IWBNI</a>, Next:<a rel="next" href="#IYFEG">IYFEG</a>, Previous:<a rel="previous" href="#ITS">ITS</a>, Up:<a rel="up" href="#chap09">= I =</a> +<br> + + +<p><b>IWBNI</b> //</p> + +<p>Abbreviation for `It Would Be Nice If'. Compare <b><a href="#WIBNI">WIBNI</a></b>.</p> + +<hr> +Node:<a name="IYFEG">IYFEG</a>, Next:<a rel="next" href="#Jrandom">J. Random</a>, Previous:<a rel="previous" href="#IWBNI">IWBNI</a>, Up:<a rel="up" href="#chap09">= I +=</a> <br> + + +<p><b>IYFEG</b> //</p> + +<p>[Usenet] Abbreviation for `Insert Your Favorite Ethnic Group'. +Used as a meta-name when telling ethnic jokes on the net to avoid +offending anyone. See <b><a href="#JEDR">JEDR</a></b>.</p> + +<hr> +Node:<a name="chap10">= J =</a>, Next:<a rel="next" href="#chap11">= K =</a>, Previous:<a rel="previous" href="#chap09">= I =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= J =</h2> + +<ul> +<li><a href="#Jrandom">J. Random</a>:</li> + +<li><a href="#JRandomHacker">J. Random Hacker</a>:</li> + +<li><a href="#jackIn">jack in</a>:</li> + +<li><a href="#jaggies">jaggies</a>:</li> + +<li><a href="#Java">Java</a>:</li> + +<li><a href="#JCL">JCL</a>:</li> + +<li><a href="#JEDR">JEDR</a>:</li> + +<li><a href="#JeffK.">Jeff K.</a>:</li> + +<li><a href="#jello">jello</a>:</li> + +<li><a href="#jiffy">jiffy</a>:</li> + +<li><a href="#jobsecurity">job security</a>:</li> + +<li><a href="#jock">jock</a>:</li> + +<li><a href="#joecode">joe code</a>:</li> + +<li><a href="#jolix">jolix</a>:</li> + +<li><a href="#jugglingeggs">juggling eggs</a>:</li> + +<li><a href="#jumpoffintoneverneverland">jump off +into never-never land</a>:</li> + +<li><a href="#jupiter">jupiter</a>:</li> +</ul> + +<hr> +Node:<a name="Jrandom">J. Random</a>, Next:<a rel="next" +href="#JRandomHacker">J. Random Hacker</a>, Previous:<a +rel="previous" href="#IYFEG">IYFEG</a>, Up:<a rel="up" href="#chap10">= J =</a> <br> + + +<p><b>J. Random</b> /J rand'm/ n.</p> + +<p>[common; generalized from <b><a href="#JRandomHacker">J. Random Hacker</a></b>] Arbitrary; +ordinary; any one; any old. `J. Random' is often prefixed to a +noun to make a name out of it. It means roughly `some particular' +or `any specific one'. "Would you let J. Random Loser marry your +daughter?" The most common uses are `J. Random Hacker', `J. +Random Loser', and `J. Random Nerd' ("Should J. Random Loser be +allowed to <b><a href="#gun">gun</a></b> down other people?"), +but it can be used simply as an elaborate version of <b><a href="#random">random</a></b> in any sense.</p> + +<hr> +Node:<a name="JRandomHacker">J. Random Hacker</a>, Next:<a +rel="next" href="#jackIn">jack in</a>, Previous:<a rel="previous" href="#Jrandom">J. Random</a>, Up:<a rel="up" +href="#chap10">= J =</a> <br> + + +<p><b>J. Random Hacker</b> /J rand'm hak'r/ n.</p> + +<p>[very common] A mythical figure like the Unknown Soldier; the +archetypal hacker nerd. This term is one of the oldest in the +jargon, apparently going back to MIT in the 1960s. See <b><a +href="#random">random</a></b>, <b><a href="#SuzieCOBOL">Suzie +COBOL</a></b>. This may originally have been inspired by `J. Fred +Muggs', a show-biz chimpanzee whose name was a household word +back in the early days of <b><a href="#TMRC">TMRC</a></b>, and +was probably influenced by `J. Presper Eckert' (one of the +co-inventors of the electronic computer). See also <b><a href="#FredFoobar">Fred Foobar</a></b>.</p> + +<hr> +Node:<a name="jackIn">jack in</a>, Next:<a rel="next" href="#jaggies">jaggies</a>, Previous:<a rel="previous" href="#JRandomHacker">J. Random Hacker</a>, Up:<a rel="up" +href="#chap10">= J =</a> <br> + + +<p><b>jack in</b> v.</p> + +<p>To log on to a machine or connect to a network or <b><a href="#BBS">BBS</a></b>, esp. for purposes of entering a <b><a href="#virtualreality">virtual reality</a></b> simulation such as a +<b><a href="#MUD">MUD</a></b> or <b><a href="#IRC">IRC</a></b> +(leaving is "jacking out"). This term derives from <b><a href="#cyberpunk">cyberpunk</a></b> SF, in which it was used for the +act of plugging an electrode set into neural sockets in order to +interface the brain directly to a virtual reality. It is +primarily used by MUD and IRC fans and younger hackers on BBS +systems.</p> + +<hr> +Node:<a name="jaggies">jaggies</a>, Next:<a rel="next" href="#Java">Java</a>, Previous:<a rel="previous" href="#jackIn">jack in</a>, Up:<a rel="up" href="#chap10">= +J =</a> <br> + + +<p><b>jaggies</b> /jag'eez/ n.</p> + +<p>The `stairstep' effect observable when an edge (esp. a linear +edge of very shallow or steep slope) is rendered on a pixel +device (as opposed to a vector display).</p> + +<hr> +Node:<a name="Java">Java</a>, Next:<a rel="next" href="#JCL">JCL</a>, Previous:<a rel="previous" href="#jaggies">jaggies</a>, Up:<a rel="up" href="#chap10">= J +=</a> <br> + + +<p><b>Java</b></p> + +<p>An object-oriented language originally developed at Sun by +James Gosling (and known by the name "Oak") with the intention of +being the successor to <b><a href="#Cplusplus">C++</a></b> (the project +was however originally sold to Sun as an embedded language for +use in set-top boxes). After the great Internet explosion of +1993-1994, Java was hacked into a byte-interpreted language and +became the focus of a relentless hype campaign by Sun, which +touted it as the new language of choice for distributed +applications.</p> + +<p>Java is indeed a stronger and cleaner design than C++ and has +been embraced by many in the hacker community - but it has been a +considerable source of frustration to many others, for reasons +ranging from uneven support on different Web browser platforms, +performance issues, and some notorious deficiencies of some of +the standard toolkits (AWT in particular). <b><a href="#Microsoft">Microsoft</a></b>'s determined attempts to corrupt +the language (which it rightly sees as a threat to its OS +monopoly) have not helped. As of 1999, these issues are still in +the process of being resolved.</p> + +<p>Despite many attractive features and a good design, it is +difficult to find people willing to praise Java who have tried to +implement a complex, real-world system with it (but to be fair it +is early days yet, and no other language has ever been forced to +spend its childhood under the limelight the way Java has). On the +other hand, Java has already been a big <b><a href="#win">win</a></b> in academic circles, where it has taken the +place of <b><a href="#Pascal">Pascal</a></b> as the preferred +tool for teaching the basics of good programming to the next +generation of hackers.</p> + +<hr> +Node:<a name="JCL">JCL</a>, Next:<a rel="next" href="#JEDR">JEDR</a>, Previous:<a rel="previous" href="#Java">Java</a>, Up:<a rel="up" href="#chap10">= J =</a> +<br> + + +<p><b>JCL</b> /J-C-L/ n.</p> + +<p>1. IBM's supremely <b><a href="#rude">rude</a></b> Job Control +Language. JCL is the script language used to control the +execution of programs in IBM's batch systems. JCL has a very +<b><a href="#fascist">fascist</a></b> syntax, and some versions +will, for example, <b><a href="#barf">barf</a></b> if two spaces +appear where it expects one. Most programmers confronted with JCL +simply copy a working file (or card deck), changing the file +names. Someone who actually understands and generates unique JCL +is regarded with the mixed respect one gives to someone who +memorizes the phone book. It is reported that hackers at IBM +itself sometimes sing "Who's the breeder of the crud that mangles +you and me? I-B-M, J-C-L, M-o-u-s-e" to the tune of the "Mickey +Mouse Club" theme to express their opinion of the beast. 2. A +comparative for any very <b><a href="#rude">rude</a></b> software +that a hacker is expected to use. "That's as bad as JCL." As with +<b><a href="#COBOL">COBOL</a></b>, JCL is often used as an +archetype of ugliness even by those who haven't experienced it. +See also <b><a href="#IBM">IBM</a></b>, <b><a href="#fearandloathing">fear and loathing</a></b>.</p> + +<p>A (poorly documented, naturally) shell simulating JCL syntax +is available at the Retrocomputing Museum http://www.ccil.org/retro.</p> + +<hr> +Node:<a name="JEDR">JEDR</a>, Next:<a rel="next" href="#JeffK.">Jeff K.</a>, Previous:<a rel="previous" href="#JCL">JCL</a>, Up:<a rel="up" href="#chap10">= J =</a> +<br> + + +<p><b>JEDR</b> // n.</p> + +<p>Synonymous with <b><a href="#IYFEG">IYFEG</a></b>. At one +time, people in the Usenet newsgroup <i>rec.humor.funny</i> +tended to use `JEDR' instead of <b><a href="#IYFEG">IYFEG</a></b> +or `<ethnic>'; this stemmed from a public attempt to +suppress the group once made by a loser with initials JEDR after +he was offended by an ethnic joke posted there. (The practice was +<b><a href="#retcon">retcon</a></b>ned by the expanding these +initials as `Joke Ethnic/Denomination/Race'.) After much sound +and fury JEDR faded away; this term appears to be doing likewise. +JEDR's only permanent effect on the net.culture was to discredit +`sensitivity' arguments for censorship so thoroughly that more +recent attempts to raise them have met with immediate and +near-universal rejection.</p> + +<hr> +Node:<a name="JeffK.">Jeff K.</a>, Next:<a rel="next" href="#jello">jello</a>, Previous:<a rel="previous" href="#JEDR">JEDR</a>, Up:<a rel="up" href="#chap10">= J =</a> +<br> + + +<p><b>Jeff K.</b></p> + +<p>The spiritual successor to <b><a href="#B1FF">B1FF</a></b> and +the archetype of <b><a href="#scriptkiddies">script +kiddies</a></b>. Jeff K. is a sixteen-year-old suburbanite who +fancies himself a "l33t haX0r", although his knowledge of +computers seems to be limited to the procedure for getting Quake +up and running. His Web page http://www.somethingawful.com/jeffk +features a number of hopelessly naive articles, essays, and +rants, all filled with the kind of misspellings, <b><a href="#studlycaps">studlycaps</a></b>, and number-for-letter +substitutions endemic to the script kiddie and <b><a href="#warezd00dz">warez d00dz</a></b> communities. Jeff's +offerings, among other things, include hardware advice (such as +"AMD VERSIS PENTIUM" and "HOW TO OVARCLOAK YOUR COMPUTAR"), his +own Quake clan (Clan 40 OUNSCE), and his own comic strip (Wacky +Fun Computar Comic Jokes).</p> + +<p>Like B1FF, Jeff K. is (fortunately) a hoax. Jeff K. was +created by internet game journalist Richard "Lowtax" Kyanka, +whose web site Something Awful (http://www.somethingawful.com) +highlights unintentionally humorous news items and Web sites, as +a parody of the kind of teenage <b><a href="#luser">luser</a></b> +who infests Quake servers, chat rooms, and other places where +computer enthusiasts congregate. He is well-recognized in the PC +game community and his influence has spread to hacker <b><a href="#fora">fora</a></b> like Slashdot as well.</p> + +<hr> +Node:<a name="jello">jello</a>, Next:<a rel="next" href="#jiffy">jiffy</a>, Previous:<a rel="previous" href="#JeffK.">Jeff K.</a>, Up:<a rel="up" href="#chap10">= +J =</a> <br> + + +<p><b>jello</b> n.</p> + +<p>[Usenet: by analogy with <b><a href="#spam">spam</a></b>] A +message that is both excessively cross-posted and too frequently +posted, as opposed to <b><a href="#spam">spam</a></b> (which is +merely too frequently posted) or <b><a href="#velveeta">velveeta</a></b> (which is merely excessively +cross-posted). This term is widely recognized but not commonly +used; most people refer to both kinds of abuse or their +combination as spam.</p> + +<hr> +Node:<a name="jiffy">jiffy</a>, Next:<a rel="next" href="#jobsecurity">job security</a>, Previous:<a rel="previous" +href="#jello">jello</a>, Up:<a rel="up" href="#chap10">= J +=</a> <br> + + +<p><b>jiffy</b> n.</p> + +<p>1. The duration of one tick of the system clock on your +computer (see <b><a href="#tick">tick</a></b>). Often one AC +cycle time (1/60 second in the U.S. and Canada, 1/50 most other +places), but more recently 1/100 sec has become common. "The +swapper runs every 6 jiffies" means that the virtual memory +management routine is executed once for every 6 ticks of the +clock, or about ten times a second. 2. Confusingly, the term is +sometimes also used for a 1-millisecond <b><a href="#walltime">wall time</a></b> interval. 3. Even more +confusingly, physicists semi-jokingly use `jiffy' to mean the +time required for light to travel one foot in a vacuum, which +turns out to be close to one <i>nanosecond</i>. 4. +Indeterminate time from a few seconds to forever. "I'll do it in +a jiffy" means certainly not now and possibly never. This is a +bit contrary to the more widespread use of the word. Oppose <b><a +href="#nano">nano</a></b>. See also <b><a href="#RealSoonNow">Real Soon Now</a></b>.</p> + +<hr> +Node:<a name="jobsecurity">job security</a>, Next:<a rel="next" href="#jock">jock</a>, Previous:<a rel="previous" href="#jiffy">jiffy</a>, Up:<a rel="up" href="#chap10">= J +=</a> <br> + + +<p><b>job security</b> n.</p> + +<p>When some piece of code is written in a particularly <b><a +href="#obscure">obscure</a></b> fashion, and no good reason (such +as time or space optimization) can be discovered, it is often +said that the programmer was attempting to increase his job +security (i.e., by making himself indispensable for maintenance). +This sour joke seldom has to be said in full; if two hackers are +looking over some code together and one points at a section and +says "job security", the other one may just nod.</p> + +<hr> +Node:<a name="jock">jock</a>, Next:<a rel="next" href="#joecode">joe code</a>, Previous:<a rel="previous" href="#jobsecurity">job security</a>, Up:<a rel="up" href="#chap10">= J =</a> <br> + + +<p><b>jock</b> n.</p> + +<p>1. A programmer who is characterized by large and somewhat +brute-force programs. See <b><a href="#bruteforce">brute +force</a></b>. 2. When modified by another noun, describes a +specialist in some particular computing area. The compounds +`compiler jock' and `systems jock' seem to be the +best-established examples.</p> + +<hr> +Node:<a name="joecode">joe code</a>, Next:<a rel="next" href="#jolix">jolix</a>, Previous:<a rel="previous" href="#jock">jock</a>, Up:<a rel="up" href="#chap10">= J =</a> +<br> + + +<p><b>joe code</b> /joh' kohd`/ n.</p> + +<p>1. Code that is overly <b><a href="#tense">tense</a></b> and +unmaintainable. "<b><a href="#Perl">Perl</a></b> may be a handy +program, but if you look at the source, it's complete joe code." +2. Badly written, possibly buggy code.</p> + +<p>Correspondents wishing to remain anonymous have fingered a +particular Joe at the Lawrence Berkeley Laboratory and observed +that usage has drifted slightly; the original sobriquet `Joe +code' was intended in sense 1.</p> + +<p>1994 update: This term has now generalized to `<name> +code', used to designate code with distinct characteristics +traceable to its author. "This section doesn't check for a NULL +return from malloc()! Oh. No wonder! It's Ed code!". Used most +often with a programmer who has left the shop and thus is a +convenient scapegoat for anything that is wrong with the +project.</p> + +<hr> +Node:<a name="jolix">jolix</a>, Next:<a rel="next" href="#jugglingeggs">juggling eggs</a>, Previous:<a rel="previous" +href="#joecode">joe code</a>, Up:<a rel="up" href="#chap10">= J =</a> <br> + + +<p><b>jolix</b> /joh'liks/ n.,adj.</p> + +<p>386BSD, the freeware port of the BSD Net/2 release to the +Intel i386 architecture by Bill Jolitz, Lynne Greer Jolitz, and +friends. Used to differentiate from BSDI's port based on the same +source tape, which used to be called BSD/386 and is now BSD/OS. +See <b><a href="#BSD">BSD</a></b>.</p> + +<hr> +Node:<a name="jugglingeggs">juggling eggs</a>, Next:<a rel="next" href="#jumpoffintoneverneverland">jump off +into never-never land</a>, Previous:<a rel="previous" href="#jolix">jolix</a>, Up:<a rel="up" href="#chap10">= J +=</a> <br> + + +<p><b>juggling eggs</b> vi.</p> + +<p>Keeping a lot of <b><a href="#state">state</a></b> in your +head while modifying a program. "Don't bother me now, I'm +juggling eggs", means that an interrupt is likely to result in +the program's being scrambled. In the classic 1975 first-contact +SF novel "The Mote in God's Eye", by Larry Niven and Jerry +Pournelle, an alien describes a very difficult task by saying "We +juggle priceless eggs in variable gravity." See also <b><a href="#hackmode">hack mode</a></b> and <b><a href="#onthegrippinghand">on the gripping hand</a></b>.</p> + +<hr> +Node:<a name="jumpoffintoneverneverland">jump off +into never-never land</a>, Next:<a rel="next" href="#jupiter">jupiter</a>, Previous:<a rel="previous" href="#jugglingeggs">juggling eggs</a>, Up:<a rel="up" href="#chap10">= J =</a> <br> + + +<p><b>jump off into never-never land</b> v.</p> + +<p>[from J. M. Barrie's "Peter Pan"] Same as <b><a href="#branchtoFishkill">branch to Fishkill</a></b>, but more +common in technical cultures associated with non-IBM computers +that use the term `jump' rather than `branch'. Compare <b><a +href="#hyperspace">hyperspace</a></b>.</p> + +<hr> +Node:<a name="jupiter">jupiter</a>, Next:<a rel="next" href="#K">K</a>, Previous:<a rel="previous" href="#jumpoffintoneverneverland">jump off into +never-never land</a>, Up:<a rel="up" href="#chap10">= J +=</a> <br> + + +<p><b>jupiter</b> vt.</p> + +<p>[IRC] To kill an <b><a href="#IRC">IRC</a></b> <b><a href="#bot">bot</a></b> or user and then take its place by adopting +its <b><a href="#nick">nick</a></b> so that it cannot reconnect. +Named after a particular IRC user who did this to NickServ, the +robot in charge of preventing people from inadvertently using a +nick claimed by another user. Now commonly shortened to +`jupe'.</p> + +<hr> +Node:<a name="chap11">= K =</a>, Next:<a rel="next" href="#chap12">= L =</a>, Previous:<a rel="previous" href="#chap10">= J =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= K =</h2> + +<ul> +<li><a href="#K">K</a>:</li> + +<li><a href="#KandR">KandR</a>:</li> + +<li><a href="#k-">k-</a>:</li> + +<li><a href="#kahuna">kahuna</a>:</li> + +<li><a href="#kamikazepacket">kamikaze packet</a>:</li> + +<li><a href="#kangaroocode">kangaroo code</a>:</li> + +<li><a href="#ken">ken</a>:</li> + +<li><a href="#kernel-of-the-weekclub">kernel-of-the-week +club</a>:</li> + +<li><a href="#kgbvax">kgbvax</a>:</li> + +<li><a href="#KIBO">KIBO</a>:</li> + +<li><a href="#kiboze">kiboze</a>:</li> + +<li><a href="#kibozo">kibozo</a>:</li> + +<li><a href="#kick">kick</a>:</li> + +<li><a href="#killfile">kill file</a>:</li> + +<li><a href="#killerapp">killer app</a>:</li> + +<li><a href="#killermicro">killer micro</a>:</li> + +<li><a href="#killerpoke">killer poke</a>:</li> + +<li><a href="#kilo-">kilo-</a>:</li> + +<li><a href="#KIPS">KIPS</a>:</li> + +<li><a href="#KISSPrinciple">KISS Principle</a>:</li> + +<li><a href="#kit">kit</a>:</li> + +<li><a href="#klone">klone</a>:</li> + +<li><a href="#kludge">kludge</a>:</li> + +<li><a href="#kluge">kluge</a>:</li> + +<li><a href="#klugearound">kluge around</a>:</li> + +<li><a href="#klugeup">kluge up</a>:</li> + +<li><a href="#KnightsoftheLambdaCalculus">Knights of +the Lambda Calculus</a>:</li> + +<li><a href="#knobs">knobs</a>:</li> + +<li><a href="#Knuth">Knuth</a>:</li> + +<li><a href="#koan">koan</a>:</li> + +<li><a href="#kremvax">kremvax</a>:</li> + +<li><a href="#kyrka">kyrka</a>:</li> +</ul> + +<hr> +Node:<a name="K">K</a>, Next:<a rel="next" href="#KandR">K&R</a>, Previous:<a rel="previous" href="#jupiter">jupiter</a>, Up:<a rel="up" href="#chap11">= K +=</a> <br> + + +<p><b>K</b> /K/ n.</p> + +<p>[from <b><a href="#kilo-">kilo-</a></b>] A kilobyte. Used both +as a spoken word and a written suffix (like <b><a href="#meg">meg</a></b> and <b><a href="#gig">gig</a></b> for megabyte +and gigabyte). See <b><a href="#quantifiers">quantifiers</a></b>.</p> + +<hr> +Node:<a name="KandR">K&R</a>, Next:<a rel="next" href="#k-">k-</a>, Previous:<a rel="previous" href="#K">K</a>, Up:<a +rel="up" href="#chap11">= K =</a> <br> + + +<p><b>K&R</b> [Kernighan and Ritchie] n.</p> + +<p>Brian Kernighan and Dennis Ritchie's book "The C Programming +Language", esp. the classic and influential first edition +(Prentice-Hall 1978; ISBN 0-13-110163-3). Syn. <b><a href="#WhiteBook">White Book</a></b>, <b><a href="#OldTestament">Old Testament</a></b>. See also <b><a href="#NewTestament">New Testament</a></b>.</p> + +<hr> +Node:<a name="k-">k-</a>, Next:<a rel="next" href="#kahuna">kahuna</a>, Previous:<a rel="previous" href="#KandR">K&R</a>, Up:<a rel="up" href="#chap11">= K +=</a> <br> + + +<p><b>k-</b> pref.</p> + +<p>[rare; poss fr. `kilo-' prefix] Extremely. Rare among hackers, +but quite common among crackers and <b><a href="#warezd00dz">warez d00dz</a></b> in compounds such as +`k-kool' /K'kool'/, `k-rad' /K'rad'/, and `k-awesome' /K'aw`sm/. +Also used to intensify negatives; thus, `k-evil', `k-lame', +`k-screwed', and `k-annoying'. Overuse of this prefix, or use in +more formal or technical contexts, is considered an indicator of +<b><a href="#lamer">lamer</a></b> status.</p> + +<hr> +Node:<a name="kahuna">kahuna</a>, Next:<a rel="next" href="#kamikazepacket">kamikaze packet</a>, Previous:<a rel="previous" href="#k-">k-</a>, Up:<a rel="up" href="#chap11">= K =</a> <br> + + +<p><b>kahuna</b> /k*-hoo'n*/ n.</p> + +<p>[IBM: from the Hawaiian title for a shaman] Synonym for <b><a +href="#wizard">wizard</a></b>, <b><a href="#guru">guru</a></b>.</p> + +<hr> +Node:<a name="kamikazepacket">kamikaze packet</a>, Next:<a +rel="next" href="#kangaroocode">kangaroo code</a>, Previous:<a +rel="previous" href="#kahuna">kahuna</a>, Up:<a rel="up" href="#chap11">= K =</a> <br> + + +<p><b>kamikaze packet</b> n.</p> + +<p>The `official' jargon for what is more commonly called a <b><a +href="#Christmastreepacket">Christmas tree packet</a></b>. +<b><a href="#RFC">RFC</a></b>-1025, "TCP and IP Bake Off" +says:</p> + +<blockquote>10 points for correctly being able to process a +"Kamikaze" packet (AKA nastygram, christmas tree packet, lamp +test segment, et al.). That is, correctly handle a segment with +the maximum combination of features at once (e.g., a SYN URG PUSH +FIN segment with options and data).</blockquote> + +<p>See also <b><a href="#Chernobylpacket">Chernobyl +packet</a></b>.</p> + +<hr> +Node:<a name="kangaroocode">kangaroo code</a>, Next:<a rel="next" href="#ken">ken</a>, Previous:<a rel="previous" href="#kamikazepacket">kamikaze packet</a>, Up:<a rel="up" href="#chap11">= K =</a> <br> + + +<p><b>kangaroo code</b> n.</p> + +<p>Syn. <b><a href="#spaghetticode">spaghetti +code</a></b>.</p> + +<hr> +Node:<a name="ken">ken</a>, Next:<a rel="next" href="#kernel-of-the-weekclub">kernel-of-the-week club</a>, +Previous:<a rel="previous" href="#kangaroocode">kangaroo +code</a>, Up:<a rel="up" href="#chap11">= K =</a> <br> + + +<p><b>ken</b> /ken/ n.</p> + +<p>1. [Unix] Ken Thompson, principal inventor of Unix. In the +early days he used to hand-cut distribution tapes, often with a +note that read "Love, ken". Old-timers still use his first name +(sometimes uncapitalized, because it's a login name and mail +address) in third-person reference; it is widely understood (on +Usenet, in particular) that without a last name `Ken' refers only +to Ken Thompson. Similarly, Dennis without last name means Dennis +Ritchie (and he is often known as <i>dmr</i>). See also <b><a +href="#demigod">demigod</a></b>, <b><a href="#Unix">Unix</a></b>. +2. A flaming user. This was originated by the Software Support +group at Symbolics because the two greatest flamers in the user +community were both named Ken.</p> + +<hr> +Node:<a name="kernel-of-the-weekclub">kernel-of-the-week +club</a>, Next:<a rel="next" href="#kgbvax">kgbvax</a>, +Previous:<a rel="previous" href="#ken">ken</a>, Up:<a rel="up" +href="#chap11">= K =</a> <br> + + +<p><b>kernel-of-the-week club</b></p> + +<p>The fictional society that <b><a href="#BSD">BSD</a></b> <b><a +href="#bigot">bigot</a></b>s claim [Linux] users belong to, +alluding to the release-early-release-often style preferred by +the kernel maintainers. See <b><a href="#bazaar">bazaar</a></b>. +This was almost certainly inspired by the earlier <b><a href="#bug-of-the-monthclub">bug-of-the-month club</a></b>.</p> + +<hr> +Node:<a name="kgbvax">kgbvax</a>, Next:<a rel="next" href="#KIBO">KIBO</a>, Previous:<a rel="previous" href="#kernel-of-the-weekclub">kernel-of-the-week club</a>, Up:<a +rel="up" href="#chap11">= K =</a> <br> + + +<p><b>kgbvax</b> /K-G-B'vaks/ n.</p> + +<p>See <b><a href="#kremvax">kremvax</a></b>.</p> + +<hr> +Node:<a name="KIBO">KIBO</a>, Next:<a rel="next" href="#kiboze">kiboze</a>, Previous:<a rel="previous" href="#kgbvax">kgbvax</a>, Up:<a rel="up" href="#chap11">= K +=</a> <br> + + +<p><b>KIBO</b> /ki:'boh/</p> + +<p>1. [acronym] Knowledge In, Bullshit Out. A summary of what +happens whenever valid data is passed through an organization (or +person) that deliberately or accidentally disregards or ignores +its significance. Consider, for example, what an advertising +campaign can do with a product's actual specifications. Compare +<b><a href="#GIGO">GIGO</a></b>; see also <b><a href="#SNAFUprinciple">SNAFU principle</a></b>. 2. James Parry +<kibo@world.std.com>, a Usenetter infamous for various +surrealist net.pranks and an uncanny, machine-assisted knack for +joining any thread in which his nom de guerre is mentioned. He +has a website at http://www.kibo.com/.</p> + +<hr> +Node:<a name="kiboze">kiboze</a>, Next:<a rel="next" href="#kibozo">kibozo</a>, Previous:<a rel="previous" href="#KIBO">KIBO</a>, Up:<a rel="up" href="#chap11">= K =</a> +<br> + + +<p><b>kiboze</b> v.</p> + +<p>[Usenet] To <b><a href="#grep">grep</a></b> the Usenet news +for a string, especially with the intention of posting a +follow-up. This activity was popularised by Kibo (see <b><a href="#KIBO">KIBO</a></b>, sense 2).</p> + +<hr> +Node:<a name="kibozo">kibozo</a>, Next:<a rel="next" href="#kick">kick</a>, Previous:<a rel="previous" href="#kiboze">kiboze</a>, Up:<a rel="up" href="#chap11">= K +=</a> <br> + + +<p><b>kibozo</b> /ki:-boh'zoh/ n.</p> + +<p>[Usenet] One who <b><a href="#kiboze">kiboze</a></b>s but is +not Kibo (see <b><a href="#KIBO">KIBO</a></b>, sense 2).</p> + +<hr> +Node:<a name="kick">kick</a>, Next:<a rel="next" href="#killfile">kill file</a>, Previous:<a rel="previous" href="#kibozo">kibozo</a>, Up:<a rel="up" href="#chap11">= K +=</a> <br> + + +<p><b>kick</b> v.</p> + +<p>1. [IRC] To cause somebody to be removed from a <b><a href="#IRC">IRC</a></b> channel, an option only available to channel +ops. This is an extreme measure, often used to combat extreme +<b><a href="#flamage">flamage</a></b> or <b><a href="#flood">flood</a></b>ing, but sometimes used at the <b><a href="#CHOP">CHOP</a></b>'s whim. Compare <b><a href="#gun">gun</a></b>. 2. To reboot a machine or kill a running +process. "The server's down, let me go kick it."</p> + +<hr> +Node:<a name="killfile">kill file</a>, Next:<a rel="next" +href="#killerapp">killer app</a>, Previous:<a rel="previous" +href="#kick">kick</a>, Up:<a rel="up" href="#chap11">= K +=</a> <br> + + +<p><b>kill file</b> n.</p> + +<p>[Usenet; very common] (alt. `KILL file') Per-user file(s) used +by some <b><a href="#Usenet">Usenet</a></b> reading programs +(originally Larry Wall's <code>rn(1)</code>) to discard summarily +(without presenting for reading) articles matching some +particularly uninteresting (or unwanted) patterns of subject, +author, or other header lines. Thus to add a person (or subject) +to one's kill file is to arrange for that person to be ignored by +one's newsreader in future. By extension, it may be used for a +decision to ignore the person or subject in other media. See also +<b><a href="#plonk">plonk</a></b>.</p> + +<hr> +Node:<a name="killerapp">killer app</a>, Next:<a rel="next" +href="#killermicro">killer micro</a>, Previous:<a rel="previous" href="#killfile">kill file</a>, Up:<a rel="up" +href="#chap11">= K =</a> <br> + + +<p><b>killer app</b></p> + +<p>The application that actually makes a sustaining market for a +promising but under-utilized technology. First used in the +mid-1980s to describe Lotus 1-2-3 once it became evident that +demand for that product had been the major driver of the early +business market for IBM PCs. The term was then restrospectively +applied to VisiCalc, which had played a similar role in the +success of the Apple II. After 1994 it became commonplace to +describe the World Wide Web as the Internet's killer app. One of +the standard questions asked about each new personal-computer +technology as it emerges has become "what's the killer app?"</p> + +<hr> +Node:<a name="killermicro">killer micro</a>, Next:<a rel="next" href="#killerpoke">killer poke</a>, Previous:<a rel="previous" href="#killerapp">killer app</a>, Up:<a rel="up" +href="#chap11">= K =</a> <br> + + +<p><b>killer micro</b> n.</p> + +<p>[popularized by Eugene Brooks] A microprocessor-based machine +that infringes on mini, mainframe, or supercomputer performance +turf. Often heard in "No one will survive the attack of the +killer micros!", the battle cry of the downsizers. Used esp. of +RISC architectures.</p> + +<p>The popularity of the phrase `attack of the killer micros' is +doubtless reinforced by the title of the movie "Attack Of The +Killer Tomatoes" (one of the <b><a href="#canonical">canonical</a></b> examples of so-bad-it's-wonderful +among hackers). This has even more <b><a href="#flavor">flavor</a></b> now that killer micros have gone on the +offensive not just individually (in workstations) but in hordes +(within massively parallel computers).</p> + +<p>[1996 update: Eugene Brooks was right. Since this term first +entered the Jargon File in 1990, the minicomputer has effectively +vanished, the <b><a href="#mainframe">mainframe</a></b> sector is +in deep and apparently terminal decline (with IBM but a shadow of +its former self), and even the supercomputer business has +contracted into a smaller niche. It's networked killer micros as +far as the eye can see. --ESR]</p> + +<hr> +Node:<a name="killerpoke">killer poke</a>, Next:<a rel="next" +href="#kilo-">kilo-</a>, Previous:<a rel="previous" href="#killermicro">killer micro</a>, Up:<a rel="up" href="#chap11">= K =</a> <br> + + +<p><b>killer poke</b> n.</p> + +<p>A recipe for inducing hardware damage on a machine via +insertion of invalid values (see <b><a href="#poke">poke</a></b>) +into a memory-mapped control register; used esp. of various +fairly well-known tricks on <b><a href="#bittybox">bitty +box</a></b>es without hardware memory management (such as the IBM +PC and Commodore PET) that can overload and trash analog +electronics in the monitor. See also <b><a href="#HCF">HCF</a></b>.</p> + +<hr> +Node:<a name="kilo-">kilo-</a>, Next:<a rel="next" href="#KIPS">KIPS</a>, Previous:<a rel="previous" href="#killerpoke">killer poke</a>, Up:<a rel="up" href="#chap11">= K =</a> <br> + + +<p><b>kilo-</b> pref.</p> + +<p>[SI] See <b><a href="#quantifiers">quantifiers</a></b>.</p> + +<hr> +Node:<a name="KIPS">KIPS</a>, Next:<a rel="next" href="#KISSPrinciple">KISS Principle</a>, Previous:<a rel="previous" href="#kilo-">kilo-</a>, Up:<a rel="up" href="#chap11">= K =</a> <br> + + +<p><b>KIPS</b> /kips/ n.</p> + +<p>[abbreviation, by analogy with <b><a href="#MIPS">MIPS</a></b> +using <b><a href="#K">K</a></b>] Thousands (<i>not</i> 1024s) +of Instructions Per Second. Usage: rare.</p> + +<hr> +Node:<a name="KISSPrinciple">KISS Principle</a>, Next:<a rel="next" href="#kit">kit</a>, Previous:<a rel="previous" href="#KIPS">KIPS</a>, Up:<a rel="up" href="#chap11">= K =</a> +<br> + + +<p><b>KISS Principle</b> /kis' prin'si-pl/ n.</p> + +<p>"Keep It Simple, Stupid". A maxim often invoked when +discussing design to fend off <b><a href="#creepingfeaturism">creeping featurism</a></b> and control +development complexity. Possibly related to the <b><a href="#marketroid">marketroid</a></b> maxim on sales presentations, +"Keep It Short and Simple".</p> + +<hr> +Node:<a name="kit">kit</a>, Next:<a rel="next" href="#klone">klone</a>, Previous:<a rel="previous" href="#KISSPrinciple">KISS Principle</a>, Up:<a rel="up" href="#chap11">= K =</a> <br> + + +<p><b>kit</b> n.</p> + +<p>[Usenet; poss. fr. <b><a href="#DEC">DEC</a></b> slang for a +full software distribution, as opposed to a patch or upgrade] A +source software distribution that has been packaged in such a way +that it can (theoretically) be unpacked and installed according +to a series of steps using only standard Unix tools, and entirely +documented by some reasonable chain of references from the +top-level <b><a href="#READMEfile">README file</a></b>. The +more general term <b><a href="#distribution">distribution</a></b> +may imply that special tools or more stringent conditions on the +host environment are required.</p> + +<hr> +Node:<a name="klone">klone</a>, Next:<a rel="next" href="#kludge">kludge</a>, Previous:<a rel="previous" href="#kit">kit</a>, Up:<a rel="up" href="#chap11">= K =</a> +<br> + + +<p><b>klone</b> /klohn/ n.</p> + +<p>See <b><a href="#clone">clone</a></b>, sense 4.</p> + +<hr> +Node:<a name="kludge">kludge</a>, Next:<a rel="next" href="#kluge">kluge</a>, Previous:<a rel="previous" href="#klone">klone</a>, Up:<a rel="up" href="#chap11">= K +=</a> <br> + + +<p><b>kludge</b> 1. /klooj/ n.</p> + +<p>Incorrect (though regrettably common) spelling of <b><a href="#kluge">kluge</a></b> (US). These two words have been confused +in American usage since the early 1960s, and widely confounded in +Great Britain since the end of World War II. 2. [TMRC] A <b><a +href="#crock">crock</a></b> that works. (A long-ago "Datamation" +article by Jackson Granholme similarly said: "An ill-assorted +collection of poorly matching parts, forming a distressing +whole.") 3. v. To use a kludge to get around a problem. "I've +kludged around it for now, but I'll fix it up properly +later."</p> + +<p>This word appears to have derived from Scots `kludge' or +`kludgie' for a common toilet, via British military slang. It +apparently became confused with U.S. <b><a href="#kluge">kluge</a></b> during or after World War II; some Britons +from that era use both words in definably different ways, but +<b><a href="#kluge">kluge</a></b> is now uncommon in Great +Britain. `Kludge' in Commonwealth hackish differs in meaning from +`kluge' in that it lacks the positive senses; a kludge is +something no Commonwealth hacker wants to be associated too +closely with. Also, `kludge' is more widely known in British +mainstream slang than `kluge' is in the U.S.</p> + +<hr> +Node:<a name="kluge">kluge</a>, Next:<a rel="next" href="#klugearound">kluge around</a>, Previous:<a rel="previous" +href="#kludge">kludge</a>, Up:<a rel="up" href="#chap11">= +K =</a> <br> + + +<p><b>kluge</b> /klooj/</p> + +<p>[from the German `klug', clever; poss. related to Polish +`klucz' (a key, a hint, a main point)] 1. n. A Rube Goldberg (or +Heath Robinson) device, whether in hardware or software. 2. n. A +clever programming trick intended to solve a particular nasty +case in an expedient, if not clear, manner. Often used to repair +bugs. Often involves <b><a href="#ad-hockery">ad-hockery</a></b> +and verges on being a <b><a href="#crock">crock</a></b>. 3. n. +Something that works for the wrong reason. 4. vt. To insert a +kluge into a program. "I've kluged this routine to get around +that weird bug, but there's probably a better way." 5. [WPI] n. A +feature that is implemented in a <b><a href="#rude">rude</a></b> +manner.</p> + +<p>Nowadays this term is often encountered in the variant +spelling `kludge'. Reports from <b><a href="#oldfart">old +fart</a></b>s are consistent that `kluge' was the original +spelling, reported around computers as far back as the mid-1950s +and, at that time, used exclusively of <i>hardware</i> kluges. +In 1947, the "New York Folklore Quarterly" reported a classic +shaggy-dog story `Murgatroyd the Kluge Maker' then current in the +Armed Forces, in which a `kluge' was a complex and puzzling +artifact with a trivial function. Other sources report that +`kluge' was common Navy slang in the WWII era for any piece of +electronics that worked well on shore but consistently failed at +sea.</p> + +<p>However, there is reason to believe this slang use may be a +decade older. Several respondents have connected it to the brand +name of a device called a "Kluge paper feeder", an adjunct to +mechanical printing presses. Legend has it that the Kluge feeder +was designed before small, cheap electric motors and control +electronics; it relied on a fiendishly complex assortment of +cams, belts, and linkages to both power and synchronize all its +operations from one motive driveshaft. It was accordingly +temperamental, subject to frequent breakdowns, and devilishly +difficult to repair -- but oh, so clever! People who tell this +story also aver that `Kluge' was the name of a design +engineer.</p> + +<p>There is in fact a Brandtjen & Kluge Inc., an old family +business that manufactures printing equipment - interestingly, +their name is pronounced /kloo'gee/! Henry Brandtjen, president +of the firm, told me (ESR, 1994) that his company was co-founded +by his father and an engineer named Kluge /kloo'gee/, who built +and co-designed the original Kluge automatic feeder in 1919. Mr. +Brandtjen claims, however, that this was a <i>simple</i> device +(with only four cams); he says he has no idea how the myth of its +complexity took hold.</p> + +<p><b><a href="#TMRC">TMRC</a></b> and the MIT hacker culture of +the early '60s seems to have developed in a milieu that +remembered and still used some WWII military slang (see also +<b><a href="#foobar">foobar</a></b>). It seems likely that +`kluge' came to MIT via alumni of the many military electronics +projects that had been located in Cambridge (many in MIT's +venerable Building 20, in which <b><a href="#TMRC">TMRC</a></b> +is also located) during the war.</p> + +<p>The variant `kludge' was apparently popularized by the <b><a +href="#Datamation">Datamation</a></b> article mentioned above; it +was titled "How to Design a Kludge" (February 1962, pp. 30, 31). +This spelling was probably imported from Great Britain, where +<b><a href="#kludge">kludge</a></b> has an independent history +(though this fact was largely unknown to hackers on either side +of the Atlantic before a mid-1993 debate in the Usenet group +<i>alt.folklore.computers</i> over the First and Second Edition +versions of this entry; everybody used to think <b><a href="#kludge">kludge</a></b> was just a mutation of <b><a href="#kluge">kluge</a></b>). It now appears that the British, having +forgotten the etymology of their own `kludge' when `kluge' +crossed the Atlantic, repaid the U.S. by lobbing the `kludge' +orthography in the other direction and confusing their American +cousins' spelling!</p> + +<p>The result of this history is a tangle. Many younger U.S. +hackers pronounce the word as /klooj/ but spell it, incorrectly +for its meaning and pronunciation, as `kludge'. (Phonetically, +consider huge, refuge, centrifuge, and deluge as opposed to +sludge, judge, budge, and fudge. Whatever its failings in other +areas, English spelling is perfectly consistent about this +distinction.) British hackers mostly learned /kluhj/ orally, use +it in a restricted negative sense and are at least consistent. +European hackers have mostly learned the word from written +American sources and tend to pronounce it /kluhj/ but use the +wider American meaning!</p> + +<p>Some observers consider this mess appropriate in view of the +word's meaning.</p> + +<hr> +Node:<a name="klugearound">kluge around</a>, Next:<a rel="next" href="#klugeup">kluge up</a>, Previous:<a rel="previous" href="#kluge">kluge</a>, Up:<a rel="up" href="#chap11">= K =</a> <br> + + +<p><b>kluge around</b> vt.</p> + +<p>To avoid a bug or difficult condition by inserting a <b><a +href="#kluge">kluge</a></b>. Compare <b><a href="#workaround">workaround</a></b>.</p> + +<hr> +Node:<a name="klugeup">kluge up</a>, Next:<a rel="next" href="#KnightsoftheLambdaCalculus">Knights of the Lambda +Calculus</a>, Previous:<a rel="previous" href="#klugearound">kluge around</a>, Up:<a rel="up" href="#chap11">= K =</a> <br> + + +<p><b>kluge up</b> vt.</p> + +<p>To lash together a quick hack to perform a task; this is +milder than <b><a href="#crufttogether">cruft together</a></b> +and has some of the connotations of <b><a href="#hackup">hack +up</a></b> (note, however, that the construction `kluge on' +corresponding to <b><a href="#hackon">hack on</a></b> is never +used). "I've kluged up this routine to dump the buffer contents +to a safe place."</p> + +<hr> +Node:<a name="KnightsoftheLambdaCalculus">Knights of +the Lambda Calculus</a>, Next:<a rel="next" href="#knobs">knobs</a>, Previous:<a rel="previous" href="#klugeup">kluge up</a>, Up:<a rel="up" href="#chap11">= K =</a> <br> + + +<p><b>Knights of the Lambda Calculus</b> n.</p> + +<p>A semi-mythical organization of wizardly LISP and Scheme +hackers. The name refers to a mathematical formalism invented by +Alonzo Church, with which LISP is intimately connected. There is +no enrollment list and the criteria for induction are unclear, +but one well-known LISPer has been known to give out buttons and, +in general, the <i>members</i> know who they +are<small>...</small>.</p> + +<hr> +Node:<a name="knobs">knobs</a>, Next:<a rel="next" href="#Knuth">Knuth</a>, Previous:<a rel="previous" href="#KnightsoftheLambdaCalculus">Knights of the Lambda +Calculus</a>, Up:<a rel="up" href="#chap11">= K =</a> <br> + + +<p><b>knobs</b> pl.n.</p> + +<p>Configurable options, even in software and even those you +can't adjust in real time. Anything you can <b><a href="#twiddle">twiddle</a></b> is a knob. "Has this PNG viewer got an +alpha knob?" Software may be described as having "knobs and +switches" or occasionally "knobs and lights".</p> + +<hr> +Node:<a name="Knuth">Knuth</a>, Next:<a rel="next" href="#koan">koan</a>, Previous:<a rel="previous" href="#knobs">knobs</a>, Up:<a rel="up" href="#chap11">= K +=</a> <br> + + +<p><b>Knuth</b> /ka-nooth'/ n.</p> + +<p>[Donald E. Knuth's "The Art of Computer Programming"] +Mythically, the reference that answers all questions about data +structures or algorithms. A safe answer when you do not know: "I +think you can find that in Knuth." Contrast <b><a href="#theliterature">the literature</a></b>. See also <b><a href="#bible">bible</a></b>. There is a Donald Knuth home page at <a +href="http://www-cs-faculty.Stanford.EDU/~knuth">http://www-cs-faculty.Stanford.EDU/~knuth</a>.</p> + +<hr> +Node:<a name="koan">koan</a>, Next:<a rel="next" href="#kremvax">kremvax</a>, Previous:<a rel="previous" href="#Knuth">Knuth</a>, Up:<a rel="up" href="#chap11">= K +=</a> <br> + + +<p><b>koan</b> /koh'an/ n.</p> + +<p>A Zen teaching riddle. Classically, koans are attractive +paradoxes to be meditated on; their purpose is to help one to +enlightenment by temporarily jamming normal cognitive processing +so that something more interesting can happen (this practice is +associated with Rinzei Zen Buddhism). Hackers are very fond of +the koan form and compose their own koans for humororous and/or +enlightening effect. See <b><a href="#SomeAIKoans">Some AI +Koans</a></b>, <b><a href="#hastheXnature">has the X +nature</a></b>, <b><a href="#hackerhumor">hacker +humor</a></b>.</p> + +<hr> +Node:<a name="kremvax">kremvax</a>, Next:<a rel="next" href="#kyrka">kyrka</a>, Previous:<a rel="previous" href="#koan">koan</a>, Up:<a rel="up" href="#chap11">= K =</a> +<br> + + +<p><b>kremvax</b> /krem-vaks/ n.</p> + +<p>[from the then large number of <b><a href="#Usenet">Usenet</a></b> <b><a href="#VAXen">VAXen</a></b> with +names of the form <i>foovax</i>] Originally, a fictitious Usenet +site at the Kremlin, announced on April 1, 1984 in a posting +ostensibly originated there by Soviet leader Konstantin +Chernenko. The posting was actually forged by Piet Beertema as an +April Fool's joke. Other fictitious sites mentioned in the hoax +were <i>moskvax</i> and <b><a href="#kgbvax">kgbvax</a></b>. This +was probably the funniest of the many April Fool's forgeries +perpetrated on Usenet (which has negligible security against +them), because the notion that Usenet might ever penetrate the +Iron Curtain seemed so totally absurd at the time.</p> + +<p>In fact, it was only six years later that the first genuine +site in Moscow, <i>demos.su</i>, joined Usenet. Some readers +needed convincing that the postings from it weren't just another +prank. Vadim Antonov, senior programmer at Demos and the major +poster from there up to mid-1991, was quite aware of all this, +referred to it frequently in his own postings, and at one point +twitted some credulous readers by blandly asserting that he +<i>was</i> a hoax!</p> + +<p>Eventually he even arranged to have the domain's gateway site +named <i>kremvax</i>, thus neatly turning fiction into fact and +demonstrating that the hackish sense of humor transcends cultural +barriers. [Mr. Antonov also contributed the Russian-language +material for this lexicon. --ESR]</p> + +<p>In an even more ironic historical footnote, <i>kremvax</i> +became an electronic center of the anti-communist resistance +during the bungled hard-line coup of August 1991. During those +three days the Soviet UUCP network centered on <i>kremvax</i> +became the only trustworthy news source for many places within +the USSR. Though the sysops were concentrating on internal +communications, cross-border postings included immediate +transliterations of Boris Yeltsin's decrees condemning the coup +and eyewitness reports of the demonstrations in Moscow's streets. +In those hours, years of speculation that totalitarianism would +prove unable to maintain its grip on politically-loaded +information in the age of computer networking were proved +devastatingly accurate -- and the original <i>kremvax</i> joke +became a reality as Yeltsin and the new Russian revolutionaries +of `glasnost' and `perestroika' made <i>kremvax</i> one of the +timeliest means of their outreach to the West.</p> + +<hr> +Node:<a name="kyrka">kyrka</a>, Next:<a rel="next" href="#lacecard">lace card</a>, Previous:<a rel="previous" href="#kremvax">kremvax</a>, Up:<a rel="up" href="#chap11">= K +=</a> <br> + + +<p><b>kyrka</b> /chur'ka/ n.</p> + +<p>[Swedish] See <b><a href="#featurekey">feature +key</a></b>.</p> + +<hr> +Node:<a name="chap12">= L =</a>, Next:<a rel="next" href="#chap13">= M =</a>, Previous:<a rel="previous" href="#chap11">= K =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= L =</h2> + +<ul> +<li><a href="#lacecard">lace card</a>:</li> + +<li><a href="#lag">lag</a>:</li> + +<li><a href="#lamer">lamer</a>:</li> + +<li><a href="#languagelawyer">language lawyer</a>:</li> + +<li><a href="#languagesofchoice">languages of +choice</a>:</li> + +<li><a href="#LART">LART</a>:</li> + +<li><a href="#larvalstage">larval stage</a>:</li> + +<li><a href="#lase">lase</a>:</li> + +<li><a href="#laserchicken">laser chicken</a>:</li> + +<li><a href="#lasherism">lasherism</a>:</li> + +<li><a href="#laundromat">laundromat</a>:</li> + +<li><a href="#LDB">LDB</a>:</li> + +<li><a href="#leafsite">leaf site</a>:</li> + +<li><a href="#leak">leak</a>:</li> + +<li><a href="#leakyheap">leaky heap</a>:</li> + +<li><a href="#leapfrogattack">leapfrog attack</a>:</li> + +<li><a href="#leech">leech</a>:</li> + +<li><a href="#leechmode">leech mode</a>:</li> + +<li><a href="#legal">legal</a>:</li> + +<li><a href="#legalese">legalese</a>:</li> + +<li><a href="#LER">LER</a>:</li> + +<li><a href="#LERP">LERP</a>:</li> + +<li><a href="#letthesmokeout">let the smoke +out</a>:</li> + +<li><a href="#letterbomb">letterbomb</a>:</li> + +<li><a href="#lexer">lexer</a>:</li> + +<li><a href="#lexiphage">lexiphage</a>:</li> + +<li><a href="#life">life</a>:</li> + +<li><a href="#Lifeishard">Life is hard</a>:</li> + +<li><a href="#lightpipe">light pipe</a>:</li> + +<li><a href="#lightweight">lightweight</a>:</li> + +<li><a href="#likekickingdeadwhalesdownthebeach">like kicking dead whales down the beach</a>:</li> + +<li><a href="#likenailingjellytoatree">like nailing jelly to a tree</a>:</li> + +<li><a href="#line666">line 666</a>:</li> + +<li><a href="#lineeaterthe">line eater the</a>:</li> + +<li><a href="#linenoise">line noise</a>:</li> + +<li><a href="#linestarve">line starve</a>:</li> + +<li><a href="#linearithmic">linearithmic</a>:</li> + +<li><a href="#linkfarm">link farm</a>:</li> + +<li><a href="#linkrot">link rot</a>:</li> + +<li><a href="#link-dead">link-dead</a>:</li> + +<li><a href="#lint">lint</a>:</li> + +<li><a href="#Lintel">Lintel</a>:</li> + +<li><a href="#Linus">Linus</a>:</li> + +<li><a href="#Linux">Linux</a>:</li> + +<li><a href="#lionfood">lion food</a>:</li> + +<li><a href="#LionsBook">Lions Book</a>:</li> + +<li><a href="#LISP">LISP</a>:</li> + +<li><a href="#list-bomb">list-bomb</a>:</li> + +<li><a href="#lithiumlick">lithium lick</a>:</li> + +<li><a href="#little-endian">little-endian</a>:</li> + +<li><a href="#live">live</a>:</li> + +<li><a href="#livedata">live data</a>:</li> + +<li><a href="#LiveFreeOrDie">Live Free Or +Die!</a>:</li> + +<li><a href="#livelock">livelock</a>:</li> + +<li><a href="#liveware">liveware</a>:</li> + +<li><a href="#lobotomy">lobotomy</a>:</li> + +<li><a href="#localsthe">locals the</a>:</li> + +<li><a href="#lockedandloaded">locked and loaded</a>:</li> + +<li><a href="#lockedup">locked up</a>:</li> + +<li><a href="#logicbomb">logic bomb</a>:</li> + +<li><a href="#logical">logical</a>:</li> + +<li><a href="#loopthrough">loop through</a>:</li> + +<li><a href="#loosebytes">loose bytes</a>:</li> + +<li><a href="#lordhighfixer">lord high fixer</a>:</li> + +<li><a href="#lose">lose</a>:</li> + +<li><a href="#loselose">lose lose</a>:</li> + +<li><a href="#loser">loser</a>:</li> + +<li><a href="#losing">losing</a>:</li> + +<li><a href="#loss">loss</a>:</li> + +<li><a href="#lossage">lossage</a>:</li> + +<li><a href="#lostinthenoise">lost in the noise</a>:</li> + +<li><a href="#lostintheunderflow">lost in the +underflow</a>:</li> + +<li><a href="#lotsofMIPSbutnoIO">lots of MIPS but no I/O</a>:</li> + +<li><a href="#low-bandwidth">low-bandwidth</a>:</li> + +<li><a href="#LPT">LPT</a>:</li> + +<li><a href="#LubarskysLawofCyberneticEntomology">Lubarsky's Law +of Cybernetic Entomology</a>:</li> + +<li><a href="#LumberCartel">Lumber Cartel</a>:</li> + +<li><a href="#lunaticfringe">lunatic fringe</a>:</li> + +<li><a href="#lurker">lurker</a>:</li> + +<li><a href="#luser">luser</a>:</li> +</ul> + +<hr> +Node:<a name="lacecard">lace card</a>, Next:<a rel="next" +href="#lag">lag</a>, Previous:<a rel="previous" href="#kyrka">kyrka</a>, Up:<a rel="up" href="#chap12">= L +=</a> <br> + + +<p><b>lace card</b> n. obs.</p> + +<p>A <b><a href="#punchedcard">punched card</a></b> with all +holes punched (also called a `whoopee card' or `ventilator +card'). Card readers tended to jam when they got to one of these, +as the resulting card had too little structural strength to avoid +buckling inside the mechanism. Card punches could also jam trying +to produce these things owing to power-supply problems. When some +practical joker fed a lace card through the reader, you needed to +clear the jam with a `card knife' -- which you used on the joker +first.</p> + +<hr> +Node:<a name="lag">lag</a>, Next:<a rel="next" href="#lamer">lamer</a>, Previous:<a rel="previous" href="#lacecard">lace card</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>lag</b> n.</p> + +<p>[MUD, IRC; very common] When used without qualification this +is synomous with <b><a href="#netlag">netlag</a></b>. Curiously, +people will often complain "I'm really lagged" when in fact it is +their server or network connection that is lagging.</p> + +<hr> +Node:<a name="lamer">lamer</a>, Next:<a rel="next" href="#languagelawyer">language lawyer</a>, Previous:<a rel="previous" href="#lag">lag</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>lamer</b> n.</p> + +<p>[prob. originated in skateboarder slang] 1. Synonym for <b><a +href="#luser">luser</a></b>, not used much by hackers but common +among <b><a href="#warezd00dz">warez d00dz</a></b>, crackers, +and <b><a href="#phreaker">phreaker</a></b>s. A person who +downloads much, but who never uploads. (Also known as `leecher'). +Oppose <b><a href="#elite">elite</a></b>. Has the same +connotations of self-conscious elitism that use of <b><a href="#luser">luser</a></b> does among hackers. 2. Someone who tries +to crack a BBS. 3. Someone who annoys the sysop or other BBS +users - for instance, by posting lots of silly messages, +uploading virus-ridden software, frequently dropping carrier, +etc.</p> + +<p>Crackers also use it to refer to cracker <b><a href="#wannabee">wannabee</a></b>s. In phreak culture, a lamer is one +who scams codes off others rather than doing cracks or really +understanding the fundamental concepts. In <b><a href="#warezd00dz">warez d00dz</a></b> culture, where the ability +to wave around cracked commercial software within days of (or +before) release to the commercial market is much esteemed, the +lamer might try to upload garbage or shareware or something +incredibly old (old in this context is read as a few years to +anything older than 3 days).</p> + +<p>`Lamer' is also much used in the IRC world in a similar sense +to the above.</p> + +<hr> +Node:<a name="languagelawyer">language lawyer</a>, Next:<a +rel="next" href="#languagesofchoice">languages of +choice</a>, Previous:<a rel="previous" href="#lamer">lamer</a>, +Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>language lawyer</b> n.</p> + +<p>A person, usually an experienced or senior software engineer, +who is intimately familiar with many or most of the numerous +restrictions and features (both useful and esoteric) applicable +to one or more computer programming languages. A language lawyer +is distinguished by the ability to show you the five sentences +scattered through a 200-plus-page manual that together imply the +answer to your question "if only you had thought to look there". +Compare <b><a href="#wizard">wizard</a></b>, <b><a href="#legal">legal</a></b>, <b><a href="#legalese">legalese</a></b>.</p> + +<hr> +Node:<a name="languagesofchoice">languages of choice</a>, +Next:<a rel="next" href="#LART">LART</a>, Previous:<a rel="previous" href="#languagelawyer">language lawyer</a>, Up:<a +rel="up" href="#chap12">= L =</a> <br> + + +<p><b>languages of choice</b> n.</p> + +<p><b><a href="#C">C</a></b>, <b><a href="#Cplusplus">C++</a></b>, +<b><a href="#LISP">LISP</a></b>, and <b><a href="#Perl">Perl</a></b>. Nearly every hacker knows one of C or LISP, +and most good ones are fluent in both. C++, despite some serious +drawbacks, is generally preferred to other object-oriented +languages (though in 1999 it looks as though <b><a href="#Java">Java</a></b> has displaced it in the affections of +hackers, if not everywhere). Since around 1990 Perl has rapidly +been gaining favor, especially as a tool for +systems-administration utilities and rapid prototyping. <b><a +href="#Python">Python</a></b>, Smalltalk and Prolog are also +popular in small but influential communities.</p> + +<p>There is also a rapidly dwindling category of older hackers +with FORTRAN, or even assembler, as their language of choice. +They often prefer to be known as <b><a href="#RealProgrammer">Real Programmer</a></b>s, and other hackers +consider them a bit odd (see "<b><a href="#TheStoryofMel">The Story of Mel</a></b>" in Appendix +A). Assembler is generally no longer considered interesting or +appropriate for anything but <b><a href="#HLL">HLL</a></b> +implementation, <b><a href="#glue">glue</a></b>, and a few +time-critical and hardware-specific uses in systems programs. +FORTRAN occupies a shrinking niche in scientific programming.</p> + +<p>Most hackers tend to frown on languages like <b><a href="#Pascal">Pascal</a></b> and <b><a href="#Ada">Ada</a></b>, which +don't give them the near-total freedom considered necessary for +hacking (see <b><a href="#bondage-and-disciplinelanguage">bondage-and-discipline +language</a></b>), and to regard everything even remotely +connected with <b><a href="#COBOL">COBOL</a></b> or other +traditional <b><a href="#cardwalloper">card walloper</a></b> +languages as a total and unmitigated <b><a href="#loss">loss</a></b>.</p> + +<hr> +Node:<a name="LART">LART</a>, Next:<a rel="next" href="#larvalstage">larval stage</a>, Previous:<a rel="previous" +href="#languagesofchoice">languages of choice</a>, Up:<a +rel="up" href="#chap12">= L =</a> <br> + + +<p><b>LART</b> //</p> + +<p>Luser Attitude Readjustment Tool. 1. n. In the collective +mythos of <b><a href="#scarydevilmonastery">scary devil +monastery</a></b>, this is an essential item in the toolkit of +every <b><a href="#BOFH">BOFH</a></b>. The LART classic is a 2x4 +or other large billet of wood usable as a club, to be applied +upside the head of spammers and other people who cause sysadmins +more grief than just naturally goes with the job. Perennial +debates rage on <i>alt.sysadmin.recovery</i> over what +constitutes the truly effective LART; knobkerries, semiautomatic +weapons, flamethrowers, and tactical nukes all have their +partisans. Compare <b><a href="#clue-by-four">clue-by-four</a></b>. 2. v. To use a LART. Some +would add "in malice", but some sysadmins do prefer to gently +lart their users as a first (and sometimes final) warning. 3. +interj. Calling for one's LART, much as a surgeon might call +"Scalpel!". 4. interj. [rare] Used in <b><a href="#flame">flame</a></b>s as a rebuke. "LART! LART! LART!"</p> + +<hr> +Node:<a name="larvalstage">larval stage</a>, Next:<a rel="next" href="#lase">lase</a>, Previous:<a rel="previous" href="#LART">LART</a>, Up:<a rel="up" href="#chap12">= L =</a> +<br> + + +<p><b>larval stage</b> n.</p> + +<p>Describes a period of monomaniacal concentration on coding +apparently passed through by all fledgling hackers. Common +symptoms include the perpetration of more than one 36-hour <b><a +href="#hackingrun">hacking run</a></b> in a given week; +neglect of all other activities including usual basics like food, +sleep, and personal hygiene; and a chronic case of advanced +bleary-eye. Can last from 6 months to 2 years, the apparent +median being around 18 months. A few so afflicted never resume a +more `normal' life, but the ordeal seems to be necessary to +produce really wizardly (as opposed to merely competent) +programmers. See also <b><a href="#wannabee">wannabee</a></b>. A +less protracted and intense version of larval stage (typically +lasting about a month) may recur when one is learning a new <b><a +href="#OS">OS</a></b> or programming language.</p> + +<hr> +Node:<a name="lase">lase</a>, Next:<a rel="next" href="#laserchicken">laser chicken</a>, Previous:<a rel="previous" +href="#larvalstage">larval stage</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>lase</b> /layz/ vt.</p> + +<p>To print a given document via a laser printer. "OK, let's lase +that sucker and see if all those graphics-macro calls did the +right things."</p> + +<hr> +Node:<a name="laserchicken">laser chicken</a>, Next:<a rel="next" href="#lasherism">lasherism</a>, Previous:<a rel="previous" href="#lase">lase</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>laser chicken</b> n.</p> + +<p>Kung Pao Chicken, a standard Chinese dish containing chicken, +peanuts, and hot red peppers in a spicy pepper-oil sauce. Many +hackers call it `laser chicken' for two reasons: It can <b><a +href="#zap">zap</a></b> you just like a laser, and the sauce has +a red color reminiscent of some laser beams. The dish has also +been called `gunpowder chicken'.</p> + +<p>In a variation on this theme, it is reported that some +Australian hackers have redesignated the common dish `lemon +chicken' as `Chernobyl Chicken'. The name is derived from the +color of the sauce, which is considered bright enough to glow in +the dark (as, mythically, do some of the inhabitants of +Chernobyl).</p> + +<hr> +Node:<a name="lasherism">lasherism</a>, Next:<a rel="next" href="#laundromat">laundromat</a>, Previous:<a rel="previous" href="#laserchicken">laser chicken</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>lasherism</b> n.</p> + +<p>[Harvard] A program that solves a standard problem (such as +the Eight Queens puzzle or implementing the <b><a href="#life">life</a></b> algorithm) in a deliberately nonstandard +way. Distinguished from a <b><a href="#crock">crock</a></b> or +<b><a href="#kluge">kluge</a></b> by the fact that the programmer +did it on purpose as a mental exercise. Such constructions are +quite popular in exercises such as the <b><a href="#ObfuscatedCContest">Obfuscated C Contest</a></b>, and +occasionally in <b><a href="#retrocomputing">retrocomputing</a></b>. Lew Lasher was a +student at Harvard around 1980 who became notorious for such +behavior.</p> + +<hr> +Node:<a name="laundromat">laundromat</a>, Next:<a rel="next" +href="#LDB">LDB</a>, Previous:<a rel="previous" href="#lasherism">lasherism</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>laundromat</b> n.</p> + +<p>Syn. <b><a href="#diskfarm">disk farm</a></b>; see <b><a +href="#washingmachine">washing machine</a></b>.</p> + +<hr> +Node:<a name="LDB">LDB</a>, Next:<a rel="next" href="#leafsite">leaf site</a>, Previous:<a rel="previous" href="#laundromat">laundromat</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>LDB</b> /l*'d*b/ vt.</p> + +<p>[from the PDP-10 instruction set] To extract from the middle. +"LDB me a slice of cake, please." This usage has been kept alive +by Common LISP's function of the same name. Considered silly. See +also <b><a href="#DPB">DPB</a></b>.</p> + +<hr> +Node:<a name="leafsite">leaf site</a>, Next:<a rel="next" +href="#leak">leak</a>, Previous:<a rel="previous" href="#LDB">LDB</a>, Up:<a rel="up" href="#chap12">= L =</a> +<br> + + +<p><b>leaf site</b> n.,obs.</p> + +<p>Before pervasive TCP/IP, this term was used of a machine that +merely originated and read Usenet news or mail, and did not relay +any third-party traffic. It was often uttered in a critical tone; +when the ratio of leaf sites to backbone, rib, and other relay +sites got too high, the network tended to develop bottlenecks. +Compare <b><a href="#backbonesite">backbone site</a></b>, +<b><a href="#ribsite">rib site</a></b>. Now that traffic +patterns depend more on the distribution of routers than of host +machines this term has largely fallen out of use.</p> + +<hr> +Node:<a name="leak">leak</a>, Next:<a rel="next" href="#leakyheap">leaky heap</a>, Previous:<a rel="previous" href="#leafsite">leaf site</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>leak</b> n.</p> + +<p>With qualifier, one of a class of resource-management bugs +that occur when resources are not freed properly after operations +on them are finished, so they effectively disappear (leak out). +This leads to eventual exhaustion as new allocation requests come +in. <b><a href="#memoryleak">memory leak</a></b> and <b><a +href="#fdleak">fd leak</a></b> have their own entries; one +might also refer, to, say, a `window handle leak' in a window +system.</p> + +<hr> +Node:<a name="leakyheap">leaky heap</a>, Next:<a rel="next" +href="#leapfrogattack">leapfrog attack</a>, Previous:<a rel="previous" href="#leak">leak</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>leaky heap</b> n.</p> + +<p>[Cambridge] An <b><a href="#arena">arena</a></b> with a <b><a +href="#memoryleak">memory leak</a></b>.</p> + +<hr> +Node:<a name="leapfrogattack">leapfrog attack</a>, Next:<a +rel="next" href="#leech">leech</a>, Previous:<a rel="previous" +href="#leakyheap">leaky heap</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>leapfrog attack</b> n.</p> + +<p>Use of userid and password information obtained illicitly from +one host (e.g., downloading a file of account IDs and passwords, +tapping TELNET, etc.) to compromise another host. Also, the act +of TELNETting through one or more hosts in order to confuse a +trace (a standard cracker procedure).</p> + +<hr> +Node:<a name="leech">leech</a>, Next:<a rel="next" href="#leechmode">leech mode</a>, Previous:<a rel="previous" href="#leapfrogattack">leapfrog attack</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>leech</b></p> + +<p>1. n. (Also `leecher'.) Among BBS types, crackers and <b><a +href="#warezd00dz">warez d00dz</a></b>, one who consumes +knowledge without generating new software, cracks, or techniques. +BBS culture specifically defines a leech as someone who downloads +files with few or no uploads in return, and who does not +contribute to the message section. Cracker culture extends this +definition to someone (a <b><a href="#lamer">lamer</a></b>, +usually) who constantly presses informed sources for information +and/or assistance, but has nothing to contribute. 2. v. [common, +Toronto area] To instantly fetch a file (other than a mail +attachment) whether by FTP or IRC file req or any other method. +Seems to be a holdover from the early 1990s when Toronto had a +very active BBS and warez scene.</p> + +<hr> +Node:<a name="leechmode">leech mode</a>, Next:<a rel="next" +href="#legal">legal</a>, Previous:<a rel="previous" href="#leech">leech</a>, Up:<a rel="up" href="#chap12">= L +=</a> <br> + + +<p><b>leech mode</b> n.</p> + +<p>[warez d00dz] "Leech mode" or "leech access" or (simply +"leech" as in "You get leech") is the access mode on a FTP site +where one can download as many files as one wants, without having +to upload. Leech mode is often promised on banner sites, but +rarely obtained. See <b><a href="#ratiosite">ratio +site</a></b>, <b><a href="#bannersite">banner +site</a></b>.</p> + +<hr> +Node:<a name="legal">legal</a>, Next:<a rel="next" href="#legalese">legalese</a>, Previous:<a rel="previous" href="#leechmode">leech mode</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>legal</b> adj.</p> + +<p>Loosely used to mean `in accordance with all the relevant +rules', esp. in connection with some set of constraints defined +by software. "The older =+ alternate for += is no longer legal +syntax in ANSI C." "This parser processes each line of legal +input the moment it sees the trailing linefeed." Hackers often +model their work as a sort of game played with the environment in +which the objective is to maneuver through the thicket of +`natural laws' to achieve a desired objective. Their use of +`legal' is flavored as much by this game-playing sense as by the +more conventional one having to do with courts and lawyers. +Compare <b><a href="#languagelawyer">language lawyer</a></b>, +<b><a href="#legalese">legalese</a></b>.</p> + +<hr> +Node:<a name="legalese">legalese</a>, Next:<a rel="next" href="#LER">LER</a>, Previous:<a rel="previous" href="#legal">legal</a>, Up:<a rel="up" href="#chap12">= L +=</a> <br> + + +<p><b>legalese</b> n.</p> + +<p>Dense, pedantic verbiage in a language description, product +specification, or interface standard; text that seems designed to +obfuscate and requires a <b><a href="#languagelawyer">language +lawyer</a></b> to <b><a href="#parse">parse</a></b> it. Though +hackers are not afraid of high information density and complexity +in language (indeed, they rather enjoy both), they share a deep +and abiding loathing for legalese; they associate it with +deception, <b><a href="#suit">suit</a></b>s, and situations in +which hackers generally get the short end of the stick.</p> + +<hr> +Node:<a name="LER">LER</a>, Next:<a rel="next" href="#LERP">LERP</a>, Previous:<a rel="previous" href="#legalese">legalese</a>, Up:<a rel="up" href="#chap12">= +L =</a> <br> + + +<p><b>LER</b> /L-E-R/</p> + +<p>n. 1. [TMRC, from `Light-Emitting Diode'] A light-emitting +resistor (that is, one in the process of burning up). Ohm's law +was broken. See also <b><a href="#SED">SED</a></b>. 2. An +incandescent light bulb (the filament emits light because it's +resistively heated).</p> + +<hr> +Node:<a name="LERP">LERP</a>, Next:<a rel="next" href="#letthesmokeout">let the smoke out</a>, Previous:<a +rel="previous" href="#LER">LER</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>LERP</b> /lerp/ vi.,n.</p> + +<p>Quasi-acronym for Linear Interpolation, used as a verb or noun +for the operation. "Bresenham's algorithm lerps incrementally +between the two endpoints of the line."</p> + +<hr> +Node:<a name="letthesmokeout">let the smoke out</a>, +Next:<a rel="next" href="#letterbomb">letterbomb</a>, Previous:<a +rel="previous" href="#LERP">LERP</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>let the smoke out</b> v.</p> + +<p>To fry hardware (see <b><a href="#fried">fried</a></b>). See +<b><a href="#magicsmoke">magic smoke</a></b> for a discussion +of the underlying mythology.</p> + +<hr> +Node:<a name="letterbomb">letterbomb</a>, Next:<a rel="next" +href="#lexer">lexer</a>, Previous:<a rel="previous" href="#letthesmokeout">let the smoke out</a>, Up:<a rel="up" +href="#chap12">= L =</a> <br> + + +<p><b>letterbomb</b></p> + +<p>1. n. A piece of <b><a href="#email">email</a></b> containing +<b><a href="#livedata">live data</a></b> intended to do +nefarious things to the recipient's machine or terminal. It used +to be possible, for example, to send letterbombs that would lock +up some specific kinds of terminals when they are viewed, so +thoroughly that the user must cycle power (see <b><a href="#cycle">cycle</a></b>, sense 3) to unwedge them. Under Unix, a +letterbomb can also try to get part of its contents interpreted +as a shell command to the mailer. The results of this could range +from silly to tragic; fortunately it has been some years since +any of the standard Unix/Internet mail software was vulnerable to +such an attack (though, as the Melissa virus attack demonstrated +in early 1999, Microsoft systems can have serious problems). See +also <b><a href="#Trojanhorse">Trojan horse</a></b>; compare +<b><a href="#nastygram">nastygram</a></b>. 2. Loosely, a <b><a +href="#mailbomb">mailbomb</a></b>.</p> + +<hr> +Node:<a name="lexer">lexer</a>, Next:<a rel="next" href="#lexiphage">lexiphage</a>, Previous:<a rel="previous" href="#letterbomb">letterbomb</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>lexer</b> /lek'sr/ n.</p> + +<p>Common hacker shorthand for `lexical analyzer', the +input-tokenizing stage in the parser for a language (the part +that breaks it into word-like pieces). "Some C lexers get +confused by the old-style compound ops like <code>=-</code>."</p> + +<hr> +Node:<a name="lexiphage">lexiphage</a>, Next:<a rel="next" href="#life">life</a>, Previous:<a rel="previous" href="#lexer">lexer</a>, Up:<a rel="up" href="#chap12">= L +=</a> <br> + + +<p><b>lexiphage</b> /lek'si-fayj`/ n.</p> + +<p>A notorious word <b><a href="#chomper">chomper</a></b> on ITS. +See <b><a href="#bagbiter">bagbiter</a></b>. This program would +draw on a selected victim's bitmapped terminal the words "THE +BAG" in ornate letters, followed a pair of jaws biting pieces of +it off.</p> + +<hr> +Node:<a name="life">life</a>, Next:<a rel="next" href="#Lifeishard">Life is hard</a>, Previous:<a rel="previous" +href="#lexiphage">lexiphage</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>life</b> n.</p> + +<p>1. A cellular-automata game invented by John Horton Conway and +first introduced publicly by Martin Gardner ("Scientific +American", October 1970); the game's popularity had to wait a few +years for computers on which it could reasonably be played, as +it's no fun to simulate the cells by hand. Many hackers pass +through a stage of fascination with it, and hackers at various +places contributed heavily to the mathematical analysis of this +game (most notably Bill Gosper at MIT, who even implemented life +in <b><a href="#TECO">TECO</a></b>!; see <b><a href="#Gosperism">Gosperism</a></b>). When a hacker mentions `life', +he is much more likely to mean this game than the magazine, the +breakfast cereal, or the human state of existence. 2. The +opposite of <b><a href="#Usenet">Usenet</a></b>. As in "<b><a +href="#Getalife">Get a life!</a></b>"</p> + +<hr> +Node:<a name="Lifeishard">Life is hard</a>, Next:<a rel="next" href="#lightpipe">light pipe</a>, Previous:<a rel="previous" href="#life">life</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>Life is hard</b> prov.</p> + +<p>[XEROX PARC] This phrase has two possible interpretations: (1) +"While your suggestion may have some merit, I will behave as +though I hadn't heard it." (2) "While your suggestion has obvious +merit, equally obvious circumstances prevent it from being +seriously considered." The charm of the phrase lies precisely in +this subtle but important ambiguity.</p> + +<hr> +Node:<a name="lightpipe">light pipe</a>, Next:<a rel="next" +href="#lightweight">lightweight</a>, Previous:<a rel="previous" +href="#Lifeishard">Life is hard</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>light pipe</b> n.</p> + +<p>Fiber optic cable. Oppose <b><a href="#copper">copper</a></b>.</p> + +<hr> +Node:<a name="lightweight">lightweight</a>, Next:<a rel="next" +href="#likekickingdeadwhalesdownthebeach">like +kicking dead whales down the beach</a>, Previous:<a rel="previous" href="#lightpipe">light pipe</a>, Up:<a rel="up" +href="#chap12">= L =</a> <br> + + +<p><b>lightweight</b> adj.</p> + +<p>Opposite of <b><a href="#heavyweight">heavyweight</a></b>; +usually found in combining forms such as `lightweight +process'.</p> + +<hr> +Node:<a name="likekickingdeadwhalesdownthebeach">like +kicking dead whales down the beach</a>, Next:<a rel="next" href="#likenailingjellytoatree">like nailing jelly to a +tree</a>, Previous:<a rel="previous" href="#lightweight">lightweight</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>like kicking dead whales down the beach</b> adj.</p> + +<p>Describes a slow, difficult, and disgusting process. First +popularized by a famous quote about the difficulty of getting +work done under one of IBM's mainframe OSes. "Well, you +<i>could</i> write a C compiler in COBOL, but it would be like +kicking dead whales down the beach." See also <b><a href="#fearandloathing">fear and loathing</a></b>.</p> + +<hr> +Node:<a name="likenailingjellytoatree">like +nailing jelly to a tree</a>, Next:<a rel="next" href="#line666">line 666</a>, Previous:<a rel="previous" href="#likekickingdeadwhalesdownthebeach">like +kicking dead whales down the beach</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>like nailing jelly to a tree</b> adj.</p> + +<p>Used to describe a task thought to be impossible, esp. one in +which the difficulty arises from poor specification or inherent +slipperiness in the problem domain. "Trying to display the +`prettiest' arrangement of nodes and arcs that diagrams a given +graph is like nailing jelly to a tree, because nobody's sure what +`prettiest' means algorithmically."</p> + +<p>Hacker use of this term may recall mainstream slang originated +early in the 20th century by President Theodore Roosevelt. There +is a legend that, weary of inconclusive talks with Colombia over +the right to dig a canal through its then-province Panama, he +remarked, "Negotiating with those pirates is like trying to nail +currant jelly to the wall." Roosevelt's government subsequently +encouraged the anti-Colombian insurgency that created the nation +of Panama.</p> + +<hr> +Node:<a name="line666">line 666</a>, Next:<a rel="next" href="#lineeaterthe">line eater the</a>, Previous:<a rel="previous" href="#likenailingjellytoatree">like +nailing jelly to a tree</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>line 666</b> [from Christian eschatological myth] n.</p> + +<p>The notional line of source at which a program fails for +obscure reasons, implying either that <i>somebody</i> is out to +get it (when you are the programmer), or that it richly deserves +to be so gotten (when you are not). "It works when I trace +through it, but seems to crash on line 666 when I run it." "What +happens is that whenever a large batch comes through, mmdf dies +on the Line of the Beast. Probably some twit hardcoded a buffer +size."</p> + +<hr> +Node:<a name="lineeaterthe">line eater the</a>, Next:<a +rel="next" href="#linenoise">line noise</a>, Previous:<a rel="previous" href="#line666">line 666</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>line eater, the</b> n. obs.</p> + +<p>[Usenet] 1. A bug in some now-obsolete versions of the netnews +software that used to eat up to BUFSIZ bytes of the article text. +The bug was triggered by having the text of the article start +with a space or tab. This bug was quickly personified as a +mythical creature called the `line eater', and postings often +included a dummy line of `line eater food'. Ironically, line +eater `food' not beginning with a space or tab wasn't actually +eaten, since the bug was avoided; but if there <i>was</i> a +space or tab before it, then the line eater would eat the food +<i>and</i> the beginning of the text it was supposed to be +protecting. The practice of `sacrificing to the line eater' +continued for some time after the bug had been <b><a href="#nailedtothewall">nailed to the wall</a></b>, and is +still humorously referred to. The bug itself was still +occasionally reported to be lurking in some mail-to-netnews +gateways as late as 1991. 2. See <b><a href="#NSAlineeater">NSA line eater</a></b>.</p> + +<hr> +Node:<a name="linenoise">line noise</a>, Next:<a rel="next" +href="#linestarve">line starve</a>, Previous:<a rel="previous" +href="#lineeaterthe">line eater the</a>, Up:<a rel="up" +href="#chap12">= L =</a> <br> + + +<p><b>line noise</b> n.</p> + +<p>1. [techspeak] Spurious characters due to electrical noise in +a communications link, especially an RS-232 serial connection. +Line noise may be induced by poor connections, interference or +crosstalk from other circuits, electrical storms, <b><a href="#cosmicrays">cosmic rays</a></b>, or (notionally) birds +crapping on the phone wires. 2. Any chunk of data in a file or +elsewhere that looks like the results of line noise in sense 1. +3. Text that is theoretically a readable text or program source +but employs syntax so bizarre that it looks like line noise in +senses 1 or 2. Yes, there are languages this ugly. The canonical +example is <b><a href="#TECO">TECO</a></b>; it is often claimed +that "TECO's input syntax is indistinguishable from line noise." +Other non-<b><a href="#WYSIWYG">WYSIWYG</a></b> editors, such as +Multics <code>qed</code> and Unix <code>ed</code>, in the hands +of a real hacker, also qualify easily, as do deliberately +obfuscated languages such as <b><a href="#INTERCAL">INTERCAL</a></b>.</p> + +<hr> +Node:<a name="linestarve">line starve</a>, Next:<a rel="next" +href="#linearithmic">linearithmic</a>, Previous:<a rel="previous" +href="#linenoise">line noise</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>line starve</b></p> + +<p>[MIT] 1. vi. To feed paper through a printer the wrong way by +one line (most printers can't do this). On a display terminal, to +move the cursor up to the previous line of the screen. "To print +`X squared', you just output `X', line starve, `2', line feed." +(The line starve causes the `2' to appear on the line above the +`X', and the line feed gets back to the original line.) 2. n. A +character (or character sequence) that causes a terminal to +perform this action. ASCII 0011010, also called SUB or control-Z, +was one common line-starve character in the days before +microcomputers and the X3.64 terminal standard. Today, the term +might be used for the ISO reverse line feed character 0x8D. +Unlike `line feed', `line starve' is <i>not</i> standard <b><a +href="#ASCII">ASCII</a></b> terminology. Even among hackers it is +considered a bit silly. 3. [proposed] A sequence such as \c (used +in System V echo, as well as <b><a href="#nroff">nroff</a></b> +and <b><a href="#troff">troff</a></b>) that suppresses a <b><a +href="#newline">newline</a></b> or other character(s) that would +normally be emitted.</p> + +<hr> +Node:<a name="linearithmic">linearithmic</a>, Next:<a rel="next" +href="#linkfarm">link farm</a>, Previous:<a rel="previous" +href="#linestarve">line starve</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>linearithmic</b> adj.</p> + +<p>Of an algorithm, having running time that is O(N log N). +Coined as a portmanteau of `linear' and `logarithmic' in +"Algorithms In C" by Robert Sedgewick (Addison-Wesley 1990, ISBN +0-201-51425-7).</p> + +<hr> +Node:<a name="linkfarm">link farm</a>, Next:<a rel="next" +href="#linkrot">link rot</a>, Previous:<a rel="previous" href="#linearithmic">linearithmic</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>link farm</b> n.</p> + +<p>[Unix] A directory tree that contains many links to files in a +master directory tree of files. Link farms save space when one is +maintaining several nearly identical copies of the same source +tree -- for example, when the only difference is +architecture-dependent object files. "Let's freeze the source and +then rebuild the FROBOZZ-3 and FROBOZZ-4 link farms." Link farms +may also be used to get around restrictions on the number of +<code>-I</code> (include-file directory) arguments on older C +preprocessors. However, they can also get completely out of hand, +becoming the filesystem equivalent of <b><a href="#spaghetticode">spaghetti code</a></b>.</p> + +<hr> +Node:<a name="linkrot">link rot</a>, Next:<a rel="next" href="#link-dead">link-dead</a>, Previous:<a rel="previous" href="#linkfarm">link farm</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>link rot</b> n.</p> + +<p>The natural decay of web links as the sites they're connected +to change or die. Compare <b><a href="#bitrot">bit +rot</a></b>.</p> + +<hr> +Node:<a name="link-dead">link-dead</a>, Next:<a rel="next" href="#lint">lint</a>, Previous:<a rel="previous" href="#linkrot">link rot</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>link-dead</b> adj.</p> + +<p>[MUD] The state a player is in when they kill their connection +to a <b><a href="#MUD">MUD</a></b> without leaving it properly. +The player is then commonly left as a statue in the game, and is +only removed after a certain period of time (an hour on most +MUDs). Used on <b><a href="#IRC">IRC</a></b> as well, although it +is inappropriate in that context. Compare <b><a href="#netdead">netdead</a></b>.</p> + +<hr> +Node:<a name="lint">lint</a>, Next:<a rel="next" href="#Lintel">Lintel</a>, Previous:<a rel="previous" href="#link-dead">link-dead</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>lint</b></p> + +<p>[from Unix's <code>lint(1)</code>, named for the bits of fluff +it supposedly picks from programs] 1. vt. To examine a program +closely for style, language usage, and portability problems, esp. +if in C, esp. if via use of automated analysis tools, most esp. +if the Unix utility <code>lint(1)</code> is used. This term used +to be restricted to use of <code>lint(1)</code> itself, but +(judging by references on Usenet) it has become a shorthand for +<b><a href="#deskcheck">desk check</a></b> at some non-Unix +shops, even in languages other than C. Also as v. <b><a href="#delint">delint</a></b>. 2. n. Excess verbiage in a document, as +in "This draft has too much lint".</p> + +<hr> +Node:<a name="Lintel">Lintel</a>, Next:<a rel="next" href="#Linus">Linus</a>, Previous:<a rel="previous" href="#lint">lint</a>, Up:<a rel="up" href="#chap12">= L =</a> +<br> + + +<p><b>Lintel</b> n.</p> + +<p>The emerging <b><a href="#Linux">Linux</a></b>/Intel alliance. +This term began to be used in early 1999 after it became clear +that the <b><a href="#Wintel">Wintel</a></b> alliance was under +increasing strain and Intel started taking stakes in Linux +companies.</p> + +<hr> +Node:<a name="Linus">Linus</a>, Next:<a rel="next" href="#Linux">Linux</a>, Previous:<a rel="previous" href="#Lintel">Lintel</a>, Up:<a rel="up" href="#chap12">= L +=</a> <br> + + +<p><b>Linus</b> /leen'us'/ or /lin'us'/, not /li:'nus/</p> + +<p>Linus Torvalds, the author of <b><a href="#Linux">Linux</a></b>. Nobody in the hacker culture has been as +readily recognized by first name alone since Ken (Thompson).</p> + +<hr> +Node:<a name="Linux">Linux</a>, Next:<a rel="next" href="#lionfood">lion food</a>, Previous:<a rel="previous" href="#Linus">Linus</a>, Up:<a rel="up" href="#chap12">= L +=</a> <br> + + +<p><b>Linux</b> /lee'nuhks/ or /li'nuks/, <i>not</i> +/li:'nuhks/ n.</p> + +<p>The free Unix workalike created by Linus Torvalds and friends +starting about 1991. The pronunciation /lee'nuhks/ is preferred +because the name `Linus' has an /ee/ sound in Swedish (Linus's +family is part of Finland's 6% ethnic-Swedish minority). This may +be the most remarkable hacker project in history -- an entire +clone of Unix for 386, 486 and Pentium micros, distributed for +free with sources over the net (ports to Alpha and Sparc and many +other machines are also in use).</p> + +<p>Linux is what <b><a href="#GNU">GNU</a></b> aimed to be, and +it relies on the GNU toolset. But the Free Software Foundation +didn't produce the kernel to go with that toolset until 1999, +which was too late. Other, similar efforts like FreeBSD and +NetBSD have been technically successful but never caught fire the +way Linux has; as this is written in 2000, Linux is seriously +challenging Microsoft's OS dominance. It has already captured 31% +of the Internet-server market and 25% of general business +servers.</p> + +<p>An earlier version of this entry opined "The secret of Linux's +success seems to be that Linus worked much harder early on to +keep the development process open and recruit other hackers, +creating a snowball effect." Truer than we knew. See <b><a href="#bazaar">bazaar</a></b>.</p> + +<p>(Some people object that the name `Linux' should be used to +refer only to the kernel, not the entire operating system. This +claim is a proxy for an underlying territorial dispute; people +who insist on the term `GNU/Linux' want the the <b><a href="#FSF">FSF</a></b> to get most of the credit for Linux because +RMS and friends wrote many of its user-level tools. Neither this +theory nor the term `GNU/Linux' has gained more than minority +acceptance).</p> + +<hr> +Node:<a name="lionfood">lion food</a>, Next:<a rel="next" +href="#LionsBook">Lions Book</a>, Previous:<a rel="previous" +href="#Linux">Linux</a>, Up:<a rel="up" href="#chap12">= L +=</a> <br> + + +<p><b>lion food</b> n.</p> + +<p>[IBM] Middle management or HQ staff (or, by extension, +administrative drones in general). From an old joke about two +lions who, escaping from the zoo, split up to increase their +chances but agree to meet after 2 months. When they finally meet, +one is skinny and the other overweight. The thin one says: "How +did you manage? I ate a human just once and they turned out a +small army to chase me -- guns, nets, it was terrible. Since then +I've been reduced to eating mice, insects, even grass." The fat +one replies: "Well, <i>I</i> hid near an IBM office and ate a +manager a day. And nobody even noticed!"</p> + +<hr> +Node:<a name="LionsBook">Lions Book</a>, Next:<a rel="next" +href="#LISP">LISP</a>, Previous:<a rel="previous" href="#lionfood">lion food</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>Lions Book</b> n.</p> + +<p>"Source Code and Commentary on Unix level 6", by John Lions. +The two parts of this book contained (1) the entire source +listing of the Unix Version 6 kernel, and (2) a commentary on the +source discussing the algorithms. These were circulated +internally at the University of New South Wales beginning +1976-77, and were, for years after, the <i>only</i> detailed +kernel documentation available to anyone outside Bell Labs. +Because Western Electric wished to maintain trade secret status +on the kernel, the Lions Book was only supposed to be distributed +to affiliates of source licensees. In spite of this, it soon +spread by <b><a href="#samizdat">samizdat</a></b> to a good many +of the early Unix hackers.</p> + +<p>[1996 update: The Lions book lives again! It was put back in +print as ISBN 1-57398-013-7 from Peer-To-Peer Communications, +with forewords by Dennis Ritchie and Ken Thompson. In a neat bit +of reflexivity, the page before the contents quotes this +entry.]</p> + +<hr> +Node:<a name="LISP">LISP</a>, Next:<a rel="next" href="#list-bomb">list-bomb</a>, Previous:<a rel="previous" href="#LionsBook">Lions Book</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>LISP</b> n.</p> + +<p>[from `LISt Processing language', but mythically from `Lots of +Irritating Superfluous Parentheses'] AI's mother tongue, a +language based on the ideas of (a) variable-length lists and +trees as fundamental data types, and (b) the interpretation of +code as data and vice-versa. Invented by John McCarthy at MIT in +the late 1950s, it is actually older than any other <b><a href="#HLL">HLL</a></b> still in use except FORTRAN. Accordingly, it +has undergone considerable adaptive radiation over the years; +modern variants are quite different in detail from the original +LISP 1.5. The dominant HLL among hackers until the early 1980s, +LISP now shares the throne with <b><a href="#C">C</a></b>. Its +partisans claim it is the only language that is truly beautiful. +See <b><a href="#languagesofchoice">languages of +choice</a></b>.</p> + +<p>All LISP functions and programs are expressions that return +values; this, together with the high memory utilization of LISPs, +gave rise to Alan Perlis's famous quip (itself a take on an Oscar +Wilde quote) that "LISP programmers know the value of everything +and the cost of nothing".</p> + +<p>One significant application for LISP has been as a proof by +example that most newer languages, such as <b><a href="#COBOL">COBOL</a></b> and <b><a href="#Ada">Ada</a></b>, are +full of unnecessary <b><a href="#crock">crock</a></b>s. When the +<b><a href="#RightThing">Right Thing</a></b> has already been +done once, there is no justification for <b><a href="#bogosity">bogosity</a></b> in newer languages.</p> + +<hr> +Node:<a name="list-bomb">list-bomb</a>, Next:<a rel="next" href="#lithiumlick">lithium lick</a>, Previous:<a rel="previous" +href="#LISP">LISP</a>, Up:<a rel="up" href="#chap12">= L +=</a> <br> + + +<p><b>list-bomb</b> v.</p> + +<p>To <b><a href="#mailbomb">mailbomb</a></b> someone by forging +messages causing the victim to become a subscriber to many +mailing lists. This is a self-defeating tactic; it merely forces +mailing list servers to require confirmation by return message +for every subscription.</p> + +<hr> +Node:<a name="lithiumlick">lithium lick</a>, Next:<a rel="next" href="#little-endian">little-endian</a>, Previous:<a rel="previous" href="#list-bomb">list-bomb</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>lithium lick</b> n.</p> + +<p>[NeXT] Steve Jobs. Employees who have gotten too much +attention from their esteemed founder are said to have `lithium +lick' when they begin to show signs of Jobsian fervor and repeat +the most recent catch phrases in normal conversation -- for +example, "It just works, right out of the box!"</p> + +<hr> +Node:<a name="little-endian">little-endian</a>, Next:<a rel="next" href="#live">live</a>, Previous:<a rel="previous" href="#lithiumlick">lithium lick</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>little-endian</b> adj.</p> + +<p>Describes a computer architecture in which, within a given 16- +or 32-bit word, bytes at lower addresses have lower significance +(the word is stored `little-end-first'). The PDP-11 and VAX +families of computers and Intel microprocessors and a lot of +communications and networking hardware are little-endian. See +<b><a href="#big-endian">big-endian</a></b>, <b><a href="#middle-endian">middle-endian</a></b>, <b><a href="#NUXIproblem">NUXI problem</a></b>. The term is sometimes +used to describe the ordering of units other than bytes; most +often, bits within a byte.</p> + +<hr> +Node:<a name="live">live</a>, Next:<a rel="next" href="#livedata">live data</a>, Previous:<a rel="previous" href="#little-endian">little-endian</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>live</b> /li:v/ adj.,adv.</p> + +<p>[common] Opposite of `test'. Refers to actual real-world data +or a program working with it. For example, the response to "I +think the record deleter is finished" might be "Is it live yet?" +or "Have you tried it out on live data?" This usage usually +carries the connotation that live data is more fragile and must +not be corrupted, or bad things will happen. So a more +appropriate response might be: "Well, make sure it works +perfectly before we throw live data at it." The implication here +is that record deletion is something pretty significant, and a +haywire record-deleter running amok live would probably cause +great harm.</p> + +<hr> +Node:<a name="livedata">live data</a>, Next:<a rel="next" +href="#LiveFreeOrDie">Live Free Or Die!</a>, +Previous:<a rel="previous" href="#live">live</a>, Up:<a rel="up" +href="#chap12">= L =</a> <br> + + +<p><b>live data</b> n.</p> + +<p>1. Data that is written to be interpreted and takes over +program flow when triggered by some un-obvious operation, such as +viewing it. One use of such hacks is to break security. For +example, some smart terminals have commands that allow one to +download strings to program keys; this can be used to write live +data that, when listed to the terminal, infects it with a +security-breaking <b><a href="#virus">virus</a></b> that is +triggered the next time a hapless user strikes that key. For +another, there are some well-known bugs in <b><a href="#vi">vi</a></b> that allow certain texts to send arbitrary +commands back to the machine when they are simply viewed. 2. In C +code, data that includes pointers to function <b><a href="#hook">hook</a></b>s (executable code). 3. An object, such as a +<b><a href="#trampoline">trampoline</a></b>, that is constructed +on the fly by a program and intended to be executed as code.</p> + +<hr> +Node:<a name="LiveFreeOrDie">Live Free Or Die!</a>, +Next:<a rel="next" href="#livelock">livelock</a>, Previous:<a +rel="previous" href="#livedata">live data</a>, Up:<a rel="up" +href="#chap12">= L =</a> <br> + + +<p><b>Live Free Or Die!</b> imp.</p> + +<p>1. The state motto of New Hampshire, which appears on that +state's automobile license plates. 2. A slogan associated with +Unix in the romantic days when Unix aficionados saw themselves as +a tiny, beleaguered underground tilting against the windmills of +industry. The "free" referred specifically to freedom from the +<b><a href="#fascist">fascist</a></b> design philosophies and +crufty misfeatures common on competing operating systems. Armando +Stettner, one of the early Unix developers, used to give out fake +license plates bearing this motto under a large Unix, all in New +Hampshire colors of green and white. These are now valued +collector's items. In 1994 <b><a href="#DEC">DEC</a></b> put an +inferior imitation of these in circulation with a red corporate +logo added. Compaq (half of which was once DEC) has continued the +practice.</p> + +<hr> +Node:<a name="livelock">livelock</a>, Next:<a rel="next" href="#liveware">liveware</a>, Previous:<a rel="previous" href="#LiveFreeOrDie">Live Free Or Die!</a>, Up:<a rel="up" +href="#chap12">= L =</a> <br> + + +<p><b>livelock</b> /li:v'lok/ n.</p> + +<p>A situation in which some critical stage of a task is unable +to finish because its clients perpetually create more work for it +to do after they have been serviced but before it can clear its +queue. Differs from <b><a href="#deadlock">deadlock</a></b> in +that the process is not blocked or waiting for anything, but has +a virtually infinite amount of work to do and can never catch +up.</p> + +<hr> +Node:<a name="liveware">liveware</a>, Next:<a rel="next" href="#lobotomy">lobotomy</a>, Previous:<a rel="previous" href="#livelock">livelock</a>, Up:<a rel="up" href="#chap12">= +L =</a> <br> + + +<p><b>liveware</b> /li:v'weir/ n.</p> + +<p>1. Synonym for <b><a href="#wetware">wetware</a></b>. Less +common. 2. [Cambridge] Vermin. "Waiter, there's some liveware in +my salad<small>...</small>"</p> + +<hr> +Node:<a name="lobotomy">lobotomy</a>, Next:<a rel="next" href="#localsthe">locals the</a>, Previous:<a rel="previous" href="#liveware">liveware</a>, Up:<a rel="up" href="#chap12">= +L =</a> <br> + + +<p><b>lobotomy</b> n.</p> + +<p>1. What a hacker subjected to formal management training is +said to have undergone. At IBM and elsewhere this term is used by +both hackers and low-level management; the latter doubtless +intend it as a joke. 2. The act of removing the processor from a +microcomputer in order to replace or upgrade it. Some very cheap +<b><a href="#clone">clone</a></b> systems are sold in +`lobotomized' form -- everything but the brain.</p> + +<hr> +Node:<a name="localsthe">locals the</a>, Next:<a rel="next" +href="#lockedandloaded">locked and loaded</a>, Previous:<a +rel="previous" href="#lobotomy">lobotomy</a>, Up:<a rel="up" +href="#chap12">= L =</a> <br> + + +<p><b>locals, the</b> pl.n.</p> + +<p>The users on one's local network (as opposed, say, to people +one reaches via public Internet or UUCP connects). The marked +thing about this usage is how little it has to do with real-space +distance. "I have to do some tweaking on this mail utility before +releasing it to the locals."</p> + +<hr> +Node:<a name="lockedandloaded">locked and loaded</a>, +Next:<a rel="next" href="#lockedup">locked up</a>, Previous:<a +rel="previous" href="#localsthe">locals the</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>locked and loaded</b> adj.,obs.</p> + +<p>[from military slang for an M-16 rifle with magazine inserted +and prepared for firing] Said of a removable disk volume properly +prepared for use -- that is, locked into the drive and with the +heads loaded. Ironically, because their heads are `loaded' +whenever the power is up, this description is never used of <b><a +href="#Winchester">Winchester</a></b> drives (which are named +after a rifle).</p> + +<hr> +Node:<a name="lockedup">locked up</a>, Next:<a rel="next" +href="#logicbomb">logic bomb</a>, Previous:<a rel="previous" +href="#lockedandloaded">locked and loaded</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>locked up</b> adj.</p> + +<p>Syn. for <b><a href="#hung">hung</a></b>, <b><a href="#wedged">wedged</a></b>.</p> + +<hr> +Node:<a name="logicbomb">logic bomb</a>, Next:<a rel="next" +href="#logical">logical</a>, Previous:<a rel="previous" href="#lockedup">locked up</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>logic bomb</b> n.</p> + +<p>Code surreptitiously inserted into an application or OS that +causes it to perform some destructive or security-compromising +activity whenever specified conditions are met. Compare <b><a +href="#backdoor">back door</a></b>.</p> + +<hr> +Node:<a name="logical">logical</a>, Next:<a rel="next" href="#loopthrough">loop through</a>, Previous:<a rel="previous" +href="#logicbomb">logic bomb</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>logical</b> adj.</p> + +<p>[from the technical term `logical device', wherein a physical +device is referred to by an arbitrary `logical' name] Having the +role of. If a person (say, Les Earnest at SAIL) who had long held +a certain post left and were replaced, the replacement would for +a while be known as the `logical' Les Earnest. (This does not +imply any judgment on the replacement.) Compare <b><a href="#virtual">virtual</a></b>.</p> + +<p>At Stanford, `logical' compass directions denote a coordinate +system in which `logical north' is toward San Francisco, `logical +west' is toward the ocean, etc., even though logical north varies +between physical (true) north near San Francisco and physical +west near San Jose. (The best rule of thumb here is that, by +definition, El Camino Real always runs logical north-and-south.) +In giving directions, one might say: "To get to Rincon Tarasco +restaurant, get onto <b><a href="#ElCaminoBignum">El Camino +Bignum</a></b> going logical north." Using the word `logical' +helps to prevent the recipient from worrying about that the fact +that the sun is setting almost directly in front of him. The +concept is reinforced by North American highways which are +almost, but not quite, consistently labeled with logical rather +than physical directions. A similar situation exists at MIT: +Route 128 (famous for the electronics industry that has grown up +along it) is a 3-quarters circle surrounding Boston at a radius +of 10 miles, terminating near the coastline at each end. It would +be most precise to describe the two directions along this highway +as `clockwise' and `counterclockwise', but the road signs all say +"north" and "south", respectively. A hacker might describe these +directions as `logical north' and `logical south', to indicate +that they are conventional directions not corresponding to the +usual denotation for those words. (If you went logical south +along the entire length of route 128, you would start out going +northwest, curve around to the south, and finish headed due east, +passing along one infamous stretch of pavement that is +simultaneously route 128 south and Interstate 93 north, and is +signed as such!)</p> + +<hr> +Node:<a name="loopthrough">loop through</a>, Next:<a rel="next" href="#loosebytes">loose bytes</a>, Previous:<a rel="previous" href="#logical">logical</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>loop through</b> vt.</p> + +<p>To process each element of a list of things. "Hold on, I've +got to loop through my paper mail." Derives from the +computer-language notion of an iterative loop; compare `cdr down' +(under <b><a href="#cdr">cdr</a></b>), which is less common among +C and Unix programmers. ITS hackers used to say `IRP over' after +an obscure pseudo-op in the MIDAS PDP-10 assembler (the same IRP +op can nowadays be found in Microsoft's assembler).</p> + +<hr> +Node:<a name="loosebytes">loose bytes</a>, Next:<a rel="next" +href="#lordhighfixer">lord high fixer</a>, Previous:<a rel="previous" href="#loopthrough">loop through</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>loose bytes</b> n.</p> + +<p>Commonwealth hackish term for the padding bytes or <b><a href="#shim">shim</a></b>s many compilers insert between members of a +record or structure to cope with alignment requirements imposed +by the machine architecture.</p> + +<hr> +Node:<a name="lordhighfixer">lord high fixer</a>, Next:<a +rel="next" href="#lose">lose</a>, Previous:<a rel="previous" +href="#loosebytes">loose bytes</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>lord high fixer</b> n.</p> + +<p>[primarily British, from Gilbert & Sullivan's `lord high +executioner'] The person in an organization who knows the most +about some aspect of a system. See <b><a href="#wizard">wizard</a></b>.</p> + +<hr> +Node:<a name="lose">lose</a>, Next:<a rel="next" href="#loselose">lose lose</a>, Previous:<a rel="previous" href="#lordhighfixer">lord high fixer</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>lose</b> vi.</p> + +<p>1. [very common] To fail. A program loses when it encounters +an exceptional condition or fails to work in the expected manner. +2. To be exceptionally unesthetic or crocky. 3. Of people, to be +obnoxious or unusually stupid (as opposed to ignorant). See also +<b><a href="#deservestolose">deserves to lose</a></b>. 4. +n. Refers to something that is <b><a href="#losing">losing</a></b>, especially in the phrases "That's a +lose!" and "What a lose!"</p> + +<hr> +Node:<a name="loselose">lose lose</a>, Next:<a rel="next" +href="#loser">loser</a>, Previous:<a rel="previous" href="#lose">lose</a>, Up:<a rel="up" href="#chap12">= L =</a> +<br> + + +<p><b>lose lose</b> interj.</p> + +<p>A reply to or comment on an undesirable situation. "I +accidentally deleted all my files!" "Lose, lose."</p> + +<hr> +Node:<a name="loser">loser</a>, Next:<a rel="next" href="#losing">losing</a>, Previous:<a rel="previous" href="#loselose">lose lose</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>loser</b> n.</p> + +<p>An unexpectedly bad situation, program, programmer, or person. +Someone who habitually loses. (Even winners can lose +occasionally.) Someone who knows not and knows not that he knows +not. Emphatic forms are `real loser', `total loser', and +`complete loser' (but not **`moby loser', which would be a +contradiction in terms). See <b><a href="#luser">luser</a></b>.</p> + +<hr> +Node:<a name="losing">losing</a>, Next:<a rel="next" href="#loss">loss</a>, Previous:<a rel="previous" href="#loser">loser</a>, Up:<a rel="up" href="#chap12">= L +=</a> <br> + + +<p><b>losing</b> adj.</p> + +<p>Said of anything that is or causes a <b><a href="#lose">lose</a></b> or <b><a href="#lossage">lossage</a></b>. +"The compiler is losing badly when I try to use templates."</p> + +<hr> +Node:<a name="loss">loss</a>, Next:<a rel="next" href="#lossage">lossage</a>, Previous:<a rel="previous" href="#losing">losing</a>, Up:<a rel="up" href="#chap12">= L +=</a> <br> + + +<p><b>loss</b> n.</p> + +<p>Something (not a person) that loses; a situation in which +something is losing. Emphatic forms include `moby loss', and +`total loss', `complete loss'. Common interjections are "What a +loss!" and "What a moby loss!" Note that `moby loss' is OK even +though **`moby loser' is not used; applied to an abstract noun, +moby is simply a magnifier, whereas when applied to a person it +implies substance and has positive connotations. Compare <b><a +href="#lossage">lossage</a></b>.</p> + +<hr> +Node:<a name="lossage">lossage</a>, Next:<a rel="next" href="#lostinthenoise">lost in the noise</a>, Previous:<a +rel="previous" href="#loss">loss</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>lossage</b> /los'*j/ n.</p> + +<p>[very common] The result of a bug or malfunction. This is a +mass or collective noun. "What a loss!" and "What lossage!" are +nearly synonymous. The former is slightly more particular to the +speaker's present circumstances; the latter implies a continuing +<b><a href="#lose">lose</a></b> of which the speaker is currently +a victim. Thus (for example) a temporary hardware failure is a +loss, but bugs in an important tool (like a compiler) are serious +lossage.</p> + +<hr> +Node:<a name="lostinthenoise">lost in the noise</a>, +Next:<a rel="next" href="#lostintheunderflow">lost in +the underflow</a>, Previous:<a rel="previous" href="#lossage">lossage</a>, Up:<a rel="up" href="#chap12">= L +=</a> <br> + + +<p><b>lost in the noise</b> adj.</p> + +<p>Syn. <b><a href="#lostintheunderflow">lost in the +underflow</a></b>. This term is from signal processing, where +signals of very small amplitude cannot be separated from +low-intensity noise in the system. Though popular among hackers, +it is not confined to hackerdom; physicists, engineers, +astronomers, and statisticians all use it.</p> + +<hr> +Node:<a name="lostintheunderflow">lost in the +underflow</a>, Next:<a rel="next" href="#lotsofMIPSbutnoIO">lots of MIPS but no +I/O</a>, Previous:<a rel="previous" href="#lostinthenoise">lost in the noise</a>, Up:<a rel="up" +href="#chap12">= L =</a> <br> + + +<p><b>lost in the underflow</b> adj.</p> + +<p>Too small to be worth considering; more specifically, small +beyond the limits of accuracy or measurement. This is a reference +to `floating underflow', a condition that can occur when a +floating-point arithmetic processor tries to handle quantities +smaller than its limit of magnitude. It is also a pun on +`undertow' (a kind of fast, cold current that sometimes runs just +offshore and can be dangerous to swimmers). "Well, sure, photon +pressure from the stadium lights alters the path of a thrown +baseball, but that effect gets lost in the underflow." Compare +<b><a href="#epsilon">epsilon</a></b>, <b><a href="#epsilonsquared">epsilon squared</a></b>; see also <b><a +href="#overflowbit">overflow bit</a></b>.</p> + +<hr> +Node:<a name="lotsofMIPSbutnoIO">lots of MIPS +but no I/O</a>, Next:<a rel="next" href="#low-bandwidth">low-bandwidth</a>, Previous:<a rel="previous" +href="#lostintheunderflow">lost in the underflow</a>, +Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>lots of MIPS but no I/O</b> adj.</p> + +<p>Used to describe a person who is technically brilliant but +can't seem to communicate with human beings effectively. +Technically it describes a machine that has lots of processing +power but is bottlenecked on input-output (in 1991, the IBM Rios, +a.k.a. RS/6000, was a notorious example).</p> + +<hr> +Node:<a name="low-bandwidth">low-bandwidth</a>, Next:<a rel="next" href="#LPT">LPT</a>, Previous:<a rel="previous" href="#lotsofMIPSbutnoIO">lots of MIPS but no +I/O</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>low-bandwidth</b> adj.</p> + +<p>[from communication theory] Used to indicate a talk that, +although not <b><a href="#content-free">content-free</a></b>, was +not terribly informative. "That was a low-bandwidth talk, but +what can you expect for an audience of <b><a href="#suit">suit</a></b>s!" Compare <b><a href="#zero-content">zero-content</a></b>, <b><a href="#bandwidth">bandwidth</a></b>, <b><a href="#math-out">math-out</a></b>.</p> + +<hr> +Node:<a name="LPT">LPT</a>, Next:<a rel="next" href="#LubarskysLawofCyberneticEntomology">Lubarsky's Law +of Cybernetic Entomology</a>, Previous:<a rel="previous" href="#low-bandwidth">low-bandwidth</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>LPT</b> /L-P-T/ or /lip'it/ or /lip-it'/ n.</p> + +<p>1. Line printer (originally Line Printing Terminal). Rare +under Unix, more common among hackers who grew up with ITS, +MS-DOS, CP/M and other operating systems that were strongly +influenced by early <b><a href="#DEC">DEC</a></b> conventions. 2. +Local PorT. Used among MS-DOS programmers (and so expanded in the +MS-DOS 5 manual). It seems likely this is a <b><a href="#backronym">backronym</a></b>.</p> + +<hr> +Node:<a name="LubarskysLawofCyberneticEntomology">Lubarsky's Law +of Cybernetic Entomology</a>, Next:<a rel="next" href="#LumberCartel">Lumber Cartel</a>, Previous:<a rel="previous" +href="#LPT">LPT</a>, Up:<a rel="up" href="#chap12">= L +=</a> <br> + + +<p><b>Lubarsky's Law of Cybernetic Entomology</b> prov.</p> + +<p>"There is <i>always</i> one more bug."</p> + +<hr> +Node:<a name="LumberCartel">Lumber Cartel</a>, Next:<a rel="next" href="#lunaticfringe">lunatic fringe</a>, Previous:<a +rel="previous" href="#LubarskysLawofCyberneticEntomology">Lubarsky's Law +of Cybernetic Entomology</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>Lumber Cartel</b> n.</p> + +<p>A mythical conspiracy accused by <b><a href="#spam">spam</a></b>-spewers of funding anti-spam activism in +order to force the direct-mail promotions industry back onto +paper. Hackers, predictably, responded by forming a "Lumber +Cartel" spoofing this paranoid theory; the web page is http://come.to/the.lumber.cartel. +Members often include the tag TINLC ("There Is No Lumber Cartel") +in their postings; see <b><a href="#TINC">TINC</a></b>, <b><a +href="#backbonecabal">backbone cabal</a></b> and <b><a href="#NANA">NANA</a></b> for explanation.</p> + +<hr> +Node:<a name="lunaticfringe">lunatic fringe</a>, Next:<a rel="next" href="#lurker">lurker</a>, Previous:<a rel="previous" +href="#LumberCartel">Lumber Cartel</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>lunatic fringe</b> n.</p> + +<p>[IBM] Customers who can be relied upon to accept release 1 +versions of software. Compare <b><a href="#heatseeker">heatseeker</a></b>.</p> + +<hr> +Node:<a name="lurker">lurker</a>, Next:<a rel="next" href="#luser">luser</a>, Previous:<a rel="previous" href="#lunaticfringe">lunatic fringe</a>, Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>lurker</b> n.</p> + +<p>One of the `silent majority' in a electronic forum; one who +posts occasionally or not at all but is known to read the group's +postings regularly. This term is not pejorative and indeed is +casually used reflexively: "Oh, I'm just lurking." Often used in +`the lurkers', the hypothetical audience for the group's <b><a +href="#flamage">flamage</a></b>-emitting regulars. When a lurker +speaks up for the first time, this is called `delurking'.</p> + +<p>The creator of the popular science-fiction TV series "Babylon +5" has ties to SF fandom and the hacker culture. In that series, +the use of the term `lurker' for a homeless or displaced person +is a conscious reference to the jargon term.</p> + +<hr> +Node:<a name="luser">luser</a>, Next:<a rel="next" href="#M">M</a>, Previous:<a rel="previous" href="#lurker">lurker</a>, +Up:<a rel="up" href="#chap12">= L =</a> <br> + + +<p><b>luser</b> /loo'zr/ n.</p> + +<p>[common] A <b><a href="#user">user</a></b>; esp. one who is +also a <b><a href="#loser">loser</a></b>. (<b><a href="#luser">luser</a></b> and <b><a href="#loser">loser</a></b> are +pronounced identically.) This word was coined around 1975 at MIT. +Under ITS, when you first walked up to a terminal at MIT and +typed Control-Z to get the computer's attention, it printed out +some status information, including how many people were already +using the computer; it might print "14 users", for example. +Someone thought it would be a great joke to patch the system to +print "14 losers" instead. There ensued a great controversy, as +some of the users didn't particularly want to be called losers to +their faces every time they used the computer. For a while +several hackers struggled covertly, each changing the message +behind the back of the others; any time you logged into the +computer it was even money whether it would say "users" or +"losers". Finally, someone tried the compromise "lusers", and it +stuck. Later one of the ITS machines supported <code>luser</code> +as a request-for-help command. ITS died the death in mid-1990, +except as a museum piece; the usage lives on, however, and the +term `luser' is often seen in program comments and on Usenet. +Compare <b><a href="#mundane">mundane</a></b>, <b><a href="#muggle">muggle</a></b>.</p> + +<hr> +Node:<a name="chap13">= M =</a>, Next:<a rel="next" href="#chap14">= N =</a>, Previous:<a rel="previous" href="#chap12">= L =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= M =</h2> + +<ul> +<li><a href="#M">M</a>:</li> + +<li><a href="#Mdollar">M$</a>:</li> + +<li><a href="#macdink">macdink</a>:</li> + +<li><a href="#machinable">machinable</a>:</li> + +<li><a href="#machoflops">machoflops</a>:</li> + +<li><a href="#Macintoy">Macintoy</a>:</li> + +<li><a href="#Macintrash">Macintrash</a>:</li> + +<li><a href="#macro">macro</a>:</li> + +<li><a href="#macro-">macro-</a>:</li> + +<li><a href="#macrology">macrology</a>:</li> + +<li><a href="#macrotape">macrotape</a>:</li> + +<li><a href="#maggotbox">maggotbox</a>:</li> + +<li><a href="#magic">magic</a>:</li> + +<li><a href="#magiccookie">magic cookie</a>:</li> + +<li><a href="#magicnumber">magic number</a>:</li> + +<li><a href="#magicsmoke">magic smoke</a>:</li> + +<li><a href="#mailstorm">mail storm</a>:</li> + +<li><a href="#mailbomb">mailbomb</a>:</li> + +<li><a href="#mailinglist">mailing list</a>:</li> + +<li><a href="#mainloop">main loop</a>:</li> + +<li><a href="#mainframe">mainframe</a>:</li> + +<li><a href="#management">management</a>:</li> + +<li><a href="#mandelbug">mandelbug</a>:</li> + +<li><a href="#manged">manged</a>:</li> + +<li><a href="#mangle">mangle</a>:</li> + +<li><a href="#mangledname">mangled name</a>:</li> + +<li><a href="#mangler">mangler</a>:</li> + +<li><a href="#manularity">manularity</a>:</li> + +<li><a href="#marbles">marbles</a>:</li> + +<li><a href="#marginal">marginal</a>:</li> + +<li><a href="#MarginalHacks">Marginal Hacks</a>:</li> + +<li><a href="#marginally">marginally</a>:</li> + +<li><a href="#marketroid">marketroid</a>:</li> + +<li><a href="#Mars">Mars</a>:</li> + +<li><a href="#martian">martian</a>:</li> + +<li><a href="#massage">massage</a>:</li> + +<li><a href="#math-out">math-out</a>:</li> + +<li><a href="#Matrix">Matrix</a>:</li> + +<li><a href="#maximumMaytagmode">maximum Maytag mode</a>:</li> + +<li><a href="#meatspace">meatspace</a>:</li> + +<li><a href="#meatware">meatware</a>:</li> + +<li><a href="#meeces">meeces</a>:</li> + +<li><a href="#meg">meg</a>:</li> + +<li><a href="#mega-">mega-</a>:</li> + +<li><a href="#megapenny">megapenny</a>:</li> + +<li><a href="#MEGO">MEGO</a>:</li> + +<li><a href="#meltdownnetwork">meltdown network</a>:</li> + +<li><a href="#meme">meme</a>:</li> + +<li><a href="#memeplague">meme plague</a>:</li> + +<li><a href="#memetics">memetics</a>:</li> + +<li><a href="#memoryfarts">memory farts</a>:</li> + +<li><a href="#memoryleak">memory leak</a>:</li> + +<li><a href="#memorysmash">memory smash</a>:</li> + +<li><a href="#menuitis">menuitis</a>:</li> + +<li><a href="#mess-dos">mess-dos</a>:</li> + +<li><a href="#meta">meta</a>:</li> + +<li><a href="#metabit">meta bit</a>:</li> + +<li><a href="#metasyntacticvariable">metasyntactic variable</a>:</li> + +<li><a href="#MFTL">MFTL</a>:</li> + +<li><a href="#mickey">mickey</a>:</li> + +<li><a href="#mickeymouseprogram">mickey mouse program</a>:</li> + +<li><a href="#micro-">micro-</a>:</li> + +<li><a href="#MicroDroid">MicroDroid</a>:</li> + +<li><a href="#microfloppies">microfloppies</a>:</li> + +<li><a href="#microfortnight">microfortnight</a>:</li> + +<li><a href="#microLenat">microLenat</a>:</li> + +<li><a href="#microReid">microReid</a>:</li> + +<li><a href="#microserf">microserf</a>:</li> + +<li><a href="#MicroslothWindows">Microsloth Windows</a>:</li> + +<li><a href="#Microsoft">Microsoft</a>:</li> + +<li><a href="#microse1">micros~1</a>:</li> + +<li><a href="#middle-endian">middle-endian</a>:</li> + +<li><a href="#middleoutimplementation">middle-out implementation</a>:</li> + +<li><a href="#milliLampson">milliLampson</a>:</li> + +<li><a href="#minifloppies">minifloppies</a>:</li> + +<li><a href="#MIPS">MIPS</a>:</li> + +<li><a href="#misbug">misbug</a>:</li> + +<li><a href="#misfeature">misfeature</a>:</li> + +<li><a href="#Missedem-five">Missed'em-five</a>:</li> + +<li><a href="#missileaddress">missile address</a>:</li> + +<li><a href="#miswart">miswart</a>:</li> + +<li><a href="#MMF">MMF</a>:</li> + +<li><a href="#mobo">mobo</a>:</li> + +<li><a href="#moby">moby</a>:</li> + +<li><a href="#mockingbird">mockingbird</a>:</li> + +<li><a href="#mod">mod</a>:</li> + +<li><a href="#mode">mode</a>:</li> + +<li><a href="#modebit">mode bit</a>:</li> + +<li><a href="#modulo">modulo</a>:</li> + +<li><a href="#molly-guard">molly-guard</a>:</li> + +<li><a href="#MongolianHordestechnique">Mongolian Hordes technique</a>:</li> + +<li><a href="#monkeyup">monkey up</a>:</li> + +<li><a href="#monkeyscratch">monkey scratch</a>:</li> + +<li><a href="#monstrosity">monstrosity</a>:</li> + +<li><a href="#monty">monty</a>:</li> + +<li><a href="#Moof">Moof</a>:</li> + +<li><a href="#MooresLaw">Moore's Law</a>:</li> + +<li><a href="#moosecall">moose call</a>:</li> + +<li><a href="#moria">moria</a>:</li> + +<li><a href="#MOTAS">MOTAS</a>:</li> + +<li><a href="#MOTOS">MOTOS</a>:</li> + +<li><a href="#MOTSS">MOTSS</a>:</li> + +<li><a href="#mouseahead">mouse ahead</a>:</li> + +<li><a href="#mousearound">mouse around</a>:</li> + +<li><a href="#mousebelt">mouse belt</a>:</li> + +<li><a href="#mousedroppings">mouse droppings</a>:</li> + +<li><a href="#mouseelbow">mouse elbow</a>:</li> + +<li><a href="#mouso">mouso</a>:</li> + +<li><a href="#MS-DOS">MS-DOS</a>:</li> + +<li><a href="#mu">mu</a>:</li> + +<li><a href="#MUD">MUD</a>:</li> + +<li><a href="#muddie">muddie</a>:</li> + +<li><a href="#mudhead">mudhead</a>:</li> + +<li><a href="#muggle">muggle</a>:</li> + +<li><a href="#multician">multician</a>:</li> + +<li><a href="#Multics">Multics</a>:</li> + +<li><a href="#multitask">multitask</a>:</li> + +<li><a href="#mumblage">mumblage</a>:</li> + +<li><a href="#mumble">mumble</a>:</li> + +<li><a href="#munch">munch</a>:</li> + +<li><a href="#munching">munching</a>:</li> + +<li><a href="#munchingsquares">munching squares</a>:</li> + +<li><a href="#munchkin">munchkin</a>:</li> + +<li><a href="#mundane">mundane</a>:</li> + +<li><a href="#mung">mung</a>:</li> + +<li><a href="#munge">munge</a>:</li> + +<li><a href="#MurphysLaw">Murphy's Law</a>:</li> + +<li><a href="#music">music</a>:</li> + +<li><a href="#mutter">mutter</a>:</li> +</ul> + +<hr> +Node:<a name="M">M</a>, Next:<a rel="next" href="#Mdollar">M$</a>, +Previous:<a rel="previous" href="#luser">luser</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>M</b> pref. (on units) suff. (on numbers)</p> + +<p>[SI] See <b><a href="#quantifiers">quantifiers</a></b>.</p> + +<hr> +Node:<a name="Mdollar">M$</a>, Next:<a rel="next" href="#macdink">macdink</a>, Previous:<a rel="previous" href="#M">M</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>M$</b></p> + +<p>Common net abbreviation for Microsoft, everybody's least +favorite monopoly.</p> + +<hr> +Node:<a name="macdink">macdink</a>, Next:<a rel="next" href="#machinable">machinable</a>, Previous:<a rel="previous" href="#Mdollar">M$</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>macdink</b> /mak'dink/ vt.</p> + +<p>[from the Apple Macintosh, which is said to encourage such +behavior] To make many incremental and unnecessary cosmetic +changes to a program or file. Often the subject of the macdinking +would be better off without them. "When I left at 11 +<small>P.M.</small> last night, he was still macdinking the +slides for his presentation." See also <b><a href="#fritterware">fritterware</a></b>, <b><a href="#windowshopping">window shopping</a></b>.</p> + +<hr> +Node:<a name="machinable">machinable</a>, Next:<a rel="next" +href="#machoflops">machoflops</a>, Previous:<a rel="previous" +href="#macdink">macdink</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>machinable</b> adj.</p> + +<p>Machine-readable. Having the <b><a href="#softcopy">softcopy</a></b> nature.</p> + +<hr> +Node:<a name="machoflops">machoflops</a>, Next:<a rel="next" +href="#Macintoy">Macintoy</a>, Previous:<a rel="previous" href="#machinable">machinable</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>machoflops</b> /mach'oh-flops/ n.</p> + +<p>[pun on `megaflops', a coinage for `millions of FLoating-point +Operations Per Second'] Refers to artificially inflated +performance figures often quoted by computer manufacturers. Real +applications are lucky to get half the quoted speed. See <b><a +href="#Yourmileagemayvary">Your mileage may +vary</a></b>, <b><a href="#benchmark">benchmark</a></b>.</p> + +<hr> +Node:<a name="Macintoy">Macintoy</a>, Next:<a rel="next" href="#Macintrash">Macintrash</a>, Previous:<a rel="previous" href="#machoflops">machoflops</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>Macintoy</b> /mak'in-toy/ n.</p> + +<p>The Apple Macintosh, considered as a <b><a href="#toy">toy</a></b>. Less pejorative than <b><a href="#Macintrash">Macintrash</a></b>.</p> + +<hr> +Node:<a name="Macintrash">Macintrash</a>, Next:<a rel="next" +href="#macro">macro</a>, Previous:<a rel="previous" href="#Macintoy">Macintoy</a>, Up:<a rel="up" href="#chap13">= +M =</a> <br> + + +<p><b>Macintrash</b> /mak'in-trash`/ n.</p> + +<p>The Apple Macintosh, as described by a hacker who doesn't +appreciate being kept away from the <i>real computer</i> by the +interface. The term <b><a href="#maggotbox">maggotbox</a></b> has +been reported in regular use in the Research Triangle area of +North Carolina. Compare <b><a href="#Macintoy">Macintoy</a></b>. +See also <b><a href="#beigetoaster">beige toaster</a></b>, +<b><a href="#WIMPenvironment">WIMP environment</a></b>, <b><a +href="#pointanddroolinterface">point-and-drool +interface</a></b>, <b><a href="#droolproofpaper">drool-proof +paper</a></b>, <b><a href="#user-friendly">user-friendly</a></b>.</p> + +<hr> +Node:<a name="macro">macro</a>, Next:<a rel="next" href="#macro-">macro-</a>, Previous:<a rel="previous" href="#Macintrash">Macintrash</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>macro</b> /mak'roh/ n.</p> + +<p>[techspeak] A name (possibly followed by a formal <b><a href="#arg">arg</a></b> list) that is equated to a text or symbolic +expression to which it is to be expanded (possibly with the +substitution of actual arguments) by a macro expander. This +definition can be found in any technical dictionary; what those +won't tell you is how the hackish connotations of the term have +changed over time.</p> + +<p>The term `macro' originated in early assemblers, which +encouraged the use of macros as a structuring and +information-hiding device. During the early 1970s, macro +assemblers became ubiquitous, and sometimes quite as powerful and +expensive as <b><a href="#HLL">HLL</a></b>s, only to fall from +favor as improving compiler technology marginalized assembler +programming (see <b><a href="#languagesofchoice">languages +of choice</a></b>). Nowadays the term is most often used in +connection with the C preprocessor, LISP, or one of several +special-purpose languages built around a macro-expansion facility +(such as TeX or Unix's [nt]roff suite).</p> + +<p>Indeed, the meaning has drifted enough that the collective +`macros' is now sometimes used for code in any special-purpose +application control language (whether or not the language is +actually translated by text expansion), and for macro-like +entities such as the `keyboard macros' supported in some text +editors (and PC TSR or Macintosh INIT/CDEV keyboard +enhancers).</p> + +<hr> +Node:<a name="macro-">macro-</a>, Next:<a rel="next" href="#macrology">macrology</a>, Previous:<a rel="previous" href="#macro">macro</a>, Up:<a rel="up" href="#chap13">= M +=</a> <br> + + +<p><b>macro-</b> pref.</p> + +<p>Large. Opposite of <b><a href="#micro-">micro-</a></b>. In the +mainstream and among other technical cultures (for example, +medical people) this competes with the prefix <b><a href="#mega-">mega-</a></b>, but hackers tend to restrict the latter +to quantification.</p> + +<hr> +Node:<a name="macrology">macrology</a>, Next:<a rel="next" href="#macrotape">macrotape</a>, Previous:<a rel="previous" href="#macro-">macro-</a>, Up:<a rel="up" href="#chap13">= M +=</a> <br> + + +<p><b>macrology</b> /mak-rol'*-jee/ n.</p> + +<p>1. Set of usually complex or crufty macros, e.g., as part of a +large system written in <b><a href="#LISP">LISP</a></b>, <b><a +href="#TECO">TECO</a></b>, or (less commonly) assembler. 2. The +art and science involved in comprehending a macrology in sense 1. +Sometimes studying the macrology of a system is not unlike +archeology, ecology, or <b><a href="#theology">theology</a></b>, +hence the sound-alike construction. See also <b><a href="#boxology">boxology</a></b>.</p> + +<hr> +Node:<a name="macrotape">macrotape</a>, Next:<a rel="next" href="#maggotbox">maggotbox</a>, Previous:<a rel="previous" href="#macrology">macrology</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>macrotape</b> /mak'roh-tayp/ n.</p> + +<p>An industry-standard reel of tape. Originally, as opposed to a +DEC microtape; nowadays, as opposed to modern QIC and DDS tapes. +Syn. <b><a href="#roundtape">round tape</a></b>.</p> + +<hr> +Node:<a name="maggotbox">maggotbox</a>, Next:<a rel="next" href="#magic">magic</a>, Previous:<a rel="previous" href="#macrotape">macrotape</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>maggotbox</b> /mag'*t-boks/ n.</p> + +<p>See <b><a href="#Macintrash">Macintrash</a></b>. This is even +more derogatory.</p> + +<hr> +Node:<a name="magic">magic</a>, Next:<a rel="next" href="#magiccookie">magic cookie</a>, Previous:<a rel="previous" +href="#maggotbox">maggotbox</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>magic</b></p> + +<p>1. adj. As yet unexplained, or too complicated to explain; +compare <b><a href="#automagically">automagically</a></b> and +(Arthur C.) Clarke's Third Law: "Any sufficiently advanced +technology is indistinguishable from magic." "TTY echoing is +controlled by a large number of magic bits." "This routine +magically computes the parity of an 8-bit byte in three +instructions." 2. adj. Characteristic of something that works +although no one really understands why (this is especially called +<b><a href="#blackmagic">black magic</a></b>). 3. n. +[Stanford] A feature not generally publicized that allows +something otherwise impossible, or a feature formerly in that +category but now unveiled. 4. n. The ultimate goal of all +engineering & development, elegance in the extreme; from the +first corollary to Clarke's Third Law: "Any technology +distinguishable from magic is insufficiently advanced".</p> + +<p>Parodies playing on these senses of the term abound; some have +made their way into serious documentation, as when a MAGIC +directive was described in the Control Card Reference for GCOS +c.1978. For more about hackish `magic', see <b><a href="#AppendixA">Appendix A</a></b>. Compare <b><a href="#blackmagic">black magic</a></b>, <b><a href="#wizardly">wizardly</a></b>, <b><a href="#deepmagic">deep +magic</a></b>, <b><a href="#heavywizardry">heavy +wizardry</a></b>.</p> + +<hr> +Node:<a name="magiccookie">magic cookie</a>, Next:<a rel="next" href="#magicnumber">magic number</a>, Previous:<a rel="previous" href="#magic">magic</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>magic cookie</b> n.</p> + +<p>[Unix; common] 1. Something passed between routines or +programs that enables the receiver to perform some operation; a +capability ticket or opaque identifier. Especially used of small +data objects that contain data encoded in a strange or +intrinsically machine-dependent way. E.g., on non-Unix OSes with +a non-byte-stream model of files, the result of +<code>ftell(3)</code> may be a magic cookie rather than a byte +offset; it can be passed to <code>fseek(3)</code>, but not +operated on in any meaningful way. The phrase `it hands you a +magic cookie' means it returns a result whose contents are not +defined but which can be passed back to the same or some other +program later. 2. An in-band code for changing graphic rendition +(e.g., inverse video or underlining) or performing other control +functions (see also <b><a href="#cookie">cookie</a></b>). Some +older terminals would leave a blank on the screen corresponding +to mode-change magic cookies; this was also called a <b><a href="#glitch">glitch</a></b> (or occasionally a `turd'; compare <b><a +href="#mousedroppings">mouse droppings</a></b>). See also +<b><a href="#cookie">cookie</a></b>.</p> + +<hr> +Node:<a name="magicnumber">magic number</a>, Next:<a rel="next" href="#magicsmoke">magic smoke</a>, Previous:<a rel="previous" href="#magiccookie">magic cookie</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>magic number</b> n.</p> + +<p>[Unix/C; common] 1. In source code, some non-obvious constant +whose value is significant to the operation of a program and that +is inserted inconspicuously in-line (<b><a href="#hardcoded">hardcoded</a></b>), rather than expanded in by a +symbol set by a commented <code>#define</code>. Magic numbers in +this sense are bad style. 2. A number that encodes critical +information used in an algorithm in some opaque way. The classic +examples of these are the numbers used in hash or CRC functions, +or the coefficients in a linear congruential generator for +pseudo-random numbers. This sense actually predates and was +ancestral to the more commonsense 1. 3. Special data located at +the beginning of a binary data file to indicate its type to a +utility. Under Unix, the system and various applications programs +(especially the linker) distinguish between types of executable +file by looking for a magic number. Once upon a time, these magic +numbers were PDP-11 branch instructions that skipped over header +data to the start of executable code; 0407, for example, was +octal for `branch 16 bytes relative'. Many other kinds of files +now have magic numbers somewhere; some magic numbers are, in +fact, strings, like the <code>!<arch></code> at the +beginning of a Unix archive file or the <code>%!</code> leading +PostScript files. Nowadays only a <b><a href="#wizard">wizard</a></b> knows the spells to create magic +numbers. How do you choose a fresh magic number of your own? +Simple -- you pick one at random. See? It's magic!</p> + +<p><i>The</i> magic number, on the other hand, is 7+/-2. See +"The magical number seven, plus or minus two: some limits on our +capacity for processing information" by George Miller, in the +"Psychological Review" 63:81-97 (1956). This classic paper +established the number of distinct items (such as numeric digits) +that humans can hold in short-term memory. Among other things, +this strongly influenced the interface design of the phone +system.</p> + +<hr> +Node:<a name="magicsmoke">magic smoke</a>, Next:<a rel="next" +href="#mailstorm">mail storm</a>, Previous:<a rel="previous" +href="#magicnumber">magic number</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>magic smoke</b> n.</p> + +<p>A substance trapped inside IC packages that enables them to +function (also called `blue smoke'; this is similar to the +archaic `phlogiston' hypothesis about combustion). Its existence +is demonstrated by what happens when a chip burns up -- the magic +smoke gets let out, so it doesn't work any more. See <b><a href="#smoketest">smoke test</a></b>, <b><a href="#letthesmokeout">let the smoke out</a></b>.</p> + +<p>Usenetter Jay Maynard tells the following story: "Once, while +hacking on a dedicated Z80 system, I was testing code by blowing +EPROMs and plugging them in the system, then seeing what +happened. One time, I plugged one in backwards. I only discovered +that <i>after</i> I realized that Intel didn't put power-on +lights under the quartz windows on the tops of their EPROMs -- +the die was glowing white-hot. Amazingly, the EPROM worked fine +after I erased it, filled it full of zeros, then erased it again. +For all I know, it's still in service. Of course, this is because +the magic smoke didn't get let out." Compare the original +phrasing of <b><a href="#MurphysLaw">Murphy's +Law</a></b>.</p> + +<hr> +Node:<a name="mailstorm">mail storm</a>, Next:<a rel="next" +href="#mailbomb">mailbomb</a>, Previous:<a rel="previous" href="#magicsmoke">magic smoke</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>mail storm</b> n.</p> + +<p>[from <b><a href="#broadcaststorm">broadcast storm</a></b>, +influenced by `maelstrom'] What often happens when a machine with +an Internet connection and active users re-connects after +extended downtime -- a flood of incoming mail that brings the +machine to its knees. See also <b><a href="#hairball">hairball</a></b>.</p> + +<hr> +Node:<a name="mailbomb">mailbomb</a>, Next:<a rel="next" href="#mailinglist">mailing list</a>, Previous:<a rel="previous" +href="#mailstorm">mail storm</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>mailbomb</b></p> + +<p>(also <i>mail bomb</i>) [Usenet] 1. v. To send, or urge others +to send, massive amounts of <b><a href="#email">email</a></b> to +a single system or person, esp. with intent to crash or <b><a +href="#spam">spam</a></b> the recipient's system. Sometimes done +in retaliation for a perceived serious offense. Mailbombing is +itself widely regarded as a serious offense -- it can disrupt +email traffic or other facilities for innocent users on the +victim's system, and in extreme cases, even at upstream sites. 2. +n. An automatic procedure with a similar effect. 3. n. The mail +sent. Compare <b><a href="#letterbomb">letterbomb</a></b>, <b><a +href="#nastygram">nastygram</a></b>, <b><a href="#BLOB">BLOB</a></b> (sense 2), <b><a href="#list-bomb">list-bomb</a></b>.</p> + +<hr> +Node:<a name="mailinglist">mailing list</a>, Next:<a rel="next" href="#mainloop">main loop</a>, Previous:<a rel="previous" href="#mailbomb">mailbomb</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>mailing list</b> n.</p> + +<p>(often shortened in context to `list') 1. An <b><a href="#email">email</a></b> address that is an alias (or <b><a href="#macro">macro</a></b>, though that word is never used in this +connection) for many other email addresses. Some mailing lists +are simple `reflectors', redirecting mail sent to them to the +list of recipients. Others are filtered by humans or programs of +varying degrees of sophistication; lists filtered by humans are +said to be `moderated'. 2. The people who receive your email when +you send it to such an address.</p> + +<p>Mailing lists are one of the primary forms of hacker +interaction, along with <b><a href="#Usenet">Usenet</a></b>. They +predate Usenet, having originated with the first UUCP and ARPANET +connections. They are often used for private information-sharing +on topics that would be too specialized for or inappropriate to +public Usenet groups. Though some of these maintain almost purely +technical content (such as the Internet Engineering Task Force +mailing list), others (like the `sf-lovers' list maintained for +many years by Saul Jaffe) are recreational, and many are purely +social. Perhaps the most infamous of the social lists was the +eccentric <i>bandykin</i> distribution; its latter-day progeny, +<i>lectroids</i> and <i>tanstaafl</i>, still include a number of +the oddest and most interesting people in hackerdom.</p> + +<p>Mailing lists are easy to create and (unlike Usenet) don't tie +up a significant amount of machine resources (until they get very +large, at which point they can become interesting torture tests +for mail software). Thus, they are often created temporarily by +working groups, the members of which can then collaborate on a +project without ever needing to meet face-to-face. Much of the +material in this lexicon was criticized and polished on just such +a mailing list (called `jargon-friends'), which included all the +co-authors of Steele-1983.</p> + +<hr> +Node:<a name="mainloop">main loop</a>, Next:<a rel="next" +href="#mainframe">mainframe</a>, Previous:<a rel="previous" href="#mailinglist">mailing list</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>main loop</b> n.</p> + +<p>The top-level control flow construct in an input- or +event-driven program, the one which receives and acts or +dispatches on the program's input. See also <b><a href="#driver">driver</a></b>.</p> + +<hr> +Node:<a name="mainframe">mainframe</a>, Next:<a rel="next" href="#management">management</a>, Previous:<a rel="previous" href="#mainloop">main loop</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>mainframe</b> n.</p> + +<p>Term originally referring to the cabinet containing the +central processor unit or `main frame' of a room-filling <b><a +href="#StoneAge">Stone Age</a></b> batch machine. After the +emergence of smaller `minicomputer' designs in the early 1970s, +the traditional <b><a href="#bigiron">big iron</a></b> +machines were described as `mainframe computers' and eventually +just as mainframes. The term carries the connotation of a machine +designed for batch rather than interactive use, though possibly +with an interactive timesharing operating system retrofitted onto +it; it is especially used of machines built by IBM, Unisys, and +the other great <b><a href="#dinosaur">dinosaur</a></b>s +surviving from computing's <b><a href="#StoneAge">Stone +Age</a></b>.</p> + +<p>It has been common wisdom among hackers since the late 1980s +that the mainframe architectural tradition is essentially dead +(outside of the tiny market for <b><a href="#number-crunching">number-crunching</a></b> supercomputers (see +<b><a href="#cray">cray</a></b>)), having been swamped by the +recent huge advances in IC technology and low-cost personal +computing. The wave of failures, takeovers, and mergers among +traditional mainframe makers in the early 1990s bore this out. +The biggest mainframer of all, IBM, was compelled to re-invent +itself as a huge systems-consulting house. (See <b><a href="#dinosaursmating">dinosaurs mating</a></b> and <b><a href="#killermicro">killer micro</a></b>).</p> + +<hr> +Node:<a name="management">management</a>, Next:<a rel="next" +href="#mandelbug">mandelbug</a>, Previous:<a rel="previous" href="#mainframe">mainframe</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>management</b> n.</p> + +<p>1. Corporate power elites distinguished primarily by their +distance from actual productive work and their chronic failure to +manage (see also <b><a href="#suit">suit</a></b>). Spoken +derisively, as in "<i>Management</i> decided that +<small>...</small>". 2. Mythically, a vast bureaucracy +responsible for all the world's minor irritations. Hackers' +satirical public notices are often signed `The Mgt'; this derives +from the "Illuminatus" novels (see the <b><a href="#Bibliography">Bibliography</a></b> in Appendix C).</p> + +<hr> +Node:<a name="mandelbug">mandelbug</a>, Next:<a rel="next" href="#manged">manged</a>, Previous:<a rel="previous" href="#management">management</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>mandelbug</b> /man'del-buhg/ n.</p> + +<p>[from the Mandelbrot set] A bug whose underlying causes are so +complex and obscure as to make its behavior appear chaotic or +even non-deterministic. This term implies that the speaker thinks +it is a <b><a href="#Bohrbug">Bohr bug</a></b>, rather than a +<b><a href="#heisenbug">heisenbug</a></b>. See also <b><a href="#schroedinbug">schroedinbug</a></b>.</p> + +<hr> +Node:<a name="manged">manged</a>, Next:<a rel="next" href="#mangle">mangle</a>, Previous:<a rel="previous" href="#mandelbug">mandelbug</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>manged</b> /mahnjd/ n.</p> + +<p>[probably from the French `manger' or Italian `mangiare', to +eat; perhaps influenced by English `mange', `mangy'] adj. Refers +to anything that is mangled or damaged, usually beyond repair. +"The disk was manged after the electrical storm." Compare <b><a +href="#mung">mung</a></b>.</p> + +<hr> +Node:<a name="mangle">mangle</a>, Next:<a rel="next" href="#mangledname">mangled name</a>, Previous:<a rel="previous" +href="#manged">manged</a>, Up:<a rel="up" href="#chap13">= +M =</a> <br> + + +<p><b>mangle</b> vt.</p> + +<p>1. Used similarly to <b><a href="#mung">mung</a></b> or <b><a +href="#scribble">scribble</a></b>, but more violent in its +connotations; something that is mangled has been irreversibly and +totally trashed. 2. To produce the <b><a href="#mangledname">mangled name</a></b> corresponding to a C++ +declaration.</p> + +<hr> +Node:<a name="mangledname">mangled name</a>, Next:<a rel="next" href="#mangler">mangler</a>, Previous:<a rel="previous" +href="#mangle">mangle</a>, Up:<a rel="up" href="#chap13">= +M =</a> <br> + + +<p><b>mangled name</b> n.</p> + +<p>A name, appearing in a C++ object file, that is a coded +representation of the object declaration as it appears in the +source. Mangled names are used because C++ allows multiple +objects to have the same name, as long as they are +distinguishable in some other way, such as by having different +parameter types. Thus, the internal name must have that +additional information embedded in it, using the limited +character set allowed by most linkers. For instance, one popular +compiler encodes the standard library function declaration +"memchr(const void*,int,unsigned int)" as "@memchr$qpxviui".</p> + +<hr> +Node:<a name="mangler">mangler</a>, Next:<a rel="next" href="#manularity">manularity</a>, Previous:<a rel="previous" href="#mangledname">mangled name</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>mangler</b> n.</p> + +<p>[DEC] A manager. Compare <b><a href="#management">management</a></b>. Note that <b><a href="#systemmangler">system mangler</a></b> is somewhat different +in connotation.</p> + +<hr> +Node:<a name="manularity">manularity</a>, Next:<a rel="next" +href="#marbles">marbles</a>, Previous:<a rel="previous" href="#mangler">mangler</a>, Up:<a rel="up" href="#chap13">= M +=</a> <br> + + +<p><b>manularity</b> /man`yoo-la'ri-tee/ n.</p> + +<p>[prob. fr. techspeak `manual' + `granularity'] A notional +measure of the manual labor required for some task, particularly +one of the sort that automation is supposed to eliminate. +"Composing English on paper has much higher manularity than using +a text editor, especially in the revising stage." Hackers tend to +consider manularity a symptom of primitive methods; in fact, a +true hacker confronted with an apparent requirement to do a +computing task <b><a href="#byhand">by hand</a></b> will +inevitably seize the opportunity to build another tool (see <b><a +href="#toolsmith">toolsmith</a></b>).</p> + +<hr> +Node:<a name="marbles">marbles</a>, Next:<a rel="next" href="#marginal">marginal</a>, Previous:<a rel="previous" href="#manularity">manularity</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>marbles</b> pl.n.</p> + +<p>[from mainstream "lost all his/her marbles"] The minimum +needed to build your way further up some hierarchy of tools or +abstractions. After a bad system crash, you need to determine if +the machine has enough marbles to come up on its own, or enough +marbles to allow a rebuild from backups, or if you need to +rebuild from scratch. "This compiler doesn't even have enough +marbles to compile <b><a href="#helloworld">hello +world</a></b>."</p> + +<hr> +Node:<a name="marginal">marginal</a>, Next:<a rel="next" href="#MarginalHacks">Marginal Hacks</a>, Previous:<a rel="previous" href="#marbles">marbles</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>marginal</b> adj.</p> + +<p>[common] 1. [techspeak] An extremely small change. "A marginal +increase in <b><a href="#core">core</a></b> can decrease <b><a +href="#GC">GC</a></b> time drastically." In everyday terms, this +means that it is a lot easier to clean off your desk if you have +a spare place to put some of the junk while you sort through it. +2. Of little merit. "This proposed new feature seems rather +marginal to me." 3. Of extremely small probability of <b><a href="#win">win</a></b>ning. "The power supply was rather marginal +anyway; no wonder it fried."</p> + +<hr> +Node:<a name="MarginalHacks">Marginal Hacks</a>, Next:<a rel="next" href="#marginally">marginally</a>, Previous:<a rel="previous" href="#marginal">marginal</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>Marginal Hacks</b> n.</p> + +<p>Margaret Jacks Hall, a building into which the Stanford AI Lab +was moved near the beginning of the 1980s (from the <b><a href="#DCPowerLab">D. C. Power Lab</a></b>).</p> + +<hr> +Node:<a name="marginally">marginally</a>, Next:<a rel="next" +href="#marketroid">marketroid</a>, Previous:<a rel="previous" +href="#MarginalHacks">Marginal Hacks</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>marginally</b> adv.</p> + +<p>Slightly. "The ravs here are only marginally better than at +Small Eating Place." See <b><a href="#epsilon">epsilon</a></b>.</p> + +<hr> +Node:<a name="marketroid">marketroid</a>, Next:<a rel="next" +href="#Mars">Mars</a>, Previous:<a rel="previous" href="#marginally">marginally</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>marketroid</b> /mar'k*-troyd/ n.</p> + +<p>alt. `marketing slime', `marketeer', `marketing droid', +`marketdroid'. A member of a company's marketing department, esp. +one who promises users that the next version of a product will +have features that are not actually scheduled for inclusion, are +extremely difficult to implement, and/or are in violation of the +laws of physics; and/or one who describes existing features (and +misfeatures) in ebullient, buzzword-laden adspeak. Derogatory. +Compare <b><a href="#droid">droid</a></b>.</p> + +<hr> +Node:<a name="Mars">Mars</a>, Next:<a rel="next" href="#martian">martian</a>, Previous:<a rel="previous" href="#marketroid">marketroid</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>Mars</b> n.</p> + +<p>A legendary tragic failure, the archetypal Hacker Dream Gone +Wrong. Mars was the code name for a family of PDP-10 compatible +computers built by Systems Concepts (now, The SC Group): the +multi-processor SC-30M, the small uniprocessor SC-25M, and the +never-built superprocessor SC-40M. These machines were marvels of +engineering design; although not much slower than the unique +<b><a href="#Foonly">Foonly</a></b> F-1, they were physically +smaller and consumed less power than the much slower <b><a href="#DEC">DEC</a></b> KS10 or Foonly F-2, F-3, or F-4 machines. They +were also completely compatible with the DEC KL10, and ran all +KL10 binaries (including the operating system) with no +modifications at about 2-3 times faster than a KL10.</p> + +<p>When DEC cancelled the Jupiter project in 1983, Systems +Concepts should have made a bundle selling their machine into +shops with a lot of software investment in PDP-10s, and in fact +their spring 1984 announcement generated a great deal of +excitement in the PDP-10 world. TOPS-10 was running on the Mars +by the summer of 1984, and TOPS-20 by early fall. Unfortunately, +the hackers running Systems Concepts were much better at +designing machines than at mass producing or selling them; the +company allowed itself to be sidetracked by a bout of +perfectionism into continually improving the design, and lost +credibility as delivery dates continued to slip. They also +overpriced the product ridiculously; they believed they were +competing with the KL10 and VAX 8600 and failed to reckon with +the likes of Sun Microsystems and other hungry startups building +workstations with power comparable to the KL10 at a fraction of +the price. By the time SC shipped the first SC-30M to Stanford in +late 1985, most customers had already made the traumatic decision +to abandon the PDP-10, usually for VMS or Unix boxes. Most of the +Mars computers built ended up being purchased by CompuServe.</p> + +<p>This tale and the related saga of <b><a href="#Foonly">Foonly</a></b> hold a lesson for hackers: if you want +to play in the <b><a href="#RealWorld">Real World</a></b>, you +need to learn Real World moves.</p> + +<hr> +Node:<a name="martian">martian</a>, Next:<a rel="next" href="#massage">massage</a>, Previous:<a rel="previous" href="#Mars">Mars</a>, Up:<a rel="up" href="#chap13">= M =</a> +<br> + + +<p><b>martian</b> n.</p> + +<p>A packet sent on a TCP/IP network with a source address of the +test loopback interface [127.0.0.1]. This means that it will come +back labeled with a source address that is clearly not of this +earth. "The domain server is getting lots of packets from Mars. +Does that gateway have a martian filter?" Compare <b><a href="#Christmastreepacket">Christmas tree packet</a></b>, <b><a +href="#Godzillagram">Godzillagram</a></b>.</p> + +<hr> +Node:<a name="massage">massage</a>, Next:<a rel="next" href="#math-out">math-out</a>, Previous:<a rel="previous" href="#martian">martian</a>, Up:<a rel="up" href="#chap13">= M +=</a> <br> + + +<p><b>massage</b> vt.</p> + +<p>[common] Vague term used to describe `smooth' transformations +of a data set into a different form, esp. transformations that do +not lose information. Connotes less pain than <b><a href="#munch">munch</a></b> or <b><a href="#crunch">crunch</a></b>. +"He wrote a program that massages X bitmap files into GIF +format." Compare <b><a href="#slurp">slurp</a></b>.</p> + +<hr> +Node:<a name="math-out">math-out</a>, Next:<a rel="next" href="#Matrix">Matrix</a>, Previous:<a rel="previous" href="#massage">massage</a>, Up:<a rel="up" href="#chap13">= M +=</a> <br> + + +<p><b>math-out</b> n.</p> + +<p>[poss. from `white-out' (the blizzard variety)] A paper or +presentation so encrusted with mathematical or other formal +notation as to be incomprehensible. This may be a device for +concealing the fact that it is actually <b><a href="#content-free">content-free</a></b>. See also <b><a href="#numbers">numbers</a></b>, <b><a href="#socialsciencenumber">social science number</a></b>.</p> + +<hr> +Node:<a name="Matrix">Matrix</a>, Next:<a rel="next" href="#maximumMaytagmode">maximum Maytag mode</a>, Previous:<a +rel="previous" href="#math-out">math-out</a>, Up:<a rel="up" +href="#chap13">= M =</a> <br> + + +<p><b>Matrix</b> n.</p> + +<p>[FidoNet] 1. What the Opus BBS software and sysops call <b><a +href="#FidoNet">FidoNet</a></b>. 2. Fanciful term for a <b><a +href="#cyberspace">cyberspace</a></b> expected to emerge from +current networking experiments (see <b><a href="#thenetwork">the network</a></b>). The name of the rather +good 1999 <b><a href="#cypherpunk">cypherpunk</a></b> movie "The +Matrix" played on this sense, which however had been established +for years before. 3. The totality of present-day computer +networks (popularized in this sense by John Quarterman; rare +outside academic literature).</p> + +<hr> +Node:<a name="maximumMaytagmode">maximum Maytag mode</a>, +Next:<a rel="next" href="#meatspace">meatspace</a>, Previous:<a +rel="previous" href="#Matrix">Matrix</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>maximum Maytag mode</b> n.</p> + +<p>What a <b><a href="#washingmachine">washing machine</a></b> +or, by extension, any disk drive is in when it's being used so +heavily that it's shaking like an old Maytag with an unbalanced +load. If prolonged for any length of time, can lead to disks +becoming <b><a href="#walkingdrives">walking drives</a></b>. +In 1999 it's been some years since hard disks were large enough +to do this, but the same phenomenon has recently been reported +with 24X CD-ROM drives.</p> + +<hr> +Node:<a name="meatspace">meatspace</a>, Next:<a rel="next" href="#meatware">meatware</a>, Previous:<a rel="previous" href="#maximumMaytagmode">maximum Maytag mode</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>meatspace</b> /meet'spays/ n.</p> + +<p>The physical world, where the meat lives - as opposed to <b><a +href="#cyberspace">cyberspace</a></b>. Hackers are actually more +willing to use this term than `cyberspace', because it's not +speculative - we already have a running meatspace implementation +(the universe). Compare <b><a href="#RL">RL</a></b>.</p> + +<hr> +Node:<a name="meatware">meatware</a>, Next:<a rel="next" href="#meeces">meeces</a>, Previous:<a rel="previous" href="#meatspace">meatspace</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>meatware</b> n.</p> + +<p>Synonym for <b><a href="#wetware">wetware</a></b>. Less +common.</p> + +<hr> +Node:<a name="meeces">meeces</a>, Next:<a rel="next" href="#meg">meg</a>, Previous:<a rel="previous" href="#meatware">meatware</a>, Up:<a rel="up" href="#chap13">= +M =</a> <br> + + +<p><b>meeces</b> /mees'*z/ n.</p> + +<p>[TMRC] Occasional furry visitors who are not <b><a href="#urchin">urchin</a></b>s. [That is, mice. This may no longer be +in live use; it clearly derives from the refrain of the +early-1960s cartoon character Mr. Jinx: "I hate meeces to +<i>pieces</i>!" -- ESR]</p> + +<hr> +Node:<a name="meg">meg</a>, Next:<a rel="next" href="#mega-">mega-</a>, Previous:<a rel="previous" href="#meeces">meeces</a>, Up:<a rel="up" href="#chap13">= M +=</a> <br> + + +<p><b>meg</b> /meg/ n.</p> + +<p>See <b><a href="#quantifiers">quantifiers</a></b>.</p> + +<hr> +Node:<a name="mega-">mega-</a>, Next:<a rel="next" href="#megapenny">megapenny</a>, Previous:<a rel="previous" href="#meg">meg</a>, Up:<a rel="up" href="#chap13">= M =</a> +<br> + + +<p><b>mega-</b> /me'g*/ pref.</p> + +<p>[SI] See <b><a href="#quantifiers">quantifiers</a></b>.</p> + +<hr> +Node:<a name="megapenny">megapenny</a>, Next:<a rel="next" href="#MEGO">MEGO</a>, Previous:<a rel="previous" href="#mega-">mega-</a>, Up:<a rel="up" href="#chap13">= M +=</a> <br> + + +<p><b>megapenny</b> /meg'*-pen`ee/ n.</p> + +<p>$10,000 (1 cent * 10^6). Used semi-humorously as a unit in +comparing computer cost and performance figures.</p> + +<hr> +Node:<a name="MEGO">MEGO</a>, Next:<a rel="next" href="#meltdownnetwork">meltdown network</a>, Previous:<a rel="previous" href="#megapenny">megapenny</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>MEGO</b> /me'goh/ or /mee'goh/</p> + +<p>[`My Eyes Glaze Over', often `Mine Eyes Glazeth (sic) Over', +attributed to the futurologist Herman Kahn] Also `MEGO factor'. +1. n. A <b><a href="#handwave">handwave</a></b> intended to +confuse the listener and hopefully induce agreement because the +listener does not want to admit to not understanding what is +going on. MEGO is usually directed at senior management by +engineers and contains a high proportion of <b><a href="#TLA">TLA</a></b>s. 2. excl. An appropriate response to MEGO +tactics. 3. Among non-hackers, often refers not to behavior that +causes the eyes to glaze, but to the eye-glazing reaction itself, +which may be triggered by the mere threat of technical detail as +effectively as by an actual excess of it.</p> + +<hr> +Node:<a name="meltdownnetwork">meltdown network</a>, Next:<a +rel="next" href="#meme">meme</a>, Previous:<a rel="previous" +href="#MEGO">MEGO</a>, Up:<a rel="up" href="#chap13">= M +=</a> <br> + + +<p><b>meltdown, network</b> n.</p> + +<p>See <b><a href="#networkmeltdown">network +meltdown</a></b>.</p> + +<hr> +Node:<a name="meme">meme</a>, Next:<a rel="next" href="#memeplague">meme plague</a>, Previous:<a rel="previous" +href="#meltdownnetwork">meltdown network</a>, Up:<a rel="up" +href="#chap13">= M =</a> <br> + + +<p><b>meme</b> /meem/ n.</p> + +<p>[coined by analogy with `gene', by Richard Dawkins] An idea +considered as a <b><a href="#replicator">replicator</a></b>, esp. +with the connotation that memes parasitize people into +propagating them much as viruses do. Used esp. in the phrase +`meme complex' denoting a group of mutually supporting memes that +form an organized belief system, such as a religion. This lexicon +is an (epidemiological) vector of the `hacker subculture' meme +complex; each entry might be considered a meme. However, `meme' +is often misused to mean `meme complex'. Use of the term connotes +acceptance of the idea that in humans (and presumably other tool- +and language-using sophonts) cultural evolution by selection of +adaptive ideas has superseded biological evolution by selection +of hereditary traits. Hackers find this idea congenial for +tolerably obvious reasons.</p> + +<hr> +Node:<a name="memeplague">meme plague</a>, Next:<a rel="next" +href="#memetics">memetics</a>, Previous:<a rel="previous" href="#meme">meme</a>, Up:<a rel="up" href="#chap13">= M =</a> +<br> + + +<p><b>meme plague</b> n.</p> + +<p>The spread of a successful but pernicious <b><a href="#meme">meme</a></b>, esp. one that parasitizes the victims into +giving their all to propagate it. Astrology, BASIC, and the other +guy's religion are often considered to be examples. This usage is +given point by the historical fact that `joiner' ideologies like +Naziism or various forms of millennarian Christianity have +exhibited plague-like cycles of exponential growth followed by +collapses to small reservoir populations.</p> + +<hr> +Node:<a name="memetics">memetics</a>, Next:<a rel="next" href="#memoryfarts">memory farts</a>, Previous:<a rel="previous" +href="#memeplague">meme plague</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>memetics</b> /me-met'iks/ n.</p> + +<p>[from <b><a href="#meme">meme</a></b>] The study of memes. As +of early 1999, this is still an extremely informal and +speculative endeavor, though the first steps towards at least +statistical rigor have been made by H. Keith Henson and others. +Memetics is a popular topic for speculation among hackers, who +like to see themselves as the architects of the new information +ecologies in which memes live and replicate.</p> + +<hr> +Node:<a name="memoryfarts">memory farts</a>, Next:<a rel="next" href="#memoryleak">memory leak</a>, Previous:<a rel="previous" href="#memetics">memetics</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>memory farts</b> n.</p> + +<p>The flatulent sounds that some DOS box BIOSes (most notably +AMI's) make when checking memory on bootup.</p> + +<hr> +Node:<a name="memoryleak">memory leak</a>, Next:<a rel="next" +href="#memorysmash">memory smash</a>, Previous:<a rel="previous" href="#memoryfarts">memory farts</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>memory leak</b> n.</p> + +<p>An error in a program's dynamic-store allocation logic that +causes it to fail to reclaim discarded memory, leading to +eventual collapse due to memory exhaustion. Also (esp. at CMU) +called <b><a href="#coreleak">core leak</a></b>. These +problems were severe on older machines with small, fixed-size +address spaces, and special "leak detection" tools were commonly +written to root them out. With the advent of virtual memory, it +is unfortunately easier to be sloppy about wasting a bit of +memory (although when you run out of memory on a VM machine, it +means you've got a <i>real</i> leak!). See <b><a href="#aliasingbug">aliasing bug</a></b>, <b><a href="#fandangooncore">fandango on core</a></b>, <b><a href="#smashthestack">smash the stack</a></b>, <b><a href="#precedencelossage">precedence lossage</a></b>, <b><a href="#overrunscrew">overrun screw</a></b>, <b><a href="#leakyheap">leaky heap</a></b>, <b><a href="#leak">leak</a></b>.</p> + +<hr> +Node:<a name="memorysmash">memory smash</a>, Next:<a rel="next" href="#menuitis">menuitis</a>, Previous:<a rel="previous" +href="#memoryleak">memory leak</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>memory smash</b> n.</p> + +<p>[XEROX PARC] Writing through a pointer that doesn't point to +what you think it does. This occasionally reduces your machine to +a rubble of bits. Note that this is subtly different from (and +more general than) related terms such as a <b><a href="#memoryleak">memory leak</a></b> or <b><a href="#fandangooncore">fandango on core</a></b> because it +doesn't imply an allocation error or overrun condition.</p> + +<hr> +Node:<a name="menuitis">menuitis</a>, Next:<a rel="next" href="#mess-dos">mess-dos</a>, Previous:<a rel="previous" href="#memorysmash">memory smash</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>menuitis</b> /men`yoo-i:'tis/ n.</p> + +<p>Notional disease suffered by software with an obsessively +simple-minded menu interface and no escape. Hackers find this +intensely irritating and much prefer the flexibility of +command-line or language-style interfaces, especially those +customizable via macros or a special-purpose language in which +one can encode useful hacks. See <b><a href="#user-obsequious">user-obsequious</a></b>, <b><a href="#droolproofpaper">drool-proof paper</a></b>, <b><a href="#WIMPenvironment">WIMP environment</a></b>, <b><a href="#fortherestofus">for the rest of us</a></b>.</p> + +<hr> +Node:<a name="mess-dos">mess-dos</a>, Next:<a rel="next" href="#meta">meta</a>, Previous:<a rel="previous" href="#menuitis">menuitis</a>, Up:<a rel="up" href="#chap13">= +M =</a> <br> + + +<p><b>mess-dos</b> /mes-dos/ n.</p> + +<p>[semi-obsolescent now that DOS is] Derisory term for MS-DOS. +Often followed by the ritual banishing "Just say No!" See <b><a +href="#MS-DOS">MS-DOS</a></b>. Most hackers (even many MS-DOS +hackers) loathed MS-DOS for its single-tasking nature, its limits +on application size, its nasty primitive interface, and its ties +to IBMness and Microsoftness (see <b><a href="#fearandloathing">fear and loathing</a></b>). Also +`mess-loss', `messy-dos', `mess-dog', `mess-dross', `mush-dos', +and various combinations thereof. In Ireland and the U.K. it is +even sometimes called `Domestos' after a brand of toilet +cleanser.</p> + +<hr> +Node:<a name="meta">meta</a>, Next:<a rel="next" href="#metabit">meta bit</a>, Previous:<a rel="previous" href="#mess-dos">mess-dos</a>, Up:<a rel="up" href="#chap13">= +M =</a> <br> + + +<p><b>meta</b> /me't*/ or /may't*/ or (Commonwealth) /mee't*/ +adj.,pref.</p> + +<p>[from analytic philosophy] One level of description up. A +metasyntactic variable is a variable in notation used to describe +syntax, and meta-language is language used to describe language. +This is difficult to explain briefly, but much hacker humor turns +on deliberate confusion between meta-levels. See <b><a href="#hackerhumor">hacker humor</a></b>.</p> + +<hr> +Node:<a name="metabit">meta bit</a>, Next:<a rel="next" href="#metasyntacticvariable">metasyntactic variable</a>, +Previous:<a rel="previous" href="#meta">meta</a>, Up:<a rel="up" +href="#chap13">= M =</a> <br> + + +<p><b>meta bit</b> n.</p> + +<p>The top bit of an 8-bit character, which is on in character +values 128-255. Also called <b><a href="#highBit">high +bit</a></b>, <b><a href="#altbit">alt bit</a></b>, or (rarely) +<b><a href="#hobbit">hobbit</a></b>. Some terminals and consoles +(see <b><a href="#space-cadetkeyboard">space-cadet +keyboard</a></b>) have a META shift key. Others (including, +<i>mirabile dictu</i>, keyboards on IBM PC-class machines) have +an ALT key. See also <b><a href="#buckybits">bucky +bits</a></b>.</p> + +<p>Historical note: although in modern usage shaped by a universe +of 8-bit bytes the meta bit is invariably hex 80 (octal 0200), +things were different on earlier machines with 36-bit words and +9-bit bytes. The MIT and Stanford keyboards (see <b><a href="#space-cadetkeyboard">space-cadet keyboard</a></b>) generated +hex 100 (octal 400) from their meta keys.</p> + +<hr> +Node:<a name="metasyntacticvariable">metasyntactic +variable</a>, Next:<a rel="next" href="#MFTL">MFTL</a>, +Previous:<a rel="previous" href="#metabit">meta bit</a>, Up:<a +rel="up" href="#chap13">= M =</a> <br> + + +<p><b>metasyntactic variable</b> n.</p> + +<p>A name used in examples and understood to stand for whatever +thing is under discussion, or any random member of a class of +things under discussion. The word <b><a href="#foo">foo</a></b> +is the <b><a href="#canonical">canonical</a></b> example. To +avoid confusion, hackers never (well, hardly ever) use `foo' or +other words like it as permanent names for anything. In +filenames, a common convention is that any filename beginning +with a metasyntactic-variable name is a <b><a href="#scratch">scratch</a></b> file that may be deleted at any +time.</p> + +<p>Metasyntactic variables are so called because (1) they are +variables in the metalanguage used to talk about programs etc; +(2) they are variables whose values are often variables (as in +usages usages like "the value of f(foo,bar) is the sum of foo and +bar"). However, it has been plausibly suggested that the real +reason for the term "metasyntactic variable" is that it sounds +good.</p> + +<p>To some extent, the list of one's preferred metasyntactic +variables is a cultural signature. They occur both in series +(used for related groups of variables or objects) and as +singletons. Here are a few common signatures:</p> + +<blockquote> +<dl> +<dt><b><a href="#foo">foo</a></b>, <b><a href="#bar">bar</a></b>, +<b><a href="#baz">baz</a></b>, <b><a href="#quux">quux</a></b>, +quuux, quuuux...:</dt> + +<dd>MIT/Stanford usage, now found everywhere (thanks largely to +early versions of this lexicon!). At MIT (but not at Stanford), +<b><a href="#baz">baz</a></b> dropped out of use for a while in +the 1970s and '80s. A common recent mutation of this sequence +inserts <b><a href="#qux">qux</a></b> before <b><a href="#quux">quux</a></b>.</dd> + +<dt>bazola, ztesch:</dt> + +<dd>Stanford (from mid-'70s on).</dd> + +<dt><b><a href="#foo">foo</a></b>, <b><a href="#bar">bar</a></b>, +thud, grunt:</dt> + +<dd>This series was popular at CMU. Other CMU-associated +variables include <b><a href="#gorp">gorp</a></b>.</dd> + +<dt><b><a href="#foo">foo</a></b>, <b><a href="#bar">bar</a></b>, +fum:</dt> + +<dd>This series is reported to be common at XEROX PARC.</dd> + +<dt><b><a href="#fred">fred</a></b>, jim, sheila, <b><a href="#barney">barney</a></b>:</dt> + +<dd>See the entry for <b><a href="#fred">fred</a></b>. These tend +to be Britishisms.</dd> + +<dt><b><a href="#corge">corge</a></b>, <b><a href="#grault">grault</a></b>, <b><a href="#flarp">flarp</a></b>:</dt> + +<dd>Popular at Rutgers University and among <b><a href="#GOSMACS">GOSMACS</a></b> hackers.</dd> + +<dt>zxc, spqr, wombat:</dt> + +<dd>Cambridge University (England).</dd> + +<dt>shme</dt> + +<dd>Berkeley, GeoWorks, Ingres. Pronounced /shme/ with a short +/e/.</dd> + +<dt>foo, bar, baz, bongo</dt> + +<dd>Yale, late 1970s.</dd> + +<dt>spam</dt> + +<dd><b><a href="#Python">Python</a></b> programmers.</dd> + +<dt>snork</dt> + +<dd>Brown University, early 1970s.</dd> + +<dt><b><a href="#foo">foo</a></b>, <b><a href="#bar">bar</a></b>, +zot</dt> + +<dd>Helsinki University of Technology, Finland.</dd> + +<dt>blarg, wibble</dt> + +<dd>New Zealand.</dd> + +<dt>toto, titi, tata, tutu</dt> + +<dd>France.</dd> + +<dt>pippo, pluto, paperino</dt> + +<dd>Italy. Pippo /pee'po/ and Paperino /pa-per-ee'-no/ are the +Italian names for Goofy and Donald Duck.</dd> + +<dt>aap, noot, mies</dt> + +<dd>The Netherlands. These are the first words a child used to +learn to spell on a Dutch spelling board.</dd> + +<dt>oogle, foogle, boogle; zork, gork, bork</dt> + +<dd>These two series (which may be continued with other initial +consonents) are reportedly common in England, and said to go back +to Lewis Carroll.</dd> +</dl> +</blockquote> + +<p>Of all these, only `foo' and `bar' are universal (and <b><a +href="#baz">baz</a></b> nearly so). The compounds <b><a href="#foobar">foobar</a></b> and `foobaz' also enjoy very wide +currency.</p> + +<p>Some jargon terms are also used as metasyntactic names; <b><a +href="#barf">barf</a></b> and <b><a href="#mumble">mumble</a></b>, for example. See also <b><a href="#CommonwealthHackish">Commonwealth Hackish</a></b> for +discussion of numerous metasyntactic variables found in Great +Britain and the Commonwealth.</p> + +<hr> +Node:<a name="MFTL">MFTL</a>, Next:<a rel="next" href="#mickey">mickey</a>, Previous:<a rel="previous" href="#metasyntacticvariable">metasyntactic variable</a>, Up:<a +rel="up" href="#chap13">= M =</a> <br> + + +<p><b>MFTL</b> /M-F-T-L/</p> + +<p>[abbreviation: `My Favorite Toy Language'] 1. adj. Describes a +talk on a programming language design that is heavy on the syntax +(with lots of BNF), sometimes even talks about semantics (e.g., +type systems), but rarely, if ever, has any content (see <b><a +href="#content-free">content-free</a></b>). More broadly applied +to talks -- even when the topic is not a programming language -- +in which the subject matter is gone into in unnecessary and +meticulous detail at the sacrifice of any conceptual content. +"Well, it was a typical MFTL talk". 2. n. Describes a language +about which the developers are passionate (often to the point of +proselytic zeal) but no one else cares about. Applied to the +language by those outside the originating group. "He cornered me +about type resolution in his MFTL."</p> + +<p>The first great goal in the mind of the designer of an MFTL is +usually to write a compiler for it, then bootstrap the design +away from contamination by lesser languages by writing a compiler +for it in itself. Thus, the standard put-down question at an MFTL +talk is "Has it been used for anything besides its own compiler?" +On the other hand, a (compiled) language that cannot even be used +to write its own compiler is beneath contempt. (The qualification +has become necessary because of the increasing popularity of +interpreted languages like <b><a href="#Perl">Perl</a></b> and +<b><a href="#Python">Python</a></b>. See <b><a href="#break-evenpoint">break-even point</a></b>.</p> + +<p>(On a related note, Doug McIlroy once proposed a test of the +generality and utility of a language and the operating system +under which it is compiled: "Is the output of a FORTRAN program +acceptable as input to the FORTRAN compiler?" In other words, can +you write programs that write programs? (See <b><a href="#toolsmith">toolsmith</a></b>.) Alarming numbers of (language, +OS) pairs fail this test, particularly when the language is +FORTRAN; aficionados are quick to point out that <b><a href="#Unix">Unix</a></b> (even using FORTRAN) passes it handily. That +the test could ever be failed is only surprising to those who +have had the good fortune to have worked only under modern +systems which lack OS-supported and -imposed "file types".)</p> + +<hr> +Node:<a name="mickey">mickey</a>, Next:<a rel="next" href="#mickeymouseprogram">mickey mouse program</a>, Previous:<a +rel="previous" href="#MFTL">MFTL</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>mickey</b> n.</p> + +<p>The resolution unit of mouse movement. It has been suggested +that the `disney' will become a benchmark unit for animation +graphics performance.</p> + +<hr> +Node:<a name="mickeymouseprogram">mickey mouse program</a>, +Next:<a rel="next" href="#micro-">micro-</a>, Previous:<a rel="previous" href="#mickey">mickey</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>mickey mouse program</b> n.</p> + +<p>North American equivalent of a <b><a href="#noddy">noddy</a></b> (that is, trivial) program. Doesn't +necessarily have the belittling connotations of mainstream slang +"Oh, that's just mickey mouse stuff!"; sometimes trivial programs +can be very useful.</p> + +<hr> +Node:<a name="micro-">micro-</a>, Next:<a rel="next" href="#MicroDroid">MicroDroid</a>, Previous:<a rel="previous" href="#mickeymouseprogram">mickey mouse program</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>micro-</b> pref.</p> + +<p>1. Very small; this is the root of its use as a quantifier +prefix. 2. A quantifier prefix, calling for multiplication by +10^(-6) (see <b><a href="#quantifiers">quantifiers</a></b>). +Neither of these uses is peculiar to hackers, but hackers tend to +fling them both around rather more freely than is countenanced in +standard English. It is recorded, for example, that one CS +professor used to characterize the standard length of his +lectures as a microcentury -- that is, about 52.6 minutes (see +also <b><a href="#attoparsec">attoparsec</a></b>, <b><a href="#nanoacre">nanoacre</a></b>, and especially <b><a href="#microfortnight">microfortnight</a></b>). 3. Personal or +human-scale -- that is, capable of being maintained or +comprehended or manipulated by one human being. This sense is +generalized from `microcomputer', and is esp. used in contrast +with `macro-' (the corresponding Greek prefix meaning `large'). +4. Local as opposed to global (or <b><a href="#macro-">macro-</a></b>). Thus a hacker might say that buying a +smaller car to reduce pollution only solves a microproblem; the +macroproblem of getting to work might be better solved by using +mass transit, moving to within walking distance, or (best of all) +telecommuting.</p> + +<hr> +Node:<a name="MicroDroid">MicroDroid</a>, Next:<a rel="next" +href="#microfloppies">microfloppies</a>, Previous:<a rel="previous" href="#micro-">micro-</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>MicroDroid</b> n.</p> + +<p>[Usenet] A Microsoft employee, esp. one who posts to various +operating-system advocacy newsgroups. MicroDroids post follow-ups +to any messages critical of Microsoft's operating systems, and +often end up sounding like visiting fundamentalist missionaries. +See also <b><a href="#astroturfing">astroturfing</a></b>; compare +<b><a href="#microserf">microserf</a></b>.</p> + +<hr> +Node:<a name="microfloppies">microfloppies</a>, Next:<a rel="next" href="#microfortnight">microfortnight</a>, Previous:<a +rel="previous" href="#MicroDroid">MicroDroid</a>, Up:<a rel="up" +href="#chap13">= M =</a> <br> + + +<p><b>microfloppies</b> n.</p> + +<p>3.5-inch floppies, as opposed to 5.25-inch <b><a href="#vanilla">vanilla</a></b> or mini-floppies and the now-obsolete +8-inch variety. This term may be headed for obsolescence as +5.25-inchers pass out of use, only to be revived if anybody +floats a sub-3-inch floppy standard. See <b><a href="#stiffy">stiffy</a></b>, <b><a href="#minifloppies">minifloppies</a></b>.</p> + +<hr> +Node:<a name="microfortnight">microfortnight</a>, Next:<a rel="next" href="#microLenat">microLenat</a>, Previous:<a rel="previous" href="#microfloppies">microfloppies</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>microfortnight</b> n.</p> + +<p>1/1000000 of the fundamental unit of time in the +Furlong/Firkin/Fortnight system of measurement; 1.2096 sec. (A +furlong is 1/8th of a mile; a firkin is 1/4th of a barrel; the +mass unit of the system is taken to be a firkin of water). The +VMS operating system has a lot of tuning parameters that you can +set with the SYSGEN utility, and one of these is TIMEPROMPTWAIT, +the time the system will wait for an operator to set the correct +date and time at boot if it realizes that the current value is +bogus. This time is specified in microfortnights!</p> + +<p>Multiple uses of the millifortnight (about 20 minutes) and +<b><a href="#nanofortnight">nanofortnight</a></b> have also been +reported.</p> + +<hr> +Node:<a name="microLenat">microLenat</a>, Next:<a rel="next" +href="#microReid">microReid</a>, Previous:<a rel="previous" href="#microfortnight">microfortnight</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>microLenat</b> /mi:`-kroh-len'-*t/ n.</p> + +<p>The unit of <b><a href="#bogosity">bogosity</a></b>. consensus +is that this is the largest unit practical for everyday use. The +microLenat, originally invented by David Jefferson, was +promulgated as an attack against noted computer scientist Doug +Lenat by a <b><a href="#tenuredgraduatestudent">tenured +graduate student</a></b> at CMU. Doug had failed the student on +an important exam because the student gave only "AI is bogus" as +his answer to the questions. The slur is generally considered +unmerited, but it has become a running gag nevertheless. Some of +Doug's friends argue that <i>of course</i> a microLenat is +bogus, since it is only one millionth of a Lenat. Others have +suggested that the unit should be redesignated after the grad +student, as the microReid.</p> + +<hr> +Node:<a name="microReid">microReid</a>, Next:<a rel="next" href="#microserf">microserf</a>, Previous:<a rel="previous" href="#microLenat">microLenat</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>microReid</b> /mi:'kroh-reed/ n.</p> + +<p>See <b><a href="#microLenat">microLenat</a></b>.</p> + +<hr> +Node:<a name="microserf">microserf</a>, Next:<a rel="next" href="#MicroslothWindows">Microsloth Windows</a>, Previous:<a rel="previous" href="#microReid">microReid</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>microserf</b> /mi:'kro-s*rf/</p> + +<p>[popularized, though not originated, by Douglas Copeland's +book "Microserfs"] A programmer at <b><a href="#Microsoft">Microsoft</a></b>, especially a low-level coder with +little chance of fame or fortune. Compare <b><a href="#MicroDroid">MicroDroid</a></b>.</p> + +<hr> +Node:<a name="MicroslothWindows">Microsloth Windows</a>, +Next:<a rel="next" href="#Microsoft">Microsoft</a>, Previous:<a +rel="previous" href="#microserf">microserf</a>, Up:<a rel="up" +href="#chap13">= M =</a> <br> + + +<p><b>Microsloth Windows</b> /mi:'kroh-sloth` win'dohz/ n.</p> + +<p>(Variants combine {Microshift, Macroshaft, Microsuck} with +{Windoze, WinDOS}. Hackerism(s) for `Microsoft Windows'. A +thirty-two bit extension and graphical shell to a sixteen bit +patch to an eight bit operating system originally coded for a +four bit microprocessor which was written by a two-bit company +that can't stand one bit of competition. Also just called +`Windoze', with the implication that you can fall asleep waiting +for it to do anything; the latter term is extremely common on +Usenet. See <b><a href="#BlackScreenofDeath">Black +Screen of Death</a></b> and <b><a href="#BlueScreenofDeath">Blue Screen of Death</a></b>; +compare <b><a href="#X">X</a></b>, <b><a href="#sun-stools">sun-stools</a></b>.</p> + +<hr> +Node:<a name="Microsoft">Microsoft</a>, Next:<a rel="next" href="#microse1">micros~1</a>, Previous:<a rel="previous" href="#MicroslothWindows">Microsloth Windows</a>, Up:<a rel="up" +href="#chap13">= M =</a> <br> + + +<p><b>Microsoft</b></p> + +<p>The new <b><a href="#EvilEmpire">Evil Empire</a></b> (the +old one was <b><a href="#IBM">IBM</a></b>). The basic complaints +are, as formerly with IBM, that (a) their system designs are +horrible botches, (b) we can't get <b><a href="#source">source</a></b> to fix them, and (c) they throw their +weight around a lot. See also <b><a href="#HalloweenDocuments">Halloween Documents</a></b>.</p> + +<hr> +Node:<a name="microse1">micros~1</a>, Next:<a rel="next" href="#middle-endian">middle-endian</a>, Previous:<a rel="previous" +href="#Microsoft">Microsoft</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>micros~1</b></p> + +<p>An abbreviation of the full name <b><a href="#Microsoft">Microsoft</a></b> resembling the rather <b><a href="#bogus">bogus</a></b> way Windows 9x's VFAT filesystem truncates +long file names to fit in the MS-DOS 8+3 scheme (the real +filename is stored elsewhere). If other files start with the same +prefix, they'll be called micros~2 and so on, causing lots of +problems with backups and other routine system-administration +problems. During the US Antitrust trial against Microsoft the +names Micros~1 ans Micros~2 were suggested for the two companies +that would exist after a break-up.</p> + +<hr> +Node:<a name="middle-endian">middle-endian</a>, Next:<a rel="next" href="#middleoutimplementation">middle-out +implementation</a>, Previous:<a rel="previous" href="#microse1">micros~1</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>middle-endian</b> adj.</p> + +<p>Not <b><a href="#big-endian">big-endian</a></b> or <b><a href="#little-endian">little-endian</a></b>. Used of perverse byte +orders such as 3-4-1-2 or 2-1-4-3, occasionally found in the +packed-decimal formats of minicomputer manufacturers who shall +remain nameless. See <b><a href="#NUXIproblem">NUXI +problem</a></b>. Non-US hackers use this term to describe the +American mm/dd/yy style of writing dates (Europeans write +little-endian dd/mm/yy, and Japanese use big-endian yy/mm/dd for +Western dates).</p> + +<hr> +Node:<a name="middleoutimplementation">middle-out +implementation</a>, Next:<a rel="next" href="#milliLampson">milliLampson</a>, Previous:<a rel="previous" +href="#middle-endian">middle-endian</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>middle-out implementation</b></p> + +<p>See <b><a href="#bottom-upimplementation">bottom-up +implementation</a></b>.</p> + +<hr> +Node:<a name="milliLampson">milliLampson</a>, Next:<a rel="next" +href="#minifloppies">minifloppies</a>, Previous:<a rel="previous" +href="#middleoutimplementation">middle-out +implementation</a>, Up:<a rel="up" href="#chap13">= M +=</a> <br> + + +<p><b>milliLampson</b> /mil'*-lamp`sn/ n.</p> + +<p>A unit of talking speed, abbreviated mL. Most people run about +200 milliLampsons. The eponymous Butler Lampson (a CS theorist +and systems implementor highly regarded among hackers) goes at +1000. A few people speak faster. This unit is sometimes used to +compare the (sometimes widely disparate) rates at which people +can generate ideas and actually emit them in speech. For example, +noted computer architect C. Gordon Bell (designer of the PDP-11) +is said, with some awe, to think at about 1200 mL but only talk +at about 300; he is frequently reduced to fragments of sentences +as his mouth tries to keep up with his speeding brain.</p> + +<hr> +Node:<a name="minifloppies">minifloppies</a>, Next:<a rel="next" +href="#MIPS">MIPS</a>, Previous:<a rel="previous" href="#milliLampson">milliLampson</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>minifloppies</b> n.,obs.</p> + +<p>5.25-inch floppy disks, as opposed to 3.5-inch or <b><a href="#microfloppies">microfloppies</a></b> and the long-obsolescent +8-inch variety (if there is ever a smaller size, they will +undoubtedly be tagged `nanofloppies'). At one time, this term was +a trademark of Shugart Associates for their SA-400 minifloppy +drive. Nobody paid any attention. See <b><a href="#stiffy">stiffy</a></b>.</p> + +<hr> +Node:<a name="MIPS">MIPS</a>, Next:<a rel="next" href="#misbug">misbug</a>, Previous:<a rel="previous" href="#minifloppies">minifloppies</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>MIPS</b> /mips/ n.</p> + +<p>[abbreviation] 1. A measure of computing speed; formally, +`Million Instructions Per Second' (that's 10^6 per second, not +2^(20)!); often rendered by hackers as `Meaningless Indication of +Processor Speed' or in other unflattering ways, such as +`Meaningless Information Provided by Salesmen'. This joke +expresses an attitude nearly universal among hackers about the +value of most <b><a href="#benchmark">benchmark</a></b> claims, +said attitude being one of the great cultural divides between +hackers and <b><a href="#marketroid">marketroid</a></b>s (see +also <b><a href="#BogoMIPS">BogoMIPS</a></b>). The singular is +sometimes `1 MIP' even though this is clearly etymologically +wrong. See also <b><a href="#KIPS">KIPS</a></b> and <b><a href="#GIPS">GIPS</a></b>. 2. Computers, especially large computers, +considered abstractly as sources of <b><a href="#computron">computron</a></b>s. "This is just a workstation; the +heavy MIPS are hidden in the basement." 3. The corporate name of +a particular RISC-chip company; among other things, they designed +the processor chips used in <b><a href="#DEC">DEC</a></b>'s 3100 +workstation series. 4. Acronym for `Meaningless Information per +Second' (a joke, prob. from sense 1).</p> + +<hr> +Node:<a name="misbug">misbug</a>, Next:<a rel="next" href="#misfeature">misfeature</a>, Previous:<a rel="previous" href="#MIPS">MIPS</a>, Up:<a rel="up" href="#chap13">= M =</a> +<br> + + +<p><b>misbug</b> /mis-buhg/ n.</p> + +<p>[MIT; rare (like its referent)] An unintended property of a +program that turns out to be useful; something that should have +been a <b><a href="#bug">bug</a></b> but turns out to be a <b><a +href="#feature">feature</a></b>. Compare <b><a href="#greenlightning">green lightning</a></b>. See <b><a href="#miswart">miswart</a></b>.</p> + +<hr> +Node:<a name="misfeature">misfeature</a>, Next:<a rel="next" +href="#Missedem-five">Missed'em-five</a>, Previous:<a rel="previous" href="#misbug">misbug</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>misfeature</b> /mis-fee'chr/ or /mis'fee`chr/ n.</p> + +<p>[common] A feature that eventually causes lossage, possibly +because it is not adequate for a new situation that has evolved. +Since it results from a deliberate and properly implemented +feature, a misfeature is not a bug. Nor is it a simple unforeseen +side effect; the term implies that the feature in question was +carefully planned, but its long-term consequences were not +accurately or adequately predicted (which is quite different from +not having thought ahead at all). A misfeature can be a +particularly stubborn problem to resolve, because fixing it +usually involves a substantial philosophical change to the +structure of the system involved.</p> + +<p>Many misfeatures (especially in user-interface design) arise +because the designers/implementors mistake their personal tastes +for laws of nature. Often a former feature becomes a misfeature +because trade-offs were made whose parameters subsequently change +(possibly only in the judgment of the implementors). "Well, yeah, +it is kind of a misfeature that file names are limited to six +characters, but the original implementors wanted to save +directory space and we're stuck with it for now."</p> + +<hr> +Node:<a name="Missedem-five">Missed'em-five</a>, Next:<a rel="next" href="#missileaddress">missile address</a>, Previous:<a +rel="previous" href="#misfeature">misfeature</a>, Up:<a rel="up" +href="#chap13">= M =</a> <br> + + +<p><b>Missed'em-five</b> n.</p> + +<p>Pejorative hackerism for AT&T System V Unix, generally +used by <b><a href="#BSD">BSD</a></b> partisans in a bigoted +mood. (The synonym `SysVile' is also encountered.) See <b><a +href="#softwarebloat">software bloat</a></b>, <b><a href="#Berzerkeley">Berzerkeley</a></b>.</p> + +<hr> +Node:<a name="missileaddress">missile address</a>, Next:<a +rel="next" href="#miswart">miswart</a>, Previous:<a rel="previous" href="#Missedem-five">Missed'em-five</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>missile address</b> n.</p> + +<p>See <b><a href="#ICBMaddress">ICBM address</a></b>.</p> + +<hr> +Node:<a name="miswart">miswart</a>, Next:<a rel="next" href="#MMF">MMF</a>, Previous:<a rel="previous" href="#missileaddress">missile address</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>miswart</b> /mis-wort/ n.</p> + +<p>[from <b><a href="#wart">wart</a></b> by analogy with <b><a +href="#misbug">misbug</a></b>] A <b><a href="#feature">feature</a></b> that superficially appears to be a +<b><a href="#wart">wart</a></b> but has been determined to be the +<b><a href="#RightThing">Right Thing</a></b>. For example, in +some versions of the <b><a href="#EMACS">EMACS</a></b> text +editor, the `transpose characters' command exchanges the +character under the cursor with the one before it on the screen, +<i>except</i> when the cursor is at the end of a line, in which +case the two characters before the cursor are exchanged. While +this behavior is perhaps surprising, and certainly inconsistent, +it has been found through extensive experimentation to be what +most users want. This feature is a miswart.</p> + +<hr> +Node:<a name="MMF">MMF</a>, Next:<a rel="next" href="#mobo">mobo</a>, Previous:<a rel="previous" href="#miswart">miswart</a>, Up:<a rel="up" href="#chap13">= M +=</a> <br> + + +<p><b>MMF</b> //</p> + +<p>[Usenet; common] Abbreviation: "Make Money Fast". Refers to +any kind of scheme which promises participants large profits with +little or no risk or effort. Typically, it is a some kind of +multi-level marketing operation which involves recruiting more +members, or an illegal pyramid scam. The term is also used to +refer to any kind of spam which promotes this. For more +information, see the Make Money Fast Myth +Page.</p> + +<hr> +Node:<a name="mobo">mobo</a>, Next:<a rel="next" href="#moby">moby</a>, Previous:<a rel="previous" href="#MMF">MMF</a>, +Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>mobo</b> /moh'bo/</p> + +<p>Written and (rarely) spoken contraction of "motherboard"</p> + +<hr> +Node:<a name="moby">moby</a>, Next:<a rel="next" href="#mockingbird">mockingbird</a>, Previous:<a rel="previous" href="#mobo">mobo</a>, Up:<a rel="up" href="#chap13">= M =</a> +<br> + + +<p><b>moby</b> /moh'bee/</p> + +<p>[MIT: seems to have been in use among model railroad fans +years ago. Derived from Melville's "Moby Dick" (some say from +`Moby Pickle'). Now common.] 1. adj. Large, immense, complex, +impressive. "A Saturn V rocket is a truly moby frob." "Some MIT +undergrads pulled off a moby hack at the Harvard-Yale game." (See +<b><a href="#AppendixA">Appendix A</a></b> for discussion.) 2. +n. obs. The maximum address space of a machine (see below). For a +680[234]0 or VAX or most modern 32-bit architectures, it is +4,294,967,296 8-bit bytes (4 gigabytes). 3. A title of address +(never of third-person reference), usually used to show +admiration, respect, and/or friendliness to a competent hacker. +"Greetings, moby Dave. How's that address-book thing for the Mac +going?" 4. adj. In backgammon, doubles on the dice, as in `moby +sixes', `moby ones', etc. Compare this with <b><a href="#bignum">bignum</a></b> (sense 3): double sixes are both bignums +and moby sixes, but moby ones are not bignums (the use of `moby' +to describe double ones is sarcastic). Standard emphatic forms: +`Moby foo', `moby win', `moby loss'. `Foby moo': a spoonerism due +to Richard Greenblatt. 5. The largest available unit of something +which is available in discrete increments. Thus, ordering a "moby +Coke" at the local fast-food joint is not just a request for a +large Coke, it's an explicit request for the largest size they +sell.</p> + +<p>This term entered hackerdom with the Fabritek 256K memory +added to the MIT AI PDP-6 machine, which was considered +unimaginably huge when it was installed in the 1960s (at a time +when a more typical memory size for a timesharing system was 72 +kilobytes). Thus, a moby is classically 256K 36-bit words, the +size of a PDP-6 or PDP-10 moby. Back when address registers were +narrow the term was more generally useful, because when a +computer had virtual memory mapping, it might actually have more +physical memory attached to it than any one program could access +directly. One could then say "This computer has 6 mobies" meaning +that the ratio of physical memory to address space is 6, without +having to say specifically how much memory there actually is. +That in turn implied that the computer could timeshare six +`full-sized' programs without having to swap programs between +memory and disk.</p> + +<p>Nowadays the low cost of processor logic means that address +spaces are usually larger than the most physical memory you can +cram onto a machine, so most systems have much <i>less</i> than +one theoretical `native' moby of <b><a href="#core">core</a></b>. +Also, more modern memory-management techniques (esp. paging) make +the `moby count' less significant. However, there is one series +of widely-used chips for which the term could stand to be revived +-- the Intel 8088 and 80286 with their incredibly <b><a href="#brain-damaged">brain-damaged</a></b> segmented-memory designs. +On these, a `moby' would be the 1-megabyte address span of a +segment/offset pair (by coincidence, a PDP-10 moby was exactly 1 +megabyte of 9-bit bytes).</p> + +<hr> +Node:<a name="mockingbird">mockingbird</a>, Next:<a rel="next" +href="#mod">mod</a>, Previous:<a rel="previous" href="#moby">moby</a>, Up:<a rel="up" href="#chap13">= M =</a> +<br> + + +<p><b>mockingbird</b> n.</p> + +<p>Software that intercepts communications (especially login +transactions) between users and hosts and provides system-like +responses to the users while saving their responses (especially +account IDs and passwords). A special case of <b><a href="#Trojanhorse">Trojan horse</a></b>.</p> + +<hr> +Node:<a name="mod">mod</a>, Next:<a rel="next" href="#mode">mode</a>, Previous:<a rel="previous" href="#mockingbird">mockingbird</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>mod</b> vt.,n.</p> + +<p>[very common] 1. Short for `modify' or `modification'. Very +commonly used -- in fact the full terms are considered markers +that one is being formal. The plural `mods' is used esp. with +reference to bug fixes or minor design changes in hardware or +software, most esp. with respect to <b><a href="#patch">patch</a></b> sets or a <b><a href="#diff">diff</a></b>. +2. Short for <b><a href="#modulo">modulo</a></b> but used +<i>only</i> for its techspeak sense.</p> + +<hr> +Node:<a name="mode">mode</a>, Next:<a rel="next" href="#modebit">mode bit</a>, Previous:<a rel="previous" href="#mod">mod</a>, Up:<a rel="up" href="#chap13">= M =</a> +<br> + + +<p><b>mode</b> n.</p> + +<p>[common] A general state, usually used with an adjective +describing the state. Use of the word `mode' rather than `state' +implies that the state is extended over time, and probably also +that some activity characteristic of that state is being carried +out. "No time to hack; I'm in thesis mode." In its jargon sense, +`mode' is most often attributed to people, though it is sometimes +applied to programs and inanimate objects. In particular, see +<b><a href="#hackmode">hack mode</a></b>, <b><a href="#daymode">day mode</a></b>, <b><a href="#nightmode">night +mode</a></b>, <b><a href="#demomode">demo mode</a></b>, <b><a +href="#fireworksmode">fireworks mode</a></b>, and <b><a href="#yoyomode">yoyo mode</a></b>; also <b><a href="#talkmode">talk mode</a></b>.</p> + +<p>One also often hears the verbs `enable' and `disable' used in +connection with jargon modes. Thus, for example, a sillier way of +saying "I'm going to crash" is "I'm going to enable crash mode +now". One might also hear a request to "disable flame mode, +please".</p> + +<p>In a usage much closer to techspeak, a mode is a special state +that certain user interfaces must pass into in order to perform +certain functions. For example, in order to insert characters +into a document in the Unix editor <code>vi</code>, one must type +the "i" key, which invokes the "Insert" command. The effect of +this command is to put vi into "insert mode", in which typing the +"i" key has a quite different effect (to wit, it inserts an "i" +into the document). One must then hit another special key, "ESC", +in order to leave "insert mode". Nowadays, modeful interfaces are +generally considered <b><a href="#losing">losing</a></b> but +survive in quite a few widely used tools built in less +enlightened times.</p> + +<hr> +Node:<a name="modebit">mode bit</a>, Next:<a rel="next" href="#modulo">modulo</a>, Previous:<a rel="previous" href="#mode">mode</a>, Up:<a rel="up" href="#chap13">= M =</a> +<br> + + +<p><b>mode bit</b> n.</p> + +<p>[common] A <b><a href="#flag">flag</a></b>, usually in +hardware, that selects between two (usually quite different) +modes of operation. The connotations are different from <b><a +href="#flag">flag</a></b> bit in that mode bits are mainly +written during a boot or set-up phase, are seldom explicitly +read, and seldom change over the lifetime of an ordinary program. +The classic example was the EBCDIC-vs.-ASCII bit (#12) of the +Program Status Word of the IBM 360.</p> + +<hr> +Node:<a name="modulo">modulo</a>, Next:<a rel="next" href="#molly-guard">molly-guard</a>, Previous:<a rel="previous" href="#modebit">mode bit</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>modulo</b> /mod'yu-loh/ prep.</p> + +<p>Except for. An overgeneralization of mathematical terminology; +one can consider saying that 4 equals 22 except for the 9s (4 = +22 mod 9). "Well, LISP seems to work okay now, modulo that <b><a +href="#GC">GC</a></b> bug." "I feel fine today modulo a slight +headache."</p> + +<hr> +Node:<a name="molly-guard">molly-guard</a>, Next:<a rel="next" +href="#MongolianHordestechnique">Mongolian Hordes +technique</a>, Previous:<a rel="previous" href="#modulo">modulo</a>, Up:<a rel="up" href="#chap13">= M +=</a> <br> + + +<p><b>molly-guard</b> /mol'ee-gard/ n.</p> + +<p>[University of Illinois] A shield to prevent tripping of some +<b><a href="#BigRedSwitch">Big Red Switch</a></b> by clumsy +or ignorant hands. Originally used of the plexiglass covers +improvised for the BRS on an IBM 4341 after a programmer's +toddler daughter (named Molly) frobbed it twice in one day. Later +generalized to covers over stop/reset switches on disk drives and +networking equipment. In hardware catalogues, you'll see the much +less interesting description "guarded button".</p> + +<hr> +Node:<a name="MongolianHordestechnique">Mongolian Hordes +technique</a>, Next:<a rel="next" href="#monkeyup">monkey +up</a>, Previous:<a rel="previous" href="#molly-guard">molly-guard</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>Mongolian Hordes technique</b> n.</p> + +<p>[poss. from the Sixties counterculture expression `Mongolian +clusterfuck' for a public orgy] Development by <b><a href="#gangbang">gang bang</a></b>. Implies that large numbers of +inexperienced programmers are being put on a job better performed +by a few skilled ones (but see <b><a href="#bazaar">bazaar</a></b>). Also called `Chinese Army technique'; +see also <b><a href="#BrookssLaw">Brooks's Law</a></b>.</p> + +<hr> +Node:<a name="monkeyup">monkey up</a>, Next:<a rel="next" +href="#monkeyscratch">monkey scratch</a>, Previous:<a rel="previous" href="#MongolianHordestechnique">Mongolian +Hordes technique</a>, Up:<a rel="up" href="#chap13">= M +=</a> <br> + + +<p><b>monkey up</b> vt.</p> + +<p>To hack together hardware for a particular task, especially a +one-shot job. Connotes an extremely <b><a href="#crufty">crufty</a></b> and consciously temporary solution. +Compare <b><a href="#hackup">hack up</a></b>, <b><a href="#klugeup">kluge up</a></b>, <b><a href="#crufttogether">cruft together</a></b>.</p> + +<hr> +Node:<a name="monkeyscratch">monkey scratch</a>, Next:<a rel="next" href="#monstrosity">monstrosity</a>, Previous:<a rel="previous" href="#monkeyup">monkey up</a>, Up:<a rel="up" +href="#chap13">= M =</a> <br> + + +<p><b>monkey, scratch</b> n.</p> + +<p>See <b><a href="#scratchmonkey">scratch monkey</a></b>.</p> + +<hr> +Node:<a name="monstrosity">monstrosity</a>, Next:<a rel="next" +href="#monty">monty</a>, Previous:<a rel="previous" href="#monkeyscratch">monkey scratch</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>monstrosity</b></p> + +<p>1. n. A ridiculously <b><a href="#elephantine">elephantine</a></b> program or system, esp. one +that is buggy or only marginally functional. 2. adj. The quality +of being monstrous (see `Overgeneralization' in the discussion of +jargonification). See also <b><a href="#baroque">baroque</a></b>.</p> + +<hr> +Node:<a name="monty">monty</a>, Next:<a rel="next" href="#Moof">Moof</a>, Previous:<a rel="previous" href="#monstrosity">monstrosity</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>monty</b> /mon'tee/ n.</p> + +<p>1. [US Geological Survey] A program with a ludicrously complex +user interface written to perform extremely trivial tasks. An +example would be a menu-driven, button clicking, pulldown, pop-up +windows program for listing directories. The original monty was +an infamous weather-reporting program, Monty the Amazing Weather +Man, written at the USGS. Monty had a widget-packed X-window +interface with over 200 buttons; and all monty actually +<i>did</i> was <b><a href="#FTP">FTP</a></b> files off the +network. 2. [Great Britain; commonly capitalized as `Monty' or as +`the Full Monty'] 16 megabytes of memory, when fitted to an +IBM-PC or compatible. A standard PC-compatible using the AT- or +ISA-bus with a normal BIOS cannot access more than 16 megabytes +of RAM. Generally used of a PC, Unix workstation, etc. to mean +`fully populated with' memory, disk-space or some other desirable +resource. This usage may be related to a TV commercial for Del +Monte fruit juice, in which one of the characters insisted on +"the full Del Monte"; but see the World Wide Words article <a +href="http://clever.net/quinion/words/articles/monty.htm">"The +Full Monty"</a> for discussion of the rather complex etymology +that may lie behind this. Compare American <b><a href="#moby">moby</a></b>.</p> + +<hr> +Node:<a name="Moof">Moof</a>, Next:<a rel="next" href="#MooresLaw">Moore's Law</a>, Previous:<a rel="previous" +href="#monty">monty</a>, Up:<a rel="up" href="#chap13">= M +=</a> <br> + + +<p><b>Moof</b> /moof/</p> + +<p>[Macintosh users] 1. n. The call of a semi-legendary creature, +properly called the <b><a href="#dogcow">dogcow</a></b>. (Some +previous versions of this entry claimed, incorrectly, that Moof +was the name of the <i>creature</i>.) 2. adj. Used to flag +software that's a hack, something untested and on the edge. On +one Apple CD-ROM, certain folders such as "Tools & Apps +(Moof!)" and "Development Platforms (Moof!)", are so marked to +indicate that they contain software not fully tested or +sanctioned by the powers that be. When you open these folders you +cross the boundary into hackerland. 3. v. On the Microsoft +Network, the term `moof' has gained popularity as a verb meaning +`to be suddenly disconnected by the system'. One might say "I got +moofed".</p> + +<hr> +Node:<a name="MooresLaw">Moore's Law</a>, Next:<a rel="next" +href="#moosecall">moose call</a>, Previous:<a rel="previous" +href="#Moof">Moof</a>, Up:<a rel="up" href="#chap13">= M +=</a> <br> + + +<p><b>Moore's Law</b> /morz law/ prov.</p> + +<p>The observation that the logic density of silicon integrated +circuits has closely followed the curve (bits per square inch) = +2^(t - 1962) where t is time in years; that is, the amount of +information storable on a given amount of silicon has roughly +doubled every year since the technology was invented. This +relation, first uttered in 1964 by semiconductor engineer Gordon +Moore (who co-founded Intel four years later) held until the late +1970s, at which point the doubling period slowed to 18 months. +The doubling period remained at that value through time of +writing (late 1999). Moore's Law is apparently self-fulfilling. +The implication is that somebody, somewhere is going to be able +to build a better chip than you if you rest on your laurels, so +you'd better start pushing hard on the problem. See also <b><a +href="#ParkinsonsLawofData">Parkinson's Law of +Data</a></b> and <b><a href="#GatessLaw">Gates's +Law</a></b>.</p> + +<hr> +Node:<a name="moosecall">moose call</a>, Next:<a rel="next" +href="#moria">moria</a>, Previous:<a rel="previous" href="#MooresLaw">Moore's Law</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>moose call</b> n.</p> + +<p>See <b><a href="#whalesong">whalesong</a></b>.</p> + +<hr> +Node:<a name="moria">moria</a>, Next:<a rel="next" href="#MOTAS">MOTAS</a>, Previous:<a rel="previous" href="#moosecall">moose call</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>moria</b> /mor'ee-*/ n.</p> + +<p>Like <b><a href="#nethack">nethack</a></b> and <b><a href="#rogue">rogue</a></b>, one of the large PD +Dungeons-and-Dragons-like simulation games, available for a wide +range of machines and operating systems. The name is from +Tolkien's Mines of Moria; compare <b><a href="#elderdays">elder days</a></b>, <b><a href="#elvish">elvish</a></b>. The game is extremely addictive and a +major consumer of time better used for hacking. See also <b><a +href="#nethack">nethack</a></b>, <b><a href="#rogue">rogue</a></b>, <b><a href="#Angband">Angband</a></b>.</p> + +<hr> +Node:<a name="MOTAS">MOTAS</a>, Next:<a rel="next" href="#MOTOS">MOTOS</a>, Previous:<a rel="previous" href="#moria">moria</a>, Up:<a rel="up" href="#chap13">= M +=</a> <br> + + +<p><b>MOTAS</b> /moh-tahz/ n.</p> + +<p>[Usenet: Member Of The Appropriate Sex, after <b><a href="#MOTOS">MOTOS</a></b> and <b><a href="#MOTSS">MOTSS</a></b>] A +potential or (less often) actual sex partner. See also <b><a +href="#SO">SO</a></b>.</p> + +<hr> +Node:<a name="MOTOS">MOTOS</a>, Next:<a rel="next" href="#MOTSS">MOTSS</a>, Previous:<a rel="previous" href="#MOTAS">MOTAS</a>, Up:<a rel="up" href="#chap13">= M +=</a> <br> + + +<p><b>MOTOS</b> /moh-tohs/ n.</p> + +<p>[acronym from the 1970 U.S. census forms via Usenet: Member Of +The Opposite Sex] A potential or (less often) actual sex partner. +See <b><a href="#MOTAS">MOTAS</a></b>, <b><a href="#MOTSS">MOTSS</a></b>, <b><a href="#SO">SO</a></b>. Less common +than MOTSS or <b><a href="#MOTAS">MOTAS</a></b>, which has +largely displaced it.</p> + +<hr> +Node:<a name="MOTSS">MOTSS</a>, Next:<a rel="next" href="#mouseahead">mouse ahead</a>, Previous:<a rel="previous" +href="#MOTOS">MOTOS</a>, Up:<a rel="up" href="#chap13">= M +=</a> <br> + + +<p><b>MOTSS</b> /mots/ or /M-O-T-S-S/ n.</p> + +<p>[from the 1970 U.S. census forms via Usenet] Member Of The +Same Sex, esp. one considered as a possible sexual partner. The +gay-issues newsgroup on Usenet is called <i>soc.motss</i>. See +<b><a href="#MOTOS">MOTOS</a></b> and <b><a href="#MOTAS">MOTAS</a></b>, which derive from it. See also <b><a +href="#SO">SO</a></b>.</p> + +<hr> +Node:<a name="mouseahead">mouse ahead</a>, Next:<a rel="next" +href="#mousearound">mouse around</a>, Previous:<a rel="previous" href="#MOTSS">MOTSS</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>mouse ahead</b> vi.</p> + +<p>Point-and-click analog of `type ahead'. To manipulate a +computer's pointing device (almost always a mouse in this usage, +but not necessarily) and its selection or command buttons before +a computer program is ready to accept such input, in anticipation +of the program accepting the input. Handling this properly is +rare, but it can help make a <b><a href="#WIMPenvironment">WIMP environment</a></b> much more usable, +assuming the users are familiar with the behavior of the user +interface.</p> + +<hr> +Node:<a name="mousearound">mouse around</a>, Next:<a rel="next" href="#mousebelt">mouse belt</a>, Previous:<a rel="previous" href="#mouseahead">mouse ahead</a>, Up:<a rel="up" +href="#chap13">= M =</a> <br> + + +<p><b>mouse around</b> vi.</p> + +<p>To explore public portions of a large system, esp. a network +such as Internet via <b><a href="#FTP">FTP</a></b> or <b><a href="#TELNET">TELNET</a></b>, looking for interesting stuff to <b><a +href="#snarf">snarf</a></b>.</p> + +<hr> +Node:<a name="mousebelt">mouse belt</a>, Next:<a rel="next" +href="#mousedroppings">mouse droppings</a>, Previous:<a rel="previous" href="#mousearound">mouse around</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>mouse belt</b> n.</p> + +<p>See <b><a href="#ratbelt">rat belt</a></b>.</p> + +<hr> +Node:<a name="mousedroppings">mouse droppings</a>, Next:<a +rel="next" href="#mouseelbow">mouse elbow</a>, Previous:<a +rel="previous" href="#mousebelt">mouse belt</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>mouse droppings</b> n.</p> + +<p>[MS-DOS] Pixels (usually single) that are not properly +restored when the mouse pointer moves away from a particular +location on the screen, producing the appearance that the mouse +pointer has left droppings behind. The major causes for this +problem are programs that write to the screen memory +corresponding to the mouse pointer's current location without +hiding the mouse pointer first, and mouse drivers that do not +quite support the graphics mode in use.</p> + +<hr> +Node:<a name="mouseelbow">mouse elbow</a>, Next:<a rel="next" +href="#mouso">mouso</a>, Previous:<a rel="previous" href="#mousedroppings">mouse droppings</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>mouse elbow</b> n.</p> + +<p>A tennis-elbow-like fatigue syndrome resulting from excessive +use of a <b><a href="#WIMPenvironment">WIMP +environment</a></b>. Similarly, `mouse shoulder'; GLS reports +that he used to get this a lot before he taught himself to be +ambimoustrous.</p> + +<hr> +Node:<a name="mouso">mouso</a>, Next:<a rel="next" href="#MS-DOS">MS-DOS</a>, Previous:<a rel="previous" href="#mouseelbow">mouse elbow</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>mouso</b> /mow'soh/ n.</p> + +<p>[by analogy with `typo'] An error in mouse usage resulting in +an inappropriate selection or graphic garbage on the screen. +Compare <b><a href="#thinko">thinko</a></b>, <b><a href="#braino">braino</a></b>.</p> + +<hr> +Node:<a name="MS-DOS">MS-DOS</a>, Next:<a rel="next" href="#mu">mu</a>, Previous:<a rel="previous" href="#mouso">mouso</a>, +Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>MS-DOS</b> /M-S-dos/ n.</p> + +<p>[MicroSoft Disk Operating System] A <b><a href="#clone">clone</a></b> of <b><a href="#CPM">CP/M</a></b> for +the 8088 crufted together in 6 weeks by hacker Tim Paterson at +Seattle Computer Products, who called the original QDOS (Quick +and Dirty Operating System) and is said to have regretted it ever +since. Microsoft licensed QDOS order to have something to demo +for IBM on time, and the rest is history. Numerous features, +including vaguely Unix-like but rather broken support for +subdirectories, I/O redirection, and pipelines, were hacked into +Microsoft's 2.0 and subsequent versions; as a result, there are +two or more incompatible versions of many system calls, and +MS-DOS programmers can never agree on basic things like what +character to use as an option switch or whether to be +case-sensitive. The resulting appalling mess is now the +highest-unit-volume OS in history. Often known simply as DOS, +which annoys people familiar with other similarly abbreviated +operating systems (the name goes back to the mid-1960s, when it +was attached to IBM's first disk operating system for the 360). +The name further annoys those who know what the term <b><a href="#operatingsystem">operating system</a></b> does (or ought to) +connote; DOS is more properly a set of relatively simple +interrupt services. Some people like to pronounce DOS like +"dose", as in "I don't work on dose, man!", or to compare it to a +dose of brain-damaging drugs (a slogan button in wide circulation +among hackers exhorts: "MS-DOS: Just say No!"). See <b><a href="#mess-dos">mess-dos</a></b>, <b><a href="#ill-behaved">ill-behaved</a></b>.</p> + +<hr> +Node:<a name="mu">mu</a>, Next:<a rel="next" href="#MUD">MUD</a>, +Previous:<a rel="previous" href="#MS-DOS">MS-DOS</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>mu</b> /moo/</p> + +<p>The correct answer to the classic trick question "Have you +stopped beating your wife yet?". Assuming that you have no wife +or you have never beaten your wife, the answer "yes" is wrong +because it implies that you used to beat your wife and then +stopped, but "no" is worse because it suggests that you have one +and are still beating her. According to various Discordians and +Douglas Hofstadter the correct answer is usually "mu", a Japanese +word alleged to mean "Your question cannot be answered because it +depends on incorrect assumptions". Hackers tend to be sensitive +to logical inadequacies in language, and many have adopted this +suggestion with enthusiasm. The word `mu' is actually from +Chinese, meaning `nothing'; it is used in mainstream Japanese in +that sense. Native speakers do not recognize the Discordian +question-denying use, which almost certainly derives from +overgeneralization of the answer in the following well-known +Rinzai Zen <b><a href="#koan">koan</a></b>:</p> + +<blockquote>A monk asked Joshu, "Does a dog have the Buddha +nature?" Joshu retorted, "Mu!"</blockquote> + +<p>See also <b><a href="#hastheXnature">has the X +nature</a></b>, <b><a href="#SomeAIKoans">Some AI +Koans</a></b>, and Douglas Hofstadter's "Gödel, Escher, +Bach: An Eternal Golden Braid" (pointer in the <b><a href="#Bibliography">Bibliography</a></b> in Appendix C.</p> + +<hr> +Node:<a name="MUD">MUD</a>, Next:<a rel="next" href="#muddie">muddie</a>, Previous:<a rel="previous" href="#mu">mu</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>MUD</b> /muhd/ n.</p> + +<p>[acronym, Multi-User Dungeon; alt. Multi-User Dimension] 1. A +class of <b><a href="#virtualreality">virtual reality</a></b> +experiments accessible via the Internet. These are real-time chat +forums with structure; they have multiple `locations' like an +adventure game, and may include combat, traps, puzzles, magic, a +simple economic system, and the capability for characters to +build more structure onto the database that represents the +existing world. 2. vi. To play a MUD. The acronym MUD is often +lowercased and/or verbed; thus, one may speak of `going mudding', +etc.</p> + +<p>Historically, MUDs (and their more recent progeny with names +of MU- form) derive from a hack by Richard Bartle and Roy +Trubshaw on the University of Essex's DEC-10 in the early 1980s; +descendants of that game still exist today and are sometimes +generically called <i>BartleMUD</i>s. There is a widespread myth +(repeated, unfortunately, by earlier versions of this lexicon) +that the name MUD was trademarked to the commercial MUD run by +Bartle on British Telecom (the motto: "You haven't <i>lived</i> +'til you've <i>died</i> on MUD!"); however, this is false -- +Richard Bartle explicitly placed `MUD' in the public domain in +1985. BT was upset at this, as they had already printed trademark +claims on some maps and posters, which were released and created +the myth.</p> + +<p>Students on the European academic networks quickly improved on +the MUD concept, spawning several new MUDs (VAXMUD, AberMUD, +LPMUD). Many of these had associated bulletin-board systems for +social interaction. Because these had an image as `research' they +often survived administrative hostility to BBSs in general. This, +together with the fact that Usenet feeds were often spotty and +difficult to get in the U.K., made the MUDs major foci of hackish +social interaction there.</p> + +<p>AberMUD and other variants crossed the Atlantic around 1988 +and quickly gained popularity in the U.S.; they became nuclei for +large hacker communities with only loose ties to traditional +hackerdom (some observers see parallels with the growth of Usenet +in the early 1980s). The second wave of MUDs (TinyMUD and +variants) tended to emphasize social interaction, puzzles, and +cooperative world-building as opposed to combat and competition +(in writing, these social MUDs are sometimes referred to as +`MU*', with `MUD' implicitly reserved for the more game-oriented +ones). By 1991, over 50% of MUD sites were of a third major +variety, LPMUD, which synthesizes the combat/puzzle aspects of +AberMUD and older systems with the extensibility of TinyMud. In +1996 the cutting edge of the technology is Pavel Curtis's MOO, +even more extensible using a built-in object-oriented language. +The trend toward greater programmability and flexibility will +doubtless continue.</p> + +<p>The state of the art in MUD design is still moving very +rapidly, with new simulation designs appearing (seemingly) every +month. Around 1991 there was an unsuccessful movement to +deprecate the term <b><a href="#MUD">MUD</a></b> itself, as newer +designs exhibit an exploding variety of names corresponding to +the different simulation styles being explored. It survived. See +also <b><a href="#bonkfoif">bonk/oif</a></b>, <b><a href="#FOD">FOD</a></b>, <b><a href="#link-dead">link-dead</a></b>, +<b><a href="#mudhead">mudhead</a></b>, <b><a href="#talkmode">talk mode</a></b>.</p> + +<hr> +Node:<a name="muddie">muddie</a>, Next:<a rel="next" href="#mudhead">mudhead</a>, Previous:<a rel="previous" href="#MUD">MUD</a>, Up:<a rel="up" href="#chap13">= M =</a> +<br> + + +<p><b>muddie</b> n.</p> + +<p>Syn. <b><a href="#mudhead">mudhead</a></b>. More common in +Great Britain, possibly because system administrators there like +to mutter "bloody muddies" when annoyed at the species.</p> + +<hr> +Node:<a name="mudhead">mudhead</a>, Next:<a rel="next" href="#muggle">muggle</a>, Previous:<a rel="previous" href="#muddie">muddie</a>, Up:<a rel="up" href="#chap13">= M +=</a> <br> + + +<p><b>mudhead</b> n.</p> + +<p>Commonly used to refer to a <b><a href="#MUD">MUD</a></b> +player who eats, sleeps, and breathes MUD. Mudheads have been +known to fail their degrees, drop out, etc., with the +consolation, however, that they made wizard level. When +encountered in person, on a MUD, or in a chat system, all a +mudhead will talk about is three topics: the tactic, character, +or wizard that is supposedly always unfairly stopping him/her +from becoming a wizard or beating a favorite MUD; why the +specific game he/she has experience with is so much better than +any other; and the MUD he or she is writing or going to write +because his/her design ideas are so much better than in any +existing MUD. See also <b><a href="#wannabee">wannabee</a></b>.</p> + +<p>To the anthropologically literate, this term may recall the +Zuni/Hopi legend of the mudheads or `koyemshi', mythical +half-formed children of an unnatural union. Figures representing +them act as clowns in Zuni sacred ceremonies. Others may recall +the `High School Madness' sequence from the Firesign Theatre +album "Don't Crush That Dwarf, Hand Me the Pliers", in which +there is a character named "Mudhead".</p> + +<hr> +Node:<a name="muggle">muggle</a>, Next:<a rel="next" href="#multician">multician</a>, Previous:<a rel="previous" href="#mudhead">mudhead</a>, Up:<a rel="up" href="#chap13">= M +=</a> <br> + + +<p><b>muggle</b></p> + +<p>[from J.K. Rowling's `Harry Potter' books, 1998] A non-<b><a +href="#wizard">wizard</a></b>. Not as disparaging as <b><a href="#luser">luser</a></b>; implies vague pity rather than contempt. +In the universe of Rowling's enormously (and deservedly) popular +children's series, muggles and wizards inhabit the same modern +world, but each group is ignorant of the commonplaces of the +others' existence - most muggles are unaware that wizards exist, +and wizards (used to magical ways of doing everything) are +perplexed and fascinated by muggle artifacts.</p> + +<p>In retrospect it seems completely inevitable that hackers +would adopt this metaphor, and in hacker usage it readily forms +compounds such as `muggle-friendly'. Compare <b><a href="#luser">luser</a></b>, <b><a href="#mundane">mundane</a></b>.</p> + +<hr> +Node:<a name="multician">multician</a>, Next:<a rel="next" href="#Multics">Multics</a>, Previous:<a rel="previous" href="#muggle">muggle</a>, Up:<a rel="up" href="#chap13">= M +=</a> <br> + + +<p><b>multician</b> /muhl-ti'shn/ n.</p> + +<p>[coined at Honeywell, ca. 1970] Competent user of <b><a href="#Multics">Multics</a></b>. Perhaps oddly, no one has ever +promoted the analogous `Unician'.</p> + +<hr> +Node:<a name="Multics">Multics</a>, Next:<a rel="next" href="#multitask">multitask</a>, Previous:<a rel="previous" href="#multician">multician</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>Multics</b> /muhl'tiks/ n.</p> + +<p>[from "MULTiplexed Information and Computing Service"] An +early time-sharing <b><a href="#operatingsystem">operating +system</a></b> co-designed by a consortium including MIT, GE, and +Bell Laboratories as a successor to <b><a href="#CTSS">CTSS</a></b>. The design was first presented in 1965, +planned for operation in 1967, first operational in 1969, and +took several more years to achieve respectable performance and +stability.</p> + +<p>Multics was very innovative for its time -- among other +things, it provided a hierarchical file system with access +control on individual files and introduced the idea of treating +all devices uniformly as special files. It was also the first OS +to run on a symmetric multiprocessor, and the only +general-purpose system to be awarded a B2 security rating by the +NSA (see <b><a href="#OrangeBook">Orange Book</a></b>).</p> + +<p>Bell Labs left the development effort in 1969 after judging +that <b><a href="#second-systemeffect">second-system +effect</a></b> had bloated Multics to the point of practical +unusability. Honeywell commercialized Multics in 1972 after +buying out GE's computer group, but it was never very successful: +at its peak in the 1980s, there were between 75 and 100 Multics +sites, each a multi-million dollar mainframe.</p> + +<p>One of the former Multics developers from Bell Labs was Ken +Thompson, and <b><a href="#Unix">Unix</a></b> deliberately +carried through and extended many of Multics' design ideas; +indeed, Thompson described the very name `Unix' as `a weak pun on +Multics'. For this and other reasons, aspects of the Multics +design remain a topic of occasional debate among hackers. See +also <b><a href="#brain-damaged">brain-damaged</a></b> and <b><a +href="#GCOS">GCOS</a></b>.</p> + +<p>MIT ended its development association with Multics in 1977. +Honeywell sold its computer business to Bull in the mid 80s, and +development on Multics was stopped in 1988. Four Multics sites +were known to be still in use as late as 1998. There is a Multics +page at http://www.stratus.com/pub/vos/multics/tvv/multics.html.</p> + +<hr> +Node:<a name="multitask">multitask</a>, Next:<a rel="next" href="#mumblage">mumblage</a>, Previous:<a rel="previous" href="#Multics">Multics</a>, Up:<a rel="up" href="#chap13">= M +=</a> <br> + + +<p><b>multitask</b> n.</p> + +<p>Often used of humans in the same meaning it has for computers, +to describe a person doing several things at once (but see <b><a +href="#thrash">thrash</a></b>). The term `multiplex', from +communications technology (meaning to handle more than one +channel at the same time), is used similarly.</p> + +<hr> +Node:<a name="mumblage">mumblage</a>, Next:<a rel="next" href="#mumble">mumble</a>, Previous:<a rel="previous" href="#multitask">multitask</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>mumblage</b> /muhm'bl*j/ n.</p> + +<p>The topic of one's mumbling (see <b><a href="#mumble">mumble</a></b>). "All that mumblage" is used like "all +that stuff" when it is not quite clear how the subject of +discussion works, or like "all that crap" when `mumble' is being +used as an implicit replacement for pejoratives.</p> + +<hr> +Node:<a name="mumble">mumble</a>, Next:<a rel="next" href="#munch">munch</a>, Previous:<a rel="previous" href="#mumblage">mumblage</a>, Up:<a rel="up" href="#chap13">= +M =</a> <br> + + +<p><b>mumble</b> interj.</p> + +<p>1. Said when the correct response is too complicated to +enunciate, or the speaker has not thought it out. Often prefaces +a longer answer, or indicates a general reluctance to get into a +long discussion. "Don't you think that we could improve LISP +performance by using a hybrid reference-count transaction garbage +collector, if the cache is big enough and there are some extra +cache bits for the microcode to use?" "Well, mumble +<small>...</small> I'll have to think about it." 2. [MIT] +Expression of not-quite-articulated agreement, often used as an +informal vote of consensus in a meeting: "So, shall we dike out +the COBOL emulation?" "Mumble!" 3. Sometimes used as an +expression of disagreement (distinguished from sense 2 by tone of +voice and other cues). "I think we should buy a <b><a href="#VAX">VAX</a></b>." "Mumble!" Common variant: `mumble frotz' +(see <b><a href="#frotz">frotz</a></b>; interestingly, one does +not say `mumble frobnitz' even though `frotz' is short for +`frobnitz'). 4. Yet another <b><a href="#metasyntacticvariable">metasyntactic variable</a></b>, like +<b><a href="#foo">foo</a></b>. 5. When used as a question +("Mumble?") means "I didn't understand you". 6. Sometimes used in +`public' contexts on-line as a placefiller for things one is +barred from giving details about. For example, a poster with +pre-released hardware in his machine might say "Yup, my machine +now has an extra 16M of memory, thanks to the card I'm testing +for Mumbleco." 7. A conversational wild card used to designate +something one doesn't want to bother spelling out, but which can +be <b><a href="#glark">glark</a></b>ed from context. Compare +<b><a href="#blurgle">blurgle</a></b>. 8. [XEROX PARC] A +colloquialism used to suggest that further discussion would be +fruitless.</p> + +<hr> +Node:<a name="munch">munch</a>, Next:<a rel="next" href="#munching">munching</a>, Previous:<a rel="previous" href="#mumble">mumble</a>, Up:<a rel="up" href="#chap13">= M +=</a> <br> + + +<p><b>munch</b> vt.</p> + +<p>[often confused with <b><a href="#mung">mung</a></b>, q.v.] To +transform information in a serial fashion, often requiring large +amounts of computation. To trace down a data structure. Related +to <b><a href="#crunch">crunch</a></b> and nearly synonymous with +<b><a href="#grovel">grovel</a></b>, but connotes less pain.</p> + +<hr> +Node:<a name="munching">munching</a>, Next:<a rel="next" href="#munchingsquares">munching squares</a>, Previous:<a rel="previous" href="#munch">munch</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>munching</b> n.</p> + +<p>Exploration of security holes of someone else's computer for +thrills, notoriety, or to annoy the system manager. Compare <b><a +href="#cracker">cracker</a></b>. See also <b><a href="#hackedoff">hacked off</a></b>.</p> + +<hr> +Node:<a name="munchingsquares">munching squares</a>, Next:<a +rel="next" href="#munchkin">munchkin</a>, Previous:<a rel="previous" href="#munching">munching</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>munching squares</b> n.</p> + +<p>A <b><a href="#displayhack">display hack</a></b> dating +back to the PDP-1 (ca. 1962, reportedly discovered by Jackson +Wright), which employs a trivial computation (repeatedly plotting +the graph Y = X XOR T for successive values of T -- see <b><a +href="#HAKMEM">HAKMEM</a></b> items 146-148) to produce an +impressive display of moving and growing squares that devour the +screen. The initial value of T is treated as a parameter, which, +when well-chosen, can produce amazing effects. Some of these, +later (re)discovered on the LISP machine, have been christened +`munching triangles' (try AND for XOR and toggling points instead +of plotting them), `munching w's', and `munching mazes'. More +generally, suppose a graphics program produces an impressive and +ever-changing display of some basic form, foo, on a display +terminal, and does it using a relatively simple program; then the +program (or the resulting display) is likely to be referred to as +`munching foos'. [This is a good example of the use of the word +<b><a href="#foo">foo</a></b> as a <b><a href="#metasyntacticvariable">metasyntactic variable</a></b>.]</p> + +<hr> +Node:<a name="munchkin">munchkin</a>, Next:<a rel="next" href="#mundane">mundane</a>, Previous:<a rel="previous" href="#munchingsquares">munching squares</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>munchkin</b> /muhnch'kin/ n.</p> + +<p>[from the squeaky-voiced little people in L. Frank Baum's "The +Wizard of Oz"] A teenage-or-younger micro enthusiast hacking +BASIC or something else equally constricted. A term of mild +derision -- munchkins are annoying but some grow up to be hackers +after passing through a <b><a href="#larvalstage">larval +stage</a></b>. The term <b><a href="#urchin">urchin</a></b> is +also used. See also <b><a href="#wannabee">wannabee</a></b>, +<b><a href="#bittybox">bitty box</a></b>.</p> + +<hr> +Node:<a name="mundane">mundane</a>, Next:<a rel="next" href="#mung">mung</a>, Previous:<a rel="previous" href="#munchkin">munchkin</a>, Up:<a rel="up" href="#chap13">= +M =</a> <br> + + +<p><b>mundane</b> n.</p> + +<p>[from SF fandom] 1. A person who is not in science fiction +fandom. 2. A person who is not in the computer industry. In this +sense, most often an adjectival modifier as in "in my mundane +life<small>...</small>." See also <b><a href="#RealWorld">Real +World</a></b>, <b><a href="#muggle">muggle</a></b>.</p> + +<hr> +Node:<a name="mung">mung</a>, Next:<a rel="next" href="#munge">munge</a>, Previous:<a rel="previous" href="#mundane">mundane</a>, Up:<a rel="up" href="#chap13">= M +=</a> <br> + + +<p><b>mung</b> /muhng/ vt.</p> + +<p>[in 1960 at MIT, `Mash Until No Good'; sometime after that the +derivation from the <b><a href="#recursiveacronym">recursive +acronym</a></b> `Mung Until No Good' became standard; but see +<b><a href="#munge">munge</a></b>] 1. To make changes to a file, +esp. large-scale and irrevocable changes. See <b><a href="#BLT">BLT</a></b>. 2. To destroy, usually accidentally, +occasionally maliciously. The system only mungs things +maliciously; this is a consequence of <b><a href="#FinaglesLaw">Finagle's Law</a></b>. See <b><a href="#scribble">scribble</a></b>, <b><a href="#mangle">mangle</a></b>, <b><a href="#trash">trash</a></b>, +<b><a href="#nuke">nuke</a></b>. Reports from <b><a href="#Usenet">Usenet</a></b> suggest that the pronunciation /muhnj/ +is now usual in speech, but the spelling `mung' is still common +in program comments (compare the widespread confusion over the +proper spelling of <b><a href="#kluge">kluge</a></b>). 3. The +kind of beans the sprouts of which are used in Chinese food. +(That's their real name! Mung beans! Really!)</p> + +<p>Like many early hacker terms, this one seems to have +originated at <b><a href="#TMRC">TMRC</a></b>; it was already in +use there in 1958. Peter Samson (compiler of the original TMRC +lexicon) thinks it may originally have been onomatopoeic for the +sound of a relay spring (contact) being twanged. However, it is +known that during the World Wars, `mung' was U.S. army slang for +the ersatz creamed chipped beef better known as `SOS', and it +seems quite likely that the word in fact goes back to +Scots-dialect <b><a href="#munge">munge</a></b>.</p> + +<hr> +Node:<a name="munge">munge</a>, Next:<a rel="next" href="#MurphysLaw">Murphy's Law</a>, Previous:<a rel="previous" +href="#mung">mung</a>, Up:<a rel="up" href="#chap13">= M +=</a> <br> + + +<p><b>munge</b> /muhnj/ vt.</p> + +<p>1. [derogatory] To imperfectly transform information. 2. A +comprehensive rewrite of a routine, data structure or the whole +program. 3. To modify data in some way the speaker doesn't need +to go into right now or cannot describe succinctly (compare <b><a +href="#mumble">mumble</a></b>). 4. To add <b><a href="#spamblock">spamblock</a></b> to an email address.</p> + +<p>This term is often confused with <b><a href="#mung">mung</a></b>, which probably was derived from it. +However, it also appears the word `munge' was in common use in +Scotland in the 1940s, and in Yorkshire in the 1950s, as a verb, +meaning to munch up into a masticated mess, and as a noun, +meaning the result of munging something up (the parallel with the +<b><a href="#kluge">kluge</a></b>/<b><a href="#kludge">kludge</a></b> pair is amusing). The OED reports +`munge' as an archaic verb nmeaning "to wipe (a person's +nose)".</p> + +<hr> +Node:<a name="MurphysLaw">Murphy's Law</a>, Next:<a rel="next" href="#music">music</a>, Previous:<a rel="previous" href="#munge">munge</a>, Up:<a rel="up" href="#chap13">= M +=</a> <br> + + +<p><b>Murphy's Law</b> prov.</p> + +<p>The correct, <i>original</i> Murphy's Law reads: "If there +are two or more ways to do something, and one of those ways can +result in a catastrophe, then someone will do it." This is a +principle of defensive design, cited here because it is usually +given in mutant forms less descriptive of the challenges of +design for <b><a href="#luser">luser</a></b>s. For example, you +don't make a two-pin plug symmetrical and then label it `THIS WAY +UP'; if it matters which way it is plugged in, then you make the +design asymmetrical (see also the anecdote under <b><a href="#magicsmoke">magic smoke</a></b>).</p> + +<p>Edward A. Murphy, Jr. was one of the engineers on the +rocket-sled experiments that were done by the U.S. Air Force in +1949 to test human acceleration tolerances (USAF project MX981). +One experiment involved a set of 16 accelerometers mounted to +different parts of the subject's body. There were two ways each +sensor could be glued to its mount, and somebody methodically +installed all 16 the wrong way around. Murphy then made the +original form of his pronouncement, which the test subject (Major +John Paul Stapp) quoted at a news conference a few days +later.</p> + +<p>Within months `Murphy's Law' had spread to various technical +cultures connected to aerospace engineering. Before too many +years had gone by variants had passed into the popular +imagination, changing as they went. Most of these are variants on +"Anything that can go wrong, will"; this is correctly referred to +as <b><a href="#FinaglesLaw">Finagle's Law</a></b>. The +memetic drift apparent in these mutants clearly demonstrates +Murphy's Law acting on itself!</p> + +<hr> +Node:<a name="music">music</a>, Next:<a rel="next" href="#mutter">mutter</a>, Previous:<a rel="previous" href="#MurphysLaw">Murphy's Law</a>, Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>music</b> n.</p> + +<p>A common extracurricular interest of hackers (compare <b><a +href="#science-fictionfandom">science-fiction fandom</a></b>, +<b><a href="#orientalfood">oriental food</a></b>; see also +<b><a href="#filk">filk</a></b>). Hackish folklore has long +claimed that musical and programming abilities are closely +related, and there has been at least one large-scale statistical +study that supports this. Hackers, as a rule, like music and +often develop musical appreciation in unusual and interesting +directions. Folk music is very big in hacker circles; so is +electronic music, and the sort of elaborate instrumental +jazz/rock that used to be called `progressive' and isn't recorded +much any more. The hacker's musical range tends to be wide; many +can listen with equal appreciation to (say) Talking Heads, Yes, +Gentle Giant, Pat Metheny, Scott Joplin, Tangerine Dream, Dream +Theater, King Sunny Ade, The Pretenders, Screaming Trees, or the +Brandenburg Concerti. It is also apparently true that hackerdom +includes a much higher concentration of talented amateur +musicians than one would expect from a similar-sized control +group of <b><a href="#mundane">mundane</a></b> types.</p> + +<hr> +Node:<a name="mutter">mutter</a>, Next:<a rel="next" href="#N">N</a>, Previous:<a rel="previous" href="#music">music</a>, +Up:<a rel="up" href="#chap13">= M =</a> <br> + + +<p><b>mutter</b> vt.</p> + +<p>To quietly enter a command not meant for the ears, eyes, or +fingers of ordinary mortals. Often used in `mutter an <b><a href="#incantation">incantation</a></b>'. See also <b><a href="#wizard">wizard</a></b>.</p> + +<hr> +Node:<a name="chap14">= N =</a>, Next:<a rel="next" href="#chap15">= O =</a>, Previous:<a rel="previous" href="#chap13">= M =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= N =</h2> + +<ul> +<li><a href="#N">N</a>:</li> + +<li><a href="#nadger">nadger</a>:</li> + +<li><a href="#nagware">nagware</a>:</li> + +<li><a href="#nailedtothewall">nailed to the wall</a>:</li> + +<li><a href="#nailingjelly">nailing jelly</a>:</li> + +<li><a href="#naive">naive</a>:</li> + +<li><a href="#naiveuser">naive user</a>:</li> + +<li><a href="#NAK">NAK</a>:</li> + +<li><a href="#NANA">NANA</a>:</li> + +<li><a href="#nano">nano</a>:</li> + +<li><a href="#nano-">nano-</a>:</li> + +<li><a href="#nanoacre">nanoacre</a>:</li> + +<li><a href="#nanobot">nanobot</a>:</li> + +<li><a href="#nanocomputer">nanocomputer</a>:</li> + +<li><a href="#nanofortnight">nanofortnight</a>:</li> + +<li><a href="#nanotechnology">nanotechnology</a>:</li> + +<li><a href="#nasaldemons">nasal demons</a>:</li> + +<li><a href="#nastygram">nastygram</a>:</li> + +<li><a href="#NathanHale">Nathan Hale</a>:</li> + +<li><a href="#nature">nature</a>:</li> + +<li><a href="#neathack">neat hack</a>:</li> + +<li><a href="#neatsvsscruffies">neats vs. scruffies</a>:</li> + +<li><a href="#neep-neep">neep-neep</a>:</li> + +<li><a href="#neophilia">neophilia</a>:</li> + +<li><a href="#nerd">nerd</a>:</li> + +<li><a href="#nerdknob">nerd knob</a>:</li> + +<li><a href="#net.-">net.-</a>:</li> + +<li><a href="#net.god">net.god</a>:</li> + +<li><a href="#net.personality">net.personality</a>:</li> + +<li><a href="#net.police">net.police</a>:</li> + +<li><a href="#NetBOLLIX">NetBOLLIX</a>:</li> + +<li><a href="#netburp">netburp</a>:</li> + +<li><a href="#netdead">netdead</a>:</li> + +<li><a href="#nethack">nethack</a>:</li> + +<li><a href="#netiquette">netiquette</a>:</li> + +<li><a href="#netlag">netlag</a>:</li> + +<li><a href="#netnews">netnews</a>:</li> + +<li><a href="#netrock">netrock</a>:</li> + +<li><a href="#Netscrape">Netscrape</a>:</li> + +<li><a href="#netsplit">netsplit</a>:</li> + +<li><a href="#netter">netter</a>:</li> + +<li><a href="#networkaddress">network address</a>:</li> + +<li><a href="#networkmeltdown">network meltdown</a>:</li> + +<li><a href="#NewJersey">New Jersey</a>:</li> + +<li><a href="#NewTestament">New Testament</a>:</li> + +<li><a href="#newbie">newbie</a>:</li> + +<li><a href="#newgroupwars">newgroup wars</a>:</li> + +<li><a href="#newline">newline</a>:</li> + +<li><a href="#NeWS">NeWS</a>:</li> + +<li><a href="#newsfroup">newsfroup</a>:</li> + +<li><a href="#newsgroup">newsgroup</a>:</li> + +<li><a href="#nick">nick</a>:</li> + +<li><a href="#nickle">nickle</a>:</li> + +<li><a href="#nightmode">night mode</a>:</li> + +<li><a href="#NightmareFileSystem">Nightmare File System</a>:</li> + +<li><a href="#NIL">NIL</a>:</li> + +<li><a href="#NinetyNinetyRule">Ninety-Ninety Rule</a>:</li> + +<li><a href="#nipplemouse">nipple mouse</a>:</li> + +<li><a href="#NMI">NMI</a>:</li> + +<li><a href="#no-op">no-op</a>:</li> + +<li><a href="#noddy">noddy</a>:</li> + +<li><a href="#node">node</a>:</li> + +<li><a href="#NominalSemidestructor">Nominal Semidestructor</a>:</li> + +<li><a href="#nonoptimalsolution">non-optimal solution</a>:</li> + +<li><a href="#nonlinear">nonlinear</a>:</li> + +<li><a href="#nontrivial">nontrivial</a>:</li> + +<li><a href="#notreadyforprimetime">not ready for prime time</a>:</li> + +<li><a href="#notwork">notwork</a>:</li> + +<li><a href="#NP-">NP-</a>:</li> + +<li><a href="#nroff">nroff</a>:</li> + +<li><a href="#NSAlineeater">NSA line eater</a>:</li> + +<li><a href="#NSP">NSP</a>:</li> + +<li><a href="#nude">nude</a>:</li> + +<li><a href="#nugry">nugry</a>:</li> + +<li><a href="#nuke">nuke</a>:</li> + +<li><a href="#number-crunching">number-crunching</a>:</li> + +<li><a href="#numbers">numbers</a>:</li> + +<li><a href="#NUXIproblem">NUXI problem</a>:</li> + +<li><a href="#nybble">nybble</a>:</li> + +<li><a href="#nyetwork">nyetwork</a>:</li> +</ul> + +<hr> +Node:<a name="N">N</a>, Next:<a rel="next" href="#nadger">nadger</a>, Previous:<a rel="previous" href="#mutter">mutter</a>, Up:<a rel="up" href="#chap14">= N +=</a> <br> + + +<p><b>N</b> /N/ quant.</p> + +<p>1. A large and indeterminate number of objects: "There were N +bugs in that crock!" Also used in its original sense of a +variable name: "This crock has N bugs, as N goes to infinity." +(The true number of bugs is always at least N + 1; see <b><a +href="#LubarskysLawofCyberneticEntomology">Lubarsky's Law +of Cybernetic Entomology</a></b>.) 2. A variable whose value is +inherited from the current context. For example, when a meal is +being ordered at a restaurant, N may be understood to mean +however many people there are at the table. From the remark "We'd +like to order N wonton soups and a family dinner for N - 1" you +can deduce that one person at the table wants to eat only soup, +even though you don't know how many people there are (see <b><a +href="#great-wall">great-wall</a></b>). 3. `Nth': adj. The +ordinal counterpart of N, senses 1 and 2. "Now for the Nth and +last time<small>...</small>" In the specific context "Nth-year +grad student", N is generally assumed to be at least 4, and is +usually 5 or more (see <b><a href="#tenuredgraduatestudent">tenured graduate +student</a></b>). See also <b><a href="#randomnumbers">random +numbers</a></b>, <b><a href="#two-to-the-N">two-to-the-N</a></b>.</p> + +<hr> +Node:<a name="nadger">nadger</a>, Next:<a rel="next" href="#nagware">nagware</a>, Previous:<a rel="previous" href="#N">N</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>nadger</b> /nad'jr/ v.</p> + +<p>[UK, from rude slang noun `nadgers' for testicles; compare +American & British `bollixed'] Of software or hardware (not +people), to twiddle some object in a hidden manner, generally so +that it conforms better to some format. For instance, string +printing routines on 8-bit processors often take the string text +from the instruction stream, thus a print call looks like +<code>jsr print:"Hello world"</code>. The print routine has to +`nadger' the saved instruction pointer so that the processor +doesn't try to execute the text as instructions when the +subroutine returns. See <b><a href="#adger">adger</a></b>.</p> + +<hr> +Node:<a name="nagware">nagware</a>, Next:<a rel="next" href="#nailedtothewall">nailed to the wall</a>, Previous:<a +rel="previous" href="#nadger">nadger</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>nagware</b> /nag'weir/ n.</p> + +<p>[Usenet] The variety of <b><a href="#shareware">shareware</a></b> that displays a large screen at +the beginning or end reminding you to register, typically +requiring some sort of keystroke to continue so that you can't +use the software in batch mode. Compare <b><a href="#annoyware">annoyware</a></b>, <b><a href="#crippleware">crippleware</a></b>.</p> + +<hr> +Node:<a name="nailedtothewall">nailed to the wall</a>, +Next:<a rel="next" href="#nailingjelly">nailing jelly</a>, +Previous:<a rel="previous" href="#nagware">nagware</a>, Up:<a +rel="up" href="#chap14">= N =</a> <br> + + +<p><b>nailed to the wall</b> adj.</p> + +<p>[like a trophy] Said of a bug finally eliminated after +protracted, and even heroic, effort.</p> + +<hr> +Node:<a name="nailingjelly">nailing jelly</a>, Next:<a rel="next" href="#naive">naive</a>, Previous:<a rel="previous" href="#nailedtothewall">nailed to the wall</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>nailing jelly</b> vi.</p> + +<p>See <b><a href="#likenailingjellytoatree">like +nailing jelly to a tree</a></b>.</p> + +<hr> +Node:<a name="naive">naive</a>, Next:<a rel="next" href="#naiveuser">naive user</a>, Previous:<a rel="previous" href="#nailingjelly">nailing jelly</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>naive</b> adj.</p> + +<p>1. Untutored in the perversities of some particular program or +system; one who still tries to do things in an intuitive way, +rather than the right way (in really good designs these coincide, +but most designs aren't `really good' in the appropriate sense). +This trait is completely unrelated to general maturity or +competence, or even competence at any other specific program. It +is a sad commentary on the primitive state of computing that the +natural opposite of this term is often claimed to be `experienced +user' but is really more like `cynical user'. 2. Said of an +algorithm that doesn't take advantage of some superior but +advanced technique, e.g., the <b><a href="#bubblesort">bubble +sort</a></b>. It may imply naivete on the part of the programmer, +although there are situations where a naive algorithm is +preferred, because it is more important to keep the code +comprehensible than to go for maximum performance. "I know the +linear search is naive, but in this case the list typically only +has half a dozen items."</p> + +<hr> +Node:<a name="naiveuser">naive user</a>, Next:<a rel="next" +href="#NAK">NAK</a>, Previous:<a rel="previous" href="#naive">naive</a>, Up:<a rel="up" href="#chap14">= N +=</a> <br> + + +<p><b>naive user</b> n.</p> + +<p>A <b><a href="#luser">luser</a></b>. Tends to imply someone +who is ignorant mainly owing to inexperience. When this is +applied to someone who <i>has</i> experience, there is a +definite implication of stupidity.</p> + +<hr> +Node:<a name="NAK">NAK</a>, Next:<a rel="next" href="#NANA">NANA</a>, Previous:<a rel="previous" href="#naiveuser">naive user</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>NAK</b> /nak/ interj.</p> + +<p>[from the ASCII mnemonic for 0010101] 1. On-line joke answer +to <b><a href="#ACK">ACK</a></b>?: "I'm not here." 2. On-line +answer to a request for chat: "I'm not available." 3. Used to +politely interrupt someone to tell them you don't understand +their point or that they have suddenly stopped making sense. See +<b><a href="#ACK">ACK</a></b>, sense 3. "And then, after we +recode the project in COBOL<small>...</small>." "Nak, Nak, Nak! I +thought I heard you say COBOL!" 4. A negative answer. "OK if I +boot the server?" "NAK!"</p> + +<hr> +Node:<a name="NANA">NANA</a>, Next:<a rel="next" href="#nano">nano</a>, Previous:<a rel="previous" href="#NAK">NAK</a>, +Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>NANA</b> //</p> + +<p>[Usenet] The newsgroups news.admin.net-abuse.*, devoted to +fighting <b><a href="#spam">spam</a></b> and network abuse. Each +individual newsgroup is often referred to by adding a letter to +NANA. For example, NANAU would refer to +news.admin.net-abuse.usenet.</p> + +<p>When spam began to be a serious problem around 1995, and a +loose network of anti-spammers formed to combat it, spammers +immediately accused them of being the <b><a href="#backbonecabal">backbone cabal</a></b>, or the Cabal reborn. +Though this was not true, spam-fighters ironically accepted the +label and the tag line "There is No Cabal" reappeared (later, and +now commonly, abbreviated to "TINC"). Nowadays "the Cabal" is +generally understood to refer to the NANA regulars.</p> + +<hr> +Node:<a name="nano">nano</a>, Next:<a rel="next" href="#nano-">nano-</a>, Previous:<a rel="previous" href="#NANA">NANA</a>, Up:<a rel="up" href="#chap14">= N =</a> +<br> + + +<p><b>nano</b> /nan'oh/ n.</p> + +<p>[CMU: from `nanosecond'] A brief period of time. "Be with you +in a nano" means you really will be free shortly, i.e., implies +what mainstream people mean by "in a jiffy" (whereas the hackish +use of `jiffy' is quite different -- see <b><a href="#jiffy">jiffy</a></b>).</p> + +<hr> +Node:<a name="nano-">nano-</a>, Next:<a rel="next" href="#nanoacre">nanoacre</a>, Previous:<a rel="previous" href="#nano">nano</a>, Up:<a rel="up" href="#chap14">= N =</a> +<br> + + +<p><b>nano-</b> pref.</p> + +<p>[SI: the next quantifier below <b><a href="#micro-">micro-</a></b>; meaning * 10^(-9)] Smaller than <b><a +href="#micro-">micro-</a></b>, and used in the same rather loose +and connotative way. Thus, one has <b><a href="#nanotechnology">nanotechnology</a></b> (coined by hacker K. +Eric Drexler) by analogy with `microtechnology'; and a few +machine architectures have a `nanocode' level below `microcode'. +Tom Duff at Bell Labs has also pointed out that "Pi seconds is a +nanocentury". See also <b><a href="#quantifiers">quantifiers</a></b>, <b><a href="#pico-">pico-</a></b>, <b><a href="#nanoacre">nanoacre</a></b>, +<b><a href="#nanobot">nanobot</a></b>, <b><a href="#nanocomputer">nanocomputer</a></b>, <b><a href="#nanofortnight">nanofortnight</a></b>.</p> + +<hr> +Node:<a name="nanoacre">nanoacre</a>, Next:<a rel="next" href="#nanobot">nanobot</a>, Previous:<a rel="previous" href="#nano-">nano-</a>, Up:<a rel="up" href="#chap14">= N +=</a> <br> + + +<p><b>nanoacre</b> /nan'oh-ay`kr/ n.</p> + +<p>A unit (about 2 mm square) of real estate on a VLSI chip. The +term gets its giggle value from the fact that VLSI nanoacres have +costs in the same range as real acres once one figures in design +and fabrication-setup costs.</p> + +<hr> +Node:<a name="nanobot">nanobot</a>, Next:<a rel="next" href="#nanocomputer">nanocomputer</a>, Previous:<a rel="previous" +href="#nanoacre">nanoacre</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>nanobot</b> /nan'oh-bot/ n.</p> + +<p>A robot of microscopic proportions, presumably built by means +of <b><a href="#nanotechnology">nanotechnology</a></b>. As yet, +only used informally (and speculatively!). Also called a +`nanoagent'.</p> + +<hr> +Node:<a name="nanocomputer">nanocomputer</a>, Next:<a rel="next" +href="#nanofortnight">nanofortnight</a>, Previous:<a rel="previous" href="#nanobot">nanobot</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>nanocomputer</b> /nan'oh-k*m-pyoo'tr/ n.</p> + +<p>A computer with molecular-sized switching elements. Designs +for mechanical nanocomputers which use single-molecule sliding +rods for their logic have been proposed. The controller for a +<b><a href="#nanobot">nanobot</a></b> would be a +nanocomputer.</p> + +<hr> +Node:<a name="nanofortnight">nanofortnight</a>, Next:<a rel="next" href="#nanotechnology">nanotechnology</a>, Previous:<a +rel="previous" href="#nanocomputer">nanocomputer</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>nanofortnight</b> n.</p> + +<p>[Adelaide University] 1 fortnight * 10^(-9), or about 1.2 +msec. This unit was used largely by students doing undergraduate +practicals. See <b><a href="#microfortnight">microfortnight</a></b>, <b><a href="#attoparsec">attoparsec</a></b>, and <b><a href="#micro-">micro-</a></b>.</p> + +<hr> +Node:<a name="nanotechnology">nanotechnology</a>, Next:<a rel="next" href="#nasaldemons">nasal demons</a>, Previous:<a rel="previous" href="#nanofortnight">nanofortnight</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>nanotechnology</b> /nan'-oh-tek-no`l*-jee/ n.</p> + +<p>A hypothetical fabrication technology in which objects are +designed and built with the individual specification and +placement of each separate atom. The first unequivocal +nanofabrication experiments took place in 1990, for example with +the deposition of individual xenon atoms on a nickel substrate to +spell the logo of a certain very large computer company. +Nanotechnology has been a hot topic in the hacker subculture ever +since the term was coined by K. Eric Drexler in his book "Engines +of Creation" (Anchor/Doubleday, ISBN 0-385-19973-2), where he +predicted that nanotechnology could give rise to replicating +assemblers, permitting an exponential growth of productivity and +personal wealth (there's an authorized transcription at http://www.foresight.org/EOC/index.html.). +See also <b><a href="#bluegoo">blue goo</a></b>, <b><a href="#graygoo">gray goo</a></b>, <b><a href="#nanobot">nanobot</a></b>.</p> + +<hr> +Node:<a name="nasaldemons">nasal demons</a>, Next:<a rel="next" href="#nastygram">nastygram</a>, Previous:<a rel="previous" href="#nanotechnology">nanotechnology</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>nasal demons</b> n.</p> + +<p>Recognized shorthand on the Usenet group <i>comp.std.c</i> for +any unexpected behavior of a C compiler on encountering an +undefined construct. During a discussion on that group in early +1992, a regular remarked "When the compiler encounters [a given +undefined construct] it is legal for it to make demons fly out of +your nose" (the implication is that the compiler may choose any +arbitrarily bizarre way to interpret the code without violating +the ANSI C standard). Someone else followed up with a reference +to "nasal demons", which quickly became established.</p> + +<hr> +Node:<a name="nastygram">nastygram</a>, Next:<a rel="next" href="#NathanHale">Nathan Hale</a>, Previous:<a rel="previous" +href="#nasaldemons">nasal demons</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>nastygram</b> /nas'tee-gram/ n.</p> + +<p>1. A protocol packet or item of email (the latter is also +called a <b><a href="#letterbomb">letterbomb</a></b>) that takes +advantage of misfeatures or security holes on the target system +to do untoward things. 2. Disapproving mail, esp. from a <b><a +href="#net.god">net.god</a></b>, pursuant to a violation of <b><a +href="#netiquette">netiquette</a></b> or a complaint about +failure to correct some mail- or news-transmission problem. +Compare <b><a href="#shitogram">shitogram</a></b>, <b><a href="#mailbomb">mailbomb</a></b>. 3. A status report from an unhappy, +and probably picky, customer. "What'd Corporate say in today's +nastygram?" 4. [deprecated] An error reply by mail from a <b><a +href="#daemon">daemon</a></b>; in particular, a <b><a href="#bouncemessage">bounce message</a></b>.</p> + +<hr> +Node:<a name="NathanHale">Nathan Hale</a>, Next:<a rel="next" +href="#nature">nature</a>, Previous:<a rel="previous" href="#nastygram">nastygram</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>Nathan Hale</b> n.</p> + +<p>An asterisk (see also <b><a href="#splat">splat</a></b>, <b><a +href="#ASCII">ASCII</a></b>). Oh, you want an etymology? +Notionally, from "I regret that I have only one asterisk for my +country!", a misquote of the famous remark uttered by Nathan Hale +just before he was hanged. Hale was a (failed) spy for the rebels +in the American War of Independence.</p> + +<hr> +Node:<a name="nature">nature</a>, Next:<a rel="next" href="#neathack">neat hack</a>, Previous:<a rel="previous" href="#NathanHale">Nathan Hale</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>nature</b> n.</p> + +<p>See <b><a href="#hastheXnature">has the X +nature</a></b>.</p> + +<hr> +Node:<a name="neathack">neat hack</a>, Next:<a rel="next" +href="#neatsvsscruffies">neats vs. scruffies</a>, +Previous:<a rel="previous" href="#nature">nature</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>neat hack</b> n.</p> + +<p>[very common] 1. A clever technique. 2. A brilliant practical +joke, where neatness is correlated with cleverness, harmlessness, +and surprise value. Example: the Caltech Rose Bowl card display +switch (see <b><a href="#AppendixA">Appendix A</a></b> for +discussion). See also <b><a href="#hack">hack</a></b>.</p> + +<hr> +Node:<a name="neatsvsscruffies">neats vs. scruffies</a>, +Next:<a rel="next" href="#neep-neep">neep-neep</a>, Previous:<a +rel="previous" href="#neathack">neat hack</a>, Up:<a rel="up" +href="#chap14">= N =</a> <br> + + +<p><b>neats vs. scruffies</b> n.</p> + +<p>The label used to refer to one of the continuing <b><a href="#holywars">holy wars</a></b> in AI research. This conflict +tangles together two separate issues. One is the relationship +between human reasoning and AI; `neats' tend to try to build +systems that `reason' in some way identifiably similar to the way +humans report themselves as doing, while `scruffies' profess not +to care whether an algorithm resembles human reasoning in the +least as long as it works. More importantly, neats tend to +believe that logic is king, while scruffies favor looser, more +ad-hoc methods driven by empirical knowledge. To a neat, scruffy +methods appear promiscuous, successful only by accident, and not +productive of insights about how intelligence actually works; to +a scruffy, neat methods appear to be hung up on formalism and +irrelevant to the hard-to-capture `common sense' of living +intelligences.</p> + +<hr> +Node:<a name="neep-neep">neep-neep</a>, Next:<a rel="next" href="#neophilia">neophilia</a>, Previous:<a rel="previous" href="#neatsvsscruffies">neats vs. scruffies</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>neep-neep</b> /neep neep/ n.</p> + +<p>[onomatopoeic, widely spread through SF fandom but reported to +have originated at Caltech in the 1970s] One who is fascinated by +computers. Less specific than <b><a href="#hacker">hacker</a></b>, as it need not imply more skill than is +required to boot games on a PC. The derived noun `neeping' +applies specifically to the long conversations about computers +that tend to develop in the corners at most SF-convention parties +(the term `neepery' is also in wide use). Fandom has a related +proverb to the effect that "Hacking is a conversational black +hole!".</p> + +<hr> +Node:<a name="neophilia">neophilia</a>, Next:<a rel="next" href="#nerd">nerd</a>, Previous:<a rel="previous" href="#neep-neep">neep-neep</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>neophilia</b> /nee`oh-fil'-ee-*/ n.</p> + +<p>The trait of being excited and pleased by novelty. Common +among most hackers, SF fans, and members of several other +connected leading-edge subcultures, including the pro-technology +`Whole Earth' wing of the ecology movement, space activists, many +members of Mensa, and the Discordian/neo-pagan underground. All +these groups overlap heavily and (where evidence is available) +seem to share characteristic hacker tropisms for science fiction, +<b><a href="#music">music</a></b>, and <b><a href="#orientalfood">oriental food</a></b>. The opposite tendency +is `neophobia'.</p> + +<hr> +Node:<a name="nerd">nerd</a>, Next:<a rel="next" href="#nerdknob">nerd knob</a>, Previous:<a rel="previous" href="#neophilia">neophilia</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>nerd</b> n.</p> + +<p>1. [mainstream slang] Pejorative applied to anyone with an +above-average IQ and few gifts at small talk and ordinary social +rituals. 2. [jargon] Term of praise applied (in conscious ironic +reference to sense 1) to someone who knows what's really +important and interesting and doesn't care to be distracted by +trivial chatter and silly status games. Compare the two senses of +<b><a href="#computergeek">computer geek</a></b>.</p> + +<p>The word itself appears to derive from the lines "And then, +just to show them, I'll sail to Ka-Troo / And Bring Back an +It-Kutch, a Preep and a Proo, / A Nerkle, a Nerd, and a +Seersucker, too!" in the Dr. Seuss book "If I Ran the Zoo" +(1950). (The spellings `nurd' and `gnurd' also used to be current +at MIT, where `nurd' is reported from as far back as 1957.) How +it developed its mainstream meaning is unclear, but sense 1 seems +to have entered mass culture in the early 1970s (there are +reports that in the mid-1960s it meant roughly "annoying misfit" +without the connotation of intelligence).</p> + +<p>An IEEE Spectrum article (4/95, page 16) once derived `nerd' +in its variant form `knurd' from the word `drunk' backwards, but +this bears all the hallmarks of a bogus folk etymology.</p> + +<p>Hackers developed sense 2 in self-defense perhaps ten years +later, and some actually wear "Nerd Pride" buttons, only half as +a joke. At MIT one can find not only buttons but (what else?) +pocket protectors bearing the slogan and the MIT seal.</p> + +<hr> +Node:<a name="nerdknob">nerd knob</a>, Next:<a rel="next" +href="#net.-">net.-</a>, Previous:<a rel="previous" href="#nerd">nerd</a>, Up:<a rel="up" href="#chap14">= N =</a> +<br> + + +<p><b>nerd knob</b> n.</p> + +<p>[Cisco] a command in a complex piece of software which is more +likely to be used by an extremely experienced user to tweak a +setting of one sort or another - a setting which the average user +may not even know exists. Nerd knobs tend to be toggles, turning +on or off a particular, specific, narrowly defined behavior.</p> + +<hr> +Node:<a name="net.-">net.-</a>, Next:<a rel="next" href="#net.god">net.god</a>, Previous:<a rel="previous" href="#nerdknob">nerd knob</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>net.-</b> /net dot/ pref.</p> + +<p>[Usenet] Prefix used to describe people and events related to +Usenet. From the time before the <b><a href="#GreatRenaming">Great Renaming</a></b>, when most non-local +newsgroups had names beginning `net.'. Includes <b><a href="#net.god">net.god</a></b>s, `net.goddesses' (various charismatic +net.women with circles of on-line admirers), `net.lurkers' (see +<b><a href="#lurker">lurker</a></b>), `net.person', `net.parties' +(a synonym for <b><a href="#boink">boink</a></b>, sense 2), and +many similar constructs. See also <b><a href="#net.police">net.police</a></b>.</p> + +<hr> +Node:<a name="net.god">net.god</a>, Next:<a rel="next" href="#net.personality">net.personality</a>, Previous:<a rel="previous" href="#net.-">net.-</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>net.god</b> /net god/ n.</p> + +<p>Accolade referring to anyone who satisfies some combination of +the following conditions: has been visible on Usenet for more +than 5 years, ran one of the original backbone sites, moderated +an important newsgroup, wrote news software, or knows Gene, Mark, +Rick, Mel, Henry, Chuq, and Greg personally. See <b><a href="#demigod">demigod</a></b>. Net.goddesses such as Rissa or the +Slime Sisters have (so far) been distinguished more by +personality than by authority.</p> + +<hr> +Node:<a name="net.personality">net.personality</a>, Next:<a rel="next" href="#net.police">net.police</a>, Previous:<a rel="previous" href="#net.god">net.god</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>net.personality</b> /net per`sn-al'-*-tee/ n.</p> + +<p>Someone who has made a name for him or herself on <b><a href="#Usenet">Usenet</a></b>, through either longevity or +attention-getting posts, but doesn't meet the other requirements +of <b><a href="#net.god">net.god</a></b>hood.</p> + +<hr> +Node:<a name="net.police">net.police</a>, Next:<a rel="next" +href="#NetBOLLIX">NetBOLLIX</a>, Previous:<a rel="previous" href="#net.personality">net.personality</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>net.police</b> /net-p*-lees'/ n.</p> + +<p>(var. `net.cops') Those Usenet readers who feel it is their +responsibility to pounce on and <b><a href="#flame">flame</a></b> +any posting which they regard as offensive or in violation of +their understanding of <b><a href="#netiquette">netiquette</a></b>. Generally used sarcastically or +pejoratively. Also spelled `net police'. See also <b><a href="#net.-">net.-</a></b>, <b><a href="#codepolice">code +police</a></b>.</p> + +<hr> +Node:<a name="NetBOLLIX">NetBOLLIX</a>, Next:<a rel="next" href="#netburp">netburp</a>, Previous:<a rel="previous" href="#net.police">net.police</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>NetBOLLIX</b> n.</p> + +<p>[from bollix: to bungle, or British `bollocks'] <b><a href="#IBM">IBM</a></b>'s NetBIOS, an extremely <b><a href="#brain-damaged">brain-damaged</a></b> network protocol that, +like <b><a href="#BlueGlue">Blue Glue</a></b>, is used at +commercial shops that don't know any better.</p> + +<hr> +Node:<a name="netburp">netburp</a>, Next:<a rel="next" href="#netdead">netdead</a>, Previous:<a rel="previous" href="#NetBOLLIX">NetBOLLIX</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>netburp</b> n.</p> + +<p>[IRC] When <b><a href="#netlag">netlag</a></b> gets really +bad, and delays between servers exceed a certain threshhold, the +<b><a href="#IRC">IRC</a></b> network effectively becomes +partitioned for a period of time, and large numbers of people +seem to be signing off at the same time and then signing back on +again when things get better. An instance of this is called a +`netburp' (or, sometimes, <b><a href="#netsplit">netsplit</a></b>).</p> + +<hr> +Node:<a name="netdead">netdead</a>, Next:<a rel="next" href="#nethack">nethack</a>, Previous:<a rel="previous" href="#netburp">netburp</a>, Up:<a rel="up" href="#chap14">= N +=</a> <br> + + +<p><b>netdead</b> n.</p> + +<p>[IRC] The state of someone who signs off <b><a href="#IRC">IRC</a></b>, perhaps during a <b><a href="#netburp">netburp</a></b>, and doesn't sign back on until later. +In the interim, he is "dead to the net". Compare <b><a href="#link-dead">link-dead</a></b>.</p> + +<hr> +Node:<a name="nethack">nethack</a>, Next:<a rel="next" href="#netiquette">netiquette</a>, Previous:<a rel="previous" href="#netdead">netdead</a>, Up:<a rel="up" href="#chap14">= N +=</a> <br> + + +<p><b>nethack</b> /net'hak/ n.</p> + +<p>[Unix] A dungeon game similar to <b><a href="#rogue">rogue</a></b> but more elaborate, distributed in C +source over <b><a href="#Usenet">Usenet</a></b> and very popular +at Unix sites and on PC-class machines (nethack is probably the +most widely distributed of the freeware dungeon games). The +earliest versions, written by Jay Fenlason and later considerably +enhanced by Andries Brouwer, were simply called `hack'. The name +changed when maintenance was taken over by a group of hackers +originally organized by Mike Stephenson. There is now an official +site one at http://www.nethack.org/. See also +<b><a href="#moria">moria</a></b>, <b><a href="#rogue">rogue</a></b>, <b><a href="#Angband">Angband</a></b>.</p> + +<hr> +Node:<a name="netiquette">netiquette</a>, Next:<a rel="next" +href="#netlag">netlag</a>, Previous:<a rel="previous" href="#nethack">nethack</a>, Up:<a rel="up" href="#chap14">= N +=</a> <br> + + +<p><b>netiquette</b> /net'ee-ket/ or /net'i-ket/ n.</p> + +<p>[portmanteau, network + etiquette] The conventions of +politeness recognized on <b><a href="#Usenet">Usenet</a></b>, +such as avoidance of cross-posting to inappropriate groups and +refraining from commercial pluggery outside the <i>biz</i> +groups.</p> + +<hr> +Node:<a name="netlag">netlag</a>, Next:<a rel="next" href="#netnews">netnews</a>, Previous:<a rel="previous" href="#netiquette">netiquette</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>netlag</b> n.</p> + +<p>[IRC, MUD] A condition that occurs when the delays in the +<b><a href="#IRC">IRC</a></b> network or on a <b><a href="#MUD">MUD</a></b> become severe enough that servers briefly lose +and then reestablish contact, causing messages to be delivered in +bursts, often with delays of up to a minute. (Note that this term +has nothing to do with mainstream "jet lag", a condition which +hackers tend not to be much bothered by.) Often shortened to just +`lag'.</p> + +<hr> +Node:<a name="netnews">netnews</a>, Next:<a rel="next" href="#netrock">netrock</a>, Previous:<a rel="previous" href="#netlag">netlag</a>, Up:<a rel="up" href="#chap14">= N +=</a> <br> + + +<p><b>netnews</b> /net'n[y]ooz/ n.</p> + +<p>1. The software that makes <b><a href="#Usenet">Usenet</a></b> +run. 2. The content of Usenet. "I read netnews right after my +mail most mornings."</p> + +<hr> +Node:<a name="netrock">netrock</a>, Next:<a rel="next" href="#Netscrape">Netscrape</a>, Previous:<a rel="previous" href="#netnews">netnews</a>, Up:<a rel="up" href="#chap14">= N +=</a> <br> + + +<p><b>netrock</b> /net'rok/ n.</p> + +<p>[IBM] A <b><a href="#flame">flame</a></b>; used esp. on VNET, +IBM's internal corporate network.</p> + +<hr> +Node:<a name="Netscrape">Netscrape</a>, Next:<a rel="next" href="#netsplit">netsplit</a>, Previous:<a rel="previous" href="#netrock">netrock</a>, Up:<a rel="up" href="#chap14">= N +=</a> <br> + + +<p><b>Netscrape</b> n.</p> + +<p>[sometimes elaborated to `Netscrape Fornicator', also +`Nutscrape'] Standard name-of-insult for Netscape +Navigator/Communicator, Netscape's overweight Web browser. +Compare <b><a href="#InternetExploiter">Internet +Exploiter</a></b>.</p> + +<hr> +Node:<a name="netsplit">netsplit</a>, Next:<a rel="next" href="#netter">netter</a>, Previous:<a rel="previous" href="#Netscrape">Netscrape</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>netsplit</b> n.</p> + +<p>Syn. <b><a href="#netburp">netburp</a></b>.</p> + +<hr> +Node:<a name="netter">netter</a>, Next:<a rel="next" href="#networkaddress">network address</a>, Previous:<a rel="previous" href="#netsplit">netsplit</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>netter</b> n.</p> + +<p>1. Loosely, anyone with a <b><a href="#networkaddress">network address</a></b>. 2. More +specifically, a <b><a href="#Usenet">Usenet</a></b> regular. Most +often found in the plural. "If you post <i>that</i> in a +technical group, you're going to be flamed by angry netters for +the rest of time!"</p> + +<hr> +Node:<a name="networkaddress">network address</a>, Next:<a +rel="next" href="#networkmeltdown">network meltdown</a>, +Previous:<a rel="previous" href="#netter">netter</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>network address</b> n.</p> + +<p>(also `net address') As used by hackers, means an address on +`the' network (see <b><a href="#thenetwork">the +network</a></b>; this used to include <b><a href="#bangpath">bang path</a></b> addresses but now almost always +implies an <b><a href="#Internetaddress">Internet +address</a></b>). Net addresses are often used in email text as a +more concise substitute for personal names; indeed, hackers may +come to know each other quite well by network names without ever +learning each others' `legal' monikers. Indeed, display of a +network address (e.g on business cards) used to function as an +important hacker identification signal, like lodge pins among +Masons or tie-dyed T-shirts among Grateful Dead fans. In the day +of pervasive Internet this is less true, but you can still be +fairly sure that anyone with a network address handwritten on his +or her convention badge is a hacker.</p> + +<hr> +Node:<a name="networkmeltdown">network meltdown</a>, Next:<a +rel="next" href="#NewJersey">New Jersey</a>, Previous:<a rel="previous" href="#networkaddress">network address</a>, Up:<a +rel="up" href="#chap14">= N =</a> <br> + + +<p><b>network meltdown</b> n.</p> + +<p>A state of complete network overload; the network equivalent +of <b><a href="#thrash">thrash</a></b>ing. This may be induced by +a <b><a href="#Chernobylpacket">Chernobyl packet</a></b>. See +also <b><a href="#broadcaststorm">broadcast storm</a></b>, +<b><a href="#kamikazepacket">kamikaze packet</a></b>.</p> + +<p>Network meltdown is often a result of network designs that are +optimized for a steady state of moderate load and don't cope well +with the very jagged, bursty usage patterns of the real world. +One amusing instance of this is triggered by the popular and very +bloody shoot-'em-up game <i>Doom</i> on the PC. When used in +multiplayer mode over a network, the game uses broadcast packets +to inform other machines when bullets are fired. This causes +problems with weapons like the chain gun which fire rapidly -- it +can blast the network into a meltdown state just as easily as it +shreds opposing monsters.</p> + +<hr> +Node:<a name="NewJersey">New Jersey</a>, Next:<a rel="next" +href="#NewTestament">New Testament</a>, Previous:<a rel="previous" href="#networkmeltdown">network meltdown</a>, Up:<a +rel="up" href="#chap14">= N =</a> <br> + + +<p><b>New Jersey</b> adj.</p> + +<p>[primarily Stanford/Silicon Valley] Brain-damaged or of poor +design. This refers to the allegedly wretched quality of such +software as C, C++, and Unix (which originated at Bell Labs in +Murray Hill, New Jersey). "This compiler bites the bag, but what +can you expect from a compiler designed in New Jersey?" Compare +<b><a href="#BerkeleyQualitySoftware">Berkeley Quality +Software</a></b>. See also <b><a href="#Unixconspiracy">Unix +conspiracy</a></b>.</p> + +<hr> +Node:<a name="NewTestament">New Testament</a>, Next:<a rel="next" href="#newbie">newbie</a>, Previous:<a rel="previous" +href="#NewJersey">New Jersey</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>New Testament</b> n.</p> + +<p>[C programmers] The second edition of K&R's "The C +Programming Language" (Prentice-Hall, 1988; ISBN 0-13-110362-8), +describing ANSI Standard C. See <b><a href="#KandR">K&R</a></b>; this version is also called +`K&R2'.</p> + +<hr> +Node:<a name="newbie">newbie</a>, Next:<a rel="next" href="#newgroupwars">newgroup wars</a>, Previous:<a rel="previous" +href="#NewTestament">New Testament</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>newbie</b> /n[y]oo'bee/ n.</p> + +<p>[verry common; orig. from British public-school and military +slang variant of `new boy'] A Usenet neophyte. This term surfaced +in the <b><a href="#newsgroup">newsgroup</a></b> +<i>talk.bizarre</i> but is now in wide use (the combination +"clueless newbie" is especially common). Criteria for being +considered a newbie vary wildly; a person can be called a newbie +in one newsgroup while remaining a respected regular in another. +The label `newbie' is sometimes applied as a serious insult to a +person who has been around Usenet for a long time but who +carefully hides all evidence of having a clue. See <b><a href="#B1FF">B1FF</a></b>; see also <b><a href="#gnubie">gnubie</a></b>.</p> + +<hr> +Node:<a name="newgroupwars">newgroup wars</a>, Next:<a rel="next" href="#newline">newline</a>, Previous:<a rel="previous" +href="#newbie">newbie</a>, Up:<a rel="up" href="#chap14">= +N =</a> <br> + + +<p><b>newgroup wars</b> /n[y]oo'groop worz/ n.</p> + +<p>[Usenet] The salvos of dueling <code>newgroup</code> and +<code>rmgroup</code> messages sometimes exchanged by persons on +opposite sides of a dispute over whether a <b><a href="#newsgroup">newsgroup</a></b> should be created net-wide, or +(even more frequently) whether an obsolete one should be removed. +These usually settle out within a week or two as it becomes clear +whether the group has a natural constituency (usually, it +doesn't). At times, especially in the completely anarchic +<i>alt</i> hierarchy, the names of newsgroups themselves become a +form of comment or humor; e.g., the group +<i>alt.swedish.chef.bork.bork.bork</i> which originated as a +birthday joke for a Muppets fan, or any number of specialized +abuse groups named after particularly notorious <b><a href="#flamer">flamer</a></b>s, e.g., <i>alt.weemba</i>.</p> + +<hr> +Node:<a name="newline">newline</a>, Next:<a rel="next" href="#NeWS">NeWS</a>, Previous:<a rel="previous" href="#newgroupwars">newgroup wars</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>newline</b> /n[y]oo'li:n/ n.</p> + +<p>1. [techspeak, primarily Unix] The ASCII LF character +(0001010), used under <b><a href="#Unix">Unix</a></b> as a text +line terminator. Though the term `newline' appears in ASCII +standards, it never caught on in the general computing world +before Unix. 2. More generally, any magic character, character +sequence, or operation (like Pascal's writeln procedure) required +to terminate a text record or separate lines. See <b><a href="#crlf">crlf</a></b>, <b><a href="#terpri">terpri</a></b>.</p> + +<hr> +Node:<a name="NeWS">NeWS</a>, Next:<a rel="next" href="#newsfroup">newsfroup</a>, Previous:<a rel="previous" href="#newline">newline</a>, Up:<a rel="up" href="#chap14">= N +=</a> <br> + + +<p><b>NeWS</b> /nee'wis/, /n[y]oo'is/ or /n[y]ooz/ n.</p> + +<p>[acronym; the `Network Window System'] The road not taken in +window systems, an elegant <b><a href="#PostScript">PostScript</a></b>-based environment that would +almost certainly have won the standards war with <b><a href="#X">X</a></b> if it hadn't been <b><a href="#proprietary">proprietary</a></b> to Sun Microsystems. There is +a lesson here that too many software vendors haven't yet heeded. +Many hackers insist on the two-syllable pronunciations above as a +way of distinguishing NeWS from Usenet news (the <b><a href="#netnews">netnews</a></b> software).</p> + +<hr> +Node:<a name="newsfroup">newsfroup</a>, Next:<a rel="next" href="#newsgroup">newsgroup</a>, Previous:<a rel="previous" href="#NeWS">NeWS</a>, Up:<a rel="up" href="#chap14">= N =</a> +<br> + + +<p><b>newsfroup</b> // n.</p> + +<p>[Usenet] Silly synonym for <b><a href="#newsgroup">newsgroup</a></b>, originally a typo but now in +regular use on Usenet's talk.bizarre, and other lunatic-fringe +groups. Compare <b><a href="#hing">hing</a></b>, <b><a href="#grilf">grilf</a></b>, <b><a href="#pr0n">pr0n</a></b> and <b><a +href="#filk">filk</a></b>.</p> + +<hr> +Node:<a name="newsgroup">newsgroup</a>, Next:<a rel="next" href="#nick">nick</a>, Previous:<a rel="previous" href="#newsfroup">newsfroup</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>newsgroup</b> n.</p> + +<p>[Usenet] One of <b><a href="#Usenet">Usenet</a></b>'s huge +collection of topic groups or <b><a href="#fora">fora</a></b>. +Usenet groups can be `unmoderated' (anyone can post) or +`moderated' (submissions are automatically directed to a +moderator, who edits or filters and then posts the results). Some +newsgroups have parallel <b><a href="#mailinglist">mailing +list</a></b>s for Internet people with no netnews access, with +postings to the group automatically propagated to the list and +vice versa. Some moderated groups (especially those which are +actually gatewayed Internet mailing lists) are distributed as +`digests', with groups of postings periodically collected into a +single large posting with an index.</p> + +<p>Among the best-known are <i>comp.lang.c</i> (the C-language +forum), <i>comp.arch</i> (on computer architectures), +<i>comp.unix.wizards</i> (for Unix wizards), +<i>rec.arts.sf.written</i> and siblings (for science-fiction +fans), and <i>talk.politics.misc</i> (miscellaneous political +discussions and <b><a href="#flamage">flamage</a></b>).</p> + +<hr> +Node:<a name="nick">nick</a>, Next:<a rel="next" href="#nickle">nickle</a>, Previous:<a rel="previous" href="#newsgroup">newsgroup</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>nick</b> n.</p> + +<p>[IRC; very common] Short for nickname. On <b><a href="#IRC">IRC</a></b>, every user must pick a nick, which is +sometimes the same as the user's real name or login name, but is +often more fanciful. Compare <b><a href="#handle">handle</a></b>, +<b><a href="#screenname">screen name</a></b>.</p> + +<hr> +Node:<a name="nickle">nickle</a>, Next:<a rel="next" href="#nightmode">night mode</a>, Previous:<a rel="previous" href="#nick">nick</a>, Up:<a rel="up" href="#chap14">= N =</a> +<br> + + +<p><b>nickle</b> /ni'kl/ n.</p> + +<p>[from `nickel', common name for the U.S. 5-cent coin] A <b><a +href="#nybble">nybble</a></b> + 1; 5 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 +also <b><a href="#deckle">deckle</a></b>, and <b><a href="#nybble">nybble</a></b> for names of other bit units.</p> + +<hr> +Node:<a name="nightmode">night mode</a>, Next:<a rel="next" +href="#NightmareFileSystem">Nightmare File System</a>, +Previous:<a rel="previous" href="#nickle">nickle</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>night mode</b> n.</p> + +<p>See <b><a href="#phase">phase</a></b> (of people).</p> + +<hr> +Node:<a name="NightmareFileSystem">Nightmare File +System</a>, Next:<a rel="next" href="#NIL">NIL</a>, Previous:<a +rel="previous" href="#nightmode">night mode</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>Nightmare File System</b> n.</p> + +<p>Pejorative hackerism for Sun's Network File System (NFS). In +any nontrivial network of Suns where there is a lot of NFS +cross-mounting, when one Sun goes down, the others often freeze +up. Some machine tries to access the down one, and (getting no +response) repeats indefinitely. This causes it to appear dead to +some messages (what is actually happening is that it is locked up +in what should have been a brief excursion to a higher <b><a +href="#spl">spl</a></b> level). Then another machine tries to +reach either the down machine or the pseudo-down machine, and +itself becomes pseudo-down. The first machine to discover the +down one is now trying both to access the down one and to respond +to the pseudo-down one, so it is even harder to reach. This +situation snowballs very quickly, and soon the entire network of +machines is frozen -- worst of all, the user can't even abort the +file access that started the problem! Many of NFS's problems are +excused by partisans as being an inevitable result of its +statelessness, which is held to be a great feature (critics, of +course, call it a great <b><a href="#misfeature">misfeature</a></b>). (ITS partisans are apt to cite +this as proof of Unix's alleged bogosity; ITS had a working +NFS-like shared file system with none of these problems in the +early 1970s.) See also <b><a href="#broadcaststorm">broadcast +storm</a></b>.</p> + +<hr> +Node:<a name="NIL">NIL</a>, Next:<a rel="next" href="#NinetyNinetyRule">Ninety-Ninety Rule</a>, Previous:<a rel="previous" href="#NightmareFileSystem">Nightmare File +System</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>NIL</b> /nil/</p> + +<p>No. Used in reply to a question, particularly one asked using +the `-P' convention. Most hackers assume this derives simply from +LISP terminology for `false' (see also <b><a href="#T">T</a></b>), but NIL as a negative reply was well-established +among radio hams decades before the advent of LISP. The +historical connection between early hackerdom and the ham radio +world was strong enough that this may have been an influence.</p> + +<hr> +Node:<a name="NinetyNinetyRule">Ninety-Ninety Rule</a>, +Next:<a rel="next" href="#nipplemouse">nipple mouse</a>, +Previous:<a rel="previous" href="#NIL">NIL</a>, Up:<a rel="up" +href="#chap14">= N =</a> <br> + + +<p><b>Ninety-Ninety Rule</b> n.</p> + +<p>"The first 90% of the code accounts for the first 90% of the +development time. The remaining 10% of the code accounts for the +other 90% of the development time." Attributed to Tom Cargill of +Bell Labs, and popularized by Jon Bentley's September 1985 +"Bumper-Sticker Computer Science" column in "Communications of +the ACM". It was there called the "Rule of Credibility", a name +which seems not to have stuck. Other maxims in the same vein +include the law attributed to the early British computer +scientist Douglas Hartree: "The time from now until the +completion of the project tends to become constant."</p> + +<hr> +Node:<a name="nipplemouse">nipple mouse</a>, Next:<a rel="next" href="#NMI">NMI</a>, Previous:<a rel="previous" href="#NinetyNinetyRule">Ninety-Ninety Rule</a>, Up:<a rel="up" +href="#chap14">= N =</a> <br> + + +<p><b>nipple mouse</b> n.</p> + +<p>Var. `clit mouse, clitoris' Common term for the pointing +device used on IBM ThinkPads and a few other laptop computers. +The device, which sits between the `g' and `h' keys on the +keyboard, indeed resembles a rubber nipple intended to be tweaked +by a forefinger. Many hackers consider these superior to the +glide pads found on most laptops, which are harder to control +precisely.</p> + +<hr> +Node:<a name="NMI">NMI</a>, Next:<a rel="next" href="#no-op">no-op</a>, Previous:<a rel="previous" href="#nipplemouse">nipple mouse</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>NMI</b> /N-M-I/ n.</p> + +<p>Non-Maskable Interrupt. An IRQ 7 on the PDP-11 or 680[01234]0; +the NMI line on an 80[1234]86. In contrast with a <b><a href="#priorityinterrupt">priority interrupt</a></b> (which might +be ignored, although that is unlikely), an NMI is <i>never</i> +ignored. Except, that is, on <b><a href="#clone">clone</a></b> +boxes, where NMI is often ignored on the motherboard because +flaky hardware can generate many spurious ones.</p> + +<hr> +Node:<a name="no-op">no-op</a>, Next:<a rel="next" href="#noddy">noddy</a>, Previous:<a rel="previous" href="#NMI">NMI</a>, Up:<a rel="up" href="#chap14">= N =</a> +<br> + + +<p><b>no-op</b> /noh'op/ n.,v.</p> + +<p>alt. NOP /nop/ [no operation] 1. A machine instruction that +does nothing (sometimes used in assembler-level programming as +filler for data or patch areas, or to overwrite code to be +removed in binaries). 2. A person who contributes nothing to a +project, or has nothing going on upstairs, or both. As in "He's a +no-op." 3. Any operation or sequence of operations with no +effect, such as circling the block without finding a parking +space, or putting money into a vending machine and having it fall +immediately into the coin-return box, or asking someone for help +and being told to go away. "Oh, well, that was a no-op." +Hot-and-sour soup (see <b><a href="#great-wall">great-wall</a></b>) that is insufficiently either +is `no-op soup'; so is wonton soup if everybody else is having +hot-and-sour.</p> + +<hr> +Node:<a name="noddy">noddy</a>, Next:<a rel="next" href="#node">node</a>, Previous:<a rel="previous" href="#no-op">no-op</a>, Up:<a rel="up" href="#chap14">= N +=</a> <br> + + +<p><b>noddy</b> /nod'ee/ adj.</p> + +<p>[UK: from the children's books] 1. Small and un-useful, but +demonstrating a point. Noddy programs are often written by people +learning a new language or system. The archetypal noddy program +is <b><a href="#helloworld">hello world</a></b>. Noddy code +may be used to demonstrate a feature or bug of a compiler. May be +used of real hardware or software to imply that it isn't worth +using. "This editor's a bit noddy." 2. A program that is more or +less instant to produce. In this use, the term does not +necessarily connote uselessness, but describes a <b><a href="#hack">hack</a></b> sufficiently trivial that it can be written +and debugged while carrying on (and during the space of) a normal +conversation. "I'll just throw together a noddy <b><a href="#awk">awk</a></b> script to dump all the first fields." In North +America this might be called a <b><a href="#mickeymouseprogram">mickey mouse program</a></b>. See +<b><a href="#toyprogram">toy program</a></b>.</p> + +<hr> +Node:<a name="node">node</a>, Next:<a rel="next" href="#NominalSemidestructor">Nominal Semidestructor</a>, +Previous:<a rel="previous" href="#noddy">noddy</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>node</b> n.</p> + +<p>1. [Internet, UUCP] A host machine on the network. 2. [MS-DOS +BBSes] A dial-in line on a BBS. Thus an MS-DOS <b><a href="#sysop">sysop</a></b> might say that his BBS has 4 nodes even +though it has a single machine and no Internet link, confusing an +Internet hacker no end.</p> + +<hr> +Node:<a name="NominalSemidestructor">Nominal +Semidestructor</a>, Next:<a rel="next" href="#nonoptimalsolution">non-optimal solution</a>, Previous:<a +rel="previous" href="#node">node</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>Nominal Semidestructor</b> n.</p> + +<p>Soundalike slang for `National Semiconductor', found among +other places in the Networking/2 networking sources. During the +late 1970s to mid-1980s this company marketed a series of +microprocessors including the NS16000 and NS32000 and several +variants. At one point early in the great microprocessor race, +the specs on these chips made them look like serious competition +for the rising Intel 80x86 and Motorola 680x0 series. +Unfortunately, the actual parts were notoriously flaky and never +implemented the full instruction set promised in their +literature, apparently because the company couldn't get any of +the mask steppings to work as designed. They eventually sank +without trace, joining the Zilog Z8000 and a few even more +obscure also-rans in the graveyard of forgotten microprocessors. +Compare <b><a href="#HP-SUX">HP-SUX</a></b>, <b><a href="#AIDX">AIDX</a></b>, <b><a href="#buglix">buglix</a></b>, <b><a +href="#Macintrash">Macintrash</a></b>, <b><a href="#Telerat">Telerat</a></b>, <b><a href="#ScumOS">ScumOS</a></b>, +<b><a href="#sun-stools">sun-stools</a></b>, <b><a href="#Slowlaris">Slowlaris</a></b>, <b><a href="#InternetExploder">Internet Exploder</a></b>.</p> + +<hr> +Node:<a name="nonoptimalsolution">non-optimal solution</a>, +Next:<a rel="next" href="#nonlinear">nonlinear</a>, Previous:<a +rel="previous" href="#NominalSemidestructor">Nominal +Semidestructor</a>, Up:<a rel="up" href="#chap14">= N +=</a> <br> + + +<p><b>non-optimal solution</b> n.</p> + +<p>(also `sub-optimal solution') An astoundingly stupid way to do +something. This term is generally used in deadpan sarcasm, as its +impact is greatest when the person speaking looks completely +serious. Compare <b><a href="#stunning">stunning</a></b>. See +also <b><a href="#BadThing">Bad Thing</a></b>.</p> + +<hr> +Node:<a name="nonlinear">nonlinear</a>, Next:<a rel="next" href="#nontrivial">nontrivial</a>, Previous:<a rel="previous" href="#nonoptimalsolution">non-optimal solution</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>nonlinear</b> adj.</p> + +<p>[scientific computation] 1. Behaving in an erratic and +unpredictable fashion; unstable. When used to describe the +behavior of a machine or program, it suggests that said machine +or program is being forced to run far outside of design +specifications. This behavior may be induced by unreasonable +inputs, or may be triggered when a more mundane bug sends the +computation far off from its expected course. 2. When describing +the behavior of a person, suggests a tantrum or a <b><a href="#flame">flame</a></b>. "When you talk to Bob, don't mention the +drug problem or he'll go nonlinear for hours." In this context, +`go nonlinear' connotes `blow up out of proportion' (proportion +connotes linearity).</p> + +<hr> +Node:<a name="nontrivial">nontrivial</a>, Next:<a rel="next" +href="#notreadyforprimetime">not ready for prime +time</a>, Previous:<a rel="previous" href="#nonlinear">nonlinear</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>nontrivial</b> adj.</p> + +<p>Requiring real thought or significant computing power. Often +used as an understated way of saying that a problem is quite +difficult or impractical, or even entirely unsolvable ("Proving +P=NP is nontrivial"). The preferred emphatic form is `decidedly +nontrivial'. See <b><a href="#trivial">trivial</a></b>, <b><a +href="#uninteresting">uninteresting</a></b>, <b><a href="#interesting">interesting</a></b>.</p> + +<hr> +Node:<a name="notreadyforprimetime">not ready for +prime time</a>, Next:<a rel="next" href="#notwork">notwork</a>, +Previous:<a rel="previous" href="#nontrivial">nontrivial</a>, +Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>not ready for prime time</b> adj.</p> + +<p>Usable, but only just so; not very robust; for internal use +only. Said of a program or device. Often connotes that the thing +will be made more solid <b><a href="#RealSoonNow">Real Soon +Now</a></b>. This term comes from the ensemble name of the +original cast of "Saturday Night Live", the "Not Ready for Prime +Time Players". It has extra flavor for hackers because of the +special (though now semi-obsolescent) meaning of <b><a href="#primeTime">prime time</a></b>. Compare <b><a href="#beta">beta</a></b>.</p> + +<hr> +Node:<a name="notwork">notwork</a>, Next:<a rel="next" href="#NP-">NP-</a>, Previous:<a rel="previous" href="#notreadyforprimetime">not ready for prime time</a>, +Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>notwork</b> /not'werk/ n.</p> + +<p>A network, when it is acting <b><a href="#flaky">flaky</a></b> +or is <b><a href="#down">down</a></b>. Compare <b><a href="#nyetwork">nyetwork</a></b>. Said at IBM to have originally +referred to a particular period of flakiness on IBM's VNET +corporate network ca. 1988; but there are independent reports of +the term from elsewhere.</p> + +<hr> +Node:<a name="NP-">NP-</a>, Next:<a rel="next" href="#nroff">nroff</a>, Previous:<a rel="previous" href="#notwork">notwork</a>, Up:<a rel="up" href="#chap14">= N +=</a> <br> + + +<p><b>NP-</b> /N-P/ pref.</p> + +<p>Extremely. Used to modify adjectives describing a level or +quality of difficulty; the connotation is often `more so than it +should be' This is generalized from the computer-science terms +`NP-hard' and `NP-complete'; NP-complete problems all seem to be +very hard, but so far no one has found a proof that they are. NP +is the set of Nondeterministic-Polynomial algorithms, those that +can be completed by a nondeterministic Turing machine in an +amount of time that is a polynomial function of the size of the +input; a solution for one NP-complete problem would solve all the +others. "Coding a BitBlt implementation to perform correctly in +every case is NP-annoying."</p> + +<p>Note, however, that strictly speaking this usage is +misleading; there are plenty of easy problems in class NP. +NP-complete problems are hard not because they are in class NP, +but because they are the hardest problems in class NP.</p> + +<hr> +Node:<a name="nroff">nroff</a>, Next:<a rel="next" href="#NSAlineeater">NSA line eater</a>, Previous:<a rel="previous" href="#NP-">NP-</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>nroff</b> /N'rof/</p> + +<p>n. [Unix, from "new roff" (see <b><a href="#troff">troff</a></b>)] A companion program to the Unix +typesetter <b><a href="#troff">troff</a></b>, accepting identical +input but preparing output for terminals and line printers.</p> + +<hr> +Node:<a name="NSAlineeater">NSA line eater</a>, Next:<a +rel="next" href="#NSP">NSP</a>, Previous:<a rel="previous" href="#nroff">nroff</a>, Up:<a rel="up" href="#chap14">= N +=</a> <br> + + +<p><b>NSA line eater</b> n.</p> + +<p>The National Security Agency trawling program sometimes +assumed to be reading the net for the U.S. Government's spooks. +Most hackers used to think it was mythical but believed in acting +as though existed just in case. since the mid-1990s it has +gradually become known that the NSA actually does this, quite +illegaly, through its Echelon program.</p> + +<p>The standard countermeasure is to put loaded phrases like +`KGB', `Uzi', `nuclear materials', `Palestine', `cocaine', and +`assassination' in their <b><a href="#sigblock">sig +block</a></b>s in a (probably futile) attempt to confuse and +overload the creature. The <b><a href="#GNU">GNU</a></b> version +of <b><a href="#EMACS">EMACS</a></b> actually has a command that +randomly inserts a bunch of insidious anarcho-verbiage into your +edited text.</p> + +<p>As far back as the 1970s there was a mainstream variant of +this myth involving a `Trunk Line Monitor', which supposedly used +speech recognition to extract words from telephone trunks. This +is much harder than noticing keywords in email, and most of the +people who originally propagated it had no idea of then-current +technology or the storage, signal-processing, or speech +recognition needs of such a project. On the basis of mass-storage +costs alone it would have been cheaper to hire 50 high-school +students and just let them listen in. Twenty years and several +orders of technological magnitude later, however, there are clear +indications that the NSA has actually deployed such filtering +(again, very much against U.S. law).</p> + +<hr> +Node:<a name="NSP">NSP</a>, Next:<a rel="next" href="#nude">nude</a>, Previous:<a rel="previous" href="#NSAlineeater">NSA line eater</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>NSP</b> /N-S-P/ n.</p> + +<p>Common abbreviation for `Network Service Provider', one of the +big national or regional companies that maintains a portion of +the Internet backbone and resells connectivity to <b><a href="#ISP">ISP</a></b>s. In 1996, major NSPs include ANS, MCI, UUNET, +and Sprint. An Internet wholesaler.</p> + +<hr> +Node:<a name="nude">nude</a>, Next:<a rel="next" href="#nugry">nugry</a>, Previous:<a rel="previous" href="#NSP">NSP</a>, Up:<a rel="up" href="#chap14">= N =</a> +<br> + + +<p><b>nude</b> adj.</p> + +<p>Said of machines delivered without an operating system +(compare <b><a href="#baremetal">bare metal</a></b>). "We +ordered 50 systems, but they all arrived nude, so we had to spend +a an extra weekend with the installation disks." This usage is a +recent innovation reflecting the fact that most IBM-PC clones are +now delivered with an operating system pre-installed at the +factory. Other kinds of hardware are still normally delivered +without OS, so this term is particular to PC support groups.</p> + +<hr> +Node:<a name="nugry">nugry</a>, Next:<a rel="next" href="#nuke">nuke</a>, Previous:<a rel="previous" href="#nude">nude</a>, Up:<a rel="up" href="#chap14">= N =</a> +<br> + + +<p><b>nugry</b> /n[y]oo'gree/</p> + +<p>[Usenet, 'newbie' + '-gry'] `. n. A <b><a href="#newbie">newbie</a></b> who posts a <b><a href="#FAQ">FAQ</a></b> in the rec.puzzles newsgroup, especially if it +is a variant of the notorious and unanswerable "What, besides +`angry' and `hungry', is the third common English word that ends +in -GRY?". In the newsgroup, the canonical answer is of course +`nugry' itself. Plural is `nusgry' /n[y]oos'gree/. 2. adj. Having +the qualities of a nugry.</p> + +<hr> +Node:<a name="nuke">nuke</a>, Next:<a rel="next" href="#number-crunching">number-crunching</a>, Previous:<a rel="previous" href="#nugry">nugry</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>nuke</b> /n[y]ook/ vt.</p> + +<p>[common] 1. To intentionally delete the entire contents of a +given directory or storage volume. "On Unix, <code>rm -r +/usr</code> will nuke everything in the usr filesystem." Never +used for accidental deletion; contrast <b><a href="#blowaway">blow away</a></b>. 2. Syn. for <b><a href="#dike">dike</a></b>, applied to smaller things such as files, +features, or code sections. Often used to express a final +verdict. "What do you want me to do with that 80-meg <b><a href="#wallpaper">wallpaper</a></b> file?" "Nuke it." 3. Used of +processes as well as files; nuke is a frequent verbal alias for +<code>kill -9</code> on Unix. 4. On IBM PCs, a bug that results +in <b><a href="#fandangooncore">fandango on core</a></b> +can trash the operating system, including the FAT (the in-core +copy of the disk block chaining information). This can utterly +scramble attached disks, which are then said to have been +`nuked'. This term is also used of analogous lossages on +Macintoshes and other micros without memory protection.</p> + +<hr> +Node:<a name="number-crunching">number-crunching</a>, Next:<a +rel="next" href="#numbers">numbers</a>, Previous:<a rel="previous" href="#nuke">nuke</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>number-crunching</b> n.</p> + +<p>[common] Computations of a numerical nature, esp. those that +make extensive use of floating-point numbers. The only thing +<b><a href="#Fortrash">Fortrash</a></b> is good for. This term is +in widespread informal use outside hackerdom and even in +mainstream slang, but has additional hackish connotations: +namely, that the computations are mindless and involve massive +use of <b><a href="#bruteforce">brute force</a></b>. This is +not always <b><a href="#evil">evil</a></b>, esp. if it involves +ray tracing or fractals or some other use that makes <b><a href="#prettypictures">pretty pictures</a></b>, esp. if such +pictures can be used as <b><a href="#wallpaper">wallpaper</a></b>. See also <b><a href="#crunch">crunch</a></b>.</p> + +<hr> +Node:<a name="numbers">numbers</a>, Next:<a rel="next" href="#NUXIproblem">NUXI problem</a>, Previous:<a rel="previous" +href="#number-crunching">number-crunching</a>, Up:<a rel="up" +href="#chap14">= N =</a> <br> + + +<p><b>numbers</b> n.</p> + +<p>[scientific computation] Output of a computation that may not +be significant results but at least indicate that the program is +running. May be used to placate management, grant sponsors, etc. +`Making numbers' means running a program because output -- any +output, not necessarily meaningful output -- is needed as a +demonstration of progress. See <b><a href="#prettypictures">pretty pictures</a></b>, <b><a href="#math-out">math-out</a></b>, <b><a href="#socialsciencenumber">social science number</a></b>.</p> + +<hr> +Node:<a name="NUXIproblem">NUXI problem</a>, Next:<a rel="next" href="#nybble">nybble</a>, Previous:<a rel="previous" +href="#numbers">numbers</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>NUXI problem</b> /nuk'see pro'bl*m/ n.</p> + +<p>Refers to the problem of transferring data between machines +with differing byte-order. The string `UNIX' might look like +`NUXI' on a machine with a different `byte sex' (e.g., when +transferring data from a <b><a href="#little-endian">little-endian</a></b> to a <b><a href="#big-endian">big-endian</a></b>, or vice-versa). See also <b><a +href="#middle-endian">middle-endian</a></b>, <b><a href="#swab">swab</a></b>, and <b><a href="#bytesexual">bytesexual</a></b>.</p> + +<hr> +Node:<a name="nybble">nybble</a>, Next:<a rel="next" href="#nyetwork">nyetwork</a>, Previous:<a rel="previous" href="#NUXIproblem">NUXI problem</a>, Up:<a rel="up" href="#chap14">= N =</a> <br> + + +<p><b>nybble</b> /nib'l/ (alt. `nibble') n.</p> + +<p>[from v. `nibble' by analogy with `bite' => `byte'] Four +bits; one <b><a href="#hex">hex</a></b> digit; a half-byte. +Though `byte' is now techspeak, this useful relative is still +jargon. Compare <b><a href="#byte">byte</a></b>; see also <b><a +href="#bit">bit</a></b>. The more mundane spelling "nibble" is +also commonly used. Apparently the `nybble' spelling is uncommon +in Commonwealth Hackish, as British orthography would suggest the +pronunciation /ni:'bl/.</p> + +<p>Following `bit', `byte' and `nybble' there have been quite a +few analogical attempts to construct unambiguous terms for bit +blocks of other sizes. All of these are strictly jargon, not +techspeak, and not very common jargon at that (most hackers would +recognize them in context but not use them spontaneously). We +collect them here for reference together with the ambiguous +techspeak terms `word', `half-word' and `double word'; some +(indicated) have substantial information separate entries.</p> + +<blockquote> +<dl> +<dt>2 bits:</dt> + +<dd><b><a href="#crumb">crumb</a></b>, <b><a href="#quad">quad</a></b>, <b><a href="#quarter">quarter</a></b>, +tayste, tydbit</dd> + +<dt>4 bits:</dt> + +<dd>nybble</dd> + +<dt>5 bits:</dt> + +<dd><b><a href="#nickle">nickle</a></b></dd> + +<dt>10 bits:</dt> + +<dd><b><a href="#deckle">deckle</a></b></dd> + +<dt>16 bits:</dt> + +<dd>playte, <b><a href="#chawmp">chawmp</a></b> (on a 32-bit +machine), word (on a 16-bit machine), half-word (on a 32-bit +machine).</dd> + +<dt>18 bits:</dt> + +<dd><b><a href="#chawmp">chawmp</a></b> (on a 36-bit machine), +half-word (on a 36-bit machine)</dd> + +<dt>32 bits:</dt> + +<dd>dynner, <b><a href="#gawble">gawble</a></b> (on a 32-bit +machine), word (on a 32-bit machine), longword (on a 16-bit +machine).</dd> + +<dt>36:</dt> + +<dd>word (on a 36-bit machine)</dd> + +<dt>48 bits:</dt> + +<dd><b><a href="#gawble">gawble</a></b> (under circumstances that +remain obscure)</dd> + +<dt>64 bits</dt> + +<dd>double word (on a 32-bit machine)</dd> +</dl> +</blockquote> + +<p>The fundamental motivation for most of these jargon terms +(aside from the normal hackerly enjoyment of punning wordplay) is +the extreme ambiguity of the term `word' and its derivatives.</p> + +<hr> +Node:<a name="nyetwork">nyetwork</a>, Next:<a rel="next" href="#Ob-">Ob-</a>, Previous:<a rel="previous" href="#nybble">nybble</a>, Up:<a rel="up" href="#chap14">= N +=</a> <br> + + +<p><b>nyetwork</b> /nyet'werk/ n.</p> + +<p>[from Russian `nyet' = no] A network, when it is acting <b><a +href="#flaky">flaky</a></b> or is <b><a href="#down">down</a></b>. Compare <b><a href="#notwork">notwork</a></b>.</p> + +<hr> +Node:<a name="chap15">= O =</a>, Next:<a rel="next" href="#chap16">= P =</a>, Previous:<a rel="previous" href="#chap14">= N =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= O =</h2> + +<ul> +<li><a href="#Ob-">Ob-</a>:</li> + +<li><a href="#ObfuscatedCContest">Obfuscated C Contest</a>:</li> + +<li><a href="#obiwanerror">obi-wan error</a>:</li> + +<li><a href="#Objectionable-C">Objectionable-C</a>:</li> + +<li><a href="#obscure">obscure</a>:</li> + +<li><a href="#octalforty">octal forty</a>:</li> + +<li><a href="#offthetrolley">off the trolley</a>:</li> + +<li><a href="#offbyoneerror">off-by-one error</a>:</li> + +<li><a href="#offline">offline</a>:</li> + +<li><a href="#ogg">ogg</a>:</li> + +<li><a href="#-oid">-oid</a>:</li> + +<li><a href="#oldfart">old fart</a>:</li> + +<li><a href="#OldTestament">Old Testament</a>:</li> + +<li><a href="#onthegrippinghand">on the gripping hand</a>:</li> + +<li><a href="#one-bananaproblem">one-banana problem</a>:</li> + +<li><a href="#onelinefix">one-line fix</a>:</li> + +<li><a href="#onelinerwars">one-liner wars</a>:</li> + +<li><a href="#ooblick">ooblick</a>:</li> + +<li><a href="#op">op</a>:</li> + +<li><a href="#open">open</a>:</li> + +<li><a href="#opensource">open source</a>:</li> + +<li><a href="#openswitch">open switch</a>:</li> + +<li><a href="#operatingsystem">operating system</a>:</li> + +<li><a href="#opticaldiff">optical diff</a>:</li> + +<li><a href="#opticalgrep">optical grep</a>:</li> + +<li><a href="#optimism">optimism</a>:</li> + +<li><a href="#Oraclethe">Oracle the</a>:</li> + +<li><a href="#OrangeBook">Orange Book</a>:</li> + +<li><a href="#orientalfood">oriental food</a>:</li> + +<li><a href="#orphan">orphan</a>:</li> + +<li><a href="#orphanedinode">orphaned i-node</a>:</li> + +<li><a href="#orthogonal">orthogonal</a>:</li> + +<li><a href="#OS">OS</a>:</li> + +<li><a href="#OSslash2">OS/2</a>:</li> + +<li><a href="#OSS">OSS</a>:</li> + +<li><a href="#OSU">OSU</a>:</li> + +<li><a href="#OTOH">OTOH</a>:</li> + +<li><a href="#out-of-band">out-of-band</a>:</li> + +<li><a href="#overclock">overclock</a>:</li> + +<li><a href="#overflowbit">overflow bit</a>:</li> + +<li><a href="#overflowpdl">overflow pdl</a>:</li> + +<li><a href="#overrun">overrun</a>:</li> + +<li><a href="#overrunscrew">overrun screw</a>:</li> +</ul> + +<hr> +Node:<a name="Ob-">Ob-</a>, Next:<a rel="next" href="#ObfuscatedCContest">Obfuscated C Contest</a>, Previous:<a +rel="previous" href="#nyetwork">nyetwork</a>, Up:<a rel="up" +href="#chap15">= O =</a> <br> + + +<p><b>Ob-</b> /ob/ pref.</p> + +<p>Obligatory. A piece of <b><a href="#netiquette">netiquette</a></b> acknowledging that the author +has been straying from the newsgroup's charter topic. For +example, if a posting in alt.sex is a response to a part of +someone else's posting that has nothing particularly to do with +sex, the author may append `ObSex' (or `Obsex') and toss off a +question or vignette about some unusual erotic act. It is +considered a sign of great <b><a href="#winnitude">winnitude</a></b> when one's Obs are more +interesting than other people's whole postings.</p> + +<hr> +Node:<a name="ObfuscatedCContest">Obfuscated C Contest</a>, +Next:<a rel="next" href="#obiwanerror">obi-wan error</a>, +Previous:<a rel="previous" href="#Ob-">Ob-</a>, Up:<a rel="up" +href="#chap15">= O =</a> <br> + + +<p><b>Obfuscated C Contest</b> n.</p> + +<p>(in full, the `International Obfuscated C Code Contest', or +IOCCC) An annual contest run since 1984 over Usenet by Landon +Curt Noll and friends. The overall winner is whoever produces the +most unreadable, creative, and bizarre (but working) C program; +various other prizes are awarded at the judges' whim. C's terse +syntax and macro-preprocessor facilities give contestants a lot +of maneuvering room. The winning programs often manage to be +simultaneously (a) funny, (b) breathtaking works of art, and (c) +horrible examples of how <i>not</i> to code in C.</p> + +<p>This relatively short and sweet entry might help convey the +flavor of obfuscated C:</p> + +<pre> +<tt>/* + * HELLO WORLD program + * by Jack Applin and Robert Heckendorn, 1985 + * (Note: depends on being able to modify elements of argv[], + * which is not guaranteed by ANSI and often not possible.) + */ +main(v,c)char**c;{for(v[c++]="Hello, world!\n)"; +(!!c)[*c]&&(v--||--c&&execlp(*c,*c,c[!!c]+!!c,!c)); +**c=!c)write(!!*c,*c,!!**c);}</tt> +</pre> + +<p>Here's another good one:</p> + +<pre> +/* + * Program to compute an approximation of pi + * by Brian Westley, 1988 + * (requires pcc macro concatenation; try gcc -traditional-cpp) + */ + +#define _ -F<00||--F-OO--; +int F=00,OO=00; +main(){F_OO();printf("%1.3f\n",4.*-F/OO/OO);}F_OO() +{ + _-_-_-_ + _-_-_-_-_-_-_-_-_ + _-_-_-_-_-_-_-_-_-_-_-_ + _-_-_-_-_-_-_-_-_-_-_-_-_-_ + _-_-_-_-_-_-_-_-_-_-_-_-_-_-_ + _-_-_-_-_-_-_-_-_-_-_-_-_-_-_ +_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ +_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ +_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ +_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_ + _-_-_-_-_-_-_-_-_-_-_-_-_-_-_ + _-_-_-_-_-_-_-_-_-_-_-_-_-_-_ + _-_-_-_-_-_-_-_-_-_-_-_-_-_ + _-_-_-_-_-_-_-_-_-_-_-_ + _-_-_-_-_-_-_-_ + _-_-_-_ +} +</pre> + +<p>Note that this program works by computing its own area. For +more digits, write a bigger program. See also <b><a href="#helloworld">hello world</a></b>.</p> + +<p>The IOCCC has an official home page at http://www.ioccc.org.</p> + +<hr> +Node:<a name="obiwanerror">obi-wan error</a>, Next:<a rel="next" href="#Objectionable-C">Objectionable-C</a>, Previous:<a +rel="previous" href="#ObfuscatedCContest">Obfuscated C +Contest</a>, Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>obi-wan error</b> /oh'bee-won` er'*r/ n.</p> + +<p>[RPI, from `off-by-one' and the Obi-Wan Kenobi character in +"Star Wars"] A loop of some sort in which the index is off by 1. +Common when the index should have started from 0 but instead +started from 1. A kind of <b><a href="#offbyoneerror">off-by-one error</a></b>. See also <b><a +href="#zeroth">zeroth</a></b>.</p> + +<hr> +Node:<a name="Objectionable-C">Objectionable-C</a>, Next:<a rel="next" href="#obscure">obscure</a>, Previous:<a rel="previous" +href="#obiwanerror">obi-wan error</a>, Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>Objectionable-C</b> n.</p> + +<p>Hackish take on "Objective-C", the name of an object-oriented +dialect of C in competition with the better-known C++ (it is used +to write native applications on the NeXT machine). +Objectionable-C uses a Smalltalk-like syntax, but lacks the +flexibility of Smalltalk method calls, and (like many such +efforts) comes frustratingly close to attaining the <b><a href="#RightThing">Right Thing</a></b> without actually doing +so.</p> + +<hr> +Node:<a name="obscure">obscure</a>, Next:<a rel="next" href="#octalforty">octal forty</a>, Previous:<a rel="previous" +href="#Objectionable-C">Objectionable-C</a>, Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>obscure</b> adj.</p> + +<p>Used in an exaggeration of its normal meaning, to imply total +incomprehensibility. "The reason for that last crash is obscure." +"The <code>find(1)</code> command's syntax is obscure!" The +phrase `moderately obscure' implies that something could be +figured out but probably isn't worth the trouble. The +construction `obscure in the extreme' is the preferred emphatic +form.</p> + +<hr> +Node:<a name="octalforty">octal forty</a>, Next:<a rel="next" +href="#offthetrolley">off the trolley</a>, Previous:<a rel="previous" href="#obscure">obscure</a>, Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>octal forty</b> /ok'tl for'tee/ n.</p> + +<p>Hackish way of saying "I'm drawing a blank." Octal 40 is the +<b><a href="#ASCII">ASCII</a></b> space character, 0100000; by an +odd coincidence, <b><a href="#hex">hex</a></b> 40 (01000000) is +the <b><a href="#EBCDIC">EBCDIC</a></b> space character. See +<b><a href="#wall">wall</a></b>.</p> + +<hr> +Node:<a name="offthetrolley">off the trolley</a>, Next:<a +rel="next" href="#offbyoneerror">off-by-one error</a>, +Previous:<a rel="previous" href="#octalforty">octal forty</a>, +Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>off the trolley</b> adj.</p> + +<p>Describes the behavior of a program that malfunctions and goes +catatonic, but doesn't actually <b><a href="#crash">crash</a></b> +or abort. See <b><a href="#glitch">glitch</a></b>, <b><a href="#bug">bug</a></b>, <b><a href="#deepspace">deep +space</a></b>, <b><a href="#wedged">wedged</a></b>.</p> + +<p>This term is much older than computing, and is (uncommon) +slang elsewhere. A trolley is the small wheel that trolls, or +runs against, the heavy wire that carries the current to run a +streetcar. It's at the end of the long pole (the trolley pole) +that reaches from the roof of the streetcar to the overhead line. +When the trolley stops making contact with the wire (from passing +through a switch, going over bumpy track, or whatever), the +streetcar comes to a halt, (usually) without crashing. The +streetcar is then said to be off the trolley, or off the wire. +Later on, trolley came to mean the streetcar itself. Since +streetcars became common in the 1890s, the term is more than 100 +years old. Nowadays, trolleys are only seen on historic +streetcars, since modern streetcars use pantographs to contact +the wire.</p> + +<hr> +Node:<a name="offbyoneerror">off-by-one error</a>, Next:<a +rel="next" href="#offline">offline</a>, Previous:<a rel="previous" href="#offthetrolley">off the trolley</a>, Up:<a +rel="up" href="#chap15">= O =</a> <br> + + +<p><b>off-by-one error</b> n.</p> + +<p>[common] Exceedingly common error induced in many ways, such +as by starting at 0 when you should have started at 1 or +vice-versa, or by writing <code>< N</code> instead of +<code><= N</code> or vice-versa. Also applied to giving +something to the person next to the one who should have gotten +it. Often confounded with <b><a href="#fenceposterror">fencepost error</a></b>, which is properly a +particular subtype of it.</p> + +<hr> +Node:<a name="offline">offline</a>, Next:<a rel="next" href="#ogg">ogg</a>, Previous:<a rel="previous" href="#offbyoneerror">off-by-one error</a>, Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>offline</b> adv.</p> + +<p>Not now or not here. "Let's take this discussion offline." +Specifically used on <b><a href="#Usenet">Usenet</a></b> to +suggest that a discussion be moved off a public newsgroup to +email.</p> + +<hr> +Node:<a name="ogg">ogg</a>, Next:<a rel="next" href="#-oid">-oid</a>, Previous:<a rel="previous" href="#offline">offline</a>, Up:<a rel="up" href="#chap15">= O +=</a> <br> + + +<p><b>ogg</b> /og/ v.</p> + +<p>[CMU] 1. In the multi-player space combat game Netrek, to +execute kamikaze attacks against enemy ships which are carrying +armies or occupying strategic positions. Named during a game in +which one of the players repeatedly used the tactic while playing +Orion ship G, showing up in the player list as "Og". This trick +has been roundly denounced by those who would return to the good +old days when the tactic of dogfighting was dominant, but as Sun +Tzu wrote, "What is of supreme importance in war is to attack the +enemy's strategy, not his tactics." However, the traditional +answer to the newbie question "What does ogg mean?" is just "Pick +up some armies and I'll show you." 2. In other games, to +forcefully attack an opponent with the expectation that the +resources expended will be renewed faster than the opponent will +be able to regain his previous advantage. Taken more seriously as +a tactic since it has gained a simple name. 3. To do anything +forcefully, possibly without consideration of the drain on future +resources. "I guess I'd better go ogg the problem set that's due +tomorrow." "Whoops! I looked down at the map for a sec and almost +ogged that oncoming car."</p> + +<hr> +Node:<a name="-oid">-oid</a>, Next:<a rel="next" href="#oldfart">old fart</a>, Previous:<a rel="previous" href="#ogg">ogg</a>, Up:<a rel="up" href="#chap15">= O =</a> +<br> + + +<p><b>-oid</b> suff.</p> + +<p>[from Greek suffix -oid = `in the image of'] 1. Used as in +mainstream slang English to indicate a poor imitation, a +counterfeit, or some otherwise slightly bogus resemblance. +Hackers will happily use it with all sorts of non-Greco/Latin +stem words that wouldn't keep company with it in mainstream +English. For example, "He's a nerdoid" means that he +superficially resembles a nerd but can't make the grade; a +`modemoid' might be a 300-baud box (Real Modems run at 28.8 or +up); a `computeroid' might be any <b><a href="#bittybox">bitty +box</a></b>. The word `keyboid' could be used to describe a <b><a +href="#chicletkeyboard">chiclet keyboard</a></b>, but would +have to be written; spoken, it would confuse the listener as to +the speaker's city of origin. 2. More specifically, an indicator +for `resembling an android' which in the past has been confined +to science-fiction fans and hackers. It too has recently (in +1991) started to go mainstream (most notably in the term +`trendoid' for victims of terminal hipness). This is probably +traceable to the popularization of the term <b><a href="#droid">droid</a></b> in "Star Wars" and its sequels. (See also +<b><a href="#windoid">windoid</a></b>.)</p> + +<p>Coinages in both forms have been common in science fiction for +at least fifty years, and hackers (who are often SF fans) have +probably been making `-oid' jargon for almost that long [though +GLS and I can personally confirm only that they were already +common in the mid-1970s --ESR].</p> + +<hr> +Node:<a name="oldfart">old fart</a>, Next:<a rel="next" href="#OldTestament">Old Testament</a>, Previous:<a rel="previous" +href="#-oid">-oid</a>, Up:<a rel="up" href="#chap15">= O +=</a> <br> + + +<p><b>old fart</b> n.</p> + +<p>Tribal elder. A title self-assumed with remarkable frequency +by (esp.) Usenetters who have been programming for more than +about 25 years; often appears in <b><a href="#sigblock">sig +block</a></b>s attached to Jargon File contributions of great +archeological significance. This is a term of insult in the +second or third person but one of pride in first person.</p> + +<hr> +Node:<a name="OldTestament">Old Testament</a>, Next:<a rel="next" href="#onthegrippinghand">on the gripping +hand</a>, Previous:<a rel="previous" href="#oldfart">old +fart</a>, Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>Old Testament</b> n.</p> + +<p>[C programmers] The first edition of <b><a href="#KandR">K&R</a></b>, the sacred text describing <b><a +href="#ClassicC">Classic C</a></b>.</p> + +<hr> +Node:<a name="onthegrippinghand">on the gripping +hand</a>, Next:<a rel="next" href="#one-bananaproblem">one-banana problem</a>, Previous:<a rel="previous" href="#OldTestament">Old Testament</a>, Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>on the gripping hand</b></p> + +<p>In the progression that starts "On the one hand..." and +continues "On the other hand..." mainstream English may add "on +the third hand..." even though most people don't have three +hands. Among hackers, it is just as likely to be "on the gripping +hand". This metaphor supplied the title of Larry Niven & +Jerry Pournelle's 1993 SF novel "The Gripping Hand" which +involved a species of hostile aliens with three arms (the same +species, in fact, referenced in <b><a href="#jugglingeggs">juggling eggs</a></b>). As with <b><a href="#TANSTAAFL">TANSTAAFL</a></b> and <b><a href="#con">con</a></b>, +this usage one of the naturalized imports from SF fandom +frequently observed among hackers.</p> + +<hr> +Node:<a name="one-bananaproblem">one-banana problem</a>, +Next:<a rel="next" href="#onelinefix">one-line fix</a>, +Previous:<a rel="previous" href="#onthegrippinghand">on +the gripping hand</a>, Up:<a rel="up" href="#chap15">= O +=</a> <br> + + +<p><b>one-banana problem</b> n.</p> + +<p>At mainframe shops, where the computers have operators for +routine administrivia, the programmers and hardware people tend +to look down on the operators and claim that a trained monkey +could do their job. It is frequently observed that the incentives +that would be offered said monkeys can be used as a scale to +describe the difficulty of a task. A one-banana problem is +simple; hence, "It's only a one-banana job at the most; what's +taking them so long?"</p> + +<p>At IBM, folklore divides the world into one-, two-, and +three-banana problems. Other cultures have different hierarchies +and may divide them more finely; at ICL, for example, five grapes +(a bunch) equals a banana. Their upper limit for the in-house +<b><a href="#sysape">sysape</a></b>s is said to be two bananas +and three grapes (another source claims it's three bananas and +one grape, but observes "However, this is subject to local +variations, cosmic rays and ISO"). At a complication level any +higher than that, one asks the manufacturers to send someone +around to check things.</p> + +<p>See also <b><a href="#InfiniteMonkeyTheorem">Infinite-Monkey Theorem</a></b>.</p> + +<hr> +Node:<a name="onelinefix">one-line fix</a>, Next:<a rel="next" href="#onelinerwars">one-liner wars</a>, Previous:<a +rel="previous" href="#one-bananaproblem">one-banana +problem</a>, Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>one-line fix</b> n.</p> + +<p>Used (often sarcastically) of a change to a program that is +thought to be trivial or insignificant right up to the moment it +crashes the system. Usually `cured' by another one-line fix. See +also <b><a href="#Ididntchangeanything">I didn't +change anything!</a></b></p> + +<hr> +Node:<a name="onelinerwars">one-liner wars</a>, Next:<a rel="next" href="#ooblick">ooblick</a>, Previous:<a rel="previous" +href="#onelinefix">one-line fix</a>, Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>one-liner wars</b> n.</p> + +<p>A game popular among hackers who code in the language APL (see +<b><a href="#writeonlylanguage">write-only language</a></b> +and <b><a href="#linenoise">line noise</a></b>). The objective +is to see who can code the most interesting and/or useful routine +in one line of operators chosen from APL's exceedingly <b><a +href="#hairy">hairy</a></b> primitive set. A similar amusement +was practiced among <b><a href="#TECO">TECO</a></b> hackers and +is now popular among <b><a href="#Perl">Perl</a></b> +aficionados.</p> + +<p>Ken Iverson, the inventor of APL, has been credited with a +one-liner that, given a number N, produces a list of the prime +numbers from 1 to N inclusive. It looks like this:</p> + +<p>(2 = 0 +.= T o.| T) / T <- iN</p> + +<p>where `o' is the APL null character, the assignment arrow is a +single character, and `i' represents the APL iota.</p> + +<p>Here's a <b><a href="#Perl">Perl</a></b> program that prints +primes:</p> + +<pre> + perl -wle '(1 x $_) !~ /^(11+)\1+$/ && print while ++ $_' +</pre> + +<p>In the Perl world this game is sometimes called Perl Golf +because the player with the fewest (key)strokes wins.</p> + +<hr> +Node:<a name="ooblick">ooblick</a>, Next:<a rel="next" href="#op">op</a>, Previous:<a rel="previous" href="#onelinerwars">one-liner wars</a>, Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>ooblick</b> /oo'blik/ n.</p> + +<p>[from the Dr. Seuss title "Bartholomew and the Oobleck"; the +spelling `oobleck' is still current in the mainstream] A bizarre +semi-liquid sludge made from cornstarch and water. Enjoyed among +hackers who make batches during playtime at parties for its +amusing and extremely non-Newtonian behavior; it pours and +splatters, but resists rapid motion like a solid and will even +crack when hit by a hammer. Often found near lasers.</p> + +<p>Here is a field-tested ooblick recipe contributed by GLS:</p> + +<dl> +<dt>1 cup cornstarch</dt> + +<dt>1 cup baking soda</dt> + +<dt>3/4 cup water</dt> + +<dt>N drops of food coloring</dt> +</dl> + +<p>This recipe isn't quite as non-Newtonian as a pure cornstarch +ooblick, but has an appropriately slimy feel.</p> + +<p>Some, however, insist that the notion of an ooblick +<i>recipe</i> is far too mechanical, and that it is best to add +the water in small increments so that the various mixed states +the cornstarch goes through as it <i>becomes</i> ooblick can be +grokked in fullness by many hands. For optional ingredients of +this experience, see the "<b><a href="#CeremonialChemicals">Ceremonial Chemicals</a></b>" section +of Appendix B.</p> + +<hr> +Node:<a name="op">op</a>, Next:<a rel="next" href="#open">open</a>, Previous:<a rel="previous" href="#ooblick">ooblick</a>, Up:<a rel="up" href="#chap15">= O +=</a> <br> + + +<p><b>op</b> /op/ n.</p> + +<p>1. In England and Ireland, common verbal abbreviation for +`operator', as in system operator. Less common in the U.S., where +<b><a href="#sysop">sysop</a></b> seems to be preferred. 2. [IRC] +Someone who is endowed with privileges on <b><a href="#IRC">IRC</a></b>, not limited to a particular channel. These +are generally people who are in charge of the IRC server at their +particular site. Sometimes used interchangeably with <b><a href="#CHOP">CHOP</a></b>. Compare <b><a href="#sysop">sysop</a></b>.</p> + +<hr> +Node:<a name="open">open</a>, Next:<a rel="next" href="#opensource">open source</a>, Previous:<a rel="previous" +href="#op">op</a>, Up:<a rel="up" href="#chap15">= O =</a> +<br> + + +<p><b>open</b> n.</p> + +<p>Abbreviation for `open (or left) parenthesis' -- used when +necessary to eliminate oral ambiguity. To read aloud the LISP +form (DEFUN FOO (X) (PLUS X 1)) one might say: "Open defun foo, +open eks close, open, plus eks one, close close."</p> + +<hr> +Node:<a name="opensource">open source</a>, Next:<a rel="next" +href="#openswitch">open switch</a>, Previous:<a rel="previous" +href="#open">open</a>, Up:<a rel="up" href="#chap15">= O +=</a> <br> + + +<p><b>open source</b> n.</p> + +<p>[common; also adj. `open-source'] Term coined in March 1998 +following the Mozilla release to describe software distributed in +source under licenses guaranteeing anybody rights to freely use, +modify, and redistribute, the code. The intent was to be able to +sell the hackers' ways of doing software to industry and the +mainstream by avoid the negative connotations (to <b><a href="#suit">suit</a></b>s) of the term "<b><a href="#freesoftware">free software</a></b>". For discussion of the +followon tactics and their consequences, see the Open Source Initiative site.</p> + +<hr> +Node:<a name="openswitch">open switch</a>, Next:<a rel="next" +href="#operatingsystem">operating system</a>, Previous:<a rel="previous" href="#opensource">open source</a>, Up:<a rel="up" +href="#chap15">= O =</a> <br> + + +<p><b>open switch</b> n.</p> + +<p>[IBM: prob. from railroading] An unresolved question, issue, +or problem.</p> + +<hr> +Node:<a name="operatingsystem">operating system</a>, Next:<a +rel="next" href="#opticaldiff">optical diff</a>, Previous:<a +rel="previous" href="#openswitch">open switch</a>, Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>operating system</b> n.</p> + +<p>[techspeak] (Often abbreviated `OS') The foundation software +of a machine; that which schedules tasks, allocates storage, and +presents a default interface to the user between applications. +The facilities an operating system provides and its general +design philosophy exert an extremely strong influence on +programming style and on the technical cultures that grow up +around its host machines. Hacker folklore has been shaped +primarily by the <b><a href="#Unix">Unix</a></b>, <b><a href="#ITS">ITS</a></b>, <b><a href="#TOPS-10">TOPS-10</a></b>, <b><a +href="#TOPS-20">TOPS-20</a></b>/<b><a href="#TWENEX">TWENEX</a></b>, <b><a href="#WAITS">WAITS</a></b>, +<b><a href="#CPM">CP/M</a></b>, <b><a href="#MS-DOS">MS-DOS</a></b>, and <b><a href="#Multics">Multics</a></b> operating systems (most importantly by +ITS and Unix).</p> + +<hr> +Node:<a name="opticaldiff">optical diff</a>, Next:<a rel="next" href="#opticalgrep">optical grep</a>, Previous:<a rel="previous" href="#operatingsystem">operating system</a>, Up:<a +rel="up" href="#chap15">= O =</a> <br> + + +<p><b>optical diff</b> n.</p> + +<p>See <b><a href="#vdiff">vdiff</a></b>.</p> + +<hr> +Node:<a name="opticalgrep">optical grep</a>, Next:<a rel="next" href="#optimism">optimism</a>, Previous:<a rel="previous" +href="#opticaldiff">optical diff</a>, Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>optical grep</b> n.</p> + +<p>See <b><a href="#vgrep">vgrep</a></b>.</p> + +<hr> +Node:<a name="optimism">optimism</a>, Next:<a rel="next" href="#Oraclethe">Oracle the</a>, Previous:<a rel="previous" href="#opticalgrep">optical grep</a>, Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>optimism</b> n.</p> + +<p>What a programmer is full of after fixing the last bug and +before discovering the <i>next</i> last bug. Fred Brooks's book +"The Mythical Man-Month" (See "Brooks's Law") contains the +following paragraph that describes this extremely well:</p> + +<blockquote>All programmers are optimists. Perhaps this modern +sorcery especially attracts those who believe in happy endings +and fairy godmothers. Perhaps the hundreds of nitty frustrations +drive away all but those who habitually focus on the end goal. +Perhaps it is merely that computers are young, programmers are +younger, and the young are always optimists. But however the +selection process works, the result is indisputable: "This time +it will surely run," or "I just found the last +bug.".</blockquote> + +<p>See also <b><a href="#LubarskysLawofCyberneticEntomology">Lubarsky's Law +of Cybernetic Entomology</a></b>.</p> + +<hr> +Node:<a name="Oraclethe">Oracle the</a>, Next:<a rel="next" +href="#OrangeBook">Orange Book</a>, Previous:<a rel="previous" +href="#optimism">optimism</a>, Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>Oracle, the</b></p> + +<p>The all-knowing, all-wise Internet Oracle +<i>rec.humor.oracle</i>), or one of the foreign language +derivatives of same. Newbies frequently confuse the Oracle with +Oracle, a database vendor. As a result, the unmoderated +<i>rec.humor.oracle.d</i> is frequently crossposted to by the +clueless, looking for advice on SQL. As more than one person has +said in similar situations, "Don't people bother to look at the +newsgroup description line anymore?" (To which the standard +response is, "Did people ever read it in the first place?")</p> + +<hr> +Node:<a name="OrangeBook">Orange Book</a>, Next:<a rel="next" +href="#orientalfood">oriental food</a>, Previous:<a rel="previous" href="#Oraclethe">Oracle the</a>, Up:<a rel="up" +href="#chap15">= O =</a> <br> + + +<p><b>Orange Book</b> n.</p> + +<p>The U.S. Government's standards document "Trusted Computer +System Evaluation Criteria, DOD standard 5200.28-STD, December, +1985" which characterize secure computing architectures and +defines levels A1 (most secure) through D (least). Modern Unixes +are roughly C2. See also <b><a href="#crayolabooks">crayola +books</a></b>, <b><a href="#booktitles">book +titles</a></b>.</p> + +<hr> +Node:<a name="orientalfood">oriental food</a>, Next:<a rel="next" href="#orphan">orphan</a>, Previous:<a rel="previous" +href="#OrangeBook">Orange Book</a>, Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>oriental food</b> n.</p> + +<p>Hackers display an intense tropism towards oriental cuisine, +especially Chinese, and especially of the spicier varieties such +as Szechuan and Hunan. This phenomenon (which has also been +observed in subcultures that overlap heavily with hackerdom, most +notably science-fiction fandom) has never been satisfactorily +explained, but is sufficiently intense that one can assume the +target of a hackish dinner expedition to be the best local +Chinese place and be right at least three times out of four. See +also <b><a href="#ravs">ravs</a></b>, <b><a href="#great-wall">great-wall</a></b>, <b><a href="#stirfriedrandom">stir-fried random</a></b>, <b><a href="#laserchicken">laser chicken</a></b>, <b><a href="#YuShiangWholeFish">Yu-Shiang Whole Fish</a></b>. Thai, +Indian, Korean, and Vietnamese cuisines are also quite +popular.</p> + +<hr> +Node:<a name="orphan">orphan</a>, Next:<a rel="next" href="#orphanedinode">orphaned i-node</a>, Previous:<a rel="previous" href="#orientalfood">oriental food</a>, Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>orphan</b> n.</p> + +<p>[Unix] A process whose parent has died; one inherited by +<code>init(1)</code>. Compare <b><a href="#zombie">zombie</a></b>.</p> + +<hr> +Node:<a name="orphanedinode">orphaned i-node</a>, Next:<a +rel="next" href="#orthogonal">orthogonal</a>, Previous:<a rel="previous" href="#orphan">orphan</a>, Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>orphaned i-node</b> /or'f*nd i:'nohd/ n.</p> + +<p>[Unix] 1. [techspeak] A file that retains storage but no +longer appears in the directories of a filesystem. 2. By +extension, a pejorative for any person no longer serving a useful +function within some organization, esp. <b><a href="#lionfood">lion food</a></b> without subordinates.</p> + +<hr> +Node:<a name="orthogonal">orthogonal</a>, Next:<a rel="next" +href="#OS">OS</a>, Previous:<a rel="previous" href="#orphanedinode">orphaned i-node</a>, Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>orthogonal</b> adj.</p> + +<p>[from mathematics] Mutually independent; well separated; +sometimes, irrelevant to. Used in a generalization of its +mathematical meaning to describe sets of primitives or +capabilities that, like a vector basis in geometry, span the +entire `capability space' of the system and are in some sense +non-overlapping or mutually independent. For example, in +architectures such as the PDP-11 or VAX where all or nearly all +registers can be used interchangeably in any role with respect to +any instruction, the register set is said to be orthogonal. Or, +in logic, the set of operators `not' and `or' is orthogonal, but +the set `nand', `or', and `not' is not (because any one of these +can be expressed in terms of the others). Also used in comments +on human discourse: "This may be orthogonal to the discussion, +but<small>...</small>."</p> + +<hr> +Node:<a name="OS">OS</a>, Next:<a rel="next" href="#OSslash2">OS/2</a>, Previous:<a rel="previous" href="#orthogonal">orthogonal</a>, Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>OS</b> /O-S/</p> + +<p>1. [Operating System] n. An abbreviation heavily used in +email, occasionally in speech. 2. n. obs. On ITS, an output spy. +See "<b><a href="#OSandJEDGAR">OS and JEDGAR</a></b>" in +Appendix A.</p> + +<hr> +Node:<a name="OSslash2">OS/2</a>, Next:<a rel="next" href="#OSS">OSS</a>, Previous:<a rel="previous" href="#OS">OS</a>, +Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>OS/2</b> /O S too/ n.</p> + +<p>The anointed successor to MS-DOS for Intel 286- and 386-based +micros; proof that IBM/Microsoft couldn't get it right the second +time, either. Often called `Half-an-OS'. Mentioning it is usually +good for a cheap laugh among hackers -- the design was so <b><a +href="#baroque">baroque</a></b>, and the implementation of 1.x so +bad, that 3 years after introduction you could still count the +major <b><a href="#app">app</a></b>s shipping for it on the +fingers of two hands -- in unary. The 2.x versions are said to +have improved somewhat, and informed hackers now rate them +superior to Microsoft Windows (an endorsement which, however, +could easily be construed as damning with faint praise). See +<b><a href="#monstrosity">monstrosity</a></b>, <b><a href="#cretinous">cretinous</a></b>, <b><a href="#second-systemeffect">second-system effect</a></b>.</p> + +<hr> +Node:<a name="OSS">OSS</a>, Next:<a rel="next" href="#OSU">OSU</a>, Previous:<a rel="previous" href="#OSslash2">OS/2</a>, Up:<a rel="up" href="#chap15">= O +=</a> <br> + + +<p><b>OSS</b></p> + +<p>Written-only acronym for "Open Source Software" (see <b><a +href="#opensource">open source</a></b>. This is a rather ugly +<b><a href="#TLA">TLA</a></b>, and the principals in the +open-source movement don't use it, but it has (perhaps +inevitably) spread through the trade press like kudzu.</p> + +<hr> +Node:<a name="OSU">OSU</a>, Next:<a rel="next" href="#OTOH">OTOH</a>, Previous:<a rel="previous" href="#OSS">OSS</a>, +Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>OSU</b> /O-S-U/ n. obs.</p> + +<p>[TMRC] Acronym for Officially Sanctioned User; a user who is +recognized as such by the computer authorities and allowed to use +the computer above the objections of the security monitor.</p> + +<hr> +Node:<a name="OTOH">OTOH</a>, Next:<a rel="next" href="#out-of-band">out-of-band</a>, Previous:<a rel="previous" href="#OSU">OSU</a>, Up:<a rel="up" href="#chap15">= O =</a> +<br> + + +<p><b>OTOH</b> //</p> + +<p>[Usenet; very common] On The Other Hand.</p> + +<hr> +Node:<a name="out-of-band">out-of-band</a>, Next:<a rel="next" +href="#overclock">overclock</a>, Previous:<a rel="previous" href="#OTOH">OTOH</a>, Up:<a rel="up" href="#chap15">= O =</a> +<br> + + +<p><b>out-of-band</b> adj.</p> + +<p>[from telecommunications and network theory] 1. In software, +describes values of a function which are not in its `natural' +range of return values, but are rather signals that some kind of +exception has occurred. Many C functions, for example, return a +nonnegative integral value, but indicate failure with an +out-of-band return value of -1. Compare <b><a href="#hiddenflag">hidden flag</a></b>, <b><a href="#greenbytes">green bytes</a></b>, <b><a href="#fence">fence</a></b>. 2. Also sometimes used to describe what +communications people call `shift characters', such as the ESC +that leads control sequences for many terminals, or the level +shift indicators in the old 5-bit Baudot codes. 3. In personal +communication, using methods other than email, such as telephones +or <b><a href="#snail-mail">snail-mail</a></b>.</p> + +<hr> +Node:<a name="overclock">overclock</a>, Next:<a rel="next" href="#overflowbit">overflow bit</a>, Previous:<a rel="previous" +href="#out-of-band">out-of-band</a>, Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>overclock</b> /oh'vr-klok'/ vt.</p> + +<p>To operate a CPU or other digital logic device at a rate +higher than it was designed for, under the assumption that the +manufacturer put some <b><a href="#slop">slop</a></b> into the +specification to account for manufacturing tolerances. +Overclocking something can result in intermittent <b><a href="#crash">crash</a></b>es, and can even burn things out, since +power dissipation is directly proportional to <b><a href="#clock">clock</a></b> frequency. People who make a hobby of this +are sometimes called "overclockers"; they are thrilled that they +can run their 450MHz CPU at 500MHz, even though they can only +tell the difference by running a <b><a href="#benchmark">benchmark</a></b> program.</p> + +<hr> +Node:<a name="overflowbit">overflow bit</a>, Next:<a rel="next" href="#overflowpdl">overflow pdl</a>, Previous:<a rel="previous" href="#overclock">overclock</a>, Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>overflow bit</b> n.</p> + +<p>1. [techspeak] A <b><a href="#flag">flag</a></b> on some +processors indicating an attempt to calculate a result too large +for a register to hold. 2. More generally, an indication of any +kind of capacity overload condition. "Well, the <b><a href="#Ada">Ada</a></b> description was <b><a href="#baroque">baroque</a></b> all right, but I could hack it OK +until they got to the exception handling <small>...</small> that +set my overflow bit." 3. The hypothetical bit that will be set if +a hacker doesn't get to make a trip to the Room of Porcelain +Fixtures: "I'd better process an internal interrupt before the +overflow bit gets set."</p> + +<hr> +Node:<a name="overflowpdl">overflow pdl</a>, Next:<a rel="next" href="#overrun">overrun</a>, Previous:<a rel="previous" +href="#overflowbit">overflow bit</a>, Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>overflow pdl</b> n.</p> + +<p>[MIT] The place where you put things when your <b><a href="#PDL">PDL</a></b> is full. If you don't have one and too many +things get pushed, you forget something. The overflow pdl for a +person's memory might be a memo pad. This usage inspired the +following doggerel:</p> + +<blockquote>Hey, diddle, diddle<br> +The overflow pdl<br> + To get a little more stack;<br> +If that's not enough<br> +Then you lose it all,<br> + And have to pop all the way back.<br> + -The Great Quux</blockquote> + +<p>The term `pdl' (see <b><a href="#PDL">PDL</a></b>) seems to be +primarily an MITism; outside MIT this term is replaced by +`overflow <b><a href="#stack">stack</a></b>' (but that wouldn't +rhyme with `diddle').</p> + +<hr> +Node:<a name="overrun">overrun</a>, Next:<a rel="next" href="#overrunscrew">overrun screw</a>, Previous:<a rel="previous" +href="#overflowpdl">overflow pdl</a>, Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>overrun</b> n.</p> + +<p>1. [techspeak] Term for a frequent consequence of data +arriving faster than it can be consumed, esp. in serial line +communications. For example, at 9600 baud there is almost exactly +one character per millisecond, so if a <b><a href="#silo">silo</a></b> can hold only two characters and the machine +takes longer than 2 msec to get to service the interrupt, at +least one character will be lost. 2. Also applied to +non-serial-I/O communications. "I forgot to pay my electric bill +due to mail overrun." "Sorry, I got four phone calls in 3 minutes +last night and lost your message to overrun." When <b><a href="#thrash">thrash</a></b>ing at tasks, the next person to make a +request might be told "Overrun!" Compare <b><a href="#firehosesyndrome">firehose syndrome</a></b>. 3. More +loosely, may refer to a <b><a href="#bufferoverflow">buffer +overflow</a></b> not necessarily related to processing time (as +in <b><a href="#overrunscrew">overrun screw</a></b>).</p> + +<hr> +Node:<a name="overrunscrew">overrun screw</a>, Next:<a rel="next" href="#P-mail">P-mail</a>, Previous:<a rel="previous" +href="#overrun">overrun</a>, Up:<a rel="up" href="#chap15">= O =</a> <br> + + +<p><b>overrun screw</b> n.</p> + +<p>[C programming] A variety of <b><a href="#fandangooncore">fandango on core</a></b> produced by +scribbling past the end of an array (C implementations typically +have no checks for this error). This is relatively benign and +easy to spot if the array is static; if it is auto, the result +may be to <b><a href="#smashthestack">smash the +stack</a></b> -- often resulting in <b><a href="#heisenbug">heisenbug</a></b>s of the most diabolical subtlety. +The term `overrun screw' is used esp. of scribbles beyond the end +of arrays allocated with <code>malloc(3)</code>; this typically +trashes the allocation header for the next block in the <b><a +href="#arena">arena</a></b>, producing massive lossage within +malloc and often a core dump on the next operation to use +<code>stdio(3)</code> or <code>malloc(3)</code> itself. See <b><a +href="#spam">spam</a></b>, <b><a href="#overrun">overrun</a></b>; +see also <b><a href="#memoryleak">memory leak</a></b>, <b><a +href="#memorysmash">memory smash</a></b>, <b><a href="#aliasingbug">aliasing bug</a></b>, <b><a href="#precedencelossage">precedence lossage</a></b>, <b><a href="#fandangooncore">fandango on core</a></b>, <b><a href="#secondarydamage">secondary damage</a></b>.</p> + +<hr> +Node:<a name="chap16">= P =</a>, Next:<a rel="next" href="#chap17">= Q =</a>, Previous:<a rel="previous" href="#chap15">= O =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= P =</h2> + +<ul> +<li><a href="#P-mail">P-mail</a>:</li> + +<li><a href="#P.O.D.">P.O.D.</a>:</li> + +<li><a href="#packetoverair">packet over air</a>:</li> + +<li><a href="#paddedcell">padded cell</a>:</li> + +<li><a href="#pagein">page in</a>:</li> + +<li><a href="#pageout">page out</a>:</li> + +<li><a href="#paininthenet">pain in the net</a>:</li> + +<li><a href="#Panglossparity">Pangloss parity</a>:</li> + +<li><a href="#paper-net">paper-net</a>:</li> + +<li><a href="#param">param</a>:</li> + +<li><a href="#PARC">PARC</a>:</li> + +<li><a href="#parentmessage">parent message</a>:</li> + +<li><a href="#parityerrors">parity errors</a>:</li> + +<li><a href="#ParkinsonsLawofData">Parkinson's Law of Data</a>:</li> + +<li><a href="#parm">parm</a>:</li> + +<li><a href="#parse">parse</a>:</li> + +<li><a href="#Pascal">Pascal</a>:</li> + +<li><a href="#pastie">pastie</a>:</li> + +<li><a href="#patch">patch</a>:</li> + +<li><a href="#patchpumpkin">patch pumpkin</a>:</li> + +<li><a href="#patchspace">patch space</a>:</li> + +<li><a href="#path">path</a>:</li> + +<li><a href="#pathological">pathological</a>:</li> + +<li><a href="#payware">payware</a>:</li> + +<li><a href="#PBD">PBD</a>:</li> + +<li><a href="#PC-ism">PC-ism</a>:</li> + +<li><a href="#PD">PD</a>:</li> + +<li><a href="#PDL">PDL</a>:</li> + +<li><a href="#PDP-10">PDP-10</a>:</li> + +<li><a href="#PDP-20">PDP-20</a>:</li> + +<li><a href="#PEBKAC">PEBKAC</a>:</li> + +<li><a href="#peek">peek</a>:</li> + +<li><a href="#pencilandpaper">pencil and paper</a>:</li> + +<li><a href="#PentagramPro">Pentagram Pro</a>:</li> + +<li><a href="#Pentium">Pentium</a>:</li> + +<li><a href="#peon">peon</a>:</li> + +<li><a href="#percent-S">percent-S</a>:</li> + +<li><a href="#perf">perf</a>:</li> + +<li><a href="#perfectprogrammersyndrome">perfect programmer syndrome</a>:</li> + +<li><a href="#Perl">Perl</a>:</li> + +<li><a href="#personofnoaccount">person of no account</a>:</li> + +<li><a href="#pessimal">pessimal</a>:</li> + +<li><a href="#pessimizingcompiler">pessimizing compiler</a>:</li> + +<li><a href="#peta-">peta-</a>:</li> + +<li><a href="#PETSCII">PETSCII</a>:</li> + +<li><a href="#PFY">PFY</a>:</li> + +<li><a href="#phage">phage</a>:</li> + +<li><a href="#phase">phase</a>:</li> + +<li><a href="#phaseofthemoon">phase of the moon</a>:</li> + +<li><a href="#phase-wrapping">phase-wrapping</a>:</li> + +<li><a href="#PHB">PHB</a>:</li> + +<li><a href="#phreaker">phreaker</a>:</li> + +<li><a href="#phreaking">phreaking</a>:</li> + +<li><a href="#pico-">pico-</a>:</li> + +<li><a href="#pig-tail">pig-tail</a>:</li> + +<li><a href="#piloterror">pilot error</a>:</li> + +<li><a href="#ping">ping</a>:</li> + +<li><a href="#PingODeath">Ping O' Death</a>:</li> + +<li><a href="#pingstorm">ping storm</a>:</li> + +<li><a href="#pinkwire">pink wire</a>:</li> + +<li><a href="#pipe">pipe</a>:</li> + +<li><a href="#pistol">pistol</a>:</li> + +<li><a href="#pixelsort">pixel sort</a>:</li> + +<li><a href="#pizzabox">pizza box</a>:</li> + +<li><a href="#plaidscreen">plaid screen</a>:</li> + +<li><a href="#plain-ASCII">plain-ASCII</a>:</li> + +<li><a href="#planfile">plan file</a>:</li> + +<li><a href="#platinum-iridium">platinum-iridium</a>:</li> + +<li><a href="#playpen">playpen</a>:</li> + +<li><a href="#playte">playte</a>:</li> + +<li><a href="#plingnet">plingnet</a>:</li> + +<li><a href="#plokta">plokta</a>:</li> + +<li><a href="#plonk">plonk</a>:</li> + +<li><a href="#plug-and-pray">plug-and-pray</a>:</li> + +<li><a href="#plugh">plugh</a>:</li> + +<li><a href="#plumbing">plumbing</a>:</li> + +<li><a href="#PM">PM</a>:</li> + +<li><a href="#pnambic">pnambic</a>:</li> + +<li><a href="#pod">pod</a>:</li> + +<li><a href="#pointanddroolinterface">point-and-drool interface</a>:</li> + +<li><a href="#pointyhat">pointy hat</a>:</li> + +<li><a href="#pointy-haired">pointy-haired</a>:</li> + +<li><a href="#poke">poke</a>:</li> + +<li><a href="#poll">poll</a>:</li> + +<li><a href="#polygonpusher">polygon pusher</a>:</li> + +<li><a href="#POM">POM</a>:</li> + +<li><a href="#pop">pop</a>:</li> + +<li><a href="#POPJ">POPJ</a>:</li> + +<li><a href="#poser">poser</a>:</li> + +<li><a href="#post">post</a>:</li> + +<li><a href="#postcardware">postcardware</a>:</li> + +<li><a href="#posting">posting</a>:</li> + +<li><a href="#postmaster">postmaster</a>:</li> + +<li><a href="#PostScript">PostScript</a>:</li> + +<li><a href="#poundon">pound on</a>:</li> + +<li><a href="#powercycle">power cycle</a>:</li> + +<li><a href="#powerhit">power hit</a>:</li> + +<li><a href="#PPN">PPN</a>:</li> + +<li><a href="#pr0n">pr0n</a>:</li> + +<li><a href="#precedencelossage">precedence lossage</a>:</li> + +<li><a href="#prepend">prepend</a>:</li> + +<li><a href="#prestidigitization">prestidigitization</a>:</li> + +<li><a href="#prettypictures">pretty pictures</a>:</li> + +<li><a href="#prettyprint">prettyprint</a>:</li> + +<li><a href="#pretzelkey">pretzel key</a>:</li> + +<li><a href="#priesthood">priesthood</a>:</li> + +<li><a href="#primeTime">prime time</a>:</li> + +<li><a href="#print">print</a>:</li> + +<li><a href="#printingdiscussion">printing discussion</a>:</li> + +<li><a href="#priorityinterrupt">priority interrupt</a>:</li> + +<li><a href="#profile">profile</a>:</li> + +<li><a href="#progasm">progasm</a>:</li> + +<li><a href="#proggy">proggy</a>:</li> + +<li><a href="#proglet">proglet</a>:</li> + +<li><a href="#program">program</a>:</li> + +<li><a href="#ProgrammersCheer">Programmer's Cheer</a>:</li> + +<li><a href="#programming">programming</a>:</li> + +<li><a href="#programmingfluid">programming fluid</a>:</li> + +<li><a href="#propellerhead">propeller head</a>:</li> + +<li><a href="#propellerkey">propeller key</a>:</li> + +<li><a href="#proprietary">proprietary</a>:</li> + +<li><a href="#protocol">protocol</a>:</li> + +<li><a href="#provocativemaintenance">provocative maintenance</a>:</li> + +<li><a href="#prowler">prowler</a>:</li> + +<li><a href="#pseudo">pseudo</a>:</li> + +<li><a href="#pseudoprime">pseudoprime</a>:</li> + +<li><a href="#pseudosuit">pseudosuit</a>:</li> + +<li><a href="#psychedelicware">psychedelicware</a>:</li> + +<li><a href="#psyton">psyton</a>:</li> + +<li><a href="#pubicdirectory">pubic directory</a>:</li> + +<li><a href="#puff">puff</a>:</li> + +<li><a href="#pumpkinholder">pumpkin holder</a>:</li> + +<li><a href="#pumpking">pumpking</a>:</li> + +<li><a href="#punchedcard">punched card</a>:</li> + +<li><a href="#punt">punt</a>:</li> + +<li><a href="#PurpleBook">Purple Book</a>:</li> + +<li><a href="#purplewire">purple wire</a>:</li> + +<li><a href="#push">push</a>:</li> + +<li><a href="#Python">Python</a>:</li> +</ul> + +<hr> +Node:<a name="P-mail">P-mail</a>, Next:<a rel="next" href="#P.O.D.">P.O.D.</a>, Previous:<a rel="previous" href="#overrunscrew">overrun screw</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>P-mail</b> n.</p> + +<p>[rare] Physical mail, as opposed to <b><a href="#email">email</a></b>. Synonymous with <b><a href="#snail-mail">snail-mail</a></b>, but much less common.</p> + +<hr> +Node:<a name="P.O.D.">P.O.D.</a>, Next:<a rel="next" href="#packetoverair">packet over air</a>, Previous:<a rel="previous" href="#P-mail">P-mail</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>P.O.D.</b> /P-O-D/</p> + +<p>[rare] Acronym for `Piece Of Data' (as opposed to a code +section). See also <b><a href="#pod">pod</a></b>.</p> + +<hr> +Node:<a name="packetoverair">packet over air</a>, Next:<a +rel="next" href="#paddedcell">padded cell</a>, Previous:<a +rel="previous" href="#P.O.D.">P.O.D.</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>packet over air</b></p> + +<p>[common among backbone ISPs] The protocol notionally being +used by Internet data attempting to traverse a physical gap or +break in the network, such as might be caused by a <b><a href="#fiber-seekingbackhoe">fiber-seeking backhoe</a></b>. "I see +why you're dropping packets. You seem to have a packet over air +problem.</p> + +<hr> +Node:<a name="paddedcell">padded cell</a>, Next:<a rel="next" +href="#pagein">page in</a>, Previous:<a rel="previous" href="#packetoverair">packet over air</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>padded cell</b> n.</p> + +<p>Where you put <b><a href="#luser">luser</a></b>s so they can't +hurt anything. A program that limits a luser to a carefully +restricted subset of the capabilities of the host system (for +example, the <code>rsh(1)</code> utility on USG Unix). Note that +this is different from an <b><a href="#ironbox">iron +box</a></b> because it is overt and not aimed at enforcing +security so much as protecting others (and the luser) from the +consequences of the luser's boundless naivete (see <b><a href="#naive">naive</a></b>). Also `padded cell environment'.</p> + +<hr> +Node:<a name="pagein">page in</a>, Next:<a rel="next" href="#pageout">page out</a>, Previous:<a rel="previous" href="#paddedcell">padded cell</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>page in</b> v.</p> + +<p>[MIT] 1. To become aware of one's surroundings again after +having paged out (see <b><a href="#pageout">page out</a></b>). +Usually confined to the sarcastic comment: "Eric pages in, <b><a +href="#filmat11">film at 11</a></b>!" 2. Syn. `swap in'; +see <b><a href="#swap">swap</a></b>.</p> + +<hr> +Node:<a name="pageout">page out</a>, Next:<a rel="next" href="#paininthenet">pain in the net</a>, Previous:<a rel="previous" href="#pagein">page in</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>page out</b> vi.</p> + +<p>[MIT] 1. To become unaware of one's surroundings temporarily, +due to daydreaming or preoccupation. "Can you repeat that? I +paged out for a minute." See <b><a href="#pagein">page +in</a></b>. Compare <b><a href="#glitch">glitch</a></b>, <b><a +href="#thinko">thinko</a></b>. 2. Syn. `swap out'; see <b><a +href="#swap">swap</a></b>.</p> + +<hr> +Node:<a name="paininthenet">pain in the net</a>, Next:<a +rel="next" href="#Panglossparity">Pangloss parity</a>, +Previous:<a rel="previous" href="#pageout">page out</a>, Up:<a +rel="up" href="#chap16">= P =</a> <br> + + +<p><b>pain in the net</b> n.</p> + +<p>A <b><a href="#flamer">flamer</a></b>.</p> + +<hr> +Node:<a name="Panglossparity">Pangloss parity</a>, Next:<a +rel="next" href="#paper-net">paper-net</a>, Previous:<a rel="previous" href="#paininthenet">pain in the net</a>, +Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>Pangloss parity</b> n.</p> + +<p>[from Dr. Pangloss, the eternal optimist in Voltaire's +"Candide"] In corporate DP shops, a common condition of severe +but equally shared <b><a href="#lossage">lossage</a></b> +resulting from the theory that as long as everyone in the +organization has the exactly the <i>same</i> model of obsolete +computer, everything will be fine.</p> + +<hr> +Node:<a name="paper-net">paper-net</a>, Next:<a rel="next" href="#param">param</a>, Previous:<a rel="previous" href="#Panglossparity">Pangloss parity</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>paper-net</b> n.</p> + +<p>Hackish way of referring to the postal service, analogizing it +to a very slow, low-reliability network. Usenet <b><a href="#sigblock">sig block</a></b>s sometimes include a +"Paper-Net:" header just before the sender's postal address; +common variants of this are "Papernet" and "P-Net". Note that the +standard <b><a href="#netiquette">netiquette</a></b> guidelines +discourage this practice as a waste of bandwidth, since netters +are quite unlikely to casually use postal addresses. Compare +<b><a href="#voice-net">voice-net</a></b>, <b><a href="#snail-mail">snail-mail</a></b>, <b><a href="#P-mail">P-mail</a></b>.</p> + +<hr> +Node:<a name="param">param</a>, Next:<a rel="next" href="#PARC">PARC</a>, Previous:<a rel="previous" href="#paper-net">paper-net</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>param</b> /p*-ram'/ n.</p> + +<p>[common] Shorthand for `parameter'. See also <b><a href="#parm">parm</a></b>; compare <b><a href="#arg">arg</a></b>, +<b><a href="#var">var</a></b>.</p> + +<hr> +Node:<a name="PARC">PARC</a>, Next:<a rel="next" href="#parentmessage">parent message</a>, Previous:<a rel="previous" href="#param">param</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>PARC</b> n.</p> + +<p>See <b><a href="#XEROXPARC">XEROX PARC</a></b>.</p> + +<hr> +Node:<a name="parentmessage">parent message</a>, Next:<a rel="next" href="#parityerrors">parity errors</a>, Previous:<a +rel="previous" href="#PARC">PARC</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>parent message</b> n.</p> + +<p>What a <b><a href="#followup">followup</a></b> follows up.</p> + +<hr> +Node:<a name="parityerrors">parity errors</a>, Next:<a rel="next" href="#ParkinsonsLawofData">Parkinson's Law of +Data</a>, Previous:<a rel="previous" href="#parentmessage">parent message</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>parity errors</b> pl.n.</p> + +<p>Little lapses of attention or (in more severe cases) +consciousness, usually brought on by having spent all night and +most of the next day hacking. "I need to go home and crash; I'm +starting to get a lot of parity errors." Derives from a +relatively common but nearly always correctable transient error +in memory hardware. It predates RAM; in fact, this term is +reported to have already have been in use in its jargoin sense +back in the 1960s when magnetic cores ruled. Parity errors can +also afflict mass storage and serial communication lines; this is +more serious because not always correctable.</p> + +<hr> +Node:<a name="ParkinsonsLawofData">Parkinson's Law of +Data</a>, Next:<a rel="next" href="#parm">parm</a>, Previous:<a +rel="previous" href="#parityerrors">parity errors</a>, Up:<a +rel="up" href="#chap16">= P =</a> <br> + + +<p><b>Parkinson's Law of Data</b> prov.</p> + +<p>"Data expands to fill the space available for storage"; buying +more memory encourages the use of more memory-intensive +techniques. It has been observed since the mid-1980s that the +memory usage of evolving systems tends to double roughly once +every 18 months. Fortunately, memory density available for +constant dollars also tends to about double once every 18 months +(see <b><a href="#MooresLaw">Moore's Law</a></b>); +unfortunately, the laws of physics guarantee that the latter +cannot continue indefinitely.</p> + +<hr> +Node:<a name="parm">parm</a>, Next:<a rel="next" href="#parse">parse</a>, Previous:<a rel="previous" href="#ParkinsonsLawofData">Parkinson's Law of Data</a>, +Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>parm</b> /parm/ n.</p> + +<p>Further-compressed form of <b><a href="#param">param</a></b>. +This term is an IBMism, and written use is almost unknown outside +IBM shops; spoken /parm/ is more widely distributed, but the +synonym <b><a href="#arg">arg</a></b> is favored among hackers. +Compare <b><a href="#arg">arg</a></b>, <b><a href="#var">var</a></b>.</p> + +<hr> +Node:<a name="parse">parse</a>, Next:<a rel="next" href="#Pascal">Pascal</a>, Previous:<a rel="previous" href="#parm">parm</a>, Up:<a rel="up" href="#chap16">= P =</a> +<br> + + +<p><b>parse</b> [from linguistic terminology] vt.</p> + +<p>1. To determine the syntactic structure of a sentence or other +utterance (close to the standard English meaning). "That was the +one I saw you." "I can't parse that." 2. More generally, to +understand or comprehend. "It's very simple; you just kretch the +glims and then aos the zotz." "I can't parse that." 3. Of fish, +to have to remove the bones yourself. "I object to parsing fish", +means "I don't want to get a whole fish, but a sliced one is +okay". A `parsed fish' has been deboned. There is some +controversy over whether `unparsed' should mean `bony', or also +mean `deboned'.</p> + +<hr> +Node:<a name="Pascal">Pascal</a>, Next:<a rel="next" href="#pastie">pastie</a>, Previous:<a rel="previous" href="#parse">parse</a>, Up:<a rel="up" href="#chap16">= P +=</a> <br> + + +<p><b>Pascal</b> n.</p> + +<p>An Algol-descended language designed by Niklaus Wirth on the +CDC 6600 around 1967-68 as an instructional tool for elementary +programming. This language, designed primarily to keep students +from shooting themselves in the foot and thus extremely +restrictive from a general-purpose-programming point of view, was +later promoted as a general-purpose tool and, in fact, became the +ancestor of a large family of languages including Modula-2 and +<b><a href="#Ada">Ada</a></b> (see also <b><a href="#bondage-and-disciplinelanguage">bondage-and-discipline +language</a></b>). The hackish point of view on Pascal was +probably best summed up by a devastating (and, in its deadpan +way, screamingly funny) 1981 paper by Brian Kernighan (of <b><a +href="#KandR">K&R</a></b> fame) entitled "Why Pascal is Not +My Favorite Programming Language", which was turned down by the +technical journals but circulated widely via photocopies. It was +eventually published in "Comparing and Assessing Programming +Languages", edited by Alan Feuer and Narain Gehani +(Prentice-Hall, 1984). Part of his discussion is worth repeating +here, because its criticisms are still apposite to Pascal itself +after ten years of improvement and could also stand as an +indictment of many other bondage-and-discipline languages. At the +end of a summary of the case against Pascal, Kernighan wrote:</p> + +<blockquote>9. There is no escape + +<p>This last point is perhaps the most important. The language is +inadequate but circumscribed, because there is no way to escape +its limitations. There are no casts to disable the type-checking +when necessary. There is no way to replace the defective run-time +environment with a sensible one, unless one controls the compiler +that defines the "standard procedures". The language is +closed.</p> + +<p>People who use Pascal for serious programming fall into a +fatal trap. Because the language is impotent, it must be +extended. But each group extends Pascal in its own direction, to +make it look like whatever language they really want. Extensions +for separate compilation, FORTRAN-like COMMON, string data types, +internal static variables, initialization, octal numbers, bit +operators, etc., all add to the utility of the language for one +group but destroy its portability to others.</p> + +<p>I feel that it is a mistake to use Pascal for anything much +beyond its original target. In its pure form, Pascal is a toy +language, suitable for teaching but not for real programming.</p> +</blockquote> + +<p>Pascal has since been almost entirely displaced (by <b><a +href="#C">C</a></b>) from the niches it had acquired in serious +applications and systems programming, but retains some popularity +as a hobbyist language in the MS-DOS and Macintosh worlds.</p> + +<hr> +Node:<a name="pastie">pastie</a>, Next:<a rel="next" href="#patch">patch</a>, Previous:<a rel="previous" href="#Pascal">Pascal</a>, Up:<a rel="up" href="#chap16">= P +=</a> <br> + + +<p><b>pastie</b> /pay'stee/ n.</p> + +<p>An adhesive-backed label designed to be attached to a key on a +keyboard to indicate some non-standard character which can be +accessed through that key. Pasties are likely to be used in APL +environments, where almost every key is associated with a special +character. A pastie on the R key, for example, might remind the +user that it is used to generate the rho character. The term +properly refers to nipple-concealing devices formerly worn by +strippers in concession to indecent-exposure laws; compare <b><a +href="#titsonakeyboard">tits on a keyboard</a></b>.</p> + +<hr> +Node:<a name="patch">patch</a>, Next:<a rel="next" href="#patchpumpkin">patch pumpkin</a>, Previous:<a rel="previous" +href="#pastie">pastie</a>, Up:<a rel="up" href="#chap16">= +P =</a> <br> + + +<p><b>patch</b></p> + +<p>1. n. A temporary addition to a piece of code, usually as a +<b><a href="#quick-and-dirty">quick-and-dirty</a></b> remedy to +an existing bug or misfeature. A patch may or may not work, and +may or may not eventually be incorporated permanently into the +program. Distinguished from a <b><a href="#diff">diff</a></b> or +<b><a href="#mod">mod</a></b> by the fact that a patch is +generated by more primitive means than the rest of the program; +the classical examples are instructions modified by using the +front panel switches, and changes made directly to the binary +executable of a program originally written in an <b><a href="#HLL">HLL</a></b>. Compare <b><a href="#onelinefix">one-line +fix</a></b>. 2. vt. To insert a patch into a piece of code. 3. +[in the Unix world] n. A <b><a href="#diff">diff</a></b> (sense +2). 4. A set of modifications to binaries to be applied by a +patching program. IBM operating systems often receive updates to +the operating system in the form of absolute hexadecimal patches. +If you have modified your OS, you have to disassemble these back +to the source. The patches might later be corrected by other +patches on top of them (patches were said to "grow scar tissue"). +The result was often a convoluted <b><a href="#patchspace">patch space</a></b> and headaches galore. 5. +[Unix] the <code>patch(1)</code> program, written by Larry Wall, +which automatically applies a patch (sense 3) to a set of source +code.</p> + +<p>There is a classic story of a <b><a href="#tigerteam">tiger +team</a></b> penetrating a secure military computer that +illustrates the danger inherent in binary patches (or, indeed, +any patches that you can't -- or don't -- inspect and examine +before installing). They couldn't find any <b><a href="#trapDoor">trap door</a></b>s or any way to penetrate +security of IBM's OS, so they made a site visit to an IBM office +(remember, these were official military types who were +purportedly on official business), swiped some IBM stationery, +and created a fake patch. The patch was actually the trapdoor +they needed. The patch was distributed at about the right time +for an IBM patch, had official stationery and all accompanying +documentation, and was dutifully installed. The installation +manager very shortly thereafter learned something about proper +procedures.</p> + +<hr> +Node:<a name="patchpumpkin">patch pumpkin</a>, Next:<a rel="next" href="#patchspace">patch space</a>, Previous:<a rel="previous" href="#patch">patch</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>patch pumpkin</b> n.</p> + +<p>[Perl hackers] A notional token passed around among the +members of a project. Possession of the patch pumpkin means one +has the exclusive authority to make changes on the project's +master source tree. The implicit assumption is that `pumpkin +holder' status is temporary and rotates periodically among senior +project members.</p> + +<p>This term comes from the Perl development community, but has +been sighted elsewhere. It derives from a stuffed-toy pumpkin +that was passed around at a development shop years ago as the +access control for a shared backup-tape drive.</p> + +<hr> +Node:<a name="patchspace">patch space</a>, Next:<a rel="next" +href="#path">path</a>, Previous:<a rel="previous" href="#patchpumpkin">patch pumpkin</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>patch space</b> n.</p> + +<p>An unused block of bits left in a binary so that it can later +be modified by insertion of machine-language instructions there +(typically, the patch space is modified to contain new code, and +the superseded code is patched to contain a jump or call to the +patch space). The near-universal use of compilers and +interpreters has made this term rare; it is now primarily +historical outside IBM shops. See <b><a href="#patch">patch</a></b> (sense 4), <b><a href="#zap">zap</a></b> +(sense 4), <b><a href="#hook">hook</a></b>.</p> + +<hr> +Node:<a name="path">path</a>, Next:<a rel="next" href="#pathological">pathological</a>, Previous:<a rel="previous" +href="#patchspace">patch space</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>path</b> n.</p> + +<p>1. A <b><a href="#bangpath">bang path</a></b> or explicitly +routed <b><a href="#Internetaddress">Internet address</a></b>; +a node-by-node specification of a link between two machines. +Though these are now obsolete as a form of addressing, they still +show up in diagnostics and trace headers ocvcasionally (e.g. in +NNTP headers). 2. [Unix] A filename, fully specified relative to +the root directory (as opposed to relative to the current +directory; the latter is sometimes called a `relative path'). +This is also called a `pathname'. 3. [Unix and MS-DOS] The +`search path', an environment variable specifying the directories +in which the <b><a href="#shell">shell</a></b> (COMMAND.COM, +under MS-DOS) should look for commands. Other, similar constructs +abound under Unix (for example, the C preprocessor has a `search +path' it uses in looking for <code>#include</code> files).</p> + +<hr> +Node:<a name="pathological">pathological</a>, Next:<a rel="next" +href="#payware">payware</a>, Previous:<a rel="previous" href="#path">path</a>, Up:<a rel="up" href="#chap16">= P =</a> +<br> + + +<p><b>pathological</b> adj.</p> + +<p>1. [scientific computation] Used of a data set that is grossly +atypical of normal expected input, esp. one that exposes a +weakness or bug in whatever algorithm one is using. An algorithm +that can be broken by pathological inputs may still be useful if +such inputs are very unlikely to occur in practice. 2. When used +of test input, implies that it was purposefully engineered as a +worst case. The implication in both senses is that the data is +spectacularly ill-conditioned or that someone had to explicitly +set out to break the algorithm in order to come up with such a +crazy example. 3. Also said of an unlikely collection of +circumstances. "If the network is down and comes up halfway +through the execution of that command by root, the system may +just crash." "Yes, but that's a pathological case." Often used to +dismiss the case from discussion, with the implication that the +consequences are acceptable, since they will happen so +infrequently (if at all) that it doesn't seem worth going to the +extra trouble to handle that case (see sense 1).</p> + +<hr> +Node:<a name="payware">payware</a>, Next:<a rel="next" href="#PBD">PBD</a>, Previous:<a rel="previous" href="#pathological">pathological</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>payware</b> /pay'weir/ n.</p> + +<p>Commercial software. Oppose <b><a href="#shareware">shareware</a></b> or <b><a href="#freeware">freeware</a></b>.</p> + +<hr> +Node:<a name="PBD">PBD</a>, Next:<a rel="next" href="#PC-ism">PC-ism</a>, Previous:<a rel="previous" href="#payware">payware</a>, Up:<a rel="up" href="#chap16">= P +=</a> <br> + + +<p><b>PBD</b> /P-B-D/ n.</p> + +<p>[abbrev. of `Programmer Brain Damage'] Applied to bug reports +revealing places where the program was obviously broken by an +incompetent or short-sighted programmer. Compare <b><a href="#UBD">UBD</a></b>; see also <b><a href="#brain-damaged">brain-damaged</a></b>.</p> + +<hr> +Node:<a name="PC-ism">PC-ism</a>, Next:<a rel="next" href="#PD">PD</a>, Previous:<a rel="previous" href="#PBD">PBD</a>, +Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>PC-ism</b> /P-C-izm/ n.</p> + +<p>A piece of code or coding technique that takes advantage of +the unprotected single-tasking environment in IBM PCs and the +like running DOS, e.g., by busy-waiting on a hardware register, +direct diddling of screen memory, or using hard timing loops. +Compare <b><a href="#ill-behaved">ill-behaved</a></b>, <b><a +href="#vaxism">vaxism</a></b>, <b><a href="#unixism">unixism</a></b>. Also, `PC-ware' n., a program full of +PC-isms on a machine with a more capable operating system. +Pejorative.</p> + +<hr> +Node:<a name="PD">PD</a>, Next:<a rel="next" href="#PDL">PDL</a>, +Previous:<a rel="previous" href="#PC-ism">PC-ism</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>PD</b> /P-D/ adj.</p> + +<p>[common] Abbreviation for `public domain', applied to software +distributed over <b><a href="#Usenet">Usenet</a></b> and from +Internet archive sites. Much of this software is not in fact +public domain in the legal sense but travels under various +copyrights granting reproduction and use rights to anyone who can +<b><a href="#snarf">snarf</a></b> a copy. See <b><a href="#copyleft">copyleft</a></b>.</p> + +<hr> +Node:<a name="PDL">PDL</a>, Next:<a rel="next" href="#PDP-10">PDP-10</a>, Previous:<a rel="previous" href="#PD">PD</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>PDL</b> /P-D-L/, /pid'l/, /p*d'l/ or /puhd'l/</p> + +<p>1. n. `Program Design Language'. Any of a large class of +formal and profoundly useless pseudo-languages in which <b><a +href="#management">management</a></b> forces one to design +programs. Too often, management expects PDL descriptions to be +maintained in parallel with the code, imposing massive overhead +to little or no benefit. See also <b><a href="#flowchart">flowchart</a></b>. 2. v. To design using a program +design language. "I've been pdling so long my eyes won't focus +beyond 2 feet." 3. n. `Page Description Language'. Refers to any +language which is used to control a graphics device, usually a +laserprinter. The most common example is, of course, Adobe's +<b><a href="#PostScript">PostScript</a></b> language, but there +are many others, such as Xerox InterPress, etc. 4. In ITS days, +the preferred MITism for <b><a href="#stack">stack</a></b>. See +<b><a href="#overflowpdl">overflow pdl</a></b>. 5. Dave +Lebling, one of the co-authors of <b><a href="#Zork">Zork</a></b>; (his <b><a href="#networkaddress">network address</a></b> on the ITS machines +was at one time pdl@dms).</p> + +<hr> +Node:<a name="PDP-10">PDP-10</a>, Next:<a rel="next" href="#PDP-20">PDP-20</a>, Previous:<a rel="previous" href="#PDL">PDL</a>, Up:<a rel="up" href="#chap16">= P =</a> +<br> + + +<p><b>PDP-10</b> n.</p> + +<p>[Programmed Data Processor model 10] The machine that made +timesharing real. It looms large in hacker folklore because of +its adoption in the mid-1970s by many university computing +facilities and research labs, including the MIT AI Lab, Stanford, +and CMU. Some aspects of the instruction set (most notably the +bit-field instructions) are still considered unsurpassed. The 10 +was eventually eclipsed by the VAX machines (descendants of the +PDP-11) when <b><a href="#DEC">DEC</a></b> recognized that the 10 +and VAX product lines were competing with each other and decided +to concentrate its software development effort on the more +profitable VAX. The machine was finally dropped from DEC's line +in 1983, following the failure of the Jupiter Project at DEC to +build a viable new model. (Some attempts by other companies to +market clones came to nothing; see <b><a href="#Foonly">Foonly</a></b> and <b><a href="#Mars">Mars</a></b>.) +This event spelled the doom of <b><a href="#ITS">ITS</a></b> and +the technical cultures that had spawned the original Jargon File, +but by mid-1991 it had become something of a badge of honorable +old-timerhood among hackers to have cut one's teeth on a PDP-10. +See <b><a href="#TOPS-10">TOPS-10</a></b>, <b><a href="#ITS">ITS</a></b>, <b><a href="#BLT">BLT</a></b>, <b><a href="#DDT">DDT</a></b>, <b><a href="#DPB">DPB</a></b>, <b><a href="#EXCH">EXCH</a></b>, <b><a href="#HAKMEM">HAKMEM</a></b>, <b><a +href="#LDB">LDB</a></b>, <b><a href="#pop">pop</a></b>, <b><a +href="#push">push</a></b>. See also http://www.inwap.com/pdp10/.</p> + +<hr> +Node:<a name="PDP-20">PDP-20</a>, Next:<a rel="next" href="#PEBKAC">PEBKAC</a>, Previous:<a rel="previous" href="#PDP-10">PDP-10</a>, Up:<a rel="up" href="#chap16">= P +=</a> <br> + + +<p><b>PDP-20</b> n.</p> + +<p>The most famous computer that never was. <b><a href="#PDP-10">PDP-10</a></b> computers running the <b><a href="#TOPS-10">TOPS-10</a></b> operating system were labeled +`DECsystem-10' as a way of differentiating them from the PDP-11. +Later on, those systems running <b><a href="#TOPS-20">TOPS-20</a></b> were labeled `DECSYSTEM-20' (the block +capitals being the result of a lawsuit brought against DEC by +Singer, which once made a computer called `system-10'), but +contrary to popular lore there was never a `PDP-20'; the only +difference between a 10 and a 20 was the operating system and the +color of the paint. Most (but not all) machines sold to run +TOPS-10 were painted `Basil Blue', whereas most TOPS-20 machines +were painted `Chinese Red' (often mistakenly called orange).</p> + +<hr> +Node:<a name="PEBKAC">PEBKAC</a>, Next:<a rel="next" href="#peek">peek</a>, Previous:<a rel="previous" href="#PDP-20">PDP-20</a>, Up:<a rel="up" href="#chap16">= P +=</a> <br> + + +<p><b>PEBKAC</b> /peb'kak/</p> + +<p>[Abbrev., "Problem Exists Between Keyboard And Chair"] Used by +support people, particularly at call centers and help desks. Not +used with the public. Denotes pilot error as the cause of the +crash, especially stupid errors that even a <b><a href="#luser">luser</a></b> could figure out. Very derogatory. Usage: +"Did you ever figure out why that guy couldn't print?" "Yeah, he +kept cancelling the operation before it could finish. +PEBKAC."</p> + +<hr> +Node:<a name="peek">peek</a>, Next:<a rel="next" href="#pencilandpaper">pencil and paper</a>, Previous:<a rel="previous" href="#PEBKAC">PEBKAC</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>peek</b> n.,vt.</p> + +<p>(and <b><a href="#poke">poke</a></b>) The commands in most +microcomputer BASICs for directly accessing memory contents at an +absolute address; often extended to mean the corresponding +constructs in any <b><a href="#HLL">HLL</a></b> (peek reads +memory, poke modifies it). Much hacking on small, non-MMU micros +used to consist of `peek'ing around memory, more or less at +random, to find the location where the system keeps interesting +stuff. Long (and variably accurate) lists of such addresses for +various computers circulated (see <b><a href="#interruptlist">interrupt list</a></b>). The results of +`poke's at these addresses may be highly useful, mildly amusing, +useless but neat, or (most likely) total <b><a href="#lossage">lossage</a></b> (see <b><a href="#killerpoke">killer poke</a></b>).</p> + +<p>Since a <b><a href="#realoperatingsystem">real operating +system</a></b> provides useful, higher-level services for the +tasks commonly performed with peeks and pokes on micros, and real +languages tend not to encourage low-level memory groveling, a +question like "How do I do a peek in C?" is diagnostic of the +<b><a href="#newbie">newbie</a></b>. (Of course, OS kernels often +have to do exactly this; a real kernel hacker would +unhesitatingly, if unportably, assign an absolute address to a +pointer variable and indirect through it.)</p> + +<hr> +Node:<a name="pencilandpaper">pencil and paper</a>, Next:<a +rel="next" href="#PentagramPro">Pentagram Pro</a>, Previous:<a +rel="previous" href="#peek">peek</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>pencil and paper</b> n.</p> + +<p>An archaic information storage and transmission device that +works by depositing smears of graphite on bleached wood pulp. +More recent developments in paper-based technology include +improved `write-once' update devices which use tiny rolling heads +similar to mouse balls to deposit colored pigment. All these +devices require an operator skilled at so-called `handwriting' +technique. These technologies are ubiquitous outside hackerdom, +but nearly forgotten inside it. Most hackers had terrible +handwriting to begin with, and years of keyboarding tend to have +encouraged it to degrade further. Perhaps for this reason, +hackers deprecate pencil-and-paper technology and often resist +using it in any but the most trivial contexts.</p> + +<hr> +Node:<a name="PentagramPro">Pentagram Pro</a>, Next:<a rel="next" href="#Pentium">Pentium</a>, Previous:<a rel="previous" +href="#pencilandpaper">pencil and paper</a>, Up:<a rel="up" +href="#chap16">= P =</a> <br> + + +<p><b>Pentagram Pro</b> n.</p> + +<p>A humorous corruption of "Pentium Pro", with a Satanic +reference, implying that the chip is inherently <b><a href="#evil">evil</a></b>. Often used with "666 MHz"; there is a +T-shirt. See <b><a href="#Pentium">Pentium</a></b></p> + +<hr> +Node:<a name="Pentium">Pentium</a>, Next:<a rel="next" href="#peon">peon</a>, Previous:<a rel="previous" href="#PentagramPro">Pentagram Pro</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>Pentium</b> n.</p> + +<p>The name given to Intel's P5 chip, the successor to the 80486. +The name was chosen because of difficulties Intel had in +trademarking a number. It suggests the number five (implying 586) +while (according to Intel) conveying a meaning of strength "like +titanium". Among hackers, the plural is frequently `pentia'. See +also <b><a href="#PentagramPro">Pentagram Pro</a></b>.</p> + +<p>Intel did not stick to this convention when naming its P6 +processor the Pentium Pro; many believe this is due to +difficulties in selling a chip with "sex" in its name. Successor +chips have been called `Pentium II' and `Pentium III'.</p> + +<hr> +Node:<a name="peon">peon</a>, Next:<a rel="next" href="#percent-S">percent-S</a>, Previous:<a rel="previous" href="#Pentium">Pentium</a>, Up:<a rel="up" href="#chap16">= P +=</a> <br> + + +<p><b>peon</b> n.</p> + +<p>A person with no special (<b><a href="#root">root</a></b> or +<b><a href="#wheel">wheel</a></b>) privileges on a computer +system. "I can't create an account on <i>foovax</i> for you; +I'm only a peon there."</p> + +<hr> +Node:<a name="percent-S">percent-S</a>, Next:<a rel="next" href="#perf">perf</a>, Previous:<a rel="previous" href="#peon">peon</a>, Up:<a rel="up" href="#chap16">= P =</a> +<br> + + +<p><b>percent-S</b> /per-sent' es'/ n.</p> + +<p>[From the code in C's <code>printf(3)</code> library function +used to insert an arbitrary string argument] An unspecified +person or object. "I was just talking to some percent-s in +administration." Compare <b><a href="#random">random</a></b>.</p> + +<hr> +Node:<a name="perf">perf</a>, Next:<a rel="next" href="#perfectprogrammersyndrome">perfect programmer +syndrome</a>, Previous:<a rel="previous" href="#percent-S">percent-S</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>perf</b> /perf/ n.</p> + +<p>Syn. <b><a href="#chad">chad</a></b> (sense 1). The term +`perfory' /per'f*-ree/ is also heard. The term <b><a href="#perf">perf</a></b> may also refer to the perforations +themselves, rather than the chad they produce when torn +(philatelists use it this way).</p> + +<hr> +Node:<a name="perfectprogrammersyndrome">perfect programmer +syndrome</a>, Next:<a rel="next" href="#Perl">Perl</a>, +Previous:<a rel="previous" href="#perf">perf</a>, Up:<a rel="up" +href="#chap16">= P =</a> <br> + + +<p><b>perfect programmer syndrome</b> n.</p> + +<p>Arrogance; the egotistical conviction that one is above normal +human error. Most frequently found among programmers of some +native ability but relatively little experience (especially new +graduates; their perceptions may be distorted by a history of +excellent performance at solving <b><a href="#toyproblem">toy +problem</a></b>s). "Of course my program is correct, there is no +need to test it." "Yes, I can see there may be a problem here, +but <i>I'll</i> never type <code>rm -r /</code> while in <b><a +href="#rootmode">root mode</a></b>."</p> + +<hr> +Node:<a name="Perl">Perl</a>, Next:<a rel="next" href="#personofnoaccount">person of no account</a>, +Previous:<a rel="previous" href="#perfectprogrammersyndrome">perfect programmer +syndrome</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>Perl</b> /perl/ n.</p> + +<p> +[Practical Extraction and Report Language, a.k.a. Pathologically Eclectic +Rubbish Lister] An interpreted language developed by Larry Wall (author of +<code>patch(1)</code> and <code>rn(1)</code>) and distributed over Usenet. +Superficially resembles <b><a href="#awk">awk</a></b>, but is much hairier, +including many facilities reminiscent of <code>sed(1)</code> and shells and a +comprehensive Unix system-call interface. Unix sysadmins, who are almost always +incorrigible hackers, generally consider it one of the <b><a +href="#languagesofchoice">languages of choice</a></b>, and it is by far +the most widely used tool for making `live' web pages via CGI. Perl has been +described, in a parody of a famous remark about <code>lex(1)</code>, as the +"Swiss-Army chainsaw" of Unix programming. Though Perl is very useful, it would +be a stretch to describe it as pretty or <b><a href="#elegant">elegant</a></b>; +people who like clean, spare design generally prefer <b><a +href="#Python">Python</a></b>. See also <b><a href="#CamelBook">Camel +Book</a></b>, <b><a href="#TMTOWTDI">TMTOWTDI</a></b>. +</p> + +<hr> +Node:<a name="personofnoaccount">person of no +account</a>, Next:<a rel="next" href="#pessimal">pessimal</a>, +Previous:<a rel="previous" href="#Perl">Perl</a>, Up:<a rel="up" +href="#chap16">= P =</a> <br> + + +<p><b>person of no account</b> n.</p> + +<p>[University of California at Santa Cruz] Used when referring +to a person with no <b><a href="#networkaddress">network +address</a></b>, frequently to forestall confusion. Most often as +part of an introduction: "This is Bill, a person of no account, +but he used to be bill@random.com". Compare <b><a href="#returnfromthedead">return from the dead</a></b>.</p> + +<hr> +Node:<a name="pessimal">pessimal</a>, Next:<a rel="next" href="#pessimizingcompiler">pessimizing compiler</a>, Previous:<a +rel="previous" href="#personofnoaccount">person of no +account</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>pessimal</b> /pes'im-l/ adj.</p> + +<p>[Latin-based antonym for `optimal'] Maximally bad. "This is a +pessimal situation." Also `pessimize' vt. To make as bad as +possible. These words are the obvious Latin-based antonyms for +`optimal' and `optimize', but for some reason they do not appear +in most English dictionaries, although `pessimize' is listed in +the OED.</p> + +<hr> +Node:<a name="pessimizingcompiler">pessimizing compiler</a>, +Next:<a rel="next" href="#peta-">peta-</a>, Previous:<a rel="previous" href="#pessimal">pessimal</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>pessimizing compiler</b> /pes'*-mi:z`ing k*m-pi:l'r/ n.</p> + +<p>A compiler that produces object [antonym of techspeak +`optimizing compiler'] code that is worse than the +straightforward or obvious hand translation. The implication is +that the compiler is actually trying to optimize the program, but +through excessive cleverness is doing the opposite. A few +pessimizing compilers have been written on purpose, however, as +pranks or burlesques.</p> + +<hr> +Node:<a name="peta-">peta-</a>, Next:<a rel="next" href="#PETSCII">PETSCII</a>, Previous:<a rel="previous" href="#pessimizingcompiler">pessimizing compiler</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>peta-</b> /pe't*/ pref</p> + +<p>[SI] See <b><a href="#quantifiers">quantifiers</a></b>.</p> + +<hr> +Node:<a name="PETSCII">PETSCII</a>, Next:<a rel="next" href="#PFY">PFY</a>, Previous:<a rel="previous" href="#peta-">peta-</a>, Up:<a rel="up" href="#chap16">= P +=</a> <br> + + +<p><b>PETSCII</b> /pet'skee/ n. obs.</p> + +<p>[abbreviation of PET ASCII] The variation (many would say +perversion) of the <b><a href="#ASCII">ASCII</a></b> character +set used by the Commodore Business Machines PET series of +personal computers and the later Commodore C64, C16, C128, and +VIC20 machines. The PETSCII set used left-arrow and up-arrow (as +in old-style ASCII) instead of underscore and caret, placed the +unshifted alphabet at positions 65-90, put the shifted alphabet +at positions 193-218, and added graphics characters.</p> + +<hr> +Node:<a name="PFY">PFY</a>, Next:<a rel="next" href="#phage">phage</a>, Previous:<a rel="previous" href="#PETSCII">PETSCII</a>, Up:<a rel="up" href="#chap16">= P +=</a> <br> + + +<p><b>PFY</b> n.</p> + +<p>[Usenet; common] Abbreviation for `Pimply-Faced Youth'. A +<b><a href="#BOFH">BOFH</a></b> in training, esp. one apprenticed +to an elder BOFH aged in evil.</p> + +<hr> +Node:<a name="phage">phage</a>, Next:<a rel="next" href="#phase">phase</a>, Previous:<a rel="previous" href="#PFY">PFY</a>, Up:<a rel="up" href="#chap16">= P =</a> +<br> + + +<p><b>phage</b> n.</p> + +<p>A program that modifies other programs or databases in +unauthorized ways; esp. one that propagates a <b><a href="#virus">virus</a></b> or <b><a href="#Trojanhorse">Trojan +horse</a></b>. See also <b><a href="#worm">worm</a></b>, <b><a +href="#mockingbird">mockingbird</a></b>. The analogy, of course, +is with phage viruses in biology.</p> + +<hr> +Node:<a name="phase">phase</a>, Next:<a rel="next" href="#phaseofthemoon">phase of the moon</a>, Previous:<a +rel="previous" href="#phage">phage</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>phase</b></p> + +<p>1. n. The offset of one's waking-sleeping schedule with +respect to the standard 24-hour cycle; a useful concept among +people who often work at night and/or according to no fixed +schedule. It is not uncommon to change one's phase by as much as +6 hours per day on a regular basis. "What's your phase?" "I've +been getting in about 8 <small>P.M.</small> lately, but I'm going +to <b><a href="#wrapAround">wrap around</a></b> to the day +schedule by Friday." A person who is roughly 12 hours out of +phase is sometimes said to be in `night mode'. (The term `day +mode' is also (but less frequently) used, meaning you're working +9 to 5 (or, more likely, 10 to 6).) The act of altering one's +cycle is called `changing phase'; `phase shifting' has also been +recently reported from Caltech. 2. `change phase the hard way': +To stay awake for a very long time in order to get into a +different phase. 3. `change phase the easy way': To stay asleep, +etc. However, some claim that either staying awake longer or +sleeping longer is easy, and that it is <i>shortening</i> your +day or night that is really hard (see <b><a href="#wrapAround">wrap around</a></b>). The `jet lag' that +afflicts travelers who cross many time-zone boundaries may be +attributed to two distinct causes: the strain of travel per se, +and the strain of changing phase. Hackers who suddenly find that +they must change phase drastically in a short period of time, +particularly the hard way, experience something very like jet lag +without traveling.</p> + +<hr> +Node:<a name="phaseofthemoon">phase of the moon</a>, +Next:<a rel="next" href="#phase-wrapping">phase-wrapping</a>, +Previous:<a rel="previous" href="#phase">phase</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>phase of the moon</b> n.</p> + +<p>Used humorously as a random parameter on which something is +said to depend. Sometimes implies unreliability of whatever is +dependent, or that reliability seems to be dependent on +conditions nobody has been able to determine. "This feature +depends on having the channel open in mumble mode, having the foo +switch set, and on the phase of the moon." See also <b><a href="#heisenbug">heisenbug</a></b>.</p> + +<p>True story: Once upon a time there was a program bug that +really did depend on the phase of the moon. There was a little +subroutine that had traditionally been used in various programs +at MIT to calculate an approximation to the moon's true phase. +GLS incorporated this routine into a LISP program that, when it +wrote out a file, would print a timestamp line almost 80 +characters long. Very occasionally the first line of the message +would be too long and would overflow onto the next line, and when +the file was later read back in the program would <b><a href="#barf">barf</a></b>. The length of the first line depended on +both the precise date and time and the length of the phase +specification when the timestamp was printed, and so the bug +literally depended on the phase of the moon!</p> + +<p>The first paper edition of the Jargon File (Steele-1983) +included an example of one of the timestamp lines that exhibited +this bug, but the typesetter `corrected' it. This has since been +described as the phase-of-the-moon-bug bug.</p> + +<p>However, beware of assumptions. A few years ago, engineers of +CERN (European Center for Nuclear Research) were baffled by some +errors in experiments conducted with the LEP particle +accelerator. As the formidable amount of data generated by such +devices is heavily processed by computers before being seen by +humans, many people suggested the software was somehow sensitive +to the phase of the moon. A few desperate engineers discovered +the truth; the error turned out to be the result of a tiny change +in the geometry of the 27km circumference ring, physically caused +by the deformation of the Earth by the passage of the Moon! This +story has entered physics folklore as a Newtonian vengeance on +particle physics and as an example of the relevance of the +simplest and oldest physical laws to the most modern science.</p> + +<hr> +Node:<a name="phase-wrapping">phase-wrapping</a>, Next:<a rel="next" href="#PHB">PHB</a>, Previous:<a rel="previous" href="#phaseofthemoon">phase of the moon</a>, Up:<a rel="up" +href="#chap16">= P =</a> <br> + + +<p><b>phase-wrapping</b> n.</p> + +<p>[MIT] Syn. <b><a href="#wrapAround">wrap around</a></b>, +sense 2.</p> + +<hr> +Node:<a name="PHB">PHB</a>, Next:<a rel="next" href="#phreaker">phreaker</a>, Previous:<a rel="previous" href="#phase-wrapping">phase-wrapping</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>PHB</b> /P-H-B/</p> + +<p>[Usenet; common; rarely spoken] Abbreviation, "Pointy-Haired +Boss". From the <b><a href="#Dilbert">Dilbert</a></b> character, +the archetypal halfwitted middle-<b><a href="#management">management</a></b> type. See also <b><a href="#pointy-haired">pointy-haired</a></b>.</p> + +<hr> +Node:<a name="phreaker">phreaker</a>, Next:<a rel="next" href="#phreaking">phreaking</a>, Previous:<a rel="previous" href="#PHB">PHB</a>, Up:<a rel="up" href="#chap16">= P =</a> +<br> + + +<p><b>phreaker</b> /freek'r/ n.</p> + +<p>One who engages in <b><a href="#phreaking">phreaking</a></b>. +See also <b><a href="#bluebox">blue box</a></b>.</p> + +<hr> +Node:<a name="phreaking">phreaking</a>, Next:<a rel="next" href="#pico-">pico-</a>, Previous:<a rel="previous" href="#phreaker">phreaker</a>, Up:<a rel="up" href="#chap16">= +P =</a> <br> + + +<p><b>phreaking</b> /freek'ing/ n.</p> + +<p>[from `phone phreak'] 1. The art and science of <b><a href="#cracking">cracking</a></b> the phone network (so as, for +example, to make free long-distance calls). 2. By extension, +security-cracking in any other context (especially, but not +exclusively, on communications networks) (see <b><a href="#cracking">cracking</a></b>).</p> + +<p>At one time phreaking was a semi-respectable activity among +hackers; there was a gentleman's agreement that phreaking as an +intellectual game and a form of exploration was OK, but serious +theft of services was taboo. There was significant crossover +between the hacker community and the hard-core phone phreaks who +ran semi-underground networks of their own through such media as +the legendary "TAP Newsletter". This ethos began to break down in +the mid-1980s as wider dissemination of the techniques put them +in the hands of less responsible phreaks. Around the same time, +changes in the phone network made old-style technical ingenuity +less effective as a way of hacking it, so phreaking came to +depend more on overtly criminal acts such as stealing phone-card +numbers. The crimes and punishments of gangs like the `414 group' +turned that game very ugly. A few old-time hackers still phreak +casually just to keep their hand in, but most these days have +hardly even heard of `blue boxes' or any of the other +paraphernalia of the great phreaks of yore.</p> + +<hr> +Node:<a name="pico-">pico-</a>, Next:<a rel="next" href="#pig-tail">pig-tail</a>, Previous:<a rel="previous" href="#phreaking">phreaking</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>pico-</b> pref.</p> + +<p>[SI: a quantifier meaning * 10^-12] Smaller than <b><a href="#nano-">nano-</a></b>; used in the same rather loose connotative +way as <b><a href="#nano-">nano-</a></b> and <b>micro-</b>. This +usage is not yet common in the way <b><a href="#nano-">nano-</a></b> and <b><a href="#micro-">micro-</a></b> +are, but should be instantly recognizable to any hacker. See also +<b><a href="#quantifiers">quantifiers</a></b>, <b><a href="#micro-">micro-</a></b>.</p> + +<hr> +Node:<a name="pig-tail">pig-tail</a>, Next:<a rel="next" href="#piloterror">pilot error</a>, Previous:<a rel="previous" +href="#pico-">pico-</a>, Up:<a rel="up" href="#chap16">= P +=</a> <br> + + +<p><b>pig-tail</b></p> + +<p>[radio hams] A short piece of cable with two connectors on +each end for converting between one connector type and another. +Common pig-tails are 9-to-25-pin serial-port converters and +cables to connect PCMCIA network cards to an RJ-45 network +cable.</p> + +<hr> +Node:<a name="piloterror">pilot error</a>, Next:<a rel="next" +href="#ping">ping</a>, Previous:<a rel="previous" href="#pig-tail">pig-tail</a>, Up:<a rel="up" href="#chap16">= +P =</a> <br> + + +<p><b>pilot error</b> n.</p> + +<p>[Sun: from aviation] A user's misconfiguration or misuse of a +piece of software, producing apparently buglike results (compare +<b><a href="#UBD">UBD</a></b>). "Joe Luser reported a bug in +sendmail that causes it to generate bogus headers." "That's not a +bug, that's pilot error. His <code>sendmail.cf</code> is +hosed."</p> + +<hr> +Node:<a name="ping">ping</a>, Next:<a rel="next" href="#PingODeath">Ping O' Death</a>, Previous:<a rel="previous" href="#piloterror">pilot error</a>, Up:<a rel="up" +href="#chap16">= P =</a> <br> + + +<p><b>ping</b></p> + +<p>[from the submariners' term for a sonar pulse] 1. n. Slang +term for a small network message (ICMP ECHO) sent by a computer +to check for the presence and alertness of another. The Unix +command <code>ping(8)</code> can be used to do this manually +(note that <code>ping(8)</code>'s author denies the widespread +folk etymology that the name was ever intended as acronym for +`Packet INternet Groper'). Occasionally used as a phone greeting. +See <b><a href="#ACK">ACK</a></b>, also <b><a href="#ENQ">ENQ</a></b>. 2. vt. To verify the presence of. 3. vt. To +get the attention of. 4. vt. To send a message to all members of +a <b><a href="#mailinglist">mailing list</a></b> requesting an +<b><a href="#ACK">ACK</a></b> (in order to verify that +everybody's addresses are reachable). "We haven't heard much of +anything from Geoff, but he did respond with an ACK both times I +pinged jargon-friends." 5. n. A quantum packet of happiness. +People who are very happy tend to exude pings; furthermore, one +can intentionally create pings and aim them at a needy party +(e.g., a depressed person). This sense of ping may appear as an +exclamation; "Ping!" (I'm happy; I am emitting a quantum of +happiness; I have been struck by a quantum of happiness). The +form "pingfulness", which is used to describe people who exude +pings, also occurs. (In the standard abuse of language, +"pingfulness" can also be used as an exclamation, in which case +it's a much stronger exclamation than just "ping"!). Oppose <b><a +href="#blargh">blargh</a></b>.</p> + +<p>The funniest use of `ping' to date was described in January +1991 by Steve Hayman on the Usenet group <i>comp.sys.next</i>. He +was trying to isolate a faulty cable segment on a TCP/IP Ethernet +hooked up to a NeXT machine, and got tired of having to run back +to his console after each cabling tweak to see if the ping +packets were getting through. So he used the sound-recording +feature on the NeXT, then wrote a script that repeatedly invoked +<code>ping(8)</code>, listened for an echo, and played back the +recording on each returned packet. Result? A program that caused +the machine to repeat, over and over, "Ping <small>...</small> +ping <small>...</small> ping <small>...</small>" as long as the +network was up. He turned the volume to maximum, ferreted through +the building with one ear cocked, and found a faulty tee +connector in no time.</p> + +<hr> +Node:<a name="PingODeath">Ping O' Death</a>, Next:<a rel="next" href="#pingstorm">ping storm</a>, Previous:<a rel="previous" href="#ping">ping</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>Ping O' Death</b> n.</p> + +<p>A notorious <b><a href="#exploit">exploit</a></b> that (when +first discovered) could be easily used to crash a wide variety of +machines by overunning size limits in their TCP/IP stacks. First +revealed in late 1996. The open-source Unix community patched its +systems to remove the vulnerability within days or weeks, the +closed-source OS vendors generally took months. While the +difference in response times repeated a pattern familiar from +other security incidents, the accompanying glare of Web-fueled +publicity proved unusually embarrassing to the OS vendors and so +passed into history and myth. The term is now used to refer to +any nudge delivered by network wizards over the network that +causes bad things to happen on the system being nudged. For the +full story on the original exploit, see http://www.insecure.org/sploits/ping-o-death.html.</p> + +<p>Compare with 'kamikaze packet,' 'Finger of Death' and +'Chernobyl packet.'</p> + +<hr> +Node:<a name="pingstorm">ping storm</a>, Next:<a rel="next" +href="#pinkwire">pink wire</a>, Previous:<a rel="previous" +href="#PingODeath">Ping O' Death</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>ping storm</b> n.</p> + +<p>A form of <b><a href="#DoSattack">DoS attack</a></b> +consisting of a flood of <b><a href="#ping">ping</a></b> requests +(normally used to check network conditions) designed to disrupt +the normal activity of a system. This act is sometimes called +`ping lashing' or `ping flood'. Compare <b><a href="#mailstorm">mail storm</a></b>, <b><a href="#broadcaststorm">broadcast storm</a></b>.</p> + +<hr> +Node:<a name="pinkwire">pink wire</a>, Next:<a rel="next" +href="#pipe">pipe</a>, Previous:<a rel="previous" href="#pingstorm">ping storm</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>pink wire</b> n.</p> + +<p>[from the pink PTFE wire used in military equipment] As <b><a +href="#bluewire">blue wire</a></b>, but used in military +applications. 2. vi. To add a pink wire to a board.</p> + +<hr> +Node:<a name="pipe">pipe</a>, Next:<a rel="next" href="#pistol">pistol</a>, Previous:<a rel="previous" href="#pinkwire">pink wire</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>pipe</b> n.</p> + +<p>[common] Idiomatically, one's connection to the Internet; in +context, the expansion "bit pipe" is understood. A "fat pipe" is +a line with T1 or higher capacity. A person with a 28.8 modem +might be heard to complain "I need a bigger pipe".</p> + +<hr> +Node:<a name="pistol">pistol</a>, Next:<a rel="next" href="#pixelsort">pixel sort</a>, Previous:<a rel="previous" href="#pipe">pipe</a>, Up:<a rel="up" href="#chap16">= P =</a> +<br> + + +<p><b>pistol</b> n.</p> + +<p>[IBM] A tool that makes it all too easy for you to shoot +yourself in the foot. "Unix <code>rm *</code> makes such a nice +pistol!"</p> + +<hr> +Node:<a name="pixelsort">pixel sort</a>, Next:<a rel="next" +href="#pizzabox">pizza box</a>, Previous:<a rel="previous" +href="#pistol">pistol</a>, Up:<a rel="up" href="#chap16">= +P =</a> <br> + + +<p><b>pixel sort</b> n.</p> + +<p>[Commodore users] Any compression routine which irretrievably +loses valuable data in the process of <b><a href="#crunch">crunch</a></b>ing it. Disparagingly used for `lossy' +methods such as JPEG. The theory, of course, is that these +methods are only used on photographic images in which minor +loss-of-data is not visible to the human eye. The term `pixel +sort' implies distrust of this theory. Compare <b><a href="#bogo-sort">bogo-sort</a></b>.</p> + +<hr> +Node:<a name="pizzabox">pizza box</a>, Next:<a rel="next" +href="#plaidscreen">plaid screen</a>, Previous:<a rel="previous" href="#pixelsort">pixel sort</a>, Up:<a rel="up" +href="#chap16">= P =</a> <br> + + +<p><b>pizza box</b> n.</p> + +<p>[Sun] The largish thin box housing the electronics in +(especially Sun) desktop workstations, so named because of its +size and shape and the dimpled pattern that looks like air +holes.</p> + +<p>Two meg single-platter removable disk packs used to be called +pizzas, and the huge drive they were stuck into was referred to +as a pizza oven. It's an index of progress that in the old days +just the disk was pizza-sized, while now the entire computer +is.</p> + +<hr> +Node:<a name="plaidscreen">plaid screen</a>, Next:<a rel="next" href="#plain-ASCII">plain-ASCII</a>, Previous:<a rel="previous" href="#pizzabox">pizza box</a>, Up:<a rel="up" +href="#chap16">= P =</a> <br> + + +<p><b>plaid screen</b> n.</p> + +<p>[XEROX PARC] A `special effect' that occurs when certain kinds +of <b><a href="#memorysmash">memory smash</a></b>es overwrite +the control blocks or image memory of a bit-mapped display. The +term "salt and pepper" may refer to a different pattern of +similar origin. Though the term as coined at PARC refers to the +result of an error, some of the <b><a href="#X">X</a></b> demos +induce plaid-screen effects deliberately as a <b><a href="#displayhack">display hack</a></b>.</p> + +<hr> +Node:<a name="plain-ASCII">plain-ASCII</a>, Next:<a rel="next" +href="#planfile">plan file</a>, Previous:<a rel="previous" +href="#plaidscreen">plaid screen</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>plain-ASCII</b> /playn-as'kee/</p> + +<p>Syn. <b><a href="#flat-ASCII">flat-ASCII</a></b>.</p> + +<hr> +Node:<a name="planfile">plan file</a>, Next:<a rel="next" +href="#platinum-iridium">platinum-iridium</a>, Previous:<a rel="previous" href="#plain-ASCII">plain-ASCII</a>, Up:<a rel="up" +href="#chap16">= P =</a> <br> + + +<p><b>plan file</b> n.</p> + +<p>[Unix] On systems that support <b><a href="#finger">finger</a></b>, the `.plan' file in a user's home +directory is displayed when the user is fingered. This feature +was originally intended to be used to keep potential fingerers +apprised of one's location and near-future plans, but has been +turned almost universally to humorous and self-expressive +purposes (like a <b><a href="#sigblock">sig block</a></b>). +See also <b><a href="#HackingXforY">Hacking X for +Y</a></b>.</p> + +<p>A recent innovation in plan files has been the introduction of +"scrolling plan files" which are one-dimensional animations made +using only the printable ASCII character set, carriage return and +line feed, avoiding terminal specific escape sequences, since the +<b><a href="#finger">finger</a></b> command will (for security +reasons; see <b><a href="#letterbomb">letterbomb</a></b>) not +pass the escape character.</p> + +<p>Scrolling .plan files have become art forms in miniature, and +some sites have started competitions to find who can create the +longest running, funniest, and most original animations. Various +animation characters include:</p> + +<dl> +<dt><tt>Centipede:</tt></dt> + +<dd>mmmmme<br> +</dd> + +<dt><tt>Lorry/Truck:</tt></dt> + +<dd>oo-oP<br> +</dd> + +<dt><tt>Andalusian Video Snail:</tt></dt> + +<dd>_@/</dd> +</dl> + +<br> +<p>and a compiler (ASP) is available on Usenet for producing +them. See also <b><a href="#twirlingbaton">twirling +baton</a></b>.</p> + +<hr> +Node:<a name="platinum-iridium">platinum-iridium</a>, Next:<a +rel="next" href="#playpen">playpen</a>, Previous:<a rel="previous" href="#planfile">plan file</a>, Up:<a rel="up" +href="#chap16">= P =</a> <br> + + +<p><b>platinum-iridium</b> adj.</p> + +<p>Standard, against which all others of the same category are +measured. Usage: silly. The notion is that one of whatever it is +has actually been cast in platinum-iridium alloy and placed in +the vault beside the Standard Kilogram at the International +Bureau of Weights and Measures near Paris. (From 1889 to 1960, +the meter was defined to be the distance between two scratches in +a platinum-iridium bar kept in that same vault -- this replaced +an earlier definition as 10^(-7) times the distance between the +North Pole and the Equator along a meridian through Paris; +unfortunately, this had been based on an inexact value of the +circumference of the Earth. From 1960 to 1984 it was defined to +be 1650763.73 wavelengths of the orange-red line of krypton-86 +propagating in a vacuum. It is now defined as the length of the +path traveled by light in a vacuum in the time interval of +1/299,792,458 of a second. The kilogram is now the only unit of +measure officially defined in terms of a unique artifact.) "This +garbage-collection algorithm has been tested against the +platinum-iridium cons cell in Paris." Compare <b><a href="#golden">golden</a></b>.</p> + +<hr> +Node:<a name="playpen">playpen</a>, Next:<a rel="next" href="#playte">playte</a>, Previous:<a rel="previous" href="#platinum-iridium">platinum-iridium</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>playpen</b> n.</p> + +<p>[IBM] A room where programmers work. Compare <b><a href="#saltmines">salt mines</a></b>.</p> + +<hr> +Node:<a name="playte">playte</a>, Next:<a rel="next" href="#plingnet">plingnet</a>, Previous:<a rel="previous" href="#playpen">playpen</a>, Up:<a rel="up" href="#chap16">= P +=</a> <br> + + +<p><b>playte</b> /playt/</p> + +<p>16 bits, by analogy with <b><a href="#nybble">nybble</a></b> +and <b><a href="#byte">byte</a></b>. Usage: rare and extremely +silly. See also <b><a href="#dynner">dynner</a></b> and <b><a +href="#crumb">crumb</a></b>. General discussion of such terms is +under <b><a href="#nybble">nybble</a></b>.</p> + +<hr> +Node:<a name="plingnet">plingnet</a>, Next:<a rel="next" href="#plokta">plokta</a>, Previous:<a rel="previous" href="#playte">playte</a>, Up:<a rel="up" href="#chap16">= P +=</a> <br> + + +<p><b>plingnet</b> /pling'net/ n.</p> + +<p>Syn. <b><a href="#UUCPNET">UUCPNET</a></b>. Also see <b><a +href="#CommonwealthHackish">Commonwealth Hackish</a></b>, +which uses `pling' for <b><a href="#bang">bang</a></b> (as in +<b><a href="#bangpath">bang path</a></b>).</p> + +<hr> +Node:<a name="plokta">plokta</a>, Next:<a rel="next" href="#plonk">plonk</a>, Previous:<a rel="previous" href="#plingnet">plingnet</a>, Up:<a rel="up" href="#chap16">= +P =</a> <br> + + +<p><b>plokta</b> /plok't*/ v.</p> + +<p>[acronym: Press Lots Of Keys To Abort] To press random keys in +an attempt to get some response from the system. One might plokta +when the abort procedure for a program is not known, or when +trying to figure out if the system is just sluggish or really +hung. Plokta can also be used while trying to figure out any +unknown key sequence for a particular operation. Someone going +into `plokta mode' usually places both hands flat on the keyboard +and mashes them down, hoping for some useful response.</p> + +<p>A slightly more directed form of plokta can often be seen in +mail messages or Usenet articles from new users -- the text might +end with</p> + +<pre> + ^X^C + q + quit + :q + ^C + end + x + exit + ZZ + ^D + ? + help +</pre> + +<p>as the user vainly tries to find the right exit sequence, with +the incorrect tries piling up at the end of the +message<small>...</small>.</p> + +<hr> +Node:<a name="plonk">plonk</a>, Next:<a rel="next" href="#plug-and-pray">plug-and-pray</a>, Previous:<a rel="previous" +href="#plokta">plokta</a>, Up:<a rel="up" href="#chap16">= +P =</a> <br> + + +<p><b>plonk</b> excl.,vt.</p> + +<p>[Usenet: possibly influenced by British slang `plonk' for +cheap booze, or `plonker' for someone behaving stupidly (latter +is lit. equivalent to Yiddish `schmuck')] The sound a <b><a href="#newbie">newbie</a></b> makes as he falls to the bottom of a +<b><a href="#killfile">kill file</a></b>. While it originated +in the <b><a href="#newsgroup">newsgroup</a></b> +<i>talk.bizarre</i>, this term (usually written "*plonk*") is now +(1994) widespread on Usenet as a form of public ridicule.</p> + +<hr> +Node:<a name="plug-and-pray">plug-and-pray</a>, Next:<a rel="next" href="#plugh">plugh</a>, Previous:<a rel="previous" href="#plonk">plonk</a>, Up:<a rel="up" href="#chap16">= P +=</a> <br> + + +<p><b>plug-and-pray</b> adj.,vi.</p> + +<p>Parody of the techspeak term `plug-and-play', describing a PC +peripheral card which is claimed to have no need for hardware +configuration via DIP switches, and which should be work as soon +as it is inserted in the PC. Unfortunately, even the PCI bus is +not up to pulling this off reliably, and people who have to do +installation or troubleshoot PCs soon find themselves longing for +the DIP switches.</p> + +<hr> +Node:<a name="plugh">plugh</a>, Next:<a rel="next" href="#plumbing">plumbing</a>, Previous:<a rel="previous" href="#plug-and-pray">plug-and-pray</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>plugh</b> /ploogh/ v.</p> + +<p>[from the <b><a href="#ADVENT">ADVENT</a></b> game] See <b><a +href="#xyzzy">xyzzy</a></b>.</p> + +<hr> +Node:<a name="plumbing">plumbing</a>, Next:<a rel="next" href="#PM">PM</a>, Previous:<a rel="previous" href="#plugh">plugh</a>, +Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>plumbing</b> n.</p> + +<p>[Unix] Term used for <b><a href="#shell">shell</a></b> code, +so called because of the prevalence of `pipelines' that feed the +output of one program to the input of another. Under Unix, user +utilities can often be implemented or at least prototyped by a +suitable collection of pipelines and temp-file grinding +encapsulated in a shell script; this is much less effort than +writing C every time, and the capability is considered one of +Unix's major winning features. A few other OSs such as IBM's +VM/CMS support similar facilities. Esp. used in the construction +`hairy plumbing' (see <b><a href="#hairy">hairy</a></b>). "You +can kluge together a basic spell-checker out of +<code>sort(1)</code>, <code>comm(1)</code>, and +<code>tr(1)</code> with a little plumbing." See also <b><a href="#tee">tee</a></b>.</p> + +<hr> +Node:<a name="PM">PM</a>, Next:<a rel="next" href="#pnambic">pnambic</a>, Previous:<a rel="previous" href="#plumbing">plumbing</a>, Up:<a rel="up" href="#chap16">= +P =</a> <br> + + +<p><b>PM</b> /P-M/</p> + +<p>1. v. (from `preventive maintenance') To bring down a machine +for inspection or test purposes. See <b><a href="#provocativemaintenance">provocative maintenance</a></b>; see +also <b><a href="#scratchmonkey">scratch monkey</a></b>. 2. n. +Abbrev. for `Presentation Manager', an <b><a href="#elephantine">elephantine</a></b> OS/2 graphical user +interface.</p> + +<hr> +Node:<a name="pnambic">pnambic</a>, Next:<a rel="next" href="#pod">pod</a>, Previous:<a rel="previous" href="#PM">PM</a>, +Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>pnambic</b> /p*-nam'bik/</p> + +<p>[Acronym from the scene in the film version of "The Wizard of +Oz" in which the true nature of the wizard is first discovered: +"Pay no attention to the man behind the curtain."] 1. A stage of +development of a process or function that, owing to incomplete +implementation or to the complexity of the system, requires human +interaction to simulate or replace some or all of the actions, +inputs, or outputs of the process or function. 2. Of or +pertaining to a process or function whose apparent operations are +wholly or partially falsified. 3. Requiring <b><a href="#prestidigitization">prestidigitization</a></b>.</p> + +<p>The ultimate pnambic product was "Dan Bricklin's Demo", a +program which supported flashy user-interface design prototyping. +There is a related maxim among hackers: "Any sufficiently +advanced technology is indistinguishable from a rigged demo." See +<b><a href="#magic">magic</a></b>, sense 1, for illumination of +this point.</p> + +<hr> +Node:<a name="pod">pod</a>, Next:<a rel="next" href="#pointanddroolinterface">point-and-drool interface</a>, +Previous:<a rel="previous" href="#pnambic">pnambic</a>, Up:<a +rel="up" href="#chap16">= P =</a> <br> + + +<p><b>pod</b> n.</p> + +<p>[allegedly from abbreviation POD for `Prince Of Darkness'] A +Diablo 630 (or, latterly, any letter-quality impact printer). +From the DEC-10 PODTYPE program used to feed formatted text to +it. Not to be confused with <b><a href="#P.O.D.">P.O.D.</a></b>.</p> + +<hr> +Node:<a name="pointanddroolinterface">point-and-drool +interface</a>, Next:<a rel="next" href="#pointyhat">pointy +hat</a>, Previous:<a rel="previous" href="#pod">pod</a>, Up:<a +rel="up" href="#chap16">= P =</a> <br> + + +<p><b>point-and-drool interface</b> n.</p> + +<p>Parody of the techspeak term `point-and-shoot interface', +describing a windows, icons, and mouse-based interface such as is +found on the Macintosh. The implication, of course, is that such +an interface is only suitable for idiots. See <b><a href="#fortherestofus">for the rest of us</a></b>, <b><a +href="#WIMPenvironment">WIMP environment</a></b>, <b><a href="#Macintrash">Macintrash</a></b>, <b><a href="#droolproofpaper">drool-proof paper</a></b>. Also +`point-and-grunt interface'.</p> + +<hr> +Node:<a name="pointyhat">pointy hat</a>, Next:<a rel="next" +href="#pointy-haired">pointy-haired</a>, Previous:<a rel="previous" href="#pointanddroolinterface">point-and-drool +interface</a>, Up:<a rel="up" href="#chap16">= P =</a> +<br> + + +<p><b>pointy hat</b> n.</p> + +<p>See <b><a href="#wizardhat">wizard hat</a></b>. This +synonym specifically refers to the wizards of Unseen University +in Terry Pratchett's "Discworld" serious of humorous fantasies; +these books are extremely popular among hackers.</p> + +<hr> +Node:<a name="pointy-haired">pointy-haired</a>, Next:<a rel="next" href="#poke">poke</a>, Previous:<a rel="previous" href="#pointyhat">pointy hat</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>pointy-haired</b> adj.</p> + +<p>[after the character in the <b><a href="#Dilbert">Dilbert</a></b> comic strip] Describes the extreme +form of the property that separates <b><a href="#suit">suit</a></b>s and <b><a href="#marketroid">marketroid</a></b>s from hackers. Compare <b><a +href="#brain-dead">brain-dead</a></b>; <b><a href="#demented">demented</a></b>; see <b><a href="#PHB">PHB</a></b>. +Always applied to people, never to ideas. The plural form is +often used as a noun. "The pointy-haireds ordered me to use +Windows NT, but I set up a Linux server with Samba instead."</p> + +<hr> +Node:<a name="poke">poke</a>, Next:<a rel="next" href="#poll">poll</a>, Previous:<a rel="previous" href="#pointy-haired">pointy-haired</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>poke</b> n.,vt.</p> + +<p>See <b><a href="#peek">peek</a></b>.</p> + +<hr> +Node:<a name="poll">poll</a>, Next:<a rel="next" href="#polygonpusher">polygon pusher</a>, Previous:<a rel="previous" href="#poke">poke</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>poll</b> v.,n.</p> + +<p>1. [techspeak] The action of checking the status of an input +line, sensor, or memory location to see if a particular external +event has been registered. 2. To repeatedly call or check with +someone: "I keep polling him, but he's not answering his phone; +he must be swapped out." 3. To ask. "Lunch? I poll for a takeout +order daily."</p> + +<hr> +Node:<a name="polygonpusher">polygon pusher</a>, Next:<a rel="next" href="#POM">POM</a>, Previous:<a rel="previous" href="#poll">poll</a>, Up:<a rel="up" href="#chap16">= P =</a> +<br> + + +<p><b>polygon pusher</b> n.</p> + +<p>A chip designer who spends most of his or her time at the +physical layout level (which requires drawing <i>lots</i> of +multi-colored polygons). Also `rectangle slinger'.</p> + +<hr> +Node:<a name="POM">POM</a>, Next:<a rel="next" href="#pop">pop</a>, Previous:<a rel="previous" href="#polygonpusher">polygon pusher</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>POM</b> /P-O-M/ n.</p> + +<p>Common abbreviation for <b><a href="#phaseofthemoon">phase of the moon</a></b>. Usage: +usually in the phrase `POM-dependent', which means <b><a href="#flaky">flaky</a></b>.</p> + +<hr> +Node:<a name="pop">pop</a>, Next:<a rel="next" href="#POPJ">POPJ</a>, Previous:<a rel="previous" href="#POM">POM</a>, +Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>pop</b> /pop/</p> + +<p>[from the operation that removes the top of a stack, and the +fact that procedure return addresses are usually saved on the +stack] (also capitalized `POP') 1. vt. To remove something from a +<b><a href="#stack">stack</a></b> or <b><a href="#PDL">PDL</a></b>. If a person says he/she has popped something +from his stack, that means he/she has finally finished working on +it and can now remove it from the list of things hanging +overhead. 2. When a discussion gets to a level of detail so deep +that the main point of the discussion is being lost, someone will +shout "Pop!", meaning "Get back up to a higher level!" The shout +is frequently accompanied by an upthrust arm with a finger +pointing to the ceiling. 3. [all-caps, as `POP'] Point of +Presence, a bank of dial-in lines allowing customers to make +(local) calls into an ISP. This is borderline techspeak.</p> + +<hr> +Node:<a name="POPJ">POPJ</a>, Next:<a rel="next" href="#poser">poser</a>, Previous:<a rel="previous" href="#pop">pop</a>, Up:<a rel="up" href="#chap16">= P =</a> +<br> + + +<p><b>POPJ</b> /pop'J/ n.,v.</p> + +<p>[from a <b><a href="#PDP-10">PDP-10</a></b> +return-from-subroutine instruction] To return from a digression. +By verb doubling, "Popj, popj" means roughly "Now let's see, +where were we?" See <b><a href="#RTI">RTI</a></b>.</p> + +<hr> +Node:<a name="poser">poser</a>, Next:<a rel="next" href="#post">post</a>, Previous:<a rel="previous" href="#POPJ">POPJ</a>, Up:<a rel="up" href="#chap16">= P =</a> +<br> + + +<p><b>poser</b> n.</p> + +<p>A <b><a href="#wannabee">wannabee</a></b>; not hacker slang, +but used among crackers, phreaks and <b><a href="#warezd00dz">warez d00dz</a></b>. Not as negative as <b><a +href="#lamer">lamer</a></b> or <b><a href="#leech">leech</a></b>. +Probably derives from a similar usage among punk-rockers and +metalheads, putting down those who "talk the talk but don't walk +the walk".</p> + +<hr> +Node:<a name="post">post</a>, Next:<a rel="next" href="#postcardware">postcardware</a>, Previous:<a rel="previous" +href="#poser">poser</a>, Up:<a rel="up" href="#chap16">= P +=</a> <br> + + +<p><b>post</b> v.</p> + +<p>To send a message to a <b><a href="#mailinglist">mailing +list</a></b> or <b><a href="#newsgroup">newsgroup</a></b>. +Distinguished in context from `mail'; one might ask, for example: +"Are you going to post the patch or mail it to known users?"</p> + +<hr> +Node:<a name="postcardware">postcardware</a>, Next:<a rel="next" +href="#posting">posting</a>, Previous:<a rel="previous" href="#post">post</a>, Up:<a rel="up" href="#chap16">= P =</a> +<br> + + +<p><b>postcardware</b> n.</p> + +<p>A kind of <b><a href="#shareware">shareware</a></b> that +borders on <b><a href="#freeware">freeware</a></b>, in that the +author requests only that satisfied users send a postcard of +their home town or something. (This practice, silly as it might +seem, serves to remind users that they are otherwise getting +something for nothing, and may also be psychologically related to +real estate `sales' in which $1 changes hands just to keep the +transaction from being a gift.)</p> + +<hr> +Node:<a name="posting">posting</a>, Next:<a rel="next" href="#postmaster">postmaster</a>, Previous:<a rel="previous" href="#postcardware">postcardware</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>posting</b> n.</p> + +<p>Noun corresp. to v. <b><a href="#post">post</a></b> (but note +that <b><a href="#post">post</a></b> can be nouned). +Distinguished from a `letter' or ordinary <b><a href="#email">email</a></b> message by the fact that it is broadcast +rather than point-to-point. It is not clear whether messages sent +to a small mailing list are postings or email; perhaps the best +dividing line is that if you don't know the names of all the +potential recipients, it is a posting.</p> + +<hr> +Node:<a name="postmaster">postmaster</a>, Next:<a rel="next" +href="#PostScript">PostScript</a>, Previous:<a rel="previous" +href="#posting">posting</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>postmaster</b> n.</p> + +<p>The email contact and maintenance person at a site connected +to the Internet or UUCPNET. Often, but not always, the same as +the <b><a href="#admin">admin</a></b>. The Internet standard for +electronic mail (<b><a href="#RFC">RFC</a></b>-822) requires each +machine to have a `postmaster' address; usually it is aliased to +this person.</p> + +<hr> +Node:<a name="PostScript">PostScript</a>, Next:<a rel="next" +href="#poundon">pound on</a>, Previous:<a rel="previous" href="#postmaster">postmaster</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>PostScript</b> n.</p> + +<p>A Page Description Language (<b><a href="#PDL">PDL</a></b>), +based on work originally done by John Gaffney at Evans and +Sutherland in 1976, evolving through `JaM' (`John and Martin', +Martin Newell) at <b><a href="#XEROXPARC">XEROX PARC</a></b>, +and finally implemented in its current form by John Warnock et +al. after he and Chuck Geschke founded Adobe Systems Incorporated +in 1982. PostScript gets its leverage by using a full programming +language, rather than a series of low-level escape sequences, to +describe an image to be printed on a laser printer or other +output device (in this it parallels <b><a href="#EMACS">EMACS</a></b>, which exploited a similar insight about +editing tasks). It is also noteworthy for implementing on-the fly +rasterization, from Bezier curve descriptions, of high-quality +fonts at low (e.g. 300 dpi) resolution (it was formerly believed +that hand-tuned bitmap fonts were required for this task). +Hackers consider PostScript to be among the most elegant hacks of +all time, and the combination of technical merits and widespread +availability has made PostScript the language of choice for +graphical output.</p> + +<hr> +Node:<a name="poundon">pound on</a>, Next:<a rel="next" href="#powercycle">power cycle</a>, Previous:<a rel="previous" +href="#PostScript">PostScript</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>pound on</b> vt.</p> + +<p>Syn. <b><a href="#bangon">bang on</a></b>.</p> + +<hr> +Node:<a name="powercycle">power cycle</a>, Next:<a rel="next" +href="#powerhit">power hit</a>, Previous:<a rel="previous" +href="#poundon">pound on</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>power cycle</b> vt.</p> + +<p>(also, `cycle power' or just `cycle') To power off a machine +and then power it on immediately, with the intention of clearing +some kind of <b><a href="#hung">hung</a></b> or <b><a href="#gronk">gronk</a></b>ed state. Syn. <b><a href="#120reset">120 reset</a></b>; see also <b><a href="#BigRedSwitch">Big Red Switch</a></b>. Compare <b><a href="#Vulcannervepinch">Vulcan nerve pinch</a></b>, <b><a href="#bounce">bounce</a></b> (sense 4), and <b><a href="#boot">boot</a></b>, and see the "<b><a href="#SomeAIKoans">Some AI Koans</a></b>" (in Appendix A) about +Tom Knight and the novice.</p> + +<hr> +Node:<a name="powerhit">power hit</a>, Next:<a rel="next" +href="#PPN">PPN</a>, Previous:<a rel="previous" href="#powercycle">power cycle</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>power hit</b> n.</p> + +<p>A spike or drop-out in the electricity supplying your machine; +a power <b><a href="#glitch">glitch</a></b>. These can cause +crashes and even permanent damage to your machine(s).</p> + +<hr> +Node:<a name="PPN">PPN</a>, Next:<a rel="next" href="#pr0n">pr0n</a>, Previous:<a rel="previous" href="#powerhit">power hit</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>PPN</b> /P-P-N/, /pip'n/ n. obs.</p> + +<p>[from `Project-Programmer Number'] A user-ID under <b><a href="#TOPS-10">TOPS-10</a></b> and its various mutant progeny at +SAIL, BBN, CompuServe, and elsewhere. Old-time hackers from the +PDP-10 era sometimes use this to refer to user IDs on other +systems as well.</p> + +<hr> +Node:<a name="pr0n">pr0n</a>, Next:<a rel="next" href="#precedencelossage">precedence lossage</a>, Previous:<a rel="previous" href="#PPN">PPN</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>pr0n</b> //</p> + +<p>[Usenet, IRC] Pornography. Originally this referred only to +Internet porn but since then it has expanded to refer to just +about anything. The term comes from the <b><a href="#warezkiddies">warez kiddies</a></b> tendency to replace +letters with numbers. At some point on IRC someone mistyped, +swapped the middle two letters, and the name stuck, then +propagated over into mainstream hacker usage. Compare <b><a href="#filk">filk</a></b>, <b><a href="#grilf">grilf</a></b>, <b><a +href="#hing">hing</a></b> and <b><a href="#newsfroup">newsfroup</a></b>.</p> + +<hr> +Node:<a name="precedencelossage">precedence lossage</a>, +Next:<a rel="next" href="#prepend">prepend</a>, Previous:<a rel="previous" href="#pr0n">pr0n</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>precedence lossage</b> /pre's*-dens los'*j/ n.</p> + +<p>[C programmers] Coding error in an expression due to +unexpected grouping of arithmetic or logical operators by the +compiler. Used esp. of certain common coding errors in C due to +the nonintuitively low precedence levels of <code>&</code>, +<code>|</code>, <code>^</code>, <code><<</code>, and +<code>>></code> (for this reason, experienced C programmers +deliberately forget the language's <b><a href="#baroque">baroque</a></b> precedence hierarchy and parenthesize +defensively). Can always be avoided by suitable use of +parentheses. <b><a href="#LISP">LISP</a></b> fans enjoy pointing +out that this can't happen in <i>their</i> favorite language, +which eschews precedence entirely, requiring one to use explicit +parentheses everywhere. See <b><a href="#aliasingbug">aliasing +bug</a></b>, <b><a href="#memoryleak">memory leak</a></b>, +<b><a href="#memorysmash">memory smash</a></b>, <b><a href="#smashthestack">smash the stack</a></b>, <b><a href="#fandangooncore">fandango on core</a></b>, <b><a href="#overrunscrew">overrun screw</a></b>.</p> + +<hr> +Node:<a name="prepend">prepend</a>, Next:<a rel="next" href="#prestidigitization">prestidigitization</a>, Previous:<a rel="previous" href="#precedencelossage">precedence lossage</a>, +Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>prepend</b> /pree`pend'/ vt.</p> + +<p>[by analogy with `append'] To prefix. As with `append' (but +not `prefix' or `suffix' as a verb), the direct object is always +the thing being added and not the original word (or character +string, or whatever). "If you prepend a semicolon to the line, +the translation routine will pass it through unaltered."</p> + +<hr> +Node:<a name="prestidigitization">prestidigitization</a>, Next:<a +rel="next" href="#prettypictures">pretty pictures</a>, +Previous:<a rel="previous" href="#prepend">prepend</a>, Up:<a +rel="up" href="#chap16">= P =</a> <br> + + +<p><b>prestidigitization</b> /pres`t*-di`j*-ti:-zay'sh*n/ n.</p> + +<p>1. The act of putting something into digital notation via +sleight of hand. 2. Data entry through legerdemain.</p> + +<hr> +Node:<a name="prettypictures">pretty pictures</a>, Next:<a +rel="next" href="#prettyprint">prettyprint</a>, Previous:<a rel="previous" href="#prestidigitization">prestidigitization</a>, +Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>pretty pictures</b> n.</p> + +<p>[scientific computation] The next step up from <b><a href="#numbers">numbers</a></b>. Interesting graphical output from a +program that may not have any sensible relationship to the system +the program is intended to model. Good for showing to <b><a href="#management">management</a></b>.</p> + +<hr> +Node:<a name="prettyprint">prettyprint</a>, Next:<a rel="next" +href="#pretzelkey">pretzel key</a>, Previous:<a rel="previous" +href="#prettypictures">pretty pictures</a>, Up:<a rel="up" +href="#chap16">= P =</a> <br> + + +<p><b>prettyprint</b> /prit'ee-print/ v.</p> + +<p>(alt. `pretty-print') 1. To generate `pretty' human-readable +output from a <b><a href="#hairy">hairy</a></b> internal +representation; esp. used for the process of <b><a href="#grind">grind</a></b>ing (sense 1) program code, and most esp. +for LISP code. 2. To format in some particularly slick and +nontrivial way.</p> + +<hr> +Node:<a name="pretzelkey">pretzel key</a>, Next:<a rel="next" +href="#priesthood">priesthood</a>, Previous:<a rel="previous" +href="#prettyprint">prettyprint</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>pretzel key</b> n.</p> + +<p>[Mac users] See <b><a href="#featurekey">feature +key</a></b>.</p> + +<hr> +Node:<a name="priesthood">priesthood</a>, Next:<a rel="next" +href="#primeTime">prime time</a>, Previous:<a rel="previous" +href="#pretzelkey">pretzel key</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>priesthood</b> n. obs.</p> + +<p>[TMRC] The select group of system managers responsible for the +operation and maintenance of a batch operated computer system. On +these computers, a user never had direct access to a computer, +but had to submit his/her data and programs to a priest for +execution. Results were returned days or even weeks later. See +<b><a href="#acolyte">acolyte</a></b>.</p> + +<hr> +Node:<a name="primeTime">prime time</a>, Next:<a rel="next" +href="#print">print</a>, Previous:<a rel="previous" href="#priesthood">priesthood</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>prime time</b> n.</p> + +<p>[from TV programming] Normal high-usage hours on a system or +network. Back in the days of big timesharing machines `prime +time' was when lots of people were competing for limited cycles, +usually the day shift. Avoidance of prime time was traditionally +given as a major reason for <b><a href="#nightmode">night +mode</a></b> hacking. The term fell into disuse during the early +PC era, but has been revived to refer to times of day or evening +at which the Internet tends to be heavily loaded, making Web +access slow. The hackish tendency to late-night <b><a href="#hackingrun">hacking run</a></b>s has changed not a bit.</p> + +<hr> +Node:<a name="print">print</a>, Next:<a rel="next" href="#printingdiscussion">printing discussion</a>, Previous:<a +rel="previous" href="#primeTime">prime time</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>print</b> v.</p> + +<p>To output, even if to a screen. If a hacker says that a +program "printed a message", he means this; if he refers to +printing a file, he probably means it in the conventional sense +of writing to a hardcopy device (compounds like `print job' and +`printout', on the other hand, always refer to the latter). This +very common term is likely a holdover from the days when printing +terminals were the norm, perpetuated by programming language +constructs like <b><a href="#C">C</a></b>'s printf(3). See senses +1 and 2 of <b><a href="#tty">tty</a></b>.</p> + +<hr> +Node:<a name="printingdiscussion">printing discussion</a>, +Next:<a rel="next" href="#priorityinterrupt">priority +interrupt</a>, Previous:<a rel="previous" href="#print">print</a>, Up:<a rel="up" href="#chap16">= P +=</a> <br> + + +<p><b>printing discussion</b> n.</p> + +<p>[XEROX PARC] A protracted, low-level, time-consuming, +generally pointless discussion of something only peripherally +interesting to all.</p> + +<hr> +Node:<a name="priorityinterrupt">priority interrupt</a>, +Next:<a rel="next" href="#profile">profile</a>, Previous:<a rel="previous" href="#printingdiscussion">printing discussion</a>, +Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>priority interrupt</b> n.</p> + +<p>[from the hardware term] Describes any stimulus compelling +enough to yank one right out of <b><a href="#hackmode">hack +mode</a></b>. Classically used to describe being dragged away by +an <b><a href="#SO">SO</a></b> for immediate sex, but may also +refer to more mundane interruptions such as a fire alarm going +off in the near vicinity. Also called an <b><a href="#NMI">NMI</a></b> (non-maskable interrupt), especially in +PC-land.</p> + +<hr> +Node:<a name="profile">profile</a>, Next:<a rel="next" href="#progasm">progasm</a>, Previous:<a rel="previous" href="#priorityinterrupt">priority interrupt</a>, Up:<a rel="up" +href="#chap16">= P =</a> <br> + + +<p><b>profile</b> n.</p> + +<p>1. A control file for a program, esp. a text file +automatically read from each user's home directory and intended +to be easily modified by the user in order to customize the +program's behavior. Used to avoid <b><a href="#hardcoded">hardcoded</a></b> choices (see also <b><a href="#dotfile">dot file</a></b>, <b><a href="#rcfile">rc +file</a></b>). 2. [techspeak] A report on the amounts of time +spent in each routine of a program, used to find and <b><a href="#tune">tune</a></b> away the <b><a href="#hotspot">hot +spot</a></b>s in it. This sense is often verbed. Some profiling +modes report units other than time (such as call counts) and/or +report at granularities other than per-routine, but the idea is +similar. 3.[techspeak] A subset of a standard used for a +particular purpose. This sense confuses hackers who wander into +the weird world of ISO standards no end!</p> + +<hr> +Node:<a name="progasm">progasm</a>, Next:<a rel="next" href="#proggy">proggy</a>, Previous:<a rel="previous" href="#profile">profile</a>, Up:<a rel="up" href="#chap16">= P +=</a> <br> + + +<p><b>progasm</b> /proh'gaz-m/ n.</p> + +<p>[University of Wisconsin] The euphoria experienced upon the +completion of a program or other computer-related project.</p> + +<hr> +Node:<a name="proggy">proggy</a>, Next:<a rel="next" href="#proglet">proglet</a>, Previous:<a rel="previous" href="#progasm">progasm</a>, Up:<a rel="up" href="#chap16">= P +=</a> <br> + + +<p><b>proggy</b> n.</p> + +<p>1. Any computer program that is considered a full application. +2. Any computer program that is made up of or otherwise contains +<b><a href="#proglet">proglet</a></b>s. 3. Any computer program +that is large enough to be normally distributed as an RPM or +<b><a href="#tarball">tarball</a></b>.</p> + +<hr> +Node:<a name="proglet">proglet</a>, Next:<a rel="next" href="#program">program</a>, Previous:<a rel="previous" href="#proggy">proggy</a>, Up:<a rel="up" href="#chap16">= P +=</a> <br> + + +<p><b>proglet</b> /prog'let/ n.</p> + +<p>[UK] A short <i>extempore</i> program written to meet an +immediate, transient need. Often written in BASIC, rarely more +than a dozen lines long, and containing no subroutines. The +largest amount of code that can be written off the top of one's +head, that does not need any editing, and that runs correctly the +first time (this amount varies significantly according to one's +skill and the language one is using). Compare <b><a href="#toyprogram">toy program</a></b>, <b><a href="#noddy">noddy</a></b>, <b><a href="#onelinerwars">one-liner +wars</a></b>.</p> + +<hr> +Node:<a name="program">program</a>, Next:<a rel="next" href="#ProgrammersCheer">Programmer's Cheer</a>, Previous:<a rel="previous" href="#proglet">proglet</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>program</b> n.</p> + +<p>1. A magic spell cast over a computer allowing it to turn +one's input into error messages. 2. An exercise in experimental +epistemology. 3. A form of art, ostensibly intended for the +instruction of computers, which is nevertheless almost inevitably +a failure if other programmers can't understand it.</p> + +<hr> +Node:<a name="ProgrammersCheer">Programmer's Cheer</a>, +Next:<a rel="next" href="#programming">programming</a>, +Previous:<a rel="previous" href="#program">program</a>, Up:<a +rel="up" href="#chap16">= P =</a> <br> + + +<p><b>Programmer's Cheer</b></p> + +<p>"Shift to the left! Shift to the right! Pop up, push down! +Byte! Byte! Byte!" A joke so old it has hair on it.</p> + +<hr> +Node:<a name="programming">programming</a>, Next:<a rel="next" +href="#programmingfluid">programming fluid</a>, Previous:<a +rel="previous" href="#ProgrammersCheer">Programmer's +Cheer</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>programming</b> n.</p> + +<p>1. The art of debugging a blank sheet of paper (or, in these +days of on-line editing, the art of debugging an empty file). +"Bloody instructions which, being taught, return to plague their +inventor" ("Macbeth", Act 1, Scene 7) 2. A pastime similar to +banging one's head against a wall, but with fewer opportunities +for reward. 3. The most fun you can have with your clothes on. 4. +The least fun you can have with your clothes off.</p> + +<hr> +Node:<a name="programmingfluid">programming fluid</a>, Next:<a +rel="next" href="#propellerhead">propeller head</a>, +Previous:<a rel="previous" href="#programming">programming</a>, +Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>programming fluid</b> n.</p> + +<p>1. Coffee. 2. Cola. 3. Any caffeinacious stimulant. Many +hackers consider these essential for those all-night hacking +runs. See <b><a href="#wirewater">wirewater</a></b>.</p> + +<hr> +Node:<a name="propellerhead">propeller head</a>, Next:<a rel="next" href="#propellerkey">propeller key</a>, Previous:<a +rel="previous" href="#programmingfluid">programming fluid</a>, +Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>propeller head</b> n.</p> + +<p>Used by hackers, this is syn. with <b><a href="#computergeek">computer geek</a></b>. Non-hackers sometimes +use it to describe all techies. Prob. derives from SF fandom's +tradition (originally invented by old-time fan Ray Faraday +Nelson) of propeller beanies as fannish insignia (though nobody +actually wears them except as a joke).</p> + +<hr> +Node:<a name="propellerkey">propeller key</a>, Next:<a rel="next" href="#proprietary">proprietary</a>, Previous:<a rel="previous" href="#propellerhead">propeller head</a>, Up:<a +rel="up" href="#chap16">= P =</a> <br> + + +<p><b>propeller key</b> n.</p> + +<p>[Mac users] See <b><a href="#featurekey">feature +key</a></b>.</p> + +<hr> +Node:<a name="proprietary">proprietary</a>, Next:<a rel="next" +href="#protocol">protocol</a>, Previous:<a rel="previous" href="#propellerkey">propeller key</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>proprietary</b> adj.</p> + +<p>1. In <b><a href="#marketroid">marketroid</a></b>-speak, +superior; implies a product imbued with exclusive magic by the +unmatched brilliance of the company's own hardware or software +designers. 2. In the language of hackers and users, inferior; +implies a product not conforming to open-systems standards, and +thus one that puts the customer at the mercy of a vendor able to +gouge freely on service and upgrade charges after the initial +sale has locked the customer in. Often in the phrase "proprietary +crap". 3. Synonym for closed-source, e.g. software issued in +binary without source and under a restructive license.</p> + +<p>Since the coining of the term <b><a href="#opensource">open +source</a></b>, many hackers have made a conscious effort to +distinguish between `proprietary' and `commercial' software. It +is possible for software to be commercial (that is, intended to +make a profit for the producers) without being proprietary. The +reverse is also possible, for example in binary-only +freeware.</p> + +<hr> +Node:<a name="protocol">protocol</a>, Next:<a rel="next" href="#provocativemaintenance">provocative maintenance</a>, +Previous:<a rel="previous" href="#proprietary">proprietary</a>, +Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>protocol</b> n.</p> + +<p>As used by hackers, this never refers to niceties about the +proper form for addressing letters to the Papal Nuncio or the +order in which one should use the forks in a Russian-style place +setting; hackers don't care about such things. It is used instead +to describe any set of rules that allow different machines or +pieces of software to coordinate with each other without +ambiguity. So, for example, it does include niceties about the +proper form for addressing packets on a network or the order in +which one should use the forks in the Dining Philosophers +Problem. It implies that there is some common message format and +an accepted set of primitives or commands that all parties +involved understand, and that transactions among them follow +predictable logical sequences. See also <b><a href="#handshaking">handshaking</a></b>, <b><a href="#doprotocol">do protocol</a></b>.</p> + +<hr> +Node:<a name="provocativemaintenance">provocative +maintenance</a>, Next:<a rel="next" href="#prowler">prowler</a>, +Previous:<a rel="previous" href="#protocol">protocol</a>, Up:<a +rel="up" href="#chap16">= P =</a> <br> + + +<p><b>provocative maintenance</b> n.</p> + +<p>[common ironic mutation of `preventive maintenance'] Actions +performed upon a machine at regularly scheduled intervals to +ensure that the system remains in a usable state. So called +because it is all too often performed by a <b><a href="#fieldservoid">field servoid</a></b> who doesn't know what he +is doing; such `maintenance' often <i>induces</i> problems, or +otherwise results in the machine's remaining in an +<i>un</i>usable state for an indeterminate amount of time. See +also <b><a href="#scratchmonkey">scratch monkey</a></b>.</p> + +<hr> +Node:<a name="prowler">prowler</a>, Next:<a rel="next" href="#pseudo">pseudo</a>, Previous:<a rel="previous" href="#provocativemaintenance">provocative maintenance</a>, Up:<a +rel="up" href="#chap16">= P =</a> <br> + + +<p><b>prowler</b> n.</p> + +<p>[Unix] A <b><a href="#daemon">daemon</a></b> that is run +periodically (typically once a week) to seek out and erase <b><a +href="#core">core</a></b> files, truncate administrative +logfiles, nuke <code>lost+found</code> directories, and otherwise +clean up the <b><a href="#cruft">cruft</a></b> that tends to pile +up in the corners of a file system. See also <b><a href="#GFR">GFR</a></b>, <b><a href="#reaper">reaper</a></b>, <b><a +href="#skulker">skulker</a></b>.</p> + +<hr> +Node:<a name="pseudo">pseudo</a>, Next:<a rel="next" href="#pseudoprime">pseudoprime</a>, Previous:<a rel="previous" href="#prowler">prowler</a>, Up:<a rel="up" href="#chap16">= P +=</a> <br> + + +<p><b>pseudo</b> /soo'doh/ n.</p> + +<p>[Usenet: truncation of `pseudonym'] 1. An electronic-mail or +<b><a href="#Usenet">Usenet</a></b> persona adopted by a human +for amusement value or as a means of avoiding negative +repercussions of one's net.behavior; a `nom de Usenet', often +associated with forged postings designed to conceal message +origins. Perhaps the best-known and funniest hoax of this type is +<b><a href="#B1FF">B1FF</a></b>. See also <b><a href="#tentacle">tentacle</a></b>. 2. Notionally, a <b><a href="#flamage">flamage</a></b>-generating AI program simulating a +Usenet user. Many flamers have been accused of actually being +such entities, despite the fact that no AI program of the +required sophistication yet exists. However, in 1989 there was a +famous series of forged postings that used a +phrase-frequency-based travesty generator to simulate the styles +of several well-known flamers; it was based on large samples of +their back postings (compare <b><a href="#DissociatedPress">Dissociated Press</a></b>). A significant +number of people were fooled by the forgeries, and the debate +over their authenticity was settled only when the perpetrator +came forward to publicly admit the hoax.</p> + +<hr> +Node:<a name="pseudoprime">pseudoprime</a>, Next:<a rel="next" +href="#pseudosuit">pseudosuit</a>, Previous:<a rel="previous" +href="#pseudo">pseudo</a>, Up:<a rel="up" href="#chap16">= +P =</a> <br> + + +<p><b>pseudoprime</b> n.</p> + +<p>A backgammon prime (six consecutive occupied points) with one +point missing. This term is an esoteric pun derived from number +theory: a number that passes a certain kind of "primality test" +may be called a `pseudoprime' (all primes pass any such test, but +so do some composite numbers), and any number that passes several +is, in some sense, almost certainly prime. The hacker backgammon +usage stems from the idea that a pseudoprime is almost as good as +a prime: it will do the same job unless you are unlucky.</p> + +<hr> +Node:<a name="pseudosuit">pseudosuit</a>, Next:<a rel="next" +href="#psychedelicware">psychedelicware</a>, Previous:<a rel="previous" href="#pseudoprime">pseudoprime</a>, Up:<a rel="up" +href="#chap16">= P =</a> <br> + + +<p><b>pseudosuit</b> /soo'doh-s[y]oot`/ n.</p> + +<p>A <b><a href="#suit">suit</a></b> wannabee; a hacker who has +decided that he wants to be in management or administration and +begins wearing ties, sport coats, and (shudder!) suits +voluntarily. It's his funeral. See also <b><a href="#lobotomy">lobotomy</a></b>.</p> + +<hr> +Node:<a name="psychedelicware">psychedelicware</a>, Next:<a rel="next" href="#psyton">psyton</a>, Previous:<a rel="previous" +href="#pseudosuit">pseudosuit</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>psychedelicware</b> /si:`k*-del'-ik-weir/ n.</p> + +<p>[UK] Syn. <b><a href="#displayhack">display hack</a></b>. +See also <b><a href="#smokingclover">smoking +clover</a></b>.</p> + +<hr> +Node:<a name="psyton">psyton</a>, Next:<a rel="next" href="#pubicdirectory">pubic directory</a>, Previous:<a rel="previous" href="#psychedelicware">psychedelicware</a>, Up:<a +rel="up" href="#chap16">= P =</a> <br> + + +<p><b>psyton</b> /si:'ton/ n.</p> + +<p>[TMRC] The elementary particle carrying the sinister force. +The probability of a process losing is proportional to the number +of psytons falling on it. Psytons are generated by observers, +which is why demos are more likely to fail when lots of people +are watching. [This term appears to have been largely superseded +by <b><a href="#bogon">bogon</a></b>; see also <b><a href="#quantumbogodynamics">quantum bogodynamics</a></b>. +--ESR]</p> + +<hr> +Node:<a name="pubicdirectory">pubic directory</a>, Next:<a +rel="next" href="#puff">puff</a>, Previous:<a rel="previous" +href="#psyton">psyton</a>, Up:<a rel="up" href="#chap16">= +P =</a> <br> + + +<p><b>pubic directory</b> /pyoob'ik d*-rek't*-ree/) n.</p> + +<p>[NYU] (also `pube directory' /pyoob' d*-rek't*-ree/) The `pub' +(public) directory on a machine that allows <b><a href="#FTP">FTP</a></b> access. So called because it is the default +location for <b><a href="#SEX">SEX</a></b> (sense 1). "I'll have +the source in the pube directory by Friday."</p> + +<hr> +Node:<a name="puff">puff</a>, Next:<a rel="next" href="#pumpkinholder">pumpkin holder</a>, Previous:<a rel="previous" href="#pubicdirectory">pubic directory</a>, Up:<a +rel="up" href="#chap16">= P =</a> <br> + + +<p><b>puff</b> vt.</p> + +<p>To decompress data that has been crunched by Huffman coding. +At least one widely distributed Huffman decoder program was +actually <i>named</i> `PUFF', but these days it is usually +packaged with the encoder. Oppose <b><a href="#huff">huff</a></b>, see <b><a href="#inflate">inflate</a></b>.</p> + +<hr> +Node:<a name="pumpkinholder">pumpkin holder</a>, Next:<a rel="next" href="#pumpking">pumpking</a>, Previous:<a rel="previous" +href="#puff">puff</a>, Up:<a rel="up" href="#chap16">= P +=</a> <br> + + +<p><b>pumpkin holder</b> n.</p> + +<p>See <b><a href="#patchpumpkin">patch pumpkin</a></b>.</p> + +<hr> +Node:<a name="pumpking">pumpking</a>, Next:<a rel="next" href="#punchedcard">punched card</a>, Previous:<a rel="previous" +href="#pumpkinholder">pumpkin holder</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>pumpking</b> n.</p> + +<p>Syn. for <b><a href="#pumpkinholder">pumpkin +holder</a></b>; see <b><a href="#patchpumpkin">patch +pumpkin</a></b>.</p> + +<hr> +Node:<a name="punchedcard">punched card</a>, Next:<a rel="next" href="#punt">punt</a>, Previous:<a rel="previous" href="#pumpking">pumpking</a>, Up:<a rel="up" href="#chap16">= +P =</a> <br> + + +<p><b>punched card</b> n.obs.</p> + +<p>[techspeak] (alt. `punch card') The signature medium of +computing's <b><a href="#StoneAge">Stone Age</a></b>, now +obsolescent outside of some IBM shops. The punched card actually +predated computers considerably, originating in 1801 as a control +device for mechanical looms. The version patented by Hollerith +and used with mechanical tabulating machines in the 1890 U.S. +Census was a piece of cardboard about 90 mm by 215 mm. There is a +widespread myth that it was designed to fit in the currency trays +used for that era's larger dollar bills, but recent +investigations have falsified this.</p> + +<p>IBM (which originated as a tabulating-machine manufacturer) +married the punched card to computers, encoding binary +information as patterns of small rectangular holes; one character +per column, 80 columns per card. Other coding schemes, sizes of +card, and hole shapes were tried at various times.</p> + +<p>The 80-column width of most character terminals is a legacy of +the IBM punched card; so is the size of the quick-reference cards +distributed with many varieties of computers even today. See +<b><a href="#chad">chad</a></b>, <b><a href="#chadbox">chad +box</a></b>, <b><a href="#eighty-columnmind">eighty-column +mind</a></b>, <b><a href="#greencard">green card</a></b>, +<b><a href="#dustydeck">dusty deck</a></b>, <b><a href="#lacecard">lace card</a></b>, <b><a href="#cardwalloper">card walloper</a></b>.</p> + +<hr> +Node:<a name="punt">punt</a>, Next:<a rel="next" href="#PurpleBook">Purple Book</a>, Previous:<a rel="previous" +href="#punchedcard">punched card</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>punt</b> v.</p> + +<p>[from the punch line of an old joke referring to American +football: "Drop back 15 yards and punt!"] 1. To give up, +typically without any intention of retrying. "Let's punt the +movie tonight." "I was going to hack all night to get this +feature in, but I decided to punt" may mean that you've decided +not to stay up all night, and may also mean you're not ever even +going to put in the feature. 2. More specifically, to give up on +figuring out what the <b><a href="#RightThing">Right +Thing</a></b> is and resort to an inefficient hack. 3. A design +decision to defer solving a problem, typically because one cannot +define what is desirable sufficiently well to frame an +algorithmic solution. "No way to know what the right form to dump +the graph in is -- we'll punt that for now." 4. To hand a tricky +implementation problem off to some other section of the design. +"It's too hard to get the compiler to do that; let's punt to the +runtime system." 5. To knock someone off an Internet or chat +connection; a `punter' thus, is a person or program that does +this.</p> + +<hr> +Node:<a name="PurpleBook">Purple Book</a>, Next:<a rel="next" +href="#purplewire">purple wire</a>, Previous:<a rel="previous" +href="#punt">punt</a>, Up:<a rel="up" href="#chap16">= P +=</a> <br> + + +<p><b>Purple Book</b> n.</p> + +<p>1. The "System V Interface Definition". The covers of the +first editions were an amazingly nauseating shade of +off-lavender. 2. Syn. <b><a href="#WizardBook">Wizard +Book</a></b>. Donald Lewine's "POSIX Programmer's Guide" +(O'Reilly, 1991, ISBN 0-937175-73-0). See also <b><a href="#booktitles">book titles</a></b>.</p> + +<hr> +Node:<a name="purplewire">purple wire</a>, Next:<a rel="next" +href="#push">push</a>, Previous:<a rel="previous" href="#PurpleBook">Purple Book</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>purple wire</b> n.</p> + +<p>[IBM] Wire installed by Field Engineers to work around +problems discovered during testing or debugging. These are called +`purple wires' even when (as is frequently the case) their actual +physical color is yellow<small>...</small>. Compare <b><a href="#bluewire">blue wire</a></b>, <b><a href="#yellowwire">yellow wire</a></b>, and <b><a href="#redwire">red wire</a></b>.</p> + +<hr> +Node:<a name="push">push</a>, Next:<a rel="next" href="#Python">Python</a>, Previous:<a rel="previous" href="#purplewire">purple wire</a>, Up:<a rel="up" href="#chap16">= P =</a> <br> + + +<p><b>push</b></p> + +<p>[from the operation that puts the current information on a +stack, and the fact that procedure return addresses are saved on +a stack] (Also PUSH /push/ or PUSHJ /push'J/, the latter based on +the PDP-10 procedure call instruction.) 1. To put something onto +a <b><a href="#stack">stack</a></b> or <b><a href="#PDL">PDL</a></b>. If one says that something has been pushed +onto one's stack, it means that the Damoclean list of things +hanging over ones's head has grown longer and heavier yet. This +may also imply that one will deal with it <i>before</i> other +pending items; otherwise one might say that the thing was `added +to my queue'. 2. vi. To enter upon a digression, to save the +current discussion for later. Antonym of <b><a href="#pop">pop</a></b>; see also <b><a href="#stack">stack</a></b>, +<b><a href="#PDL">PDL</a></b>.</p> + +<hr> +Node:<a name="Python">Python</a>, Next:<a rel="next" href="#quad">quad</a>, Previous:<a rel="previous" href="#push">push</a>, Up:<a rel="up" href="#chap16">= P =</a> +<br> + + +<p><b>Python</b> /pi:'thon/</p> + +<p> +In the words of its author, "the other scripting language" (other than <b><a +href="#Perl">Perl</a></b>, that is). Python's design is notably clean, elegant, +and well thought through; it tends to attract the sort of programmers who find +Perl grubby and exiguous. Python's relationship with Perl is rather like the +<b><a href="#BSD">BSD</a></b> community's relationship to <b><a +href="#Linux">Linux</a></b> - it's the smaller party in a (usually friendly) +rivalry, but the average quality of its developers is generally conceded to be +rather higher than in the larger community it competes with. There's a Python +resource page at http://www.python.org. See also <b><a +href="#Guido">Guido</a></b>. +</p> + +<hr> +Node:<a name="chap17">= Q =</a>, Next:<a rel="next" href="#chap18">= R =</a>, Previous:<a rel="previous" href="#chap16">= P =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= Q =</h2> + +<ul> +<li><a href="#quad">quad</a>:</li> + +<li><a href="#quadruplebucky">quadruple bucky</a>:</li> + +<li><a href="#quantifiers">quantifiers</a>:</li> + +<li><a href="#quantumbogodynamics">quantum +bogodynamics</a>:</li> + +<li><a href="#quarter">quarter</a>:</li> + +<li><a href="#ques">ques</a>:</li> + +<li><a href="#quick-and-dirty">quick-and-dirty</a>:</li> + +<li><a href="#quine">quine</a>:</li> + +<li><a href="#quotechapterandverse">quote chapter and +verse</a>:</li> + +<li><a href="#quotient">quotient</a>:</li> + +<li><a href="#quux">quux</a>:</li> + +<li><a href="#qux">qux</a>:</li> + +<li><a href="#QWERTY">QWERTY</a>:</li> +</ul> + +<hr> +Node:<a name="quad">quad</a>, Next:<a rel="next" href="#quadruplebucky">quadruple bucky</a>, Previous:<a rel="previous" href="#Python">Python</a>, Up:<a rel="up" href="#chap17">= Q =</a> <br> + + +<p><b>quad</b> n.</p> + +<p>1. Two bits; syn. for <b><a href="#quarter">quarter</a></b>, +<b><a href="#crumb">crumb</a></b>, <b><a href="#tayste">tayste</a></b>. 2. A four-pack of anything (compare +<b><a href="#hex">hex</a></b>, sense 2). 3. The rectangle or box +glyph used in the APL language for various arcane purposes mostly +related to I/O. Former Ivy-Leaguers and Oxford types are said to +associate it with nostalgic memories of dear old University.</p> + +<hr> +Node:<a name="quadruplebucky">quadruple bucky</a>, Next:<a +rel="next" href="#quantifiers">quantifiers</a>, Previous:<a rel="previous" href="#quad">quad</a>, Up:<a rel="up" href="#chap17">= Q =</a> <br> + + +<p><b>quadruple bucky</b> n. obs.</p> + +<p>1. On an MIT <b><a href="#space-cadetkeyboard">space-cadet +keyboard</a></b>, use of all four of the shifting keys (control, +meta, hyper, and super) while typing a character key. 2. On a +Stanford or MIT keyboard in <b><a href="#rawmode">raw +mode</a></b>, use of four shift keys while typing a fifth +character, where the four shift keys are the control and meta +keys on <i>both</i> sides of the keyboard. This was very +difficult to do! One accepted technique was to press the +left-control and left-meta keys with your left hand, the +right-control and right-meta keys with your right hand, and the +fifth key with your nose.</p> + +<p>Quadruple-bucky combinations were very seldom used in +practice, because when one invented a new command one usually +assigned it to some character that was easier to type. If you +want to imply that a program has ridiculously many commands or +features, you can say something like: "Oh, the command that makes +it spin the tapes while whistling Beethoven's Fifth Symphony is +quadruple-bucky-cokebottle." See <b><a href="#doublebucky">double bucky</a></b>, <b><a href="#buckybits">bucky bits</a></b>, <b><a href="#cokebottle">cokebottle</a></b>.</p> + +<hr> +Node:<a name="quantifiers">quantifiers</a>, Next:<a rel="next" +href="#quantumbogodynamics">quantum bogodynamics</a>, +Previous:<a rel="previous" href="#quadruplebucky">quadruple +bucky</a>, Up:<a rel="up" href="#chap17">= Q =</a> <br> + + +<p><b>quantifiers</b></p> + +<p>In techspeak and jargon, the standard metric prefixes used in +the SI (Système International) conventions for scientific +measurement have dual uses. With units of time or things that +come in powers of 10, such as money, they retain their usual +meanings of multiplication by powers of 1000 = 10^3. But when +used with bytes or other things that naturally come in powers of +2, they usually denote multiplication by powers of 1024 = +2^(10).</p> + +<p>Here are the SI magnifying prefixes, along with the +corresponding binary interpretations in common use:</p> + +<pre> +prefix decimal binary +kilo- 1000^1 1024^1 = 2^10 = 1,024<br> +mega- 1000^2 1024^2 = 2^20 = 1,048,576<br> +giga- 1000^3 1024^3 = 2^30 = 1,073,741,824<br> +tera- 1000^4 1024^4 = 2^40 = 1,099,511,627,776<br> +peta- 1000^5 1024^5 = 2^50 = 1,125,899,906,842,624<br> +exa- 1000^6 1024^6 = 2^60 = 1,152,921,504,606,846,976<br> +zetta- 1000^7 1024^7 = 2^70 = 1,180,591,620,717,411,303,424<br> +yotta- 1000^8 1024^8 = 2^80 = 1,208,925,819,614,629,174,706,176<br> +</pre> + +<p>Here are the SI fractional prefixes:</p> + +<pre> +<i>prefix decimal jargon usage</i> +milli- 1000^-1 (seldom used in jargon) +micro- 1000^-2 small or human-scale (see <b><a href="#micro-">micro-</a></b>) +nano- 1000^-3 even smaller (see <b><a href="#nano-">nano-</a></b>) +pico- 1000^-4 even smaller yet (see <b><a href="#pico-">pico-</a></b>) +femto- 1000^-5 (not used in jargon---yet) +atto- 1000^-6 (not used in jargon---yet) +zepto- 1000^-7 (not used in jargon---yet) +yocto- 1000^-8 (not used in jargon---yet) +</pre> + +<p>The prefixes zetta-, yotta-, zepto-, and yocto- have been +included in these tables purely for completeness and giggle +value; they were adopted in 1990 by the `19th Conference Generale +des Poids et Mesures'. The binary peta- and exa- loadings, though +well established, are not in jargon use either -- yet. The prefix +milli-, denoting multiplication by 1/1000, has always been rare +in jargon (there is, however, a standard joke about the +`millihelen' -- notionally, the amount of beauty required to +launch one ship). See the entries on <b><a href="#micro-">micro-</a></b>, <b><a href="#pico-">pico-</a></b>, and +<b><a href="#nano-">nano-</a></b> for more information on +connotative jargon use of these terms. `Femto' and `atto' (which, +interestingly, derive not from Greek but from Danish) have not +yet acquired jargon loadings, though it is easy to predict what +those will be once computing technology enters the required +realms of magnitude (however, see <b><a href="#attoparsec">attoparsec</a></b>).</p> + +<p>There are, of course, some standard unit prefixes for powers +of 10. In the following table, the `prefix' column is the +international standard suffix for the appropriate power of ten; +the `binary' column lists jargon abbreviations and words for the +corresponding power of 2. The B-suffixed forms are commonly used +for byte quantities; the words `meg' and `gig' are nouns that may +(but do not always) pluralize with `s'.</p> + +<pre> +<i>prefix decimal binary pronunciation</i> +kilo- k K, KB, /kay/ +mega- M M, MB, meg /meg/ +giga- G G, GB, gig /gig/,/jig/ +</pre> + +<p>Confusingly, hackers often use K or M as though they were +suffix or numeric multipliers rather than a prefix; thus "2K +dollars", "2M of disk space". This is also true (though less +commonly) of G.</p> + +<p>Note that the formal SI metric prefix for 1000 is `k'; some +use this strictly, reserving `K' for multiplication by 1024 (KB +is thus `kilobytes').</p> + +<p>K, M, and G used alone refer to quantities of bytes; thus, 64G +is 64 gigabytes and `a K' is a kilobyte (compare mainstream use +of `a G' as short for `a grand', that is, $1000). Whether one +pronounces `gig' with hard or soft `g' depends on what one thinks +the proper pronunciation of `giga-' is.</p> + +<p>Confusing 1000 and 1024 (or other powers of 2 and 10 close in +magnitude) -- for example, describing a memory in units of 500K +or 524K instead of 512K -- is a sure sign of the <b><a href="#marketroid">marketroid</a></b>. One example of this: it is +common to refer to the capacity of 3.5" <b><a href="#microfloppies">microfloppies</a></b> as `1.44 MB' In fact, this +is a completely <b><a href="#bogus">bogus</a></b> number. The +correct size is 1440 KB, that is, 1440 * 1024 = 1474560 bytes. So +the `mega' in `1.44 MB' is compounded of two `kilos', one of +which is 1024 and the other of which is 1000. The correct number +of megabytes would of course be 1440 / 1024 = 1.40625. Alas, this +fine point is probably lost on the world forever.</p> + +<p>[1993 update: hacker Morgan Burke has proposed, to general +approval on Usenet, the following additional prefixes:</p> + +<dl> +<dt>groucho</dt> + +<dd>10^(-30)</dd> + +<dt>harpo</dt> + +<dd>10^(-27)</dd> + +<dt>harpi</dt> + +<dd>10^(27)</dd> + +<dt>grouchi</dt> + +<dd>10^(30)</dd> +</dl> + +<p>We observe that this would leave the prefixes zeppo-, gummo-, +and chico- available for future expansion. Sadly, there is little +immediate prospect that Mr. Burke's eminently sensible proposal +will be ratified.]</p> + +<p>[1999 upate: there is an <a href="ftp://ftp.informatik.uni-erlangen.de/pub/doc/ISO/information-units"> +IEC proposal</a> for binary multipliers, but no evidence that any +of its proposals are in live use.]</p> + +<hr> +Node:<a name="quantumbogodynamics">quantum bogodynamics</a>, +Next:<a rel="next" href="#quarter">quarter</a>, Previous:<a rel="previous" href="#quantifiers">quantifiers</a>, Up:<a rel="up" +href="#chap17">= Q =</a> <br> + + +<p><b>quantum bogodynamics</b> /kwon'tm boh`goh-di:-nam'iks/ +n.</p> + +<p>A theory that characterizes the universe in terms of bogon +sources (such as politicians, used-car salesmen, TV evangelists, +and <b><a href="#suit">suit</a></b>s in general), bogon sinks +(such as taxpayers and computers), and bogosity potential fields. +Bogon absorption, of course, causes human beings to behave +mindlessly and machines to fail (and may also cause both to emit +secondary bogons); however, the precise mechanics of the +bogon-computron interaction are not yet understood and remain to +be elucidated. Quantum bogodynamics is most often invoked to +explain the sharp increase in hardware and software failures in +the presence of suits; the latter emit bogons, which the former +absorb. See <b><a href="#bogon">bogon</a></b>, <b><a href="#computron">computron</a></b>, <b><a href="#suit">suit</a></b>, +<b><a href="#psyton">psyton</a></b>.</p> + +<hr> +Node:<a name="quarter">quarter</a>, Next:<a rel="next" href="#ques">ques</a>, Previous:<a rel="previous" href="#quantumbogodynamics">quantum bogodynamics</a>, Up:<a rel="up" href="#chap17">= Q =</a> <br> + + +<p><b>quarter</b> n.</p> + +<p>Two bits. This in turn comes from the `pieces of eight' famed +in pirate movies -- Spanish silver crowns that could be broken +into eight pie-slice-shaped `bits' to make change. Early in +American history the Spanish coin was considered equal to a +dollar, so each of these `bits' was considered worth 12.5 cents. +Syn. <b><a href="#tayste">tayste</a></b>, <b><a href="#crumb">crumb</a></b>, <b><a href="#quad">quad</a></b>. Usage: +rare. General discussion of such terms is under <b><a href="#nybble">nybble</a></b>.</p> + +<hr> +Node:<a name="ques">ques</a>, Next:<a rel="next" href="#quick-and-dirty">quick-and-dirty</a>, Previous:<a rel="previous" href="#quarter">quarter</a>, Up:<a rel="up" href="#chap17">= Q =</a> <br> + + +<p><b>ques</b> /kwes/</p> + +<p>1. n. The question mark character (<code>?</code>, ASCII +0111111). 2. interj. What? Also frequently verb-doubled as "Ques +ques?" See <b><a href="#wall">wall</a></b>.</p> + +<hr> +Node:<a name="quick-and-dirty">quick-and-dirty</a>, Next:<a rel="next" href="#quine">quine</a>, Previous:<a rel="previous" href="#ques">ques</a>, Up:<a rel="up" href="#chap17">= Q =</a> +<br> + + +<p><b>quick-and-dirty</b> adj.</p> + +<p>[common] Describes a <b><a href="#crock">crock</a></b> put +together under time or user pressure. Used esp. when you want to +convey that you think the fast way might lead to trouble further +down the road. "I can have a quick-and-dirty fix in place +tonight, but I'll have to rewrite the whole module to solve the +underlying design problem." See also <b><a href="#kluge">kluge</a></b>.</p> + +<hr> +Node:<a name="quine">quine</a>, Next:<a rel="next" href="#quotechapterandverse">quote chapter and verse</a>, +Previous:<a rel="previous" href="#quick-and-dirty">quick-and-dirty</a>, Up:<a rel="up" href="#chap17">= Q =</a> <br> + + +<p><b>quine</b> /kwi:n/ n.</p> + +<p>[from the name of the logician Willard van Orman Quine, via +Douglas Hofstadter] A program that generates a copy of its own +source text as its complete output. Devising the shortest +possible quine in some given programming language is a common +hackish amusement. (We ignore some variants of BASIC in which a +program consisting of a single empty string literal reproduces +itself trivially.) Here is one classic quine:</p> + +<pre> +((lambda (x) + (list x (list (quote quote) x))) + (quote + (lambda (x) + (list x (list (quote quote) x))))) +</pre> + +<p>This one works in LISP or Scheme. It's relatively easy to +write quines in other languages such as Postscript which readily +handle programs as data; much harder (and thus more challenging!) +in languages like C which do not. Here is a classic C quine for +ASCII machines:</p> + +<pre> +char*f="char*f=%c%s%c;main() +{printf(f,34,f,34,10);}%c"; +main(){printf(f,34,f,34,10);} +</pre> + +<p>For excruciatingly exact quinishness, remove the interior line +breaks. Here is another elegant quine in ANSI C:</p> + +<pre> +#define q(k)main(){return!puts(#k"\nq("#k")");} +q(#define q(k)main(){return!puts(#k"\nq("#k")");}) +</pre> + +<p>Some infamous <b><a href="#ObfuscatedCContest">Obfuscated C Contest</a></b> entries +have been quines that reproduced in exotic ways. There is an +amusing Quine +Home Page.</p> + +<hr> +Node:<a name="quotechapterandverse">quote chapter and +verse</a>, Next:<a rel="next" href="#quotient">quotient</a>, +Previous:<a rel="previous" href="#quine">quine</a>, Up:<a rel="up" href="#chap17">= Q =</a> <br> + + +<p><b>quote chapter and verse</b> v.</p> + +<p>[by analogy with the mainstream phrase] To cite a relevant +excerpt from an appropriate <b><a href="#bible">bible</a></b>. "I +don't care if <code>rn</code> gets it wrong; `Followup-To: +poster' is explicitly permitted by <b><a href="#RFC">RFC</a></b>-1036. I'll quote chapter and verse if you +don't believe me." See also <b><a href="#legalese">legalese</a></b>, <b><a href="#languagelawyer">language lawyer</a></b>, <b><a href="#RTFS">RTFS</a></b> (sense 2).</p> + +<hr> +Node:<a name="quotient">quotient</a>, Next:<a rel="next" href="#quux">quux</a>, Previous:<a rel="previous" href="#quotechapterandverse">quote chapter and verse</a>, +Up:<a rel="up" href="#chap17">= Q =</a> <br> + + +<p><b>quotient</b> n.</p> + +<p>See <b><a href="#coefficientofX">coefficient of +X</a></b>.</p> + +<hr> +Node:<a name="quux">quux</a>, Next:<a rel="next" href="#qux">qux</a>, Previous:<a rel="previous" href="#quotient">quotient</a>, Up:<a rel="up" href="#chap17">= +Q =</a> <br> + + +<p><b>quux</b> /kwuhks/ n.</p> + +<p>[Mythically, from the Latin semi-deponent verb quuxo, quuxare, +quuxandum iri; noun form variously `quux' (plural `quuces', +anglicized to `quuxes') and `quuxu' (genitive plural is +`quuxuum', for four u-letters out of seven in all, using up all +the `u' letters in Scrabble).] 1. Originally, a <b><a href="#metasyntacticvariable">metasyntactic variable</a></b> like +<b><a href="#foo">foo</a></b> and <b><a href="#foobar">foobar</a></b>. Invented by Guy Steele for precisely +this purpose when he was young and naive and not yet interacting +with the real computing community. Many people invent such words; +this one seems simply to have been lucky enough to have spread a +little. In an eloquent display of poetic justice, it has returned +to the originator in the form of a nickname. 2. interj. See <b><a +href="#foo">foo</a></b>; however, denotes very little disgust, +and is uttered mostly for the sake of the sound of it. 3. Guy +Steele in his persona as `The Great Quux', which is somewhat +infamous for light verse and for the `Crunchly' cartoons. 4. In +some circles, used as a punning opposite of `crux'. "Ah, that's +the quux of the matter!" implies that the point is <i>not</i> +crucial (compare <b><a href="#tipoftheicecube">tip of +the ice-cube</a></b>). 5. quuxy: adj. Of or pertaining to a +quux.</p> + +<hr> +Node:<a name="qux">qux</a>, Next:<a rel="next" href="#QWERTY">QWERTY</a>, Previous:<a rel="previous" href="#quux">quux</a>, Up:<a rel="up" href="#chap17">= Q =</a> +<br> + + +<p><b>qux</b> /kwuhks/</p> + +<p>The fourth of the standard <b><a href="#metasyntacticvariable">metasyntactic variable</a></b>, after +<b><a href="#baz">baz</a></b> and before the +quu(u<small>...</small>)x series. See <b><a href="#foo">foo</a></b>, <b><a href="#bar">bar</a></b>, <b><a href="#baz">baz</a></b>, <b><a href="#quux">quux</a></b>. This appears +to be a recent mutation from <b><a href="#quux">quux</a></b>, and +many versions (especially older versions) of the standard series +just run <b><a href="#foo">foo</a></b>, <b><a href="#bar">bar</a></b>, <b><a href="#baz">baz</a></b>, <b><a href="#quux">quux</a></b>, <small>...</small>.</p> + +<hr> +Node:<a name="QWERTY">QWERTY</a>, Next:<a rel="next" href="#rabbitjob">rabbit job</a>, Previous:<a rel="previous" href="#qux">qux</a>, Up:<a rel="up" href="#chap17">= Q =</a> +<br> + + +<p><b>QWERTY</b> /kwer'tee/ adj.</p> + +<p>[from the keycaps at the upper left] Pertaining to a standard +English-language typewriter keyboard (sometimes called the Sholes +keyboard after its inventor), as opposed to Dvorak or +non-US-ASCII layouts or a <b><a href="#space-cadetkeyboard">space-cadet keyboard</a></b> or APL +keyboard.</p> + +<p>Historical note: The QWERTY layout is a fine example of a +<b><a href="#fossil">fossil</a></b>. It is sometimes said that it +was designed to slow down the typist, but this is wrong; it was +designed to allow <i>faster</i> typing -- under a constraint +now long obsolete. In early typewriters, fast typing using nearby +type-bars jammed the mechanism. So Sholes fiddled the layout to +separate the letters of many common digraphs (he did a far from +perfect job, though; `th', `tr', `ed', and `er', for example, +each use two nearby keys). Also, putting the letters of +`typewriter' on one line allowed it to be typed with particular +speed and accuracy for <b><a href="#demo">demo</a></b>s. The +jamming problem was essentially solved soon afterward by a +suitable use of springs, but the keyboard layout lives on.</p> + +<p>The QWERTY keyboard has also spawned some unhelpful economic +myths about how technical standards get and stay established; see +http://www.reasonmag.com/9606/Fe.QWERTY.html.</p> + +<hr> +Node:<a name="chap18">= R =</a>, Next:<a rel="next" href="#chap19">= S =</a>, Previous:<a rel="previous" href="#chap17">= Q =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= R =</h2> + +<ul> +<li><a href="#rabbitjob">rabbit job</a>:</li> + +<li><a href="#raindance">rain dance</a>:</li> + +<li><a href="#rainbowseries">rainbow series</a>:</li> + +<li><a href="#random">random</a>:</li> + +<li><a href="#RandomNumberGod">Random Number God</a>:</li> + +<li><a href="#randomnumbers">random numbers</a>:</li> + +<li><a href="#randomness">randomness</a>:</li> + +<li><a href="#rape">rape</a>:</li> + +<li><a href="#raremode">rare mode</a>:</li> + +<li><a href="#rasterblaster">raster blaster</a>:</li> + +<li><a href="#rasterburn">raster burn</a>:</li> + +<li><a href="#rasterbation">rasterbation</a>:</li> + +<li><a href="#ratbelt">rat belt</a>:</li> + +<li><a href="#ratdance">rat dance</a>:</li> + +<li><a href="#ratiosite">ratio site</a>:</li> + +<li><a href="#rave">rave</a>:</li> + +<li><a href="#raveon">rave on!</a>:</li> + +<li><a href="#ravs">ravs</a>:</li> + +<li><a href="#rawmode">raw mode</a>:</li> + +<li><a href="#RBL">RBL</a>:</li> + +<li><a href="#rcfile">rc file</a>:</li> + +<li><a href="#RE">RE</a>:</li> + +<li><a href="#readonlyuser">read-only user</a>:</li> + +<li><a href="#READMEfile">README file</a>:</li> + +<li><a href="#real">real</a>:</li> + +<li><a href="#realestate">real estate</a>:</li> + +<li><a href="#realhack">real hack</a>:</li> + +<li><a href="#realoperatingsystem">real operating system</a>:</li> + +<li><a href="#RealProgrammer">Real Programmer</a>:</li> + +<li><a href="#RealSoonNow">Real Soon Now</a>:</li> + +<li><a href="#realTime">real time</a>:</li> + +<li><a href="#realuser">real user</a>:</li> + +<li><a href="#RealWorld">Real World</a>:</li> + +<li><a href="#realitycheck">reality check</a>:</li> + +<li><a href="#realitydistortionfield">reality-distortion field</a>:</li> + +<li><a href="#reaper">reaper</a>:</li> + +<li><a href="#recompiletheworld">recompile the world</a>:</li> + +<li><a href="#rectangleslinger">rectangle slinger</a>:</li> + +<li><a href="#recursion">recursion</a>:</li> + +<li><a href="#recursiveacronym">recursive acronym</a>:</li> + +<li><a href="#RedBook">Red Book</a>:</li> + +<li><a href="#redwire">red wire</a>:</li> + +<li><a href="#regexp">regexp</a>:</li> + +<li><a href="#registerdancing">register dancing</a>:</li> + +<li><a href="#rehi">rehi</a>:</li> + +<li><a href="#reincarnationcycleof">reincarnation cycle of</a>:</li> + +<li><a href="#reinventthewheel">reinvent the wheel</a>:</li> + +<li><a href="#relayrape">relay rape</a>:</li> + +<li><a href="#religionofCHI">religion of CHI</a>:</li> + +<li><a href="#religiousissues">religious issues</a>:</li> + +<li><a href="#replicator">replicator</a>:</li> + +<li><a href="#reply">reply</a>:</li> + +<li><a href="#restriction">restriction</a>:</li> + +<li><a href="#retcon">retcon</a>:</li> + +<li><a href="#RETI">RETI</a>:</li> + +<li><a href="#retrocomputing">retrocomputing</a>:</li> + +<li><a href="#returnfromthedead">return from the dead</a>:</li> + +<li><a href="#RFC">RFC</a>:</li> + +<li><a href="#RFE">RFE</a>:</li> + +<li><a href="#ribsite">rib site</a>:</li> + +<li><a href="#ricebox">rice box</a>:</li> + +<li><a href="#RightThing">Right Thing</a>:</li> + +<li><a href="#rip">rip</a>:</li> + +<li><a href="#ripoff">ripoff</a>:</li> + +<li><a href="#RL">RL</a>:</li> + +<li><a href="#roach">roach</a>:</li> + +<li><a href="#robocanceller">robocanceller</a>:</li> + +<li><a href="#robot">robot</a>:</li> + +<li><a href="#robust">robust</a>:</li> + +<li><a href="#rococo">rococo</a>:</li> + +<li><a href="#rogue">rogue</a>:</li> + +<li><a href="#roomtemperatureIQ">room-temperature IQ</a>:</li> + +<li><a href="#root">root</a>:</li> + +<li><a href="#rootmode">root mode</a>:</li> + +<li><a href="#rot13">rot13</a>:</li> + +<li><a href="#rotarydebugger">rotary debugger</a>:</li> + +<li><a href="#roundtape">round tape</a>:</li> + +<li><a href="#RSN">RSN</a>:</li> + +<li><a href="#RTBM">RTBM</a>:</li> + +<li><a href="#RTFAQ">RTFAQ</a>:</li> + +<li><a href="#RTFB">RTFB</a>:</li> + +<li><a href="#RTFM">RTFM</a>:</li> + +<li><a href="#RTFS">RTFS</a>:</li> + +<li><a href="#RTI">RTI</a>:</li> + +<li><a href="#RTM">RTM</a>:</li> + +<li><a href="#RTS">RTS</a>:</li> + +<li><a href="#rude">rude</a>:</li> + +<li><a href="#runes">runes</a>:</li> + +<li><a href="#runic">runic</a>:</li> + +<li><a href="#rustyiron">rusty iron</a>:</li> + +<li><a href="#rustymemory">rusty memory</a>:</li> + +<li><a href="#rustywire">rusty wire</a>:</li> +</ul> + +<hr> +Node:<a name="rabbitjob">rabbit job</a>, Next:<a rel="next" +href="#raindance">rain dance</a>, Previous:<a rel="previous" +href="#QWERTY">QWERTY</a>, Up:<a rel="up" href="#chap18">= +R =</a> <br> + + +<p><b>rabbit job</b> n.</p> + +<p>[Cambridge] A batch job that does little, if any, real work, +but creates one or more copies of itself, breeding like rabbits. +Compare <b><a href="#wabbit">wabbit</a></b>, <b><a href="#forkbomb">fork bomb</a></b>.</p> + +<hr> +Node:<a name="raindance">rain dance</a>, Next:<a rel="next" +href="#rainbowseries">rainbow series</a>, Previous:<a rel="previous" href="#rabbitjob">rabbit job</a>, Up:<a rel="up" +href="#chap18">= R =</a> <br> + + +<p><b>rain dance</b> n.</p> + +<p>1. Any ceremonial action taken to correct a hardware problem, +with the expectation that nothing will be accomplished. This +especially applies to reseating printed circuit boards, +reconnecting cables, etc. "I can't boot up the machine. We'll +have to wait for Greg to do his rain dance." 2. Any arcane +sequence of actions performed with computers or software in order +to achieve some goal; the term is usually restricted to rituals +that include both an <b><a href="#incantation">incantation</a></b> or two and physical activity +or motion. Compare <b><a href="#magic">magic</a></b>, <b><a href="#voodooprogramming">voodoo programming</a></b>, <b><a href="#blackart">black art</a></b>, <b><a href="#cargocultprogramming">cargo cult programming</a></b>, +<b><a href="#waveadeadchicken">wave a dead +chicken</a></b>; see also <b><a href="#castingtherunes">casting the runes</a></b>.</p> + +<hr> +Node:<a name="rainbowseries">rainbow series</a>, Next:<a rel="next" href="#random">random</a>, Previous:<a rel="previous" +href="#raindance">rain dance</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>rainbow series</b> n.</p> + +<p>Any of several series of technical manuals distinguished by +cover color. The original rainbow series was the NCSC security +manuals (see <b><a href="#OrangeBook">Orange Book</a></b>, +<b><a href="#crayolabooks">crayola books</a></b>); the term +has also been commonly applied to the PostScript reference set +(see <b><a href="#RedBook">Red Book</a></b>, <b><a href="#GreenBook">Green Book</a></b>, <b><a href="#BlueBook">Blue Book</a></b>, <b><a href="#WhiteBook">White Book</a></b>). Which books are meant by +"`the' rainbow series" unqualified is thus dependent on one's +local technical culture.</p> + +<hr> +Node:<a name="random">random</a>, Next:<a rel="next" href="#RandomNumberGod">Random Number God</a>, Previous:<a rel="previous" href="#rainbowseries">rainbow series</a>, Up:<a +rel="up" href="#chap18">= R =</a> <br> + + +<p><b>random</b> adj.</p> + +<p>1. Unpredictable (closest to mathematical definition); weird. +"The system's been behaving pretty randomly." 2. Assorted; +undistinguished. "Who was at the conference?" "Just a bunch of +random business types." 3. (pejorative) Frivolous; unproductive; +undirected. "He's just a random loser." 4. Incoherent or +inelegant; poorly chosen; not well organized. "The program has a +random set of misfeatures." "That's a random name for that +function." "Well, all the names were chosen pretty randomly." 5. +In no particular order, though deterministic. "The I/O channels +are in a pool, and when a file is opened one is chosen randomly." +6. Arbitrary. "It generates a random name for the scratch file." +7. Gratuitously wrong, i.e., poorly done and for no good apparent +reason. For example, a program that handles file name defaulting +in a particularly useless way, or an assembler routine that could +easily have been coded using only three registers, but +redundantly uses seven for values with non-overlapping lifetimes, +so that no one else can invoke it without first saving four extra +registers. What <b><a href="#randomness">randomness</a></b>! 8. +n. A random hacker; used particularly of high-school students who +soak up computer time and generally get in the way. 9. n. Anyone +who is not a hacker (or, sometimes, anyone not known to the +hacker speaking); the noun form of sense 2. "I went to the talk, +but the audience was full of randoms asking bogus questions". 10. +n. (occasional MIT usage) One who lives at Random Hall. See also +<b><a href="#Jrandom">J. Random</a></b>, <b><a href="#somerandomX">some random X</a></b>. 11. [UK] +Conversationally, a non sequitur or something similarly +out-of-the-blue. As in: "Stop being so random!" This sense +equates to `hatstand', taken from the Viz comic character "Roger +Irrelevant - He's completely Hatstand."</p> + +<hr> +Node:<a name="RandomNumberGod">Random Number God</a>, +Next:<a rel="next" href="#randomnumbers">random numbers</a>, +Previous:<a rel="previous" href="#random">random</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>Random Number God</b></p> + +<p>[rec.games.roguelike.angband; often abbreviated `RNG'] The +malign force which lurks behind the random number generator in +<b><a href="#Angband">Angband</a></b> (and by extension +elsewhere). A dark god that demands sacrifices and toys with its +victims. "I just found a really great item; I suppose the RNG is +about to punish me..." Apparently, Angband's random number +generator occasionally gets locked in a repetition, so you get +something with a 3% chance happening 8 times in a row. +Improbable, but far too common to be pure chance. Compare <b><a +href="#Shub-Internet">Shub-Internet</a></b>.</p> + +<hr> +Node:<a name="randomnumbers">random numbers</a>, Next:<a rel="next" href="#randomness">randomness</a>, Previous:<a rel="previous" href="#RandomNumberGod">Random Number God</a>, +Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>random numbers</b> n.</p> + +<p>When one wishes to specify a large but random number of +things, and the context is inappropriate for <b><a href="#N">N</a></b>, certain numbers are preferred by hacker tradition +(that is, easily recognized as placeholders). These include the +following:</p> + +<blockquote> +<dl> +<dt>17</dt> + +<dd>Long described at MIT as `the least random number'; see +23.<br> +</dd> + +<dt>23</dt> + +<dd>Sacred number of Eris, Goddess of Discord (along with 17 and +5).<br> +</dd> + +<dt>42</dt> + +<dd>The Answer to the Ultimate Question of Life, the Universe, +and Everything. (Note that this answer is completely fortuitous. +<code>:-)</code>)<br> +</dd> + +<dt>69</dt> + +<dd>From the sexual act. This one was favored in MIT's ITS +culture.<br> +</dd> + +<dt>105</dt> + +<dd>69 hex = 105 decimal, and 69 decimal = 105 octal.<br> +</dd> + +<dt>666</dt> + +<dd>The Number of the Beast.</dd> +</dl> +</blockquote> + +<p>For further enlightenment, study the "Principia Discordia", +"<b><a href="#TheHitchhikersGuidetotheGalaxy">The +Hitchhiker's Guide to the Galaxy</a></b>", "The Joy of Sex", and +the Christian Bible (Revelation 13:18). See also <b><a href="#Discordianism">Discordianism</a></b> or consult your pineal +gland. See also <b><a href="#forvaluesof">for values +of</a></b>.</p> + +<hr> +Node:<a name="randomness">randomness</a>, Next:<a rel="next" +href="#rape">rape</a>, Previous:<a rel="previous" href="#randomnumbers">random numbers</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>randomness</b> n.</p> + +<p>1. An inexplicable misfeature; gratuitous inelegance. 2. A +<b><a href="#hack">hack</a></b> or <b><a href="#crock">crock</a></b> that depends on a complex combination of +coincidences (or, possibly, the combination upon which the crock +depends for its accidental failure to malfunction). "This hack +can output characters 40-57 by putting the character in the +four-bit accumulator field of an XCT and then extracting six bits +-- the low 2 bits of the XCT opcode are the right thing." "What +randomness!" 3. Of people, synonymous with `flakiness'. The +connotation is that the person so described is behaving weirdly, +incompetently, or inappropriately for reasons which are (a) too +tiresome to bother inquiring into, (b) are probably as +inscrutable as quantum phenomena anyway, and (c) are likely to +pass with time. "Maybe he has a real complaint, or maybe it's +just randomness. See if he calls back."</p> + +<p>Despite the negative connotations jargon uses of this term +have, it is worth noting that randomness can actually be a +valuable resource, very useful for applications in cryptography +and elsewhere. Computers are so thoroughly deterministic that +they have a hard time generating high-quality randomess, so +hackers have sometimes felt the need to built special-purpose +contraptions for this purpose alone. One well-known website +offers random bits generated by radioactive +decay. Another derives random bits from images of Lava Lite lamps. +(Hackers invariably find the latter hilarious. If you have to ask +why, you'll never get it.)</p> + +<hr> +Node:<a name="rape">rape</a>, Next:<a rel="next" href="#raremode">rare mode</a>, Previous:<a rel="previous" href="#randomness">randomness</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>rape</b> vt.</p> + +<p>1. To <b><a href="#screw">screw</a></b> someone or something, +violently; in particular, to destroy a program or information +irrecoverably. Often used in describing file-system damage. +"So-and-so was running a program that did absolute disk I/O and +ended up raping the master directory." 2. To strip a piece of +hardware for parts. 3. [CMU/Pitt] To mass-copy files from an +anonymous ftp site. "Last night I raped Simtel's dskutl +directory."</p> + +<hr> +Node:<a name="raremode">rare mode</a>, Next:<a rel="next" +href="#rasterblaster">raster blaster</a>, Previous:<a rel="previous" href="#rape">rape</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>rare mode</b> adj.</p> + +<p>[Unix] CBREAK mode (character-by-character with interrupts +enabled). Distinguished from <b><a href="#rawmode">raw +mode</a></b> and <b><a href="#cookedmode">cooked mode</a></b>; +the phrase "a sort of half-cooked (rare?) mode" is used in the +V7/BSD manuals to describe the mode. Usage: rare.</p> + +<hr> +Node:<a name="rasterblaster">raster blaster</a>, Next:<a rel="next" href="#rasterburn">raster burn</a>, Previous:<a rel="previous" href="#raremode">rare mode</a>, Up:<a rel="up" +href="#chap18">= R =</a> <br> + + +<p><b>raster blaster</b> n.</p> + +<p>[Cambridge] Specialized hardware for <b><a href="#bitblt">bitblt</a></b> operations (a <b><a href="#blitter">blitter</a></b>). Allegedly inspired by `Rasta +Blasta', British slang for the sort of portable stereo Americans +call a `boom box' or `ghetto blaster'.</p> + +<hr> +Node:<a name="rasterburn">raster burn</a>, Next:<a rel="next" +href="#rasterbation">rasterbation</a>, Previous:<a rel="previous" +href="#rasterblaster">raster blaster</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>raster burn</b> n.</p> + +<p>Eyestrain brought on by too many hours of looking at low-res, +poorly tuned, or glare-ridden monitors, esp. graphics monitors. +See <b><a href="#terminalillness">terminal +illness</a></b>.</p> + +<hr> +Node:<a name="rasterbation">rasterbation</a>, Next:<a rel="next" +href="#ratbelt">rat belt</a>, Previous:<a rel="previous" href="#rasterburn">raster burn</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>rasterbation</b> n.</p> + +<p>[portmanteau: raster + masturbation] The gratuituous use of +comuputer generated images and effects in movies and graphic art +which would have been better without them. Especially employed as +a term of abuse by Photoshop/GIMP users and graphic artists.</p> + +<hr> +Node:<a name="ratbelt">rat belt</a>, Next:<a rel="next" href="#ratdance">rat dance</a>, Previous:<a rel="previous" href="#rasterbation">rasterbation</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>rat belt</b> n.</p> + +<p>A cable tie, esp. the sawtoothed, self-locking plastic kind +that you can remove only by cutting (as opposed to a random twist +of wire or a twist tie or one of those humongous metal clip +frobs). Small cable ties are `mouse belts'.</p> + +<hr> +Node:<a name="ratdance">rat dance</a>, Next:<a rel="next" +href="#ratiosite">ratio site</a>, Previous:<a rel="previous" +href="#ratbelt">rat belt</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>rat dance</b> n.</p> + +<p>[From the <b><a href="#Dilbert">Dilbert</a></b> comic strip of +November 14, 1995] A <b><a href="#hackingrun">hacking +run</a></b> that produces results which, while superficially +coherent, have little or nothing to do with its original +objectives. There are strong connotations that the coding process +and the objectives themselves were pretty <b><a href="#random">random</a></b>. (In the original comic strip, the +Ratbert is invited to dance on Dilbert's keyboard in order to +produce bugs for him to fix, and authors a Web browser instead.) +Compare <b><a href="#InfiniteMonkeyTheorem">Infinite-Monkey +Theorem</a></b>.</p> + +<p>This term seems to have become widely recognized quite rapidly +after the original strip, a fact which testifies to Dilbert's +huge popularity among hackers. All too many find the perverse +incentives and Kafkaesque atmosphere of Dilbert's mythical +workplace reflective of their own experiences.</p> + +<hr> +Node:<a name="ratiosite">ratio site</a>, Next:<a rel="next" +href="#rave">rave</a>, Previous:<a rel="previous" href="#ratdance">rat dance</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>ratio site</b></p> + +<p>[warez d00dz] A FTP site storing pirated files where one must +first upload something before being able to download. There is a +ratio, based on bytes or files count, between the uploads and +download. For instance, on a 2:1 site, to download a 4 Mb file, +one must first upload at least 2 Mb of files. The hotter the +contents of the server are, the smaller the ratio is. More often +than not, the server refuses uploads because its disk is full, +making it useless for downloading - or the connection magically +breaks after one has uploaded a large amount of files, just +before the downloading phase begins. See also <b><a href="#bannersite">banner site</a></b>, <b><a href="#leechmode">leech mode</a></b>.</p> + +<hr> +Node:<a name="rave">rave</a>, Next:<a rel="next" href="#raveon">rave on!</a>, Previous:<a rel="previous" href="#ratiosite">ratio site</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>rave</b> vi.</p> + +<p>[WPI] 1. To persist in discussing a specific subject. 2. To +speak authoritatively on a subject about which one knows very +little. 3. To complain to a person who is not in a position to +correct the difficulty. 4. To purposely annoy another person +verbally. 5. To evangelize. See <b><a href="#flame">flame</a></b>. 6. Also used to describe a less negative +form of blather, such as friendly bullshitting. `Rave' differs +slightly from <b><a href="#flame">flame</a></b> in that `rave' +implies that it is the persistence or obliviousness of the person +speaking that is annoying, while <b><a href="#flame">flame</a></b> implies somewhat more strongly that the +tone or content is offensive as well.</p> + +<hr> +Node:<a name="raveon">rave on!</a>, Next:<a rel="next" href="#ravs">ravs</a>, Previous:<a rel="previous" href="#rave">rave</a>, Up:<a rel="up" href="#chap18">= R =</a> +<br> + + +<p><b>rave on!</b> imp.</p> + +<p>Sarcastic invitation to continue a <b><a href="#rave">rave</a></b>, often by someone who wishes the raver would +get a clue but realizes this is unlikely.</p> + +<hr> +Node:<a name="ravs">ravs</a>, Next:<a rel="next" href="#rawmode">raw mode</a>, Previous:<a rel="previous" href="#raveon">rave on!</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>ravs</b> /ravz/, also `Chinese ravs' n.</p> + +<p>[primarily MIT/Boston usage] Jiao-zi (steamed or boiled) or +Guo-tie (pan-fried). A Chinese appetizer, known variously in the +plural as dumplings, pot stickers (the literal translation of +guo-tie), and (around Boston) `Peking Ravioli'. The term `rav' is +short for `ravioli', and among hackers always means the Chinese +kind rather than the Italian kind. Both consist of a filling in a +pasta shell, but the Chinese kind includes no cheese, uses a +thinner pasta, has a pork-vegetable filling (good ones include +Chinese chives), and is cooked differently, either by steaming or +frying. A rav or dumpling can be cooked any way, but a potsticker +is always the pan-fried kind (so called because it sticks to the +frying pot and has to be scraped off). "Let's get hot-and-sour +soup and three orders of ravs." See also <b><a href="#orientalfood">oriental food</a></b>.</p> + +<hr> +Node:<a name="rawmode">raw mode</a>, Next:<a rel="next" href="#RBL">RBL</a>, Previous:<a rel="previous" href="#ravs">ravs</a>, +Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>raw mode</b> n.</p> + +<p>A mode that allows a program to transfer bits directly to or +from an I/O device (or, under <b><a href="#bogus">bogus</a></b> +operating systems that make a distinction, a disk file) without +any processing, abstraction, or interpretation by the operating +system. Compare <b><a href="#raremode">rare mode</a></b>, +<b><a href="#cookedmode">cooked mode</a></b>. This is +techspeak under Unix, jargon elsewhere.</p> + +<hr> +Node:<a name="RBL">RBL</a>, Next:<a rel="next" href="#rcfile">rc file</a>, Previous:<a rel="previous" href="#rawmode">raw mode</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>RBL</b> /R-B-L/</p> + +<p>Abbreviation: "Realtime Blackhole List". A service that allows +people to blacklist sites for emitting <b><a href="#spam">spam</a></b>, and makes the blacklist available in real +time to electronic-mail transport programs that know how to use +RBL so they can filter out mail from those sites. Drastic (and +controversial) but effective. There is an RBL home page.</p> + +<hr> +Node:<a name="rcfile">rc file</a>, Next:<a rel="next" href="#RE">RE</a>, Previous:<a rel="previous" href="#RBL">RBL</a>, +Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>rc file</b> /R-C fi:l/ n.</p> + +<p>[Unix: from `runcom files' on the <b><a href="#CTSS">CTSS</a></b> system 1962-63, via the startup script +<code>/etc/rc</code>] Script file containing startup instructions +for an application program (or an entire operating system), +usually a text file containing commands of the sort that might +have been invoked manually once the system was running but are to +be executed automatically each time the system starts up. See +also <b><a href="#dotfile">dot file</a></b>, <b><a href="#profile">profile</a></b> (sense 1).</p> + +<hr> +Node:<a name="RE">RE</a>, Next:<a rel="next" href="#readonlyuser">read-only user</a>, Previous:<a rel="previous" href="#rcfile">rc file</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>RE</b> /R-E/ n.</p> + +<p>Common spoken and written shorthand for <b><a href="#regexp">regexp</a></b>.</p> + +<hr> +Node:<a name="readonlyuser">read-only user</a>, Next:<a rel="next" href="#READMEfile">README file</a>, Previous:<a rel="previous" href="#RE">RE</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>read-only user</b> n.</p> + +<p>Describes a <b><a href="#luser">luser</a></b> who uses +computers almost exclusively for reading Usenet, bulletin boards, +and/or email, rather than writing code or purveying useful +information. See <b><a href="#twink">twink</a></b>, <b><a href="#terminaljunkie">terminal junkie</a></b>, <b><a href="#lurker">lurker</a></b>.</p> + +<hr> +Node:<a name="READMEfile">README file</a>, Next:<a rel="next" +href="#real">real</a>, Previous:<a rel="previous" href="#readonlyuser">read-only user</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>README file</b> n.</p> + +<p>Hacker's-eye introduction traditionally included in the +top-level directory of a Unix source distribution, containing a +pointer to more detailed documentation, credits, miscellaneous +revision history, notes, etc. (The file may be named README, or +READ.ME, or rarely ReadMe or readme.txt or some other variant.) +In the Mac and PC worlds, software is not usually distributed in +source form, and the README is more likely to contain +user-oriented material like last-minute documentation changes, +error workarounds, and restrictions. When asked, hackers +invariably relate the README convention to the famous scene in +Lewis Carroll's "Alice's Adventures In Wonderland" in which Alice +confronts magic munchies labeled "Eat Me" and "Drink Me".</p> + +<hr> +Node:<a name="real">real</a>, Next:<a rel="next" href="#realestate">real estate</a>, Previous:<a rel="previous" +href="#READMEfile">README file</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>real</b> adj.</p> + +<p>Not simulated. Often used as a specific antonym to <b><a href="#virtual">virtual</a></b> in any of its jargon senses.</p> + +<hr> +Node:<a name="realestate">real estate</a>, Next:<a rel="next" +href="#realhack">real hack</a>, Previous:<a rel="previous" +href="#real">real</a>, Up:<a rel="up" href="#chap18">= R +=</a> <br> + + +<p><b>real estate</b> n.</p> + +<p>May be used for any critical resource measured in units of +area. Most frequently used of `chip real estate', the area +available for logic on the surface of an integrated circuit (see +also <b><a href="#nanoacre">nanoacre</a></b>). May also be used +of floor space in a <b><a href="#dinosaurpen">dinosaur +pen</a></b>, or even space on a crowded desktop (whether physical +or electronic).</p> + +<hr> +Node:<a name="realhack">real hack</a>, Next:<a rel="next" +href="#realoperatingsystem">real operating system</a>, +Previous:<a rel="previous" href="#realestate">real estate</a>, +Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>real hack</b> n.</p> + +<p>A <b><a href="#crock">crock</a></b>. This is sometimes used +affectionately; see <b><a href="#hack">hack</a></b>.</p> + +<hr> +Node:<a name="realoperatingsystem">real operating +system</a>, Next:<a rel="next" href="#RealProgrammer">Real +Programmer</a>, Previous:<a rel="previous" href="#realhack">real hack</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>real operating system</b> n.</p> + +<p>The sort the speaker is used to. People from the BSDophilic +academic community are likely to issue comments like "System V? +Why don't you use a <i>real</i> operating system?", people from +the commercial/industrial Unix sector are known to complain "BSD? +Why don't you use a <i>real</i> operating system?", and people +from IBM object "Unix? Why don't you use a <i>real</i> +operating system?" Only <b><a href="#MS-DOS">MS-DOS</a></b> is +universally considered unreal. See <b><a href="#holywars">holy +wars</a></b>, <b><a href="#religiousissues">religious +issues</a></b>, <b><a href="#proprietary">proprietary</a></b>, +<b><a href="#Getarealcomputer">Get a real +computer!</a></b></p> + +<hr> +Node:<a name="RealProgrammer">Real Programmer</a>, Next:<a +rel="next" href="#RealSoonNow">Real Soon Now</a>, +Previous:<a rel="previous" href="#realoperatingsystem">real +operating system</a>, Up:<a rel="up" href="#chap18">= R +=</a> <br> + + +<p><b>Real Programmer</b> n.</p> + +<p>[indirectly, from the book "Real Men Don't Eat Quiche"] A +particular sub-variety of hacker: one possessed of a flippant +attitude toward complexity that is arrogant even when justified +by experience. The archetypal `Real Programmer' likes to program +on the <b><a href="#baremetal">bare metal</a></b> and is very +good at same, remembers the binary opcodes for every machine he +has ever programmed, thinks that HLLs are sissy, and uses a +debugger to edit his code because full-screen editors are for +wimps. Real Programmers aren't satisfied with code that hasn't +been <b><a href="#bum">bum</a></b>med into a state of <b><a href="#tense">tense</a></b>ness just short of rupture. Real +Programmers never use comments or write documentation: "If it was +hard to write", says the Real Programmer, "it should be hard to +understand." Real Programmers can make machines do things that +were never in their spec sheets; in fact, they are seldom really +happy unless doing so. A Real Programmer's code can awe with its +fiendish brilliance, even as its crockishness appalls. Real +Programmers live on junk food and coffee, hang line-printer art +on their walls, and terrify the crap out of other programmers -- +because someday, somebody else might have to try to understand +their code in order to change it. Their successors generally +consider it a <b><a href="#GoodThing">Good Thing</a></b> that +there aren't many Real Programmers around any more. For a famous +(and somewhat more positive) portrait of a Real Programmer, see +"<b><a href="#TheStoryofMel">The Story of Mel</a></b>" +in Appendix A. The term itself was popularized by a 1983 +Datamation article "Real Programmers Don't Use Pascal" by Ed +Post, still circulating on Usenet and Internet in on-line form. +You can browse "Real Programmers Don't Use Pascal" from the +Datamation home page http://www.datamation.com.</p> + +<hr> +Node:<a name="RealSoonNow">Real Soon Now</a>, Next:<a rel="next" href="#realTime">real time</a>, Previous:<a rel="previous" href="#RealProgrammer">Real Programmer</a>, Up:<a +rel="up" href="#chap18">= R =</a> <br> + + +<p><b>Real Soon Now</b> adv.</p> + +<p>[orig. from SF's fanzine community, popularized by Jerry +Pournelle's column in "BYTE"] 1. Supposed to be available (or +fixed, or cheap, or whatever) real soon now according to +somebody, but the speaker is quite skeptical. 2. When one's gods, +fates, or other time commitments permit one to get to it (in +other words, don't hold your breath). Often abbreviated RSN. +Compare <b><a href="#copiousfreetime">copious free +time</a></b>.</p> + +<hr> +Node:<a name="realTime">real time</a>, Next:<a rel="next" +href="#realuser">real user</a>, Previous:<a rel="previous" +href="#RealSoonNow">Real Soon Now</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>real time</b></p> + +<p>1. [techspeak] adj. Describes an application which requires a +program to respond to stimuli within some small upper limit of +response time (typically milli- or microseconds). Process control +at a chemical plant is the <b><a href="#canonical">canonical</a></b> example. Such applications often +require special operating systems (because everything else must +take a back seat to response time) and speed-tuned hardware. 2. +adv. In jargon, refers to doing something while people are +watching or waiting. "I asked her how to find the calling +procedure's program counter on the stack and she came up with an +algorithm in real time."</p> + +<hr> +Node:<a name="realuser">real user</a>, Next:<a rel="next" +href="#RealWorld">Real World</a>, Previous:<a rel="previous" +href="#realTime">real time</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>real user</b> n.</p> + +<p>1. A commercial user. One who is paying <i>real</i> money +for his computer usage. 2. A non-hacker. Someone using the system +for an explicit purpose (a research project, a course, etc.) +other than pure exploration. See <b><a href="#user">user</a></b>. +Hackers who are also students may also be real users. "I need +this fixed so I can do a problem set. I'm not complaining out of +randomness, but as a real user." See also <b><a href="#luser">luser</a></b>.</p> + +<hr> +Node:<a name="RealWorld">Real World</a>, Next:<a rel="next" +href="#realitycheck">reality check</a>, Previous:<a rel="previous" href="#realuser">real user</a>, Up:<a rel="up" +href="#chap18">= R =</a> <br> + + +<p><b>Real World</b> n.</p> + +<p>1. Those institutions at which `programming' may be used in +the same sentence as `FORTRAN', `<b><a href="#COBOL">COBOL</a></b>', `RPG', `<b><a href="#IBM">IBM</a></b>', +`DBASE', etc. Places where programs do such commercially +necessary but intellectually uninspiring things as generating +payroll checks and invoices. 2. The location of non-programmers +and activities not related to programming. 3. A bizarre dimension +in which the standard dress is shirt and tie and in which a +person's working hours are defined as 9 to 5 (see <b><a href="#codegrinder">code grinder</a></b>). 4. Anywhere outside a +university. "Poor fellow, he's left MIT and gone into the Real +World." Used pejoratively by those not in residence there. In +conversation, talking of someone who has entered the Real World +is not unlike speaking of a deceased person. It is also +noteworthy that on the campus of Cambridge University in England, +there is a gaily-painted lamp-post which bears the label `REALITY +CHECKPOINT'. It marks the boundary between university and the +Real World; check your notions of reality before passing. This +joke is funnier because the Cambridge `campus' is actually +coextensive with the center of Cambridge town. See also <b><a +href="#fearandloathing">fear and loathing</a></b>, <b><a +href="#mundane">mundane</a></b>, and <b><a href="#uninteresting">uninteresting</a></b>.</p> + +<hr> +Node:<a name="realitycheck">reality check</a>, Next:<a rel="next" href="#realitydistortionfield">reality-distortion +field</a>, Previous:<a rel="previous" href="#RealWorld">Real +World</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>reality check</b> n.</p> + +<p>1. The simplest kind of test of software or hardware; doing +the equivalent of asking it what 2 + 2 is and seeing if you get +4. The software equivalent of a <b><a href="#smoketest">smoke +test</a></b>. 2. The act of letting a <b><a href="#realuser">real user</a></b> try out prototype software. +Compare <b><a href="#sanitycheck">sanity check</a></b>.</p> + +<hr> +Node:<a name="realitydistortionfield">reality-distortion +field</a>, Next:<a rel="next" href="#reaper">reaper</a>, +Previous:<a rel="previous" href="#realitycheck">reality +check</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>reality-distortion field</b> n.</p> + +<p>An expression used to describe the persuasive ability of +managers like Steve Jobs (the term originated at Apple in the +1980s to describe his peculiar charisma). Those close to these +managers become passionately committed to possibly insane +projects, without regard to the practicality of their +implementation or competitive forces in the marketpace.</p> + +<hr> +Node:<a name="reaper">reaper</a>, Next:<a rel="next" href="#recompiletheworld">recompile the world</a>, Previous:<a +rel="previous" href="#realitydistortionfield">reality-distortion field</a>, Up:<a +rel="up" href="#chap18">= R =</a> <br> + + +<p><b>reaper</b> n.</p> + +<p>A <b><a href="#prowler">prowler</a></b> that <b><a href="#GFR">GFR</a></b>s files. A file removed in this way is said to +have been `reaped'.</p> + +<hr> +Node:<a name="recompiletheworld">recompile the world</a>, +Next:<a rel="next" href="#rectangleslinger">rectangle +slinger</a>, Previous:<a rel="previous" href="#reaper">reaper</a>, Up:<a rel="up" href="#chap18">= R +=</a> <br> + + +<p><b>recompile the world</b></p> + +<p>The surprisingly large amount of work that needs to be done as +the result of any small but globally visible program change. "The +world" may mean the entirety of some huge program, or may in +theory refer to every program of a certain class in the entire +known universe. For instance, "Add one #define to stdio.h, and +you have to recompile the world." This means that any minor +change to the standard-I/O header file theoretically mandates +recompiling every C program in existence, even if only to verify +that the change didn't screw something else up. In practice, you +may not actually have to recompile the world, but the implication +is that some human cleverness is required to figure out what +parts can be safely left out.</p> + +<hr> +Node:<a name="rectangleslinger">rectangle slinger</a>, Next:<a +rel="next" href="#recursion">recursion</a>, Previous:<a rel="previous" href="#recompiletheworld">recompile the +world</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>rectangle slinger</b> n.</p> + +<p>See <b><a href="#polygonpusher">polygon pusher</a></b>.</p> + +<hr> +Node:<a name="recursion">recursion</a>, Next:<a rel="next" href="#recursiveacronym">recursive acronym</a>, Previous:<a rel="previous" href="#rectangleslinger">rectangle slinger</a>, +Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>recursion</b> n.</p> + +<p>See <b><a href="#recursion">recursion</a></b>. See also <b><a +href="#tailrecursion">tail recursion</a></b>.</p> + +<hr> +Node:<a name="recursiveacronym">recursive acronym</a>, Next:<a +rel="next" href="#RedBook">Red Book</a>, Previous:<a rel="previous" href="#recursion">recursion</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>recursive acronym</b> n.</p> + +<p>A hackish (and especially MIT) tradition is to choose +acronyms/abbreviations that refer humorously to themselves or to +other acronyms/abbreviations. The classic examples were two MIT +editors called EINE ("EINE Is Not EMACS") and ZWEI ("ZWEI Was +EINE Initially"). More recently, there is a Scheme compiler +called LIAR (Liar Imitates Apply Recursively), and <b><a href="#GNU">GNU</a></b> (q.v., sense 1) stands for "GNU's Not Unix!" +-- and a company with the name Cygnus, which expands to "Cygnus, +Your GNU Support" (though Cygnus people say this is a <b><a href="#backronym">backronym</a></b>). See also <b><a href="#mung">mung</a></b>, <b><a href="#EMACS">EMACS</a></b>.</p> + +<hr> +Node:<a name="RedBook">Red Book</a>, Next:<a rel="next" href="#redwire">red wire</a>, Previous:<a rel="previous" href="#recursiveacronym">recursive acronym</a>, Up:<a rel="up" +href="#chap18">= R =</a> <br> + + +<p><b>Red Book</b> n.</p> + +<p>1. Informal name for one of the four standard references on +<b><a href="#PostScript">PostScript</a></b> ("PostScript Language +Reference Manual", Adobe Systems (Addison-Wesley, 1985; +QA76.73.P67P67; ISBN 0-201-10174-2, or the 1990 second edition +ISBN 0-201-18127-4); the others are known as the <b><a href="#GreenBook">Green Book</a></b>, the <b><a href="#BlueBook">Blue Book</a></b>, and the <b><a href="#WhiteBook">White Book</a></b> (sense 2). 2. Informal name +for one of the 3 standard references on Smalltalk ("Smalltalk-80: +The Interactive Programming Environment" by Adele Goldberg +(Addison-Wesley, 1984; QA76.8.S635G638; ISBN 0-201-11372-4); this +too is associated with blue and green books). 3. Any of the 1984 +standards issued by the CCITT eighth plenary assembly. These +include, among other things, the X.400 email spec and the Group 1 +through 4 fax standards. 4. The new version of the <b><a href="#GreenBook">Green Book</a></b> (sense 4) -- IEEE 1003.1-1990, +a.k.a ISO 9945-1 -- is (because of the color and the fact that it +is printed on A4 paper) known in the USA as "the Ugly Red Book +That Won't Fit On The Shelf" and in Europe as "the Ugly Red Book +That's A Sensible Size". 5. The NSA "Trusted Network +Interpretation" companion to the <b><a href="#OrangeBook">Orange Book</a></b>. 6. Nemeth, Snyder, Seebass, +Hein; "Unix System Administration Handbook, Second Edition" +(Prentice Hall PTR, New Jersey; 1995; QA76.76.063N45; ISBN +0-13-151051-7). See also <b><a href="#booktitles">book +titles</a></b>.</p> + +<hr> +Node:<a name="redwire">red wire</a>, Next:<a rel="next" href="#regexp">regexp</a>, Previous:<a rel="previous" href="#RedBook">Red Book</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>red wire</b> n.</p> + +<p>[IBM] Patch wires installed by programmers who have no +business mucking with the hardware. It is said that the only +thing more dangerous than a hardware guy with a code patch is a +<b><a href="#softy">softy</a></b> with a soldering +iron<small>...</small>. Compare <b><a href="#bluewire">blue +wire</a></b>, <b><a href="#yellowwire">yellow wire</a></b>, +<b><a href="#purplewire">purple wire</a></b>.</p> + +<hr> +Node:<a name="regexp">regexp</a>, Next:<a rel="next" href="#registerdancing">register dancing</a>, Previous:<a rel="previous" href="#redwire">red wire</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>regexp</b> /reg'eksp/ n.</p> + +<p> +[Unix] (alt. `regex' or `reg-ex') 1. Common written and spoken abbreviation for +`regular expression', one of the wildcard patterns used, e.g., by Unix +utilities such as <code>grep(1)</code>, <code>sed(1)</code>, and +<code>awk(1)</code>. These use conventions similar to but more elaborate than +those described under <b><a href="#glob">glob</a></b>. For purposes of this +lexicon, it is sufficient to note that regexps also allow complemented +character sets using <code>^</code>; thus, one can specify `any non-alphabetic +character' with <code>[^A-Za-z]</code>. 2. Name of a well-known PD +regexp-handling package in portable C, written by revered Usenetter Henry +Spencer. +</p> + +<hr> +Node:<a name="registerdancing">register dancing</a>, Next:<a +rel="next" href="#rehi">rehi</a>, Previous:<a rel="previous" +href="#regexp">regexp</a>, Up:<a rel="up" href="#chap18">= +R =</a> <br> + + +<p><b>register dancing</b> n.</p> + +<p>Many older processor architectures suffer from a serious +shortage of general-purpose registers. This is especially a +problem for compiler-writers, because their generated code needs +places to store temporaries for things like intermediate values +in expression evaluation. Some designs with this problem, like +the Intel 80x86, do have a handful of special-purpose registers +that can be pressed into service, providing suitable care is +taken to avoid unpleasant side effects on the state of the +processor: while the special-purpose register is being used to +hold an intermediate value, a delicate minuet is required in +which the previous value of the register is saved and then +restored just before the official function (and value) of the +special-purpose register is again needed.</p> + +<hr> +Node:<a name="rehi">rehi</a>, Next:<a rel="next" href="#reincarnationcycleof">reincarnation cycle of</a>, +Previous:<a rel="previous" href="#registerdancing">register +dancing</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>rehi</b></p> + +<p>[IRC, MUD] "Hello again." Very commonly used to greet people +upon returning to an IRC channel after <b><a href="#channelhopping">channel hopping</a></b>.</p> + +<hr> +Node:<a name="reincarnationcycleof">reincarnation cycle +of</a>, Next:<a rel="next" href="#reinventthewheel">reinvent the wheel</a>, Previous:<a +rel="previous" href="#rehi">rehi</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>reincarnation, cycle of</b> n.</p> + +<p>See <b><a href="#cycleofreincarnation">cycle of +reincarnation</a></b>.</p> + +<hr> +Node:<a name="reinventthewheel">reinvent the wheel</a>, +Next:<a rel="next" href="#relayrape">relay rape</a>, +Previous:<a rel="previous" href="#reincarnationcycleof">reincarnation cycle of</a>, Up:<a +rel="up" href="#chap18">= R =</a> <br> + + +<p><b>reinvent the wheel</b> v.</p> + +<p>To design or implement a tool equivalent to an existing one or +part of one, with the implication that doing so is silly or a +waste of time. This is often a valid criticism. On the other +hand, automobiles don't use wooden rollers, and some kinds of +wheel have to be reinvented many times before you get them right. +On the third hand, people reinventing the wheel do tend to come +up with the moral equivalent of a trapezoid with an offset +axle.</p> + +<hr> +Node:<a name="relayrape">relay rape</a>, Next:<a rel="next" +href="#religionofCHI">religion of CHI</a>, Previous:<a rel="previous" href="#reinventthewheel">reinvent the wheel</a>, +Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>relay rape</b> n.</p> + +<p>The hijacking of a third party's unsecured mail server to +deliver <b><a href="#spam">spam</a></b>.</p> + +<hr> +Node:<a name="religionofCHI">religion of CHI</a>, Next:<a +rel="next" href="#religiousissues">religious issues</a>, +Previous:<a rel="previous" href="#relayrape">relay rape</a>, +Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>religion of CHI</b> /ki:/ n.</p> + +<p>[Case Western Reserve University] Yet another hackish parody +religion (see also <b><a href="#ChurchoftheSubGenius">Church of the SubGenius</a></b>, +<b><a href="#Discordianism">Discordianism</a></b>). In the +mid-70s, the canonical "Introduction to Programming" courses at +CWRU were taught in Algol, and student exercises were punched on +cards and run on a Univac 1108 system using a homebrew operating +system named CHI. The religion had no doctrines and but one +ritual: whenever the worshipper noted that a digital clock read +11:08, he or she would recite the phrase "It is 11:08; ABS, +ALPHABETIC, ARCSIN, ARCCOS, ARCTAN." The last five words were the +first five functions in the appropriate chapter of the Algol +manual; note the special pronunciations /obz/ and /ark'sin/ +rather than the more common /ahbz/ and /ark'si:n/. Using an alarm +clock to warn of 11:08's arrival was <b><a href="#consideredharmful">considered harmful</a></b>.</p> + +<hr> +Node:<a name="religiousissues">religious issues</a>, Next:<a +rel="next" href="#replicator">replicator</a>, Previous:<a rel="previous" href="#religionofCHI">religion of CHI</a>, Up:<a +rel="up" href="#chap18">= R =</a> <br> + + +<p><b>religious issues</b> n.</p> + +<p>Questions which seemingly cannot be raised without touching +off <b><a href="#holywars">holy wars</a></b>, such as "What is +the best operating system (or editor, language, architecture, +shell, mail reader, news reader)?", "What about that Heinlein +guy, eh?", "What should we add to the new Jargon File?" See <b><a +href="#holywars">holy wars</a></b>; see also <b><a href="#theology">theology</a></b>, <b><a href="#bigot">bigot</a></b>.</p> + +<p>This term is a prime example of <b><a href="#hahaonlyserious">ha ha only serious</a></b>. People +actually develop the most amazing and religiously intense +attachments to their tools, even when the tools are intangible. +The most constructive thing one can do when one stumbles into the +crossfire is mumble <b><a href="#Getalife">Get a +life!</a></b> and leave -- unless, of course, one's <i>own</i> +unassailably rational and obviously correct choices are being +slammed.</p> + +<hr> +Node:<a name="replicator">replicator</a>, Next:<a rel="next" +href="#reply">reply</a>, Previous:<a rel="previous" href="#religiousissues">religious issues</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>replicator</b> n.</p> + +<p>Any construct that acts to produce copies of itself; this +could be a living organism, an idea (see <b><a href="#meme">meme</a></b>), a program (see <b><a href="#quine">quine</a></b>, <b><a href="#worm">worm</a></b>, <b><a +href="#wabbit">wabbit</a></b>, <b><a href="#forkbomb">fork +bomb</a></b>, and <b><a href="#virus">virus</a></b>), a pattern +in a cellular automaton (see <b><a href="#life">life</a></b>, +sense 1), or (speculatively) a robot or <b><a href="#nanobot">nanobot</a></b>. It is even claimed by some that <b><a +href="#Unix">Unix</a></b> and <b><a href="#C">C</a></b> are the +symbiotic halves of an extremely successful replicator; see <b><a +href="#Unixconspiracy">Unix conspiracy</a></b>.</p> + +<hr> +Node:<a name="reply">reply</a>, Next:<a rel="next" href="#restriction">restriction</a>, Previous:<a rel="previous" href="#replicator">replicator</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>reply</b> n.</p> + +<p>See <b><a href="#followup">followup</a></b>.</p> + +<hr> +Node:<a name="restriction">restriction</a>, Next:<a rel="next" +href="#retcon">retcon</a>, Previous:<a rel="previous" href="#reply">reply</a>, Up:<a rel="up" href="#chap18">= R +=</a> <br> + + +<p><b>restriction</b> n.</p> + +<p>A <b><a href="#bug">bug</a></b> or design error that limits a +program's capabilities, and which is sufficiently egregious that +nobody can quite work up enough nerve to describe it as a <b><a +href="#feature">feature</a></b>. Often used (esp. by <b><a href="#marketroid">marketroid</a></b> types) to make it sound as +though some crippling bogosity had been intended by the designers +all along, or was forced upon them by arcane technical +constraints of a nature no mere user could possibly comprehend +(these claims are almost invariably false).</p> + +<p>Old-time hacker Joseph M. Newcomer advises that whenever +choosing a quantifiable but arbitrary restriction, you should +make it either a power of 2 or a power of 2 minus 1. If you +impose a limit of 107 items in a list, everyone will know it is a +random number -- on the other hand, a limit of 15 or 16 suggests +some deep reason (involving 0- or 1-based indexing in binary) and +you will get less <b><a href="#flamage">flamage</a></b> for it. +Limits which are round numbers in base 10 are always especially +suspect.</p> + +<hr> +Node:<a name="retcon">retcon</a>, Next:<a rel="next" href="#RETI">RETI</a>, Previous:<a rel="previous" href="#restriction">restriction</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>retcon</b> /ret'kon/</p> + +<p>[short for `retroactive continuity', from the Usenet newsgroup +<i>rec.arts.comics</i>] 1. n. The common situation in pulp +fiction (esp. comics or soap operas) where a new story `reveals' +things about events in previous stories, usually leaving the +`facts' the same (thus preserving continuity) while completely +changing their interpretation. For example, revealing that a +whole season of "Dallas" was a dream was a retcon. 2. vt. To +write such a story about a character or fictitious object. "Byrne +has retconned Superman's cape so that it is no longer +unbreakable." "Marvelman's old adventures were retconned into +synthetic dreams." "Swamp Thing was retconned from a transformed +person into a sentient vegetable." "Darth Vader was retconned +into Luke Skywalker's father in "The Empire Strikes Back".</p> + +<p>[This term is included because it is a good example of hackish +linguistic innovation in a field completely unrelated to +computers. The word `retcon' will probably spread through comics +fandom and lose its association with hackerdom within a couple of +years; for the record, it started here. --ESR]</p> + +<p>[1993 update: some comics fans on the net now claim that +retcon was independently in use in comics fandom before +<i>rec.arts.comics</i>. In lexicography, nothing is ever simple. +--ESR]</p> + +<hr> +Node:<a name="RETI">RETI</a>, Next:<a rel="next" href="#retrocomputing">retrocomputing</a>, Previous:<a rel="previous" +href="#retcon">retcon</a>, Up:<a rel="up" href="#chap18">= +R =</a> <br> + + +<p><b>RETI</b> v.</p> + +<p>Syn. <b><a href="#RTI">RTI</a></b></p> + +<hr> +Node:<a name="retrocomputing">retrocomputing</a>, Next:<a rel="next" href="#returnfromthedead">return from the +dead</a>, Previous:<a rel="previous" href="#RETI">RETI</a>, Up:<a +rel="up" href="#chap18">= R =</a> <br> + + +<p><b>retrocomputing</b> /ret'-roh-k*m-pyoo'ting/ n.</p> + +<p>Refers to emulations of way-behind-the-state-of-the-art +hardware or software, or implementations of +never-was-state-of-the-art; esp. if such implementations are +elaborate practical jokes and/or parodies, written mostly for +<b><a href="#hackvalue">hack value</a></b>, of more `serious' +designs. Perhaps the most widely distributed retrocomputing +utility was the <code>pnch(6)</code> or <code>bcd(6)</code> +program on V7 and other early Unix versions, which would accept +up to 80 characters of text argument and display the +corresponding pattern in <b><a href="#punchedcard">punched +card</a></b> code. Other well-known retrocomputing hacks have +included the programming language <b><a href="#INTERCAL">INTERCAL</a></b>, a <b><a href="#JCL">JCL</a></b>-emulating shell for Unix, the +card-punch-emulating editor named 029, and various elaborate +PDP-11 hardware emulators and RT-11 OS emulators written just to +keep an old, sourceless <b><a href="#Zork">Zork</a></b> binary +running.</p> + +<p>A tasty selection of retrocomputing programs are made +available at the Retrocomputing Museum, http://www.ccil.org/retro.</p> + +<hr> +Node:<a name="returnfromthedead">return from the +dead</a>, Next:<a rel="next" href="#RFC">RFC</a>, Previous:<a +rel="previous" href="#retrocomputing">retrocomputing</a>, Up:<a +rel="up" href="#chap18">= R =</a> <br> + + +<p><b>return from the dead</b> v.</p> + +<p>To regain access to the net after a long absence. Compare +<b><a href="#personofnoaccount">person of no +account</a></b>.</p> + +<hr> +Node:<a name="RFC">RFC</a>, Next:<a rel="next" href="#RFE">RFE</a>, Previous:<a rel="previous" href="#returnfromthedead">return from the dead</a>, Up:<a +rel="up" href="#chap18">= R =</a> <br> + + +<p><b>RFC</b> /R-F-C/ n.</p> + +<p>[Request For Comment] One of a long-established series of +numbered Internet informational documents and standards widely +followed by commercial software and freeware in the Internet and +Unix communities. Perhaps the single most influential one has +been RFC-822 (the Internet mail-format standard). The RFCs are +unusual in that they are floated by technical experts acting on +their own initiative and reviewed by the Internet at large, +rather than formally promulgated through an institution such as +ANSI. For this reason, they remain known as RFCs even once +adopted as standards.</p> + +<p>The RFC tradition of pragmatic, experience-driven, +after-the-fact standard writing done by individuals or small +working groups has important advantages over the more formal, +committee-driven process typical of ANSI or ISO. Emblematic of +some of these advantages is the existence of a flourishing +tradition of `joke' RFCs; usually at least one a year is +published, usually on April 1st. Well-known joke RFCs have +included 527 ("ARPAWOCKY", R. Merryman, UCSD; 22 June 1973), 748 +("Telnet Randomly-Lose Option", Mark R. Crispin; 1 April 1978), +and 1149 ("A Standard for the Transmission of IP Datagrams on +Avian Carriers", D. Waitzman, BBN STC; 1 April 1990). The first +was a Lewis Carroll pastiche; the second a parody of the TCP-IP +documentation style, and the third a deadpan skewering of +standards-document legalese, describing protocols for +transmitting Internet data packets by carrier pigeon.</p> + +<p>The RFCs are most remarkable for how well they work -- they +manage to have neither the ambiguities that are usually rife in +informal specifications, nor the committee-perpetrated +misfeatures that often haunt formal standards, and they define a +network that has grown to truly worldwide proportions.</p> + +<hr> +Node:<a name="RFE">RFE</a>, Next:<a rel="next" href="#ribsite">rib site</a>, Previous:<a rel="previous" href="#RFC">RFC</a>, Up:<a rel="up" href="#chap18">= R =</a> +<br> + + +<p><b>RFE</b> /R-F-E/ n.</p> + +<p>1. [techspeak] Request For Enhancement (compare <b><a href="#RFC">RFC</a></b>). 2. [from `Radio Free Europe', Bellcore and +Sun] Radio Free Ethernet, a system (originated by Peter Langston) +for broadcasting audio among Sun SPARCstations over the +ethernet.</p> + +<hr> +Node:<a name="ribsite">rib site</a>, Next:<a rel="next" href="#ricebox">rice box</a>, Previous:<a rel="previous" href="#RFE">RFE</a>, Up:<a rel="up" href="#chap18">= R =</a> +<br> + + +<p><b>rib site</b> n.</p> + +<p>[by analogy with <b><a href="#backbonesite">backbone +site</a></b>] A machine that has an on-demand high-speed link to +a <b><a href="#backbonesite">backbone site</a></b> and serves +as a regional distribution point for lots of third-party traffic +in email and Usenet news. Compare <b><a href="#leafsite">leaf +site</a></b>, <b><a href="#backbonesite">backbone +site</a></b>.</p> + +<hr> +Node:<a name="ricebox">rice box</a>, Next:<a rel="next" href="#RightThing">Right Thing</a>, Previous:<a rel="previous" +href="#ribsite">rib site</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>rice box</b> n.</p> + +<p>[from ham radio slang] Any Asian-made commodity computer, esp. +an 80x86-based machine built to IBM PC-compatible ISA or EISA-bus +standards.</p> + +<hr> +Node:<a name="RightThing">Right Thing</a>, Next:<a rel="next" +href="#rip">rip</a>, Previous:<a rel="previous" href="#ricebox">rice box</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>Right Thing</b> n.</p> + +<p>That which is <i>compellingly</i> the correct or appropriate +thing to use, do, say, etc. Often capitalized, always emphasized +in speech as though capitalized. Use of this term often implies +that in fact reasonable people may disagree. "What's the right +thing for LISP to do when it sees <code>(mod a 0)</code>? Should +it return <code>a</code>, or give a divide-by-0 error?" Oppose +<b><a href="#WrongThing">Wrong Thing</a></b>.</p> + +<hr> +Node:<a name="rip">rip</a>, Next:<a rel="next" href="#ripoff">ripoff</a>, Previous:<a rel="previous" href="#RightThing">Right Thing</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>rip</b> v.</p> + +<p>1. To extract the digital representation of a piece of music +from an audio CD. Software that does this is often called a "CD +ripper". 2. [Amiga hackers] To extract sound or graphics from a +program that they have been compiled/assembled into, or which +generates them at run-time. In the case of older Amiga games this +entails searching through memory shortly after a reboot. This +sense has been in use for many years and probably gave rise to +the (now more common) sense 1.</p> + +<hr> +Node:<a name="ripoff">ripoff</a>, Next:<a rel="next" href="#RL">RL</a>, Previous:<a rel="previous" href="#rip">rip</a>, +Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>ripoff</b> n.</p> + +<p>Synonym for <b><a href="#chad">chad</a></b>, sense 1.</p> + +<hr> +Node:<a name="RL">RL</a>, Next:<a rel="next" href="#roach">roach</a>, Previous:<a rel="previous" href="#ripoff">ripoff</a>, Up:<a rel="up" href="#chap18">= R +=</a> <br> + + +<p><b>RL</b> // n.</p> + +<p>[MUD community] Real Life. "Firiss laughs in RL" means that +Firiss's player is laughing. Compare <b><a href="#meatspace">meatspace</a></b>; oppose <b><a href="#VR">VR</a></b>.</p> + +<hr> +Node:<a name="roach">roach</a>, Next:<a rel="next" href="#robocanceller">robocanceller</a>, Previous:<a rel="previous" +href="#RL">RL</a>, Up:<a rel="up" href="#chap18">= R =</a> +<br> + + +<p><b>roach</b> vt.</p> + +<p>[Bell Labs] To destroy, esp. of a data structure. Hardware +gets <b><a href="#toast">toast</a></b>ed or <b><a href="#fried">fried</a></b>, software gets roached.</p> + +<hr> +Node:<a name="robocanceller">robocanceller</a>, Next:<a rel="next" href="#robot">robot</a>, Previous:<a rel="previous" href="#roach">roach</a>, Up:<a rel="up" href="#chap18">= R +=</a> <br> + + +<p><b>robocanceller</b> /roh-boh-kan'sel-*r/</p> + +<p>A program that monitors Usenet feeds, attempting to detect and +eliminate <b><a href="#spam">spam</a></b> by sending appropriate +cancel messages . Robocancellers may use the <b><a href="#BreidbartIndex">Breidbart Index</a></b> as a trigger. +Programming them is not a game for amateurs; see <b><a href="#ARMM">ARMM</a></b>. See also <b><a href="#DavetheResurrector">Dave the Resurrector</a></b>.</p> + +<hr> +Node:<a name="robot">robot</a>, Next:<a rel="next" href="#robust">robust</a>, Previous:<a rel="previous" href="#robocanceller">robocanceller</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>robot</b> n.</p> + +<p>See <b><a href="#bot">bot</a></b>.</p> + +<hr> +Node:<a name="robust">robust</a>, Next:<a rel="next" href="#rococo">rococo</a>, Previous:<a rel="previous" href="#robot">robot</a>, Up:<a rel="up" href="#chap18">= R +=</a> <br> + + +<p><b>robust</b> adj.</p> + +<p>Said of a system that has demonstrated an ability to recover +gracefully from the whole range of exceptional inputs and +situations in a given environment. One step below <b><a href="#bulletproof">bulletproof</a></b>. Carries the additional +connotation of elegance in addition to just careful attention to +detail. Compare <b><a href="#smart">smart</a></b>, oppose <b><a +href="#brittle">brittle</a></b>.</p> + +<hr> +Node:<a name="rococo">rococo</a>, Next:<a rel="next" href="#rogue">rogue</a>, Previous:<a rel="previous" href="#robust">robust</a>, Up:<a rel="up" href="#chap18">= R +=</a> <br> + + +<p><b>rococo</b> adj.</p> + +<p>Terminally <b><a href="#baroque">baroque</a></b>. Used to +imply that a program has become so encrusted with the software +equivalent of gold leaf and curlicues that they have completely +swamped the underlying design. Called after the later and more +extreme forms of Baroque architecture and decoration prevalent +during the mid-1700s in Europe. Alan Perlis said: "Every program +eventually becomes rococo, and then rubble." Compare <b><a href="#criticalmass">critical mass</a></b>.</p> + +<hr> +Node:<a name="rogue">rogue</a>, Next:<a rel="next" href="#roomtemperatureIQ">room-temperature IQ</a>, Previous:<a +rel="previous" href="#rococo">rococo</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>rogue</b></p> + +<p>1. [Unix] n. A Dungeons-and-Dragons-like game using character +graphics, written under BSD Unix and subsequently ported to other +Unix systems. The original BSD <code>curses(3)</code> +screen-handling package was hacked together by Ken Arnold +primarily to support games, and the development of +<code>rogue(6)</code> popularized its use; it has since become +one of Unix's most important and heavily used application +libraries. Nethack, Omega, Larn, Angband, and an entire subgenre +of computer dungeon games (all known as `roguelikes') all took +off from the inspiration provided by <code>rogue(6)</code>; the +popular Windows game Diablo, though graphics-intensive, has very +similar play logic. See also <b><a href="#nethack">nethack</a></b>. 2. [Usenet] adj. An <b><a href="#ISP">ISP</a></b> which permits net abuse (usually in the form +of <b><a href="#spam">spam</a></b>ming) by its customers, or +which itself engages in such activities. Rogue ISPs are sometimes +subject to <b><a href="#IDP">IDP</a></b>s or <b><a href="#UDP">UDP</a></b>s. Sometimes deliberately mispelled as "rouge". +See also <b><a href="#nethack">nethack</a></b>, <b><a href="#moria">moria</a></b>, <b><a href="#Angband">Angband</a></b>.</p> + +<hr> +Node:<a name="roomtemperatureIQ">room-temperature IQ</a>, +Next:<a rel="next" href="#root">root</a>, Previous:<a rel="previous" href="#rogue">rogue</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>room-temperature IQ</b> quant.</p> + +<p>[IBM] 80 or below (nominal room temperature is 72 degrees +Fahrenheit, 22 degrees Celsius). Used in describing the expected +intelligence range of the <b><a href="#luser">luser</a></b>. +"Well, but how's this interface going to play with the +room-temperature IQ crowd?" See <b><a href="#droolproofpaper">drool-proof paper</a></b>. This is a much +more insulting phrase in countries that use Celsius +thermometers.</p> + +<hr> +Node:<a name="root">root</a>, Next:<a rel="next" href="#rootmode">root mode</a>, Previous:<a rel="previous" href="#roomtemperatureIQ">room-temperature IQ</a>, Up:<a rel="up" +href="#chap18">= R =</a> <br> + + +<p><b>root</b> n.</p> + +<p>[Unix] 1. The <b><a href="#superuser">superuser</a></b> +account (with user name `root') that ignores permission bits, +user number 0 on a Unix system. The term <b><a href="#avatar">avatar</a></b> is also used. 2. The top node of the +system directory structure; historically the home directory of +the root user, but probably named after the root of an (inverted) +tree. 3. By extension, the privileged system-maintenance login on +any OS. See <b><a href="#rootmode">root mode</a></b>, <b><a +href="#goRoot">go root</a></b>, see also <b><a href="#wheel">wheel</a></b>.</p> + +<hr> +Node:<a name="rootmode">root mode</a>, Next:<a rel="next" +href="#rot13">rot13</a>, Previous:<a rel="previous" href="#root">root</a>, Up:<a rel="up" href="#chap18">= R =</a> +<br> + + +<p><b>root mode</b> n.</p> + +<p>Syn. with <b><a href="#wizardmode">wizard mode</a></b> or +`wheel mode'. Like these, it is often generalized to describe +privileged states in systems other than OSes.</p> + +<hr> +Node:<a name="rot13">rot13</a>, Next:<a rel="next" href="#rotarydebugger">rotary debugger</a>, Previous:<a rel="previous" href="#rootmode">root mode</a>, Up:<a rel="up" +href="#chap18">= R =</a> <br> + + +<p><b>rot13</b> /rot ther'teen/ n.,v.</p> + +<p>[Usenet: from `rotate alphabet 13 places'] The simple +Caesar-cypher encryption that replaces each English letter with +the one 13 places forward or back along the alphabet, so that +"The butler did it!" becomes "Gur ohgyre qvq vg!" Most Usenet +news reading and posting programs include a rot13 feature. It is +used to enclose the text in a sealed wrapper that the reader must +choose to open -- e.g., for posting things that might offend some +readers, or <b><a href="#spoiler">spoiler</a></b>s. A major +advantage of rot13 over rot(N) for other N is that it is +self-inverse, so the same code can be used for encoding and +decoding. See also <b><a href="#spoilerspace">spoiler +space</a></b>, which has partly displaced rot13 since +non-Unix-based newsreaders became common.</p> + +<hr> +Node:<a name="rotarydebugger">rotary debugger</a>, Next:<a +rel="next" href="#roundtape">round tape</a>, Previous:<a rel="previous" href="#rot13">rot13</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>rotary debugger</b> n.</p> + +<p>[Commodore] Essential equipment for those late-night or +early-morning debugging sessions. Mainly used as sustenance for +the hacker. Comes in many decorator colors, such as Sausage, +Pepperoni, and Garbage. See <b><a href="#ANSIstandardpizza">ANSI standard pizza</a></b>.</p> + +<hr> +Node:<a name="roundtape">round tape</a>, Next:<a rel="next" +href="#RSN">RSN</a>, Previous:<a rel="previous" href="#rotarydebugger">rotary debugger</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>round tape</b> n.</p> + +<p>Industry-standard 1/2-inch magnetic tape (7- or 9-track) on +traditional circular reels. See <b><a href="#macrotape">macrotape</a></b>, oppose <b><a href="#squaretape">square tape</a></b>.</p> + +<hr> +Node:<a name="RSN">RSN</a>, Next:<a rel="next" href="#RTBM">RTBM</a>, Previous:<a rel="previous" href="#roundtape">round tape</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>RSN</b> /R-S-N/ adj.</p> + +<p>See <b><a href="#RealSoonNow">Real Soon Now</a></b>.</p> + +<hr> +Node:<a name="RTBM">RTBM</a>, Next:<a rel="next" href="#RTFAQ">RTFAQ</a>, Previous:<a rel="previous" href="#RSN">RSN</a>, Up:<a rel="up" href="#chap18">= R =</a> +<br> + + +<p><b>RTBM</b> /R-T-B-M/ imp.</p> + +<p>[Unix] Commonwealth Hackish variant of <b><a href="#RTFM">RTFM</a></b>; expands to `Read The Bloody Manual'. RTBM +is often the entire text of the first reply to a question from a +<b><a href="#newbie">newbie</a></b>; the <i>second</i> would +escalate to "RTFM".</p> + +<hr> +Node:<a name="RTFAQ">RTFAQ</a>, Next:<a rel="next" href="#RTFB">RTFB</a>, Previous:<a rel="previous" href="#RTBM">RTBM</a>, Up:<a rel="up" href="#chap18">= R =</a> +<br> + + +<p><b>RTFAQ</b> /R-T-F-A-Q/ imp.</p> + +<p>[Usenet: primarily written, by analogy with <b><a href="#RTFM">RTFM</a></b>] Abbrev. for `Read the FAQ!', an exhortation +that the person addressed ought to read the newsgroup's <b><a +href="#FAQlist">FAQ list</a></b> before posting questions.</p> + +<hr> +Node:<a name="RTFB">RTFB</a>, Next:<a rel="next" href="#RTFM">RTFM</a>, Previous:<a rel="previous" href="#RTFAQ">RTFAQ</a>, Up:<a rel="up" href="#chap18">= R +=</a> <br> + + +<p><b>RTFB</b> /R-T-F-B/ imp.</p> + +<p>[Unix] Abbreviation for `Read The Fucking Binary'. Used when +neither documentation nor source for the problem at hand exists, +and the only thing to do is use some debugger or monitor and +directly analyze the assembler or even the machine code. "No +source for the buggy port driver? Aaargh! I <i>hate</i> +proprietary operating systems. Time to RTFB."</p> + +<p>Of the various RTF? forms, `RTFB' is the least pejorative +against anyone asking a question for which RTFB is the answer; +the anger here is directed at the absence of both source +<i>and</i> adequate documentation.</p> + +<hr> +Node:<a name="RTFM">RTFM</a>, Next:<a rel="next" href="#RTFS">RTFS</a>, Previous:<a rel="previous" href="#RTFB">RTFB</a>, Up:<a rel="up" href="#chap18">= R =</a> +<br> + + +<p><b>RTFM</b> /R-T-F-M/ imp.</p> + +<p>[Unix] Abbreviation for `Read The Fucking Manual'. 1. Used by +<b><a href="#guru">guru</a></b>s to brush off questions they +consider trivial or annoying. Compare <b><a href="#Dontdothatthen">Don't do that then!</a></b>. 2. Used +when reporting a problem to indicate that you aren't just asking +out of <b><a href="#randomness">randomness</a></b>. "No, I can't +figure out how to interface Unix to my toaster, and yes, I have +RTFM." Unlike sense 1, this use is considered polite. See also +<b><a href="#FM">FM</a></b>, <b><a href="#RTFAQ">RTFAQ</a></b>, +<b><a href="#RTFB">RTFB</a></b>, <b><a href="#RTFS">RTFS</a></b>, +<b><a href="#STFW">STFW</a></b>, <b><a href="#RTM">RTM</a></b>, +all of which mutated from RTFM, and compare <b><a href="#UTSL">UTSL</a></b>.</p> + +<hr> +Node:<a name="RTFS">RTFS</a>, Next:<a rel="next" href="#RTI">RTI</a>, Previous:<a rel="previous" href="#RTFM">RTFM</a>, +Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>RTFS</b> /R-T-F-S/</p> + +<p>[Unix] 1. imp. Abbreviation for `Read The Fucking Source'. +Variant form of <b><a href="#RTFM">RTFM</a></b>, used when the +problem at hand is not necessarily obvious and not answerable +from the manuals -- or the manuals are not yet written and maybe +never will be. For even trickier situations, see <b><a href="#RTFB">RTFB</a></b>. Unlike RTFM, the anger inherent in RTFS is +not usually directed at the person asking the question, but +rather at the people who failed to provide adequate +documentation. 2. imp. `Read The Fucking Standard'; this oath can +only be used when the problem area (e.g., a language or operating +system interface) has actually been codified in a ratified +standards document. The existence of these standards documents +(and the technically inappropriate but politically mandated +compromises that they inevitably contain, and the impenetrable +<b><a href="#legalese">legalese</a></b> in which they are +invariably written, and the unbelievably tedious bureaucratic +process by which they are produced) can be unnerving to hackers, +who are used to a certain amount of ambiguity in the +specifications of the systems they use. (Hackers feel that such +ambiguities are acceptable as long as the <b><a href="#RightThing">Right Thing</a></b> to do is obvious to any +thinking observer; sadly, this casual attitude towards +specifications becomes unworkable when a system becomes popular +in the <b><a href="#RealWorld">Real World</a></b>.) Since a +hacker is likely to feel that a standards document is both +unnecessary and technically deficient, the deprecation inherent +in this term may be directed as much against the standard as +against the person who ought to read it.</p> + +<hr> +Node:<a name="RTI">RTI</a>, Next:<a rel="next" href="#RTM">RTM</a>, Previous:<a rel="previous" href="#RTFS">RTFS</a>, +Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>RTI</b> /R-T-I/ interj.</p> + +<p>The mnemonic for the `return from interrupt' instruction on +many computers including the 6502 and 6800. The variant `RETI' is +found among former Z80 hackers (almost nobody programs these +things in assembler anymore). Equivalent to "Now, where was I?" +or used to end a conversational digression. See <b><a href="#pop">pop</a></b>; see also <b><a href="#POPJ">POPJ</a></b>.</p> + +<hr> +Node:<a name="RTM">RTM</a>, Next:<a rel="next" href="#RTS">RTS</a>, Previous:<a rel="previous" href="#RTI">RTI</a>, +Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>RTM</b> /R-T-M/</p> + +<p>[Usenet: abbreviation for `Read The Manual'] 1. Politer +variant of <b><a href="#RTFM">RTFM</a></b>. 2. Robert Tappan +Morris, perpetrator of the great Internet worm of 1988 (see <b><a +href="#GreatWorm">Great Worm</a></b>); villain to many, naive +hacker gone wrong to a few. Morris claimed that the worm that +brought the Internet to its knees was a benign experiment that +got out of control as the result of a coding error. After the +storm of negative publicity that followed this blunder, Morris's +username on ITS was hacked from RTM to <b><a href="#RTFM">RTFM</a></b>.</p> + +<hr> +Node:<a name="RTS">RTS</a>, Next:<a rel="next" href="#rude">rude</a>, Previous:<a rel="previous" href="#RTM">RTM</a>, +Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>RTS</b> /R-T-S/ imp.</p> + +<p>Abbreviation for `Read The Screen'. Mainly used by hackers in +the microcomputer world. Refers to what one would like to tell +the <b><a href="#suit">suit</a></b> one is forced to explain an +extremely simple application to. Particularly appropriate when +the suit failed to notice the `Press any key to continue' prompt, +and wishes to know `why won't it do anything'. Also seen as +`RTFS' in especially deserving cases.</p> + +<hr> +Node:<a name="rude">rude</a>, Next:<a rel="next" href="#runes">runes</a>, Previous:<a rel="previous" href="#RTS">RTS</a>, Up:<a rel="up" href="#chap18">= R =</a> +<br> + + +<p><b>rude</b> [WPI] adj.</p> + +<p>1. (of a program) Badly written. 2. Functionally poor, e.g., a +program that is very difficult to use because of gratuitously +poor (random?) design decisions. Oppose <b><a href="#cuspy">cuspy</a></b>. 3. Anything that manipulates a shared +resource without regard for its other users in such a way as to +cause a (non-fatal) problem. Examples: programs that change tty +modes without resetting them on exit, or windowing programs that +keep forcing themselves to the top of the window stack. Compare +<b><a href="#all-elbows">all-elbows</a></b>.</p> + +<hr> +Node:<a name="runes">runes</a>, Next:<a rel="next" href="#runic">runic</a>, Previous:<a rel="previous" href="#rude">rude</a>, Up:<a rel="up" href="#chap18">= R =</a> +<br> + + +<p><b>runes</b> pl.n.</p> + +<p>1. Anything that requires <b><a href="#heavywizardry">heavy +wizardry</a></b> or <b><a href="#blackart">black art</a></b> +to <b><a href="#parse">parse</a></b>: core dumps, JCL commands, +APL, or code in a language you haven't a clue how to read. Not +quite as bad as <b><a href="#linenoise">line noise</a></b>, +but close. Compare <b><a href="#castingtherunes">casting +the runes</a></b>, <b><a href="#GreatRunes">Great +Runes</a></b>. 2. Special display characters (for example, the +high-half graphics on an IBM PC). 3. [borderline techspeak] +16-bit characters from the Unicode multilingual character +set.</p> + +<hr> +Node:<a name="runic">runic</a>, Next:<a rel="next" href="#rustyiron">rusty iron</a>, Previous:<a rel="previous" href="#runes">runes</a>, Up:<a rel="up" href="#chap18">= R +=</a> <br> + + +<p><b>runic</b> adj.</p> + +<p>Syn. <b><a href="#obscure">obscure</a></b>. VMS fans sometimes +refer to Unix as `Runix'; Unix fans return the compliment by +expanding VMS to `Very Messy Syntax' or `Vachement Mauvais +Système' (French idiom, "Hugely Bad System").</p> + +<hr> +Node:<a name="rustyiron">rusty iron</a>, Next:<a rel="next" +href="#rustymemory">rusty memory</a>, Previous:<a rel="previous" href="#runic">runic</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>rusty iron</b> n.</p> + +<p>Syn. <b><a href="#tirediron">tired iron</a></b>. It has +been claimed that this is the inevitable fate of <b><a href="#waterMIPS">water MIPS</a></b>.</p> + +<hr> +Node:<a name="rustymemory">rusty memory</a>, Next:<a rel="next" href="#rustywire">rusty wire</a>, Previous:<a rel="previous" href="#rustyiron">rusty iron</a>, Up:<a rel="up" +href="#chap18">= R =</a> <br> + + +<p><b>rusty memory</b> n.</p> + +<p>Mass-storage that uses iron-oxide-based magnetic media (esp. +tape and the pre-Winchester removable disk packs used in <b><a +href="#washingmachine">washing machine</a></b>s). Compare +<b><a href="#donuts">donuts</a></b>.</p> + +<hr> +Node:<a name="rustywire">rusty wire</a>, Next:<a rel="next" +href="#SfNratio">S/N ratio</a>, Previous:<a rel="previous" +href="#rustymemory">rusty memory</a>, Up:<a rel="up" href="#chap18">= R =</a> <br> + + +<p><b>rusty wire</b> n.</p> + +<p>[Amateur Packet Radio] Any very noisy network medium, in which +the packets are subject to frequent corruption. Most prevalent in +reference to wireless links subject to all the vagaries of RF +noise and marginal propagation conditions. "Yes, but how good is +your whizbang new protocol on really rusty wire?".</p> + +<hr> +Node:<a name="chap19">= S =</a>, Next:<a rel="next" href="#chap20">= T =</a>, Previous:<a rel="previous" href="#chap18">= R =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= S =</h2> + +<ul> +<li><a href="#SfNratio">S/N ratio</a>:</li> + +<li><a href="#sacred">sacred</a>:</li> + +<li><a href="#saga">saga</a>:</li> + +<li><a href="#sagan">sagan</a>:</li> + +<li><a href="#SAIL">SAIL</a>:</li> + +<li><a href="#salescritter">salescritter</a>:</li> + +<li><a href="#salt">salt</a>:</li> + +<li><a href="#saltmines">salt mines</a>:</li> + +<li><a href="#saltsubstrate">salt substrate</a>:</li> + +<li><a href="#samedayservice">same-day service</a>:</li> + +<li><a href="#samizdat">samizdat</a>:</li> + +<li><a href="#samurai">samurai</a>:</li> + +<li><a href="#sandbender">sandbender</a>:</li> + +<li><a href="#sandbox">sandbox</a>:</li> + +<li><a href="#sanitycheck">sanity check</a>:</li> + +<li><a href="#Saturdaynightspecial">Saturday-night special</a>:</li> + +<li><a href="#say">say</a>:</li> + +<li><a href="#scag">scag</a>:</li> + +<li><a href="#scanno">scanno</a>:</li> + +<li><a href="#scarydevilmonastery">scary devil monastery</a>:</li> + +<li><a href="#schroedinbug">schroedinbug</a>:</li> + +<li><a href="#science-fictionfandom">science-fiction fandom</a>:</li> + +<li><a href="#scramswitch">scram switch</a>:</li> + +<li><a href="#scratch">scratch</a>:</li> + +<li><a href="#scratchmonkey">scratch monkey</a>:</li> + +<li><a href="#screamanddie">scream and die</a>:</li> + +<li><a href="#screamingtty">screaming tty</a>:</li> + +<li><a href="#screen">screen</a>:</li> + +<li><a href="#screenname">screen name</a>:</li> + +<li><a href="#screw">screw</a>:</li> + +<li><a href="#screwage">screwage</a>:</li> + +<li><a href="#scribble">scribble</a>:</li> + +<li><a href="#scriptkiddies">script kiddies</a>:</li> + +<li><a href="#scrog">scrog</a>:</li> + +<li><a href="#scrool">scrool</a>:</li> + +<li><a href="#scrozzle">scrozzle</a>:</li> + +<li><a href="#scruffies">scruffies</a>:</li> + +<li><a href="#SCSI">SCSI</a>:</li> + +<li><a href="#ScumOS">ScumOS</a>:</li> + +<li><a href="#searchanddestroymode">search-and-destroy mode</a>:</li> + +<li><a href="#second-systemeffect">second-system effect</a>:</li> + +<li><a href="#secondarydamage">secondary damage</a>:</li> + +<li><a href="#securitythroughobscurity">security through obscurity</a>:</li> + +<li><a href="#SED">SED</a>:</li> + +<li><a href="#segfault">segfault</a>:</li> + +<li><a href="#seggie">seggie</a>:</li> + +<li><a href="#segment">segment</a>:</li> + +<li><a href="#segmentationfault">segmentation fault</a>:</li> + +<li><a href="#segv">segv</a>:</li> + +<li><a href="#self-reference">self-reference</a>:</li> + +<li><a href="#selvage">selvage</a>:</li> + +<li><a href="#semi">semi</a>:</li> + +<li><a href="#semi-automated">semi-automated</a>:</li> + +<li><a href="#semi-infinite">semi-infinite</a>:</li> + +<li><a href="#seniorbit">senior bit</a>:</li> + +<li><a href="#Septemberthatneverended">September that never ended</a>:</li> + +<li><a href="#server">server</a>:</li> + +<li><a href="#SEX">SEX</a>:</li> + +<li><a href="#sexchanger">sex changer</a>:</li> + +<li><a href="#shamboliclink">shambolic link</a>:</li> + +<li><a href="#sharfile">shar file</a>:</li> + +<li><a href="#sharchive">sharchive</a>:</li> + +<li><a href="#Shareandenjoy">Share and enjoy!</a>:</li> + +<li><a href="#shareware">shareware</a>:</li> + +<li><a href="#sharingviolation">sharing violation</a>:</li> + +<li><a href="#shebang">shebang</a>:</li> + +<li><a href="#shelfware">shelfware</a>:</li> + +<li><a href="#shell">shell</a>:</li> + +<li><a href="#shellout">shell out</a>:</li> + +<li><a href="#shiftleftorrightlogical">shift left (or right) logical</a>:</li> + +<li><a href="#shim">shim</a>:</li> + +<li><a href="#shitogram">shitogram</a>:</li> + +<li><a href="#shortcard">short card</a>:</li> + +<li><a href="#shotgundebugging">shotgun debugging</a>:</li> + +<li><a href="#shovelware">shovelware</a>:</li> + +<li><a href="#showstopper">showstopper</a>:</li> + +<li><a href="#shriek">shriek</a>:</li> + +<li><a href="#Shub-Internet">Shub-Internet</a>:</li> + +<li><a href="#sidecar">sidecar</a>:</li> + +<li><a href="#SIG">SIG</a>:</li> + +<li><a href="#sigblock">sig block</a>:</li> + +<li><a href="#sigquote">sig quote</a>:</li> + +<li><a href="#sigvirus">sig virus</a>:</li> + +<li><a href="#signaltonoiseratio">signal-to-noise ratio</a>:</li> + +<li><a href="#silicon">silicon</a>:</li> + +<li><a href="#sillywalk">silly walk</a>:</li> + +<li><a href="#silo">silo</a>:</li> + +<li><a href="#SilverBook">Silver Book</a>:</li> + +<li><a href="#sincetimeTequalsminusinfinity">since time T equals minus infinity</a>:</li> + +<li><a href="#sitename">sitename</a>:</li> + +<li><a href="#skrog">skrog</a>:</li> + +<li><a href="#skulker">skulker</a>:</li> + +<li><a href="#slab">slab</a>:</li> + +<li><a href="#slack">slack</a>:</li> + +<li><a href="#slapontheside">slap on the side</a>:</li> + +<li><a href="#slash">slash</a>:</li> + +<li><a href="#slashdoteffect">slashdot effect</a>:</li> + +<li><a href="#sleep">sleep</a>:</li> + +<li><a href="#slim">slim</a>:</li> + +<li><a href="#slop">slop</a>:</li> + +<li><a href="#slopsucker">slopsucker</a>:</li> + +<li><a href="#Slowlaris">Slowlaris</a>:</li> + +<li><a href="#slurp">slurp</a>:</li> + +<li><a href="#smart">smart</a>:</li> + +<li><a href="#smartterminal">smart terminal</a>:</li> + +<li><a href="#smashcase">smash case</a>:</li> + +<li><a href="#smashthestack">smash the stack</a>:</li> + +<li><a href="#smiley">smiley</a>:</li> + +<li><a href="#smoke">smoke</a>:</li> + +<li><a href="#smokeandmirrors">smoke and mirrors</a>:</li> + +<li><a href="#smoketest">smoke test</a>:</li> + +<li><a href="#smokingclover">smoking clover</a>:</li> + +<li><a href="#smoot">smoot</a>:</li> + +<li><a href="#SMOP">SMOP</a>:</li> + +<li><a href="#smurf">smurf</a>:</li> + +<li><a href="#SNAFUprinciple">SNAFU principle</a>:</li> + +<li><a href="#snail">snail</a>:</li> + +<li><a href="#snail-mail">snail-mail</a>:</li> + +<li><a href="#snap">snap</a>:</li> + +<li><a href="#snarf">snarf</a>:</li> + +<li><a href="#snarfampbarf">snarf & barf</a>:</li> + +<li><a href="#snarfdown">snarf down</a>:</li> + +<li><a href="#snark">snark</a>:</li> + +<li><a href="#sneaker">sneaker</a>:</li> + +<li><a href="#sneakernet">sneakernet</a>:</li> + +<li><a href="#sniff">sniff</a>:</li> + +<li><a href="#snivitz">snivitz</a>:</li> + +<li><a href="#Snooze">'Snooze</a>:</li> + +<li><a href="#SO">SO</a>:</li> + +<li><a href="#socialengineering">social engineering</a>:</li> + +<li><a href="#socialsciencenumber">social science number</a>:</li> + +<li><a href="#sockpuppet">sock puppet</a>:</li> + +<li><a href="#sodiumsubstrate">sodium substrate</a>:</li> + +<li><a href="#softboot">soft boot</a>:</li> + +<li><a href="#softcopy">softcopy</a>:</li> + +<li><a href="#softwarebloat">software bloat</a>:</li> + +<li><a href="#softwarehoarding">software hoarding</a>:</li> + +<li><a href="#softwarelaser">software laser</a>:</li> + +<li><a href="#softwarerot">software rot</a>:</li> + +<li><a href="#softwarily">softwarily</a>:</li> + +<li><a href="#softy">softy</a>:</li> + +<li><a href="#somerandomX">some random X</a>:</li> + +<li><a href="#sorcerersapprenticemode">sorcerer's apprentice mode</a>:</li> + +<li><a href="#SOS">SOS</a>:</li> + +<li><a href="#source">source</a>:</li> + +<li><a href="#sourceofallgoodbits">source of all good bits</a>:</li> + +<li><a href="#space-cadetkeyboard">space-cadet keyboard</a>:</li> + +<li><a href="#spaceshipoperator">spaceship operator</a>:</li> + +<li><a href="#SPACEWAR">SPACEWAR</a>:</li> + +<li><a href="#spaghetticode">spaghetti code</a>:</li> + +<li><a href="#spaghettiinheritance">spaghetti inheritance</a>:</li> + +<li><a href="#spam">spam</a>:</li> + +<li><a href="#spambait">spam bait</a>:</li> + +<li><a href="#spamblock">spamblock</a>:</li> + +<li><a href="#spamhaus">spamhaus</a>:</li> + +<li><a href="#spamvertize">spamvertize</a>:</li> + +<li><a href="#spangle">spangle</a>:</li> + +<li><a href="#spawn">spawn</a>:</li> + +<li><a href="#special-case">special-case</a>:</li> + +<li><a href="#speedometer">speedometer</a>:</li> + +<li><a href="#spell">spell</a>:</li> + +<li><a href="#spellingflame">spelling flame</a>:</li> + +<li><a href="#spider">spider</a>:</li> + +<li><a href="#spiderfood">spider food</a>:</li> + +<li><a href="#spiffy">spiffy</a>:</li> + +<li><a href="#spike">spike</a>:</li> + +<li><a href="#spin">spin</a>:</li> + +<li><a href="#spl">spl</a>:</li> + +<li><a href="#splashscreen">splash screen</a>:</li> + +<li><a href="#splat">splat</a>:</li> + +<li><a href="#splatout">splat out</a>:</li> + +<li><a href="#spod">spod</a>:</li> + +<li><a href="#spoiler">spoiler</a>:</li> + +<li><a href="#spoilerspace">spoiler space</a>:</li> + +<li><a href="#sponge">sponge</a>:</li> + +<li><a href="#spoof">spoof</a>:</li> + +<li><a href="#spool">spool</a>:</li> + +<li><a href="#spoolfile">spool file</a>:</li> + +<li><a href="#spungle">spungle</a>:</li> + +<li><a href="#squaretape">square tape</a>:</li> + +<li><a href="#squirrelcide">squirrelcide</a>:</li> + +<li><a href="#stack">stack</a>:</li> + +<li><a href="#stackpuke">stack puke</a>:</li> + +<li><a href="#stalepointerbug">stale pointer bug</a>:</li> + +<li><a href="#starout">star out</a>:</li> + +<li><a href="#state">state</a>:</li> + +<li><a href="#stealthmanager">stealth manager</a>:</li> + +<li><a href="#steam-powered">steam-powered</a>:</li> + +<li><a href="#STFW">STFW</a>:</li> + +<li><a href="#stiffy">stiffy</a>:</li> + +<li><a href="#stirfriedrandom">stir-fried random</a>:</li> + +<li><a href="#stompon">stomp on</a>:</li> + +<li><a href="#StoneAge">Stone Age</a>:</li> + +<li><a href="#stoneknivesandbearskins">stone knives and bearskins</a>:</li> + +<li><a href="#stoppage">stoppage</a>:</li> + +<li><a href="#store">store</a>:</li> + +<li><a href="#strided">strided</a>:</li> + +<li><a href="#stroke">stroke</a>:</li> + +<li><a href="#strudel">strudel</a>:</li> + +<li><a href="#stubroutine">stubroutine</a>:</li> + +<li><a href="#studly">studly</a>:</li> + +<li><a href="#studlycaps">studlycaps</a>:</li> + +<li><a href="#stunning">stunning</a>:</li> + +<li><a href="#stupid-sort">stupid-sort</a>:</li> + +<li><a href="#Stupids">Stupids</a>:</li> + +<li><a href="#SturgeonsLaw">Sturgeon's Law</a>:</li> + +<li><a href="#suckingmud">sucking mud</a>:</li> + +<li><a href="#sufficientlysmall">sufficiently small</a>:</li> + +<li><a href="#suit">suit</a>:</li> + +<li><a href="#suitablewin">suitable win</a>:</li> + +<li><a href="#suitablysmall">suitably small</a>:</li> + +<li><a href="#Sun">Sun</a>:</li> + +<li><a href="#sunlounge">sun lounge</a>:</li> + +<li><a href="#sun-stools">sun-stools</a>:</li> + +<li><a href="#sunspots">sunspots</a>:</li> + +<li><a href="#supersourcequench">super source quench</a>:</li> + +<li><a href="#superloser">superloser</a>:</li> + +<li><a href="#superprogrammer">superprogrammer</a>:</li> + +<li><a href="#superuser">superuser</a>:</li> + +<li><a href="#support">support</a>:</li> + +<li><a href="#surf">surf</a>:</li> + +<li><a href="#SuzieCOBOL">Suzie COBOL</a>:</li> + +<li><a href="#swab">swab</a>:</li> + +<li><a href="#swap">swap</a>:</li> + +<li><a href="#swapspace">swap space</a>:</li> + +<li><a href="#swappedin">swapped in</a>:</li> + +<li><a href="#swappedout">swapped out</a>:</li> + +<li><a href="#swizzle">swizzle</a>:</li> + +<li><a href="#sync">sync</a>:</li> + +<li><a href="#syntacticsalt">syntactic salt</a>:</li> + +<li><a href="#syntacticsugar">syntactic sugar</a>:</li> + +<li><a href="#sys-frog">sys-frog</a>:</li> + +<li><a href="#sysadmin">sysadmin</a>:</li> + +<li><a href="#sysape">sysape</a>:</li> + +<li><a href="#sysop">sysop</a>:</li> + +<li><a href="#system">system</a>:</li> + +<li><a href="#systemsjock">systems jock</a>:</li> + +<li><a href="#systemmangler">system mangler</a>:</li> + +<li><a href="#SysVile">SysVile</a>:</li> +</ul> + +<hr> +Node:<a name="SfNratio">S/N ratio</a>, Next:<a rel="next" +href="#sacred">sacred</a>, Previous:<a rel="previous" href="#rustywire">rusty wire</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>S/N ratio</b> // n.</p> + +<p>(also `s/n ratio', `s:n ratio'). Syn. <b><a href="#signaltonoiseratio">signal-to-noise ratio</a></b>. Often +abbreviated `SNR'.</p> + +<hr> +Node:<a name="sacred">sacred</a>, Next:<a rel="next" href="#saga">saga</a>, Previous:<a rel="previous" href="#SfNratio">S/N ratio</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>sacred</b> adj.</p> + +<p>Reserved for the exclusive use of something (an extension of +the standard meaning). Often means that anyone may look at the +sacred object, but clobbering it will screw whatever it is sacred +to. The comment "Register 7 is sacred to the interrupt handler" +appearing in a program would be interpreted by a hacker to mean +that if any <i>other</i> part of the program changes the +contents of register 7, dire consequences are likely to +ensue.</p> + +<hr> +Node:<a name="saga">saga</a>, Next:<a rel="next" href="#sagan">sagan</a>, Previous:<a rel="previous" href="#sacred">sacred</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>saga</b> n.</p> + +<p>[WPI] A cuspy but bogus raving story about N random broken +people.</p> + +<p>Here is a classic example of the saga form, as told by Guy L. +Steele:</p> + +<blockquote>Jon L. White (login name JONL) and I (GLS) were +office mates at MIT for many years. One April, we both flew from +Boston to California for a week on research business, to consult +face-to-face with some people at Stanford, particularly our +mutual friend Richard P. Gabriel (RPG; see <b><a href="#gabriel">gabriel</a></b>). + +<p>RPG picked us up at the San Francisco airport and drove us +back to Palo Alto (going <b><a href="#logical">logical</a></b> +south on route 101, parallel to <b><a href="#ElCaminoBignum">El Camino Bignum</a></b>). Palo Alto is +adjacent to Stanford University and about 40 miles south of San +Francisco. We ate at The Good Earth, a `health food' restaurant, +very popular, the sort whose milkshakes all contain honey and +protein powder. JONL ordered such a shake -- the waitress claimed +the flavor of the day was "lalaberry". I still have no idea what +that might be, but it became a running joke. It was the color of +raspberry, and JONL said it tasted rather bitter. I ate a better +tostada there than I have ever had in a Mexican restaurant.</p> + +<p>After this we went to the local Uncle Gaylord's Old Fashioned +Ice Cream Parlor. They make ice cream fresh daily, in a variety +of intriguing flavors. It's a chain, and they have a slogan: "If +you don't live near an Uncle Gaylord's -- MOVE!" Also, Uncle +Gaylord (a real person) wages a constant battle to force big-name +ice cream makers to print their ingredients on the package (like +air and plastic and other non-natural garbage). JONL and I had +first discovered Uncle Gaylord's the previous August, when we had +flown to a computer-science conference in Berkeley, California, +the first time either of us had been on the West Coast. When not +in the conference sessions, we had spent our time wandering the +length of Telegraph Avenue, which (like Harvard Square in +Cambridge) was lined with picturesque street vendors and +interesting little shops. On that street we discovered Uncle +Gaylord's Berkeley store. The ice cream there was very good. +During that August visit JONL went absolutely bananas (so to +speak) over one particular flavor, ginger honey.</p> + +<p>Therefore, after eating at The Good Earth -- indeed, after +every lunch and dinner and before bed during our April visit -- a +trip to Uncle Gaylord's (the one in Palo Alto) was mandatory. We +had arrived on a Wednesday, and by Thursday evening we had been +there at least four times. Each time, JONL would get ginger honey +ice cream, and proclaim to all bystanders that "Ginger was the +spice that drove the Europeans mad! That's why they sought a +route to the East! They used it to preserve their otherwise +off-taste meat." After the third or fourth repetition RPG and I +were getting a little tired of this spiel, and began to +paraphrase him: "Wow! Ginger! The spice that makes rotten meat +taste good!" "Say! Why don't we find some dog that's been run +over and sat in the sun for a week and put some <i>ginger</i> +on it for dinner?!" "Right! With a lalaberry shake!" And so on. +This failed to faze JONL; he took it in good humor, as long as we +kept returning to Uncle Gaylord's. He loves ginger honey ice +cream.</p> + +<p>Now RPG and his then-wife KBT (Kathy Tracy) were putting us up +(putting up with us?) in their home for our visit, so to thank +them JONL and I took them out to a nice French restaurant of +their choosing. I unadventurously chose the filet mignon, and KBT +had <i>je ne sais quoi du jour</i>, but RPG and JONL had +<i>lapin</i> (rabbit). (Waitress: "<i>Oui</i>, we have fresh +rabbit, fresh today." RPG: "Well, JONL, I guess we won't need any +<i>ginger</i>!")</p> + +<p>We finished the meal late, about 11 <small>P.M.</small>, which +is 2 <small>A.M</small> Boston time, so JONL and I were rather +droopy. But it wasn't yet midnight. Off to Uncle Gaylord's!</p> + +<p>Now the French restaurant was in Redwood City, north of Palo +Alto. In leaving Redwood City, we somehow got onto route 101 +going north instead of south. JONL and I wouldn't have known the +difference had RPG not mentioned it. We still knew very little of +the local geography. I did figure out, however, that we were +headed in the direction of Berkeley, and half-jokingly suggested +that we continue north and go to Uncle Gaylord's in Berkeley.</p> + +<p>RPG said "Fine!" and we drove on for a while and talked. I was +drowsy, and JONL actually dropped off to sleep for 5 minutes. +When he awoke, RPG said, "Gee, JONL, you must have slept all the +way over the bridge!", referring to the one spanning San +Francisco Bay. Just then we came to a sign that said "University +Avenue". I mumbled something about working our way over to +Telegraph Avenue; RPG said "Right!" and maneuvered some more. +Eventually we pulled up in front of an Uncle Gaylord's.</p> + +<p>Now, I hadn't really been paying attention because I was so +sleepy, and I didn't really understand what was happening until +RPG let me in on it a few moments later, but I was just alert +enough to notice that we had somehow come to the Palo Alto Uncle +Gaylord's after all.</p> + +<p>JONL noticed the resemblance to the Palo Alto store, but +hadn't caught on. (The place is lit with red and yellow lights at +night, and looks much different from the way it does in +daylight.) He said, "This isn't the Uncle Gaylord's I went to in +Berkeley! It looked like a barn! But this place looks <i>just +like</i> the one back in Palo Alto!"</p> + +<p>RPG deadpanned, "Well, this is the one <i>I</i> always come +to when I'm in Berkeley. They've got two in San Francisco, too. +Remember, they're a chain."</p> + +<p>JONL accepted this bit of wisdom. And he was not totally +ignorant -- he knew perfectly well that University Avenue was in +Berkeley, not far from Telegraph Avenue. What he didn't know was +that there is a completely different University Avenue in Palo +Alto.</p> + +<p>JONL went up to the counter and asked for ginger honey. The +guy at the counter asked whether JONL would like to taste it +first, evidently their standard procedure with that flavor, as +not too many people like it.</p> + +<p>JONL said, "I'm sure I like it. Just give me a cone." The guy +behind the counter insisted that JONL try just a taste first. +"Some people think it tastes like soap." JONL insisted, "Look, I +<i>love</i> ginger. I eat Chinese food. I eat raw ginger roots. +I already went through this hassle with the guy back in Palo +Alto. I <i>know</i> I like that flavor!"</p> + +<p>At the words "back in Palo Alto" the guy behind the counter +got a very strange look on his face, but said nothing. KBT caught +his eye and winked. Through my stupor I still hadn't quite +grasped what was going on, and thought RPG was rolling on the +floor laughing and clutching his stomach just because JONL had +launched into his spiel ("makes rotten meat a dish for princes") +for the forty-third time. At this point, RPG clued me in +fully.</p> + +<p>RPG, KBT, and I retreated to a table, trying to stifle our +chuckles. JONL remained at the counter, talking about ice cream +with the guy b.t.c., comparing Uncle Gaylord's to other ice cream +shops and generally having a good old time.</p> + +<p>At length the g.b.t.c. said, "How's the ginger honey?" JONL +said, "Fine! I wonder what exactly is in it?" Now Uncle Gaylord +publishes all his recipes and even teaches classes on how to make +his ice cream at home. So the g.b.t.c. got out the recipe, and he +and JONL pored over it for a while. But the g.b.t.c. could +contain his curiosity no longer, and asked again, "You really +like that stuff, huh?" JONL said, "Yeah, I've been eating it +constantly back in Palo Alto for the past two days. In fact, I +think this batch is about as good as the cones I got back in Palo +Alto!"</p> + +<p>G.b.t.c. looked him straight in the eye and said, "You're +<i>in</i> Palo Alto!"</p> + +<p>JONL turned slowly around, and saw the three of us collapse in +a fit of giggles. He clapped a hand to his forehead and +exclaimed, "I've been hacked!"</p> +</blockquote> + +<p>[My spies on the West Coast inform me that there is a close +relative of the raspberry found out there called an +`ollalieberry' --ESR]</p> + +<p>[Ironic footnote: the <b><a href="#meme">meme</a></b> about +ginger vs. rotting meat is an urban legend. It's not borne out by +an examination of medieval recipes or period purchase records for +spices, and appears full-blown in the works of Samuel Pegge, a +gourmand and notorious flake case who originated numerous food +myths. The truth seems to be that ginger was used to cover not +rot but the extreme salt taste of meat packed in brine, which was +the best method available before refrigeration. --ESR]</p> + +<hr> +Node:<a name="sagan">sagan</a>, Next:<a rel="next" href="#SAIL">SAIL</a>, Previous:<a rel="previous" href="#saga">saga</a>, Up:<a rel="up" href="#chap19">= S =</a> +<br> + + +<p><b>sagan</b> /say'gn/ n.</p> + +<p>[from Carl Sagan's TV series "Cosmos"; think "billions and +billions"] A large quantity of anything. "There's a sagan +different ways to tweak EMACS." "The U.S. Government spends +sagans on bombs and welfare -- hard to say which is more +destructive."</p> + +<hr> +Node:<a name="SAIL">SAIL</a>, Next:<a rel="next" href="#salescritter">salescritter</a>, Previous:<a rel="previous" +href="#sagan">sagan</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>SAIL</b> /sayl/, not /S-A-I-L/ n.</p> + +<p>1. The Stanford Artificial Intelligence Lab. An important site +in the early development of LISP; with the MIT AI Lab, BBN, CMU, +XEROX PARC, and the Unix community, one of the major wellsprings +of technical innovation and hacker-culture traditions (see the +<b><a href="#WAITS">WAITS</a></b> entry for details). The SAIL +machines were shut down in late May 1990, scant weeks after the +MIT AI Lab's ITS cluster was officially decommissioned. 2. The +Stanford Artificial Intelligence Language used at SAIL (sense 1). +It was an Algol-60 derivative with a coroutining facility and +some new data types intended for building search trees and +association lists.</p> + +<hr> +Node:<a name="salescritter">salescritter</a>, Next:<a rel="next" +href="#salt">salt</a>, Previous:<a rel="previous" href="#SAIL">SAIL</a>, Up:<a rel="up" href="#chap19">= S =</a> +<br> + + +<p><b>salescritter</b> /sayls'kri`tr/ n.</p> + +<p>Pejorative hackerism for a computer salesperson. Hackers tell +the following joke:</p> + +<pre> +Q. What's the difference between a used-car dealer and a + computer salesman? +A. The used-car dealer knows he's lying. [Some versions add: + ...and probably knows how to drive.] +</pre> + +<p>This reflects the widespread hacker belief that salescritters +are self-selected for stupidity (after all, if they had brains +and the inclination to use them, they'd be in programming). The +terms `salesthing' and `salesdroid' are also common. Compare +<b><a href="#marketroid">marketroid</a></b>, <b><a href="#suit">suit</a></b>, <b><a href="#droid">droid</a></b>.</p> + +<hr> +Node:<a name="salt">salt</a>, Next:<a rel="next" href="#saltmines">salt mines</a>, Previous:<a rel="previous" href="#salescritter">salescritter</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>salt</b> n.</p> + +<p>A tiny bit of near-random data inserted where too much +regularity would be undesirable; a data <b><a href="#frob">frob</a></b> (sense 1). For example, the Unix crypt(3) +man page mentions that "the salt string is used to perturb the +DES algorithm in one of 4096 different ways."</p> + +<hr> +Node:<a name="saltmines">salt mines</a>, Next:<a rel="next" +href="#saltsubstrate">salt substrate</a>, Previous:<a rel="previous" href="#salt">salt</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>salt mines</b> n.</p> + +<p>Dense quarters housing large numbers of programmers working +long hours on grungy projects, with some hope of seeing the end +of the tunnel in N years. Noted for their absence of sunshine. +Compare <b><a href="#playpen">playpen</a></b>, <b><a href="#sandbox">sandbox</a></b>.</p> + +<hr> +Node:<a name="saltsubstrate">salt substrate</a>, Next:<a rel="next" href="#samedayservice">same-day service</a>, +Previous:<a rel="previous" href="#saltmines">salt mines</a>, +Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>salt substrate</b> n.</p> + +<p>[MIT] Collective noun used to refer to potato chips, pretzels, +saltines, or any other form of snack food designed primarily as a +carrier for sodium chloride. Also `sodium substrate'. From the +technical term `chip substrate', used to refer to the silicon on +the top of which the active parts of integrated circuits are +deposited.</p> + +<hr> +Node:<a name="samedayservice">same-day service</a>, Next:<a +rel="next" href="#samizdat">samizdat</a>, Previous:<a rel="previous" href="#saltsubstrate">salt substrate</a>, Up:<a +rel="up" href="#chap19">= S =</a> <br> + + +<p><b>same-day service</b> n.</p> + +<p>Ironic term used to describe long response time, particularly +with respect to <b><a href="#MS-DOS">MS-DOS</a></b> system calls +(which ought to require only a tiny fraction of a second to +execute). Such response time is a major incentive for programmers +to write programs that are not <b><a href="#well-behaved">well-behaved</a></b>. See also <b><a href="#PC-ism">PC-ism</a></b>.</p> + +<hr> +Node:<a name="samizdat">samizdat</a>, Next:<a rel="next" href="#samurai">samurai</a>, Previous:<a rel="previous" href="#samedayservice">same-day service</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>samizdat</b> /sahm-iz-daht/ n.</p> + +<p>[Russian, literally "self publishing"] The process of +disseminating documentation via underground channels. Originally +referred to underground duplication and distribution of banned +books in the Soviet Union; now refers by obvious extension to any +less-than-official promulgation of textual material, esp. rare, +obsolete, or never-formally-published computer documentation. +Samizdat is obviously much easier when one has access to +high-bandwidth networks and high-quality laser printers. Note +that samizdat is properly used only with respect to documents +which contain needed information (see also <b><a href="#hackerethic">hacker ethic</a></b>) but which are for some +reason otherwise unavailable, but <i>not</i> in the context of +documents which are available through normal channels, for which +unauthorized duplication would be unethical copyright violation. +See <b><a href="#LionsBook">Lions Book</a></b> for a +historical example.</p> + +<hr> +Node:<a name="samurai">samurai</a>, Next:<a rel="next" href="#sandbender">sandbender</a>, Previous:<a rel="previous" href="#samizdat">samizdat</a>, Up:<a rel="up" href="#chap19">= +S =</a> <br> + + +<p><b>samurai</b> n.</p> + +<p>A hacker who hires out for legal cracking jobs, snooping for +factions in corporate political fights, lawyers pursuing +privacy-rights and First Amendment cases, and other parties with +legitimate reasons to need an electronic locksmith. In 1991, +mainstream media reported the existence of a loose-knit culture +of samurai that meets electronically on BBS systems, mostly +bright teenagers with personal micros; they have modeled +themselves explicitly on the historical samurai of Japan and on +the "net cowboys" of William Gibson's <b><a href="#cyberpunk">cyberpunk</a></b> novels. Those interviewed claim to +adhere to a rigid ethic of loyalty to their employers and to +disdain the vandalism and theft practiced by criminal crackers as +beneath them and contrary to the hacker ethic; some quote +Miyamoto Musashi's "Book of Five Rings", a classic of historical +samurai doctrine, in support of these principles. See also <b><a +href="#sneaker">sneaker</a></b>, <b><a href="#Stupids">Stupids</a></b>, <b><a href="#socialengineering">social engineering</a></b>, <b><a href="#cracker">cracker</a></b>, <b><a href="#hackerethic">hacker +ethic</a></b>, and <b><a href="#darksidehacker">dark-side +hacker</a></b>.</p> + +<hr> +Node:<a name="sandbender">sandbender</a>, Next:<a rel="next" +href="#sandbox">sandbox</a>, Previous:<a rel="previous" href="#samurai">samurai</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>sandbender</b> n.</p> + +<p>[IBM] A person involved with silicon lithography and the +physical design of chips. Compare <b><a href="#ironmonger">ironmonger</a></b>, <b><a href="#polygonpusher">polygon pusher</a></b>.</p> + +<hr> +Node:<a name="sandbox">sandbox</a>, Next:<a rel="next" href="#sanitycheck">sanity check</a>, Previous:<a rel="previous" +href="#sandbender">sandbender</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>sandbox</b> n.</p> + +<p>1. (also `sandbox, the') Common term for the R&D +department at many software and computer companies (where hackers +in commercial environments are likely to be found). +Half-derisive, but reflects the truth that research is a form of +creative play. Compare <b><a href="#playpen">playpen</a></b>. 2. +Syn. <b><a href="#linkfarm">link farm</a></b>. 3. A controlled +environment within which potentially dangerous programs are run. +Used esp. in reference to Java implementations.</p> + +<hr> +Node:<a name="sanitycheck">sanity check</a>, Next:<a rel="next" href="#Saturdaynightspecial">Saturday-night +special</a>, Previous:<a rel="previous" href="#sandbox">sandbox</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>sanity check</b> n.</p> + +<p>[very common] 1. The act of checking a piece of code (or +anything else, e.g., a Usenet posting) for completely stupid +mistakes. Implies that the check is to make sure the author was +sane when it was written; e.g., if a piece of scientific software +relied on a particular formula and was giving unexpected results, +one might first look at the nesting of parentheses or the coding +of the formula, as a `sanity check', before looking at the more +complex I/O or data structure manipulation routines, much less +the algorithm itself. Compare <b><a href="#realitycheck">reality check</a></b>. 2. A run-time test, +either validating input or ensuring that the program hasn't +screwed up internally (producing an inconsistent value or +state).</p> + +<hr> +Node:<a name="Saturdaynightspecial">Saturday-night +special</a>, Next:<a rel="next" href="#say">say</a>, Previous:<a +rel="previous" href="#sanitycheck">sanity check</a>, Up:<a +rel="up" href="#chap19">= S =</a> <br> + + +<p><b>Saturday-night special</b> n.</p> + +<p>[from police slang for a cheap handgun] A <b><a href="#quick-and-dirty">quick-and-dirty</a></b> program or feature +kluged together during off hours, under a deadline, and in +response to pressure from a <b><a href="#salescritter">salescritter</a></b>. Such hacks are dangerously +unreliable, but all too often sneak into a production release +after insufficient review.</p> + +<hr> +Node:<a name="say">say</a>, Next:<a rel="next" href="#scag">scag</a>, Previous:<a rel="previous" href="#Saturdaynightspecial">Saturday-night special</a>, Up:<a +rel="up" href="#chap19">= S =</a> <br> + + +<p><b>say</b> vt.</p> + +<p>1. To type to a terminal. "To list a directory verbosely, you +have to say <code>ls -l</code>." Tends to imply a <b><a href="#newline">newline</a></b>-terminated command (a `sentence'). 2. +A computer may also be said to `say' things to you, even if it +doesn't have a speech synthesizer, by displaying them on a +terminal in response to your commands. Hackers find it odd that +this usage confuses <b><a href="#mundane">mundane</a></b>s.</p> + +<hr> +Node:<a name="scag">scag</a>, Next:<a rel="next" href="#scanno">scanno</a>, Previous:<a rel="previous" href="#say">say</a>, Up:<a rel="up" href="#chap19">= S =</a> +<br> + + +<p><b>scag</b> vt.</p> + +<p>To destroy the data on a disk, either by corrupting the +filesystem or by causing media damage. "That last power hit +scagged the system disk." Compare <b><a href="#scrog">scrog</a></b>, <b><a href="#roach">roach</a></b>.</p> + +<hr> +Node:<a name="scanno">scanno</a>, Next:<a rel="next" href="#scarydevilmonastery">scary devil monastery</a>, +Previous:<a rel="previous" href="#scag">scag</a>, Up:<a rel="up" +href="#chap19">= S =</a> <br> + + +<p><b>scanno</b> /skan'oh/ n.</p> + +<p>An error in a document caused by a scanner glitch, analogous +to a typo or <b><a href="#thinko">thinko</a></b>.</p> + +<hr> +Node:<a name="scarydevilmonastery">scary devil +monastery</a>, Next:<a rel="next" href="#schroedinbug">schroedinbug</a>, Previous:<a rel="previous" +href="#scanno">scanno</a>, Up:<a rel="up" href="#chap19">= +S =</a> <br> + + +<p><b>scary devil monastery</b> n.</p> + +<p>Anagram frequently used to refer to the newsgroup +<i>alt.sysadmin.recovery</i>, which is populated with characters +that rather justify the reference.</p> + +<hr> +Node:<a name="schroedinbug">schroedinbug</a>, Next:<a rel="next" +href="#science-fictionfandom">science-fiction fandom</a>, +Previous:<a rel="previous" href="#scarydevilmonastery">scary devil monastery</a>, Up:<a +rel="up" href="#chap19">= S =</a> <br> + + +<p><b>schroedinbug</b> /shroh'din-buhg/ n.</p> + +<p>[MIT: from the Schroedinger's Cat thought-experiment in +quantum physics] A design or implementation bug in a program that +doesn't manifest until someone reading source or using the +program in an unusual way notices that it never should have +worked, at which point the program promptly stops working for +everybody until fixed. Though (like <b><a href="#bitrot">bit +rot</a></b>) this sounds impossible, it happens; some programs +have harbored latent schroedinbugs for years. Compare <b><a href="#heisenbug">heisenbug</a></b>, <b><a href="#Bohrbug">Bohr +bug</a></b>, <b><a href="#mandelbug">mandelbug</a></b>.</p> + +<hr> +Node:<a name="science-fictionfandom">science-fiction +fandom</a>, Next:<a rel="next" href="#scramswitch">scram +switch</a>, Previous:<a rel="previous" href="#schroedinbug">schroedinbug</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>science-fiction fandom</b> n.</p> + +<p>Another voluntary subculture having a very heavy overlap with +hackerdom; most hackers read SF and/or fantasy fiction avidly, +and many go to `cons' (SF conventions) or are involved in +fandom-connected activities such as the Society for Creative +Anachronism. Some hacker jargon originated in SF fandom; see +<b><a href="#defenestration">defenestration</a></b>, <b><a href="#great-wall">great-wall</a></b>, <b><a href="#cyberpunk">cyberpunk</a></b>, <b><a href="#h">h</a></b>, <b><a +href="#hahaonlyserious">ha ha only serious</a></b>, +<b><a href="#IMHO">IMHO</a></b>, <b><a href="#mundane">mundane</a></b>, <b><a href="#neep-neep">neep-neep</a></b>, <b><a href="#RealSoonNow">Real Soon Now</a></b>. Additionally, the +jargon terms <b><a href="#cowboy">cowboy</a></b>, <b><a href="#cyberspace">cyberspace</a></b>, <b><a href="#de-rezz">de-rezz</a></b>, <b><a href="#goflatline">go +flatline</a></b>, <b><a href="#ice">ice</a></b>, <b><a href="#phage">phage</a></b>, <b><a href="#virus">virus</a></b>, <b><a +href="#wetware">wetware</a></b>, <b><a href="#wirehead">wirehead</a></b>, and <b><a href="#worm">worm</a></b> +originated in SF stories.</p> + +<hr> +Node:<a name="scramswitch">scram switch</a>, Next:<a rel="next" href="#scratch">scratch</a>, Previous:<a rel="previous" +href="#science-fictionfandom">science-fiction fandom</a>, +Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>scram switch</b> n.</p> + +<p>[from the nuclear power industry] An emergency-power-off +switch (see <b><a href="#BigRedSwitch">Big Red +Switch</a></b>), esp. one positioned to be easily hit by +evacuating personnel. In general, this is <i>not</i> something +you <b><a href="#frob">frob</a></b> lightly; these often initiate +expensive events (such as Halon dumps) and are installed in a +<b><a href="#dinosaurpen">dinosaur pen</a></b> for use in case +of electrical fire or in case some luckless <b><a href="#fieldservoid">field servoid</a></b> should put 120 volts +across himself while <b><a href="#Easteregging">Easter +egging</a></b>. (See also <b><a href="#molly-guard">molly-guard</a></b>, <b><a href="#TMRC">TMRC</a></b>.)</p> + +<p>A correspondent reports a legend that "Scram" is an acronym +for "Start Cutting Right Away, Man" (another less plausible +variant of this legend refers to "Safety Control Rod Axe Man"; +these are almost certainly both <b><a href="#backronym">backronym</a></b>s). The story goes that in the +earliest nuclear power experiments the engineers recognized the +possibility that the reactor wouldn't behave exactly as predicted +by their mathematical models. Accordingly, they made sure that +they had mechanisms in place that would rapidly drop the control +rods back into the reactor. One mechanism took the form of `scram +technicians'. These individuals stood next to the ropes or cables +that raised and lowered the control rods. Equipped with axes or +cable-cutters, these technicians stood ready for the (literal) +`scram' command. If necessary, they would cut the cables, and +gravity would expeditiously return the control rods to the +reactor, thereby averting yet another kind of <b><a href="#coredump">core dump</a></b>.</p> + +<p>Modern reactor control rods are held in place with claw-like +devices, held closed by current. SCRAM switches are circuit +breakers that immediately open the circuit to the rod arms, +resulting in the rapid insertion and subsequent bottoming of the +control rods.</p> + +<hr> +Node:<a name="scratch">scratch</a>, Next:<a rel="next" href="#scratchmonkey">scratch monkey</a>, Previous:<a rel="previous" href="#scramswitch">scram switch</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>scratch</b></p> + +<p>1. [from `scratchpad'] adj. Describes a data structure or +recording medium attached to a machine for testing or +temporary-use purposes; one that can be <b><a href="#scribble">scribble</a></b>d on without loss. Usually in the +combining forms `scratch memory', `scratch register', `scratch +disk', `scratch tape', `scratch volume'. See also <b><a href="#scratchmonkey">scratch monkey</a></b>. 2. [primarily IBM] +vt. To delete (as in a file).</p> + +<hr> +Node:<a name="scratchmonkey">scratch monkey</a>, Next:<a rel="next" href="#screamanddie">scream and die</a>, Previous:<a +rel="previous" href="#scratch">scratch</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>scratch monkey</b> n.</p> + +<p>As in "Before testing or reconfiguring, always mount a <b><a +href="#scratchmonkey">scratch monkey</a></b>", a proverb used +to advise caution when dealing with irreplaceable data or +devices. Used to refer to any scratch volume hooked to a computer +during any risky operation as a replacement for some precious +resource or data that might otherwise get trashed.</p> + +<p>This term preserves the memory of Mabel, the Swimming Wonder +Monkey, star of a biological research program at the University +of Toronto. Mabel was not (so the legend goes) your ordinary +monkey; the university had spent years teaching her how to swim, +breathing through a regulator, in order to study the effects of +different gas mixtures on her physiology. Mabel suffered an +untimely demise one day when a <b><a href="#DEC">DEC</a></b> +<b><a href="#fieldcircus">field circus</a></b> engineer +troubleshooting a crash on the program's VAX inadvertently +interfered with some custom hardware that was wired to Mabel.</p> + +<p>It is reported that, after calming down an understandably +irate customer sufficiently to ascertain the facts of the matter, +a DEC troubleshooter called up the <b><a href="#fieldcircus">field circus</a></b> manager responsible and +asked him sweetly, "Can you swim?"</p> + +<p>Not all the consequences to humans were so amusing; the sysop +of the machine in question was nearly thrown in jail at the +behest of certain clueless <b><a href="#droid">droid</a></b>s at +the local `humane' society. The moral is clear: When in doubt, +always mount a scratch monkey.</p> + +<p>[The actual incident occured in 1979 or 1980. There is a +version of this story, complete with reported dialogue between +one of the project people and DEC field service, that has been +circulating on Internet since 1986. It is hilarious and mythic, +but gets some facts wrong. For example, it reports the machine as +a PDP-11 and alleges that Mabel's demise occurred when DEC <b><a +href="#PM">PM</a></b>ed the machine. Earlier versions of this +entry were based on that story; this one has been corrected from +an interview with the hapless sysop. --ESR]</p> + +<hr> +Node:<a name="screamanddie">scream and die</a>, Next:<a +rel="next" href="#screamingtty">screaming tty</a>, Previous:<a +rel="previous" href="#scratchmonkey">scratch monkey</a>, Up:<a +rel="up" href="#chap19">= S =</a> <br> + + +<p><b>scream and die</b> v.</p> + +<p>Syn. <b><a href="#coughanddie">cough and die</a></b>, +but connotes that an error message was printed or displayed +before the program crashed.</p> + +<hr> +Node:<a name="screamingtty">screaming tty</a>, Next:<a rel="next" href="#screen">screen</a>, Previous:<a rel="previous" +href="#screamanddie">scream and die</a>, Up:<a rel="up" +href="#chap19">= S =</a> <br> + + +<p><b>screaming tty</b> n.</p> + +<p>[Unix] A terminal line which spews an infinite number of +random characters at the operating system. This can happen if the +terminal is either disconnected or connected to a powered-off +terminal but still enabled for login; misconfiguration, +misimplementation, or simple bad luck can start such a terminal +screaming. A screaming tty or two can seriously degrade the +performance of a vanilla Unix system; the arriving "characters" +are treated as userid/password pairs and tested as such. The Unix +password encryption algorithm is designed to be computationally +intensive in order to foil brute-force crack attacks, so although +none of the logins succeeds; the overhead of rejecting them all +can be substantial.</p> + +<hr> +Node:<a name="screen">screen</a>, Next:<a rel="next" href="#screenname">screen name</a>, Previous:<a rel="previous" +href="#screamingtty">screaming tty</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>screen</b> n.</p> + +<p>[Atari ST <b><a href="#demoscene">demoscene</a></b>] One <b><a +href="#demoeffect">demoeffect</a></b> or one screenful of them. +Probably comes from old Sierra-style adventures or shoot-em-ups +where one travels from one place to another one screenful at a +time.</p> + +<hr> +Node:<a name="screenname">screen name</a>, Next:<a rel="next" +href="#screw">screw</a>, Previous:<a rel="previous" href="#screen">screen</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>screen name</b> n.</p> + +<p>A <b><a href="#handle">handle</a></b> sense 1. This term has +been common among users of IRC, MUDs, and commercial on-line +services since the mid-1990s. Hackers recognize the term but +don't generally use it.</p> + +<hr> +Node:<a name="screw">screw</a>, Next:<a rel="next" href="#screwage">screwage</a>, Previous:<a rel="previous" href="#screenname">screen name</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>screw</b> n.</p> + +<p>[MIT] A <b><a href="#lose">lose</a></b>, usually in software. +Especially used for user-visible misbehavior caused by a bug or +misfeature. This use has become quite widespread outside MIT.</p> + +<hr> +Node:<a name="screwage">screwage</a>, Next:<a rel="next" href="#scribble">scribble</a>, Previous:<a rel="previous" href="#screw">screw</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>screwage</b> /skroo'*j/ n.</p> + +<p>Like <b><a href="#lossage">lossage</a></b> but connotes that +the failure is due to a designed-in misfeature rather than a +simple inadequacy or a mere bug.</p> + +<hr> +Node:<a name="scribble">scribble</a>, Next:<a rel="next" href="#scriptkiddies">script kiddies</a>, Previous:<a rel="previous" href="#screwage">screwage</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>scribble</b> n.</p> + +<p>To modify a data structure in a random and unintentionally +destructive way. "Bletch! Somebody's disk-compactor program went +berserk and scribbled on the i-node table." "It was working fine +until one of the allocation routines scribbled on low core." +Synonymous with <b><a href="#trash">trash</a></b>; compare <b><a +href="#mung">mung</a></b>, which conveys a bit more intention, +and <b><a href="#mangle">mangle</a></b>, which is more violent +and final.</p> + +<hr> +Node:<a name="scriptkiddies">script kiddies</a>, Next:<a rel="next" href="#scrog">scrog</a>, Previous:<a rel="previous" href="#scribble">scribble</a>, Up:<a rel="up" href="#chap19">= +S =</a> <br> + + +<p><b>script kiddies</b> pl.n.</p> + +<p>1. The lowest form of <b><a href="#cracker">cracker</a></b>; +script kiddies do mischief with scripts and programs written by +others, often without understanding the <b><a href="#exploit">exploit</a></b>. 2. People who cannot program, but who +create tacky HTML pages by copying JavaScript routines from other +tacky HTML pages. More generally, a script kiddie writes (or more +likely cuts and pastes) code without either having or desiring to +have a mental model of what the code does; someone who thinks of +code as magical incantations and asks only "what do I need to +type to make this happen?"</p> + +<hr> +Node:<a name="scrog">scrog</a>, Next:<a rel="next" href="#scrool">scrool</a>, Previous:<a rel="previous" href="#scriptkiddies">script kiddies</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>scrog</b> /skrog/ vt.</p> + +<p>[Bell Labs] To damage, trash, or corrupt a data structure. +"The list header got scrogged." Also reported as `skrog', and +ascribed to the comic strip "The Wizard of Id". Compare <b><a +href="#scag">scag</a></b>; possibly the two are related. +Equivalent to <b><a href="#scribble">scribble</a></b> or <b><a +href="#mangle">mangle</a></b>.</p> + +<hr> +Node:<a name="scrool">scrool</a>, Next:<a rel="next" href="#scrozzle">scrozzle</a>, Previous:<a rel="previous" href="#scrog">scrog</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>scrool</b> /skrool/ n.</p> + +<p>[from the pioneering Roundtable chat system in Houston ca. +1984; prob. originated as a typo for `scroll'] The log of old +messages, available for later perusal or to help one get back in +synch with the conversation. It was originally called the `scrool +monster', because an early version of the roundtable software had +a bug where it would dump all 8K of scrool on a user's +terminal.</p> + +<hr> +Node:<a name="scrozzle">scrozzle</a>, Next:<a rel="next" href="#scruffies">scruffies</a>, Previous:<a rel="previous" href="#scrool">scrool</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>scrozzle</b> /skroz'l/ vt.</p> + +<p>Used when a self-modifying code segment runs incorrectly and +corrupts the running program or vital data. "The damn compiler +scrozzled itself again!"</p> + +<hr> +Node:<a name="scruffies">scruffies</a>, Next:<a rel="next" href="#SCSI">SCSI</a>, Previous:<a rel="previous" href="#scrozzle">scrozzle</a>, Up:<a rel="up" href="#chap19">= +S =</a> <br> + + +<p><b>scruffies</b> n.</p> + +<p>See <b><a href="#neatsvsscruffies">neats vs. +scruffies</a></b>.</p> + +<hr> +Node:<a name="SCSI">SCSI</a>, Next:<a rel="next" href="#ScumOS">ScumOS</a>, Previous:<a rel="previous" href="#scruffies">scruffies</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>SCSI</b> n.</p> + +<p>[Small Computer System Interface] A bus-independent standard +for system-level interfacing between a computer and intelligent +devices. Typically annotated in literature with `sexy' +(/sek'see/), `sissy' (/sis'ee/), and `scuzzy' (/skuh'zee/) as +pronunciation guides -- the last being the overwhelmingly +predominant form, much to the dismay of the designers and their +marketing people. One can usually assume that a person who +pronounces it /S-C-S-I/ is clueless.</p> + +<hr> +Node:<a name="ScumOS">ScumOS</a>, Next:<a rel="next" href="#searchanddestroymode">search-and-destroy mode</a>, +Previous:<a rel="previous" href="#SCSI">SCSI</a>, Up:<a rel="up" +href="#chap19">= S =</a> <br> + + +<p><b>ScumOS</b> /skuhm'os/ or /skuhm'O-S/ n.</p> + +<p>Unflattering hackerism for SunOS, the BSD Unix variant +supported on Sun Microsystems's Unix workstations (see also <b><a +href="#sun-stools">sun-stools</a></b>), and compare <b><a href="#AIDX">AIDX</a></b>, <b><a href="#Macintrash">Macintrash</a></b>, <b><a href="#NominalSemidestructor">Nominal Semidestructor</a></b>, <b><a +href="#HP-SUX">HP-SUX</a></b>. Despite what this term might +suggest, Sun was founded by hackers and still enjoys excellent +relations with hackerdom; usage is more often in exasperation +than outright loathing.</p> + +<hr> +Node:<a name="searchanddestroymode">search-and-destroy +mode</a>, Next:<a rel="next" href="#second-systemeffect">second-system effect</a>, Previous:<a +rel="previous" href="#ScumOS">ScumOS</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>search-and-destroy mode</b> n.</p> + +<p>Hackerism for a noninteractive search-and-replace facility in +an editor, so called because an incautiously chosen match pattern +can cause <b><a href="#infinite">infinite</a></b> damage.</p> + +<hr> +Node:<a name="second-systemeffect">second-system effect</a>, +Next:<a rel="next" href="#secondarydamage">secondary +damage</a>, Previous:<a rel="previous" href="#searchanddestroymode">search-and-destroy mode</a>, Up:<a +rel="up" href="#chap19">= S =</a> <br> + + +<p><b>second-system effect</b> n.</p> + +<p>(sometimes, more euphoniously, `second-system syndrome') When +one is designing the successor to a relatively small, elegant, +and successful system, there is a tendency to become grandiose in +one's success and design an <b><a href="#elephantine">elephantine</a></b> feature-laden monstrosity. The +term was first used by Fred Brooks in his classic "The Mythical +Man-Month: Essays on Software Engineering" (Addison-Wesley, 1975; +ISBN 0-201-00650-2). It described the jump from a set of nice, +simple operating systems on the IBM 70xx series to OS/360 on the +360 series. A similar effect can also happen in an evolving +system; see <b><a href="#BrookssLaw">Brooks's Law</a></b>, +<b><a href="#creepingelegance">creeping elegance</a></b>, +<b><a href="#creepingfeaturism">creeping featurism</a></b>. +See also <b><a href="#Multics">Multics</a></b>, <b><a href="#OSslash2">OS/2</a></b>, <b><a href="#X">X</a></b>, <b><a href="#softwarebloat">software bloat</a></b>.</p> + +<p>This version of the jargon lexicon has been described (with +altogether too much truth for comfort) as an example of +second-system effect run amok on jargon-1<small>...</small>.</p> + +<hr> +Node:<a name="secondarydamage">secondary damage</a>, Next:<a +rel="next" href="#securitythroughobscurity">security +through obscurity</a>, Previous:<a rel="previous" href="#second-systemeffect">second-system effect</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>secondary damage</b> n.</p> + +<p>When a fatal error occurs (esp. a <b><a href="#segfault">segfault</a></b>) the immediate cause may be that a +pointer has been trashed due to a previous <b><a href="#fandangooncore">fandango on core</a></b>. However, this +fandango may have been due to an <i>earlier</i> fandango, so no +amount of analysis will reveal (directly) how the damage +occurred. "The data structure was clobbered, but it was secondary +damage."</p> + +<p>By extension, the corruption resulting from N cascaded +fandangoes on core is `Nth-level damage'. There is at least one +case on record in which 17 hours of <b><a href="#grovel">grovel</a></b>ling with <code>adb</code> actually dug +up the underlying bug behind an instance of seventh-level damage! +The hacker who accomplished this near-superhuman feat was +presented with an award by his fellows.</p> + +<hr> +Node:<a name="securitythroughobscurity">security through +obscurity</a>, Next:<a rel="next" href="#SED">SED</a>, +Previous:<a rel="previous" href="#secondarydamage">secondary +damage</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>security through obscurity</b></p> + +<p>(alt. `security by obscurity') A term applied by hackers to +most OS vendors' favorite way of coping with security holes -- +namely, ignoring them, documenting neither any known holes nor +the underlying security algorithms, trusting that nobody will +find out about them and that people who do find out about them +won't exploit them. This "strategy" never works for long and +occasionally sets the world up for debacles like the <b><a href="#RTM">RTM</a></b> worm of 1988 (see <b><a href="#GreatWorm">Great Worm</a></b>), but once the brief moments +of panic created by such events subside most vendors are all too +willing to turn over and go back to sleep. After all, actually +fixing the bugs would siphon off the resources needed to +implement the next user-interface frill on marketing's wish list +-- and besides, if they started fixing security bugs customers +might begin to <i>expect</i> it and imagine that their +warranties of merchantability gave them some sort of +<i>right</i> to a system with fewer holes in it than a +shotgunned Swiss cheese, and <i>then</i> where would we be?</p> + +<p>Historical note: There are conflicting stories about the +origin of this term. It has been claimed that it was first used +in the Usenet newsgroup in <i>comp.sys.apollo</i> during a +campaign to get HP/Apollo to fix security problems in its +Unix-<b><a href="#clone">clone</a></b> Aegis/DomainOS (they +didn't change a thing). <b><a href="#ITS">ITS</a></b> fans, on +the other hand, say it was coined years earlier in opposition to +the incredibly paranoid <b><a href="#Multics">Multics</a></b> +people down the hall, for whom security was everything. In the +ITS culture it referred to (1) the fact that by the time a +tourist figured out how to make trouble he'd generally gotten +over the urge to make it, because he felt part of the community; +and (2) (self-mockingly) the poor coverage of the documentation +and obscurity of many commands. One instance of +<i>deliberate</i> security through obscurity is recorded; the +command to allow patching the running ITS system (escape escape +control-R) echoed as $$^D. If you actually typed alt alt ^D, that +set a flag that would prevent patching the system even if you +later got it right.</p> + +<hr> +Node:<a name="SED">SED</a>, Next:<a rel="next" href="#segfault">segfault</a>, Previous:<a rel="previous" href="#securitythroughobscurity">security through obscurity</a>, +Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>SED</b> /S-E-D/ n.</p> + +<p>[TMRC, from `Light-Emitting Diode'] Smoke-emitting diode. A +<b><a href="#friode">friode</a></b> that lost the war. See also +<b><a href="#LER">LER</a></b>.</p> + +<hr> +Node:<a name="segfault">segfault</a>, Next:<a rel="next" href="#seggie">seggie</a>, Previous:<a rel="previous" href="#SED">SED</a>, Up:<a rel="up" href="#chap19">= S =</a> +<br> + + +<p><b>segfault</b> n.,vi.</p> + +<p>Syn. <b><a href="#segment">segment</a></b>, <b><a href="#segmentationfault">segmentation fault</a></b>.</p> + +<hr> +Node:<a name="seggie">seggie</a>, Next:<a rel="next" href="#segment">segment</a>, Previous:<a rel="previous" href="#segfault">segfault</a>, Up:<a rel="up" href="#chap19">= +S =</a> <br> + + +<p><b>seggie</b> /seg'ee/ n.</p> + +<p>[Unix] Shorthand for <b><a href="#segmentationfault">segmentation fault</a></b> reported from +Britain.</p> + +<hr> +Node:<a name="segment">segment</a>, Next:<a rel="next" href="#segmentationfault">segmentation fault</a>, Previous:<a rel="previous" href="#seggie">seggie</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>segment</b> /seg'ment/ vi.</p> + +<p>To experience a <b><a href="#segmentationfault">segmentation fault</a></b>. Confusingly, +this is often pronounced more like the noun `segment' than like +mainstream v. segment; this is because it is actually a noun +shorthand that has been verbed.</p> + +<hr> +Node:<a name="segmentationfault">segmentation fault</a>, +Next:<a rel="next" href="#segv">segv</a>, Previous:<a rel="previous" href="#segment">segment</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>segmentation fault</b> n.</p> + +<p>[Unix] 1. [techspeak] An error in which a running program +attempts to access memory not allocated to it and <b><a href="#coredump">core dump</a></b>s with a segmentation violation +error. This is often caused by improper usage of pointers in the +source code, dereferencing a null pointer, or (in C) +inadvertently using a non-pointer variable as a pointer. The +classic example is:</p> + +<pre> + int i; + scanf ("%d", i); /* should have used &i */ +</pre> + +<br> +<p>2. To lose a train of thought or a line of reasoning. Also +uttered as an exclamation at the point of befuddlement.</p> + +<hr> +Node:<a name="segv">segv</a>, Next:<a rel="next" href="#self-reference">self-reference</a>, Previous:<a rel="previous" +href="#segmentationfault">segmentation fault</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>segv</b> /seg'vee/ n.,vi.</p> + +<p>Yet another synonym for <b><a href="#segmentationfault">segmentation fault</a></b> (actually, in +this case, `segmentation violation').</p> + +<hr> +Node:<a name="self-reference">self-reference</a>, Next:<a rel="next" href="#selvage">selvage</a>, Previous:<a rel="previous" +href="#segv">segv</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>self-reference</b> n.</p> + +<p>See <b><a href="#self-reference">self-reference</a></b>.</p> + +<hr> +Node:<a name="selvage">selvage</a>, Next:<a rel="next" href="#semi">semi</a>, Previous:<a rel="previous" href="#self-reference">self-reference</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>selvage</b> /sel'v*j/ n.</p> + +<p>[from sewing and weaving] See <b><a href="#chad">chad</a></b> +(sense 1).</p> + +<hr> +Node:<a name="semi">semi</a>, Next:<a rel="next" href="#semi-automated">semi-automated</a>, Previous:<a rel="previous" +href="#selvage">selvage</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>semi</b> /se'mee/ or /se'mi:/</p> + +<p>1. n. Abbreviation for `semicolon', when speaking. "Commands +to <b><a href="#grind">grind</a></b> are prefixed by +semi-semi-star" means that the prefix is <code>;;*</code>, not +1/4 of a star. 2. A prefix used with words such as `immediately' +as a qualifier. "When is the system coming up?" +"Semi-immediately." (That is, maybe not for an hour.) "We did +consider that possibility semi-seriously." See also <b><a href="#infinite">infinite</a></b>.</p> + +<hr> +Node:<a name="semi-automated">semi-automated</a>, Next:<a rel="next" href="#semi-infinite">semi-infinite</a>, Previous:<a rel="previous" href="#semi">semi</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>semi-automated</b> adj.</p> + +<p>[US Geological Survey] A procedure that has yet to be +completely automated; it still requires a smidge of clueful human +interaction. Semi-automated programs usually come with +written-out operator instructions that are worth their weight in +gold - without them, very nasty things can happen. At USGS +semi-automated programs are often referred to as "semi-automated +weapons".</p> + +<hr> +Node:<a name="semi-infinite">semi-infinite</a>, Next:<a rel="next" href="#seniorbit">senior bit</a>, Previous:<a rel="previous" href="#semi-automated">semi-automated</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>semi-infinite</b> n.</p> + +<p>See <b><a href="#infinite">infinite</a></b>.</p> + +<hr> +Node:<a name="seniorbit">senior bit</a>, Next:<a rel="next" +href="#Septemberthatneverended">September that never +ended</a>, Previous:<a rel="previous" href="#semi-infinite">semi-infinite</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>senior bit</b> n.</p> + +<p>[IBM; rare] Syn. <b><a href="#metabit">meta +bit</a></b>.</p> + +<hr> +Node:<a name="Septemberthatneverended">September that +never ended</a>, Next:<a rel="next" href="#server">server</a>, +Previous:<a rel="previous" href="#seniorbit">senior bit</a>, +Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>September that never ended</b></p> + +<p>All time since September 1993. One of the seasonal rhythms of +the Usenet used to be the annual September influx of clueless +newbies who, lacking any sense of <b><a href="#netiquette">netiquette</a></b>, made a general nuisance of +themselves. This coincided with people starting college, getting +their first internet accounts, and plunging in without bothering +to learn what was acceptable. These relatively small drafts of +newbies could be assimilated within a few months. But in +September 1993, AOL users became able to post to Usenet, nearly +overwhelming the old-timers' capacity to acculturate them; to +those who nostalgically recall the period before hand, this +triggered an inexorable decline in the quality of discussions on +newsgroups. See also <b><a href="#AOLexcl">AOL!</a></b>.</p> + +<hr> +Node:<a name="server">server</a>, Next:<a rel="next" href="#SEX">SEX</a>, Previous:<a rel="previous" href="#Septemberthatneverended">September that never +ended</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>server</b> n.</p> + +<p>A kind of <b><a href="#daemon">daemon</a></b> that performs a +service for the requester and which often runs on a computer +other than the one on which the server runs. A particularly +common term on the Internet, which is rife with `web servers', +`name servers', `domain servers', `news servers', `finger +servers', and the like.</p> + +<hr> +Node:<a name="SEX">SEX</a>, Next:<a rel="next" href="#sexchanger">sex changer</a>, Previous:<a rel="previous" +href="#server">server</a>, Up:<a rel="up" href="#chap19">= +S =</a> <br> + + +<p><b>SEX</b> /seks/</p> + +<p>[Sun Users' Group & elsewhere] n. 1. Software EXchange. A +technique invented by the blue-green algae hundreds of millions +of years ago to speed up their evolution, which had been terribly +slow up until then. Today, SEX parties are popular among hackers +and others (of course, these are no longer limited to exchanges +of genetic software). In general, SEX parties are a <b><a href="#GoodThing">Good Thing</a></b>, but unprotected SEX can +propagate a <b><a href="#virus">virus</a></b>. See also <b><a +href="#pubicdirectory">pubic directory</a></b>. 2. The rather +Freudian mnemonic often used for Sign EXtend, a machine +instruction found in the PDP-11 and many other architectures. The +RCA 1802 chip used in the early Elf and SuperElf personal +computers had a `SEt X register' SEX instruction, but this seems +to have had little folkloric impact. The Data General instruction +set also had <code>SEX</code>.</p> + +<p><b><a href="#DEC">DEC</a></b>'s engineers nearly got a PDP-11 +assembler that used the <code>SEX</code> mnemonic out the door at +one time, but (for once) marketing wasn't asleep and forced a +change. That wasn't the last time this happened, either. The +author of "The Intel 8086 Primer", who was one of the original +designers of the 8086, noted that there was originally a +<code>SEX</code> instruction on that processor, too. He says that +Intel management got cold feet and decreed that it be changed, +and thus the instruction was renamed <code>CBW</code> and +<code>CWD</code> (depending on what was being extended). +Amusingly, the Intel 8048 (the microcontroller used in IBM PC +keyboards) is also missing straight <code>SEX</code> but has +logical-or and logical-and instructions <code>ORL</code> and +<code>ANL</code>.</p> + +<p>The Motorola 6809, used in the Radio Shack Color Computer and +in U.K.'s `Dragon 32' personal computer, actually had an official +<code>SEX</code> instruction; the 6502 in the Apple II with which +it competed did not. British hackers thought this made perfect +mythic sense; after all, it was commonly observed, you could (on +some theoretical level) have sex with a dragon, but you can't +have sex with an apple.</p> + +<hr> +Node:<a name="sexchanger">sex changer</a>, Next:<a rel="next" +href="#shamboliclink">shambolic link</a>, Previous:<a rel="previous" href="#SEX">SEX</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>sex changer</b> n.</p> + +<p>Syn. <b><a href="#gendermender">gender mender</a></b>.</p> + +<hr> +Node:<a name="shamboliclink">shambolic link</a>, Next:<a rel="next" href="#sharfile">shar file</a>, Previous:<a rel="previous" href="#sexchanger">sex changer</a>, Up:<a rel="up" +href="#chap19">= S =</a> <br> + + +<p><b>shambolic link</b> /sham-bol'ik link/ n.</p> + +<p>A Unix symbolic link, particularly when it confuses you, +points to nothing at all, or results in your ending up in some +completely unexpected part of the +filesystem<small>...</small>.</p> + +<hr> +Node:<a name="sharfile">shar file</a>, Next:<a rel="next" +href="#sharchive">sharchive</a>, Previous:<a rel="previous" href="#shamboliclink">shambolic link</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>shar file</b> /shar' fi:l/ n.</p> + +<p>Syn. <b><a href="#sharchive">sharchive</a></b>.</p> + +<hr> +Node:<a name="sharchive">sharchive</a>, Next:<a rel="next" href="#Shareandenjoy">Share and enjoy!</a>, Previous:<a rel="previous" href="#sharfile">shar file</a>, Up:<a rel="up" +href="#chap19">= S =</a> <br> + + +<p><b>sharchive</b> /shar'ki:v/ n.</p> + +<p>[Unix and Usenet; from /bin/sh archive] A <b><a href="#flatten">flatten</a></b>ed representation of a set of one or +more files, with the unique property that it can be unflattened +(the original files restored) by feeding it through a standard +Unix shell; thus, a sharchive can be distributed to anyone +running Unix, and no special unpacking software is required. +Sharchives are also intriguing in that they are typically created +by shell scripts; the script that produces sharchives is thus a +script which produces self-unpacking scripts, which may +themselves contain scripts. (The downsides of sharchives are that +they are an ideal venue for <b><a href="#Trojanhorse">Trojan +horse</a></b> attacks and that, for recipients not running Unix, +no simple un-sharchiving program is possible; sharchives can and +do make use of arbitrarily-powerful shell features.) Sharchives +are also commonly referred to as `shar files' after the name of +the most common program for generating them.</p> + +<hr> +Node:<a name="Shareandenjoy">Share and enjoy!</a>, Next:<a +rel="next" href="#shareware">shareware</a>, Previous:<a rel="previous" href="#sharchive">sharchive</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>Share and enjoy!</b> imp.</p> + +<p>1. Commonly found at the end of software release announcements +and <b><a href="#READMEfile">README file</a></b>s, this phrase +indicates allegiance to the hacker ethic of free information +sharing (see <b><a href="#hackerethic">hacker ethic</a></b>, +sense 1). 2. The motto of the complaints division of Sirius +Cybernetics Corporation (the ultimate gaggle of incompetent <b><a +href="#suit">suit</a></b>s) in Douglas Adams's "Hitch Hiker's +Guide to the Galaxy". The irony of using this as a cultural +recognition signal appeals to hackers.</p> + +<hr> +Node:<a name="shareware">shareware</a>, Next:<a rel="next" href="#sharingviolation">sharing violation</a>, Previous:<a rel="previous" href="#Shareandenjoy">Share and enjoy!</a>, +Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>shareware</b> /sheir'weir/ n.</p> + +<p>A kind of <b><a href="#freeware">freeware</a></b> (sense 1) +for which the author requests some payment, usually in the +accompanying documentation files or in an announcement made by +the software itself. Such payment may or may not buy additional +support or functionality. See also <b><a href="#careware">careware</a></b>, <b><a href="#charityware">charityware</a></b>, <b><a href="#crippleware">crippleware</a></b>, <b><a href="#FRS">FRS</a></b>, <b><a href="#guiltware">guiltware</a></b>, +<b><a href="#postcardware">postcardware</a></b>, and <b><a href="#-ware">-ware</a></b>; compare <b><a href="#payware">payware</a></b>.</p> + +<hr> +Node:<a name="sharingviolation">sharing violation</a>, Next:<a +rel="next" href="#shebang">shebang</a>, Previous:<a rel="previous" href="#shareware">shareware</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>sharing violation</b></p> + +<p>[From a file error common to several <b><a href="#OS">OS</a></b>s] A response to receiving information, typically +of an excessively personal nature, that you were probably happier +not knowing. "You know those little noises that Pat makes in +bed..?" "Whoa! Sharing violation!" In contrast to the original +file error, which indicated that you were <i>not</i> being +given data that you <i>did</i> want.</p> + +<hr> +Node:<a name="shebang">shebang</a>, Next:<a rel="next" href="#shelfware">shelfware</a>, Previous:<a rel="previous" href="#sharingviolation">sharing violation</a>, Up:<a rel="up" +href="#chap19">= S =</a> <br> + + +<p><b>shebang</b> /sh*-bang/ n.</p> + +<p>The character sequence "#!" that frequently begins executable +shell scripts under Unix. Probably derived from "shell bang" +under the influence of American slang "the whole shebang" +(everything, the works).</p> + +<hr> +Node:<a name="shelfware">shelfware</a>, Next:<a rel="next" href="#shell">shell</a>, Previous:<a rel="previous" href="#shebang">shebang</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>shelfware</b> /shelf'weir/ n.</p> + +<p>Software purchased on a whim (by an individual user) or in +accordance with policy (by a corporation or government agency), +but not actually required for any particular use. Therefore, it +often ends up on some shelf.</p> + +<hr> +Node:<a name="shell">shell</a>, Next:<a rel="next" href="#shellout">shell out</a>, Previous:<a rel="previous" href="#shelfware">shelfware</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>shell</b> [orig. <b><a href="#Multics">Multics</a></b> +n.</p> + +<p>techspeak, widely propagated via Unix] 1. [techspeak] The +command interpreter used to pass commands to an operating system; +so called because it is the part of the operating system that +interfaces with the outside world. 2. More generally, any +interface program that mediates access to a special resource or +<b><a href="#server">server</a></b> for convenience, efficiency, +or security reasons; for this meaning, the usage is usually `a +shell around' whatever. This sort of program is also called a +`wrapper'. 3. A skeleton program, created by hand or by another +program (like, say, a parser generator), which provides the +necessary <b><a href="#incantation">incantation</a></b>s to set +up some task and the control flow to drive it (the term <b><a +href="#driver">driver</a></b> is sometimes used synonymously). +The user is meant to fill in whatever code is needed to get real +work done. This usage is common in the AI and Microsoft Windows +worlds, and confuses Unix hackers.</p> + +<p>Historical note: Apparently, the original Multics shell (sense +1) was so called because it was a shell (sense 3); it ran user +programs not by starting up separate processes, but by +dynamically linking the programs into its own code, calling them +as subroutines, and then dynamically de-linking them on return. +The VMS command interpreter still does something very like +this.</p> + +<hr> +Node:<a name="shellout">shell out</a>, Next:<a rel="next" +href="#shiftleftorrightlogical">shift left (or +right) logical</a>, Previous:<a rel="previous" href="#shell">shell</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>shell out</b> vi.</p> + +<p>[Unix] To <b><a href="#spawn">spawn</a></b> an interactive +subshell from within a program (e.g., a mailer or editor). "Bang +foo runs foo in a subshell, while bang alone shells out."</p> + +<hr> +Node:<a name="shiftleftorrightlogical">shift left +(or right) logical</a>, Next:<a rel="next" href="#shim">shim</a>, +Previous:<a rel="previous" href="#shellout">shell out</a>, +Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>shift left (or right) logical</b></p> + +<p>[from any of various machines' instruction sets] 1. vi. To +move oneself to the left (right). To move out of the way. 2. +imper. "Get out of that (my) seat! You can shift to that empty +one to the left (right)." Often used without the `logical', or as +`left shift' instead of `shift left'. Sometimes heard as LSH +/lish/, from the <b><a href="#PDP-10">PDP-10</a></b> instruction +set. See <b><a href="#ProgrammersCheer">Programmer's +Cheer</a></b>.</p> + +<hr> +Node:<a name="shim">shim</a>, Next:<a rel="next" href="#shitogram">shitogram</a>, Previous:<a rel="previous" href="#shiftleftorrightlogical">shift left (or right) +logical</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>shim</b> n.</p> + +<p>A small piece of data inserted in order to achieve a desired +memory alignment or other addressing property. For example, the +PDP-11 Unix linker, in split I&D (instructions and data) +mode, inserts a two-byte shim at location 0 in data space so that +no data object will have an address of 0 (and be confused with +the C null pointer). See also <b><a href="#loosebytes">loose +bytes</a></b>.</p> + +<hr> +Node:<a name="shitogram">shitogram</a>, Next:<a rel="next" href="#shortcard">short card</a>, Previous:<a rel="previous" href="#shim">shim</a>, Up:<a rel="up" href="#chap19">= S =</a> +<br> + + +<p><b>shitogram</b> /shit'oh-gram/ n.</p> + +<p>A <i>really</i> nasty piece of email. Compare <b><a href="#nastygram">nastygram</a></b>, <b><a href="#flame">flame</a></b>.</p> + +<hr> +Node:<a name="shortcard">short card</a>, Next:<a rel="next" +href="#shotgundebugging">shotgun debugging</a>, Previous:<a +rel="previous" href="#shitogram">shitogram</a>, Up:<a rel="up" +href="#chap19">= S =</a> <br> + + +<p><b>short card</b> n.</p> + +<p>A half-length IBM XT expansion card or adapter that will fit +in one of the two short slots located towards the right rear of a +standard chassis (tucked behind the floppy disk drives). See also +<b><a href="#tallcard">tall card</a></b>.</p> + +<hr> +Node:<a name="shotgundebugging">shotgun debugging</a>, Next:<a +rel="next" href="#shovelware">shovelware</a>, Previous:<a rel="previous" href="#shortcard">short card</a>, Up:<a rel="up" +href="#chap19">= S =</a> <br> + + +<p><b>shotgun debugging</b> n.</p> + +<p>The software equivalent of <b><a href="#Easteregging">Easter egging</a></b>; the making of +relatively undirected changes to software in the hope that a bug +will be perturbed out of existence. This almost never works, and +usually introduces more bugs.</p> + +<hr> +Node:<a name="shovelware">shovelware</a>, Next:<a rel="next" +href="#showstopper">showstopper</a>, Previous:<a rel="previous" +href="#shotgundebugging">shotgun debugging</a>, Up:<a rel="up" +href="#chap19">= S =</a> <br> + + +<p><b>shovelware</b> /shuh'v*l-weir`/ n.</p> + +<p>1. Extra software dumped onto a CD-ROM or tape to fill up the +remaining space on the medium after the software distribution +it's intended to carry, but not integrated with the distribution. +2. A slipshod compilation of software dumped onto a CD-ROM +without much care for organization or even usability.</p> + +<hr> +Node:<a name="showstopper">showstopper</a>, Next:<a rel="next" +href="#shriek">shriek</a>, Previous:<a rel="previous" href="#shovelware">shovelware</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>showstopper</b> n.</p> + +<p>A hardware or (especially) software bug that makes an +implementation effectively unusable; one that absolutely has to +be fixed before development can go on. Opposite in connotation +from its original theatrical use, which refers to something +stunningly <i>good</i>.</p> + +<hr> +Node:<a name="shriek">shriek</a>, Next:<a rel="next" href="#Shub-Internet">Shub-Internet</a>, Previous:<a rel="previous" +href="#showstopper">showstopper</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>shriek</b> n.</p> + +<p>See <b><a href="#excl">excl</a></b>. Occasional CMU usage, +also in common use among APL fans and mathematicians, especially +category theorists.</p> + +<hr> +Node:<a name="Shub-Internet">Shub-Internet</a>, Next:<a rel="next" href="#sidecar">sidecar</a>, Previous:<a rel="previous" +href="#shriek">shriek</a>, Up:<a rel="up" href="#chap19">= +S =</a> <br> + + +<p><b>Shub-Internet</b> /shuhb' in't*r-net/ n.</p> + +<p>[MUD: from H. P. Lovecraft's evil fictional deity +Shub-Niggurath, the Black Goat with a Thousand Young] The harsh +personification of the Internet: Beast of a Thousand Processes, +Eater of Characters, Avatar of Line Noise, and Imp of Call +Waiting; the hideous multi-tendriled entity formed of all the +manifold connections of the net. A sect of MUDders worships +Shub-Internet, sacrificing objects and praying for good +connections. To no avail -- its purpose is malign and evil, and +is the cause of all network slowdown. Often heard as in "Freela +casts a tac nuke at Shub-Internet for slowing her down." (A +forged response often follows along the lines of: "Shub-Internet +gulps down the tac nuke and burps happily.") Also cursed by users +of the Web, <b><a href="#FTP">FTP</a></b> and <b><a href="#TELNET">TELNET</a></b> when the system slows down. The dread +name of Shub-Internet is seldom spoken aloud, as it is said that +repeating it three times will cause the being to wake, deep +within its lair beneath the Pentagon. Compare <b><a href="#RandomNumberGod">Random Number God</a></b>.</p> + +<p>[January 1996: It develops that one of the computer +administrators in the basement of the Pentagon read this entry +and fell over laughing. As a result, you too can now poke +Shub-Internet by <b><a href="#ping">ping</a></b>ing +<i>shub-internet.ims.disa.mil</i>. See also <b><a href="#kremvax">kremvax</a></b>. - ESR]</p> + +<p>[April 1999: shub-internet.ims.disa.mil is no more, alas. But +Shub-Internet lives o^$#$*^ - ESR]</p> + +<hr> +Node:<a name="sidecar">sidecar</a>, Next:<a rel="next" href="#SIG">SIG</a>, Previous:<a rel="previous" href="#Shub-Internet">Shub-Internet</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>sidecar</b> n.</p> + +<p>1. Syn. <b><a href="#slapontheside">slap on the +side</a></b>. Esp. used of add-ons for the late and unlamented +IBM PCjr. 2. The IBM PC compatibility box that could be bolted +onto the side of an Amiga. Designed and produced by Commodore, it +broke all of the company's own design rules. If it worked with +any other peripherals, it was by <b><a href="#magic">magic</a></b>. 3. More generally, any of various devices +designed to be connected to the expansion slot on the left side +of the Amiga 500 (and later, 600 & 1200), which included a +hard drive controller, a hard drive, and additional memory.</p> + +<hr> +Node:<a name="SIG">SIG</a>, Next:<a rel="next" href="#sigblock">sig block</a>, Previous:<a rel="previous" href="#sidecar">sidecar</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>SIG</b> /sig/ n.</p> + +<p>(also common as a prefix in combining forms) A Special +Interest Group, in one of several technical areas, sponsored by +the Association for Computing Machinery; well-known ones include +SIGPLAN (the Special Interest Group on Programming Languages), +SIGARCH (the Special Interest Group for Computer Architecture) +and SIGGRAPH (the Special Interest Group for Computer Graphics). +Hackers, not surprisingly, like to overextend this naming +convention to less formal associations like SIGBEER (at ACM +conferences) and SIGFOOD (at University of Illinois).</p> + +<hr> +Node:<a name="sigblock">sig block</a>, Next:<a rel="next" +href="#sigquote">sig quote</a>, Previous:<a rel="previous" +href="#SIG">SIG</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>sig block</b> /sig blok/ n.</p> + +<p>[Unix; often written `.sig' there] Short for `signature', used +specifically to refer to the electronic signature block that most +Unix mail- and news-posting software will <b><a href="#automagically">automagically</a></b> append to outgoing mail +and news. The composition of one's sig can be quite an art form, +including an ASCII logo or one's choice of witty sayings (see +<b><a href="#sigquote">sig quote</a></b>, <b><a href="#foolfile">fool file</a></b>); but many consider large sigs a +waste of <b><a href="#bandwidth">bandwidth</a></b>, and it has +been observed that the size of one's sig block is usually +inversely proportional to one's longevity and level of prestige +on the net. See also <b><a href="#doubledsig">doubled +sig</a></b>.</p> + +<hr> +Node:<a name="sigquote">sig quote</a>, Next:<a rel="next" +href="#sigvirus">sig virus</a>, Previous:<a rel="previous" +href="#sigblock">sig block</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>sig quote</b> /sig kwoht/ n.</p> + +<p>[Usenet] A maxim, quote, proverb, joke, or slogan embedded in +one's <b><a href="#sigblock">sig block</a></b> and intended to +convey something of one's philosophical stance, pet peeves, or +sense of humor. "Calm down, it's only ones and zeroes."</p> + +<hr> +Node:<a name="sigvirus">sig virus</a>, Next:<a rel="next" +href="#signaltonoiseratio">signal-to-noise ratio</a>, +Previous:<a rel="previous" href="#sigquote">sig quote</a>, +Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>sig virus</b> n.</p> + +<p>A parasitic <b><a href="#meme">meme</a></b> embedded in a +<b><a href="#sigblock">sig block</a></b>. There was a <b><a +href="#memeplague">meme plague</a></b> or fad for these on +Usenet in late 1991. Most were equivalents of "I am a .sig virus. +Please reproduce me in your .sig block.". Of course, the .sig +virus's memetic hook is the giggle value of going along with the +gag; this, however, was a self-limiting phenomenon as more and +more people picked up on the idea. There were creative variants +on it; some people stuck `sig virus antibody' texts in their +sigs, and there was at least one instance of a sig virus +eater.</p> + +<hr> +Node:<a name="signaltonoiseratio">signal-to-noise ratio</a>, +Next:<a rel="next" href="#silicon">silicon</a>, Previous:<a rel="previous" href="#sigvirus">sig virus</a>, Up:<a rel="up" +href="#chap19">= S =</a> <br> + + +<p><b>signal-to-noise ratio</b> [from analog electronics] n.</p> + +<p>Used by hackers in a generalization of its technical meaning. +`Signal' refers to useful information conveyed by some +communications medium, and `noise' to anything else on that +medium. Hence a low ratio implies that it is not worth paying +attention to the medium in question. Figures for such +metaphorical ratios are never given. The term is most often +applied to <b><a href="#Usenet">Usenet</a></b> newsgroups during +<b><a href="#flamewarr">flame war</a></b>s. Compare <b><a href="#bandwidth">bandwidth</a></b>. See also <b><a href="#coefficientofX">coefficient of X</a></b>, <b><a href="#lostinthenoise">lost in the noise</a></b>.</p> + +<hr> +Node:<a name="silicon">silicon</a>, Next:<a rel="next" href="#sillywalk">silly walk</a>, Previous:<a rel="previous" href="#signaltonoiseratio">signal-to-noise ratio</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>silicon</b> n.</p> + +<p>Hardware, esp. ICs or microprocessor-based computer systems +(compare <b><a href="#iron">iron</a></b>). Contrasted with +software. See also <b><a href="#sandbender">sandbender</a></b>.</p> + +<hr> +Node:<a name="sillywalk">silly walk</a>, Next:<a rel="next" +href="#silo">silo</a>, Previous:<a rel="previous" href="#silicon">silicon</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>silly walk</b> vi.</p> + +<p>[from Monty Python's Flying Circus] 1. A ridiculous procedure +required to accomplish a task. Like <b><a href="#grovel">grovel</a></b>, but more <b><a href="#random">random</a></b> and humorous. "I had to silly-walk +through half the /usr directories to find the maps file." 2. Syn. +<b><a href="#fandangooncore">fandango on core</a></b>.</p> + +<hr> +Node:<a name="silo">silo</a>, Next:<a rel="next" href="#SilverBook">Silver Book</a>, Previous:<a rel="previous" +href="#sillywalk">silly walk</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>silo</b> n.</p> + +<p>The FIFO input-character buffer in an RS-232 line card. So +called from <b><a href="#DEC">DEC</a></b> terminology used on DH +and DZ line cards for the VAX and PDP-11, presumably because it +was a storage space for fungible stuff that went in at the top +and came out at the bottom.</p> + +<hr> +Node:<a name="SilverBook">Silver Book</a>, Next:<a rel="next" +href="#sincetimeTequalsminusinfinity">since time T +equals minus infinity</a>, Previous:<a rel="previous" href="#silo">silo</a>, Up:<a rel="up" href="#chap19">= S =</a> +<br> + + +<p><b>Silver Book</b> n.</p> + +<p>Jensen and Wirth's infamous "Pascal User Manual and Report", +so called because of the silver cover of the widely distributed +Springer-Verlag second edition of 1978 (ISBN 0-387-90144-2). See +<b><a href="#booktitles">book titles</a></b>, <b><a href="#Pascal">Pascal</a></b>.</p> + +<hr> +Node:<a name="sincetimeTequalsminusinfinity">since +time T equals minus infinity</a>, Next:<a rel="next" href="#sitename">sitename</a>, Previous:<a rel="previous" href="#SilverBook">Silver Book</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>since time T equals minus infinity</b> adv.</p> + +<p>A long time ago; for as long as anyone can remember; at the +time that some particular frob was first designed. Usually the +word `time' is omitted. See also <b><a href="#timeT">time +T</a></b>; contrast <b><a href="#epoch">epoch</a></b>.</p> + +<hr> +Node:<a name="sitename">sitename</a>, Next:<a rel="next" href="#skrog">skrog</a>, Previous:<a rel="previous" href="#sincetimeTequalsminusinfinity">since time T +equals minus infinity</a>, Up:<a rel="up" href="#chap19">= +S =</a> <br> + + +<p><b>sitename</b> /si:t'naym/ n.</p> + +<p>[Unix/Internet] The unique electronic name of a computer +system, used to identify it in UUCP mail, Usenet, or other forms +of electronic information interchange. The folklore interest of +sitenames stems from the creativity and humor they often display. +Interpreting a sitename is not unlike interpreting a vanity +license plate; one has to mentally unpack it, allowing for +mono-case and length restrictions and the lack of whitespace. +Hacker tradition deprecates dull, institutional-sounding names in +favor of punchy, humorous, and clever coinages (except that it is +considered appropriate for the official public gateway machine of +an organization to bear the organization's name or acronym). +Mythological references, cartoon characters, animal names, and +allusions to SF or fantasy literature are probably the most +popular sources for sitenames (in roughly descending order). The +obligatory comment when discussing these is Harris's Lament: "All +the good ones are taken!" See also <b><a href="#networkaddress">network address</a></b>.</p> + +<hr> +Node:<a name="skrog">skrog</a>, Next:<a rel="next" href="#skulker">skulker</a>, Previous:<a rel="previous" href="#sitename">sitename</a>, Up:<a rel="up" href="#chap19">= +S =</a> <br> + + +<p><b>skrog</b> v.</p> + +<p>Syn. <b><a href="#scrog">scrog</a></b>.</p> + +<hr> +Node:<a name="skulker">skulker</a>, Next:<a rel="next" href="#slab">slab</a>, Previous:<a rel="previous" href="#skrog">skrog</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>skulker</b> n.</p> + +<p>Syn. <b><a href="#prowler">prowler</a></b>.</p> + +<hr> +Node:<a name="slab">slab</a>, Next:<a rel="next" href="#slack">slack</a>, Previous:<a rel="previous" href="#skulker">skulker</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>slab</b> [Apple]</p> + +<p>1. n. A continuous horizontal line of pixels, all with the +same color. 2. vi. To paint a slab on an output device. Apple's +QuickDraw, like most other professional-level graphics systems, +renders polygons and lines not with Bresenham's algorithm, but by +calculating `slab points' for each scan line on the screen in +succession, and then slabbing in the actual image pixels.</p> + +<hr> +Node:<a name="slack">slack</a>, Next:<a rel="next" href="#slapontheside">slap on the side</a>, Previous:<a rel="previous" href="#slab">slab</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>slack</b> n.</p> + +<p>1. Space allocated to a disk file but not actually used to +store useful information. The techspeak equivalent is `internal +fragmentation'. Antonym: <b><a href="#hole">hole</a></b>. 2. In +the theology of the <b><a href="#ChurchoftheSubGenius">Church of the SubGenius</a></b>, +a mystical substance or quality that is the prerequisite of all +human happiness.</p> + +<p>Since Unix files are stored compactly, except for the +unavoidable wastage in the last block or fragment, it might be +said that "Unix has no slack". See <b><a href="#hahaonlyserious">ha ha only serious</a></b>.</p> + +<hr> +Node:<a name="slapontheside">slap on the side</a>, +Next:<a rel="next" href="#slash">slash</a>, Previous:<a rel="previous" href="#slack">slack</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>slap on the side</b> n.</p> + +<p>(also called a <b><a href="#sidecar">sidecar</a></b>, or +abbreviated `SOTS'.) A type of external expansion hardware +marketed by computer manufacturers (e.g., Commodore for the Amiga +500/1000 series and IBM for the hideous failure called `PCjr'). +Various SOTS boxes provided necessities such as memory, hard +drive controllers, and conventional expansion slots.</p> + +<hr> +Node:<a name="slash">slash</a>, Next:<a rel="next" href="#slashdoteffect">slashdot effect</a>, Previous:<a rel="previous" href="#slapontheside">slap on the side</a>, +Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>slash</b> n.</p> + +<p>Common name for the slant (`/', ASCII 0101111) character. See +<b><a href="#ASCII">ASCII</a></b> for other synonyms.</p> + +<hr> +Node:<a name="slashdoteffect">slashdot effect</a>, Next:<a +rel="next" href="#sleep">sleep</a>, Previous:<a rel="previous" +href="#slash">slash</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>slashdot effect</b> n.</p> + +<p>1. Also spelled "/. effect"; what is said to have happened +when a website being virtually unreachable because too many +people are hitting it after the site was mentioned in an +interesting article on the popular Slashdot news service. The term is +quite widely used by /. readers, including variants like "That +site has been slashdotted again!" 2. In a perhaps inevitable +generation, the term is being used to describe any similar effect +from being listed on a popular site. This would better be +described as a <b><a href="#flashcrowd">flash +crowd</a></b>.</p> + +<hr> +Node:<a name="sleep">sleep</a>, Next:<a rel="next" href="#slim">slim</a>, Previous:<a rel="previous" href="#slashdoteffect">slashdot effect</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>sleep</b> vi.</p> + +<p>1. [techspeak] To relinquish a claim (of a process on a +multitasking system) for service; to indicate to the scheduler +that a process may be deactivated until some given event occurs +or a specified time delay elapses. 2. In jargon, used very +similarly to v. <b><a href="#block">block</a></b>; also in `sleep +on', syn. with `block on'. Often used to indicate that the +speaker has relinquished a demand for resources until some +(possibly unspecified) external event: "They can't get the fix +I've been asking for into the next release, so I'm going to sleep +on it until the release, then start hassling them again."</p> + +<hr> +Node:<a name="slim">slim</a>, Next:<a rel="next" href="#slop">slop</a>, Previous:<a rel="previous" href="#sleep">sleep</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>slim</b> n.</p> + +<p>A small, derivative change (e.g., to code).</p> + +<hr> +Node:<a name="slop">slop</a>, Next:<a rel="next" href="#slopsucker">slopsucker</a>, Previous:<a rel="previous" href="#slim">slim</a>, Up:<a rel="up" href="#chap19">= S =</a> +<br> + + +<p><b>slop</b> n.</p> + +<p>1. A one-sided <b><a href="#fudgefactor">fudge +factor</a></b>, that is, an allowance for error but in only one +of two directions. For example, if you need a piece of wire 10 +feet long and have to guess when you cut it, you make very sure +to cut it too long, by a large amount if necessary, rather than +too short by even a little bit, because you can always cut off +the slop but you can't paste it back on again. When discrete +quantities are involved, slop is often introduced to avoid the +possibility of being on the losing side of a <b><a href="#fenceposterror">fencepost error</a></b>. 2. The percentage +of `extra' code generated by a compiler over the size of +equivalent assembler code produced by <b><a href="#hand-hacking">hand-hacking</a></b>; i.e., the space (or maybe +time) you lose because you didn't do it yourself. This number is +often used as a measure of the goodness of a compiler; slop below +5% is very good, and 10% is usually acceptable. With modern +compiler technology, esp. on RISC machines, the compiler's slop +may actually be <i>negative</i>; that is, humans may be unable +to generate code as good. This is one of the reasons assembler +programming is no longer common.</p> + +<hr> +Node:<a name="slopsucker">slopsucker</a>, Next:<a rel="next" +href="#Slowlaris">Slowlaris</a>, Previous:<a rel="previous" href="#slop">slop</a>, Up:<a rel="up" href="#chap19">= S =</a> +<br> + + +<p><b>slopsucker</b> /slop'suhk-r/ n.</p> + +<p>A lowest-priority task that waits around until everything else +has `had its fill' of machine resources. Only when the machine +would otherwise be idle is the task allowed to `suck up the +slop'. Also called a `hungry puppy' or `bottom feeder'. One +common variety of slopsucker hunts for large prime numbers. +Compare <b><a href="#background">background</a></b>.</p> + +<hr> +Node:<a name="Slowlaris">Slowlaris</a>, Next:<a rel="next" href="#slurp">slurp</a>, Previous:<a rel="previous" href="#slopsucker">slopsucker</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>Slowlaris</b> /slo'-lahr-is/ n.</p> + +<p>[Usenet; poss. from the variety of prosimian called a "slow +loris". The variant `Slowlartus' is also common, related to <b><a +href="#LART">LART</a></b>] Common hackish term for Solaris, Sun's +System VR4 version of UNIX that came out of the standardization +wars of the early 1990s. So named because especially on older +hardware, responsiveness was much less crisp than under the +preceding SunOS. Early releases of Solaris (that is, Solaris 2, +as some <b><a href="#marketroid">marketroid</a></b>s at Sun +retroactively rechristened SunOS as Solaris 1) were quite buggy, +and Sun was forced by customer demand to support SunOS for quite +some time. Newer versions are acknowledged to be among the best +commercial UNIX variants in 1998, but still lose single-processor +benchmarks to Sparc <b><a href="#Linux">Linux</a></b>. Compare +<b><a href="#AIDX">AIDX</a></b>, <b><a href="#HP-SUX">HP-SUX</a></b>, <b><a href="#NominalSemidestructor">Nominal Semidestructor</a></b>, <b><a +href="#Telerat">Telerat</a></b>, <b><a href="#sun-stools">sun-stools</a></b>.</p> + +<hr> +Node:<a name="slurp">slurp</a>, Next:<a rel="next" href="#smart">smart</a>, Previous:<a rel="previous" href="#Slowlaris">Slowlaris</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>slurp</b> vt.</p> + +<p>To read a large data file entirely into <b><a href="#core">core</a></b> before working on it. This may be contrasted +with the strategy of reading a small piece at a time, processing +it, and then reading the next piece. "This program slurps in a +1K-by-1K matrix and does an FFT." See also <b><a href="#sponge">sponge</a></b>.</p> + +<hr> +Node:<a name="smart">smart</a>, Next:<a rel="next" href="#smartterminal">smart terminal</a>, Previous:<a rel="previous" href="#slurp">slurp</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>smart</b> adj.</p> + +<p>Said of a program that does the <b><a href="#RightThing">Right Thing</a></b> in a wide variety of +complicated circumstances. There is a difference between calling +a program smart and calling it intelligent; in particular, there +do not exist any intelligent programs (yet -- see <b><a href="#AI-complete">AI-complete</a></b>). Compare <b><a href="#robust">robust</a></b> (smart programs can be <b><a href="#brittle">brittle</a></b>).</p> + +<hr> +Node:<a name="smartterminal">smart terminal</a>, Next:<a rel="next" href="#smashcase">smash case</a>, Previous:<a rel="previous" href="#smart">smart</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>smart terminal</b> n.</p> + +<p>1. A terminal that has enough computing capability to render +graphics or to offload some kind of front-end processing from the +computer it talks to. The development of workstations and +personal computers has made this term and the product it +describes semi-obsolescent, but one may still hear variants of +the phrase `act like a smart terminal' used to describe the +behavior of workstations or PCs with respect to programs that +execute almost entirely out of a remote <b><a href="#server">server</a></b>'s storage, using local devices as +displays. 2. obs. Any terminal with an addressable cursor; the +opposite of a <b><a href="#glasstty">glass tty</a></b>. Today, +a terminal with merely an addressable cursor, but with none of +the more-powerful features mentioned in sense 1, is called a +<b><a href="#dumbterminal">dumb terminal</a></b>.</p> + +<p>There is a classic quote from Rob Pike (inventor of the <b><a +href="#blit">blit</a></b> terminal): "A smart terminal is not a +smart<i>ass</i> terminal, but rather a terminal you can +educate." This illustrates a common design problem: The attempt +to make peripherals (or anything else) intelligent sometimes +results in finicky, rigid `special features' that become just so +much dead weight if you try to use the device in any way the +designer didn't anticipate. Flexibility and programmability, on +the other hand, are <i>really</i> smart. Compare <b><a href="#hook">hook</a></b>.</p> + +<hr> +Node:<a name="smashcase">smash case</a>, Next:<a rel="next" +href="#smashthestack">smash the stack</a>, Previous:<a rel="previous" href="#smartterminal">smart terminal</a>, Up:<a +rel="up" href="#chap19">= S =</a> <br> + + +<p><b>smash case</b> vi.</p> + +<p>To lose or obliterate the uppercase/lowercase distinction in +text input. "MS-DOS will automatically smash case in the names of +all the files you create." Compare <b><a href="#foldcase">fold +case</a></b>.</p> + +<hr> +Node:<a name="smashthestack">smash the stack</a>, Next:<a +rel="next" href="#smiley">smiley</a>, Previous:<a rel="previous" +href="#smashcase">smash case</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>smash the stack</b> n.</p> + +<p>[C programming] To corrupt the execution stack by writing past +the end of a local array or other data structure. Code that +smashes the stack can cause a return from the routine to jump to +a random address, resulting in some of the most insidious +data-dependent bugs known to mankind. Variants include `trash' +the stack, <b><a href="#scribble">scribble</a></b> the stack, +<b><a href="#mangle">mangle</a></b> the stack; the term **<b><a +href="#mung">mung</a></b> the stack is not used, as this is never +done intentionally. See <b><a href="#spam">spam</a></b>; see also +<b><a href="#aliasingbug">aliasing bug</a></b>, <b><a href="#fandangooncore">fandango on core</a></b>, <b><a href="#memoryleak">memory leak</a></b>, <b><a href="#memorysmash">memory smash</a></b>, <b><a href="#precedencelossage">precedence lossage</a></b>, <b><a href="#overrunscrew">overrun screw</a></b>.</p> + +<hr> +Node:<a name="smiley">smiley</a>, Next:<a rel="next" href="#smoke">smoke</a>, Previous:<a rel="previous" href="#smashthestack">smash the stack</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>smiley</b> n.</p> + +<p>See <b><a href="#emoticon">emoticon</a></b>.</p> + +<hr> +Node:<a name="smoke">smoke</a>, Next:<a rel="next" href="#smokeandmirrors">smoke and mirrors</a>, Previous:<a rel="previous" href="#smiley">smiley</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>smoke</b> vi.</p> + +<p>1. To <b><a href="#crash">crash</a></b> or blow up, usually +spectacularly. "The new version smoked, just like the last one." +Used for both hardware (where it often describes an actual +physical event), and software (where it's merely colorful). 2. +[from automotive slang] To be conspicuously fast. "That processor +really smokes." Compare <b><a href="#magicsmoke">magic +smoke</a></b>.</p> + +<hr> +Node:<a name="smokeandmirrors">smoke and mirrors</a>, +Next:<a rel="next" href="#smoketest">smoke test</a>, +Previous:<a rel="previous" href="#smoke">smoke</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>smoke and mirrors</b> n.</p> + +<p>Marketing deceptions. The term is mainstream in this general +sense. Among hackers it's strongly associated with bogus demos +and crocked <b><a href="#benchmark">benchmark</a></b>s (see also +<b><a href="#MIPS">MIPS</a></b>, <b><a href="#machoflops">machoflops</a></b>). "They claim their new box +cranks 50 MIPS for under $5000, but didn't specify the +instruction mix -- sounds like smoke and mirrors to me." The +phrase, popularized by newspaper columnist Jimmy Breslin c.1975, +has been said to derive from carnie slang for magic acts and +`freak show' displays that depend on `trompe l'oeil' effects, but +also calls to mind the fierce Aztec god Tezcatlipoca (lit. +"Smoking Mirror") for whom the hearts of huge numbers of human +sacrificial victims were regularly cut out. Upon hearing about a +rigged demo or yet another round of fantasy-based marketing +promises, hackers often feel analogously disheartened. See also +<b><a href="#stealthmanager">stealth manager</a></b>.</p> + +<hr> +Node:<a name="smoketest">smoke test</a>, Next:<a rel="next" +href="#smokingclover">smoking clover</a>, Previous:<a rel="previous" href="#smokeandmirrors">smoke and mirrors</a>, +Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>smoke test</b> n.</p> + +<p>1. A rudimentary form of testing applied to electronic +equipment following repair or reconfiguration, in which power is +applied and the tester checks for sparks, smoke, or other +dramatic signs of fundamental failure. See <b><a href="#magicsmoke">magic smoke</a></b>. 2. By extension, the first +run of a piece of software after construction or a critical +change. See and compare <b><a href="#realitycheck">reality +check</a></b>.</p> + +<p>There is an interesting semi-parallel to this term among +typographers and printers: When new typefaces are being punch-cut +by hand, a `smoke test' (hold the letter in candle smoke, then +press it onto paper) is used to check out new dies.</p> + +<hr> +Node:<a name="smokingclover">smoking clover</a>, Next:<a rel="next" href="#smoot">smoot</a>, Previous:<a rel="previous" href="#smoketest">smoke test</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>smoking clover</b> n.</p> + +<p>[ITS] A <b><a href="#displayhack">display hack</a></b> +originally due to Bill Gosper. Many convergent lines are drawn on +a color monitor in such a way that every pixel struck has its +color incremented. The lines all have one endpoint in the middle +of the screen; the other endpoints are spaced one pixel apart +around the perimeter of a large square. The color map is then +repeatedly rotated. This results in a striking, rainbow-hued, +shimmering four-leaf clover. Gosper joked about keeping it hidden +from the FDA (the U.S.'s Food and Drug Administration) lest its +hallucinogenic properties cause it to be banned.</p> + +<hr> +Node:<a name="smoot">smoot</a>, Next:<a rel="next" href="#SMOP">SMOP</a>, Previous:<a rel="previous" href="#smokingclover">smoking clover</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>smoot</b> /smoot/ n.</p> + +<p>[MIT] A unit of length equal five feet seven inches. The +length of the Harvard Bridge in Boston is famously 364.4 smoots +plus or minus an ear (the ear stands for <b><a href="#epsilon">epsilon</a></b>). This legend began with a fraternity +prank in 1958 during which the body length of Oliver Smoot (class +of '62) was actually used to measure out that distance. It is +commemorated by smoot marks that MIT students repaint every few +years; the tradition even survived the demolition and rebuilding +of the bridge in the late 1980s. The Boston police have been +known to use smoot markers to indicate accident locations on the +bridge.</p> + +<hr> +Node:<a name="SMOP">SMOP</a>, Next:<a rel="next" href="#smurf">smurf</a>, Previous:<a rel="previous" href="#smoot">smoot</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>SMOP</b> /S-M-O-P/ n.</p> + +<p>[Simple (or Small) Matter of Programming] 1. A piece of code, +not yet written, whose anticipated length is significantly +greater than its complexity. Used to refer to a program that +could obviously be written, but is not worth the trouble. Also +used ironically to imply that a difficult problem can be easily +solved because a program can be written to do it; the irony is +that it is very clear that writing such a program will be a great +deal of work. "It's easy to enhance a FORTRAN compiler to compile +COBOL as well; it's just an SMOP." 2. Often used ironically by +the intended victim when a suggestion for a program is made which +seems easy to the suggester, but is obviously (to the victim) a +lot of work.</p> + +<hr> +Node:<a name="smurf">smurf</a>, Next:<a rel="next" href="#SNAFUprinciple">SNAFU principle</a>, Previous:<a rel="previous" href="#SMOP">SMOP</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>smurf</b> /smerf/ n.</p> + +<p>1. [from the <i>soc.motss</i> newsgroup on Usenet, after some +obnoxiously gooey cartoon characters] A newsgroup regular with a +habitual style that is irreverent, silly, and <i>cute</i>. Like +many other hackish terms for people, this one may be praise or +insult depending on who uses it. In general, being referred to as +a smurf is probably not going to make your day unless you've +previously adopted the label yourself in a spirit of irony. +Compare <b><a href="#oldfart">old fart</a></b>. 2. [techspeak] +A ping packet with a forged source address sent to some other +network's broadcast address. All the machines on the destination +network will send a ping response to the forged source address +(the victim). This both overloads the victim's network and hides +the location of the attacker.</p> + +<hr> +Node:<a name="SNAFUprinciple">SNAFU principle</a>, Next:<a +rel="next" href="#snail">snail</a>, Previous:<a rel="previous" +href="#smurf">smurf</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>SNAFU principle</b> /sna'foo prin'si-pl/ n.</p> + +<p>[from a WWII Army acronym for `Situation Normal, All Fucked +Up'] "True communication is possible only between equals, because +inferiors are more consistently rewarded for telling their +superiors pleasant lies than for telling the truth." -- a central +tenet of <b><a href="#Discordianism">Discordianism</a></b>, often +invoked by hackers to explain why authoritarian hierarchies screw +up so reliably and systematically. The effect of the SNAFU +principle is a progressive disconnection of decision-makers from +reality. This lightly adapted version of a fable dating back to +the early 1960s illustrates the phenomenon perfectly:</p> + +<blockquote>In the beginning was the plan,<br> + and then the specification;<br> +And the plan was without form,<br> + and the specification was void.<br> + + +<p>And darkness<br> + was on the faces of the implementors thereof;<br> +And they spake unto their leader,<br> + saying:<br> +"It is a crock of shit,<br> + and smells as of a sewer."<br> +</p> + +<p>And the leader took pity on them,<br> + and spoke to the project leader:<br> +"It is a crock of excrement,<br> + and none may abide the odor thereof."<br> +</p> + +<p>And the project leader<br> + spake unto his section head, saying:<br> +"It is a container of excrement,<br> + and it is very strong, such that none may abide it."<br> +</p> + +<p>The section head then hurried to his department manager,<br> + and informed him thus:<br> +"It is a vessel of fertilizer,<br> + and none may abide its strength."<br> +</p> + +<p>The department manager carried these words<br> + to his general manager,<br> +and spoke unto him<br> + saying:<br> +"It containeth that which aideth the growth of plants,<br> + and it is very strong."<br> +</p> + +<p>And so it was that the general manager rejoiced<br> + and delivered the good news unto the Vice President.<br> +"It promoteth growth,<br> + and it is very powerful."<br> +</p> + +<p>The Vice President rushed to the President's side,<br> + and joyously exclaimed:<br> +"This powerful new software product<br> + will promote the growth of the company!"<br> +</p> + +<p>And the President looked upon the product,<br> + and saw that it was very good.<br> +</p> +</blockquote> + +<p>After the subsequent and inevitable disaster, the <b><a href="#suit">suit</a></b>s protect themselves by saying "I was +misinformed!", and the implementors are demoted or fired. Compare +<b><a href="#ConwaysLaw">Conway's Law</a></b>.</p> + +<hr> +Node:<a name="snail">snail</a>, Next:<a rel="next" href="#snail-mail">snail-mail</a>, Previous:<a rel="previous" href="#SNAFUprinciple">SNAFU principle</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>snail</b> vt.</p> + +<p>To <b><a href="#snail-mail">snail-mail</a></b> something. +"Snail me a copy of those graphics, will you?"</p> + +<hr> +Node:<a name="snail-mail">snail-mail</a>, Next:<a rel="next" +href="#snap">snap</a>, Previous:<a rel="previous" href="#snail">snail</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>snail-mail</b> n.</p> + +<p>Paper mail, as opposed to electronic. Sometimes written as the +single word `SnailMail'. One's postal address is, +correspondingly, a `snail address'. Derives from earlier coinage +`USnail' (from `U.S. Mail'), for which there have even been +parody posters and stamps made. Also (less commonly) called +`P-mail', from `paper mail' or `physical mail'. Oppose <b><a +href="#email">email</a></b>.</p> + +<hr> +Node:<a name="snap">snap</a>, Next:<a rel="next" href="#snarf">snarf</a>, Previous:<a rel="previous" href="#snail-mail">snail-mail</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>snap</b> v.</p> + +<p>To replace a pointer to a pointer with a direct pointer; to +replace an old address with the forwarding address found there. +If you telephone the main number for an institution and ask for a +particular person by name, the operator may tell you that +person's extension before connecting you, in the hopes that you +will `snap your pointer' and dial direct next time. The +underlying metaphor may be that of a rubber band stretched +through a number of intermediate points; if you remove all the +thumbtacks in the middle, it snaps into a straight line from +first to last. See <b><a href="#chasepointers">chase +pointers</a></b>.</p> + +<p>Often, the behavior of a <b><a href="#trampoline">trampoline</a></b> is to perform an error check +once and then snap the pointer that invoked it so as henceforth +to bypass the trampoline (and its one-shot error check). In this +context one also speaks of `snapping links'. For example, in a +LISP implementation, a function interface trampoline might check +to make sure that the caller is passing the correct number of +arguments; if it is, and if the caller and the callee are both +compiled, then snapping the link allows that particular path to +use a direct procedure-call instruction with no further +overhead.</p> + +<hr> +Node:<a name="snarf">snarf</a>, Next:<a rel="next" href="#snarfampbarf">snarf & barf</a>, Previous:<a rel="previous" href="#snap">snap</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>snarf</b> /snarf/ vt.</p> + +<p>1. To grab, esp. to grab a large document or file for the +purpose of using it with or without the author's permission. See +also <b><a href="#BLT">BLT</a></b>. 2. [in the Unix community] To +fetch a file or set of files across a network. See also <b><a +href="#blast">blast</a></b>. This term was mainstream in the late +1960s, meaning `to eat piggishly'. It may still have this +connotation in context. "He's in the snarfing phase of hacking -- +<b><a href="#FTP">FTP</a></b>ing megs of stuff a day." 3. To +acquire, with little concern for legal forms or <i>politesse</i> +(but not quite by stealing). "They were giving away samples, so I +snarfed a bunch of them." 4. Syn. for <b><a href="#slurp">slurp</a></b>. "This program starts by snarfing the +entire database into core, then<small>...</small>." 5. [GEnie] To +spray food or <b><a href="#programmingfluid">programming +fluid</a></b>s due to laughing at the wrong moment. "I was +drinking coffee, and when I read your post I snarfed all over my +desk." "If I keep reading this topic, I think I'll have to +snarf-proof my computer with a keyboard <b><a href="#condom">condom</a></b>." [This sense appears to be widespread +among mundane teenagers --ESR]</p> + +<hr> +Node:<a name="snarfampbarf">snarf & barf</a>, Next:<a +rel="next" href="#snarfdown">snarf down</a>, Previous:<a rel="previous" href="#snarf">snarf</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>snarf & barf</b> /snarf'n-barf`/ n.</p> + +<p>Under a <b><a href="#WIMPenvironment">WIMP +environment</a></b>, the act of grabbing a region of text and +then stuffing the contents of that region into another region (or +the same one) to avoid retyping a command line. In the late +1960s, this was a mainstream expression for an `eat now, regret +it later' cheap-restaurant expedition.</p> + +<hr> +Node:<a name="snarfdown">snarf down</a>, Next:<a rel="next" +href="#snark">snark</a>, Previous:<a rel="previous" href="#snarfampbarf">snarf & barf</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>snarf down</b> v.</p> + +<p>To <b><a href="#snarf">snarf</a></b>, with the connotation of +absorbing, processing, or understanding. "I'll snarf down the +latest version of the <b><a href="#nethack">nethack</a></b> +user's guide -- it's been a while since I played last and I don't +know what's changed recently."</p> + +<hr> +Node:<a name="snark">snark</a>, Next:<a rel="next" href="#sneaker">sneaker</a>, Previous:<a rel="previous" href="#snarfdown">snarf down</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>snark</b> n.</p> + +<p>[Lewis Carroll, via the Michigan Terminal System] 1. A system +failure. When a user's process bombed, the operator would get the +message "Help, Help, Snark in MTS!" 2. More generally, any kind +of unexplained or threatening event on a computer (especially if +it might be a boojum). Often used to refer to an event or a log +file entry that might indicate an attempted security violation. +See <b><a href="#snivitz">snivitz</a></b>. 3. UUCP name of +<i>snark.thyrsus.com</i>, home site of the Jargon File versions +from 2.*.* on (i.e., this lexicon).</p> + +<hr> +Node:<a name="sneaker">sneaker</a>, Next:<a rel="next" href="#sneakernet">sneakernet</a>, Previous:<a rel="previous" href="#snark">snark</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>sneaker</b> n.</p> + +<p>An individual hired to break into places in order to test +their security; analogous to <b><a href="#tigerteam">tiger +team</a></b>. Compare <b><a href="#samurai">samurai</a></b>.</p> + +<hr> +Node:<a name="sneakernet">sneakernet</a>, Next:<a rel="next" +href="#sniff">sniff</a>, Previous:<a rel="previous" href="#sneaker">sneaker</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>sneakernet</b> /snee'ker-net/ n.</p> + +<p>Term used (generally with ironic intent) for transfer of +electronic information by physically carrying tape, disks, or +some other media from one machine to another. "Never +underestimate the bandwidth of a station wagon filled with +magtape, or a 747 filled with CD-ROMs." Also called `Tennis-Net', +`Armpit-Net', `Floppy-Net' or `Shoenet'; in the 1990s, `Nike +network' after a well-known sneaker brand.</p> + +<hr> +Node:<a name="sniff">sniff</a>, Next:<a rel="next" href="#snivitz">snivitz</a>, Previous:<a rel="previous" href="#sneakernet">sneakernet</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>sniff</b> v.,n.</p> + +<p>1. To watch IP packets traversing a local network. Most often +in the phrase `packet sniffer', a program for doing same. +2.Synonym for <b><a href="#poll">poll</a></b>.</p> + +<hr> +Node:<a name="snivitz">snivitz</a>, Next:<a rel="next" href="#Snooze">'Snooze</a>, Previous:<a rel="previous" href="#sniff">sniff</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>snivitz</b> /sniv'itz/ n.</p> + +<p>A hiccup in hardware or software; a small, transient problem +of unknown origin (less serious than a <b><a href="#snark">snark</a></b>). Compare <b><a href="#glitch">glitch</a></b>.</p> + +<hr> +Node:<a name="Snooze">'Snooze</a>, Next:<a rel="next" href="#SO">SO</a>, Previous:<a rel="previous" href="#snivitz">snivitz</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>'Snooze</b> /snooz/ [FidoNet] n.</p> + +<p>Fidonews, the weekly official on-line newsletter of FidoNet. +As the editorial policy of Fidonews is "anything that arrives, we +print", there are often large articles completely unrelated to +FidoNet, which in turn tend to elicit <b><a href="#flamage">flamage</a></b> in subsequent issues.</p> + +<hr> +Node:<a name="SO">SO</a>, Next:<a rel="next" href="#socialengineering">social engineering</a>, Previous:<a rel="previous" href="#Snooze">'Snooze</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>SO</b> /S-O/ n.</p> + +<p>1. (also `S.O.') Abbrev. for Significant Other, almost +invariably written abbreviated and pronounced /S-O/ by hackers. +Used to refer to one's primary relationship, esp. a live-in to +whom one is not married. See <b><a href="#MOTAS">MOTAS</a></b>, +<b><a href="#MOTOS">MOTOS</a></b>, <b><a href="#MOTSS">MOTSS</a></b>. 2. [techspeak] The Shift Out control +character in ASCII (Control-N, 0001110).</p> + +<hr> +Node:<a name="socialengineering">social engineering</a>, +Next:<a rel="next" href="#socialsciencenumber">social +science number</a>, Previous:<a rel="previous" href="#SO">SO</a>, +Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>social engineering</b> n.</p> + +<p>Term used among <b><a href="#cracker">cracker</a></b>s and +<b><a href="#samurai">samurai</a></b> for cracking techniques +that rely on weaknesses in <b><a href="#wetware">wetware</a></b> +rather than software; the aim is to trick people into revealing +passwords or other information that compromises a target system's +security. Classic scams include phoning up a mark who has the +required information and posing as a field service tech or a +fellow employee with an urgent access problem. See also the <b><a +href="#tigerteam">tiger team</a></b> story in the <b><a href="#patch">patch</a></b> entry.</p> + +<hr> +Node:<a name="socialsciencenumber">social science +number</a>, Next:<a rel="next" href="#sockpuppet">sock +puppet</a>, Previous:<a rel="previous" href="#socialengineering">social engineering</a>, Up:<a rel="up" +href="#chap19">= S =</a> <br> + + +<p><b>social science number</b> n. //</p> + +<p>[IBM] A statistic that is <b><a href="#content-free">content-free</a></b>, or nearly so. A measure +derived via methods of questionable validity from data of a +dubious and vague nature. Predictively, having a social science +number in hand is seldom much better than nothing, and can be +considerably worse. As a rule, <b><a href="#management">management</a></b> loves them. See also <b><a href="#numbers">numbers</a></b>, <b><a href="#math-out">math-out</a></b>, <b><a href="#prettypictures">pretty pictures</a></b>.</p> + +<hr> +Node:<a name="sockpuppet">sock puppet</a>, Next:<a rel="next" +href="#sodiumsubstrate">sodium substrate</a>, Previous:<a rel="previous" href="#socialsciencenumber">social science +number</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>sock puppet</b> n.</p> + +<p>[Usenet: from the act of placing a sock over your hand and +talking to it and pretending it's talking back] In Usenet +parlance, a <b><a href="#pseudo">pseudo</a></b> through which the +puppeteer posts follow-ups to their own original message to give +the appearance that a number of people support the views held in +the original message.</p> + +<hr> +Node:<a name="sodiumsubstrate">sodium substrate</a>, Next:<a +rel="next" href="#softboot">soft boot</a>, Previous:<a rel="previous" href="#sockpuppet">sock puppet</a>, Up:<a rel="up" +href="#chap19">= S =</a> <br> + + +<p><b>sodium substrate</b> n.</p> + +<p>Syn <b><a href="#saltsubstrate">salt substrate</a></b>.</p> + +<hr> +Node:<a name="softboot">soft boot</a>, Next:<a rel="next" +href="#softcopy">softcopy</a>, Previous:<a rel="previous" href="#sodiumsubstrate">sodium substrate</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>soft boot</b> n.</p> + +<p>See <b><a href="#boot">boot</a></b>.</p> + +<hr> +Node:<a name="softcopy">softcopy</a>, Next:<a rel="next" href="#softwarebloat">software bloat</a>, Previous:<a rel="previous" href="#softboot">soft boot</a>, Up:<a rel="up" +href="#chap19">= S =</a> <br> + + +<p><b>softcopy</b> /soft'kop-ee/ n.</p> + +<p>[by analogy with `hardcopy'] A machine-readable form of +corresponding hardcopy. See <b><a href="#bits">bits</a></b>, +<b><a href="#machinable">machinable</a></b>.</p> + +<hr> +Node:<a name="softwarebloat">software bloat</a>, Next:<a rel="next" href="#softwarehoarding">software hoarding</a>, +Previous:<a rel="previous" href="#softcopy">softcopy</a>, Up:<a +rel="up" href="#chap19">= S =</a> <br> + + +<p><b>software bloat</b> n.</p> + +<p>The results of <b><a href="#second-systemeffect">second-system effect</a></b> or <b><a +href="#creepingfeaturitis">creeping featuritis</a></b>. +Commonly cited examples include <code>ls(1)</code>, <b><a href="#X">X</a></b>, <b><a href="#BSD">BSD</a></b>, <b><a href="#Missedem-five">Missed'em-five</a></b>, and <b><a href="#OSslash2">OS/2</a></b>.</p> + +<hr> +Node:<a name="softwarehoarding">software hoarding</a>, Next:<a +rel="next" href="#softwarelaser">software laser</a>, +Previous:<a rel="previous" href="#softwarebloat">software +bloat</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>software hoarding</b> n.</p> + +<p>Pejorative term employed by members and adherents of the <b><a +href="#GNU">GNU</a></b> project to describe the act of holding +software proprietary, keeping it under trade secret or license +terms which prohibit free redistribution and modification. Used +primarily in Free Software Foundation propaganda. For a summary +of related issues, see <b><a href="#GNU">GNU</a></b>.</p> + +<hr> +Node:<a name="softwarelaser">software laser</a>, Next:<a rel="next" href="#softwarerot">software rot</a>, Previous:<a rel="previous" href="#softwarehoarding">software hoarding</a>, +Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>software laser</b> n.</p> + +<p>An optical laser works by bouncing photons back and forth +between two mirrors, one totally reflective and one partially +reflective. If the lasing material (usually a crystal) has the +right properties, photons scattering off the atoms in the crystal +will excite cascades of more photons, all in lockstep. Eventually +the beam will escape through the partially-reflective mirror. One +kind of <b><a href="#sorcerersapprenticemode">sorcerer's +apprentice mode</a></b> involving <b><a href="#bouncemessage">bounce message</a></b>s can produce closely +analogous results, with a <b><a href="#cascade">cascade</a></b> +of messages escaping to flood nearby systems. By mid-1993 there +had been at least two publicized incidents of this kind.</p> + +<hr> +Node:<a name="softwarerot">software rot</a>, Next:<a rel="next" href="#softwarily">softwarily</a>, Previous:<a rel="previous" href="#softwarelaser">software laser</a>, Up:<a +rel="up" href="#chap19">= S =</a> <br> + + +<p><b>software rot</b> n.</p> + +<p>Term used to describe the tendency of software that has not +been used in a while to <b><a href="#lose">lose</a></b>; such +failure may be semi-humorously ascribed to <b><a href="#bitrot">bit rot</a></b>. More commonly, `software rot' +strikes when a program's assumptions become out of date. If the +design was insufficiently <b><a href="#robust">robust</a></b>, +this may cause it to fail in mysterious ways. Syn. `code rot'. +See also <b><a href="#linkrot">link rot</a></b>.</p> + +<p>For example, owing to endemic shortsightedness in the design +of COBOL programs, a good number of them succumbed to software +rot when their 2-digit year counters underwent <b><a href="#wrapAround">wrap around</a></b> at the beginning of the year +2000. Actually, related lossages often afflict centenarians who +have to deal with computer software designed by unimaginative +clods. One such incident became the focus of a minor public flap +in 1990, when a gentleman born in 1889 applied for a driver's +license renewal in Raleigh, North Carolina. The new system +refused to issue the card, probably because with 2-digit years +the ages 101 and 1 cannot be distinguished.</p> + +<p>Historical note: Software rot in an even funnier sense than +the mythical one was a real problem on early research computers +(e.g., the R1; see <b><a href="#grindcrank">grind +crank</a></b>). If a program that depended on a peculiar +instruction hadn't been run in quite a while, the user might +discover that the opcodes no longer did the same things they once +did. ("Hey, so-and-so needs an instruction to do such-and-such. +We can <b><a href="#snarf">snarf</a></b> this opcode, right? No +one uses it.")</p> + +<p>Another classic example of this sprang from the time an MIT +hacker found a simple way to double the speed of the +unconditional jump instruction on a PDP-6, so he patched the +hardware. Unfortunately, this broke some fragile timing software +in a music-playing program, throwing its output out of tune. This +was fixed by adding a defensive initialization routine to compare +the speed of a timing loop with the real-time clock; in other +words, it figured out how fast the PDP-6 was that day, and +corrected appropriately.</p> + +<p>Compare <b><a href="#bitrot">bit rot</a></b>.</p> + +<hr> +Node:<a name="softwarily">softwarily</a>, Next:<a rel="next" +href="#softy">softy</a>, Previous:<a rel="previous" href="#softwarerot">software rot</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>softwarily</b> /soft-weir'i-lee/ adv.</p> + +<p>In a way pertaining to software. "The system is softwarily +unreliable." The adjective **`softwary' is <i>not</i> used. See +<b><a href="#hardwarily">hardwarily</a></b>.</p> + +<hr> +Node:<a name="softy">softy</a>, Next:<a rel="next" href="#somerandomX">some random X</a>, Previous:<a rel="previous" href="#softwarily">softwarily</a>, Up:<a rel="up" +href="#chap19">= S =</a> <br> + + +<p><b>softy</b> n.</p> + +<p>[IBM] Hardware hackers' term for a software expert who is +largely ignorant of the mysteries of hardware.</p> + +<hr> +Node:<a name="somerandomX">some random X</a>, Next:<a rel="next" href="#sorcerersapprenticemode">sorcerer's +apprentice mode</a>, Previous:<a rel="previous" href="#softy">softy</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>some random X</b> adj.</p> + +<p>Used to indicate a member of class X, with the implication +that Xs are interchangeable. "I think some random cracker tripped +over the guest timeout last night." See also <b><a href="#Jrandom">J. Random</a></b>.</p> + +<hr> +Node:<a name="sorcerersapprenticemode">sorcerer's +apprentice mode</a>, Next:<a rel="next" href="#SOS">SOS</a>, +Previous:<a rel="previous" href="#somerandomX">some random +X</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>sorcerer's apprentice mode</b> n.</p> + +<p>[from Goethe's "Der Zauberlehrling" via Paul Dukas's +"L'apprenti sorcier" the film "Fantasia"] A bug in a protocol +where, under some circumstances, the receipt of a message causes +multiple messages to be sent, each of which, when received, +triggers the same bug. Used esp. of such behavior caused by <b><a +href="#bouncemessage">bounce message</a></b> loops in <b><a +href="#email">email</a></b> software. Compare <b><a href="#broadcaststorm">broadcast storm</a></b>, <b><a href="#networkmeltdown">network meltdown</a></b>, <b><a href="#softwarelaser">software laser</a></b>, <b><a href="#ARMM">ARMM</a></b>.</p> + +<hr> +Node:<a name="SOS">SOS</a>, Next:<a rel="next" href="#source">source</a>, Previous:<a rel="previous" href="#sorcerersapprenticemode">sorcerer's apprentice mode</a>, +Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>SOS</b> /S-O-S/</p> + +<p>n.,obs. An infamously <b><a href="#losing">losing</a></b> text +editor. Once, back in the 1960s, when a text editor was needed +for the PDP-6, a hacker crufted together a <b><a href="#quick-and-dirty">quick-and-dirty</a></b> `stopgap editor' to be +used until a better one was written. Unfortunately, the old one +was never really discarded when new ones came along. SOS is a +descendant (`Son of Stopgap') of that editor, and many PDP-10 +users gained the dubious pleasure of its acquaintance. Since then +other programs similar in style to SOS have been written, notably +the early font editor BILOS /bye'lohs/, the Brother-In-Law Of +Stopgap (the alternate expansion `Bastard Issue, Loins of +Stopgap' has been proposed).</p> + +<hr> +Node:<a name="source">source</a>, Next:<a rel="next" href="#sourceofallgoodbits">source of all good bits</a>, +Previous:<a rel="previous" href="#SOS">SOS</a>, Up:<a rel="up" +href="#chap19">= S =</a> <br> + + +<p><b>source</b> n.</p> + +<p>[very common] In reference to software, `source' is invariably +shorthand for `source code', the preferred human-readable and +human-modifiable form of the program. This is as opposed to +object code, the derived binary executable form of a program. +This shorthand readily takes derivative forms; one may speak of +"the sources of a system" or of "having source".</p> + +<hr> +Node:<a name="sourceofallgoodbits">source of all good +bits</a>, Next:<a rel="next" href="#space-cadetkeyboard">space-cadet keyboard</a>, Previous:<a +rel="previous" href="#source">source</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>source of all good bits</b> n.</p> + +<p>A person from whom (or a place from which) useful information +may be obtained. If you need to know about a program, a <b><a +href="#guru">guru</a></b> might be the source of all good bits. +The title is often applied to a particularly competent +secretary.</p> + +<hr> +Node:<a name="space-cadetkeyboard">space-cadet keyboard</a>, +Next:<a rel="next" href="#spaceshipoperator">spaceship +operator</a>, Previous:<a rel="previous" href="#sourceofallgoodbits">source of all good bits</a>, +Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>space-cadet keyboard</b> n.</p> + +<p>A now-legendary device used on MIT LISP machines, which +inspired several still-current jargon terms and influenced the +design of <b><a href="#EMACS">EMACS</a></b>. It was equipped with +no fewer than <i>seven</i> shift keys: four keys for <b><a +href="#buckybits">bucky bits</a></b> (`control', `meta', +`hyper', and `super') and three like regular shift keys, called +`shift', `top', and `front'. Many keys had three symbols on them: +a letter and a symbol on the top, and a Greek letter on the +front. For example, the `L' key had an `L' and a two-way arrow on +the top, and the Greek letter lambda on the front. By pressing +this key with the right hand while playing an appropriate `chord' +with the left hand on the shift keys, you could get the following +results:</p> + +<blockquote> +<dl> +<dt>L</dt> + +<dd>lowercase l</dd> + +<dt>shift-L</dt> + +<dd>uppercase L</dd> + +<dt>front-L</dt> + +<dd>lowercase lambda</dd> + +<dt>front-shift-L</dt> + +<dd>uppercase lambda</dd> + +<dt>top-L</dt> + +<dd>two-way arrow (front and shift are ignored)</dd> +</dl> +</blockquote> + +<p>And of course each of these might also be typed with any +combination of the control, meta, hyper, and super keys. On this +keyboard, you could type over 8000 different characters! This +allowed the user to type very complicated mathematical text, and +also to have thousands of single-character commands at his +disposal. Many hackers were actually willing to memorize the +command meanings of that many characters if it reduced typing +time (this attitude obviously shaped the interface of EMACS). +Other hackers, however, thought having that many bucky bits was +overkill, and objected that such a keyboard can require three or +four hands to operate. See <b><a href="#buckybits">bucky +bits</a></b>, <b><a href="#cokebottle">cokebottle</a></b>, <b><a +href="#doublebucky">double bucky</a></b>, <b><a href="#metabit">meta bit</a></b>, <b><a href="#quadruplebucky">quadruple bucky</a></b>.</p> + +<p>Note: early versions of this entry incorrectly identified the +space-cadet keyboard with the `Knight keyboard'. Though both were +designed by Tom Knight, the latter term was properly applied only +to a keyboard used for ITS on the PDP-10 and modeled on the +Stanford keyboard (as described under <b><a href="#buckybits">bucky bits</a></b>). The true space-cadet +keyboard evolved from the first Knight keyboard.</p> + +<hr> +Node:<a name="spaceshipoperator">spaceship operator</a>, +Next:<a rel="next" href="#SPACEWAR">SPACEWAR</a>, Previous:<a +rel="previous" href="#space-cadetkeyboard">space-cadet +keyboard</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>spaceship operator</b> n.</p> + +<p>The glyph <code><=></code>, so-called apparently because +in the low-resolution constant-width font used on many terminals +it vaguely resembles a flying saucer. <b><a href="#Perl">Perl</a></b> uses this to denote the signum-of-difference +operation.</p> + +<hr> +Node:<a name="SPACEWAR">SPACEWAR</a>, Next:<a rel="next" href="#spaghetticode">spaghetti code</a>, Previous:<a rel="previous" href="#spaceshipoperator">spaceship operator</a>, +Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>SPACEWAR</b> n.</p> + +<p>A space-combat simulation game, inspired by E. E. "Doc" +Smith's "Lensman" books, in which two spaceships duel around a +central sun, shooting torpedoes at each other and jumping through +hyperspace. This game was first implemented on the PDP-1 at MIT +in 1962. In 1968-69, a descendant of the game motivated Ken +Thompson to build, in his spare time on a scavenged PDP-7, the +operating system that became <b><a href="#Unix">Unix</a></b>. +Less than nine years after that, SPACEWAR was commercialized as +one of the first video games; descendants are still <b><a href="#feep">feep</a></b>ing in video arcades everywhere.</p> + +<hr> +Node:<a name="spaghetticode">spaghetti code</a>, Next:<a rel="next" href="#spaghettiinheritance">spaghetti inheritance</a>, +Previous:<a rel="previous" href="#SPACEWAR">SPACEWAR</a>, Up:<a +rel="up" href="#chap19">= S =</a> <br> + + +<p><b>spaghetti code</b> n.</p> + +<p>Code with a complex and tangled control structure, esp. one +using many GOTOs, exceptions, or other `unstructured' branching +constructs. Pejorative. The synonym `kangaroo code' has been +reported, doubtless because such code has so many jumps in +it.</p> + +<hr> +Node:<a name="spaghettiinheritance">spaghetti inheritance</a>, +Next:<a rel="next" href="#spam">spam</a>, Previous:<a rel="previous" href="#spaghetticode">spaghetti code</a>, Up:<a +rel="up" href="#chap19">= S =</a> <br> + + +<p><b>spaghetti inheritance</b> n.</p> + +<p>[encountered among users of object-oriented languages that use +inheritance, such as Smalltalk] A convoluted class-subclass +graph, often resulting from carelessly deriving subclasses from +other classes just for the sake of reusing their code. Coined in +a (successful) attempt to discourage such practice, through +guilt-by-association with <b><a href="#spaghetticode">spaghetti code</a></b>.</p> + +<hr> +Node:<a name="spam">spam</a>, Next:<a rel="next" href="#spambait">spam bait</a>, Previous:<a rel="previous" href="#spaghettiinheritance">spaghetti inheritance</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>spam</b> vt.,vi.,n.</p> + +<p>[from "Monty Python's Flying Circus"] 1. To crash a program by +overrunning a fixed-size buffer with excessively large input +data. See also <b><a href="#bufferoverflow">buffer +overflow</a></b>, <b><a href="#overrunscrew">overrun +screw</a></b>, <b><a href="#smashthestack">smash the +stack</a></b>. 2. To cause a newsgroup to be flooded with +irrelevant or inappropriate messages. You can spam a newsgroup +with as little as one well- (or ill-) planned message (e.g. +asking "What do you think of abortion?" on <i>soc.women</i>). +This is often done with <b><a href="#cross-post">cross-post</a></b>ing (e.g. any message which is +crossposted to <i>alt.rush-limbaugh</i> and +<i>alt.politics.homosexuality</i> will almost inevitably spam +both groups). This overlaps with <b><a href="#troll">troll</a></b> behavior; the latter more specific term +has become more common. 3. To send many identical or +nearly-identical messages separately to a large number of Usenet +newsgroups. This is more specifically called `ECP', Excessive +Cross-Posting. This is one sure way to infuriate nearly everyone +on the Net. See also <b><a href="#velveeta">velveeta</a></b> and +<b><a href="#jello">jello</a></b>. 4. To bombard a newsgroup with +multiple copies of a message. This is more specifically called +`EMP', Excessive Multi-Posting. 5. To mass-mail unrequested +identical or nearly-identical email messages, particularly those +containing advertising. Especially used when the mail addresses +have been culled from network traffic or databases without the +consent of the recipients. Synonyms include <b><a href="#UCE">UCE</a></b>, <b><a href="#UBE">UBE</a></b>. 6. Any large, +annoying, quantity of output. For instance, someone on IRC who +walks away from their screen and comes back to find 200 lines of +text might say "Oh no, spam".</p> + +<p>The later definitions have become much more prevalent as the +Internet has opened up to non-techies, and to most people senses +3 4 and 5 are now primary. All three behaviors are considered +abuse of the net, and are almost universally grounds for +termination of the originator's email account or network +connection. In these senses the term `spam' has gone mainstream, +though without its original sense or folkloric freight - there is +apparently a widespread myth among <b><a href="#luser">luser</a></b>s that "spamming" is what happens when you +dump cans of Spam into a revolving fan.</p> + +<hr> +Node:<a name="spambait">spam bait</a>, Next:<a rel="next" +href="#spamblock">spamblock</a>, Previous:<a rel="previous" href="#spam">spam</a>, Up:<a rel="up" href="#chap19">= S =</a> +<br> + + +<p><b>spam bait</b> n.</p> + +<p>Email addresses included in, or comprising the entirety of, a +usenet message so that spammers mining a newsgroup with an <b><a +href="#addressharvester">address harvester</a></b> will +collect them. These addresses can be people who have offended or +annoyed the poster, or who are included so that a spammer will +spam an official, thereby causing himself trouble. One +particularly effective form of spam bait is the address of a +<b><a href="#teergrube">teergrube</a></b>.</p> + +<hr> +Node:<a name="spamblock">spamblock</a>, Next:<a rel="next" href="#spamhaus">spamhaus</a>, Previous:<a rel="previous" href="#spambait">spam bait</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>spamblock</b> /spam'blok/ n.</p> + +<p>[poss. by analogy to sunblock] Text inserted in an email +address to render it invalid and thus useless to spammers. For +example, the address `jrandom@hacker.org' might be transformed to +`jrandom@NOSPAM.hacker.org'. Adding spamblock to an address is +often referred to as `munging' it (see <b><a href="#munge">munge</a></b>)-. This evasion tactic depends on the fact +that most spammers collect names with some sort of <b><a href="#addressharvester">address harvester</a></b> on volumes too +high to de-mung by hand, but individual humans reading an email +message can readily spot and remove a spamblock in the from +address.</p> + +<p>Note: This is not actually a very effective tactic, and may +already be passing out of use in early 1999 after about two years +of life. In both mail and news, it's essentially impossible to +keep a smart address harvester from mining out the addresses in +the message header and trace lines. Therefore the only people who +can be protected are third parties mentioned by email address in +the message - not a common enough case to interest spammers.</p> + +<hr> +Node:<a name="spamhaus">spamhaus</a>, Next:<a rel="next" href="#spamvertize">spamvertize</a>, Previous:<a rel="previous" href="#spamblock">spamblock</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>spamhaus</b> spam'hows n.</p> + +<p>Pejorative term for an internet service provider that permits +or even encourages <b><a href="#spam">spam</a></b> mailings from +its systems. The plural is `spamhausen'. There is a web page +devoted to tracking +spamhausen.</p> + +<p>The most notorious of the spamhausen was Sanford Wallace's +Cyber Promotions Inc., shut down by a lawsuit on 16 October 1997. +The anniversary of the shutdown is celebrated on Usenet as Spam +Freedom Day, but lesser imitators of the Spamford still infest +various murky corners of the net. Since prosecution of spammers +became routine under the junk-fax laws and statues specifically +targeting spam, spamhausen have declined in relative importance; +today, hit-and-run attacks by spammers using <b><a href="#relayrape">relay rape</a></b> and <b><a href="#throwawayaccount">throwaway account</a></b>s on reputable +ISPs seem to account for most of the flow.</p> + +<hr> +Node:<a name="spamvertize">spamvertize</a>, Next:<a rel="next" +href="#spangle">spangle</a>, Previous:<a rel="previous" href="#spamhaus">spamhaus</a>, Up:<a rel="up" href="#chap19">= +S =</a> <br> + + +<p><b>spamvertize</b> v.</p> + +<p>To advertise using <b><a href="#spam">spam</a></b>. +Pejorative.</p> + +<hr> +Node:<a name="spangle">spangle</a>, Next:<a rel="next" href="#spawn">spawn</a>, Previous:<a rel="previous" href="#spamvertize">spamvertize</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>spangle</b> n.</p> + +<p>[UK] The singular of <b><a href="#bellsandwhistles">bells and whistles</a></b>. See also +<b><a href="#spungle">spungle</a></b>.</p> + +<hr> +Node:<a name="spawn">spawn</a>, Next:<a rel="next" href="#special-case">special-case</a>, Previous:<a rel="previous" +href="#spangle">spangle</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>spawn</b> n.,vi.</p> + +<p>1. [techspeak] In UNIX parlance, to create a child process +from within a process. Technically this is a `fork'; the term +`spawn' is a bit more general and is used for threads +(lightweight processes) as well as traditional heavyweight +processes. 2. In gaming, meant to indicate where (`spawn-point') +and when a player comes to life (or `re-spawns') after being +killed. Opposite of <b><a href="#frag">frag</a></b>.</p> + +<hr> +Node:<a name="special-case">special-case</a>, Next:<a rel="next" +href="#speedometer">speedometer</a>, Previous:<a rel="previous" +href="#spawn">spawn</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>special-case</b> vt.</p> + +<p>To write unique code to handle input to or situations arising +in a program that are somehow distinguished from normal +processing. This would be used for processing of mode switches or +interrupt characters in an interactive interface (as opposed, +say, to text entry or normal commands), or for processing of +<b><a href="#hiddenflag">hidden flag</a></b>s in the input of +a batch program or <b><a href="#filter">filter</a></b>.</p> + +<hr> +Node:<a name="speedometer">speedometer</a>, Next:<a rel="next" +href="#spell">spell</a>, Previous:<a rel="previous" href="#special-case">special-case</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>speedometer</b> n.</p> + +<p>A pattern of lights displayed on a linear set of LEDs (today) +or nixie tubes (yesterday, on ancient mainframes). The pattern is +shifted left every N times the operating system goes through its +<b><a href="#mainloop">main loop</a></b>. A swiftly moving +pattern indicates that the system is mostly idle; the speedometer +slows down as the system becomes overloaded. The speedometer on +Sun Microsystems hardware bounces back and forth like the eyes on +one of the Cylons from the wretched "Battlestar Galactica" TV +series.</p> + +<p>Historical note: One computer, the GE 600 (later Honeywell +6000) actually had an <i>analog</i> speedometer on the front +panel, calibrated in instructions executed per second.</p> + +<hr> +Node:<a name="spell">spell</a>, Next:<a rel="next" href="#spellingflame">spelling flame</a>, Previous:<a rel="previous" href="#speedometer">speedometer</a>, Up:<a rel="up" +href="#chap19">= S =</a> <br> + + +<p><b>spell</b> n.</p> + +<p>Syn. <b><a href="#incantation">incantation</a></b>.</p> + +<hr> +Node:<a name="spellingflame">spelling flame</a>, Next:<a rel="next" href="#spider">spider</a>, Previous:<a rel="previous" +href="#spell">spell</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>spelling flame</b> n. //</p> + +<p>[Usenet] A posting ostentatiously correcting a previous +article's spelling as a way of casting scorn on the point the +article was trying to make, instead of actually responding to +that point (compare <b><a href="#dictionaryflame">dictionary +flame</a></b>). Of course, people who are more than usually +slovenly spellers are prone to think <i>any</i> correction is a +spelling flame. It's an amusing comment on human nature that +spelling flames themselves often contain spelling errors.</p> + +<hr> +Node:<a name="spider">spider</a>, Next:<a rel="next" href="#spiderfood">spider food</a>, Previous:<a rel="previous" +href="#spellingflame">spelling flame</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>spider</b></p> + +<p>The Web-walking part of a search engine that collects pages +for indexing in the search engine's database. Also called a <b><a +href="#bot">bot</a></b>. The best-known spider is Scooter, the +web-walker for the Alta Vista search engine.</p> + +<hr> +Node:<a name="spiderfood">spider food</a>, Next:<a rel="next" +href="#spiffy">spiffy</a>, Previous:<a rel="previous" href="#spider">spider</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>spider food</b> n.</p> + +<p>Keywords embedded (usually invisibly) into a web page to +attract search engines (spiders). The intended result of +including spider food in one's web page is to insure that the +page appears high on the list of matching entries to a search +engine query. There are right and wrong ways to do this; the +right way is a discreet `meta keywords' tag, the wrong way is to +embed many repeats of a keyword in comments (and many search +engines now detect and ignore the latter).</p> + +<hr> +Node:<a name="spiffy">spiffy</a>, Next:<a rel="next" href="#spike">spike</a>, Previous:<a rel="previous" href="#spiderfood">spider food</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>spiffy</b> /spi'fee/ adj.</p> + +<p>1. Said of programs having a pretty, clever, or exceptionally +well-designed interface. "Have you seen the spiffy <b><a href="#X">X</a></b> version of <b><a href="#empire">empire</a></b> +yet?" 2. Said sarcastically of a program that is perceived to +have little more than a flashy interface going for it. Which +meaning should be drawn depends delicately on tone of voice and +context. This word was common mainstream slang during the 1940s, +in a sense close to 1.</p> + +<hr> +Node:<a name="spike">spike</a>, Next:<a rel="next" href="#spin">spin</a>, Previous:<a rel="previous" href="#spiffy">spiffy</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>spike</b> v.</p> + +<p>To defeat a selection mechanism by introducing a (sometimes +temporary) device that forces a specific result. The word is used +in several industries; telephone engineers refer to spiking a +relay by inserting a pin to hold the relay in either the closed +or open state, and railroaders refer to spiking a track switch so +that it cannot be moved. In programming environments it normally +refers to a temporary change, usually for testing purposes (as +opposed to a permanent change, which would be called <b><a href="#hardwired">hardwired</a></b>).</p> + +<hr> +Node:<a name="spin">spin</a>, Next:<a rel="next" href="#spl">spl</a>, Previous:<a rel="previous" href="#spike">spike</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>spin</b> vi.</p> + +<p>Equivalent to <b><a href="#buzz">buzz</a></b>. More common +among C and Unix programmers. See the discussion of `spinlock' +under <b><a href="#busy-wait">busy-wait</a></b>.</p> + +<hr> +Node:<a name="spl">spl</a>, Next:<a rel="next" href="#splashscreen">splash screen</a>, Previous:<a rel="previous" +href="#spin">spin</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>spl</b> /S-P-L/</p> + +<p>[abbrev, from Set Priority Level] The way traditional Unix +kernels implement mutual exclusion by running code at high +interrupt levels. Used in jargon to describe the act of tuning in +or tuning out ordinary communication. Classically, spl levels run +from 1 to 7; "Fred's at spl 6 today" would mean that he is very +hard to interrupt. "Wait till I finish this; I'll spl down then." +See also <b><a href="#interruptslockedout">interrupts +locked out</a></b>.</p> + +<hr> +Node:<a name="splashscreen">splash screen</a>, Next:<a rel="next" href="#splat">splat</a>, Previous:<a rel="previous" href="#spl">spl</a>, Up:<a rel="up" href="#chap19">= S =</a> +<br> + + +<p><b>splash screen</b> n.</p> + +<p>[Mac users] Syn. <b><a href="#banner">banner</a></b>, sense +3.</p> + +<hr> +Node:<a name="splat">splat</a>, Next:<a rel="next" href="#splatout">splat out</a>, Previous:<a rel="previous" href="#splashscreen">splash screen</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>splat</b> n.</p> + +<p>1. Name used in many places (DEC, IBM, and others) for the +asterisk (<code>*</code>) character (ASCII 0101010). This may +derive from the `squashed-bug' appearance of the asterisk on many +early line printers. 2. [MIT] Name used by some people for the +<code>#</code> character (ASCII 0100011). 3. The <b><a href="#featurekey">feature key</a></b> on a Mac (same as <b><a +href="#alt">alt</a></b>, sense 2). 4. obs. Name used by some +people for the Stanford/ITS extended ASCII circle-x character. +This character is also called `blobby' and `frob', among other +names; it is sometimes used by mathematicians as a notation for +`tensor product'. 5. obs. Name for the semi-mythical Stanford +extended ASCII circle-plus character. See also <b><a href="#ASCII">ASCII</a></b>.</p> + +<hr> +Node:<a name="splatout">splat out</a>, Next:<a rel="next" +href="#spod">spod</a>, Previous:<a rel="previous" href="#splat">splat</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>splat out</b> v.</p> + +<p>[Usenet] To partially obscure a potentially provocative word +by substituting <b><a href="#splat">splat</a></b> characters for +some of its letters (usually, but not always, the vowels). The +purpose is not to make the word unrecognizable but to make it a +mention rather than a use, so that no flamewar ensues. Words +often splatted out include N*z* (see <b><a href="#GodwinsLaw">Godwin's Law</a></b>), *v*l*t**n (anywhere +fundamentalists might be lurking), *b*rt**n, and g*n c*ntr*l. +Compare <b><a href="#UNX">UNX</a></b>.</p> + +<hr> +Node:<a name="spod">spod</a>, Next:<a rel="next" href="#spoiler">spoiler</a>, Previous:<a rel="previous" href="#splatout">splat out</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>spod</b> n.</p> + +<p>[UK] 1. A lower form of life found on <b><a href="#talkersystem">talker system</a></b>s and <b><a href="#MUD">MUD</a></b>s. The spod has few friends in <b><a href="#RL">RL</a></b> and uses talkers instead, finding communication +easier and preferable over the net. He has all the negative +traits of the <b><a href="#computergeek">computer geek</a></b> +without having any interest in computers per se. Lacking any +knowledge of or interest in how networks work, and considering +his access a God-given right, he is a major irritant to +sysadmins, clogging up lines in order to reach new MUDs, +following passed-on instructions on how to sneak his way onto +Internet ("Wow! It's in America!") and complaining when he is not +allowed to use busy routes. A true spod will start any +conversation with "Are you male or female?" (and follow it up +with "Got any good numbers/IDs/passwords?") and will not talk to +someone physically present in the same terminal room until they +log onto the same machine that he is using and enter talk mode. +Compare <b><a href="#newbie">newbie</a></b>, <b><a href="#tourist">tourist</a></b>, <b><a href="#weenie">weenie</a></b>, +<b><a href="#twink">twink</a></b>, <b><a href="#terminaljunkie">terminal junkie</a></b>, <b><a href="#warezd00dz">warez d00dz</a></b>. 2. A <b><a href="#backronym">backronym</a></b> for "Sole Purpose, Obtain a +Degree"; according to some self-described spods, this term is +used by indifferent students to condemn their harder-working +fellows. Compare the defiant adoption of the term `geek' in the +mid-1990s by people who would previously have been stigmatized by +it (see <b><a href="#computergeek">computer geek</a></b>). 3. +[obs.] An ordinary person; a <b><a href="#random">random</a></b>. +This is the meaning with which the term was coined, but the +inventor informs us he has himself accepted sense 1.</p> + +<hr> +Node:<a name="spoiler">spoiler</a>, Next:<a rel="next" href="#spoilerspace">spoiler space</a>, Previous:<a rel="previous" +href="#spod">spod</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>spoiler</b> n.</p> + +<p>[Usenet] 1. A remark which reveals important plot elements +from books or movies, thus denying the reader (of the article) +the proper suspense when reading the book or watching the movie. +2. Any remark which telegraphs the solution of a problem or +puzzle, thus denying the reader the pleasure of working out the +correct answer (see also <b><a href="#interesting">interesting</a></b>). Either sense readily forms +compounds like `total spoiler', `quasi-spoiler' and even +`pseudo-spoiler'.</p> + +<p>By convention, articles which are spoilers in either sense +should contain the word `spoiler' in the Subject: line, or +guarantee via various tricks that the answer appears only after +several screens-full of warning, or conceal the sensitive +information via <b><a href="#rot13">rot13</a></b>, <b><a href="#spoilerspace">spoiler space</a></b> or some combination of +these techniques.</p> + +<hr> +Node:<a name="spoilerspace">spoiler space</a>, Next:<a rel="next" href="#sponge">sponge</a>, Previous:<a rel="previous" +href="#spoiler">spoiler</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>spoiler space</b></p> + +<p>[also `spoiler spoo'] A screenful of blank lines (and, often, +form-feeds) deliberately inserted in a message following a <b><a +href="#spoiler">spoiler</a></b> warning, so the actual spoiler +can't be seen without hitting a key.</p> + +<hr> +Node:<a name="sponge">sponge</a>, Next:<a rel="next" href="#spoof">spoof</a>, Previous:<a rel="previous" href="#spoilerspace">spoiler space</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>sponge</b> n.</p> + +<p>[Unix] A special case of a <b><a href="#filter">filter</a></b> +that reads its entire input before writing any output; the +canonical example is a sort utility. Unlike most filters, a +sponge can conveniently overwrite the input file with the output +data stream. If a file system has versioning (as ITS did and VMS +does now) the sponge/filter distinction loses its usefulness, +because directing filter output would just write a new version. +See also <b><a href="#slurp">slurp</a></b>.</p> + +<hr> +Node:<a name="spoof">spoof</a>, Next:<a rel="next" href="#spool">spool</a>, Previous:<a rel="previous" href="#sponge">sponge</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>spoof</b> vi.</p> + +<p>To capture, alter, and retransmit a communication stream in a +way that misleads the recipient. As used by hackers, refers +especially to altering TCP/IP packet source addresses or other +packet-header data in order to masquerade as a trusted machine. +This term has become very widespread and is borderline +techspeak.</p> + +<hr> +Node:<a name="spool">spool</a>, Next:<a rel="next" href="#spoolfile">spool file</a>, Previous:<a rel="previous" href="#spoof">spoof</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>spool</b> vi.</p> + +<p>[from early IBM `Simultaneous Peripheral Operation On-Line', +but is widely thought to be a <b><a href="#backronym">backronym</a></b>] To send files to some device or +program (a `spooler') that queues them up and does something +useful with them later. Without qualification, the spooler is the +`print spooler' controlling output of jobs to a printer; but the +term has been used in connection with other peripherals +(especially plotters and graphics devices) and occasionally even +for input devices. See also <b><a href="#demon">demon</a></b>.</p> + +<hr> +Node:<a name="spoolfile">spool file</a>, Next:<a rel="next" +href="#spungle">spungle</a>, Previous:<a rel="previous" href="#spool">spool</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>spool file</b> n.</p> + +<p>Any file to which data is <b><a href="#spool">spool</a></b>ed +to await the next stage of processing. Especially used in +circumstances where spooling the data copes with a mismatch +between speeds in two devices or pieces of software. For example, +when you send mail under Unix, it's typically copied to a spool +file to await a transport <b><a href="#demon">demon</a></b>'s +attentions. This is borderline techspeak.</p> + +<hr> +Node:<a name="spungle">spungle</a>, Next:<a rel="next" href="#squaretape">square tape</a>, Previous:<a rel="previous" +href="#spoolfile">spool file</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>spungle</b> n.</p> + +<p>[Durham, UK; portmanteau, <b><a href="#spangle">spangle</a></b> + bungle] A <b><a href="#spangle">spangle</a></b> of no actual usefulness. Example: +Roger the Bent Paperclip in Microsoft Word '98. A spungle's only +virtue is that it looks pretty, unless you find creeping +featurism ugly.</p> + +<hr> +Node:<a name="squaretape">square tape</a>, Next:<a rel="next" +href="#squirrelcide">squirrelcide</a>, Previous:<a rel="previous" +href="#spungle">spungle</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>square tape</b> n.</p> + +<p>Mainframe magnetic tape cartridges for use with IBM 3480 or +compatible tape drives; or QIC tapes used on workstations and +micros. The term comes from the square (actually rectangular) +shape of the cartridges; contrast <b><a href="#roundtape">round tape</a></b>.</p> + +<hr> +Node:<a name="squirrelcide">squirrelcide</a>, Next:<a rel="next" +href="#stack">stack</a>, Previous:<a rel="previous" href="#squaretape">square tape</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>squirrelcide</b> n.</p> + +<p>[common on Usenet's <i>comp.risks</i> newsgroup.] (alt. +`squirrelicide') What all too frequently happens when a squirrel +decides to exercise its species's unfortunate penchant for +shorting out power lines with their little furry bodies. Result: +one dead squirrel, one down computer installation. In this +situation, the computer system is said to have been +squirrelcided.</p> + +<hr> +Node:<a name="stack">stack</a>, Next:<a rel="next" href="#stackpuke">stack puke</a>, Previous:<a rel="previous" href="#squirrelcide">squirrelcide</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>stack</b> n.</p> + +<p>The set of things a person has to do in the future. One speaks +of the next project to be attacked as having risen to the top of +the stack. "I'm afraid I've got real work to do, so this'll have +to be pushed way down on my stack." "I haven't done it yet +because every time I pop my stack something new gets pushed." If +you are interrupted several times in the middle of a +conversation, "My stack overflowed" means "I forget what we were +talking about." The implication is that more items were pushed +onto the stack than could be remembered, so the least recent +items were lost. The usual physical example of a stack is to be +found in a cafeteria: a pile of plates or trays sitting on a +spring in a well, so that when you put one on the top they all +sink down, and when you take one off the top the rest spring up a +bit. See also <b><a href="#push">push</a></b> and <b><a href="#pop">pop</a></b>.</p> + +<p>At MIT, <b><a href="#PDL">PDL</a></b> used to be a more common +synonym for <b><a href="#stack">stack</a></b> in all these +contexts, and this may still be true. Everywhere else <b><a href="#stack">stack</a></b> seems to be the preferred term. <b><a +href="#Knuth">Knuth</a></b> ("The Art of Computer Programming", +second edition, vol. 1, p. 236) says:</p> + +<blockquote>Many people who realized the importance of stacks and +queues independently have given other names to these structures: +stacks have been called push-down lists, reversion storages, +cellars, nesting stores, piles, last-in-first-out ("LIFO") lists, +and even yo-yo lists!</blockquote> + +<hr> +Node:<a name="stackpuke">stack puke</a>, Next:<a rel="next" +href="#stalepointerbug">stale pointer bug</a>, Previous:<a +rel="previous" href="#stack">stack</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>stack puke</b> n.</p> + +<p>Some processor architectures are said to `puke their guts onto +the stack' to save their internal state during exception +processing. The Motorola 68020, for example, regurgitates up to +92 bytes on a bus fault. On a pipelined machine, this can take a +while.</p> + +<hr> +Node:<a name="stalepointerbug">stale pointer bug</a>, +Next:<a rel="next" href="#starout">star out</a>, Previous:<a +rel="previous" href="#stackpuke">stack puke</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>stale pointer bug</b> n.</p> + +<p>Synonym for <b><a href="#aliasingbug">aliasing bug</a></b> +used esp. among microcomputer hackers.</p> + +<hr> +Node:<a name="starout">star out</a>, Next:<a rel="next" href="#state">state</a>, Previous:<a rel="previous" href="#stalepointerbug">stale pointer bug</a>, Up:<a rel="up" +href="#chap19">= S =</a> <br> + + +<p><b>star out</b> v.</p> + +<p>[University of York, England] To replace a user's encrypted +password in /etc/passwd with a single asterisk. Under Unix this +is not a legal encryption of any password; hence the user is not +permitted to log in. In general, accounts like adm, news, and +daemon are permanently "starred out"; occasionally a real user +might have the this inflicted upon him/her as a punishment, e.g. +"Graham was starred out for playing Omega in working hours". Also +occasionally known as The Order Of The Gold Star in this context. +"Don't do that, or you'll be awarded the Order of the Gold +Star..." Compare <b><a href="#disusered">disusered</a></b>.</p> + +<hr> +Node:<a name="state">state</a>, Next:<a rel="next" href="#stealthmanager">stealth manager</a>, Previous:<a rel="previous" href="#starout">star out</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>state</b> n.</p> + +<p>1. Condition, situation. "What's the state of your latest +hack?" "It's winning away." "The system tried to read and write +the disk simultaneously and got into a totally <b><a href="#wedged">wedged</a></b> state." The standard question "What's +your state?" means "What are you doing?" or "What are you about +to do?" Typical answers are "about to gronk out", or "hungry". +Another standard question is "What's the state of the world?", +meaning "What's new?" or "What's going on?". The more terse and +humorous way of asking these questions would be "State-p?". +Another way of phrasing the first question under sense 1 would be +"state-p latest hack?". 2. Information being maintained in +non-permanent memory (electronic or human).</p> + +<hr> +Node:<a name="stealthmanager">stealth manager</a>, Next:<a +rel="next" href="#steam-powered">steam-powered</a>, Previous:<a +rel="previous" href="#state">state</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>stealth manager</b> n.</p> + +<p>[Corporate DP] A manager that appears out of nowhere, promises +undeliverable software to unknown end users, and vanishes before +the programming staff realizes what has happened. See <b><a href="#smokeandmirrors">smoke and mirrors</a></b>.</p> + +<hr> +Node:<a name="steam-powered">steam-powered</a>, Next:<a rel="next" href="#STFW">STFW</a>, Previous:<a rel="previous" href="#stealthmanager">stealth manager</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>steam-powered</b> adj.</p> + +<p>Old-fashioned or underpowered; archaic. This term does not +have a strong negative loading and may even be used +semi-affectionately for something that clanks and wheezes a lot +but hangs in there doing the job.</p> + +<hr> +Node:<a name="STFW">STFW</a>, Next:<a rel="next" href="#stiffy">stiffy</a>, Previous:<a rel="previous" href="#steam-powered">steam-powered</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>STFW</b> imp. /S-T-F-W/</p> + +<p>[Usenet] Commmon abbreviation for "Search The Fucking Web", a +suggestion that what you're asking for is a query better handled +by a search engine than a human being. Usage is common and +exactly parallel to both senses of <b><a href="#RTFM">RTFM</a></b>.</p> + +<hr> +Node:<a name="stiffy">stiffy</a>, Next:<a rel="next" href="#stirfriedrandom">stir-fried random</a>, Previous:<a rel="previous" href="#STFW">STFW</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>stiffy</b> n.</p> + +<p>3.5-inch <b><a href="#microfloppies">microfloppies</a></b>, so +called because their jackets are more rigid than those of the +5.25-inch and the (now totally obsolete) 8-inch floppy. Elsewhere +this might be called a `firmy'. For some odd reason, several +sources have taken the trouble to inform us that this term is +widespread in South Africa.</p> + +<hr> +Node:<a name="stirfriedrandom">stir-fried random</a>, Next:<a +rel="next" href="#stompon">stomp on</a>, Previous:<a rel="previous" href="#stiffy">stiffy</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>stir-fried random</b> n.</p> + +<p>(alt. `stir-fried mumble') Term used for the best dish of many +of those hackers who can cook. Consists of random fresh veggies +and meat wokked with random spices. Tasty and economical. See +<b><a href="#random">random</a></b>, <b><a href="#great-wall">great-wall</a></b>, <b><a href="#ravs">ravs</a></b>, <b><a href="#laserchicken">laser +chicken</a></b>, <b><a href="#orientalfood">oriental +food</a></b>; see also <b><a href="#mumble">mumble</a></b>.</p> + +<hr> +Node:<a name="stompon">stomp on</a>, Next:<a rel="next" href="#StoneAge">Stone Age</a>, Previous:<a rel="previous" href="#stirfriedrandom">stir-fried random</a>, Up:<a rel="up" +href="#chap19">= S =</a> <br> + + +<p><b>stomp on</b> vt.</p> + +<p>To inadvertently overwrite something important, usually +automatically. "All the work I did this weekend got stomped on +last night by the nightly server script." Compare <b><a href="#scribble">scribble</a></b>, <b><a href="#mangle">mangle</a></b>, <b><a href="#trash">trash</a></b>, +<b><a href="#scrog">scrog</a></b>, <b><a href="#roach">roach</a></b>.</p> + +<hr> +Node:<a name="StoneAge">Stone Age</a>, Next:<a rel="next" +href="#stoneknivesandbearskins">stone knives and +bearskins</a>, Previous:<a rel="previous" href="#stompon">stomp on</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>Stone Age</b> n.,adj.</p> + +<p>1. In computer folklore, an ill-defined period from ENIAC (ca. +1943) to the mid-1950s; the great age of electromechanical <b><a +href="#dinosaur">dinosaur</a></b>s. Sometimes used for the entire +period up to 1960-61 (see <b><a href="#IronAge">Iron +Age</a></b>); however, it is funnier and more descriptive to +characterize the latter period in terms of a `Bronze Age' era of +transistor-logic, pre-ferrite-<b><a href="#core">core</a></b> +machines with drum or CRT mass storage (as opposed to just +mercury delay lines and/or relays). See also <b><a href="#IronAge">Iron Age</a></b>. 2. More generally, a pejorative +for any crufty, ancient piece of hardware or software technology. +Note that this is used even by people who were there for the +<b><a href="#StoneAge">Stone Age</a></b> (sense 1).</p> + +<hr> +Node:<a name="stoneknivesandbearskins">stone knives and +bearskins</a>, Next:<a rel="next" href="#stoppage">stoppage</a>, +Previous:<a rel="previous" href="#StoneAge">Stone Age</a>, +Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>stone knives and bearskins</b> n.</p> + +<p>[from the Star Trek Classic episode "The City on the Edge of +Forever"] A term traditionally used to describe (and deprecate) +computing environments that are grotesquely primitive in light of +what is known about good ways to design things. As in "Don't get +too used to the facilities here. Once you leave SAIL it's stone +knives and bearskins as far as the eye can see". Compare <b><a +href="#steam-powered">steam-powered</a></b>.</p> + +<hr> +Node:<a name="stoppage">stoppage</a>, Next:<a rel="next" href="#store">store</a>, Previous:<a rel="previous" href="#stoneknivesandbearskins">stone knives and +bearskins</a>, Up:<a rel="up" href="#chap19">= S =</a> +<br> + + +<p><b>stoppage</b> /sto'p*j/ n.</p> + +<p>Extreme <b><a href="#lossage">lossage</a></b> that renders +something (usually something vital) completely unusable. "The +recent system stoppage was caused by a <b><a href="#fried">fried</a></b> transformer."</p> + +<hr> +Node:<a name="store">store</a>, Next:<a rel="next" href="#strided">strided</a>, Previous:<a rel="previous" href="#stoppage">stoppage</a>, Up:<a rel="up" href="#chap19">= +S =</a> <br> + + +<p><b>store</b> n.</p> + +<p>[prob. from techspeak `main store'] In some varieties of +Commonwealth hackish, the preferred synonym for <b><a href="#core">core</a></b>. Thus, `bringing a program into store' means +not that one is returning shrink-wrapped software but that a +program is being <b><a href="#swap">swap</a></b>ped in.</p> + +<hr> +Node:<a name="strided">strided</a>, Next:<a rel="next" href="#stroke">stroke</a>, Previous:<a rel="previous" href="#store">store</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>strided</b> /stri:'d*d/ adj.</p> + +<p>[scientific computing] Said of a sequence of memory reads and +writes to addresses, each of which is separated from the last by +a constant interval called the `stride length'. These can be a +worst-case access pattern for the standard memory-caching schemes +when the stride length is a multiple of the cache line size. +Strided references are often generated by loops through an array, +and (if your data is large enough that access-time is +significant) it can be worthwhile to tune for better locality by +inverting double loops or by partially unrolling the outer loop +of a loop nest. This usage is borderline techspeak; the related +term `memory stride' is definitely techspeak.</p> + +<hr> +Node:<a name="stroke">stroke</a>, Next:<a rel="next" href="#strudel">strudel</a>, Previous:<a rel="previous" href="#strided">strided</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>stroke</b> n.</p> + +<p>Common name for the slant (`/', ASCII 0101111) character. See +<b><a href="#ASCII">ASCII</a></b> for other synonyms.</p> + +<hr> +Node:<a name="strudel">strudel</a>, Next:<a rel="next" href="#stubroutine">stubroutine</a>, Previous:<a rel="previous" href="#stroke">stroke</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>strudel</b> n.</p> + +<p>Common (spoken) name for the at-sign (`@', ASCII 1000000) +character. See <b><a href="#ASCII">ASCII</a></b> for other +synonyms.</p> + +<hr> +Node:<a name="stubroutine">stubroutine</a>, Next:<a rel="next" +href="#studly">studly</a>, Previous:<a rel="previous" href="#strudel">strudel</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>stubroutine</b> /stuhb'roo-teen/ n.</p> + +<p>[contraction of `stub subroutine'] Tiny, often vacuous +placeholder for a subroutine that is to be written or fleshed out +later.</p> + +<hr> +Node:<a name="studly">studly</a>, Next:<a rel="next" href="#studlycaps">studlycaps</a>, Previous:<a rel="previous" href="#stubroutine">stubroutine</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>studly</b> adj.</p> + +<p>Impressive; powerful. Said of code and designs which exhibit +both complexity and a virtuoso flair. Has connotations similar to +<b><a href="#hairy">hairy</a></b> but is more positive in tone. +Often in the emphatic `most studly' or as noun-form `studliness'. +"Smail 3.0's configuration parser is most studly."</p> + +<hr> +Node:<a name="studlycaps">studlycaps</a>, Next:<a rel="next" +href="#stunning">stunning</a>, Previous:<a rel="previous" href="#studly">studly</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>studlycaps</b> /stuhd'lee-kaps/ n.</p> + +<p>A hackish form of silliness similar to <b><a href="#BiCapitalization">BiCapitalization</a></b> for trademarks, but +applied randomly and to arbitrary text rather than to trademarks. +ThE oRigiN and SigNificaNce of thIs pRacTicE iS oBscuRe.</p> + +<hr> +Node:<a name="stunning">stunning</a>, Next:<a rel="next" href="#stupid-sort">stupid-sort</a>, Previous:<a rel="previous" href="#studlycaps">studlycaps</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>stunning</b> adj.</p> + +<p>Mind-bogglingly stupid. Usually used in sarcasm. "You want to +code <i>what</i> in ADA? That's a <small>...</small> stunning +idea!"</p> + +<hr> +Node:<a name="stupid-sort">stupid-sort</a>, Next:<a rel="next" +href="#Stupids">Stupids</a>, Previous:<a rel="previous" href="#stunning">stunning</a>, Up:<a rel="up" href="#chap19">= +S =</a> <br> + + +<p><b>stupid-sort</b> n.</p> + +<p>Syn. <b><a href="#bogo-sort">bogo-sort</a></b>.</p> + +<hr> +Node:<a name="Stupids">Stupids</a>, Next:<a rel="next" href="#SturgeonsLaw">Sturgeon's Law</a>, Previous:<a rel="previous" href="#stupid-sort">stupid-sort</a>, Up:<a rel="up" +href="#chap19">= S =</a> <br> + + +<p><b>Stupids</b> n.</p> + +<p>Term used by <b><a href="#samurai">samurai</a></b> for the +<b><a href="#suit">suit</a></b>s who employ them; succinctly +expresses an attitude at least as common, though usually better +disguised, among other subcultures of hackers. There may be +intended reference here to an SF story originally published in +1952 but much anthologized since, Mark Clifton's "Star, Bright". +In it, a super-genius child classifies humans into a very few +`Brights' like herself, a huge majority of `Stupids', and a +minority of `Tweens', the merely ordinary geniuses.</p> + +<hr> +Node:<a name="SturgeonsLaw">Sturgeon's Law</a>, Next:<a rel="next" href="#suckingmud">sucking mud</a>, Previous:<a rel="previous" href="#Stupids">Stupids</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>Sturgeon's Law</b> prov.</p> + +<p>"Ninety percent of everything is crap". Derived from a quote +by science fiction author Theodore Sturgeon, who once said, +"Sure, 90% of science fiction is crud. That's because 90% of +everything is crud." Oddly, when Sturgeon's Law is cited, the +final word is almost invariably changed to `crap'. Compare <b><a +href="#HanlonsRazor">Hanlon's Razor</a></b>, <b><a href="#NinetyNinetyRule">Ninety-Ninety Rule</a></b>. Though this +maxim originated in SF fandom, most hackers recognize it and are +all too aware of its truth.</p> + +<hr> +Node:<a name="suckingmud">sucking mud</a>, Next:<a rel="next" +href="#sufficientlysmall">sufficiently small</a>, Previous:<a +rel="previous" href="#SturgeonsLaw">Sturgeon's Law</a>, Up:<a +rel="up" href="#chap19">= S =</a> <br> + + +<p><b>sucking mud</b> adj.</p> + +<p>[Applied Data Research] (also `pumping mud') Crashed or <b><a +href="#wedged">wedged</a></b>. Usually said of a machine that +provides some service to a network, such as a file server. This +Dallas regionalism derives from the East Texas oilfield lament, +"Shut 'er down, Ma, she's a-suckin' mud". Often used as a query. +"We are going to reconfigure the network, are you ready to suck +mud?"</p> + +<hr> +Node:<a name="sufficientlysmall">sufficiently small</a>, +Next:<a rel="next" href="#suit">suit</a>, Previous:<a rel="previous" href="#suckingmud">sucking mud</a>, Up:<a rel="up" +href="#chap19">= S =</a> <br> + + +<p><b>sufficiently small</b> adj.</p> + +<p>Syn. <b><a href="#suitablysmall">suitably +small</a></b>.</p> + +<hr> +Node:<a name="suit">suit</a>, Next:<a rel="next" href="#suitablewin">suitable win</a>, Previous:<a rel="previous" +href="#sufficientlysmall">sufficiently small</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>suit</b> n.</p> + +<p>1. Ugly and uncomfortable `business clothing' often worn by +non-hackers. Invariably worn with a `tie', a strangulation device +that partially cuts off the blood supply to the brain. It is +thought that this explains much about the behavior of +suit-wearers. Compare <b><a href="#droid">droid</a></b>. 2. A +person who habitually wears suits, as distinct from a techie or +hacker. See <b><a href="#pointy-haired">pointy-haired</a></b>, +<b><a href="#burble">burble</a></b>, <b><a href="#management">management</a></b>, <b><a href="#Stupids">Stupids</a></b>, <b><a href="#SNAFUprinciple">SNAFU +principle</a></b>, <b><a href="#PHB">PHB</a></b>, and <b><a href="#brain-damaged">brain-damaged</a></b>.</p> + +<hr> +Node:<a name="suitablewin">suitable win</a>, Next:<a rel="next" href="#suitablysmall">suitably small</a>, Previous:<a +rel="previous" href="#suit">suit</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>suitable win</b> n.</p> + +<p>See <b><a href="#win">win</a></b>.</p> + +<hr> +Node:<a name="suitablysmall">suitably small</a>, Next:<a rel="next" href="#Sun">Sun</a>, Previous:<a rel="previous" href="#suitablewin">suitable win</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>suitably small</b> adj.</p> + +<p>[perverted from mathematical jargon]</p> + +<p>An expression used ironically to characterize unquantifiable +behavior that differs from expected or required behavior. For +example, suppose a newly created program came up with a correct +full-screen display, and one publicly exclaimed: "It works!" +Then, if the program dumped core on the first mouse click, one +might add: "Well, for suitably small values of `works'." Compare +the characterization of pi under <b><a href="#randomnumbers">random numbers</a></b>.</p> + +<hr> +Node:<a name="Sun">Sun</a>, Next:<a rel="next" href="#sunlounge">sun lounge</a>, Previous:<a rel="previous" href="#suitablysmall">suitably small</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>Sun</b> n.</p> + +<p>Sun Microsystems. Hackers remember that the name was +originally an acronym, Stanford University Network. Sun started +out around 1980 with some hardware hackers (mainly) from Stanford +talking to some software hackers (mainly) from UC Berkeley; Sun's +original technology concept married a clever board design based +on the Motorola 68000 to <b><a href="#BSD">BSD</a></b> Unix. Sun +went on to lead the worstation industry through the 1980s, and +for years afterwards remained an engineering-driven company and a +good place for hackers to work. Though Sun drifted away from its +techie origins after 1990 and has since made some strategic moves +that disappointed and annoyed many hackers (especially by +maintaining proprietary control of Java and rejecting Linux), +it's still considered within the family in much the same way +<b><a href="#DEC">DEC</a></b> was in the 1970s and early +1980s.</p> + +<hr> +Node:<a name="sunlounge">sun lounge</a>, Next:<a rel="next" +href="#sun-stools">sun-stools</a>, Previous:<a rel="previous" +href="#Sun">Sun</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>sun lounge</b> n.</p> + +<p>[UK] The room where all the Sun workstations live. The humor +in this term comes from the fact that it's also in mainstream use +to describe a solarium, and all those Sun workstations clustered +together give off an amazing amount of heat.</p> + +<hr> +Node:<a name="sun-stools">sun-stools</a>, Next:<a rel="next" +href="#sunspots">sunspots</a>, Previous:<a rel="previous" href="#sunlounge">sun lounge</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>sun-stools</b> n.</p> + +<p>Unflattering hackerism for SunTools, a pre-X windowing +environment notorious in its day for size, slowness, and +misfeatures. <b><a href="#X">X</a></b>, however, is larger and +(some claim) slower; see <b><a href="#second-systemeffect">second-system effect</a></b>.</p> + +<hr> +Node:<a name="sunspots">sunspots</a>, Next:<a rel="next" href="#supersourcequench">super source quench</a>, Previous:<a +rel="previous" href="#sun-stools">sun-stools</a>, Up:<a rel="up" +href="#chap19">= S =</a> <br> + + +<p><b>sunspots</b> n.</p> + +<p>1. Notional cause of an odd error. "Why did the program +suddenly turn the screen blue?" "Sunspots, I guess." 2. Also the +cause of <b><a href="#bitrot">bit rot</a></b> -- from the myth +that sunspots will increase <b><a href="#cosmicrays">cosmic +rays</a></b>, which can flip single bits in memory. See also +<b><a href="#phaseofthemoon">phase of the +moon</a></b>.</p> + +<hr> +Node:<a name="supersourcequench">super source quench</a>, +Next:<a rel="next" href="#superloser">superloser</a>, Previous:<a +rel="previous" href="#sunspots">sunspots</a>, Up:<a rel="up" +href="#chap19">= S =</a> <br> + + +<p><b>super source quench</b> n.</p> + +<p>A special packet designed to shut up an Internet host. The +Internet Protocol (IP) has a control message called Source Quench +that asks a host to transmit more slowly on a particular +connection to avoid congestion. It also has a Redirect control +message intended to instruct a host to send certain packets to a +different local router. A "super source quench" is actually a +redirect control packet, forged to look like it came from a local +router, that instructs a host to send all packets to its own +local loopback address. This will effectively tie many Internet +hosts up in knots. Compare <b><a href="#Godzillagram">Godzillagram</a></b>, <b><a href="#breath-of-lifepacket">breath-of-life packet</a></b>.</p> + +<hr> +Node:<a name="superloser">superloser</a>, Next:<a rel="next" +href="#superprogrammer">superprogrammer</a>, Previous:<a rel="previous" href="#supersourcequench">super source +quench</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>superloser</b> n.</p> + +<p>[Unix] A superuser with no clue - someone with root privileges +on a Unix system and no idea what he/she is doing, the moral +equivalent of a three-year-old with an unsafetied Uzi. Anyone who +thinks this is an uncommon situation reckons without the +territorial urges of <b><a href="#management">management</a></b>.</p> + +<hr> +Node:<a name="superprogrammer">superprogrammer</a>, Next:<a rel="next" href="#superuser">superuser</a>, Previous:<a rel="previous" href="#superloser">superloser</a>, Up:<a rel="up" +href="#chap19">= S =</a> <br> + + +<p><b>superprogrammer</b> n.</p> + +<p>A prolific programmer; one who can code exceedingly well and +quickly. Not all hackers are superprogrammers, but many are. +(Productivity can vary from one programmer to another by three +orders of magnitude. For example, one programmer might be able to +write an average of 3 lines of working code in one day, while +another, with the proper tools, might be able to write 3,000. +This range is astonishing; it is matched in very few other areas +of human endeavor.) The term `superprogrammer' is more commonly +used within such places as IBM than in the hacker community. It +tends to stress naive measures of productivity and to underweight +creativity, ingenuity, and getting the job <i>done</i> -- and +to sidestep the question of whether the 3,000 lines of code do +more or less useful work than three lines that do the <b><a href="#RightThing">Right Thing</a></b>. Hackers tend to prefer the +terms <b><a href="#hacker">hacker</a></b> and <b><a href="#wizard">wizard</a></b>.</p> + +<hr> +Node:<a name="superuser">superuser</a>, Next:<a rel="next" href="#support">support</a>, Previous:<a rel="previous" href="#superprogrammer">superprogrammer</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>superuser</b> n.</p> + +<p>[Unix] Syn. <b><a href="#root">root</a></b>, <b><a href="#avatar">avatar</a></b>. This usage has spread to non-Unix +environments; the superuser is any account with all <b><a href="#wheel">wheel</a></b> bits on. A more specific term than <b><a +href="#wheel">wheel</a></b>.</p> + +<hr> +Node:<a name="support">support</a>, Next:<a rel="next" href="#surf">surf</a>, Previous:<a rel="previous" href="#superuser">superuser</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>support</b> n.</p> + +<p>After-sale handholding; something many software vendors +promise but few deliver. To hackers, most support people are +useless -- because by the time a hacker calls support he or she +will usually know the software and the relevant manuals better +than the support people (sadly, this is <i>not</i> a joke or +exaggeration). A hacker's idea of `support' is a +tête-à-tête with the software's designer.</p> + +<hr> +Node:<a name="surf">surf</a>, Next:<a rel="next" href="#SuzieCOBOL">Suzie COBOL</a>, Previous:<a rel="previous" +href="#support">support</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>surf</b> v.</p> + +<p>[from the `surf' idiom for rapidly flipping TV channels] To +traverse the Internet in search of interesting stuff, used esp. +if one is doing so with a World Wide Web browser. It is also +common to speak of `surfing in' to a particular resource.</p> + +<p>Hackers adopted this term early, but many have stopped using +it since it went completely mainstream around 1995. The passive, +couch-potato connotations that go with TV channel surfing were +never pleasant, and hearing non-hackers wax enthusiastic about +"surfing the net" tends to make hackers feel a bit as though +their home is being overrun by ignorami.</p> + +<hr> +Node:<a name="SuzieCOBOL">Suzie COBOL</a>, Next:<a rel="next" +href="#swab">swab</a>, Previous:<a rel="previous" href="#surf">surf</a>, Up:<a rel="up" href="#chap19">= S =</a> +<br> + + +<p><b>Suzie COBOL</b> /soo'zee koh'bol/</p> + +<p>1. [IBM: prob. from Frank Zappa's `Suzy Creamcheese'] n. A +coder straight out of training school who knows everything except +the value of comments in plain English. Also (fashionable among +personkind wishing to avoid accusations of sexism) `Sammy Cobol' +or (in some non-IBM circles) `Cobol Charlie'. 2. [proposed] +Meta-name for any <b><a href="#codegrinder">code +grinder</a></b>, analogous to <b><a href="#JRandomHacker">J. Random Hacker</a></b>.</p> + +<hr> +Node:<a name="swab">swab</a>, Next:<a rel="next" href="#swap">swap</a>, Previous:<a rel="previous" href="#SuzieCOBOL">Suzie COBOL</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>swab</b> /swob/</p> + +<p>[From the mnemonic for the PDP-11 `SWAp Byte' instruction, as +immortalized in the <code>dd(1)</code> option +<code>conv=swab</code> (see <b><a href="#dd">dd</a></b>)] 1. vt. +To solve the <b><a href="#NUXIproblem">NUXI problem</a></b> by +swapping bytes in a file. 2. n. The program in V7 Unix used to +perform this action, or anything functionally equivalent to it. +See also <b><a href="#big-endian">big-endian</a></b>, <b><a href="#little-endian">little-endian</a></b>, <b><a href="#middle-endian">middle-endian</a></b>, <b><a href="#bytesexual">bytesexual</a></b>.</p> + +<hr> +Node:<a name="swap">swap</a>, Next:<a rel="next" href="#swapspace">swap space</a>, Previous:<a rel="previous" href="#swab">swab</a>, Up:<a rel="up" href="#chap19">= S =</a> +<br> + + +<p><b>swap</b> vt.</p> + +<p>1. [techspeak] To move information from a fast-access memory +to a slow-access memory (`swap out'), or vice versa (`swap in'). +Often refers specifically to the use of disks as `virtual +memory'. As pieces of data or program are needed, they are +swapped into <b><a href="#core">core</a></b> for processing; when +they are no longer needed they may be swapped out again. 2. The +jargon use of these terms analogizes people's short-term memories +with core. Cramming for an exam might be spoken of as swapping +in. If you temporarily forget someone's name, but then remember +it, your excuse is that it was swapped out. To `keep something +swapped in' means to keep it fresh in your memory: "I reread the +TECO manual every few months to keep it swapped in." If someone +interrupts you just as you got a good idea, you might say "Wait a +moment while I swap this out", implying that a piece of paper is +your extra-somatic memory and that if you don't swap the idea out +by writing it down it will get overwritten and lost as you talk. +Compare <b><a href="#pagein">page in</a></b>, <b><a href="#pageout">page out</a></b>.</p> + +<hr> +Node:<a name="swapspace">swap space</a>, Next:<a rel="next" +href="#swappedin">swapped in</a>, Previous:<a rel="previous" +href="#swap">swap</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>swap space</b> n.</p> + +<p>Storage space, especially temporary storage space used during +a move or reconfiguration. "I'm just using that corner of the +machine room for swap space."</p> + +<hr> +Node:<a name="swappedin">swapped in</a>, Next:<a rel="next" +href="#swappedout">swapped out</a>, Previous:<a rel="previous" +href="#swapspace">swap space</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>swapped in</b> n.</p> + +<p>See <b><a href="#swap">swap</a></b>. See also <b><a href="#pagein">page in</a></b>.</p> + +<hr> +Node:<a name="swappedout">swapped out</a>, Next:<a rel="next" +href="#swizzle">swizzle</a>, Previous:<a rel="previous" href="#swappedin">swapped in</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>swapped out</b> n.</p> + +<p>See <b><a href="#swap">swap</a></b>. See also <b><a href="#pageout">page out</a></b>.</p> + +<hr> +Node:<a name="swizzle">swizzle</a>, Next:<a rel="next" href="#sync">sync</a>, Previous:<a rel="previous" href="#swappedout">swapped out</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>swizzle</b> v.</p> + +<p>To convert external names, array indices, or references within +a data structure into address pointers when the data structure is +brought into main memory from external storage (also called +`pointer swizzling'); this may be done for speed in chasing +references or to simplify code (e.g., by turning lots of name +lookups into pointer dereferences). The converse operation is +sometimes termed `unswizzling'. See also <b><a href="#snap">snap</a></b>.</p> + +<hr> +Node:<a name="sync">sync</a>, Next:<a rel="next" href="#syntacticsalt">syntactic salt</a>, Previous:<a rel="previous" href="#swizzle">swizzle</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>sync</b> /sink/ n., vi.</p> + +<p>(var. `synch') 1. To synchronize, to bring into +synchronization. 2. [techspeak] To force all pending I/O to the +disk; see <b><a href="#flush">flush</a></b>, sense 2. 3. More +generally, to force a number of competing processes or agents to +a state that would be `safe' if the system were to crash; thus, +to checkpoint (in the database-theory sense).</p> + +<hr> +Node:<a name="syntacticsalt">syntactic salt</a>, Next:<a rel="next" href="#syntacticsugar">syntactic sugar</a>, Previous:<a +rel="previous" href="#sync">sync</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>syntactic salt</b> n.</p> + +<p>The opposite of <b><a href="#syntacticsugar">syntactic +sugar</a></b>, a feature designed to make it harder to write bad +code. Specifically, syntactic salt is a hoop the programmer must +jump through just to prove that he knows what's going on, rather +than to express a program action. Some programmers consider +required type declarations to be syntactic salt. A requirement to +write <code>end if</code>, <code>end while</code>, <code>end +do</code>, etc. to terminate the last block controlled by a +control construct (as opposed to just <code>end</code>) would +definitely be syntactic salt. Syntactic salt is like the real +thing in that it tends to raise hackers' blood pressures in an +unhealthy way. Compare <b><a href="#candygrammar">candygrammar</a></b>.</p> + +<hr> +Node:<a name="syntacticsugar">syntactic sugar</a>, Next:<a +rel="next" href="#sys-frog">sys-frog</a>, Previous:<a rel="previous" href="#syntacticsalt">syntactic salt</a>, Up:<a +rel="up" href="#chap19">= S =</a> <br> + + +<p><b>syntactic sugar</b> n.</p> + +<p>[coined by Peter Landin] Features added to a language or other +formalism to make it `sweeter' for humans, features which do not +affect the expressiveness of the formalism (compare <b><a href="#chrome">chrome</a></b>). Used esp. when there is an obvious and +trivial translation of the `sugar' feature into other constructs +already present in the notation. C's <code>a[i]</code> notation +is syntactic sugar for <code>*(a + i)</code>. "Syntactic sugar +causes cancer of the semicolon." -- Alan Perlis.</p> + +<p>The variants `syntactic saccharin' and `syntactic syrup' are +also recorded. These denote something even more gratuitous, in +that syntactic sugar serves a purpose (making something more +acceptable to humans), but syntactic saccharin or syrup serve no +purpose at all. Compare <b><a href="#candygrammar">candygrammar</a></b>, <b><a href="#syntacticsalt">syntactic salt</a></b>.</p> + +<hr> +Node:<a name="sys-frog">sys-frog</a>, Next:<a rel="next" href="#sysadmin">sysadmin</a>, Previous:<a rel="previous" href="#syntacticsugar">syntactic sugar</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>sys-frog</b> /sis'frog/ n.</p> + +<p>[the PLATO system] Playful variant of `sysprog', which is in +turn short for `systems programmer'.</p> + +<hr> +Node:<a name="sysadmin">sysadmin</a>, Next:<a rel="next" href="#sysape">sysape</a>, Previous:<a rel="previous" href="#sys-frog">sys-frog</a>, Up:<a rel="up" href="#chap19">= +S =</a> <br> + + +<p><b>sysadmin</b> /sis'ad-min/ n.</p> + +<p>Common contraction of `system admin'; see <b><a href="#admin">admin</a></b>.</p> + +<hr> +Node:<a name="sysape">sysape</a>, Next:<a rel="next" href="#sysop">sysop</a>, Previous:<a rel="previous" href="#sysadmin">sysadmin</a>, Up:<a rel="up" href="#chap19">= +S =</a> <br> + + +<p><b>sysape</b> /sys'ayp/ n.</p> + +<p>A rather derogatory term for a computer operator; a play on +<b><a href="#sysop">sysop</a></b> common at sites that use the +banana hierarchy of problem complexity (see <b><a href="#one-bananaproblem">one-banana problem</a></b>).</p> + +<hr> +Node:<a name="sysop">sysop</a>, Next:<a rel="next" href="#system">system</a>, Previous:<a rel="previous" href="#sysape">sysape</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>sysop</b> /sis'op/ n.</p> + +<p>[esp. in the BBS world] The operator (and usually the owner) +of a bulletin-board system. A common neophyte mistake on <b><a +href="#FidoNet">FidoNet</a></b> is to address a message to +`sysop' in an international <b><a href="#echo">echo</a></b>, thus +sending it to hundreds of sysops around the world.</p> + +<hr> +Node:<a name="system">system</a>, Next:<a rel="next" href="#systemsjock">systems jock</a>, Previous:<a rel="previous" +href="#sysop">sysop</a>, Up:<a rel="up" href="#chap19">= S +=</a> <br> + + +<p><b>system</b> n.</p> + +<p>1. The supervisor program or OS on a computer. 2. The entire +computer system, including input/output devices, the supervisor +program or OS, and possibly other software. 3. Any large-scale +program. 4. Any method or algorithm. 5. `System hacker': one who +hacks the system (in senses 1 and 2 only; for sense 3 one +mentions the particular program: e.g., `LISP hacker')</p> + +<hr> +Node:<a name="systemsjock">systems jock</a>, Next:<a rel="next" href="#systemmangler">system mangler</a>, Previous:<a +rel="previous" href="#system">system</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>systems jock</b> n.</p> + +<p>See <b><a href="#jock">jock</a></b>, sense 2.</p> + +<hr> +Node:<a name="systemmangler">system mangler</a>, Next:<a rel="next" href="#SysVile">SysVile</a>, Previous:<a rel="previous" +href="#systemsjock">systems jock</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>system mangler</b> n.</p> + +<p>Humorous synonym for `system manager', poss. from the fact +that one major IBM OS had a <b><a href="#root">root</a></b> +account called SYSMANGR. Refers specifically to a systems +programmer in charge of administration, software maintenance, and +updates at some site. Unlike <b><a href="#admin">admin</a></b>, +this term emphasizes the technical end of the skills +involved.</p> + +<hr> +Node:<a name="SysVile">SysVile</a>, Next:<a rel="next" href="#T">T</a>, Previous:<a rel="previous" href="#systemmangler">system mangler</a>, Up:<a rel="up" href="#chap19">= S =</a> <br> + + +<p><b>SysVile</b> /sis-vi:l'/ n.</p> + +<p>See <b><a href="#Missedem-five">Missed'em-five</a></b>.</p> + +<hr> +Node:<a name="chap20">= T =</a>, Next:<a rel="next" href="#chap21">= U =</a>, Previous:<a rel="previous" href="#chap19">= S =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= T =</h2> + +<ul> +<li><a href="#T">T</a>:</li> + +<li><a href="#tailrecursion">tail recursion</a>:</li> + +<li><a href="#talkmode">talk mode</a>:</li> + +<li><a href="#talkersystem">talker system</a>:</li> + +<li><a href="#tallcard">tall card</a>:</li> + +<li><a href="#tanked">tanked</a>:</li> + +<li><a href="#TANSTAAFL">TANSTAAFL</a>:</li> + +<li><a href="#tapemonkey">tape monkey</a>:</li> + +<li><a href="#tarandfeather">tar and feather</a>:</li> + +<li><a href="#tarball">tarball</a>:</li> + +<li><a href="#tardegy">tardegy</a>:</li> + +<li><a href="#taste">taste</a>:</li> + +<li><a href="#tayste">tayste</a>:</li> + +<li><a href="#TCB">TCB</a>:</li> + +<li><a href="#TCPIP">TCP/IP</a>:</li> + +<li><a href="#TechRef">TechRef</a>:</li> + +<li><a href="#TECO">TECO</a>:</li> + +<li><a href="#tee">tee</a>:</li> + +<li><a href="#teergrube">teergrube</a>:</li> + +<li><a href="#teledildonics">teledildonics</a>:</li> + +<li><a href="#Telerat">Telerat</a>:</li> + +<li><a href="#TELNET">TELNET</a>:</li> + +<li><a href="#tenfingerinterface">ten-finger interface</a>:</li> + +<li><a href="#tense">tense</a>:</li> + +<li><a href="#tentacle">tentacle</a>:</li> + +<li><a href="#tenuredgraduatestudent">tenured graduate student</a>:</li> + +<li><a href="#tera-">tera-</a>:</li> + +<li><a href="#teraflopclub">teraflop club</a>:</li> + +<li><a href="#terminak">terminak</a>:</li> + +<li><a href="#terminalbraindeath">terminal brain death</a>:</li> + +<li><a href="#terminalillness">terminal illness</a>:</li> + +<li><a href="#terminaljunkie">terminal junkie</a>:</li> + +<li><a href="#terpri">terpri</a>:</li> + +<li><a href="#test">test</a>:</li> + +<li><a href="#TeX">TeX</a>:</li> + +<li><a href="#text">text</a>:</li> + +<li><a href="#thanksinadvance">thanks in advance</a>:</li> + +<li><a href="#Thatsnotabugthatsafeature">That's not a bug that's a feature!</a>:</li> + +<li><a href="#theliterature">the literature</a>:</li> + +<li><a href="#thenetwork">the network</a>:</li> + +<li><a href="#theXthatcanbeYisnotthetrueX">the X that can be Y is not the true X</a>:</li> + +<li><a href="#theology">theology</a>:</li> + +<li><a href="#theory">theory</a>:</li> + +<li><a href="#thinko">thinko</a>:</li> + +<li><a href="#Thiscanthappen">This can't happen</a>:</li> + +<li><a href="#Thistimeforsure">This time for sure!</a>:</li> + +<li><a href="#thrash">thrash</a>:</li> + +<li><a href="#thread">thread</a>:</li> + +<li><a href="#three-fingersalute">three-finger salute</a>:</li> + +<li><a href="#throwawayaccount">throwaway account</a>:</li> + +<li><a href="#thud">thud</a>:</li> + +<li><a href="#thumb">thumb</a>:</li> + +<li><a href="#thunderingherdproblem">thundering herd problem</a>:</li> + +<li><a href="#thunk">thunk</a>:</li> + +<li><a href="#tick">tick</a>:</li> + +<li><a href="#ticklistfeatures">tick-list features</a>:</li> + +<li><a href="#tickleabug">tickle a bug</a>:</li> + +<li><a href="#tigerteam">tiger team</a>:</li> + +<li><a href="#timebomb">time bomb</a>:</li> + +<li><a href="#timesink">time sink</a>:</li> + +<li><a href="#timeT">time T</a>:</li> + +<li><a href="#times-or-divided-by">times-or-divided-by</a>:</li> + +<li><a href="#TINC">TINC</a>:</li> + +<li><a href="#Tinkerbellprogram">Tinkerbell program</a>:</li> + +<li><a href="#TINLC">TINLC</a>:</li> + +<li><a href="#tipoftheicecube">tip of the ice-cube</a>:</li> + +<li><a href="#tirediron">tired iron</a>:</li> + +<li><a href="#titsonakeyboard">tits on a keyboard</a>:</li> + +<li><a href="#TLA">TLA</a>:</li> + +<li><a href="#TM">(TM)</a>:</li> + +<li><a href="#TMRC">TMRC</a>:</li> + +<li><a href="#TMRCie">TMRCie</a>:</li> + +<li><a href="#TMTOWTDI">TMTOWTDI</a>:</li> + +<li><a href="#toafirstapproximation">to a first approximation</a>:</li> + +<li><a href="#toazerothapproximation">to a zeroth approximation</a>:</li> + +<li><a href="#toad">toad</a>:</li> + +<li><a href="#toast">toast</a>:</li> + +<li><a href="#toaster">toaster</a>:</li> + +<li><a href="#toeprint">toeprint</a>:</li> + +<li><a href="#toggle">toggle</a>:</li> + +<li><a href="#tool">tool</a>:</li> + +<li><a href="#toolsmith">toolsmith</a>:</li> + +<li><a href="#toor">toor</a>:</li> + +<li><a href="#topicdrift">topic drift</a>:</li> + +<li><a href="#topicgroup">topic group</a>:</li> + +<li><a href="#TOPS-10">TOPS-10</a>:</li> + +<li><a href="#TOPS-20">TOPS-20</a>:</li> + +<li><a href="#tourist">tourist</a>:</li> + +<li><a href="#touristinformation">tourist information</a>:</li> + +<li><a href="#touristic">touristic</a>:</li> + +<li><a href="#toy">toy</a>:</li> + +<li><a href="#toylanguage">toy language</a>:</li> + +<li><a href="#toyproblem">toy problem</a>:</li> + +<li><a href="#toyprogram">toy program</a>:</li> + +<li><a href="#trampoline">trampoline</a>:</li> + +<li><a href="#trap">trap</a>:</li> + +<li><a href="#trapDoor">trap door</a>:</li> + +<li><a href="#trash">trash</a>:</li> + +<li><a href="#trawl">trawl</a>:</li> + +<li><a href="#tree-killer">tree-killer</a>:</li> + +<li><a href="#treeware">treeware</a>:</li> + +<li><a href="#trit">trit</a>:</li> + +<li><a href="#trivial">trivial</a>:</li> + +<li><a href="#troff">troff</a>:</li> + +<li><a href="#troglodyte">troglodyte</a>:</li> + +<li><a href="#troglodytemode">troglodyte mode</a>:</li> + +<li><a href="#Trojanhorse">Trojan horse</a>:</li> + +<li><a href="#troll">troll</a>:</li> + +<li><a href="#Troll-O-Meter">Troll-O-Meter</a>:</li> + +<li><a href="#tron">tron</a>:</li> + +<li><a href="#true-hacker">true-hacker</a>:</li> + +<li><a href="#tty">tty</a>:</li> + +<li><a href="#tube">tube</a>:</li> + +<li><a href="#tubetime">tube time</a>:</li> + +<li><a href="#tunafish">tunafish</a>:</li> + +<li><a href="#tune">tune</a>:</li> + +<li><a href="#turbonerd">turbo nerd</a>:</li> + +<li><a href="#Turingtarpit">Turing tar-pit</a>:</li> + +<li><a href="#turist">turist</a>:</li> + +<li><a href="#Tux">Tux</a>:</li> + +<li><a href="#tweak">tweak</a>:</li> + +<li><a href="#tweeter">tweeter</a>:</li> + +<li><a href="#TWENEX">TWENEX</a>:</li> + +<li><a href="#twiddle">twiddle</a>:</li> + +<li><a href="#twiddle">twiddle</a>:</li> + +<li><a href="#twilightzone">twilight zone</a>:</li> + +<li><a href="#twink">twink</a>:</li> + +<li><a href="#twirlingbaton">twirling baton</a>:</li> + +<li><a href="#twopi">two pi</a>:</li> + +<li><a href="#two-to-the-N">two-to-the-N</a>:</li> + +<li><a href="#twonkie">twonkie</a>:</li> +</ul> + +<hr> +Node:<a name="T">T</a>, Next:<a rel="next" href="#tailrecursion">tail recursion</a>, Previous:<a rel="previous" href="#SysVile">SysVile</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>T</b> /T/</p> + +<p>1. [from LISP terminology for `true'] Yes. Used in reply to a +question (particularly one asked using <b><a href="#The-Pconvention">The -P convention</a></b>). In LISP, the +constant T means `true', among other things. Some Lisp hackers +use `T' and `NIL' instead of `Yes' and `No' almost reflexively. +This sometimes causes misunderstandings. When a waiter or flight +attendant asks whether a hacker wants coffee, he may absently +respond `T', meaning that he wants coffee; but of course he will +be brought a cup of tea instead. Fortunately, most hackers +(particularly those who frequent Chinese restaurants) like tea at +least as well as coffee -- so it is not that big a problem. 2. +See <b><a href="#timeT">time T</a></b> (also <b><a href="#sincetimeTequalsminusinfinity">since time T +equals minus infinity</a></b>). 3. [techspeak] In +transaction-processing circles, an abbreviation for the noun +`transaction'. 4. [Purdue] Alternate spelling of <b><a href="#tee">tee</a></b>. 5. A dialect of <b><a href="#LISP">LISP</a></b> developed at Yale. (There is an intended +allusion to NIL, "New Implementation of Lisp", another dialect of +Lisp developed for the <b><a href="#VAX">VAX</a></b>)</p> + +<hr> +Node:<a name="tailrecursion">tail recursion</a>, Next:<a rel="next" href="#talkmode">talk mode</a>, Previous:<a rel="previous" href="#T">T</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>tail recursion</b> n.</p> + +<p>If you aren't sick of it already, see <b><a href="#tailrecursion">tail recursion</a></b>.</p> + +<hr> +Node:<a name="talkmode">talk mode</a>, Next:<a rel="next" +href="#talkersystem">talker system</a>, Previous:<a rel="previous" href="#tailrecursion">tail recursion</a>, Up:<a +rel="up" href="#chap20">= T =</a> <br> + + +<p><b>talk mode</b> n.</p> + +<p>A feature supported by Unix, ITS, and some other OSes that +allows two or more logged-in users to set up a real-time on-line +conversation. It combines the immediacy of talking with all the +precision (and verbosity) that written language entails. It is +difficult to communicate inflection, though conventions have +arisen for some of these (see the section on writing style in the +Prependices for details).</p> + +<p>Talk mode has a special set of jargon words, used to save +typing, which are not used orally. Some of these are identical to +(and probably derived from) Morse-code jargon used by ham-radio +amateurs since the 1920s.</p> + +<dl> +<dt><tt>AFAIAC</tt></dt> + +<dd>as far as I am concerned</dd> + +<dt><tt>AFAIK</tt></dt> + +<dd>as far as I know</dd> + +<dt><tt>BCNU</tt></dt> + +<dd>be seeing you</dd> + +<dt><tt>BTW</tt></dt> + +<dd>by the way</dd> + +<dt><tt>BYE?</tt></dt> + +<dd>are you ready to unlink? (this is the standard way to end a +talk-mode conversation; the other person types <code>BYE</code> +to confirm, or else continues the conversation)</dd> + +<dt><tt>CUL</tt></dt> + +<dd>see you later</dd> + +<dt><tt>ENQ?</tt></dt> + +<dd>are you busy? (expects <code>ACK</code> or <code>NAK</code> +in return)</dd> + +<dt><tt>FOO?</tt></dt> + +<dd>are you there? (often used on unexpected links, meaning also +"Sorry if I butted in <small>...</small>" (linker) or "What's +up?" (linkee))<br> +</dd> + +<dt><tt>FWIW</tt></dt> + +<dd>for what it's worth</dd> + +<dt><tt>FYI</tt></dt> + +<dd>for your information</dd> + +<dt><tt>FYA</tt></dt> + +<dd>for your amusement</dd> + +<dt><tt>GA</tt></dt> + +<dd>go ahead (used when two people have tried to type +simultaneously; this cedes the right to type to the other)</dd> + +<dt><tt>GRMBL</tt></dt> + +<dd>grumble (expresses disquiet or disagreement)</dd> + +<dt><tt>HELLOP</tt></dt> + +<dd>hello? (an instance of the `-P' convention)</dd> + +<dt><tt>IIRC</tt></dt> + +<dd>if I recall correctly</dd> + +<dt><tt>JAM</tt></dt> + +<dd>just a minute (equivalent to <code>SEC....</code>)</dd> + +<dt><tt>MIN</tt></dt> + +<dd>same as <code>JAM</code></dd> + +<dt><tt>NIL</tt></dt> + +<dd>no (see <b><a href="#NIL">NIL</a></b>)</dd> + +<dt><tt>NP</tt></dt> + +<dd>no problem</dd> + +<dt><tt>O</tt></dt> + +<dd>over to you</dd> + +<dt><tt>OO</tt></dt> + +<dd>over and out</dd> + +<dt><tt>/</tt></dt> + +<dd>another form of "over to you" (from x/y as "x over y")</dd> + +<dt><tt>\</tt></dt> + +<dd>lambda (used in discussing LISPy things)</dd> + +<dt><tt>OBTW</tt></dt> + +<dd>oh, by the way</dd> + +<dt><tt>OTOH</tt></dt> + +<dd>on the other hand</dd> + +<dt><tt>R U THERE?</tt></dt> + +<dd>are you there?</dd> + +<dt><tt>SEC</tt></dt> + +<dd>wait a second (sometimes written <code>SEC...</code>)</dd> + +<dt><tt>SYN</tt></dt> + +<dd>Are you busy? (expects ACK, SYN|ACK, or RST in return; this +is modeled on the TCP/IP handshake sequence)</dd> + +<dt><tt>T</tt></dt> + +<dd>yes (see the main entry for <b><a href="#T">T</a></b>)</dd> + +<dt><tt>TNX</tt></dt> + +<dd>thanks</dd> + +<dt><tt>TNX 1.0E6</tt></dt> + +<dd>thanks a million (humorous)</dd> + +<dt><tt>TNXE6</tt></dt> + +<dd>another form of "thanks a million"</dd> + +<dt><tt>WRT</tt></dt> + +<dd>with regard to, or with respect to.</dd> + +<dt><tt>WTF</tt></dt> + +<dd>the universal interrogative particle; WTF knows what it +means?</dd> + +<dt><tt>WTH</tt></dt> + +<dd>what the hell?</dd> + +<dt><tt><double newline></tt></dt> + +<dd>When the typing party has finished, he/she types two newlines +to signal that he/she is done; this leaves a blank line between +`speeches' in the conversation, making it easier to reread the +preceding text.</dd> + +<dt><tt><name>:</tt></dt> + +<dd>When three or more terminals are linked, it is conventional +for each typist to <b><a href="#prepend">prepend</a></b> his/her +login name or handle and a colon (or a hyphen) to each line to +indicate who is typing (some conferencing facilities do this +automatically). The login name is often shortened to a unique +prefix (possibly a single letter) during a very long +conversation.</dd> + +<dt><tt>/\/\/\</tt></dt> + +<dd>A giggle or chuckle. On a MUD, this usually means `earthquake +fault'.</dd> +</dl> + +<p>Most of the above sub-jargon is used at both Stanford and MIT. +Several of these expressions are also common in <b><a href="#email">email</a></b>, esp. FYI, FYA, BTW, BCNU, WTF, and CUL. A +few other abbreviations have been reported from commercial +networks, such as GEnie and CompuServe, where on-line `live' chat +including more than two people is common and usually involves a +more `social' context, notably the following:</p> + +<dl> +<dt><tt><g></tt></dt> + +<dd>grin</dd> + +<dt><tt><gd&r></tt></dt> + +<dd>grinning, ducking, and running</dd> + +<dt><tt>BBL</tt></dt> + +<dd>be back later</dd> + +<dt><tt>BRB</tt></dt> + +<dd>be right back</dd> + +<dt><tt>HHOJ</tt></dt> + +<dd>ha ha only joking</dd> + +<dt><tt>HHOK</tt></dt> + +<dd>ha ha only kidding</dd> + +<dt><tt>HHOS</tt></dt> + +<dd><b><a href="#hahaonlyserious">ha ha only +serious</a></b></dd> + +<dt><tt>IMHO</tt></dt> + +<dd>in my humble opinion (see <b><a href="#IMHO">IMHO</a></b>)</dd> + +<dt><tt>LOL</tt></dt> + +<dd>laughing out loud</dd> + +<dt><tt>NHOH</tt></dt> + +<dd>Never Heard of Him/Her (often used in <b><a href="#initgame">initgame</a></b>)</dd> + +<dt><tt>ROTF</tt></dt> + +<dd>rolling on the floor</dd> + +<dt><tt>ROTFL</tt></dt> + +<dd>rolling on the floor laughing</dd> + +<dt><tt>AFK</tt></dt> + +<dd>away from keyboard</dd> + +<dt><tt>b4</tt></dt> + +<dd>before</dd> + +<dt><tt>CU l8tr</tt></dt> + +<dd>see you later</dd> + +<dt><tt>MORF</tt></dt> + +<dd>male or female?</dd> + +<dt><tt>TTFN</tt></dt> + +<dd>ta-ta for now</dd> + +<dt><tt>TTYL</tt></dt> + +<dd>talk to you later</dd> + +<dt><tt>OIC</tt></dt> + +<dd>oh, I see</dd> + +<dt><tt>rehi</tt></dt> + +<dd>hello again</dd> +</dl> + +<p>Most of these are not used at universities or in the Unix +world, though ROTF and TTFN have gained some currency there and +IMHO is common; conversely, most of the people who know these are +unfamiliar with FOO?, BCNU, HELLOP, <b><a href="#NIL">NIL</a></b>, and <b><a href="#T">T</a></b>.</p> + +<p>The <b><a href="#MUD">MUD</a></b> community uses a mixture of +Usenet/Internet emoticons, a few of the more natural of the +old-style talk-mode abbrevs, and some of the `social' list above; +specifically, MUD respondents report use of BBL, BRB, LOL, b4, +BTW, WTF, TTFN, and WTH. The use of `rehi' is also common; in +fact, mudders are fond of re- compounds and will frequently +`rehug' or `rebonk' (see <b><a href="#bonkfoif">bonk/oif</a></b>) people. The word `re' by itself +is taken as `regreet'. In general, though, MUDders express a +preference for typing things out in full rather than using +abbreviations; this may be due to the relative youth of the MUD +cultures, which tend to include many touch typists and to assume +high-speed links. The following uses specific to MUDs are +reported:</p> + +<dl> +<dt><tt>CU l8er</tt></dt> + +<dd>see you later (mutant of <code>CU l8tr</code>)</dd> + +<dt><tt>FOAD</tt></dt> + +<dd>fuck off and die (use of this is generally OTT)</dd> + +<dt><tt>OTT</tt></dt> + +<dd>over the top (excessive, uncalled for)</dd> + +<dt><tt>ppl</tt></dt> + +<dd>abbrev for "people"</dd> + +<dt><tt>THX</tt></dt> + +<dd>thanks (mutant of <code>TNX</code>; clearly this comes in +batches of 1138 (the Lucasian K)).</dd> + +<dt><tt>UOK?</tt></dt> + +<dd>are you OK?</dd> +</dl> + +<p>Some <b><a href="#B1FF">B1FF</a></b>isms (notably the variant +spelling <code>d00d</code>) appear to be passing into wider use +among some subgroups of MUDders.</p> + +<p>One final note on talk mode style: neophytes, when in talk +mode, often seem to think they must produce letter-perfect prose +because they are typing rather than speaking. This is not the +best approach. It can be very frustrating to wait while your +partner pauses to think of a word, or repeatedly makes the same +spelling error and backs up to fix it. It is usually best just to +leave typographical errors behind and plunge forward, unless +severe confusion may result; in that case it is often fastest +just to type "xxx" and start over from before the mistake.</p> + +<p>See also <b><a href="#hakspek">hakspek</a></b>, <b><a href="#emoticon">emoticon</a></b>.</p> + +<hr> +Node:<a name="talkersystem">talker system</a>, Next:<a rel="next" href="#tallcard">tall card</a>, Previous:<a rel="previous" href="#talkmode">talk mode</a>, Up:<a rel="up" +href="#chap20">= T =</a> <br> + + +<p><b>talker system</b> n.</p> + +<p>British hackerism for software that enables real-time chat or +<b><a href="#talkmode">talk mode</a></b>.</p> + +<hr> +Node:<a name="tallcard">tall card</a>, Next:<a rel="next" +href="#tanked">tanked</a>, Previous:<a rel="previous" href="#talkersystem">talker system</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>tall card</b> n.</p> + +<p>A PC/AT-size expansion card (these can be larger than IBM PC +or XT cards because the AT case is bigger). See also <b><a href="#shortcard">short card</a></b>. When IBM introduced the PS/2 +model 30 (its last gasp at supporting the ISA) they made the case +lower and many industry-standard tall cards wouldn't fit; this +was felt to be a reincarnation of the <b><a href="#connectorconspiracy">connector conspiracy</a></b>, done with +less style.</p> + +<hr> +Node:<a name="tanked">tanked</a>, Next:<a rel="next" href="#TANSTAAFL">TANSTAAFL</a>, Previous:<a rel="previous" href="#tallcard">tall card</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>tanked</b> adj.</p> + +<p>Same as <b><a href="#down">down</a></b>, used primarily by +Unix hackers. See also <b><a href="#hosed">hosed</a></b>. +Popularized as a synonym for `drunk' by Steve Dallas in the late +lamented "Bloom County" comic strip.</p> + +<hr> +Node:<a name="TANSTAAFL">TANSTAAFL</a>, Next:<a rel="next" href="#tapemonkey">tape monkey</a>, Previous:<a rel="previous" +href="#tanked">tanked</a>, Up:<a rel="up" href="#chap20">= +T =</a> <br> + + +<p><b>TANSTAAFL</b> /tan'stah-fl/</p> + +<p>[acronym, from Robert Heinlein's classic "The Moon is a Harsh +Mistress".] "There Ain't No Such Thing As A Free Lunch", often +invoked when someone is balking at the prospect of using an +unpleasantly <b><a href="#heavyweight">heavyweight</a></b> +technique, or at the poor quality of some piece of software, or +at the <b><a href="#signaltonoiseratio">signal-to-noise +ratio</a></b> of unmoderated Usenet newsgroups. "What? Don't tell +me I have to implement a database back end to get my address book +program to work!" "Well, TANSTAAFL you know." This phrase owes +some of its popularity to the high concentration of +science-fiction fans and political libertarians in hackerdom (see +<b><a href="#AppendixB">Appendix B</a></b> for +discussion).</p> + +<hr> +Node:<a name="tapemonkey">tape monkey</a>, Next:<a rel="next" +href="#tarandfeather">tar and feather</a>, Previous:<a rel="previous" href="#TANSTAAFL">TANSTAAFL</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>tape monkey</b> n.</p> + +<p>A junior system administrator, one who might plausibly be +assigned to do physical swapping of tapes and subsequent storage. +When a backup needs to be restored, one might holler "Tape +monkey!" (Compare <b><a href="#one-bananaproblem">one-banana +problem</a></b>) Also used to dismiss jobs not worthy of a highly +trained sysadmin's ineffable talents: "Cable up her PC? You must +be joking - I'm no tape monkey."</p> + +<hr> +Node:<a name="tarandfeather">tar and feather</a>, Next:<a +rel="next" href="#tarball">tarball</a>, Previous:<a rel="previous" href="#tapemonkey">tape monkey</a>, Up:<a rel="up" +href="#chap20">= T =</a> <br> + + +<p><b>tar and feather</b> vi.</p> + +<p>[from Unix <code>tar(1)</code>] To create a transportable +archive from a group of files by first sticking them together +with <code>tar(1)</code> (the Tape ARchiver) and then compressing +the result (see <b><a href="#compress">compress</a></b>). The +latter action is dubbed `feathering' partly for euphony and (if +only for contrived effect) by analogy to what you do with an +airplane propeller to decrease wind resistance, or with an oar to +reduce water resistance; smaller files, after all, slip through +comm links more easily. Compare the more common <b><a href="#tarball">tarball</a></b>.</p> + +<hr> +Node:<a name="tarball">tarball</a>, Next:<a rel="next" href="#tardegy">tardegy</a>, Previous:<a rel="previous" href="#tarandfeather">tar and feather</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>tarball</b> n.</p> + +<p>[very common; prob. based on the "tar baby" in the Uncle Remus +folk tales] An archive, created with the Unix tar(1) utility, +containing myriad related files. "Here, I'll just ftp you a +tarball of the whole project." Tarballs have been the standard +way to ship around source-code distributions since the mid-1980s; +in retrospect it seems odd that this term did not enter common +usage until the late 1990s.</p> + +<hr> +Node:<a name="tardegy">tardegy</a>, Next:<a rel="next" href="#taste">taste</a>, Previous:<a rel="previous" href="#tarball">tarball</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + + +<p><b>tardegy</b></p> + +<p>n. [deliberate mangling of `tragedy'] An incident in which +someone who clearly deserves to be selected out of the gene pool +on grounds of extreme stupidity meets with a messy end. Coined on +the Darwin list, which is dedicated to chronicling such +incidents; but almost all hackers would instantly recognize the +intention of the term and laugh.</p> + +<hr> +Node:<a name="taste">taste</a>, Next:<a rel="next" href="#tayste">tayste</a>, Previous:<a rel="previous" href="#tardegy">tardegy</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + + +<p><b>taste</b> [primarily MIT] n.</p> + +<p>1. The quality in a program that tends to be inversely +proportional to the number of features, hacks, and kluges +programmed into it. Also `tasty', `tasteful', `tastefulness'. +"This feature comes in N tasty flavors." Although `tasty' and +`flavorful' are essentially synonyms, `taste' and <b><a href="#flavor">flavor</a></b> are not. Taste refers to sound judgment +on the part of the creator; a program or feature can +<i>exhibit</i> taste but cannot <i>have</i> taste. On the +other hand, a feature can have <b><a href="#flavor">flavor</a></b>. Also, <b><a href="#flavor">flavor</a></b> has the additional meaning of `kind' or +`variety' not shared by `taste'. The marked sense of <b><a href="#flavor">flavor</a></b> is more popular than `taste', though +both are widely used. See also <b><a href="#elegant">elegant</a></b>. 2. Alt. sp. of <b><a href="#tayste">tayste</a></b>.</p> + +<hr> +Node:<a name="tayste">tayste</a>, Next:<a rel="next" href="#TCB">TCB</a>, Previous:<a rel="previous" href="#taste">taste</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + + +<p><b>tayste</b> /tayst/</p> + +<p>n. Two bits; also as <b><a href="#taste">taste</a></b>. Syn. +<b><a href="#crumb">crumb</a></b>, <b><a href="#quarter">quarter</a></b>. See <b><a href="#nybble">nybble</a></b>.</p> + +<hr> +Node:<a name="TCB">TCB</a>, Next:<a rel="next" href="#TCPIP">TCP/IP</a>, Previous:<a rel="previous" href="#tayste">tayste</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + + +<p><b>TCB</b> /T-C-B/ n.</p> + +<p>[IBM] 1. Trouble Came Back. An intermittent or +difficult-to-reproduce problem that has failed to respond to +neglect or <b><a href="#shotgundebugging">shotgun +debugging</a></b>. Compare <b><a href="#heisenbug">heisenbug</a></b>. Not to be confused with: 2. +Trusted Computing Base, an `official' jargon term from the <b><a +href="#OrangeBook">Orange Book</a></b>.</p> + +<hr> +Node:<a name="TCPIP">TCP/IP</a>, Next:<a rel="next" href="#TechRef">TechRef</a>, Previous:<a rel="previous" href="#TCB">TCB</a>, Up:<a rel="up" href="#chap20">= T =</a> +<br> + + +<p><b>TCP/IP</b> /T'C-P I'P/ n.</p> + +<p>1. [Transmission Control Protocol/Internet Protocol] The +wide-area-networking protocol that makes the Internet work, and +the only one most hackers can speak the name of without laughing +or retching. Unlike such allegedly `standard' competitors such as +X.25, DECnet, and the ISO 7-layer stack, TCP/IP evolved primarily +by actually being <i>used</i>, rather than being handed down +from on high by a vendor or a heavily-politicized standards +committee. Consequently, it (a) works, (b) actually promotes +cheap cross-platform connectivity, and (c) annoys the hell out of +corporate and governmental empire-builders everywhere. Hackers +value all three of these properties. See <b><a href="#creationism">creationism</a></b>. 2. [Amateur Packet Radio] +Formerly expanded as "The Crap Phil Is Pushing". The reference is +to Phil Karn, KA9Q, and the context was an ongoing +technical/political war between the majority of sites still +running AX.25 and the TCP/IP relays. TCP/IP won.</p> + +<hr> +Node:<a name="TechRef">TechRef</a>, Next:<a rel="next" href="#TECO">TECO</a>, Previous:<a rel="previous" href="#TCPIP">TCP/IP</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + + +<p><b>TechRef</b> /tek'ref/ n.</p> + +<p>[MS-DOS] The original "IBM PC Technical Reference Manual", +including the BIOS listing and complete schematics for the PC. +The only PC documentation in the original-issue package that was +considered serious by real hackers.</p> + +<hr> +Node:<a name="TECO">TECO</a>, Next:<a rel="next" href="#tee">tee</a>, Previous:<a rel="previous" href="#TechRef">TechRef</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + + +<p><b>TECO</b> /tee'koh/ n.,v. obs.</p> + +<p>1. [originally an acronym for `[paper] Tape Editor and +COrrector'; later, `Text Editor and COrrector'] n. A text editor +developed at MIT and modified by just about everybody. With all +the dialects included, TECO may have been the most prolific +editor in use before <b><a href="#EMACS">EMACS</a></b>, to which +it was directly ancestral. Noted for its powerful +programming-language-like features and its unspeakably hairy +syntax. It is literally the case that every string of characters +is a valid TECO program (though probably not a useful one); one +common game used to be mentally working out what the TECO +commands corresponding to human names did. 2. vt. Originally, to +edit using the TECO editor in one of its infinite variations (see +below). 3. vt.,obs. To edit even when TECO is <i>not</i> the +editor being used! This usage is rare and now primarily +historical.</p> + +<p>As an example of TECO's obscurity, here is a TECO program that +takes a list of names such as:</p> + +<pre> +Loser, J. Random +Quux, The Great +Dick, Moby +</pre> + +<p>sorts them alphabetically according to surname, and then puts +the surname last, removing the comma, to produce the +following:</p> + +<pre> +Moby Dick +J. Random Loser +The Great Quux +</pre> + +<p>The program is</p> + +<pre> +[1 J^P$L$$ +J <.-Z; .,(S,$ -D .)FX1 @F^B $K :L I $ G1 L>$$ +</pre> + +<p>(where ^B means `Control-B' (ASCII 0000010) and $ is actually +an <b><a href="#alt">alt</a></b> or escape (ASCII 0011011) +character).</p> + +<p>In fact, this very program was used to produce the second, +sorted list from the first list. The first hack at it had a <b><a +href="#bug">bug</a></b>: GLS (the author) had accidentally +omitted the <code>@</code> in front of <code>F^B</code>, which as +anyone can see is clearly the <b><a href="#WrongThing">Wrong +Thing</a></b>. It worked fine the second time. There is no space +to describe all the features of TECO, but it may be of interest +that <code>^P</code> means `sort' and <code>J<.-Z; +<small>...</small> L></code> is an idiomatic series of +commands for `do once for every line'.</p> + +<p>In mid-1991, TECO is pretty much one with the dust of history, +having been replaced in the affections of hackerdom by <b><a +href="#EMACS">EMACS</a></b>. Descendants of an early (and +somewhat lobotomized) version adopted by DEC can still be found +lurking on VMS and a couple of crufty PDP-11 operating systems, +however, and ports of the more advanced MIT versions remain the +focus of some antiquarian interest. See also <b><a href="#retrocomputing">retrocomputing</a></b>, <b><a href="#writeonlylanguage">write-only language</a></b>.</p> + +<hr> +Node:<a name="tee">tee</a>, Next:<a rel="next" href="#teergrube">teergrube</a>, Previous:<a rel="previous" href="#TECO">TECO</a>, Up:<a rel="up" href="#chap20">= T =</a> +<br> + + +<p><b>tee</b> n.,vt.</p> + +<p>[Purdue] A carbon copy of an electronic transmission. "Oh, +you're sending him the <b><a href="#bits">bits</a></b> to that? +Slap on a tee for me." From the Unix command <code>tee(1)</code>, +itself named after a pipe fitting (see <b><a href="#plumbing">plumbing</a></b>). Can also mean `save one for me', +as in "Tee a slice for me!" Also spelled `T'.</p> + +<hr> +Node:<a name="teergrube">teergrube</a>, Next:<a rel="next" href="#teledildonics">teledildonics</a>, Previous:<a rel="previous" +href="#tee">tee</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + + +<p><b>teergrube</b> /teer'groob/ n.</p> + +<p>[German for `tar pit'] A trap set to punish spammers who use +an <b><a href="#addressharvester">address harvester</a></b>; a +mail server deliberately set up to be really, really slow. To +activate it, scatter addresses that look like users on the +teergrube's host in places where the address harvester will be +trolling (one popular way is to embed the fake address in a +Usenet sig block next to a human-readable warning not to send +mail to it). The address harvester will dutifully collect the +address. When the spammer tries to mailbomb it, his mailer will +get stuck.</p> + +<hr> +Node:<a name="teledildonics">teledildonics</a>, Next:<a rel="next" href="#Telerat">Telerat</a>, Previous:<a rel="previous" +href="#teergrube">teergrube</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>teledildonics</b> /tel`*-dil-do'-niks/ n.</p> + +<p>Sex in a computer simulated virtual reality, esp. +computer-mediated sexual interaction between the <b><a href="#VR">VR</a></b> presences of two humans. This practice is not +yet possible except in the rather limited form of erotic +conversation on <b><a href="#MUD">MUD</a></b>s and the like. The +term, however, is widely recognized in the VR community as a +<b><a href="#hahaonlyserious">ha ha only serious</a></b> +projection of things to come. "When we can sustain a +multi-sensory surround good enough for teledildonics, +<i>then</i> we'll know we're getting somewhere." See also <b><a +href="#hotchat">hot chat</a></b>.</p> + +<hr> +Node:<a name="Telerat">Telerat</a>, Next:<a rel="next" href="#TELNET">TELNET</a>, Previous:<a rel="previous" href="#teledildonics">teledildonics</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>Telerat</b> /tel'*-rat/ n. obs.</p> + +<p>Unflattering hackerism for `Teleray', a now-extinct line of +extremely losing terminals. Compare <b><a href="#AIDX">AIDX</a></b>, <b><a href="#Macintrash">Macintrash</a></b> +<b><a href="#NominalSemidestructor">Nominal +Semidestructor</a></b>, <b><a href="#ScumOS">ScumOS</a></b>, +<b><a href="#sun-stools">sun-stools</a></b>, <b><a href="#HP-SUX">HP-SUX</a></b>, <b><a href="#Slowlaris">Slowlaris</a></b>.</p> + +<hr> +Node:<a name="TELNET">TELNET</a>, Next:<a rel="next" href="#tenfingerinterface">ten-finger interface</a>, Previous:<a +rel="previous" href="#Telerat">Telerat</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>TELNET</b> /tel'net/ vt.</p> + +<p>(also commonly lowercased as `telnet') To communicate with +another Internet host using the TELNET (<b><a href="#RFC">RFC</a></b> 854) protocol (usually using a program of the +same name). TOPS-10 people used the word IMPCOM, since that was +the program name for them. Sometimes abbreviated to TN /T-N/. "I +usually TN over to SAIL just to read the AP News."</p> + +<hr> +Node:<a name="tenfingerinterface">ten-finger interface</a>, +Next:<a rel="next" href="#tense">tense</a>, Previous:<a rel="previous" href="#TELNET">TELNET</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>ten-finger interface</b> n.</p> + +<p>The interface between two networks that cannot be directly +connected for security reasons; refers to the practice of placing +two terminals side by side and having an operator read from one +and type into the other.</p> + +<hr> +Node:<a name="tense">tense</a>, Next:<a rel="next" href="#tentacle">tentacle</a>, Previous:<a rel="previous" href="#tenfingerinterface">ten-finger interface</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>tense</b> adj.</p> + +<p>Of programs, very clever and efficient. A tense piece of code +often got that way because it was highly <b><a href="#bum">bum</a></b>med, but sometimes it was just based on a great +idea. A comment in a clever routine by Mike Kazar, once a +grad-student hacker at CMU: "This routine is so tense it will +bring tears to your eyes." A tense programmer is one who produces +tense code.</p> + +<hr> +Node:<a name="tentacle">tentacle</a>, Next:<a rel="next" href="#tenuredgraduatestudent">tenured graduate student</a>, +Previous:<a rel="previous" href="#tense">tense</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>tentacle</b> n.</p> + +<p>A covert <b><a href="#pseudo">pseudo</a></b>, sense 1. An +artificial identity created in cyberspace for nefarious and +deceptive purposes. The implication is that a single person may +have multiple tentacles. This term was originally floated in some +paranoid ravings on the cypherpunks list (see <b><a href="#cypherpunk">cypherpunk</a></b>), and adopted in a spirit of +irony by other, saner members. It has since shown up, used +seriously, in the documentation for some remailer software, and +is now (1994) widely recognized on the net.</p> + +<hr> +Node:<a name="tenuredgraduatestudent">tenured graduate +student</a>, Next:<a rel="next" href="#tera-">tera-</a>, +Previous:<a rel="previous" href="#tentacle">tentacle</a>, Up:<a +rel="up" href="#chap20">= T =</a> <br> + + +<p><b>tenured graduate student</b> n.</p> + +<p>One who has been in graduate school for 10 years (the usual +maximum is 5 or 6): a `ten-yeared' student (get it?). Actually, +this term may be used of any grad student beginning in his +seventh year. Students don't really get tenure, of course, the +way professors do, but a tenth-year graduate student has probably +been around the university longer than any untenured +professor.</p> + +<hr> +Node:<a name="tera-">tera-</a>, Next:<a rel="next" href="#teraflopclub">teraflop club</a>, Previous:<a rel="previous" +href="#tenuredgraduatestudent">tenured graduate +student</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>tera-</b> /te'r*/ pref.</p> + +<p>[SI] See <b><a href="#quantifiers">quantifiers</a></b>.</p> + +<hr> +Node:<a name="teraflopclub">teraflop club</a>, Next:<a rel="next" href="#terminak">terminak</a>, Previous:<a rel="previous" +href="#tera-">tera-</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + + +<p><b>teraflop club</b> /te'r*-flop kluhb/ n.</p> + +<p>[FLOP = Floating Point Operation] A mythical association of +people who consume outrageous amounts of computer time in order +to produce a few simple pictures of glass balls with intricate +ray-tracing techniques. Caltech professor James Kajiya is said to +have been the founder. Compare <b><a href="#KnightsoftheLambdaCalculus">Knights of the Lambda +Calculus</a></b>.</p> + +<hr> +Node:<a name="terminak">terminak</a>, Next:<a rel="next" href="#terminalbraindeath">terminal brain death</a>, Previous:<a +rel="previous" href="#teraflopclub">teraflop club</a>, Up:<a +rel="up" href="#chap20">= T =</a> <br> + + +<p><b>terminak</b> /ter'mi-nak`/ n.</p> + +<p>[Caltech, ca. 1979] Any malfunctioning computer terminal. A +common failure mode of Lear-Siegler ADM 3a terminals caused the +`L' key to produce the `K' code instead; complaints about this +tended to look like "Terminak #3 has a bad keyboard. Pkease fix." +Compare <b><a href="#dreadhighbitdisease">dread high-bit +disease</a></b>, <b><a href="#frogging">frogging</a></b>; see +also <b><a href="#AIDX">AIDX</a></b>, <b><a href="#NominalSemidestructor">Nominal Semidestructor</a></b>, <b><a +href="#ScumOS">ScumOS</a></b>, <b><a href="#sun-stools">sun-stools</a></b>, <b><a href="#Telerat">Telerat</a></b>, <b><a href="#HP-SUX">HP-SUX</a></b>, +<b><a href="#Slowlaris">Slowlaris</a></b>.</p> + +<hr> +Node:<a name="terminalbraindeath">terminal brain death</a>, +Next:<a rel="next" href="#terminalillness">terminal +illness</a>, Previous:<a rel="previous" href="#terminak">terminak</a>, Up:<a rel="up" href="#chap20">= +T =</a> <br> + + +<p><b>terminal brain death</b> n.</p> + +<p>The extreme form of <b><a href="#terminalillness">terminal +illness</a></b> (sense 1). What someone who has obviously been +hacking continuously for far too long is said to be suffering +from.</p> + +<hr> +Node:<a name="terminalillness">terminal illness</a>, Next:<a +rel="next" href="#terminaljunkie">terminal junkie</a>, +Previous:<a rel="previous" href="#terminalbraindeath">terminal brain death</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>terminal illness</b> n.</p> + +<p>1. Syn. <b><a href="#rasterburn">raster burn</a></b>. 2. +The `burn-in' condition your CRT tends to get if you don't have a +screen saver.</p> + +<hr> +Node:<a name="terminaljunkie">terminal junkie</a>, Next:<a +rel="next" href="#terpri">terpri</a>, Previous:<a rel="previous" +href="#terminalillness">terminal illness</a>, Up:<a rel="up" +href="#chap20">= T =</a> <br> + + +<p><b>terminal junkie</b> n.</p> + +<p>[UK] A <b><a href="#wannabee">wannabee</a></b> or early <b><a +href="#larvalstage">larval stage</a></b> hacker who spends +most of his or her time wandering the directory tree and writing +<b><a href="#noddy">noddy</a></b> programs just to get a fix of +computer time. Variants include `terminal jockey', `console +junkie', and <b><a href="#consolejockey">console +jockey</a></b>. The term `console jockey' seems to imply more +expertise than the other three (possibly because of the exalted +status of the <b><a href="#console">console</a></b> relative to +an ordinary terminal). See also <b><a href="#twink">twink</a></b>, <b><a href="#readonlyuser">read-only +user</a></b>. Appropriately, this term was used in the works of +William S. Burroughs to describe a heroin addict with an +unlimited supply.</p> + +<hr> +Node:<a name="terpri">terpri</a>, Next:<a rel="next" href="#test">test</a>, Previous:<a rel="previous" href="#terminaljunkie">terminal junkie</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>terpri</b> /ter'pree/ vi.</p> + +<p>[from LISP 1.5 (and later, MacLISP)] To output a <b><a href="#newline">newline</a></b>. Now rare as jargon, though still used +as techspeak in Common LISP. It is a contraction of `TERminate +PRInt line', named for the fact that, on some early OSes and +hardware, no characters would be printed until a complete line +was formed, so this operation terminated the line and emitted the +output.</p> + +<hr> +Node:<a name="test">test</a>, Next:<a rel="next" href="#TeX">TeX</a>, Previous:<a rel="previous" href="#terpri">terpri</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + + +<p><b>test</b> n.</p> + +<p>1. Real users bashing on a prototype long enough to get +thoroughly acquainted with it, with careful monitoring and +followup of the results. 2. Some bored random user trying a +couple of the simpler features with a developer looking over his +or her shoulder, ready to pounce on mistakes. Judging by the +quality of most software, the second definition is far more +prevalent. See also <b><a href="#demo">demo</a></b>.</p> + +<hr> +Node:<a name="TeX">TeX</a>, Next:<a rel="next" href="#text">text</a>, Previous:<a rel="previous" href="#test">test</a>, Up:<a rel="up" href="#chap20">= T =</a> +<br> + + +<p><b>TeX</b> /tekh/ n.</p> + +<p>An extremely powerful <b><a href="#macro">macro</a></b>-based +text formatter written by Donald E. <b><a href="#Knuth">Knuth</a></b>, very popular in the computer-science +community (it is good enough to have displaced Unix <b><a href="#troff">troff</a></b>, the other favored formatter, even at many +Unix installations). TeX fans insist on the correct (guttural) +pronunciation, and the correct spelling (all caps, squished +together, with the E depressed below the baseline; the mixed-case +`TeX' is considered an acceptable kluge on ASCII-only devices). +Fans like to proliferate names from the word `TeX' -- such as +TeXnician (TeX user), TeXhacker (TeX programmer), TeXmaster +(competent TeX programmer), TeXhax, and TeXnique. See also <b><a +href="#CrApTeX">CrApTeX</a></b>.</p> + +<p>Knuth began TeX because he had become annoyed at the declining +quality of the typesetting in volumes I-III of his monumental +"Art of Computer Programming" (see <b><a href="#Knuth">Knuth</a></b>, also <b><a href="#bible">bible</a></b>). +In a manifestation of the typical hackish urge to solve the +problem at hand once and for all, he began to design his own +typesetting language. He thought he would finish it on his +sabbatical in 1978; he was wrong by only about 8 years. The +language was finally frozen around 1985, but volume IV of "The +Art of Computer Programming" is not expected to appear until +2002. The impact and influence of TeX's design has been such that +nobody minds this very much. Many grand hackish projects have +started as a bit of <b><a href="#toolsmith">toolsmith</a></b>ing +on the way to something else; Knuth's diversion was simply on a +grander scale than most.</p> + +<p>TeX has also been a noteworthy example of free, shared, but +high-quality software. Knuth offers a monetary awards to anyone +who found and reported bugs dating from before the 1989 code +freeze; as the years wore on and the few remaining bugs were +fixed (and new ones even harder to find), the bribe went up. +Though well-written, TeX is so large (and so full of cutting edge +technique) that it is said to have unearthed at least one bug in +every Pascal system it has been compiled with.</p> + +<hr> +Node:<a name="text">text</a>, Next:<a rel="next" href="#thanksinadvance">thanks in advance</a>, Previous:<a rel="previous" href="#TeX">TeX</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>text</b> n.</p> + +<p>1. [techspeak] Executable code, esp. a `pure code' portion +shared between multiple instances of a program running in a +multitasking OS. Compare <b><a href="#English">English</a></b>. +2. Textual material in the mainstream sense; data in ordinary +<b><a href="#ASCII">ASCII</a></b> or <b><a href="#EBCDIC">EBCDIC</a></b> representation (see <b><a href="#flat-ASCII">flat-ASCII</a></b>). "Those are text files; you can +review them using the editor." These two contradictory senses +confuse hackers, too.</p> + +<hr> +Node:<a name="thanksinadvance">thanks in advance</a>, +Next:<a rel="next" href="#Thatsnotabugthatsafeature">That's not a +bug that's a feature!</a>, Previous:<a rel="previous" href="#text">text</a>, Up:<a rel="up" href="#chap20">= T =</a> +<br> + + +<p><b>thanks in advance</b></p> + +<p>[Usenet] Conventional net.politeness ending a posted request +for information or assistance. Sometimes written `advTHANKSance' +or `aTdHvAaNnKcSe' or abbreviated `TIA'. See <b><a href="#net.-">net.-</a></b>, <b><a href="#netiquette">netiquette</a></b>.</p> + +<hr> +Node:<a name="Thatsnotabugthatsafeature">That's not a bug +that's a feature!</a>, Next:<a rel="next" href="#theliterature">the literature</a>, Previous:<a rel="previous" href="#thanksinadvance">thanks in advance</a>, +Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>That's not a bug, that's a feature!</b></p> + +<p>The <b><a href="#canonical">canonical</a></b> first parry in a +debate about a purported bug. The complainant, if unconvinced, is +likely to retort that the bug is then at best a <b><a href="#misfeature">misfeature</a></b>. See also <b><a href="#feature">feature</a></b>.</p> + +<hr> +Node:<a name="theliterature">the literature</a>, Next:<a rel="next" href="#thenetwork">the network</a>, Previous:<a rel="previous" href="#Thatsnotabugthatsafeature">That's not a +bug that's a feature!</a>, Up:<a rel="up" href="#chap20">= +T =</a> <br> + + +<p><b>the literature</b> n.</p> + +<p>Computer-science journals and other publications, vaguely +gestured at to answer a question that the speaker believes is +<b><a href="#trivial">trivial</a></b>. Thus, one might answer an +annoying question by saying "It's in the literature." Oppose +<b><a href="#Knuth">Knuth</a></b>, which has no connotation of +triviality.</p> + +<hr> +Node:<a name="thenetwork">the network</a>, Next:<a rel="next" +href="#theXthatcanbeYisnotthetrueX">the +X that can be Y is not the true X</a>, Previous:<a rel="previous" +href="#theliterature">the literature</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>the network</b> n.</p> + +<p>1. Historicaslly, the union of all the major noncommercial, +academic, and hacker-oriented networks, such as Internet, the +pre-1990 ARPANET, NSFnet, <b><a href="#BITNET">BITNET</a></b>, +and the virtual UUCP and <b><a href="#Usenet">Usenet</a></b> +`networks', plus the corporate in-house networks and commercial +time-sharing services (such as CompuServe, GEnie and AOL) that +gateway to them. A site is generally considered `on the network' +if it can be reached through some combination of Internet-style +(@-sign) and UUCP (bang-path) addresses. See <b><a href="#Internet">Internet</a></b>, <b><a href="#bangpath">bang +path</a></b>, <b><a href="#Internetaddress">Internet +address</a></b>, <b><a href="#networkaddress">network +address</a></b>. 2. Following the mass-culture discovery of the +Internet in 1994 and subsequent proliferation of cheap TCP/IP +connections, "the network" is increasingly synonymous with the +Internet itself (as it was before the second wave of wide-area +computer networking began around 1980). 3. A fictional conspiracy +of libertarian hacker-subversives and anti-authoritarian +monkeywrenchers described in Robert Anton Wilson's novel +"Schrödinger's Cat", to which many hackers have subsequently +decided they belong (this is an example of <b><a href="#hahaonlyserious">ha ha only serious</a></b>).</p> + +<p>In sense 1, `the network' is often abbreviated to `the net'. +"Are you on the net?" is a frequent question when hackers first +meet face to face, and "See you on the net!" is a frequent +goodbye.</p> + +<hr> +Node:<a name="theXthatcanbeYisnotthetrueX">the X +that can be Y is not the true X</a>, Next:<a rel="next" href="#theology">theology</a>, Previous:<a rel="previous" href="#thenetwork">the network</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>the X that can be Y is not the true X</b></p> + +<p>Yet another instance of hackerdom's peculiar attraction to +mystical references -- a common humorous way of making exclusive +statements about a class of things. The template is from the "Tao +te Ching": "The Tao which can be spoken of is not the true Tao." +The implication is often that the X is a mystery accessible only +to the enlightened. See the <b><a href="#trampoline">trampoline</a></b> entry for an example, and +compare <b><a href="#hastheXnature">has the X +nature</a></b>.</p> + +<hr> +Node:<a name="theology">theology</a>, Next:<a rel="next" href="#theory">theory</a>, Previous:<a rel="previous" href="#theXthatcanbeYisnotthetrueX">the +X that can be Y is not the true X</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>theology</b> n.</p> + +<p>1. Ironically or humorously used to refer to <b><a href="#religiousissues">religious issues</a></b>. 2. Technical fine +points of an abstruse nature, esp. those where the resolution is +of theoretical interest but is relatively <b><a href="#marginal">marginal</a></b> with respect to actual use of a +design or system. Used esp. around software issues with a heavy +AI or language-design component, such as the smart-data vs. +smart-programs dispute in AI.</p> + +<hr> +Node:<a name="theory">theory</a>, Next:<a rel="next" href="#thinko">thinko</a>, Previous:<a rel="previous" href="#theology">theology</a>, Up:<a rel="up" href="#chap20">= +T =</a> <br> + + +<p><b>theory</b> n.</p> + +<p>The consensus, idea, plan, story, or set of rules that is +currently being used to inform a behavior. This usage is a +generalization and (deliberate) abuse of the technical meaning. +"What's the theory on fixing this TECO loss?" "What's the theory +on dinner tonight?" ("Chinatown, I guess.") "What's the current +theory on letting lusers on during the day?" "The theory behind +this change is to fix the following well-known +screw<small>...</small>."</p> + +<hr> +Node:<a name="thinko">thinko</a>, Next:<a rel="next" href="#Thiscanthappen">This can't happen</a>, Previous:<a rel="previous" href="#theory">theory</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>thinko</b> /thing'koh/ n.</p> + +<p>[by analogy with `typo'] A momentary, correctable glitch in +mental processing, especially one involving recall of information +learned by rote; a bubble in the stream of consciousness. Syn. +<b><a href="#braino">braino</a></b>; see also <b><a href="#brainfart">brain fart</a></b>. Compare <b><a href="#mouso">mouso</a></b>.</p> + +<hr> +Node:<a name="Thiscanthappen">This can't happen</a>, +Next:<a rel="next" href="#Thistimeforsure">This time +for sure!</a>, Previous:<a rel="previous" href="#thinko">thinko</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + + +<p><b>This can't happen</b></p> + +<p>Less clipped variant of <b><a href="#cannothappen">can't +happen</a></b>.</p> + +<hr> +Node:<a name="Thistimeforsure">This time for sure!</a>, +Next:<a rel="next" href="#thrash">thrash</a>, Previous:<a rel="previous" href="#Thiscanthappen">This can't happen</a>, +Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>This time, for sure!</b> excl.</p> + +<p>Ritual affirmation frequently uttered during protracted +debugging sessions involving numerous small obstacles (e.g., +attempts to bring up a UUCP connection). For the proper effect, +this must be uttered in a fruity imitation of Bullwinkle J. +Moose. Also heard: "Hey, Rocky! Watch me pull a rabbit out of my +hat!" The <b><a href="#canonical">canonical</a></b> response is, +of course, "But that trick <i>never</i> works!" See <b><a href="#hackerhumor">hacker humor</a></b>.</p> + +<hr> +Node:<a name="thrash">thrash</a>, Next:<a rel="next" href="#thread">thread</a>, Previous:<a rel="previous" href="#Thistimeforsure">This time for sure!</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>thrash</b> vi.</p> + +<p>To move wildly or violently, without accomplishing anything +useful. Paging or swapping systems that are overloaded waste most +of their time moving data into and out of core (rather than +performing useful computation) and are therefore said to thrash. +Someone who keeps changing his mind (esp. about what to work on +next) is said to be thrashing. A person frantically trying to +execute too many tasks at once (and not spending enough time on +any single task) may also be described as thrashing. Compare +<b><a href="#multitask">multitask</a></b>.</p> + +<hr> +Node:<a name="thread">thread</a>, Next:<a rel="next" href="#three-fingersalute">three-finger salute</a>, Previous:<a +rel="previous" href="#thrash">thrash</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>thread</b> n.</p> + +<p>[Usenet, GEnie, CompuServe] Common abbreviation of `topic +thread', a more or less continuous chain of postings on a single +topic. To `follow a thread' is to read a series of Usenet +postings sharing a common subject or (more correctly) which are +connected by Reference headers. The better newsreaders can +present news in thread order automatically. Not to be confused +with the techspeak sense of `thread', e.g. a lightweight +process.</p> + +<p>Interestingly, this is far from a neologism. The OED says: +"That which connects the successive points in anything, esp. a +narrative, train of thought, or the like; the sequence of events +or ideas continuing throughout the whole course of anything;" +Citations are given going back to 1642!</p> + +<hr> +Node:<a name="three-fingersalute">three-finger salute</a>, +Next:<a rel="next" href="#throwawayaccount">throwaway +account</a>, Previous:<a rel="previous" href="#thread">thread</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + + +<p><b>three-finger salute</b> n.</p> + +<p>Syn. <b><a href="#Vulcannervepinch">Vulcan nerve +pinch</a></b>.</p> + +<hr> +Node:<a name="throwawayaccount">throwaway account</a>, Next:<a +rel="next" href="#thud">thud</a>, Previous:<a rel="previous" +href="#three-fingersalute">three-finger salute</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>throwaway account</b> n.</p> + +<p>1. An inexpensive Internet account purchased on a legitimate +<b><a href="#ISP">ISP</a></b> for the the sole purpose of spewing +<b><a href="#spam">spam</a></b>. 2. An inexpensive Internet +account obtained for the sole purpose of doing something which +requires a valid email address but being able to ignore spam +since the user will not look at the account again.</p> + +<hr> +Node:<a name="thud">thud</a>, Next:<a rel="next" href="#thumb">thumb</a>, Previous:<a rel="previous" href="#throwawayaccount">throwaway account</a>, Up:<a rel="up" +href="#chap20">= T =</a> <br> + + +<p><b>thud</b> n.</p> + +<p>1. Yet another <b><a href="#metasyntacticvariable">metasyntactic variable</a></b> (see +<b><a href="#foo">foo</a></b>). It is reported that at CMU from +the mid-1970s the canonical series of these was `foo', `bar', +`thud', `blat'. 2. Rare term for the hash character, `#' (ASCII +0100011). See <b><a href="#ASCII">ASCII</a></b> for other +synonyms.</p> + +<hr> +Node:<a name="thumb">thumb</a>, Next:<a rel="next" href="#thunderingherdproblem">thundering herd problem</a>, +Previous:<a rel="previous" href="#thud">thud</a>, Up:<a rel="up" +href="#chap20">= T =</a> <br> + + +<p><b>thumb</b> n.</p> + +<p>The slider on a window-system scrollbar. So called because +moving it allows you to browse through the contents of a text +window in a way analogous to thumbing through a book.</p> + +<hr> +Node:<a name="thunderingherdproblem">thundering herd +problem</a>, Next:<a rel="next" href="#thunk">thunk</a>, +Previous:<a rel="previous" href="#thumb">thumb</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>thundering herd problem</b></p> + +<p>Scheduler thrashing. This can happen under Unix when you have +a number of processes that are waiting on a single event. When +that event (a connection to the web server, say) happens, every +process which could possibly handle the event is awakened. In the +end, only one of those processes will actually be able to do the +work, but, in the meantime, all the others wake up and contend +for CPU time before being put back to sleep. Thus the system +thrashes briefly while a herd of processes thunders through. If +this starts to happen many times per second, the performance +impact can be significant.</p> + +<hr> +Node:<a name="thunk">thunk</a>, Next:<a rel="next" href="#tick">tick</a>, Previous:<a rel="previous" href="#thunderingherdproblem">thundering herd problem</a>, Up:<a +rel="up" href="#chap20">= T =</a> <br> + + +<p><b>thunk</b> /thuhnk/ n.</p> + +<p>1. [obs.]"A piece of coding which provides an address", +according to P. Z. Ingerman, who invented thunks in 1961 as a way +of binding actual parameters to their formal definitions in +Algol-60 procedure calls. If a procedure is called with an +expression in the place of a formal parameter, the compiler +generates a thunk which computes the expression and leaves the +address of the result in some standard location. 2. Later +generalized into: an expression, frozen together with its +environment, for later evaluation if and when needed (similar to +what in techspeak is called a `closure'). The process of +unfreezing these thunks is called `forcing'. 3. A <b><a href="#stubroutine">stubroutine</a></b>, in an overlay programming +environment, that loads and jumps to the correct overlay. Compare +<b><a href="#trampoline">trampoline</a></b>. 4. People and +activities scheduled in a thunklike manner. "It occurred to me +the other day that I am rather accurately modeled by a thunk -- I +frequently need to be forced to completion." -- paraphrased from +a <b><a href="#planfile">plan file</a></b>.</p> + +<p>Historical note: There are a couple of onomatopoeic myths +circulating about the origin of this term. The most common is +that it is the sound made by data hitting the stack; another +holds that the sound is that of the data hitting an accumulator. +Yet another suggests that it is the sound of the expression being +unfrozen at argument-evaluation time. In fact, according to the +inventors, it was coined after they realized (in the wee hours +after hours of discussion) that the type of an argument in +Algol-60 could be figured out in advance with a little +compile-time thought, simplifying the evaluation machinery. In +other words, it had `already been thought of'; thus it was +christened a `thunk', which is "the past tense of `think' at two +in the morning".</p> + +<hr> +Node:<a name="tick">tick</a>, Next:<a rel="next" href="#ticklistfeatures">tick-list features</a>, Previous:<a rel="previous" href="#thunk">thunk</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>tick</b> n.</p> + +<p>1. A <b><a href="#jiffy">jiffy</a></b> (sense 1). 2. In +simulations, the discrete unit of time that passes between +iterations of the simulation mechanism. In AI applications, this +amount of time is often left unspecified, since the only +constraint of interest is the ordering of events. This sort of AI +simulation is often pejoratively referred to as `tick-tick-tick' +simulation, especially when the issue of simultaneity of events +with long, independent chains of causes is <b><a href="#handwave">handwave</a></b>d. 3. In the FORTH language, a single +quote character.</p> + +<hr> +Node:<a name="ticklistfeatures">tick-list features</a>, +Next:<a rel="next" href="#tickleabug">tickle a bug</a>, +Previous:<a rel="previous" href="#tick">tick</a>, Up:<a rel="up" +href="#chap20">= T =</a> <br> + + +<p><b>tick-list features</b> n.</p> + +<p>[Acorn Computers] Features in software or hardware that +customers insist on but never use (calculators in desktop TSRs +and that sort of thing). The American equivalent would be +`checklist features', but this jargon sense of the phrase has not +been reported.</p> + +<hr> +Node:<a name="tickleabug">tickle a bug</a>, Next:<a rel="next" href="#tigerteam">tiger team</a>, Previous:<a rel="previous" href="#ticklistfeatures">tick-list features</a>, +Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>tickle a bug</b> vt.</p> + +<p>To cause a normally hidden bug to manifest itself through some +known series of inputs or operations. "You can tickle the bug in +the Paradise VGA card's highlight handling by trying to set +bright yellow reverse video."</p> + +<hr> +Node:<a name="tigerteam">tiger team</a>, Next:<a rel="next" +href="#timebomb">time bomb</a>, Previous:<a rel="previous" +href="#tickleabug">tickle a bug</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>tiger team</b> n.</p> + +<p>[U.S. military jargon] 1. Originally, a team (of <b><a href="#sneaker">sneaker</a></b>s) whose purpose is to penetrate +security, and thus test security measures. These people are paid +professionals who do hacker-type tricks, e.g., leave cardboard +signs saying "bomb" in critical defense installations, +hand-lettered notes saying "Your codebooks have been stolen" +(they usually haven't been) inside safes, etc. After a successful +penetration, some high-ranking security type shows up the next +morning for a `security review' and finds the sign, note, etc., +and all hell breaks loose. Serious successes of tiger teams +sometimes lead to early retirement for base commanders and +security officers (see the <b><a href="#patch">patch</a></b> +entry for an example). 2. Recently, and more generally, any +official inspection team or special <b><a href="#firefighting">firefighting</a></b> group called in to look at a +problem.</p> + +<p>A subset of tiger teams are professional <b><a href="#cracker">cracker</a></b>s, testing the security of military +computer installations by attempting remote attacks via networks +or supposedly `secure' comm channels. Some of their escapades, if +declassified, would probably rank among the greatest hacks of all +times. The term has been adopted in commercial computer-security +circles in this more specific sense.</p> + +<hr> +Node:<a name="timebomb">time bomb</a>, Next:<a rel="next" +href="#timesink">time sink</a>, Previous:<a rel="previous" +href="#tigerteam">tiger team</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>time bomb</b> n.</p> + +<p>A subspecies of <b><a href="#logicbomb">logic bomb</a></b> +that is triggered by reaching some preset time, either once or +periodically. There are numerous legends about time bombs set up +by programmers in their employers' machines, to go off if the +programmer is fired or laid off and is not present to perform the +appropriate suppressing action periodically.</p> + +<p>Interestingly, the only such incident for which we have been +pointed to documentary evidence took place in the Soviet Union in +1986! A disgruntled programmer at the Volga Automobile Plant +(where the Fiat clones called Ladas were manufactured) planted a +time bomb which, a week after he'd left on vacation, stopped the +entire main assembly line for a day. The case attracted lots of +attention in the Soviet Union because it was the first cracking +case to make it to court there. The perpetrator got a suspended +sentence of 3 years in jail and was barred from future work as a +programmer.</p> + +<hr> +Node:<a name="timesink">time sink</a>, Next:<a rel="next" +href="#timeT">time T</a>, Previous:<a rel="previous" href="#timebomb">time bomb</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>time sink</b> n.</p> + +<p>[poss. by analogy with `heat sink' or `current sink'] A +project that consumes unbounded amounts of time.</p> + +<hr> +Node:<a name="timeT">time T</a>, Next:<a rel="next" href="#times-or-divided-by">times-or-divided-by</a>, Previous:<a rel="previous" href="#timesink">time sink</a>, Up:<a rel="up" +href="#chap20">= T =</a> <br> + + +<p><b>time T</b> /ti:m T/ n.</p> + +<p>1. An unspecified but usually well-understood time, often used +in conjunction with a later time T+1. "We'll meet on campus at +time T or at Louie's at time T+1" means, in the context of going +out for dinner: "We can meet on campus and go to Louie's, or we +can meet at Louie's itself a bit later." (Louie's was a Chinese +restaurant in Palo Alto that was a favorite with hackers.) Had +the number 30 been used instead of the number 1, it would have +implied that the travel time from campus to Louie's is 30 +minutes; whatever time T is (and that hasn't been decided on +yet), you can meet half an hour later at Louie's than you could +on campus and end up eating at the same time. See also <b><a +href="#sincetimeTequalsminusinfinity">since time T +equals minus infinity</a></b>.</p> + +<hr> +Node:<a name="times-or-divided-by">times-or-divided-by</a>, +Next:<a rel="next" href="#TINC">TINC</a>, Previous:<a rel="previous" href="#timeT">time T</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>times-or-divided-by</b> quant.</p> + +<p>[by analogy with `plus-or-minus'] Term occasionally used when +describing the uncertainty associated with a scheduling estimate, +for either humorous or brutally honest effect. For a software +project, the scheduling uncertainty factor is usually at least +2.</p> + +<hr> +Node:<a name="TINC">TINC</a>, Next:<a rel="next" href="#Tinkerbellprogram">Tinkerbell program</a>, Previous:<a rel="previous" href="#times-or-divided-by">times-or-divided-by</a>, +Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>TINC</b> //</p> + +<p>[Usenet] Abbreviation: "There Is No Cabal". See <b><a href="#backbonecabal">backbone cabal</a></b> and <b><a href="#NANA">NANA</a></b>, but note that this abbreviation did not +enter use until long after the dispersal of the backbone +cabal.</p> + +<hr> +Node:<a name="Tinkerbellprogram">Tinkerbell program</a>, +Next:<a rel="next" href="#TINLC">TINLC</a>, Previous:<a rel="previous" href="#TINC">TINC</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>Tinkerbell program</b> n.</p> + +<p>[Great Britain] A monitoring program used to scan incoming +network calls and generate alerts when calls are received from +particular sites, or when logins are attempted using certain IDs. +Named after `Project Tinkerbell', an experimental phone-tapping +program developed by British Telecom in the early 1980s.</p> + +<hr> +Node:<a name="TINLC">TINLC</a>, Next:<a rel="next" href="#tipoftheicecube">tip of the ice-cube</a>, Previous:<a +rel="previous" href="#Tinkerbellprogram">Tinkerbell +program</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>TINLC</b> //</p> + +<p>Abbreviation: "There Is No Lumber Cartel". See <b><a href="#LumberCartel">Lumber Cartel</a></b>. TINLC is a takeoff on +<b><a href="#TINC">TINC</a></b>.</p> + +<hr> +Node:<a name="tipoftheicecube">tip of the ice-cube</a>, +Next:<a rel="next" href="#tirediron">tired iron</a>, +Previous:<a rel="previous" href="#TINLC">TINLC</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>tip of the ice-cube</b> n. //</p> + +<p>[IBM] The visible part of something small and insignificant. +Used as an ironic comment in situations where `tip of the +iceberg' might be appropriate if the subject were at all +important.</p> + +<hr> +Node:<a name="tirediron">tired iron</a>, Next:<a rel="next" +href="#titsonakeyboard">tits on a keyboard</a>, +Previous:<a rel="previous" href="#tipoftheicecube">tip +of the ice-cube</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + + +<p><b>tired iron</b> n.</p> + +<p>[IBM] Hardware that is perfectly functional but far enough +behind the state of the art to have been superseded by new +products, presumably with sufficient improvement in bang-per-buck +that the old stuff is starting to look a bit like a <b><a href="#dinosaur">dinosaur</a></b>.</p> + +<hr> +Node:<a name="titsonakeyboard">tits on a keyboard</a>, +Next:<a rel="next" href="#TLA">TLA</a>, Previous:<a rel="previous" href="#tirediron">tired iron</a>, Up:<a rel="up" +href="#chap20">= T =</a> <br> + + +<p><b>tits on a keyboard</b> n.</p> + +<p>Small bumps on certain keycaps to keep touch-typists +registered. Usually on the <code>5</code> of a numeric keypad, +and on the <code>F</code> and <code>J</code> of a <b><a href="#QWERTY">QWERTY</a></b> keyboard; but older Macs, perverse as +usual, had them on the <code>D</code> and <code>K</code> keys +(this changed in 1999).</p> + +<hr> +Node:<a name="TLA">TLA</a>, Next:<a rel="next" href="#TM">(TM)</a>, Previous:<a rel="previous" href="#titsonakeyboard">tits on a keyboard</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>TLA</b> /T-L-A/ n.</p> + +<p>[Three-Letter Acronym] 1. Self-describing abbreviation for a +species with which computing terminology is infested. 2. Any +confusing acronym. Examples include MCA, FTP, SNA, CPU, MMU, +SCCS, DMU, FPU, NNTP, TLA. People who like this looser usage +argue that not all TLAs have three letters, just as not all +four-letter words have four letters. One also hears of `ETLA' +(Extended Three-Letter Acronym, pronounced /ee tee el ay/) being +used to describe four-letter acronyms. The term `SFLA' (Stupid +Four-Letter Acronym) has also been reported. See also <b><a href="#YABA">YABA</a></b>.</p> + +<p>The self-effacing phrase "TDM TLA" (Too Damn +Many<small>...</small>) is often used to bemoan the plethora of +TLAs in use. In 1989, a random of the journalistic persuasion +asked hacker Paul Boutin "What do you think will be the biggest +problem in computing in the 90s?" Paul's straight-faced response: +"There are only 17,000 three-letter acronyms." (To be exact, +there are 26^3 = 17,576.) There is probably some karmic justice +in the fact that Paul Boutin subsequently became a +journalist.</p> + +<hr> +Node:<a name="TM">(TM)</a>, Next:<a rel="next" href="#TMRC">TMRC</a>, Previous:<a rel="previous" href="#TLA">TLA</a>, +Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>(TM)</b> //</p> + +<p>[Usenet] ASCII rendition of the trademark-superscript symbol +appended to phrases that the author feels should be recorded for +posterity, perhaps in future editions of this lexicon. Sometimes +used ironically as a form of protest against the recent spate of +software and algorithm patents and `look and feel' lawsuits. See +also <b><a href="#UNX">UNX</a></b>.</p> + +<hr> +Node:<a name="TMRC">TMRC</a>, Next:<a rel="next" href="#TMRCie">TMRCie</a>, Previous:<a rel="previous" href="#TM">(TM)</a>, Up:<a rel="up" href="#chap20">= T =</a> +<br> + + +<p><b>TMRC</b> /tmerk'/ n.</p> + +<p>The Tech Model Railroad Club at MIT, one of the wellsprings of +hacker culture. The 1959 "Dictionary of the TMRC Language" +compiled by Peter Samson included several terms that became +basics of the hackish vocabulary (see esp. <b><a href="#foo">foo</a></b>, <b><a href="#mung">mung</a></b>, and <b><a +href="#frob">frob</a></b>).</p> + +<p>By 1962, TMRC's legendary layout was already a marvel of +complexity and has grown in the years since. All the features +described here were still present when the old layout was +decomissioned in 1998 just before the demolition of MIT Building +20, and will almost certainly be retained when the old layout is +rebuilt (expected in 2003). The control system alone featured +about 1200 relays. There were <b><a href="#scramswitch">scram +switch</a></b>es located at numerous places around the room that +could be thwacked if something undesirable was about to occur, +such as a train going full-bore at an obstruction. Another +feature of the system was a digital clock on the dispatch board, +which was itself something of a wonder in those bygone days +before cheap LEDs and seven-segment displays. When someone hit a +scram switch the clock stopped and the display was replaced with +the word `FOO'; at TMRC the scram switches are therefore called +`foo switches'.</p> + +<p>Steven Levy, in his book "Hackers" (see the <b><a href="#Bibliography">Bibliography</a></b> in Appendix C), gives a +stimulating account of those early years. TMRC's Signals and +Power Committee included many of the early PDP-1 hackers and the +people who later became the core of the MIT AI Lab staff. Thirty +years later that connection is still very much alive, and this +lexicon accordingly includes a number of entries from a recent +revision of the TMRC dictionary.</p> + +<p>TMRC has a web page at http://web.mit.edu/tmrc/www/.</p> + +<hr> +Node:<a name="TMRCie">TMRCie</a>, Next:<a rel="next" href="#TMTOWTDI">TMTOWTDI</a>, Previous:<a rel="previous" href="#TMRC">TMRC</a>, Up:<a rel="up" href="#chap20">= T =</a> +<br> + + +<p><b>TMRCie</b> /tmerk'ee/, n.</p> + +<p>[MIT] A denizen of <b><a href="#TMRC">TMRC</a></b>.</p> + +<hr> +Node:<a name="TMTOWTDI">TMTOWTDI</a>, Next:<a rel="next" href="#toafirstapproximation">to a first approximation</a>, +Previous:<a rel="previous" href="#TMRCie">TMRCie</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>TMTOWTDI</b> /tim-toh'-dee/</p> + +<p>There's More Than One Way To Do It. This abbreviation of the +official motto of <b><a href="#Perl">Perl</a></b> is frequently +used on newsgroups and mailing lists related to that +language.</p> + +<hr> +Node:<a name="toafirstapproximation">to a first +approximation</a>, Next:<a rel="next" href="#toazerothapproximation">to a zeroth approximation</a>, +Previous:<a rel="previous" href="#TMTOWTDI">TMTOWTDI</a>, Up:<a +rel="up" href="#chap20">= T =</a> <br> + + +<p><b>to a first approximation</b> adj.</p> + +<p>1. [techspeak] When one is doing certain numerical +computations, an approximate solution may be computed by any of +several heuristic methods, then refined to a final value. By +using the starting point of a first approximation of the answer, +one can write an algorithm that converges more quickly to the +correct result. 2. In jargon, a preface to any comment that +indicates that the comment is only approximately true. The remark +"To a first approximation, I feel good" might indicate that +deeper questioning would reveal that not all is perfect (e.g., a +nagging cough still remains after an illness).</p> + +<hr> +Node:<a name="toazerothapproximation">to a zeroth +approximation</a>, Next:<a rel="next" href="#toad">toad</a>, +Previous:<a rel="previous" href="#toafirstapproximation">to a first approximation</a>, +Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>to a zeroth approximation</b></p> + +<p>[from `to a first approximation'] A <i>really</i> sloppy +approximation; a wild guess. Compare <b><a href="#socialsciencenumber">social science number</a></b>.</p> + +<hr> +Node:<a name="toad">toad</a>, Next:<a rel="next" href="#toast">toast</a>, Previous:<a rel="previous" href="#toazerothapproximation">to a zeroth approximation</a>, +Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>toad</b> vt. [MUD]</p> + +<p>1. Notionally, to change a <b><a href="#MUD">MUD</a></b> +player into a toad. 2. To permanently and totally exile a player +from the MUD. A very serious action, which can only be done by a +MUD <b><a href="#wizard">wizard</a></b>; often involves a lot of +debate among the other characters first. See also <b><a href="#frog">frog</a></b>, <b><a href="#FOD">FOD</a></b>.</p> + +<hr> +Node:<a name="toast">toast</a>, Next:<a rel="next" href="#toaster">toaster</a>, Previous:<a rel="previous" href="#toad">toad</a>, Up:<a rel="up" href="#chap20">= T =</a> +<br> + + +<p><b>toast</b> 1. n.</p> + +<p>Any completely inoperable system or component, esp. one that +has just crashed and burned: "Uh, oh <small>...</small> I think +the serial board is toast." 2. vt. To cause a system to crash +accidentally, especially in a manner that requires manual +rebooting. "Rick just toasted the <b><a href="#firewallmachine">firewall machine</a></b> again." Compare +<b><a href="#fried">fried</a></b>.</p> + +<hr> +Node:<a name="toaster">toaster</a>, Next:<a rel="next" href="#toeprint">toeprint</a>, Previous:<a rel="previous" href="#toast">toast</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + + +<p><b>toaster</b> n.</p> + +<p>1. The archetypal really stupid application for an embedded +microprocessor controller; often used in comments that imply that +a scheme is inappropriate technology (but see <b><a href="#elevatorcontroller">elevator controller</a></b>). "<b><a +href="#DWIM">DWIM</a></b> for an assembler? That'd be as silly as +running Unix on your toaster!" +2. A very, very dumb computer. "You could run this program on any +dumb toaster." See <b><a href="#bittybox">bitty box</a></b>, +<b><a href="#Getarealcomputer">Get a real +computer!</a></b>, <b><a href="#toy">toy</a></b>, <b><a href="#beigetoaster">beige toaster</a></b>. 3. A Macintosh, esp. +the Classic Mac. Some hold that this is implied by sense 2. 4. A +peripheral device. "I bought my box without toasters, but since +then I've added two boards and a second disk drive." 5. A +specialized computer used as an appliance. See <b><a href="#webtoaster">web toaster</a></b>, <b><a href="#videotoaster">video toaster</a></b>.</p> + +<hr> +Node:<a name="toeprint">toeprint</a>, Next:<a rel="next" href="#toggle">toggle</a>, Previous:<a rel="previous" href="#toaster">toaster</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + + +<p><b>toeprint</b> n.</p> + +<p>A <b><a href="#footprint">footprint</a></b> of especially +small size.</p> + +<hr> +Node:<a name="toggle">toggle</a>, Next:<a rel="next" href="#tool">tool</a>, Previous:<a rel="previous" href="#toeprint">toeprint</a>, Up:<a rel="up" href="#chap20">= +T =</a> <br> + + +<p><b>toggle</b> vt.</p> + +<p>To change a <b><a href="#bit">bit</a></b> from whatever state +it is in to the other state; to change from 1 to 0 or from 0 to +1. This comes from `toggle switches', such as standard light +switches, though the word `toggle' actually refers to the +mechanism that keeps the switch in the position to which it is +flipped rather than to the fact that the switch has two +positions. There are four things you can do to a bit: set it +(force it to be 1), clear (or zero) it, leave it alone, or toggle +it. (Mathematically, one would say that there are four distinct +boolean-valued functions of one boolean argument, but saying that +is much less fun than talking about toggling bits.)</p> + +<hr> +Node:<a name="tool">tool</a>, Next:<a rel="next" href="#toolsmith">toolsmith</a>, Previous:<a rel="previous" href="#toggle">toggle</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + + +<p><b>tool</b> 1. n.</p> + +<p>A program used primarily to create, manipulate, modify, or +analyze other programs, such as a compiler or an editor or a +cross-referencing program. Oppose <b><a href="#app">app</a></b>, +<b><a href="#operatingsystem">operating system</a></b>. 2. +[Unix] An application program with a simple, `transparent' +(typically text-stream) interface designed specifically to be +used in programmed combination with other tools (see <b><a href="#filter">filter</a></b>, <b><a href="#plumbing">plumbing</a></b>). 3. [MIT: general to students +there] vi. To work; to study (connotes tedium). The TMRC +Dictionary defined this as "to set one's brain to the +grindstone". See <b><a href="#hack">hack</a></b>. 4. n. [MIT] A +student who studies too much and hacks too little. (MIT's student +humor magazine rejoices in the name "Tool and Die".)</p> + +<hr> +Node:<a name="toolsmith">toolsmith</a>, Next:<a rel="next" href="#toor">toor</a>, Previous:<a rel="previous" href="#tool">tool</a>, Up:<a rel="up" href="#chap20">= T =</a> +<br> + + +<p><b>toolsmith</b> n.</p> + +<p>The software equivalent of a tool-and-die specialist; one who +specializes in making the <b><a href="#tool">tool</a></b>s with +which other programmers create applications. Many hackers +consider this more fun than applications per se; to understand +why, see <b><a href="#uninteresting">uninteresting</a></b>. Jon +Bentley, in the "Bumper-Sticker Computer Science" chapter of his +book "More Programming Pearls", quotes Dick Sites from <b><a +href="#DEC">DEC</a></b> as saying "I'd rather write programs to +write programs than write programs".</p> + +<hr> +Node:<a name="toor">toor</a>, Next:<a rel="next" href="#topicdrift">topic drift</a>, Previous:<a rel="previous" +href="#toolsmith">toolsmith</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>toor</b> n.</p> + +<p>The Bourne-Again Super-user. An alternate account with UID of +0, created on Unix machines where the root user has an +inconvenient choice of shell. Compare <b><a href="#avatar">avatar</a></b>.</p> + +<hr> +Node:<a name="topicdrift">topic drift</a>, Next:<a rel="next" +href="#topicgroup">topic group</a>, Previous:<a rel="previous" +href="#toor">toor</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + + +<p><b>topic drift</b> n.</p> + +<p>Term used on GEnie, Usenet and other electronic fora to +describe the tendency of a <b><a href="#thread">thread</a></b> to +drift away from the original subject of discussion (and thus, +from the Subject header of the originating message), or the +results of that tendency. The header in each post can be changed +to keep current with the posts, but usually isn't due to +forgetfulness or laziness. A single post may often result in +several posts each responding to a different point in the +original. Some subthreads will actually be in response to some +off-the-cuff side comment, possibly degenerating into a <b><a +href="#flamewarr">flame war</a></b>, or just as often evolving +into a separate discussion. Hence, discussions aren't really so +much threads as they are trees. Except that they don't really +have leaves, or multiple branching roots; usually some lines of +discussion will just sort of die off after everyone gets tired of +them. This could take anywhere from hours to weeks, or even +longer.</p> + +<p>The term `topic drift' is often used in gentle reminders that +the discussion has strayed off any useful track. "I think we +started with a question about Niven's last book, but we've ended +up discussing the sexual habits of the common marmoset. Now +<i>that's</i> topic drift!"</p> + +<hr> +Node:<a name="topicgroup">topic group</a>, Next:<a rel="next" +href="#TOPS-10">TOPS-10</a>, Previous:<a rel="previous" href="#topicdrift">topic drift</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>topic group</b> n.</p> + +<p>Syn. <b><a href="#forum">forum</a></b>.</p> + +<hr> +Node:<a name="TOPS-10">TOPS-10</a>, Next:<a rel="next" href="#TOPS-20">TOPS-20</a>, Previous:<a rel="previous" href="#topicgroup">topic group</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>TOPS-10</b> /tops-ten/ n.</p> + +<p><b><a href="#DEC">DEC</a></b>'s proprietary OS for the fabled +<b><a href="#PDP-10">PDP-10</a></b> machines, long a favorite of +hackers but now effectively extinct. A fountain of hacker +folklore; see Appendix A. See also <b><a href="#ITS">ITS</a></b>, +<b><a href="#TOPS-20">TOPS-20</a></b>, <b><a href="#TWENEX">TWENEX</a></b>, <b><a href="#VMS">VMS</a></b>, <b><a +href="#operatingsystem">operating system</a></b>. TOPS-10 was +sometimes called BOTS-10 (from `bottoms-ten') as a comment on the +inappropriateness of describing it as the top of anything.</p> + +<hr> +Node:<a name="TOPS-20">TOPS-20</a>, Next:<a rel="next" href="#tourist">tourist</a>, Previous:<a rel="previous" href="#TOPS-10">TOPS-10</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + + +<p><b>TOPS-20</b> /tops-twen'tee/ n.</p> + +<p>See <b><a href="#TWENEX">TWENEX</a></b>.</p> + +<hr> +Node:<a name="tourist">tourist</a>, Next:<a rel="next" href="#touristinformation">tourist information</a>, Previous:<a +rel="previous" href="#TOPS-20">TOPS-20</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>tourist</b> n.</p> + +<p>1. [ITS] A guest on the system, especially one who generally +logs in over a network from a remote location for <b><a href="#commmode">comm mode</a></b>, email, games, and other trivial +purposes. One step below <b><a href="#luser">luser</a></b>. ITS +hackers often used to spell this <b><a href="#turist">turist</a></b>, perhaps by some sort of tenuous analogy +with <b><a href="#luser">luser</a></b> (this usage may also have +expressed the ITS culture's penchant for six-letterisms, and-or +been some sort of tribute to Alan Turing). Compare <b><a href="#twink">twink</a></b>, <b><a href="#lurker">lurker</a></b>, +<b><a href="#readonlyuser">read-only user</a></b>. 2. [IRC] +An <b><a href="#IRC">IRC</a></b> user who goes from channel to +channel without saying anything; see <b><a href="#channelhopping">channel hopping</a></b>.</p> + +<hr> +Node:<a name="touristinformation">tourist information</a>, +Next:<a rel="next" href="#touristic">touristic</a>, Previous:<a +rel="previous" href="#tourist">tourist</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>tourist information</b> n.</p> + +<p>Information in an on-line display that is not immediately +useful, but contributes to a viewer's gestalt of what's going on +with the software or hardware behind it. Whether a given piece of +info falls in this category depends partly on what the user is +looking for at any given time. The `bytes free' information at +the bottom of an MS-DOS <code>dir</code> display is tourist +information; so (most of the time) is the TIME information in a +Unix <code>ps(1)</code> display.</p> + +<hr> +Node:<a name="touristic">touristic</a>, Next:<a rel="next" href="#toy">toy</a>, Previous:<a rel="previous" href="#touristinformation">tourist information</a>, Up:<a rel="up" +href="#chap20">= T =</a> <br> + + +<p><b>touristic</b> adj.</p> + +<p>Having the quality of a <b><a href="#tourist">tourist</a></b>. +Often used as a pejorative, as in `losing touristic scum'. Often +spelled `turistic' or `turistik', so that phrase might be more +properly rendered `lusing turistic scum'.</p> + +<hr> +Node:<a name="toy">toy</a>, Next:<a rel="next" href="#toylanguage">toy language</a>, Previous:<a rel="previous" +href="#touristic">touristic</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>toy</b> n.</p> + +<p>A computer system; always used with qualifiers. 1. `nice toy': +One that supports the speaker's hacking style adequately. 2. +`just a toy': A machine that yields insufficient <b><a href="#computron">computron</a></b>s for the speaker's preferred uses. +This is not condemnatory, as is <b><a href="#bittybox">bitty +box</a></b>; toys can at least be fun. It is also strongly +conditioned by one's expectations; Cray XMP users sometimes +consider the Cray-1 a `toy', and certainly all RISC boxes and +mainframes are toys by their standards. See also <b><a href="#Getarealcomputer">Get a real computer!</a></b>.</p> + +<hr> +Node:<a name="toylanguage">toy language</a>, Next:<a rel="next" href="#toyproblem">toy problem</a>, Previous:<a rel="previous" href="#toy">toy</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>toy language</b> n.</p> + +<p>A language useful for instructional purposes or as a +proof-of-concept for some aspect of computer-science theory, but +inadequate for general-purpose programming. <b><a href="#BadThing">Bad Thing</a></b>s can result when a toy language +is promoted as a general purpose solution for programming (see +<b><a href="#bondage-and-disciplinelanguage">bondage-and-discipline +language</a></b>); the classic example is <b><a href="#Pascal">Pascal</a></b>. Several moderately well-known +formalisms for conceptual tasks such as programming Turing +machines also qualify as toy languages in a less negative sense. +See also <b><a href="#MFTL">MFTL</a></b>.</p> + +<hr> +Node:<a name="toyproblem">toy problem</a>, Next:<a rel="next" +href="#toyprogram">toy program</a>, Previous:<a rel="previous" +href="#toylanguage">toy language</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>toy problem</b> n.</p> + +<p>[AI] A deliberately oversimplified case of a challenging +problem used to investigate, prototype, or test algorithms for a +real problem. Sometimes used pejoratively. See also <b><a href="#gedanken">gedanken</a></b>, <b><a href="#toyprogram">toy +program</a></b>.</p> + +<hr> +Node:<a name="toyprogram">toy program</a>, Next:<a rel="next" +href="#trampoline">trampoline</a>, Previous:<a rel="previous" +href="#toyproblem">toy problem</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>toy program</b> n.</p> + +<p>1. One that can be readily comprehended; hence, a trivial +program (compare <b><a href="#noddy">noddy</a></b>). 2. One for +which the effort of initial coding dominates the costs through +its life cycle. See also <b><a href="#noddy">noddy</a></b>.</p> + +<hr> +Node:<a name="trampoline">trampoline</a>, Next:<a rel="next" +href="#trap">trap</a>, Previous:<a rel="previous" href="#toyprogram">toy program</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>trampoline</b> n.</p> + +<p>An incredibly <b><a href="#hairy">hairy</a></b> technique, +found in some <b><a href="#HLL">HLL</a></b> and program-overlay +implementations (e.g., on the Macintosh), that involves +on-the-fly generation of small executable (and, likely as not, +self-modifying) code objects to do indirection between code +sections. Under BSD and possibly in other Unixes, trampoline code +is used to transfer control from the kernel back to user mode +when a signal (which has had a handler installed) is sent to a +process. hese pieces of <b><a href="#livedata">live +data</a></b> are called `trampolines'. Trampolines are +notoriously difficult to understand in action; in fact, it is +said by those who use this term that the trampoline that doesn't +bend your brain is not the true trampoline. See also <b><a href="#snap">snap</a></b>.</p> + +<hr> +Node:<a name="trap">trap</a>, Next:<a rel="next" href="#trapDoor">trap door</a>, Previous:<a rel="previous" href="#trampoline">trampoline</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>trap</b></p> + +<p>1. n. A program interrupt, usually an interrupt caused by some +exceptional situation in the user program. In most cases, the OS +performs some action, then returns control to the program. 2. vi. +To cause a trap. "These instructions trap to the monitor." Also +used transitively to indicate the cause of the trap. "The monitor +traps all input/output instructions."</p> + +<p>This term is associated with assembler programming +(`interrupt' or `exception' is more common among <b><a href="#HLL">HLL</a></b> programmers) and appears to be fading into +history among programmers as the role of assembler continues to +shrink. However, it is still important to computer architects and +systems hackers (see <b><a href="#system">system</a></b>, sense +1), who use it to distinguish deterministically repeatable +exceptions from timing-dependent ones (such as I/O +interrupts).</p> + +<hr> +Node:<a name="trapDoor">trap door</a>, Next:<a rel="next" +href="#trash">trash</a>, Previous:<a rel="previous" href="#trap">trap</a>, Up:<a rel="up" href="#chap20">= T =</a> +<br> + + +<p><b>trap door</b> n.</p> + +<p>(alt. `trapdoor') 1. Syn. <b><a href="#backdoor">back +door</a></b> -- a <b><a href="#BadThing">Bad Thing</a></b>. 2. +[techspeak] A `trap-door function' is one which is easy to +compute but very difficult to compute the inverse of. Such +functions are <b><a href="#GoodThing">Good Thing</a></b>s with +important applications in cryptography, specifically in the +construction of public-key cryptosystems.</p> + +<hr> +Node:<a name="trash">trash</a>, Next:<a rel="next" href="#trawl">trawl</a>, Previous:<a rel="previous" href="#trapDoor">trap door</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>trash</b> vt.</p> + +<p>To destroy the contents of (said of a data structure). The +most common of the family of near-synonyms including <b><a href="#mung">mung</a></b>, <b><a href="#mangle">mangle</a></b>, and +<b><a href="#scribble">scribble</a></b>.</p> + +<hr> +Node:<a name="trawl">trawl</a>, Next:<a rel="next" href="#tree-killer">tree-killer</a>, Previous:<a rel="previous" href="#trash">trash</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + + +<p><b>trawl</b> v.</p> + +<p>To sift through large volumes of data (e.g., Usenet postings, +FTP archives, or the Jargon File) looking for something of +interest.</p> + +<hr> +Node:<a name="tree-killer">tree-killer</a>, Next:<a rel="next" +href="#treeware">treeware</a>, Previous:<a rel="previous" href="#trawl">trawl</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + + +<p><b>tree-killer</b> n.</p> + +<p>[Sun] 1. A printer. 2. A person who wastes paper. This epithet +should be interpreted in a broad sense; `wasting paper' includes +the production of <b><a href="#spiffy">spiffy</a></b> but <b><a +href="#content-free">content-free</a></b> documents. Thus, most +<b><a href="#suit">suit</a></b>s are tree-killers. The negative +loading of this term may reflect the epithet `tree-killer' +applied by Treebeard the Ent to the Orcs in J.R.R. Tolkien's +"Lord of the Rings" (see also <b><a href="#elvish">elvish</a></b>, <b><a href="#elderdays">elder +days</a></b>).</p> + +<hr> +Node:<a name="treeware">treeware</a>, Next:<a rel="next" href="#trit">trit</a>, Previous:<a rel="previous" href="#tree-killer">tree-killer</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>treeware</b> /tree'weir/ n.</p> + +<p>Printouts, books, and other information media made from pulped +dead trees. Compare <b><a href="#tree-killer">tree-killer</a></b>, see <b><a href="#documentation">documentation</a></b>.</p> + +<hr> +Node:<a name="trit">trit</a>, Next:<a rel="next" href="#trivial">trivial</a>, Previous:<a rel="previous" href="#treeware">treeware</a>, Up:<a rel="up" href="#chap20">= +T =</a> <br> + + +<p><b>trit</b> /trit/ n.</p> + +<p>[by analogy with `bit'] One base-3 digit; the amount of +information conveyed by a selection among one of three equally +likely outcomes (see also <b><a href="#bit">bit</a></b>). Trits +arise, for example, in the context of a <b><a href="#flag">flag</a></b> that should actually be able to assume +<i>three</i> values -- such as yes, no, or unknown. Trits are +sometimes jokingly called `3-state bits'. A trit may be +semi-seriously referred to as `a bit and a half', although it is +linearly equivalent to 1.5849625 bits (that is, log2(3) +bits).</p> + +<hr> +Node:<a name="trivial">trivial</a>, Next:<a rel="next" href="#troff">troff</a>, Previous:<a rel="previous" href="#trit">trit</a>, Up:<a rel="up" href="#chap20">= T =</a> +<br> + + +<p><b>trivial</b> adj.</p> + +<p>1. Too simple to bother detailing. 2. Not worth the speaker's +time. 3. Complex, but solvable by methods so well known that +anyone not utterly <b><a href="#cretinous">cretinous</a></b> +would have thought of them already. 4. Any problem one has +already solved (some claim that hackish `trivial' usually +evaluates to `I've seen it before'). Hackers' notions of +triviality may be quite at variance with those of non-hackers. +See <b><a href="#nontrivial">nontrivial</a></b>, <b><a href="#uninteresting">uninteresting</a></b>.</p> + +<p>The physicist Richard Feynman, who had the hacker nature to an +amazing degree (see his essay "Los Alamos From Below" in "Surely +You're Joking, Mr. Feynman!"), defined `trivial theorem' as "one +that has already been proved".</p> + +<hr> +Node:<a name="troff">troff</a>, Next:<a rel="next" href="#troglodyte">troglodyte</a>, Previous:<a rel="previous" href="#trivial">trivial</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + + +<p><b>troff</b> /T'rof/ or /trof/ n.</p> + +<p>[Unix] The gray eminence of Unix text processing; a formatting +and phototypesetting program, written originally in PDP-11 +assembler and then in barely-structured early C by the late +Joseph Ossanna, modeled after the earlier ROFF which was in turn +modeled after the <b><a href="#Multics">Multics</a></b> and <b><a +href="#CTSS">CTSS</a></b> program RUNOFF by Jerome Saltzer +(<i>that</i> name came from the expression "to run off a +copy"). A companion program, <b><a href="#nroff">nroff</a></b>, +formats output for terminals and line printers.</p> + +<p>In 1979, Brian Kernighan modified troff so that it could drive +phototypesetters other than the Graphic Systems CAT. His paper +describing that work ("A Typesetter-independent troff," AT&T +CSTR #97) explains troff's durability. After discussing the +program's "obvious deficiencies -- a rebarbative input syntax, +mysterious and undocumented properties in some areas, and a +voracious appetite for computer resources" and noting the +ugliness and extreme hairiness of the code and internals, +Kernighan concludes:</p> + +<blockquote>None of these remarks should be taken as denigrating +Ossanna's accomplishment with TROFF. It has proven a remarkably +robust tool, taking unbelievable abuse from a variety of +preprocessors and being forced into uses that were never +conceived of in the original design, all with considerable grace +under fire.</blockquote> + +<p>The success of <b><a href="#TeX">TeX</a></b> and desktop +publishing systems have reduced <code>troff</code>'s relative +importance, but this tribute perfectly captures the strengths +that secured <code>troff</code> a place in hacker folklore; +indeed, it could be taken more generally as an indication of +those qualities of good programs that, in the long run, hackers +most admire.</p> + +<hr> +Node:<a name="troglodyte">troglodyte</a>, Next:<a rel="next" +href="#troglodytemode">troglodyte mode</a>, Previous:<a rel="previous" href="#troff">troff</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>troglodyte</b> n.</p> + +<p>[Commodore] 1. A hacker who never leaves his cubicle. The term +`gnoll' (from Dungeons & Dragons) is also reported. 2. A +curmudgeon attached to an obsolescent computing environment. The +combination `ITS troglodyte' was flung around some during the +Usenet and email wringle-wrangle attending the 2.x.x revision of +the Jargon File; at least one of the people it was intended to +describe adopted it with pride.</p> + +<hr> +Node:<a name="troglodytemode">troglodyte mode</a>, Next:<a +rel="next" href="#Trojanhorse">Trojan horse</a>, Previous:<a +rel="previous" href="#troglodyte">troglodyte</a>, Up:<a rel="up" +href="#chap20">= T =</a> <br> + + +<p><b>troglodyte mode</b> n.</p> + +<p>[Rice University] Programming with the lights turned off, +sunglasses on, and the terminal inverted (black on white) because +you've been up for so many days straight that your eyes hurt (see +<b><a href="#rasterburn">raster burn</a></b>). Loud music +blaring from a stereo stacked in the corner is optional but +recommended. See <b><a href="#larvalstage">larval +stage</a></b>, <b><a href="#hackmode">hack mode</a></b>.</p> + +<hr> +Node:<a name="Trojanhorse">Trojan horse</a>, Next:<a rel="next" href="#troll">troll</a>, Previous:<a rel="previous" href="#troglodytemode">troglodyte mode</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>Trojan horse</b> n.</p> + +<p>[coined by MIT-hacker-turned-NSA-spook Dan Edwards] A +malicious, security-breaking program that is disguised as +something benign, such as a directory lister, archiver, game, or +(in one notorious 1990 case on the Mac) a program to find and +destroy viruses! See <b><a href="#backdoor">back door</a></b>, +<b><a href="#virus">virus</a></b>, <b><a href="#worm">worm</a></b>, <b><a href="#phage">phage</a></b>, <b><a +href="#mockingbird">mockingbird</a></b>.</p> + +<hr> +Node:<a name="troll">troll</a>, Next:<a rel="next" href="#Troll-O-Meter">Troll-O-Meter</a>, Previous:<a rel="previous" +href="#Trojanhorse">Trojan horse</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>troll</b> v.,n.</p> + +<p>1. [From the Usenet group <i>alt.folklore.urban</i>] To utter +a posting on <b><a href="#Usenet">Usenet</a></b> designed to +attract predictable responses or <b><a href="#flame">flame</a></b>s; or, the post itself. Derives from the +phrase "trolling for <b><a href="#newbie">newbie</a></b>s" which +in turn comes from mainstream "trolling", a style of fishing in +which one trails bait through a likely spot hoping for a bite. +The well-constructed troll is a post that induces lots of newbies +and flamers to make themselves look even more clueless than they +already do, while subtly conveying to the more savvy and +experienced that it is in fact a deliberate troll. If you don't +fall for the joke, you get to be in on it. See also <b><a href="#YHBT">YHBT</a></b>. 2. An individual who chronically trolls in +sense 1; regularly posts specious arguments, flames or personal +attacks to a newsgroup, discussion list, or in email for no other +purpose than to annoy someone or disrupt a discussion. Trolls are +recognizable by the fact that the have no real interest in +learning about the topic at hand - they simply want to utter +flame bait. Like the ugly creatures they are named after, they +exhibit no redeeming characteristics, and as such, they are +recognized as a lower form of life on the net, as in, "Oh, ignore +him, he's just a troll." 3. [Berkeley] Computer lab monitor. A +popular campus job for CS students. Duties include helping +newbies and ensuring that lab policies are followed. Probably +so-called because it involves lurking in dark cavelike +corners.</p> + +<p>Some people claim that the troll (sense 1) is properly a +narrower category than <b><a href="#flamebait">flame +bait</a></b>, that a troll is categorized by containing some +assertion that is wrong but not overtly controversial. See also +<b><a href="#Troll-O-Meter">Troll-O-Meter</a></b>.</p> + +<p>The use of `troll' in either sense is a live metaphor that +readily produces elaborations and combining forms. For example, +one not infrequently sees the warning "Do not feed the troll" as +part of a followup to troll postings.</p> + +<hr> +Node:<a name="Troll-O-Meter">Troll-O-Meter</a>, Next:<a rel="next" href="#tron">tron</a>, Previous:<a rel="previous" href="#troll">troll</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + + +<p><b>Troll-O-Meter</b> n.</p> + +<p>Common Usenet jargon for a notional instrument used to measure +the quality of a Usenet <b><a href="#troll">troll</a></b>. "Come +on, everyone! If the above doesn't set off the Troll-O-Meter, +we're going to have to get him to run around with a big blinking +sign saying `I am a troll, I'm only in it for the controversy and +flames' and shooting random gobs of Jell-O(tm) at us before the +point is proven." Mentions of the Troll-O-Meter are often +accompanied by an ASCII picture of an arrow pointing at a numeric +scale. Compare <b><a href="#bogometer">bogometer</a></b>.</p> + +<hr> +Node:<a name="tron">tron</a>, Next:<a rel="next" href="#true-hacker">true-hacker</a>, Previous:<a rel="previous" href="#Troll-O-Meter">Troll-O-Meter</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>tron</b> v.</p> + +<p>[NRL, CMU; prob. fr. the movie "Tron"] To become inaccessible +except via email or <code>talk(1)</code>, especially when one is +normally available via telephone or in person. Frequently used in +the past tense, as in: "Ran seems to have tronned on us this +week" or "Gee, Ran, glad you were able to un-tron yourself". One +may also speak of `tron mode'; compare <b><a href="#spod">spod</a></b>.</p> + +<p>Note that many dialects of BASIC have a TRON/TROFF command +pair that enables/disables line number tracing; this has no +obvious relationship to the slang usage.</p> + +<hr> +Node:<a name="true-hacker">true-hacker</a>, Next:<a rel="next" +href="#tty">tty</a>, Previous:<a rel="previous" href="#tron">tron</a>, Up:<a rel="up" href="#chap20">= T =</a> +<br> + + +<p><b>true-hacker</b> n.</p> + +<p>[analogy with `trufan' from SF fandom] One who exemplifies the +primary values of hacker culture, esp. competence and helpfulness +to other hackers. A high compliment. "He spent 6 hours helping me +bring up UUCP and netnews on my FOOBAR 4000 last week -- +manifestly the act of a true-hacker." Compare <b><a href="#demigod">demigod</a></b>, oppose <b><a href="#munchkin">munchkin</a></b>.</p> + +<hr> +Node:<a name="tty">tty</a>, Next:<a rel="next" href="#tube">tube</a>, Previous:<a rel="previous" href="#true-hacker">true-hacker</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>tty</b> /T-T-Y/, /tit'ee/ n.</p> + +<p>The latter pronunciation was primarily ITS, but some Unix +people say it this way as well; this pronunciation is +<i>not</i> considered to have sexual undertones. 1. A terminal +of the teletype variety, characterized by a noisy mechanical +printer, a very limited character set, and poor print quality. +Usage: antiquated (like the TTYs themselves). See also <b><a +href="#bit-pairedkeyboard">bit-paired keyboard</a></b>. 2. +[especially Unix] Any terminal at all; sometimes used to refer to +the particular terminal controlling a given job. 3. [Unix] Any +serial port, whether or not the device connected to it is a +terminal; so called because under Unix such devices have names of +the form tty*. Ambiguity between senses 2 and 3 is common but +seldom bothersome.</p> + +<hr> +Node:<a name="tube">tube</a>, Next:<a rel="next" href="#tubetime">tube time</a>, Previous:<a rel="previous" href="#tty">tty</a>, Up:<a rel="up" href="#chap20">= T =</a> +<br> + + +<p><b>tube</b></p> + +<p>1. n. A CRT terminal. Never used in the mainstream sense of +TV; real hackers don't watch TV, except for Loony Toons, Rocky +& Bullwinkle, Trek Classic, the Simpsons, and the occasional +cheesy old swashbuckler movie. 2. [IBM] To send a copy of +something to someone else's terminal. "Tube me that note?"</p> + +<hr> +Node:<a name="tubetime">tube time</a>, Next:<a rel="next" +href="#tunafish">tunafish</a>, Previous:<a rel="previous" href="#tube">tube</a>, Up:<a rel="up" href="#chap20">= T =</a> +<br> + + +<p><b>tube time</b> n.</p> + +<p>Time spent at a terminal or console. More inclusive than +hacking time; commonly used in discussions of what parts of one's +environment one uses most heavily. "I find I'm spending too much +of my tube time reading mail since I started this revision."</p> + +<hr> +Node:<a name="tunafish">tunafish</a>, Next:<a rel="next" href="#tune">tune</a>, Previous:<a rel="previous" href="#tubetime">tube time</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>tunafish</b> n.</p> + +<p>In hackish lore, refers to the mutated punchline of an age-old +joke to be found at the bottom of the manual pages of +<code>tunefs(8)</code> in the original <b><a href="#BSD">BSD</a></b> 4.2 distribution. The joke was removed in +later releases once commercial sites started using 4.2, but +apparently restored on the 4.4BSD tape and in {Net,Free,Open}BSD. +Tunefs relates to the `tuning' of file-system parameters for +optimum performance, and at the bottom of a few pages of wizardly +inscriptions was a `BUGS' section consisting of the line "You can +tune a file system, but you can't tunafish". Variants of this can +be seen in other BSD versions, though it has been excised from +some versions by humorless management <b><a href="#droid">droid</a></b>s. The [nt]roff source for SunOS 4.1.1 +contains a comment apparently designed to prevent this: "Take +this out and a Unix Demon will dog your steps from now until the +<code>time_t</code>'s wrap around."</p> + +<p>[It has since been pointed out that indeed you can tunafish. +Usually at a canning factory... --ESR]</p> + +<hr> +Node:<a name="tune">tune</a>, Next:<a rel="next" href="#turbonerd">turbo nerd</a>, Previous:<a rel="previous" href="#tunafish">tunafish</a>, Up:<a rel="up" href="#chap20">= +T =</a> <br> + + +<p><b>tune</b> vt.</p> + +<p>[from automotive or musical usage] To optimize a program or +system for a particular environment, esp. by adjusting numerical +parameters designed as <b><a href="#hook">hook</a></b>s for +tuning, e.g., by changing <code>#define</code> lines in C. One +may `tune for time' (fastest execution), `tune for space' (least +memory use), or `tune for configuration' (most efficient use of +hardware). See <b><a href="#bum">bum</a></b>, <b><a href="#hotspot">hot spot</a></b>, <b><a href="#hand-hacking">hand-hacking</a></b>.</p> + +<hr> +Node:<a name="turbonerd">turbo nerd</a>, Next:<a rel="next" +href="#Turingtarpit">Turing tar-pit</a>, Previous:<a rel="previous" href="#tune">tune</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>turbo nerd</b> n.</p> + +<p>See <b><a href="#computergeek">computer geek</a></b>.</p> + +<hr> +Node:<a name="Turingtarpit">Turing tar-pit</a>, Next:<a rel="next" href="#turist">turist</a>, Previous:<a rel="previous" +href="#turbonerd">turbo nerd</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>Turing tar-pit</b> n.</p> + +<p>1. A place where anything is possible but nothing of interest +is practical. Alan Turing helped lay the foundations of computer +science by showing that all machines and languages capable of +expressing a certain very primitive set of operations are +logically equivalent in the kinds of computations they can carry +out, and in principle have capabilities that differ only in speed +from those of the most powerful and elegantly designed computers. +However, no machine or language exactly matching Turing's +primitive set has ever been built (other than possibly as a +classroom exercise), because it would be horribly slow and far +too painful to use. A `Turing tar-pit' is any computer language +or other tool that shares this property. That is, it's +theoretically universal -- but in practice, the harder you +struggle to get any real work done, the deeper its inadequacies +suck you in. Compare <b><a href="#bondage-and-disciplinelanguage">bondage-and-discipline +language</a></b>. 2. The perennial <b><a href="#holywars">holy +wars</a></b> over whether language A or B is the "most +powerful".</p> + +<hr> +Node:<a name="turist">turist</a>, Next:<a rel="next" href="#Tux">Tux</a>, +Previous:<a rel="previous" href="#Turingtarpit">Turing tar-pit</a>, +Up:<a rel="up" href="#chap20">= T =</a> <br> + +<p><b>turist</b> /too'rist/ n.</p> + +<p>Var. sp. of <b><a href="#tourist">tourist</a></b>, q.v. Also +in adjectival form, `turistic'. Poss. influenced by <b><a href="#luser">luser</a></b> and `Turing'.</p> + +<hr> +Node:<a name="Tux">Tux</a>, Next:<a rel="next" href="#tweak">tweak</a>, Previous:<a rel="previous" href="#turist">turist</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + +<p><b>Tux</b></p> + +<p>Tux the Penguin is the official emblem of <b><a href="#Linux">Linux</a></b>, This eventuated after a logo contest in +1996, during which Linus Torvalds endorsed the idea of a penguin +logo in a couple of famously funny postings. Linus +explained that he was once bitten by a killer penguin in +Australia and has felt a special affinity for the species ever +since. (Linus has since admitted that he was also thinking of +Feathers McGraw, the evil-genius penguin jewel thief who appeared +in a Wallace & Grommit feature cartoon, "The Wrong +Trousers".)</p> + +<p>Larry Ewing designed the +official Tux logo. It has proved a wise choice, amenable to +hundreds of recognizable variations used as emblems of +Linux-related projects, products, and user groups. In fact, Tux +has spawned an entire mythology, of which the Gospel According to +Tux and the mock-epic poem "Tuxowolf" are among the +best-known examples.</p> + +<p>There is a `real' Tux - a black-footed penguin resident at the +Bristol Zoo. Several friends of Linux bought a zoo sponsorship +for Linus as a birthday present in 1996.</p> + +<hr> +Node:<a name="tweak">tweak</a>, Next:<a rel="next" href="#tweeter">tweeter</a>, Previous:<a rel="previous" href="#Tux">Tux</a>, Up:<a rel="up" href="#chap20">= T =</a> +<br> + + +<p><b>tweak</b> vt.</p> + +<p>1. To change slightly, usually in reference to a value. Also +used synonymously with <b><a href="#twiddle">twiddle</a></b>. If +a program is almost correct, rather than figure out the precise +problem you might just keep tweaking it until it works. See <b><a +href="#frobnicate">frobnicate</a></b> and <b><a href="#fudgefactor">fudge factor</a></b>; also see <b><a href="#shotgundebugging">shotgun debugging</a></b>. 2. To <b><a +href="#tune">tune</a></b> or <b><a href="#bum">bum</a></b> a +program; preferred usage in the U.K.</p> + +<hr> +Node:<a name="tweeter">tweeter</a>, Next:<a rel="next" href="#TWENEX">TWENEX</a>, Previous:<a rel="previous" href="#tweak">tweak</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + + +<p><b>tweeter</b> n.</p> + +<p>[University of Waterloo] Syn. <b><a href="#perf">perf</a></b>, +<b><a href="#chad">chad</a></b> (sense 1). This term (like <b><a +href="#woofer">woofer</a></b>) has been in use at Waterloo since +1972 but is elsewhere unknown. In audio jargon, the word refers +to the treble speaker(s) on a hi-fi.</p> + +<hr> +Node:<a name="TWENEX">TWENEX</a>, Next:<a rel="next" href="#twiddle">twiddle</a>, Previous:<a rel="previous" href="#tweeter">tweeter</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + + +<p><b>TWENEX</b> /twe'neks/ n.</p> + +<p>The TOPS-20 operating system by <b><a href="#DEC">DEC</a></b> +-- the second proprietary OS for the PDP-10 -- preferred by most +PDP-10 hackers over TOPS-10 (that is, by those who were not <b><a +href="#ITS">ITS</a></b> or <b><a href="#WAITS">WAITS</a></b> +partisans). TOPS-20 began in 1969 as Bolt, Beranek & Newman's +TENEX operating system using special paging hardware. By the +early 1970s, almost all of the systems on the ARPANET ran TENEX. +DEC purchased the rights to TENEX from BBN and began work to make +it their own. The first in-house code name for the operating +system was VIROS (VIRtual memory Operating System); when +customers started asking questions, the name was changed to SNARK +so DEC could truthfully deny that there was any project called +VIROS. When the name SNARK became known, the name was briefly +reversed to become KRANS; this was quickly abandoned when someone +objected that `krans' meant `funeral wreath' in Swedish (though +some Swedish speakers have since said it means simply `wreath'; +this part of the story may be apocryphal). Ultimately DEC picked +TOPS-20 as the name of the operating system, and it was as +TOPS-20 that it was marketed. The hacker community, mindful of +its origins, quickly dubbed it TWENEX (a contraction of `twenty +TENEX'), even though by this point very little of the original +TENEX code remained (analogously to the differences between +AT&T V6 Unix and BSD). DEC people cringed when they heard +"TWENEX", but the term caught on nevertheless (the written +abbreviation `20x' was also used). TWENEX was successful and very +popular; in fact, there was a period in the early 1980s when it +commanded as fervent a culture of partisans as Unix or ITS -- but +DEC's decision to scrap all the internal rivals to the VAX +architecture and its relatively stodgy VMS OS killed the DEC-20 +and put a sad end to TWENEX's brief day in the sun. DEC attempted +to convince TOPS-20 users to convert to <b><a href="#VMS">VMS</a></b>, but instead, by the late 1980s, most of the +TOPS-20 hackers had migrated to Unix.</p> + +<hr> +Node:<a name="twiddle">twiddle</a>, Next:<a rel="next" href="#twilightzone">twilight zone</a>, Previous:<a rel="previous" +href="#TWENEX">TWENEX</a>, Up:<a rel="up" href="#chap20">= +T =</a> <br> + + +<p><b>twiddle</b> n.</p> + +<p>1. Tilde (ASCII 1111110, <code>~</code>). Also called +`squiggle', `sqiggle' (sic -- pronounced /skig'l/), and +`twaddle', but twiddle is the most common term. 2. A small and +insignificant change to a program. Usually fixes one bug and +generates several new ones (see also <b><a href="#shotgundebugging">shotgun debugging</a></b>). 3. vt. To +change something in a small way. Bits, for example, are often +twiddled. Twiddling a switch or <b><a href="#knobs">knobs</a></b> +implies much less sense of purpose than toggling or tweaking it; +see <b><a href="#frobnicate">frobnicate</a></b>. To speak of +twiddling a bit connotes aimlessness, and at best doesn't specify +what you're doing to the bit; `toggling a bit' has a more +specific meaning (see <b><a href="#bittwiddling">bit +twiddling</a></b>, <b><a href="#toggle">toggle</a></b>). 4. +Uncommon name for the <b><a href="#twirlingbaton">twirling +baton</a></b> prompt.</p> + +<hr> +Node:<a name="twilightzone">twilight zone</a>, Next:<a rel="next" href="#twink">twink</a>, Previous:<a rel="previous" href="#twiddle">twiddle</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + + +<p><b>twilight zone</b> n. //</p> + +<p>[IRC] Notionally, the area of cyberspace where <b><a href="#IRC">IRC</a></b> operators live. An <b><a href="#op">op</a></b> +is said to have a "connection to the twilight zone".</p> + +<hr> +Node:<a name="twink">twink</a>, Next:<a rel="next" href="#twirlingbaton">twirling baton</a>, Previous:<a rel="previous" href="#twilightzone">twilight zone</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>twink</b> /twink/ n.</p> + +<p>1. [Berkeley] A clue-repellant user; the next step beyond a +clueless one. 2. [UCSC] A <b><a href="#readonlyuser">read-only user</a></b>. Also reported on the +Usenet group <i>soc.motss</i>; may derive from gay slang for a +cute young thing with nothing upstairs (compare mainstream +`chick').</p> + +<hr> +Node:<a name="twirlingbaton">twirling baton</a>, Next:<a rel="next" href="#twopi">two pi</a>, Previous:<a rel="previous" +href="#twink">twink</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + + +<p><b>twirling baton</b> n.</p> + +<p>[PLATO] The overstrike sequence -/|\-/|\- which produces an +animated twirling baton. If you output it with a single backspace +between characters, the baton spins in place. If you output the +sequence BS SP between characters, the baton spins from left to +right. If you output BS SP BS BS between characters, the baton +spins from right to left. This is also occasionally called a +twiddle prompt.</p> + +<p>The twirling baton was a popular component of animated +signature files on the pioneering PLATO educational timesharing +system. The <code>archie</code> Internet service is perhaps the +best-known baton program today; it uses the twirling baton as an +idler indicating that the program is working on a query. The +twirling baton is also used as a boot progress indicator on +several BSD variants of Unix; if it stops you're probably going +to have a long and trying day.</p> + +<hr> +Node:<a name="twopi">two pi</a>, Next:<a rel="next" href="#two-to-the-N">two-to-the-N</a>, Previous:<a rel="previous" +href="#twirlingbaton">twirling baton</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>two pi</b> quant.</p> + +<p>The number of years it takes to finish one's thesis. Occurs in +stories in the following form: "He started on his thesis; 2 pi +years later<small>...</small>"</p> + +<hr> +Node:<a name="two-to-the-N">two-to-the-N</a>, Next:<a rel="next" +href="#twonkie">twonkie</a>, Previous:<a rel="previous" href="#twopi">two pi</a>, Up:<a rel="up" href="#chap20">= T +=</a> <br> + + +<p><b>two-to-the-N</b> quant.</p> + +<p>An amount much larger than <b><a href="#N">N</a></b> but +smaller than <b><a href="#infinity">infinity</a></b>. "I have +2-to-the-N things to do before I can go out for lunch" means you +probably won't show up.</p> + +<hr> +Node:<a name="twonkie">twonkie</a>, Next:<a rel="next" href="#u-">u-</a>, Previous:<a rel="previous" href="#two-to-the-N">two-to-the-N</a>, Up:<a rel="up" href="#chap20">= T =</a> <br> + + +<p><b>twonkie</b> /twon'kee/ n.</p> + +<p>The software equivalent of a Twinkie (a variety of +sugar-loaded junk food, or (in gay slang with a small t) the male +equivalent of `chick'); a useless `feature' added to look sexy +and placate a <b><a href="#marketroid">marketroid</a></b> +(compare <b><a href="#Saturdaynightspecial">Saturday-night +special</a></b>). The term may also be related to "The Twonky", +title menace of a classic SF short story by Lewis Padgett (Henry +Kuttner and C. L. Moore), first published in the September 1942 +"Astounding Science Fiction" and subsequently much +anthologized.</p> + +<hr> +Node:<a name="chap21">= U =</a>, Next:<a rel="next" href="#chap22">= V =</a>, Previous:<a rel="previous" href="#chap20">= T =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= U =</h2> + +<ul> +<li><a href="#u-">u-</a>:</li> + +<li><a href="#UBD">UBD</a>:</li> + +<li><a href="#UBE">UBE</a>:</li> + +<li><a href="#UCE">UCE</a>:</li> + +<li><a href="#UDP">UDP</a>:</li> + +<li><a href="#UNX">UNX</a>:</li> + +<li><a href="#undefinedexternalreference">undefined external reference</a>:</li> + +<li><a href="#underthehood">under the hood</a>:</li> + +<li><a href="#undocumentedfeature">undocumented feature</a>:</li> + +<li><a href="#uninteresting">uninteresting</a>:</li> + +<li><a href="#Unix">Unix</a>:</li> + +<li><a href="#Unixbraindamage">Unix brain damage</a>:</li> + +<li><a href="#Unixconspiracy">Unix conspiracy</a>:</li> + +<li><a href="#Unixweenie">Unix weenie</a>:</li> + +<li><a href="#unixism">unixism</a>:</li> + +<li><a href="#unswizzle">unswizzle</a>:</li> + +<li><a href="#unwindthestack">unwind the stack</a>:</li> + +<li><a href="#unwind-protect">unwind-protect</a>:</li> + +<li><a href="#up">up</a>:</li> + +<li><a href="#upload">upload</a>:</li> + +<li><a href="#upthread">upthread</a>:</li> + +<li><a href="#urchin">urchin</a>:</li> + +<li><a href="#URL">URL</a>:</li> + +<li><a href="#Usenet">Usenet</a>:</li> + +<li><a href="#UsenetDeathPenalty">Usenet Death Penalty</a>:</li> + +<li><a href="#user">user</a>:</li> + +<li><a href="#user-friendly">user-friendly</a>:</li> + +<li><a href="#user-obsequious">user-obsequious</a>:</li> + +<li><a href="#userland">userland</a>:</li> + +<li><a href="#USGUnix">USG Unix</a>:</li> + +<li><a href="#UTSL">UTSL</a>:</li> + +<li><a href="#UUCPNET">UUCPNET</a>:</li> +</ul> + +<hr> +Node:<a name="u-">u-</a>, Next:<a rel="next" href="#UBD">UBD</a>, +Previous:<a rel="previous" href="#twonkie">twonkie</a>, Up:<a +rel="up" href="#chap21">= U =</a> <br> + + +<p><b>u-</b> pref.</p> + +<p>Written shorthand for <b><a href="#micro-">micro-</a></b>; +techspeak when applied to metric units, jargon when used +otherwise. Derived from the Greek letter "mu", the first letter +of "micro" (and which letter looks a lot like the English letter +"u").</p> + +<hr> +Node:<a name="UBD">UBD</a>, Next:<a rel="next" href="#UBE">UBE</a>, Previous:<a rel="previous" href="#u-">u-</a>, +Up:<a rel="up" href="#chap21">= U =</a> <br> + + +<p><b>UBD</b> /U-B-D/ n.</p> + +<p>[abbreviation for `User Brain Damage'] An abbreviation used to +close out trouble reports obviously due to utter cluelessness on +the user's part. Compare <b><a href="#piloterror">pilot +error</a></b>; oppose <b><a href="#PBD">PBD</a></b>; see also +<b><a href="#brain-damaged">brain-damaged</a></b>.</p> + +<hr> +Node:<a name="UBE">UBE</a>, Next:<a rel="next" href="#UCE">UCE</a>, Previous:<a rel="previous" href="#UBD">UBD</a>, +Up:<a rel="up" href="#chap21">= U =</a> <br> + + +<p><b>UBE</b> // n.</p> + +<p>[abbrev., Unsoliclited Bulk Email] A widespread, more formal +term for email <b><a href="#spam">spam</a></b>. Compare <b><a +href="#UCE">UCE</a></b>. The UBE term recognizes that spam is +uttered by nonprofit and advocacy groups whose motives are not +commercial.</p> + +<hr> +Node:<a name="UCE">UCE</a>, Next:<a rel="next" href="#UDP">UDP</a>, Previous:<a rel="previous" href="#UBE">UBE</a>, +Up:<a rel="up" href="#chap21">= U =</a> <br> + + +<p><b>UCE</b> n.</p> + +<p>[abbrev., Unsolicited Commercial Email] A widespread, more +formal term for email <b><a href="#spam">spam</a></b>. Compare +<b><a href="#UBE">UBE</a></b>, which may be superseding it.</p> + +<hr> +Node:<a name="UDP">UDP</a>, Next:<a rel="next" href="#UNX">UNX</a>, Previous:<a rel="previous" href="#UCE">UCE</a>, +Up:<a rel="up" href="#chap21">= U =</a> <br> + + +<p><b>UDP</b> /U-D-P/ v.,n.</p> + +<p>[Usenet] Abbreviation for <b><a href="#UsenetDeathPenalty">Usenet Death Penalty</a></b>. Common +(probably now more so than the full form), and frequently verbed. +Compare <b><a href="#IDP">IDP</a></b>.</p> + +<hr> +Node:<a name="UNX">UNX</a>, Next:<a rel="next" href="#undefinedexternalreference">undefined external +reference</a>, Previous:<a rel="previous" href="#UDP">UDP</a>, +Up:<a rel="up" href="#chap21">= U =</a> <br> + + +<p><b>UNX</b> n.</p> + +<p>Used to refer to the Unix operating system (a trademark of +AT&T, then of Novell, then of SCO, and then of Caldera) in +writing, but avoiding the need for the ugly <b><a href="#TM">(TM)</a></b> typography. Also used to refer to any or all +varieties of Unixoid operating systems. Ironically, lawyers now +say that the requirement for the trademark postfix has no legal +force, but the asterisk usage is entrenched anyhow. It has been +suggested that there may be a psychological connection to +practice in certain religions (especially Judaism) in which the +name of the deity is never written out in full, e.g., `YHWH' or +`G-d' is used. See also <b><a href="#glob">glob</a></b> and <b><a +href="#splatout">splat out</a></b>.</p> + +<hr> +Node:<a name="undefinedexternalreference">undefined +external reference</a>, Next:<a rel="next" href="#underthehood">under the hood</a>, Previous:<a rel="previous" href="#UNX">UNX</a>, Up:<a rel="up" href="#chap21">= U =</a> <br> + + +<p><b>undefined external reference</b> excl.</p> + +<p>[Unix] A message from Unix's linker. Used in speech to flag +loose ends or dangling references in an argument or +discussion.</p> + +<hr> +Node:<a name="underthehood">under the hood</a>, Next:<a +rel="next" href="#undocumentedfeature">undocumented +feature</a>, Previous:<a rel="previous" href="#undefinedexternalreference">undefined external +reference</a>, Up:<a rel="up" href="#chap21">= U =</a> +<br> + + +<p><b>under the hood</b> adj.</p> + +<p>[hot-rodder talk] 1. Used to introduce the underlying +implementation of a product (hardware, software, or idea). +Implies that the implementation is not intuitively obvious from +the appearance, but the speaker is about to enable the listener +to <b><a href="#grok">grok</a></b> it. "Let's now look under the +hood to see how <small>...</small>." 2. Can also imply that the +implementation is much simpler than the appearance would +indicate: "Under the hood, we are just fork/execing the shell." +3. Inside a chassis, as in "Under the hood, this baby has a 40MHz +68030!"</p> + +<hr> +Node:<a name="undocumentedfeature">undocumented feature</a>, +Next:<a rel="next" href="#uninteresting">uninteresting</a>, +Previous:<a rel="previous" href="#underthehood">under the +hood</a>, Up:<a rel="up" href="#chap21">= U =</a> <br> + + +<p><b>undocumented feature</b> n.</p> + +<p>See <b><a href="#feature">feature</a></b>.</p> + +<hr> +Node:<a name="uninteresting">uninteresting</a>, Next:<a rel="next" href="#Unix">Unix</a>, Previous:<a rel="previous" href="#undocumentedfeature">undocumented feature</a>, Up:<a rel="up" href="#chap21">= U =</a> <br> + + +<p><b>uninteresting</b> adj.</p> + +<p>1. Said of a problem that, although <b><a href="#nontrivial">nontrivial</a></b>, can be solved simply by +throwing sufficient resources at it. 2. Also said of problems for +which a solution would neither advance the state of the art nor +be fun to design and code.</p> + +<p>Hackers regard uninteresting problems as intolerable wastes of +time, to be solved (if at all) by lesser mortals. <i>Real</i> +hackers (see <b><a href="#toolsmith">toolsmith</a></b>) +generalize uninteresting problems enough to make them interesting +and solve them -- thus solving the original problem as a special +case (and, it must be admitted, occasionally turning a molehill +into a mountain, or a mountain into a tectonic plate). See <b><a +href="#WOMBAT">WOMBAT</a></b>, <b><a href="#SMOP">SMOP</a></b>; +compare <b><a href="#toyproblem">toy problem</a></b>, oppose +<b><a href="#interesting">interesting</a></b>.</p> + +<hr> +Node:<a name="Unix">Unix</a>, Next:<a rel="next" href="#Unixbraindamage">Unix brain damage</a>, Previous:<a rel="previous" href="#uninteresting">uninteresting</a>, Up:<a rel="up" href="#chap21">= U =</a> <br> + + +<p><b>Unix</b> /yoo'niks/ n.</p> + +<p>[In the authors' words, "A weak pun on Multics"; very early on +it was `UNICS'] (also `UNIX') An interactive time-sharing system +invented in 1969 by Ken Thompson after Bell Labs left the Multics +project, originally so he could play games on his scavenged +PDP-7. Dennis Ritchie, the inventor of C, is considered a +co-author of the system. The turning point in Unix's history came +when it was reimplemented almost entirely in C during 1972-1974, +making it the first source-portable OS. Unix subsequently +underwent mutations and expansions at the hands of many different +people, resulting in a uniquely flexible and developer-friendly +environment. By 1991, Unix had become the most widely used +multiuser general-purpose operating system in the world - and +since 1996 the variiant called <b><a href="#Linux">Linux</a></b> +has been at the cutting edge of the <b><a href="#opensource">open source</a></b> movement. Many people +consider the success of Unix the most important victory yet of +hackerdom over industry opposition (but see <b><a href="#Unixweenie">Unix weenie</a></b> and <b><a href="#Unixconspiracy">Unix conspiracy</a></b> for an opposing +point of view). See <b><a href="#Version7">Version 7</a></b>, +<b><a href="#BSD">BSD</a></b>, <b><a href="#USGUnix">USG +Unix</a></b>, <b><a href="#Linux">Linux</a></b>.</p> + +<p>Some people are confused over whether this word is +appropriately `UNIX' or `Unix'; both forms are common, and used +interchangeably. Dennis Ritchie says that the `UNIX' spelling +originally happened in CACM's 1974 paper "The UNIX Time-Sharing +System" because "we had a new typesetter and <b><a href="#troff">troff</a></b> had just been invented and we were +intoxicated by being able to produce small caps." Later, dmr +tried to get the spelling changed to `Unix' in a couple of Bell +Labs papers, on the grounds that the word is not acronymic. He +failed, and eventually (his words) "wimped out" on the issue. So, +while the trademark today is `UNIX', both capitalizations are +grounded in ancient usage; the Jargon File uses `Unix' in +deference to dmr's wishes.</p> + +<hr> +Node:<a name="Unixbraindamage">Unix brain damage</a>, +Next:<a rel="next" href="#Unixconspiracy">Unix conspiracy</a>, +Previous:<a rel="previous" href="#Unix">Unix</a>, Up:<a rel="up" +href="#chap21">= U =</a> <br> + + +<p><b>Unix brain damage</b> n.</p> + +<p>Something that has to be done to break a network program +(typically a mailer) on a non-Unix system so that it will +interoperate with Unix systems. The hack may qualify as `Unix +brain damage' if the program conforms to published standards and +the Unix program in question does not. Unix brain damage happens +because it is much easier for other (minority) systems to change +their ways to match non-conforming behavior than it is to change +all the hundreds of thousands of Unix systems out there.</p> + +<p>An example of Unix brain damage is a <b><a href="#kluge">kluge</a></b> in a mail server to recognize bare line +feed (the Unix newline) as an equivalent form to the Internet +standard newline, which is a carriage return followed by a line +feed. Such things can make even a hardened <b><a href="#jock">jock</a></b> weep.</p> + +<hr> +Node:<a name="Unixconspiracy">Unix conspiracy</a>, Next:<a +rel="next" href="#Unixweenie">Unix weenie</a>, Previous:<a +rel="previous" href="#Unixbraindamage">Unix brain +damage</a>, Up:<a rel="up" href="#chap21">= U =</a> <br> + + +<p><b>Unix conspiracy</b> n.</p> + +<p>[ITS] According to a conspiracy theory long popular among +<b><a href="#ITS">ITS</a></b> and <b><a href="#TOPS-20">TOPS-20</a></b> fans, Unix's growth is the result of a +plot, hatched during the 1970s at Bell Labs, whose intent was to +hobble AT&T's competitors by making them dependent upon a +system whose future evolution was to be under AT&T's control. +This would be accomplished by disseminating an operating system +that is apparently inexpensive and easily portable, but also +relatively unreliable and insecure (so as to require continuing +upgrades from AT&T). This theory was lent a substantial +impetus in 1984 by the paper referenced in the <b><a href="#backdoor">back door</a></b> entry.</p> + +<p>In this view, Unix was designed to be one of the first +computer viruses (see <b><a href="#virus">virus</a></b>) -- but a +virus spread to computers indirectly by people and market forces, +rather than directly through disks and networks. Adherents of +this `Unix virus' theory like to cite the fact that the +well-known quotation "Unix is snake oil" was uttered by <b><a +href="#DEC">DEC</a></b> president Kenneth Olsen shortly before +DEC began actively promoting its own family of Unix workstations. +(Olsen now claims to have been misquoted.)</p> + +<p>[If there was ever such a conspiracy, it got thoroughly out of +the plotters' control after 1990. AT&T sold its UNIX +operation to Novell around the same time <b><a href="#Linux">Linux</a></b> and other free-UNIX distributions were +beginning to make noise. --ESR]</p> + +<hr> +Node:<a name="Unixweenie">Unix weenie</a>, Next:<a rel="next" +href="#unixism">unixism</a>, Previous:<a rel="previous" href="#Unixconspiracy">Unix conspiracy</a>, Up:<a rel="up" href="#chap21">= U =</a> <br> + + +<p><b>Unix weenie</b> n.</p> + +<p>[ITS] 1. A derogatory play on `Unix wizard', common among +hackers who use Unix by necessity but would prefer alternatives. +The implication is that although the person in question may +consider mastery of Unix arcana to be a wizardly skill, the only +real skill involved is the ability to tolerate (and the bad taste +to wallow in) the incoherence and needless complexity that is +alleged to infest many Unix programs. "This shell script tries to +parse its arguments in 69 bletcherous ways. It must have been +written by a real Unix weenie." 2. A derogatory term for anyone +who engages in uncritical praise of Unix. Often appearing in the +context "stupid Unix weenie". See <b><a href="#Weenix">Weenix</a></b>, <b><a href="#Unixconspiracy">Unix +conspiracy</a></b>. See also <b><a href="#weenie">weenie</a></b>.</p> + +<hr> +Node:<a name="unixism">unixism</a>, Next:<a rel="next" href="#unswizzle">unswizzle</a>, Previous:<a rel="previous" href="#Unixweenie">Unix weenie</a>, Up:<a rel="up" href="#chap21">= U =</a> <br> + + +<p><b>unixism</b> n.</p> + +<p>A piece of code or a coding technique that depends on the +protected multi-tasking environment with relatively low +process-spawn overhead that exists on virtual-memory Unix +systems. Common <b><a href="#unixism">unixism</a></b>s include: +gratuitous use of <code>fork(2)</code>; the assumption that +certain undocumented but well-known features of Unix libraries +such as <code>stdio(3)</code> are supported elsewhere; reliance +on <b><a href="#obscure">obscure</a></b> side-effects of system +calls (use of <code>sleep(2)</code> with a 0 argument to clue the +scheduler that you're willing to give up your time-slice, for +example); the assumption that freshly allocated memory is zeroed; +and the assumption that fragmentation problems won't arise from +never <code>free()</code>ing memory. Compare <b><a href="#vaxocentrism">vaxocentrism</a></b>; see also <b><a href="#NewJersey">New Jersey</a></b>.</p> + +<hr> +Node:<a name="unswizzle">unswizzle</a>, Next:<a rel="next" href="#unwindthestack">unwind the stack</a>, Previous:<a rel="previous" href="#unixism">unixism</a>, Up:<a rel="up" href="#chap21">= U =</a> <br> + + +<p><b>unswizzle</b> v.</p> + +<p>See <b><a href="#swizzle">swizzle</a></b>.</p> + +<hr> +Node:<a name="unwindthestack">unwind the stack</a>, Next:<a +rel="next" href="#unwind-protect">unwind-protect</a>, Previous:<a +rel="previous" href="#unswizzle">unswizzle</a>, Up:<a rel="up" +href="#chap21">= U =</a> <br> + + +<p><b>unwind the stack</b> vi.</p> + +<p>1. [techspeak] During the execution of a procedural language, +one is said to `unwind the stack' from a called procedure up to a +caller when one discards the stack frame and any number of frames +above it, popping back up to the level of the given caller. In C +this is done with <code>longjmp</code>/<code>setjmp</code>, in +LISP or C++ with <code>throw/catch</code>. See also <b><a href="#smashthestack">smash the stack</a></b>. 2. People can +unwind the stack as well, by quickly dealing with a bunch of +problems: "Oh heck, let's do lunch. Just a second while I unwind +my stack."</p> + +<hr> +Node:<a name="unwind-protect">unwind-protect</a>, Next:<a rel="next" href="#up">up</a>, Previous:<a rel="previous" href="#unwindthestack">unwind the stack</a>, Up:<a rel="up" +href="#chap21">= U =</a> <br> + + +<p><b>unwind-protect</b> n.</p> + +<p>[MIT: from the name of a LISP operator] A task you must +remember to perform before you leave a place or finish a project. +"I have an unwind-protect to call my advisor."</p> + +<hr> +Node:<a name="up">up</a>, Next:<a rel="next" href="#upload">upload</a>, Previous:<a rel="previous" href="#unwind-protect">unwind-protect</a>, Up:<a rel="up" href="#chap21">= U =</a> <br> + + +<p><b>up</b> adj.</p> + +<p>1. Working, in order. "The down escalator is up." Oppose <b><a +href="#down">down</a></b>. 2. `bring up': vt. To create a working +version and start it. "They brought up a down system." 3. `come +up' vi. To become ready for production use.</p> + +<hr> +Node:<a name="upload">upload</a>, Next:<a rel="next" href="#upthread">upthread</a>, Previous:<a rel="previous" href="#up">up</a>, Up:<a rel="up" href="#chap21">= U =</a> <br> + + +<p><b>upload</b> /uhp'lohd/ v.</p> + +<p>1. [techspeak] To transfer programs or data over a digital +communications link from a system near you (espercially a smaller +or peripheral `client' system) to one further away from you +(especially a larger or central `host' system). A transfer in the +other direction is, of course, called a <b><a href="#download">download</a></b> 2. [speculatively] To move the +essential patterns and algorithms that make up one's mind from +one's brain into a computer. Those who are convinced that such +patterns and algorithms capture the complete essence of the self +view this prospect with pleasant anticipation.</p> + +<hr> +Node:<a name="upthread">upthread</a>, Next:<a rel="next" href="#urchin">urchin</a>, Previous:<a rel="previous" href="#upload">upload</a>, Up:<a rel="up" href="#chap21">= U +=</a> <br> + + +<p><b>upthread</b> adv.</p> + +<p>Earlier in the discussion (see <b><a href="#thread">thread</a></b>), i.e., `above'. "As Joe pointed out +upthread, <small>...</small>" See also <b><a href="#followup">followup</a></b>.</p> + +<hr> +Node:<a name="urchin">urchin</a>, Next:<a rel="next" href="#URL">URL</a>, Previous:<a rel="previous" href="#upthread">upthread</a>, Up:<a rel="up" href="#chap21">= +U =</a> <br> + + +<p><b>urchin</b> n.</p> + +<p>See <b><a href="#munchkin">munchkin</a></b>.</p> + +<hr> +Node:<a name="URL">URL</a>, Next:<a rel="next" href="#Usenet">Usenet</a>, Previous:<a rel="previous" href="#urchin">urchin</a>, Up:<a rel="up" href="#chap21">= U +=</a> <br> + + +<p><b>URL</b> /U-R-L/ or /erl/ n.</p> + +<p>Uniform Resource Locator, an address widget that identifies a +document or resource on the World Wide Web. This entry is here +primarily to record the fact that the term is commonly pronounced +both /erl/, and /U-R-L/ (the latter predominates in more formal +contexts).</p> + +<hr> +Node:<a name="Usenet">Usenet</a>, Next:<a rel="next" href="#UsenetDeathPenalty">Usenet Death Penalty</a>, Previous:<a +rel="previous" href="#URL">URL</a>, Up:<a rel="up" href="#chap21">= U =</a> <br> + + +<p><b>Usenet</b> /yoos'net/ or /yooz'net/ n.</p> + +<p>[from `Users' Network'; the original spelling was USENET, but +the mixed-case form is now widely preferred] A distributed <b><a +href="#bboard">bboard</a></b> (bulletin board) system supported +mainly by Unix machines. Originally implemented in 1979-1980 by +Steve Bellovin, Jim Ellis, Tom Truscott, and Steve Daniel at Duke +University, it has swiftly grown to become international in scope +and is now probably the largest decentralized information utility +in existence. As of early 1996, it hosts over 10,000 <b><a href="#newsgroup">newsgroup</a></b>s and an average of over 500 +megabytes (the equivalent of several thousand paper pages) of new +technical articles, news, discussion, chatter, and <b><a href="#flamage">flamage</a></b> every day (and that leaves out the +graphics...).</p> + +<p>By the year the Internet hit the mainstream (1994) the +original UUCP transport for Usenet was fading out of use (see +<b><a href="#UUCPNET">UUCPNET</a></b>) - almost all Usenet +connections were over Internet links. A lot of newbies and +journalists began to refer to "Internet newsgroups" as though +Usenet was and always had been just another Internet service. +This ignorance greatly annoys experienced Usenetters.</p> + +<hr> +Node:<a name="UsenetDeathPenalty">Usenet Death Penalty</a>, +Next:<a rel="next" href="#user">user</a>, Previous:<a rel="previous" href="#Usenet">Usenet</a>, Up:<a rel="up" href="#chap21">= U =</a> <br> + + +<p><b>Usenet Death Penalty</b></p> + +<p>[Usenet] A sanction against sites that habitually spew Usenet +<b><a href="#spam">spam</a></b>. This can be either passive or +active. A passive UDP refers to the dropping of all postings by a +particular domain so as to inhibit propagation. An active UDP +refers to third-party cancellation of all postings by the UDPed +domain. A partial UDP is one which applies only to certain +newsgroups or hierarchies in Usenet. Compare <b><a href="#InternetDeathPenalty">Internet Death Penalty</a></b>, +with which this term is sometimes confused.</p> + +<hr> +Node:<a name="user">user</a>, Next:<a rel="next" href="#user-friendly">user-friendly</a>, Previous:<a rel="previous" +href="#UsenetDeathPenalty">Usenet Death Penalty</a>, Up:<a +rel="up" href="#chap21">= U =</a> <br> + + +<p><b>user</b> n.</p> + +<p>1. Someone doing `real work' with the computer, using it as a +means rather than an end. Someone who pays to use a computer. See +<b><a href="#realuser">real user</a></b>. 2. A programmer who +will believe anything you tell him. One who asks silly questions. +[GLS observes: This is slightly unfair. It is true that users ask +questions (of necessity). Sometimes they are thoughtful or deep. +Very often they are annoying or downright stupid, apparently +because the user failed to think for two seconds or look in the +documentation before bothering the maintainer.] See <b><a href="#luser">luser</a></b>. 3. Someone who uses a program from the +outside, however skillfully, without getting into the internals +of the program. One who reports bugs instead of just going ahead +and fixing them.</p> + +<p>The general theory behind this term is that there are two +classes of people who work with a program: there are implementors +(hackers) and <b><a href="#luser">luser</a></b>s. The users are +looked down on by hackers to some extent because they don't +understand the full ramifications of the system in all its glory. +(The few users who do are known as `real winners'.) The term is a +relative one: a skilled hacker may be a user with respect to some +program he himself does not hack. A LISP hacker might be one who +maintains LISP or one who uses LISP (but with the skill of a +hacker). A LISP user is one who uses LISP, whether skillfully or +not. Thus there is some overlap between the two terms; the subtle +distinctions must be resolved by context.</p> + +<hr> +Node:<a name="user-friendly">user-friendly</a>, Next:<a rel="next" href="#user-obsequious">user-obsequious</a>, Previous:<a +rel="previous" href="#user">user</a>, Up:<a rel="up" href="#chap21">= U =</a> <br> + + +<p><b>user-friendly</b> adj.</p> + +<p>Programmer-hostile. Generally used by hackers in a critical +tone, to describe systems that hold the user's hand so +obsessively that they make it painful for the more experienced +and knowledgeable to get any work done. See <b><a href="#menuitis">menuitis</a></b>, <b><a href="#droolproofpaper">drool-proof paper</a></b>, <b><a href="#Macintrash">Macintrash</a></b>, <b><a href="#user-obsequious">user-obsequious</a></b>.</p> + +<hr> +Node:<a name="user-obsequious">user-obsequious</a>, Next:<a rel="next" href="#userland">userland</a>, Previous:<a rel="previous" +href="#user-friendly">user-friendly</a>, Up:<a rel="up" href="#chap21">= U =</a> <br> + + +<p><b>user-obsequious</b> adj.</p> + +<p>Emphatic form of <b><a href="#user-friendly">user-friendly</a></b>. Connotes a system so +verbose, inflexible, and determinedly simple-minded that it is +nearly unusable. "Design a system any fool can use and only a +fool will want to use it." See <b><a href="#WIMPenvironment">WIMP environment</a></b>, <b><a href="#Macintrash">Macintrash</a></b>.</p> + +<hr> +Node:<a name="userland">userland</a>, Next:<a rel="next" href="#USGUnix">USG Unix</a>, Previous:<a rel="previous" href="#user-obsequious">user-obsequious</a>, Up:<a rel="up" href="#chap21">= U =</a> <br> + + +<p><b>userland</b> n.</p> + +<p>Anywhere outside the kernel. "That code belongs in userland." +This term has been in common use among <b><a href="#Linux">Linux</a></b> kernel hackers since at leat 1997, and +seems to have originated in that community.</p> + +<hr> +Node:<a name="USGUnix">USG Unix</a>, Next:<a rel="next" href="#UTSL">UTSL</a>, Previous:<a rel="previous" href="#userland">userland</a>, Up:<a rel="up" href="#chap21">= +U =</a> <br> + + +<p><b>USG Unix</b> /U-S-G yoo'niks/ n.,obs.</p> + +<p>Refers to AT&T Unix commercial versions after <b><a href="#Version7">Version 7</a></b>, especially System III and +System V releases 1, 2, and 3. So called because during most of +the lifespan of those versions AT&T's support crew was called +the `Unix Support Group', but it is applied to version that pre- +and post-dated the USG group but were of the same lineage. This +term is now historical. See <b><a href="#BSD">BSD</a></b>, <b><a +href="#Unix">Unix</a></b>.</p> + +<hr> +Node:<a name="UTSL">UTSL</a>, Next:<a rel="next" href="#UUCPNET">UUCPNET</a>, Previous:<a rel="previous" href="#USGUnix">USG Unix</a>, Up:<a rel="up" href="#chap21">= U =</a> <br> + + +<p><b>UTSL</b> // n.</p> + +<p>[Unix] On-line acronym for `Use the Source, Luke' (a pun on +Obi-Wan Kenobi's "Use the Force, Luke!" in "Star Wars") -- +analogous to <b><a href="#RTFS">RTFS</a></b> (sense 1), but more +polite. This is a common way of suggesting that someone would be +better off reading the source code that supports whatever feature +is causing confusion, rather than making yet another futile pass +through the manuals, or broadcasting questions on Usenet that +haven't attracted <b><a href="#wizard">wizard</a></b>s to answer +them.</p> + +<p>Once upon a time in <b><a href="#elderdays">elder +days</a></b>, everyone running Unix had source. After 1978, +AT&T's policy tightened up, so this objurgation was in theory +appropriately directed only at associates of some outfit with a +Unix source license. In practice, bootlegs of Unix source code +(made precisely for reference purposes) were so ubiquitous that +one could utter it at almost anyone on the network without +concern.</p> + +<p>Nowadays, free Unix clones have become widely enough +distributed that anyone can read source legally. The most widely +distributed is certainly Linux, with variants of the NET/2 and +4.4BSD distributions running second. Cheap commercial Unixes with +source such as BSD/OS are accelerating this trend.</p> + +<hr> +Node:<a name="UUCPNET">UUCPNET</a>, Next:<a rel="next" href="#V7">V7</a>, Previous:<a rel="previous" href="#UTSL">UTSL</a>, +Up:<a rel="up" href="#chap21">= U =</a> <br> + + +<p><b>UUCPNET</b> n. obs.</p> + +<p>The store-and-forward network consisting of all the world's +connected Unix machines (and others running some clone of the +UUCP (Unix-to-Unix CoPy) software). Any machine reachable only +via a <b><a href="#bangpath">bang path</a></b> is on UUCPNET. +This term has been rendered obsolescent by the spread of cheap +Internet connections in the 1990s; the few remaining UUCP links +are essentially slow channels to the Internet rather than an +autonomous network. See <b><a href="#networkaddress">network +address</a></b>.</p> + +<hr> +Node:<a name="chap22">= V =</a>, Next:<a rel="next" href="#chap23">= W =</a>, Previous:<a rel="previous" href="#chap21">= U =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= V =</h2> + +<ul> +<li><a href="#V7">V7</a>:</li> + +<li><a href="#vadding">vadding</a>:</li> + +<li><a href="#vanilla">vanilla</a>:</li> + +<li><a href="#vanitydomain">vanity domain</a>:</li> + +<li><a href="#vannevar">vannevar</a>:</li> + +<li><a href="#vaporware">vaporware</a>:</li> + +<li><a href="#var">var</a>:</li> + +<li><a href="#vaston">vaston</a>:</li> + +<li><a href="#VAX">VAX</a>:</li> + +<li><a href="#VAXectomy">VAXectomy</a>:</li> + +<li><a href="#VAXen">VAXen</a>:</li> + +<li><a href="#vaxherd">vaxherd</a>:</li> + +<li><a href="#vaxism">vaxism</a>:</li> + +<li><a href="#vaxocentrism">vaxocentrism</a>:</li> + +<li><a href="#vdiff">vdiff</a>:</li> + +<li><a href="#veeblefester">veeblefester</a>:</li> + +<li><a href="#velveeta">velveeta</a>:</li> + +<li><a href="#ventilatorcard">ventilator card</a>:</li> + +<li><a href="#Venusflytrap">Venus flytrap</a>:</li> + +<li><a href="#verbage">verbage</a>:</li> + +<li><a href="#verbiage">verbiage</a>:</li> + +<li><a href="#Version7">Version 7</a>:</li> + +<li><a href="#vgrep">vgrep</a>:</li> + +<li><a href="#vi">vi</a>:</li> + +<li><a href="#videotoaster">video toaster</a>:</li> + +<li><a href="#videotex">videotex</a>:</li> + +<li><a href="#virgin">virgin</a>:</li> + +<li><a href="#virtual">virtual</a>:</li> + +<li><a href="#virtualbeer">virtual beer</a>:</li> + +<li><a href="#virtualFriday">virtual Friday</a>:</li> + +<li><a href="#virtualreality">virtual reality</a>:</li> + +<li><a href="#virtualshredder">virtual shredder</a>:</li> + +<li><a href="#virus">virus</a>:</li> + +<li><a href="#visionary">visionary</a>:</li> + +<li><a href="#VMS">VMS</a>:</li> + +<li><a href="#voice">voice</a>:</li> + +<li><a href="#voice-net">voice-net</a>:</li> + +<li><a href="#voodooprogramming">voodoo programming</a>:</li> + +<li><a href="#VR">VR</a>:</li> + +<li><a href="#Vulcannervepinch">Vulcan nerve pinch</a>:</li> + +<li><a href="#vulturecapitalist">vulture capitalist</a>:</li> +</ul> + +<hr> +Node:<a name="V7">V7</a>, Next:<a rel="next" href="#vadding">vadding</a>, Previous:<a rel="previous" href="#UUCPNET">UUCPNET</a>, Up:<a rel="up" href="#chap22">= V +=</a> <br> + + +<p><b>V7</b> /V'sev'en/ n.</p> + +<p>See <b><a href="#Version7">Version 7</a></b>.</p> + +<hr> +Node:<a name="vadding">vadding</a>, Next:<a rel="next" href="#vanilla">vanilla</a>, Previous:<a rel="previous" href="#V7">V7</a>, Up:<a rel="up" href="#chap22">= V =</a> <br> + + +<p><b>vadding</b> /vad'ing/ n.</p> + +<p>[from VAD, a permutation of ADV (i.e., <b><a href="#ADVENT">ADVENT</a></b>), used to avoid a particular <b><a href="#admin">admin</a></b>'s continual search-and-destroy sweeps for +the game] A leisure-time activity of certain hackers involving +the covert exploration of the `secret' parts of large buildings +-- basements, roofs, freight elevators, maintenance crawlways, +steam tunnels, and the like. A few go so far as to learn +locksmithing in order to synthesize vadding keys. The verb is `to +vad' (compare <b><a href="#phreaking">phreaking</a></b>; see also +<b><a href="#hack">hack</a></b>, sense 9). This term dates from +the late 1970s, before which such activity was simply called +`hacking'; the older usage is still prevalent at MIT.</p> + +<p>The most extreme and dangerous form of vadding is `elevator +rodeo', a.k.a. `elevator surfing', a sport played by wrasslin' +down a thousand-pound elevator car with a 3-foot piece of string, +and then exploiting this mastery in various stimulating ways +(such as elevator hopping, shaft exploration, rat-racing, and the +ever-popular drop experiments). Kids, don't try this at home! See +also <b><a href="#hobbit">hobbit</a></b> (sense 2).</p> + +<hr> +Node:<a name="vanilla">vanilla</a>, Next:<a rel="next" href="#vanitydomain">vanity domain</a>, Previous:<a rel="previous" +href="#vadding">vadding</a>, Up:<a rel="up" href="#chap22">= V =</a> <br> + + +<p><b>vanilla</b> adj.</p> + +<p>[from the default flavor of ice cream in the U.S.] Ordinary +<b><a href="#flavor">flavor</a></b>, standard. When used of food, +very often does not mean that the food is flavored with vanilla +extract! For example, `vanilla wonton soup' means ordinary wonton +soup, as opposed to hot-and-sour wonton soup. Applied to hardware +and software, as in "Vanilla Version 7 Unix can't run on a +vanilla 11/34." Also used to orthogonalize chip nomenclature; for +instance, a 74V00 means what TI calls a 7400, as distinct from a +74LS00, etc. This word differs from <b><a href="#canonical">canonical</a></b> in that the latter means +`default', whereas vanilla simply means `ordinary'. For example, +when hackers go on a <b><a href="#great-wall">great-wall</a></b>, +hot-and-sour soup is the <b><a href="#canonical">canonical</a></b> soup to get (because that is what +most of them usually order) even though it isn't the vanilla +(wonton) soup.</p> + +<hr> +Node:<a name="vanitydomain">vanity domain</a>, Next:<a rel="next" href="#vannevar">vannevar</a>, Previous:<a rel="previous" +href="#vanilla">vanilla</a>, Up:<a rel="up" href="#chap22">= V =</a> <br> + + +<p><b>vanity domain</b> n.</p> + +<p>[common; from `vanity plate' as in car license plate] An +Internet domain, particularly in the .com or .org top-level +domains, apparently created for no reason other than boosting the +creator's ego.</p> + +<hr> +Node:<a name="vannevar">vannevar</a>, Next:<a rel="next" href="#vaporware">vaporware</a>, Previous:<a rel="previous" href="#vanitydomain">vanity domain</a>, Up:<a rel="up" href="#chap22">= V =</a> <br> + + +<p><b>vannevar</b> /van'*-var/ n.</p> + +<p>A bogus technological prediction or a foredoomed engineering +concept, esp. one that fails by implicitly assuming that +technologies develop linearly, incrementally, and in isolation +from one another when in fact the learning curve tends to be +highly nonlinear, revolutions are common, and competition is the +rule. The prototype was Vannevar Bush's prediction of `electronic +brains' the size of the Empire State Building with a +Niagara-Falls-equivalent cooling system for their tubes and +relays, a prediction made at a time when the semiconductor effect +had already been demonstrated. Other famous vannevars have +included magnetic-bubble memory, LISP machines, <b><a href="#videotex">videotex</a></b>, and a paper from the late 1970s +that computed a purported ultimate limit on areal density for ICs +that was in fact less than the routine densities of 5 years +later.</p> + +<hr> +Node:<a name="vaporware">vaporware</a>, Next:<a rel="next" href="#var">var</a>, Previous:<a rel="previous" href="#vannevar">vannevar</a>, Up:<a rel="up" href="#chap22">= +V =</a> <br> + + +<p><b>vaporware</b> /vay'pr-weir/ n.</p> + +<p>Products announced far in advance of any release (which may or +may not actually take place). See also <b><a href="#brochureware">brochureware</a></b>.</p> + +<hr> +Node:<a name="var">var</a>, Next:<a rel="next" href="#vaston">vaston</a>, Previous:<a rel="previous" href="#vaporware">vaporware</a>, Up:<a rel="up" href="#chap22">= V =</a> <br> + + +<p><b>var</b> /veir/ or /var/ n.</p> + +<p>Short for `variable'. Compare <b><a href="#arg">arg</a></b>, +<b><a href="#param">param</a></b>.</p> + +<hr> +Node:<a name="vaston">vaston</a>, Next:<a rel="next" href="#VAX">VAX</a>, Previous:<a rel="previous" href="#var">var</a>, +Up:<a rel="up" href="#chap22">= V =</a> <br> + + +<p><b>vaston</b> n.</p> + +<p>[Durham, UK] The unit of `load average'. A measure of how much +work a computer is doing. A meter displaying this as a function +of time is known as a `vastometer'. First used during a computing +practical in December 1996.</p> + +<hr> +Node:<a name="VAX">VAX</a>, Next:<a rel="next" href="#VAXectomy">VAXectomy</a>, Previous:<a rel="previous" href="#vaston">vaston</a>, Up:<a rel="up" href="#chap22">= V +=</a> <br> + + +<p><b>VAX</b> /vaks/ n.</p> + +<p>1. [from Virtual Address eXtension] The most successful +minicomputer design in industry history, possibly excepting its +immediate ancestor, the PDP-11. Between its release in 1978 and +its eclipse by <b><a href="#killermicro">killer micro</a></b>s +after about 1986, the VAX was probably the hacker's favorite +machine of them all, esp. after the 1982 release of 4.2 BSD Unix +(see <b><a href="#BSD">BSD</a></b>). Esp. noted for its large, +assembler-programmer-friendly instruction set -- an asset that +became a liability after the RISC revolution. 2. A major brand of +vacuum cleaner in Britain. Cited here because its sales pitch, +"Nothing sucks like a VAX!" became a sort of battle-cry of RISC +partisans. It is even sometimes claimed that DEC actually entered +a cross-licensing deal with the vacuum-Vax people that allowed +them to market VAX computers in the U.K. in return for not +challenging the vacuum cleaner trademark in the U.S.</p> + +<p>A rival brand actually pioneered the slogan: its original form +was "Nothing sucks like Electrolux". It has apparently become a +classic example (used in advertising textbooks) of the perils of +not knowing the local idiom. But in 1996, the press manager of +Electrolux AB, while confirming that the company used this slogan +in the late 1960s, also tells us that their marketing people were +fully aware of the possible double entendre and intended it to +gain attention.</p> + +<p>And gain attention it did - the VAX-vacuum-cleaner people +thought the slogan a sufficiently good idea to copy it. Several +British hackers report that VAX's promotions used it in +1986-1987, and we have one report from a New Zealander that the +infamous slogan surfaced there in TV ads for the product in +1992.</p> + +<hr> +Node:<a name="VAXectomy">VAXectomy</a>, Next:<a rel="next" href="#VAXen">VAXen</a>, Previous:<a rel="previous" href="#VAX">VAX</a>, Up:<a rel="up" href="#chap22">= V =</a> +<br> + + +<p><b>VAXectomy</b> /vak-sek't*-mee/ n.</p> + +<p>[by analogy with `vasectomy'] A VAX removal. <b><a href="#DEC">DEC</a></b>'s Microvaxen, especially, are much slower than +newer RISC-based workstations such as the SPARC. Thus, if one +knows one has a replacement coming, VAX removal can be cause for +celebration.</p> + +<hr> +Node:<a name="VAXen">VAXen</a>, Next:<a rel="next" href="#vaxherd">vaxherd</a>, Previous:<a rel="previous" href="#VAXectomy">VAXectomy</a>, Up:<a rel="up" href="#chap22">= V =</a> <br> + + +<p><b>VAXen</b> /vak'sn/ n.</p> + +<p>[from `oxen', perhaps influenced by `vixen'] (alt. `vaxen') +The plural canonically used among hackers for the <b><a href="#DEC">DEC</a></b> VAX computers. "Our installation has four +PDP-10s and twenty vaxen." See <b><a href="#boxen">boxen</a></b>.</p> + +<hr> +Node:<a name="vaxherd">vaxherd</a>, Next:<a rel="next" href="#vaxism">vaxism</a>, Previous:<a rel="previous" href="#VAXen">VAXen</a>, Up:<a rel="up" href="#chap22">= V +=</a> <br> + + +<p><b>vaxherd</b> /vaks'herd/ n. obs.</p> + +<p>[from `oxherd'] A VAX operator. The image is reinforced +because VAXen actually did tend to come in herds, technically +known as `clusters'.</p> + +<hr> +Node:<a name="vaxism">vaxism</a>, Next:<a rel="next" href="#vaxocentrism">vaxocentrism</a>, Previous:<a rel="previous" +href="#vaxherd">vaxherd</a>, Up:<a rel="up" href="#chap22">= V =</a> <br> + + +<p><b>vaxism</b> /vak'sizm/ n.</p> + +<p>A piece of code that exhibits <b><a href="#vaxocentrism">vaxocentrism</a></b> in critical areas. Compare +<b><a href="#PC-ism">PC-ism</a></b>, <b><a href="#unixism">unixism</a></b>.</p> + +<hr> +Node:<a name="vaxocentrism">vaxocentrism</a>, Next:<a rel="next" +href="#vdiff">vdiff</a>, Previous:<a rel="previous" href="#vaxism">vaxism</a>, Up:<a rel="up" href="#chap22">= V +=</a> <br> + + +<p><b>vaxocentrism</b> /vak`soh-sen'trizm/ n.</p> + +<p>[analogy with `ethnocentrism'] A notional disease said to +afflict C programmers who persist in coding according to certain +assumptions that are valid (esp. under Unix) on <b><a href="#VAXen">VAXen</a></b> but false elsewhere. Among these are:</p> + +<ol type="1" start="1"> +<li>The assumption that dereferencing a null pointer is safe +because it is all bits 0, and location 0 is readable and 0. +Problem: this may instead cause an illegal-address trap on +non-VAXen, and even on VAXen under OSes other than BSD Unix. +Usually this is an implicit assumption of sloppy code (forgetting +to check the pointer before using it), rather than deliberate +exploitation of a misfeature.</li> + +<li>The assumption that characters are signed.</li> + +<li>The assumption that a pointer to any one type can freely be +cast into a pointer to any other type. A stronger form of this is +the assumption that all pointers are the same size and format, +which means you don't have to worry about getting the casts or +types correct in calls. Problem: this fails on word-oriented +machines or others with multiple pointer formats.</li> + +<li>The assumption that the parameters of a routine are stored in +memory, on a stack, contiguously, and in strictly ascending or +descending order. Problem: this fails on many RISC +architectures.</li> + +<li>The assumption that pointer and integer types are the same +size, and that pointers can be stuffed into integer variables +(and vice-versa) and drawn back out without being truncated or +mangled. Problem: this fails on segmented architectures or +word-oriented machines with funny pointer formats.</li> + +<li>The assumption that a data type of any size may begin at any +byte address in memory (for example, that you can freely +construct and dereference a pointer to a word- or greater-sized +object at an odd char address). Problem: this fails on many (esp. +RISC) architectures better optimized for <b><a href="#HLL">HLL</a></b> execution speed, and can cause an illegal +address fault or bus error.</li> + +<li>The (related) assumption that there is no padding at the end +of types and that in an array you can thus step right from the +last byte of a previous component to the first byte of the next +one. This is not only machine- but compiler-dependent.</li> + +<li>The assumption that memory address space is globally flat and +that the array reference <code>foo[-1]</code> is necessarily +valid. Problem: this fails at 0, or other places on +segment-addressed machines like Intel chips (yes, segmentation is +universally considered a <b><a href="#brain-damaged">brain-damaged</a></b> way to design machines +(see <b><a href="#moby">moby</a></b>), but that is a separate +issue).</li> + +<li>The assumption that objects can be arbitrarily large with no +special considerations. Problem: this fails on segmented +architectures and under non-virtual-addressing environments.</li> + +<li>The assumption that the stack can be as large as memory. +Problem: this fails on segmented architectures or almost anything +else without virtual addressing and a paged stack.</li> + +<li>The assumption that bits and addressable units within an +object are ordered in the same way and that this order is a +constant of nature. Problem: this fails on <b><a href="#big-endian">big-endian</a></b> machines.</li> + +<li>The assumption that it is meaningful to compare pointers to +different objects not located within the same array, or to +objects of different types. Problem: the former fails on +segmented architectures, the latter on word-oriented machines or +others with multiple pointer formats.</li> + +<li>The assumption that an <code>int</code> is 32 bits, or +(nearly equivalently) the assumption that <code>sizeof(int) == +sizeof(long)</code>. Problem: this fails on PDP-11s, 286-based +systems and even on 386 and 68000 systems under some compilers +(and on 64-bit systems like the Alpha, of course).</li> + +<li>The assumption that <code>argv[]</code> is writable. Problem: +this fails in many embedded-systems C environments and even under +a few flavors of Unix.</li> +</ol> + +<p>Note that a programmer can validly be accused of vaxocentrism +even if he or she has never seen a VAX. Some of these assumptions +(esp. 2-5) were valid on the PDP-11, the original C machine, and +became endemic years before the VAX. The terms `vaxocentricity' +and `all-the-world's-a-VAX syndrome' have been used +synonymously.</p> + +<hr> +Node:<a name="vdiff">vdiff</a>, Next:<a rel="next" href="#veeblefester">veeblefester</a>, Previous:<a rel="previous" +href="#vaxocentrism">vaxocentrism</a>, Up:<a rel="up" href="#chap22">= V =</a> <br> + + +<p><b>vdiff</b> /vee'dif/ v.,n.</p> + +<p>Visual diff. The operation of finding differences between two +files by <b><a href="#eyeballsearch">eyeball search</a></b>. +The term `optical diff' has also been reported, and is sometimes +more specifically used for the act of superimposing two nearly +identical printouts on one another and holding them up to a light +to spot differences. Though this method is poor for detecting +omissions in the `rear' file, it can also be used with printouts +of graphics, a claim few if any diff programs can make. See <b><a +href="#diff">diff</a></b>.</p> + +<hr> +Node:<a name="veeblefester">veeblefester</a>, Next:<a rel="next" +href="#velveeta">velveeta</a>, Previous:<a rel="previous" href="#vdiff">vdiff</a>, Up:<a rel="up" href="#chap22">= V +=</a> <br> + + +<p><b>veeblefester</b> /vee'b*l-fes`tr/ n.</p> + +<p>[from the "Born Loser" comix via Commodore; prob. originally +from "Mad" Magazine's `Veeblefetzer' parodies beginning in #15, +1954] Any obnoxious person engaged in the (alleged) professions +of marketing or management. Antonym of <b><a href="#hacker">hacker</a></b>. Compare <b><a href="#suit">suit</a></b>, <b><a href="#marketroid">marketroid</a></b>.</p> + +<hr> +Node:<a name="velveeta">velveeta</a>, Next:<a rel="next" href="#ventilatorcard">ventilator card</a>, Previous:<a rel="previous" href="#veeblefester">veeblefester</a>, Up:<a rel="up" +href="#chap22">= V =</a> <br> + + +<p><b>velveeta</b> n.</p> + +<p>[Usenet: by analogy with <b><a href="#spam">spam</a></b>. The +trade name Velveeta is attached in the U.S. to a particularly +nasty processed-cheese spread.] Also knows as <b><a href="#ECP">ECP</a></b>; a message that is excessively cross-posted, +as opposed to <b><a href="#spam">spam</a></b> which is too +frequently posted. This term is widely recognized but not +commonly used; most people refer to both kinds of abuse as spam. +Compare <b><a href="#jello">jello</a></b>.</p> + +<hr> +Node:<a name="ventilatorcard">ventilator card</a>, Next:<a +rel="next" href="#Venusflytrap">Venus flytrap</a>, Previous:<a +rel="previous" href="#velveeta">velveeta</a>, Up:<a rel="up" +href="#chap22">= V =</a> <br> + + +<p><b>ventilator card</b> n.</p> + +<p>Syn. <b><a href="#lacecard">lace card</a></b>.</p> + +<hr> +Node:<a name="Venusflytrap">Venus flytrap</a>, Next:<a rel="next" href="#verbage">verbage</a>, Previous:<a rel="previous" +href="#ventilatorcard">ventilator card</a>, Up:<a rel="up" +href="#chap22">= V =</a> <br> + + +<p><b>Venus flytrap</b> n.</p> + +<p>[after the insect-eating plant] See <b><a href="#firewallmachine">firewall machine</a></b>.</p> + +<hr> +Node:<a name="verbage">verbage</a>, Next:<a rel="next" href="#verbiage">verbiage</a>, Previous:<a rel="previous" href="#Venusflytrap">Venus flytrap</a>, Up:<a rel="up" href="#chap22">= V =</a> <br> + + +<p><b>verbage</b> /ver'b*j/ n.</p> + +<p>A deliberate misspelling and mispronunciation of <b><a href="#verbiage">verbiage</a></b> that assimilates it to the word +`garbage'. Compare <b><a href="#content-free">content-free</a></b>. More pejorative than +`verbiage'.</p> + +<hr> +Node:<a name="verbiage">verbiage</a>, Next:<a rel="next" href="#Version7">Version 7</a>, Previous:<a rel="previous" href="#verbage">verbage</a>, Up:<a rel="up" href="#chap22">= V +=</a> <br> + + +<p><b>verbiage</b> n.</p> + +<p>When the context involves a software or hardware system, this +refers to <b><a href="#documentation">documentation</a></b>. This +term borrows the connotations of mainstream `verbiage' to suggest +that the documentation is of marginal utility and that the +motives behind its production have little to do with the +ostensible subject.</p> + +<hr> +Node:<a name="Version7">Version 7</a>, Next:<a rel="next" +href="#vgrep">vgrep</a>, Previous:<a rel="previous" href="#verbiage">verbiage</a>, Up:<a rel="up" href="#chap22">= +V =</a> <br> + + +<p><b>Version 7</b> alt. V7 /vee' se'vn/ n.</p> + +<p>The first widely distributed version of <b><a href="#Unix">Unix</a></b>, released unsupported by Bell Labs in 1978. +The term is used adjectivally to describe Unix features and +programs that date from that release, and are thus guaranteed to +be present and portable in all Unix versions (this was the +standard gauge of portability before the POSIX and IEEE 1003 +standards). Note that this usage does <i>not</i> derive from +the release being the "seventh version of <b><a href="#Unix">Unix</a></b>"; research <b><a href="#Unix">Unix</a></b> +at Bell Labs has traditionally been numbered according to the +edition of the associated documentation. Indeed, only the +widely-distributed Sixth and Seventh Editions are widely known as +V[67]; the OS that might today be known as `V10' is instead known +in full as "Tenth Edition Research Unix" or just "Tenth Edition" +for short. For this reason, "V7" is often read by cognoscenti as +"Seventh Edition". See <b><a href="#BSD">BSD</a></b>, <b><a href="#USGUnix">USG Unix</a></b>, <b><a href="#Unix">Unix</a></b>. +Some old-timers impatient with commercialization and kernel bloat +still maintain that V7 was the Last True Unix.</p> + +<hr> +Node:<a name="vgrep">vgrep</a>, Next:<a rel="next" href="#vi">vi</a>, Previous:<a rel="previous" href="#Version7">Version 7</a>, Up:<a rel="up" href="#chap22">= V =</a> <br> + + +<p><b>vgrep</b> /vee'grep/ v.,n.</p> + +<p>Visual grep. The operation of finding patterns in a file +optically rather than digitally (also called an `optical grep'). +See <b><a href="#grep">grep</a></b>; compare <b><a href="#vdiff">vdiff</a></b>.</p> + +<hr> +Node:<a name="vi">vi</a>, Next:<a rel="next" href="#videotoaster">video toaster</a>, Previous:<a rel="previous" +href="#vgrep">vgrep</a>, Up:<a rel="up" href="#chap22">= V +=</a> <br> + + +<p><b>vi</b> /V-I/, <i>not</i> /vi:/ and <i>never</i> /siks/ +n.</p> + +<p>[from `Visual Interface'] A screen editor crufted together by +Bill Joy for an early <b><a href="#BSD">BSD</a></b> release. +Became the <i>de facto</i> standard Unix editor and a nearly +undisputed hacker favorite outside of MIT until the rise of <b><a +href="#EMACS">EMACS</a></b> after about 1984. Tends to frustrate +new users no end, as it will neither take commands while +expecting input text nor vice versa, and the default setup on +older versions provides no indication of which mode the editor is +in (years ago, a correspondent reported that he has often heard +the editor's name pronounced /vi:l/; there is now a vi clone +named `vile'). Nevertheless vi (and variants such as vim and +elvis) is still widely used (about half the respondents in a 1991 +Usenet poll preferred it), and even EMACS fans often resort to it +as a mail editor and for small editing jobs (mainly because it +starts up faster than the bulkier versions of EMACS). See <b><a +href="#holywars">holy wars</a></b>.</p> + +<hr> +Node:<a name="videotoaster">video toaster</a>, Next:<a rel="next" href="#videotex">videotex</a>, Previous:<a rel="previous" +href="#vi">vi</a>, Up:<a rel="up" href="#chap22">= V =</a> +<br> + + +<p><b>video toaster</b> n.</p> + +<p>Historically, an Amiga fitted with a particular line of +special video effects hardware from NewTek - long a popular +platform at special-effects and video production houses. More +generally, any computer system designed specifically for video +production and manipulation. Compare <b><a href="#webtoaster">web toaster</a></b> and see <b><a href="#toaster">toaster</a></b>.</p> + +<hr> +Node:<a name="videotex">videotex</a>, Next:<a rel="next" href="#virgin">virgin</a>, Previous:<a rel="previous" href="#videotoaster">video toaster</a>, Up:<a rel="up" href="#chap22">= V =</a> <br> + + +<p><b>videotex</b> n. obs.</p> + +<p>An electronic service offering people the privilege of paying +to read the weather on their television screens instead of having +somebody read it to them for free while they brush their teeth. +The idea bombed everywhere it wasn't government-subsidized, +because by the time videotex was practical the installed base of +personal computers could hook up to timesharing services and do +the things for which videotex might have been worthwhile better +and cheaper. Videotex planners badly overestimated both the +appeal of getting information from a computer and the cost of +local intelligence at the user's end. Like the <b><a href="#gorillaarm">gorilla arm</a></b> effect, this has been a +cautionary tale to hackers ever since. See also <b><a href="#vannevar">vannevar</a></b>.</p> + +<hr> +Node:<a name="virgin">virgin</a>, Next:<a rel="next" href="#virtual">virtual</a>, Previous:<a rel="previous" href="#videotex">videotex</a>, Up:<a rel="up" href="#chap22">= +V =</a> <br> + + +<p><b>virgin</b> adj.</p> + +<p>Unused; pristine; in a known initial state. "Let's bring up a +virgin system and see if it crashes again." (Esp. useful after +contracting a <b><a href="#virus">virus</a></b> through <b><a +href="#SEX">SEX</a></b>.) Also, by extension, buffers and the +like within a program that have not yet been used.</p> + +<hr> +Node:<a name="virtual">virtual</a>, Next:<a rel="next" href="#virtualbeer">virtual beer</a>, Previous:<a rel="previous" +href="#virgin">virgin</a>, Up:<a rel="up" href="#chap22">= +V =</a> <br> + + +<p><b>virtual</b> adj.</p> + +<p>[via the technical term `virtual memory', prob. from the term +`virtual image' in optics] 1. Common alternative to <b><a href="#logical">logical</a></b>; often used to refer to the artificial +objects (like addressable virtual memory larger than physical +memory) simulated by a computer system as a convenient way to +manage access to shared resources. 2. Simulated; performing the +functions of something that isn't really there. An imaginative +child's doll may be a virtual playmate. Oppose <b><a href="#real">real</a></b>.</p> + +<hr> +Node:<a name="virtualbeer">virtual beer</a>, Next:<a rel="next" href="#virtualFriday">virtual Friday</a>, Previous:<a +rel="previous" href="#virtual">virtual</a>, Up:<a rel="up" href="#chap22">= V =</a> <br> + + +<p><b>virtual beer</b> n.</p> + +<p>Praise or thanks. Used universally in the Linux community. +Originally this term signified cash, after a famous incident in +which some some Britishers who wanted to buy Linus a beer and +sent him money to Finland to do so.</p> + +<hr> +Node:<a name="virtualFriday">virtual Friday</a>, Next:<a rel="next" href="#virtualreality">virtual reality</a>, Previous:<a +rel="previous" href="#virtualbeer">virtual beer</a>, Up:<a +rel="up" href="#chap22">= V =</a> <br> + + +<p><b>virtual Friday</b> n.</p> + +<p>(also `logical Friday') The last day before an extended +weekend, if that day is not a `real' Friday. For example, the +U.S. holiday Thanksgiving is always on a Thursday. The next day +is often also a holiday or taken as an extra day off, in which +case Wednesday of that week is a virtual Friday (and Thursday is +a virtual Saturday, as is Friday). There are also `virtual +Mondays' that are actually Tuesdays, after the three-day weekends +associated with many national holidays in the U.S.</p> + +<hr> +Node:<a name="virtualreality">virtual reality</a>, Next:<a +rel="next" href="#virtualshredder">virtual shredder</a>, +Previous:<a rel="previous" href="#virtualFriday">virtual +Friday</a>, Up:<a rel="up" href="#chap22">= V =</a> <br> + + +<p><b>virtual reality</b> n.</p> + +<p>1. Computer simulations that use 3-D graphics and devices such +as the Dataglove to allow the user to interact with the +simulation. See <b><a href="#cyberspace">cyberspace</a></b>. 2. A +form of network interaction incorporating aspects of role-playing +games, interactive theater, improvisational comedy, and `true +confessions' magazines. In a virtual reality forum (such as +Usenet's <i>alt.callahans</i> newsgroup or the <b><a href="#MUD">MUD</a></b> experiments on Internet), interaction between +the participants is written like a shared novel complete with +scenery, `foreground characters' that may be personae utterly +unlike the people who write them, and common `background +characters' manipulable by all parties. The one iron law is that +you may not write irreversible changes to a character without the +consent of the person who `owns' it. Otherwise anything goes. See +<b><a href="#bamf">bamf</a></b>, <b><a href="#cyberspace">cyberspace</a></b>, <b><a href="#teledildonics">teledildonics</a></b>.</p> + +<hr> +Node:<a name="virtualshredder">virtual shredder</a>, Next:<a +rel="next" href="#virus">virus</a>, Previous:<a rel="previous" +href="#virtualreality">virtual reality</a>, Up:<a rel="up" +href="#chap22">= V =</a> <br> + + +<p><b>virtual shredder</b> n.</p> + +<p>The jargonic equivalent of the <b><a href="#bitbucket">bit +bucket</a></b> at shops using IBM's VM/CMS operating system. +VM/CMS officially supports a whole bestiary of virtual card +readers, virtual printers, and other phantom devices; these are +used to supply some of the same capabilities Unix gets from pipes +and I/O redirection.</p> + +<hr> +Node:<a name="virus">virus</a>, Next:<a rel="next" href="#visionary">visionary</a>, Previous:<a rel="previous" href="#virtualshredder">virtual shredder</a>, Up:<a rel="up" href="#chap22">= V =</a> <br> + + +<p><b>virus</b> n.</p> + +<p>[from the obvious analogy with biological viruses, via SF] A +cracker program that searches out other programs and `infects' +them by embedding a copy of itself in them, so that they become +<b><a href="#Trojanhorse">Trojan horse</a></b>s. When these +programs are executed, the embedded virus is executed too, thus +propagating the `infection'. This normally happens invisibly to +the user. Unlike a <b><a href="#worm">worm</a></b>, a virus +cannot infect other computers without assistance. It is +propagated by vectors such as humans trading programs with their +friends (see <b><a href="#SEX">SEX</a></b>). The virus may do +nothing but propagate itself and then allow the program to run +normally. Usually, however, after propagating silently for a +while, it starts doing things like writing cute messages on the +terminal or playing strange tricks with the display (some viruses +include nice <b><a href="#displayhack">display hack</a></b>s). +Many nasty viruses, written by particularly perversely minded +<b><a href="#cracker">cracker</a></b>s, do irreversible damage, +like nuking all the user's files.</p> + +<p>In the 1990s, viruses became a serious problem, especially +among Windows users; the lack of security on these machines +enables viruses to spread easily, even infecting the operating +system (Unix machines, by contrast, are immune to such attacks). +The production of special anti-virus software has become an +industry, and a number of exaggerated media reports have caused +outbreaks of near hysteria among users; many <b><a href="#luser">luser</a></b>s tend to blame <i>everything</i> that +doesn't work as they had expected on virus attacks. Accordingly, +this sense of `virus' has passed not only into techspeak but into +also popular usage (where it is often incorrectly used to denote +a <b><a href="#worm">worm</a></b> or even a <b><a href="#Trojanhorse">Trojan horse</a></b>). See <b><a href="#phage">phage</a></b>; compare <b><a href="#backdoor">back +door</a></b>; see also <b><a href="#Unixconspiracy">Unix +conspiracy</a></b>.</p> + +<hr> +Node:<a name="visionary">visionary</a>, Next:<a rel="next" href="#VMS">VMS</a>, Previous:<a rel="previous" href="#virus">virus</a>, Up:<a rel="up" href="#chap22">= V +=</a> <br> + + +<p><b>visionary</b> n.</p> + +<p>1. One who hacks vision, in the sense of an Artificial +Intelligence researcher working on the problem of getting +computers to `see' things using TV cameras. (There isn't any +problem in sending information from a TV camera to a computer. +The problem is, how can the computer be programmed to make use of +the camera information? See <b><a href="#SMOP">SMOP</a></b>, +<b><a href="#AI-complete">AI-complete</a></b>.) 2. [IBM] One who +reads the outside literature. At IBM, apparently, such a penchant +is viewed with awe and wonder.</p> + +<hr> +Node:<a name="VMS">VMS</a>, Next:<a rel="next" href="#voice">voice</a>, Previous:<a rel="previous" href="#visionary">visionary</a>, Up:<a rel="up" href="#chap22">= V =</a> <br> + + +<p><b>VMS</b> /V-M-S/ n.</p> + +<p><b><a href="#DEC">DEC</a></b>'s proprietary operating system +for its VAX minicomputer; one of the seven or so environments +that loom largest in hacker folklore. Many Unix fans generously +concede that VMS would probably be the hacker's favorite +commercial OS if Unix didn't exist; though true, this makes VMS +fans furious. One major hacker gripe with VMS concerns its +slowness -- thus the following limerick:</p> + +<pre> + There once was a system called VMS + Of cycles by no means abstemious. + It's chock-full of hacks + And runs on a VAX + And makes my poor stomach all squeamious. + --- The Great Quux +</pre> + +<p>See also <b><a href="#VAX">VAX</a></b>, <b><a href="#TOPS-10">TOPS-10</a></b>, <b><a href="#TOPS-20">TOPS-20</a></b>, <b><a href="#Unix">Unix</a></b>, +<b><a href="#runic">runic</a></b>.</p> + +<hr> +Node:<a name="voice">voice</a>, Next:<a rel="next" href="#voice-net">voice-net</a>, Previous:<a rel="previous" href="#VMS">VMS</a>, Up:<a rel="up" href="#chap22">= V =</a> +<br> + + +<p><b>voice</b> vt.</p> + +<p>To phone someone, as opposed to emailing them or connecting in +<b><a href="#talkmode">talk mode</a></b>. "I'm busy now; I'll +voice you later."</p> + +<hr> +Node:<a name="voice-net">voice-net</a>, Next:<a rel="next" href="#voodooprogramming">voodoo programming</a>, Previous:<a rel="previous" href="#voice">voice</a>, Up:<a rel="up" href="#chap22">= V =</a> <br> + + +<p><b>voice-net</b> n.</p> + +<p>Hackish way of referring to the telephone system, analogizing +it to a digital network. Usenet <b><a href="#sigblock">sig +block</a></b>s not uncommonly include the sender's phone next to +a "Voice:" or "Voice-Net:" header; common variants of this are +"Voicenet" and "V-Net". Compare <b><a href="#paper-net">paper-net</a></b>, <b><a href="#snail-mail">snail-mail</a></b>.</p> + +<hr> +Node:<a name="voodooprogramming">voodoo programming</a>, +Next:<a rel="next" href="#VR">VR</a>, Previous:<a rel="previous" +href="#voice-net">voice-net</a>, Up:<a rel="up" href="#chap22">= V =</a> <br> + + +<p><b>voodoo programming</b> n.</p> + +<p>[from George Bush's "voodoo economics"] 1. The use by guess or +cookbook of an <b><a href="#obscure">obscure</a></b> or <b><a +href="#hairy">hairy</a></b> system, feature, or algorithm that +one does not truly understand. The implication is that the +technique may not work, and if it doesn't, one will never know +why. Almost synonymous with <b><a href="#blackmagic">black +magic</a></b>, except that black magic typically isn't documented +and <i>nobody</i> understands it. Compare <b><a href="#magic">magic</a></b>, <b><a href="#deepmagic">deep +magic</a></b>, <b><a href="#heavywizardry">heavy +wizardry</a></b>, <b><a href="#raindance">rain dance</a></b>, +<b><a href="#cargocultprogramming">cargo cult +programming</a></b>, <b><a href="#waveadeadchicken">wave +a dead chicken</a></b>. 2. Things programmers do that they know +shouldn't work but they try anyway, and which sometimes actually +work, such as recompiling everything.</p> + +<hr> +Node:<a name="VR">VR</a>, Next:<a rel="next" href="#Vulcannervepinch">Vulcan nerve pinch</a>, Previous:<a +rel="previous" href="#voodooprogramming">voodoo +programming</a>, Up:<a rel="up" href="#chap22">= V =</a> +<br> + + +<p><b>VR</b> // [MUD] n.</p> + +<p>On-line abbrev for <b><a href="#virtualreality">virtual +reality</a></b>, as opposed to <b><a href="#RL">RL</a></b>.</p> + +<hr> +Node:<a name="Vulcannervepinch">Vulcan nerve pinch</a>, +Next:<a rel="next" href="#vulturecapitalist">vulture +capitalist</a>, Previous:<a rel="previous" href="#VR">VR</a>, +Up:<a rel="up" href="#chap22">= V =</a> <br> + + +<p><b>Vulcan nerve pinch</b> n.</p> + +<p>[from the old "Star Trek" TV series via Commodore Amiga +hackers] The keyboard combination that forces a soft-boot or jump +to ROM monitor (on machines that support such a feature). On PC +clones this is Ctrl-Alt-Del; on Suns, L1-A; on Macintoshes, it is +<Cmd>-<Power switch> or +<CMD>-<CTRL>-<POWER>! Also called <b><a href="#three-fingersalute">three-finger salute</a></b>. Compare +<b><a href="#quadruplebucky">quadruple bucky</a></b>.</p> + +<hr> +Node:<a name="vulturecapitalist">vulture capitalist</a>, +Next:<a rel="next" href="#W2Kbug">W2K bug</a>, Previous:<a +rel="previous" href="#Vulcannervepinch">Vulcan nerve +pinch</a>, Up:<a rel="up" href="#chap22">= V =</a> <br> + + +<p><b>vulture capitalist</b> n.</p> + +<p>Pejorative hackerism for `venture capitalist', deriving from +the common practice of pushing contracts that deprive inventors +of control over their own innovations and most of the money they +ought to have made from them.</p> + +<hr> +Node:<a name="chap23">= W =</a>, Next:<a rel="next" href="#chap24">= X =</a>, Previous:<a rel="previous" href="#chap22">= V =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= W =</h2> + +<ul> +<li><a href="#W2Kbug">W2K bug</a>:</li> + +<li><a href="#wabbit">wabbit</a>:</li> + +<li><a href="#WAITS">WAITS</a>:</li> + +<li><a href="#waldo">waldo</a>:</li> + +<li><a href="#walk">walk</a>:</li> + +<li><a href="#walkofftheendof">walk off the end of</a>:</li> + +<li><a href="#walkingdrives">walking drives</a>:</li> + +<li><a href="#wall">wall</a>:</li> + +<li><a href="#wallfollower">wall follower</a>:</li> + +<li><a href="#walltime">wall time</a>:</li> + +<li><a href="#wallwart">wall wart</a>:</li> + +<li><a href="#wallpaper">wallpaper</a>:</li> + +<li><a href="#wango">wango</a>:</li> + +<li><a href="#wank">wank</a>:</li> + +<li><a href="#wannabee">wannabee</a>:</li> + +<li><a href="#wardialer">war dialer</a>:</li> + +<li><a href="#-ware">-ware</a>:</li> + +<li><a href="#warez">warez</a>:</li> + +<li><a href="#warezd00dz">warez d00dz</a>:</li> + +<li><a href="#warezkiddies">warez kiddies</a>:</li> + +<li><a href="#warlording">warlording</a>:</li> + +<li><a href="#warmboot">warm boot</a>:</li> + +<li><a href="#wart">wart</a>:</li> + +<li><a href="#washingmachine">washing machine</a>:</li> + +<li><a href="#washingsoftware">washing software</a>:</li> + +<li><a href="#waterMIPS">water MIPS</a>:</li> + +<li><a href="#waveadeadchicken">wave a dead chicken</a>:</li> + +<li><a href="#weasel">weasel</a>:</li> + +<li><a href="#webpointer">web pointer</a>:</li> + +<li><a href="#webtoaster">web toaster</a>:</li> + +<li><a href="#webify">webify</a>:</li> + +<li><a href="#webmaster">webmaster</a>:</li> + +<li><a href="#webring">web ring</a>:</li> + +<li><a href="#wedged">wedged</a>:</li> + +<li><a href="#wedgie">wedgie</a>:</li> + +<li><a href="#wedgitude">wedgitude</a>:</li> + +<li><a href="#weeble">weeble</a>:</li> + +<li><a href="#weeds">weeds</a>:</li> + +<li><a href="#weenie">weenie</a>:</li> + +<li><a href="#Weenix">Weenix</a>:</li> + +<li><a href="#well-behaved">well-behaved</a>:</li> + +<li><a href="#well-connected">well-connected</a>:</li> + +<li><a href="#wetware">wetware</a>:</li> + +<li><a href="#whack">whack</a>:</li> + +<li><a href="#whack-a-mole">whack-a-mole</a>:</li> + +<li><a href="#whacker">whacker</a>:</li> + +<li><a href="#whales">whales</a>:</li> + +<li><a href="#whalesong">whalesong</a>:</li> + +<li><a href="#Whatsaspline">What's a spline?</a>:</li> + +<li><a href="#wheel">wheel</a>:</li> + +<li><a href="#wheelbit">wheel bit</a>:</li> + +<li><a href="#wheelofreincarnation">wheel of reincarnation</a>:</li> + +<li><a href="#wheelwars">wheel wars</a>:</li> + +<li><a href="#WhiteBook">White Book</a>:</li> + +<li><a href="#whitelist">whitelist</a>:</li> + +<li><a href="#whizzy">whizzy</a>:</li> + +<li><a href="#wibble">wibble</a>:</li> + +<li><a href="#WIBNI">WIBNI</a>:</li> + +<li><a href="#widget">widget</a>:</li> + +<li><a href="#wiggles">wiggles</a>:</li> + +<li><a href="#WIMPenvironment">WIMP environment</a>:</li> + +<li><a href="#win">win</a>:</li> + +<li><a href="#winbig">win big</a>:</li> + +<li><a href="#winwin">win win</a>:</li> + +<li><a href="#Winchester">Winchester</a>:</li> + +<li><a href="#windoid">windoid</a>:</li> + +<li><a href="#windowshopping">window shopping</a>:</li> + +<li><a href="#Windoze">Windoze</a>:</li> + +<li><a href="#wingedcomments">winged comments</a>:</li> + +<li><a href="#winkey">winkey</a>:</li> + +<li><a href="#winnage">winnage</a>:</li> + +<li><a href="#winner">winner</a>:</li> + +<li><a href="#winnitude">winnitude</a>:</li> + +<li><a href="#Wintel">Wintel</a>:</li> + +<li><a href="#wired">wired</a>:</li> + +<li><a href="#wirehead">wirehead</a>:</li> + +<li><a href="#wirewater">wirewater</a>:</li> + +<li><a href="#wishlist">wish list</a>:</li> + +<li><a href="#withindeltaof">within delta of</a>:</li> + +<li><a href="#withinepsilonof">within epsilon of</a>:</li> + +<li><a href="#wizard">wizard</a>:</li> + +<li><a href="#WizardBook">Wizard Book</a>:</li> + +<li><a href="#wizardhat">wizard hat</a>:</li> + +<li><a href="#wizardmode">wizard mode</a>:</li> + +<li><a href="#wizardly">wizardly</a>:</li> + +<li><a href="#wok-on-the-wall">wok-on-the-wall</a>:</li> + +<li><a href="#wombbox">womb box</a>:</li> + +<li><a href="#WOMBAT">WOMBAT</a>:</li> + +<li><a href="#womble">womble</a>:</li> + +<li><a href="#wonky">wonky</a>:</li> + +<li><a href="#woofer">woofer</a>:</li> + +<li><a href="#workaround">workaround</a>:</li> + +<li><a href="#workingasdesigned">working as designed</a>:</li> + +<li><a href="#worm">worm</a>:</li> + +<li><a href="#wormhole">wormhole</a>:</li> + +<li><a href="#woundaroundtheaxle">wound around the axle</a>:</li> + +<li><a href="#wrapAround">wrap around</a>:</li> + +<li><a href="#writeonlycode">write-only code</a>:</li> + +<li><a href="#writeonlylanguage">write-only language</a>:</li> + +<li><a href="#write-onlymemory">write-only memory</a>:</li> + +<li><a href="#WrongThing">Wrong Thing</a>:</li> + +<li><a href="#wuggawugga">wugga wugga</a>:</li> + +<li><a href="#wumpus">wumpus</a>:</li> + +<li><a href="#WYSIAYG">WYSIAYG</a>:</li> + +<li><a href="#WYSIWYG">WYSIWYG</a>:</li> +</ul> + +<hr> +Node:<a name="W2Kbug">W2K bug</a>, Next:<a rel="next" href="#wabbit">wabbit</a>, Previous:<a rel="previous" href="#vulturecapitalist">vulture capitalist</a>, Up:<a rel="up" +href="#chap23">= W =</a> <br> + + +<p><b>W2K bug</b></p> + +<p>[from `Y2K bug' for the Year 2000 problem] The upcoming +deployment of Microsoft's Windows 2000 operating system, which +hackers generally expect will be among the worst train wrecks in +the history of software engineering. Such is the power of +Microsoft marketing, however, that it is also expected this will +not become obvious until it has incurred hundreds of millions of +dollars in downtime and lost opportunity costs.</p> + +<hr> +Node:<a name="wabbit">wabbit</a>, Next:<a rel="next" href="#WAITS">WAITS</a>, Previous:<a rel="previous" href="#W2Kbug">W2K bug</a>, Up:<a rel="up" href="#chap23">= +W =</a> <br> + + +<p><b>wabbit</b> /wab'it/ n.</p> + +<p>[almost certainly from Elmer Fudd's immortal line "You +wascawwy wabbit!"] 1. A legendary early hack reported on a +System/360 at RPI and elsewhere around 1978; this may have +descended (if only by inspiration) from a hack called RABBITS +reported from 1969 on a Burroughs 5500 at the University of +Washington Computer Center. The program would make two copies of +itself every time it was run, eventually crashing the system. 2. +By extension, any hack that includes infinite self-replication +but is not a <b><a href="#virus">virus</a></b> or <b><a href="#worm">worm</a></b>. See <b><a href="#forkbomb">fork +bomb</a></b> and <b><a href="#rabbitjob">rabbit job</a></b>, +see also <b><a href="#cookiemonster">cookie +monster</a></b>.</p> + +<hr> +Node:<a name="WAITS">WAITS</a>, Next:<a rel="next" href="#waldo">waldo</a>, Previous:<a rel="previous" href="#wabbit">wabbit</a>, Up:<a rel="up" href="#chap23">= W +=</a> <br> + + +<p><b>WAITS</b> /wayts/ n.</p> + +<p>The mutant cousin of <b><a href="#TOPS-10">TOPS-10</a></b> +used on a handful of systems at <b><a href="#SAIL">SAIL</a></b> +up to 1990. There was never an `official' expansion of WAITS (the +name itself having been arrived at by a rather sideways process), +but it was frequently glossed as `West-coast Alternative to ITS'. +Though WAITS was less visible than ITS, there was frequent +exchange of people and ideas between the two communities, and +innovations pioneered at WAITS exerted enormous indirect +influence. The early screen modes of <b><a href="#EMACS">EMACS</a></b>, for example, were directly inspired by +WAITS's `E' editor -- one of a family of editors that were the +first to do `real-time editing', in which the editing commands +were invisible and where one typed text at the point of +insertion/overwriting. The modern style of multi-region windowing +is said to have originated there, and WAITS alumni at XEROX PARC +and elsewhere played major roles in the developments that led to +the XEROX Star, the Macintosh, and the Sun workstations. Also +invented there were <b><a href="#buckybits">bucky bits</a></b> +-- thus, the ALT key on every IBM PC is a WAITS legacy. One WAITS +feature very notable in pre-Web days was a news-wire interface +that allowed WAITS hackers to read, store, and filter AP and UPI +dispatches from their terminals; the system also featured a +still-unusual level of support for what is now called +`multimedia' computing, allowing analog audio and video signals +to be switched to programming terminals.</p> + +<hr> +Node:<a name="waldo">waldo</a>, Next:<a rel="next" href="#walk">walk</a>, Previous:<a rel="previous" href="#WAITS">WAITS</a>, Up:<a rel="up" href="#chap23">= W +=</a> <br> + + +<p><b>waldo</b> /wol'doh/ n.</p> + +<p>[From Robert A. Heinlein's story "Waldo"] 1. A mechanical +agent, such as a gripper arm, controlled by a human limb. When +these were developed for the nuclear industry in the mid-1940s +they were named after the invention described by Heinlein in the +story, which he wrote in 1942. Now known by the more generic term +`telefactoring', this technology is of intense interest to NASA +for tasks like space station maintenance. 2. At Harvard +(particularly by Tom Cheatham and students), this is used instead +of <b><a href="#foobar">foobar</a></b> as a metasyntactic +variable and general nonsense word. See <b><a href="#foo">foo</a></b>, <b><a href="#bar">bar</a></b>, <b><a href="#foobar">foobar</a></b>, <b><a href="#quux">quux</a></b>.</p> + +<hr> +Node:<a name="walk">walk</a>, Next:<a rel="next" href="#walkofftheendof">walk off the end of</a>, +Previous:<a rel="previous" href="#waldo">waldo</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>walk</b> n.,vt.</p> + +<p>Traversal of a data structure, especially an array or +linked-list data structure in <b><a href="#core">core</a></b>. +See also <b><a href="#codewalker">codewalker</a></b>, <b><a href="#sillywalk">silly walk</a></b>, <b><a href="#clobber">clobber</a></b>.</p> + +<hr> +Node:<a name="walkofftheendof">walk off the end +of</a>, Next:<a rel="next" href="#walkingdrives">walking +drives</a>, Previous:<a rel="previous" href="#walk">walk</a>, +Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>walk off the end of</b> vt.</p> + +<p>To run past the end of an array, list, or medium after +stepping through it -- a good way to land in trouble. Often the +result of an <b><a href="#offbyoneerror">off-by-one +error</a></b>. Compare <b><a href="#clobber">clobber</a></b>, +<b><a href="#roach">roach</a></b>, <b><a href="#smashthestack">smash the stack</a></b>.</p> + +<hr> +Node:<a name="walkingdrives">walking drives</a>, Next:<a rel="next" href="#wall">wall</a>, Previous:<a rel="previous" href="#walkofftheendof">walk off the end of</a>, Up:<a +rel="up" href="#chap23">= W =</a> <br> + + +<p><b>walking drives</b> n.</p> + +<p>An occasional failure mode of magnetic-disk drives back in the +days when they were huge, clunky <b><a href="#washingmachine">washing machine</a></b>s. Those old <b><a +href="#dinosaur">dinosaur</a></b> parts carried terrific angular +momentum; the combination of a misaligned spindle or worn +bearings and stick-slip interactions with the floor could cause +them to `walk' across a room, lurching alternate corners forward +a couple of millimeters at a time. There is a legend about a +drive that walked over to the only door to the computer room and +jammed it shut; the staff had to cut a hole in the wall in order +to get at it! Walking could also be induced by certain patterns +of drive access (a fast seek across the whole width of the disk, +followed by a slow seek in the other direction). Some bands of +old-time hackers figured out how to induce disk-accessing +patterns that would do this to particular drive models and held +disk-drive races.</p> + +<hr> +Node:<a name="wall">wall</a>, Next:<a rel="next" href="#wallfollower">wall follower</a>, Previous:<a rel="previous" +href="#walkingdrives">walking drives</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>wall</b> interj.</p> + +<p>[WPI] 1. An indication of confusion, usually spoken with a +quizzical tone: "Wall??" 2. A request for further explication. +Compare <b><a href="#octalforty">octal forty</a></b>. 3. +[Unix, from `write all'] v. To send a message to everyone +currently logged in, esp. with the wall(8) utility.</p> + +<p>It is said that sense 1 came from the idiom `like talking to a +blank wall'. It was originally used in situations where, after +you had carefully answered a question, the questioner stared at +you blankly, clearly having understood nothing that was +explained. You would then throw out a "Hello, wall?" to elicit +some sort of response from the questioner. Later, confused +questioners began voicing "Wall?" themselves.</p> + +<hr> +Node:<a name="wallfollower">wall follower</a>, Next:<a rel="next" href="#walltime">wall time</a>, Previous:<a rel="previous" href="#wall">wall</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>wall follower</b> n.</p> + +<p>A person or algorithm that compensates for lack of +sophistication or native stupidity by efficiently following some +simple procedure shown to have been effective in the past. Used +of an algorithm, this is not necessarily pejorative; it recalls +`Harvey Wallbanger', the winning robot in an early AI contest +(named, of course, after the cocktail). Harvey successfully +solved mazes by keeping a `finger' on one wall and running till +it came out the other end. This was inelegant, but it was +mathematically guaranteed to work on simply-connected mazes -- +and, in fact, Harvey outperformed more sophisticated robots that +tried to `learn' each maze by building an internal representation +of it. Used of humans, the term <i>is</i> pejorative and +implies an uncreative, bureaucratic, by-the-book mentality. See +also <b><a href="#codegrinder">code grinder</a></b>; compare +<b><a href="#droid">droid</a></b>.</p> + +<hr> +Node:<a name="walltime">wall time</a>, Next:<a rel="next" +href="#wallwart">wall wart</a>, Previous:<a rel="previous" +href="#wallfollower">wall follower</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>wall time</b> n.</p> + +<p>(also `wall clock time') 1. `Real world' time (what the clock +on the wall shows), as opposed to the system clock's idea of +time. 2. The real running time of a program, as opposed to the +number of <b><a href="#tick">tick</a></b>s required to execute it +(on a timesharing system these always differ, as no one program +gets all the ticks, and on multiprocessor systems with good +thread support one may get more processor time than real +time).</p> + +<hr> +Node:<a name="wallwart">wall wart</a>, Next:<a rel="next" +href="#wallpaper">wallpaper</a>, Previous:<a rel="previous" href="#walltime">wall time</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>wall wart</b> n.</p> + +<p>A small power-supply brick with integral male plug, designed +to plug directly into a wall outlet; called a `wart' because when +installed on a power strip it tends to block up at least one more +socket than it uses.. These are frequently associated with modems +and other small electronic devices which would become +unacceptably bulky or hot if they had power supplies on board +(there are other reasons as well having to do with the cost of UL +certification).</p> + +<hr> +Node:<a name="wallpaper">wallpaper</a>, Next:<a rel="next" href="#wango">wango</a>, Previous:<a rel="previous" href="#wallwart">wall wart</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>wallpaper</b> n.</p> + +<p>1. A file containing a listing (e.g., assembly listing) or a +transcript, esp. a file containing a transcript of all or part of +a login session. (The idea was that the paper for such listings +was essentially good only for wallpaper, as evidenced at +Stanford, where it was used to cover windows.) Now rare, esp. +since other systems have developed other terms for it (e.g., +PHOTO on TWENEX). However, the Unix world doesn't have an +equivalent term, so perhaps <b><a href="#wallpaper">wallpaper</a></b> will take hold there. The term +probably originated on ITS, where the commands to begin and end +transcript files were <code>:WALBEG</code> and +<code>:WALEND</code>, with default file <code>WALL PAPER</code> +(the space was a path delimiter). 2. The background pattern used +on graphical workstations (this is techspeak under the `Windows' +graphical user interface to MS-DOS). 3. `wallpaper file' n. The +file that contains the wallpaper information before it is +actually printed on paper. (Even if you don't intend ever to +produce a real paper copy of the file, it is still called a +wallpaper file.)</p> + +<hr> +Node:<a name="wango">wango</a>, Next:<a rel="next" href="#wank">wank</a>, Previous:<a rel="previous" href="#wallpaper">wallpaper</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>wango</b> /wang'goh/ n.</p> + +<p>Random bit-level <b><a href="#grovel">grovel</a></b>ling going +on in a system during some unspecified operation. Often used in +combination with <b><a href="#mumble">mumble</a></b>. For +example: "You start with the `.o' file, run it through this +postprocessor that does mumble-wango -- and it comes out a snazzy +object-oriented executable."</p> + +<hr> +Node:<a name="wank">wank</a>, Next:<a rel="next" href="#wannabee">wannabee</a>, Previous:<a rel="previous" href="#wango">wango</a>, Up:<a rel="up" href="#chap23">= W +=</a> <br> + + +<p><b>wank</b> /wangk/ n.,v.,adj.</p> + +<p>[Columbia University: prob. by mutation from Commonwealth +slang v. `wank', to masturbate] Used much as <b><a href="#hack">hack</a></b> is elsewhere, as a noun denoting a clever +technique or person or the result of such cleverness. May +describe (negatively) the act of hacking for hacking's sake +("Quit wanking, let's go get supper!") or (more positively) a +<b><a href="#wizard">wizard</a></b>. Adj. `wanky' describes +something particularly clever (a person, program, or algorithm). +Conversations can also get wanky when there are too many wanks +involved. This excess wankiness is signalled by an overload of +the `wankometer' (compare <b><a href="#bogometer">bogometer</a></b>). When the wankometer overloads, +the conversation's subject must be changed, or all non-wanks will +leave. Compare `neep-neeping' (under <b><a href="#neep-neep">neep-neep</a></b>). Usage: U.S. only. In Britain and +the Commonwealth this word is <i>extremely</i> rude and is best +avoided unless one intends to give offense. Adjectival `wanky' is +less offensive and simply means `stupid' or `broken' (this is +mainstream in Great Britain).</p> + +<hr> +Node:<a name="wannabee">wannabee</a>, Next:<a rel="next" href="#wardialer">war dialer</a>, Previous:<a rel="previous" href="#wank">wank</a>, Up:<a rel="up" href="#chap23">= W =</a> +<br> + + +<p><b>wannabee</b> /won'*-bee/ n.</p> + +<p>(also, more plausibly, spelled `wannabe') [from a term +recently used to describe Madonna fans who dress, talk, and act +like their idol; prob. originally from biker slang] A would-be +<b><a href="#hacker">hacker</a></b>. The connotations of this +term differ sharply depending on the age and exposure of the +subject. Used of a person who is in or might be entering <b><a +href="#larvalstage">larval stage</a></b>, it is +semi-approving; such wannabees can be annoying but most hackers +remember that they, too, were once such creatures. When used of +any professional programmer, CS academic, writer, or <b><a href="#suit">suit</a></b>, it is derogatory, implying that said person +is trying to cuddle up to the hacker mystique but doesn't, +fundamentally, have a prayer of understanding what it is all +about. Overuse of terms from this lexicon is often an indication +of the <b><a href="#wannabee">wannabee</a></b> nature. Compare +<b><a href="#newbie">newbie</a></b>.</p> + +<p>Historical note: The wannabee phenomenon has a slightly +different flavor now (1993) than it did ten or fifteen years ago. +When the people who are now hackerdom's tribal elders were in +<b><a href="#larvalstage">larval stage</a></b>, the process of +becoming a hacker was largely unconscious and unaffected by +models known in popular culture -- communities formed +spontaneously around people who, <i>as individuals</i>, felt +irresistibly drawn to do hackerly things, and what wannabees +experienced was a fairly pure, skill-focused desire to become +similarly wizardly. Those days of innocence are gone forever; +society's adaptation to the advent of the microcomputer after +1980 included the elevation of the hacker as a new kind of folk +hero, and the result is that some people semi-consciously set out +to <i>be hackers</i> and borrow hackish prestige by fitting the +popular image of hackers. Fortunately, to do this really well, +one has to actually become a wizard. Nevertheless, old-time +hackers tend to share a poorly articulated disquiet about the +change; among other things, it gives them mixed feelings about +the effects of public compendia of lore like this one.</p> + +<hr> +Node:<a name="wardialer">war dialer</a>, Next:<a rel="next" +href="#-ware">-ware</a>, Previous:<a rel="previous" href="#wannabee">wannabee</a>, Up:<a rel="up" href="#chap23">= +W =</a> <br> + + +<p><b>war dialer</b> n.</p> + +<p>A cracking tool, a program that calls a given list or range of +phone numbers and records those which answer with handshake tones +(and so might be entry points to computer or telecommunications +systems). Some of these programs have become quite sophisticated, +and can now detect modem, fax, or PBX tones and log each one +separately. The war dialer is one of the most important tools in +the <b><a href="#phreaker">phreaker</a></b>'s kit. These programs +evolved from early <b><a href="#demondialer">demon +dialer</a></b>s.</p> + +<hr> +Node:<a name="-ware">-ware</a>, Next:<a rel="next" href="#warez">warez</a>, Previous:<a rel="previous" href="#wardialer">war dialer</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>-ware</b> suff.</p> + +<p>[from `software'] Commonly used to form jargon terms for +classes of software. For examples, see <b><a href="#annoyware">annoyware</a></b>, <b><a href="#careware">careware</a></b>, <b><a href="#crippleware">crippleware</a></b>, <b><a href="#crudware">crudware</a></b>, <b><a href="#freeware">freeware</a></b>, <b><a href="#fritterware">fritterware</a></b>, <b><a href="#guiltware">guiltware</a></b>, <b><a href="#liveware">liveware</a></b>, <b><a href="#meatware">meatware</a></b>, <b><a href="#payware">payware</a></b>, <b><a href="#psychedelicware">psychedelicware</a></b>, <b><a href="#shareware">shareware</a></b>, <b><a href="#shelfware">shelfware</a></b>, <b><a href="#vaporware">vaporware</a></b>, <b><a href="#wetware">wetware</a></b>.</p> + +<hr> +Node:<a name="warez">warez</a>, Next:<a rel="next" href="#warezd00dz">warez d00dz</a>, Previous:<a rel="previous" +href="#-ware">-ware</a>, Up:<a rel="up" href="#chap23">= W +=</a> <br> + + +<p><b>warez</b> /weirz/ n.</p> + +<p>Widely used in <b><a href="#cracker">cracker</a></b> +subcultures to denote cracked version of commercial software, +that is versions from which copy-protection has been stripped. +Hackers recognize this term but don't use it themselves. See +<b><a href="#warezd00dz">warez d00dz</a></b>, <b><a href="#courier">courier</a></b>, <b><a href="#leech">leech</a></b>, +<b><a href="#elite">elite</a></b>.</p> + +<hr> +Node:<a name="warezd00dz">warez d00dz</a>, Next:<a rel="next" +href="#warezkiddies">warez kiddies</a>, Previous:<a rel="previous" href="#warez">warez</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>warez d00dz</b> /weirz doodz/ n.</p> + +<p>A substantial subculture of <b><a href="#cracker">cracker</a></b>s refer to themselves as `warez d00dz'; +there is evidently some connection with <b><a href="#B1FF">B1FF</a></b> here. As `Ozone Pilot', one former warez +d00d, wrote:</p> + +<blockquote>Warez d00dz get illegal copies of copyrighted +software. If it has copy protection on it, they break the +protection so the software can be copied. Then they distribute it +around the world via several gateways. Warez d00dz form badass +group names like RAZOR and the like. They put up boards that +distribute the latest ware, or pirate program. The whole point of +the Warez sub-culture is to get the pirate program released and +distributed before any other group. I know, I know. But don't +ask, and it won't hurt as much. This is how they prove their +poweress [sic]. It gives them the right to say, "I released +King's Quest IVXIX before you so obviously my testicles are +larger." Again don't ask...</blockquote> + +<p>The studly thing to do if one is a warez d00d, it appears, is +emit `0-day warez', that is copies of commercial software copied +and cracked on the same day as its retail release. Warez d00ds +also hoard software in a big way, collecting untold megabytes of +arcade-style games, pornographic JPGs, and applications they'll +never use onto their hard disks. As Ozone Pilot acutely +observes:</p> + +<blockquote>[BELONG] is the only word you will need to know. +Warez d00dz want to belong. They have been shunned by everyone, +and thus turn to cyberspace for acceptance. That is why they +always start groups like TGW, FLT, USA and the like. Structure +makes them happy. [...] Warez d00dz will never have a handle like +"Pink Daisy" because warez d00dz are insecure. Only someone who +is very secure with a good dose of self-esteem can stand up to +the cries of fag and girlie-man. More likely you will find warez +d00dz with handles like: Doctor Death, Deranged Lunatic, +Hellraiser, Mad Prince, Dreamdevil, The Unknown, Renegade +Chemist, Terminator, and Twin Turbo. They like to sound badass +when they can hide behind their terminals. More likely, if you +were given a sample of 100 people, the person whose handle is +Hellraiser is the last person you'd associate with the +name.</blockquote> + +<p>The contrast with Internet hackers is stark and instructive. +See <b><a href="#cracker">cracker</a></b>, <b><a href="#wannabee">wannabee</a></b>, <b><a href="#handle">handle</a></b>, <b><a href="#elite">elite</a></b>, +<b><a href="#courier">courier</a></b>, <b><a href="#leech">leech</a></b>; compare <b><a href="#weenie">weenie</a></b>, <b><a href="#spod">spod</a></b>.</p> + +<hr> +Node:<a name="warezkiddies">warez kiddies</a>, Next:<a rel="next" href="#warlording">warlording</a>, Previous:<a rel="previous" href="#warezd00dz">warez d00dz</a>, Up:<a rel="up" +href="#chap23">= W =</a> <br> + + +<p><b>warez kiddies</b> n.</p> + +<p>Even more derogatory way of referring to <b><a href="#warezd00dz">warez d00dz</a></b>; refers to the fact that +most warez d00dz are around the age of puberty. Compare <b><a +href="#scriptkiddies">script kiddies</a></b>.</p> + +<hr> +Node:<a name="warlording">warlording</a>, Next:<a rel="next" +href="#warmboot">warm boot</a>, Previous:<a rel="previous" +href="#warezkiddies">warez kiddies</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>warlording</b> v.</p> + +<p>[from the Usenet group <i>alt.fan.warlord</i>] The act of +excoriating a bloated, ugly, or derivative <b><a href="#sigblock">sig block</a></b>. Common grounds for warlording +include the presence of a signature rendered in a <b><a href="#BUAF">BUAF</a></b>, over-used or cliched <b><a href="#sigquote">sig quote</a></b>s, ugly <b><a href="#ASCIIart">ASCII art</a></b>, or simply excessive size. The +original `Warlord' was a <b><a href="#B1FF">B1FF</a></b>-like +<b><a href="#newbie">newbie</a></b> c.1991 who featured in his +sig a particularly large and obnoxious ASCII graphic resembling +the sword of Conan the Barbarian in the 1981 John Milius movie; +the group name <i>alt.fan.warlord</i> was sarcasm, and the +characteristic mode of warlording is devastatingly sarcastic +praise.</p> + +<hr> +Node:<a name="warmboot">warm boot</a>, Next:<a rel="next" +href="#wart">wart</a>, Previous:<a rel="previous" href="#warlording">warlording</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>warm boot</b> n.</p> + +<p>See <b><a href="#boot">boot</a></b>.</p> + +<hr> +Node:<a name="wart">wart</a>, Next:<a rel="next" href="#washingmachine">washing machine</a>, Previous:<a rel="previous" href="#warmboot">warm boot</a>, Up:<a rel="up" +href="#chap23">= W =</a> <br> + + +<p><b>wart</b> n.</p> + +<p>A small, <b><a href="#crock">crock</a></b>y <b><a href="#feature">feature</a></b> that sticks out of an otherwise <b><a +href="#clean">clean</a></b> design. Something conspicuous for +localized ugliness, especially a special-case exception to a +general rule. For example, in some versions of +<code>csh(1)</code>, single quotes literalize every character +inside them except <code>!</code>. In ANSI C, the <code>??</code> +syntax used for obtaining ASCII characters in a foreign +environment is a wart. See also <b><a href="#miswart">miswart</a></b>.</p> + +<hr> +Node:<a name="washingmachine">washing machine</a>, Next:<a +rel="next" href="#washingsoftware">washing software</a>, +Previous:<a rel="previous" href="#wart">wart</a>, Up:<a rel="up" +href="#chap23">= W =</a> <br> + + +<p><b>washing machine</b> n.</p> + +<p>1. Old-style 14-inch hard disks in floor-standing cabinets. So +called because of the size of the cabinet and the `top-loading' +access to the media packs -- and, of course, they were always set +on `spin cycle'. The washing-machine idiom transcends language +barriers; it is even used in Russian hacker jargon. See also +<b><a href="#walkingdrives">walking drives</a></b>. The thick +channel cables connecting these were called `bit hoses' (see +<b><a href="#hose">hose</a></b>, sense 3). 2. [CMU] A machine +used exclusively for <b><a href="#washingsoftware">washing +software</a></b>. CMU has clusters of these.</p> + +<hr> +Node:<a name="washingsoftware">washing software</a>, Next:<a +rel="next" href="#waterMIPS">water MIPS</a>, Previous:<a rel="previous" href="#washingmachine">washing machine</a>, Up:<a +rel="up" href="#chap23">= W =</a> <br> + + +<p><b>washing software</b> n.</p> + +<p>The process of recompiling a software distribution (used more +often when the recompilation is occuring from scratch) to pick up +and merge together all of the various changes that have been made +to the source.</p> + +<hr> +Node:<a name="waterMIPS">water MIPS</a>, Next:<a rel="next" +href="#waveadeadchicken">wave a dead chicken</a>, +Previous:<a rel="previous" href="#washingsoftware">washing +software</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>water MIPS</b> n.</p> + +<p>(see <b><a href="#MIPS">MIPS</a></b>, sense 2) Large, +water-cooled machines of either today's ECL-supercomputer flavor +or yesterday's traditional <b><a href="#mainframe">mainframe</a></b> type.</p> + +<hr> +Node:<a name="waveadeadchicken">wave a dead chicken</a>, +Next:<a rel="next" href="#weasel">weasel</a>, Previous:<a rel="previous" href="#waterMIPS">water MIPS</a>, Up:<a rel="up" +href="#chap23">= W =</a> <br> + + +<p><b>wave a dead chicken</b> v.</p> + +<p>To perform a ritual in the direction of crashed software or +hardware that one believes to be futile but is nevertheless +necessary so that others are satisfied that an appropriate degree +of effort has been expended. "I'll wave a dead chicken over the +source code, but I really think we've run into an OS bug." +Compare <b><a href="#voodooprogramming">voodoo +programming</a></b>, <b><a href="#raindance">rain +dance</a></b>; see also <b><a href="#castingtherunes">casting the runes</a></b>.</p> + +<hr> +Node:<a name="weasel">weasel</a>, Next:<a rel="next" href="#webpointer">web pointer</a>, Previous:<a rel="previous" +href="#waveadeadchicken">wave a dead chicken</a>, Up:<a +rel="up" href="#chap23">= W =</a> <br> + + +<p><b>weasel</b> n.</p> + +<p>[Cambridge] A naive user, one who deliberately or accidentally +does things that are stupid or ill-advised. Roughly synonymous +with <b><a href="#loser">loser</a></b>.</p> + +<hr> +Node:<a name="webpointer">web pointer</a>, Next:<a rel="next" +href="#webtoaster">web toaster</a>, Previous:<a rel="previous" +href="#weasel">weasel</a>, Up:<a rel="up" href="#chap23">= +W =</a> <br> + + +<p><b>web pointer</b> n.</p> + +<p>A World Wide Web <b><a href="#URL">URL</a></b>. See also <b><a +href="#hotlink">hotlink</a></b>, which has slightly different +connotations.</p> + +<hr> +Node:<a name="webtoaster">web toaster</a>, Next:<a rel="next" +href="#webify">webify</a>, Previous:<a rel="previous" href="#webpointer">web pointer</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>web toaster</b> n.</p> + +<p>A small specialized computer, shipped with no monitor or +keyboard or any other external peripherals, pre-configured to be +controlled through an Ethernet port and function as a WWW server. +Products of this kind (for example the Cobalt Qube) are often +about the size of a toaster. See <b><a href="#toaster">toaster</a></b>; compare <b><a href="#videotoaster">video toaster</a></b>.</p> + +<hr> +Node:<a name="webify">webify</a>, Next:<a rel="next" href="#webmaster">webmaster</a>, Previous:<a rel="previous" href="#webtoaster">web toaster</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>webify</b> n.</p> + +<p>To put a piece of (possibly already existing) material on the +WWW. Frequently used for papers ("Why don't you webify all your +publications?") or for demos ("They webified their 6.866 final +project"). This term seems to have been (rather logically) +independently invented multiple times in the early 1990s.</p> + +<hr> +Node:<a name="webmaster">webmaster</a>, Next:<a rel="next" href="#webring">web ring</a>, Previous:<a rel="previous" href="#webify">webify</a>, Up:<a rel="up" href="#chap23">= W +=</a> <br> + + +<p><b>webmaster</b> n.</p> + +<p>[WWW: from <b><a href="#postmaster">postmaster</a></b>] The +person at a site providing World Wide Web information who is +responsible for maintaining the public pages and keeping the Web +server running and properly configured.</p> + +<hr> +Node:<a name="webring">web ring</a>, Next:<a rel="next" href="#wedged">wedged</a>, Previous:<a rel="previous" href="#webmaster">webmaster</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>web ring</b> n.</p> + +<p>Two or more web sites connected by prominent links between +sites sharing a common interest or theme. Usually such cliques +have the topology of a ring, in order to make it easy for +visitors to navigate through all of them.</p> + +<hr> +Node:<a name="wedged">wedged</a>, Next:<a rel="next" href="#wedgie">wedgie</a>, Previous:<a rel="previous" href="#webring">web ring</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>wedged</b> adj.</p> + +<p>1. To be stuck, incapable of proceeding without help. This is +different from having crashed. If the system has crashed, it has +become totally non-functioning. If the system is wedged, it is +trying to do something but cannot make progress; it may be +capable of doing a few things, but not be fully operational. For +example, a process may become wedged if it <b><a href="#deadlock">deadlock</a></b>s with another (but not all instances +of wedging are deadlocks). See also <b><a href="#gronk">gronk</a></b>, <b><a href="#lockedup">locked +up</a></b>, <b><a href="#hosed">hosed</a></b>, <b><a href="#hung">hung</a></b> (wedged is more severe than <b><a href="#hung">hung</a></b>). 2. Often refers to humans suffering +misconceptions. "He's totally wedged -- he's convinced that he +can levitate through meditation." 3. [Unix] Specifically used to +describe the state of a TTY left in a losing state by abort of a +screen-oriented program or one that has messed with the line +discipline in some obscure way.</p> + +<p>There is some dispute over the origin of this term. It is +usually thought to derive from a common description of +recto-cranial inversion; however, it may actually have originated +with older `hot-press' printing technology in which physical type +elements were locked into type frames with wedges driven in by +mallets. Once this had been done, no changes in the typesetting +for that page could be made.</p> + +<hr> +Node:<a name="wedgie">wedgie</a>, Next:<a rel="next" href="#wedgitude">wedgitude</a>, Previous:<a rel="previous" href="#wedged">wedged</a>, Up:<a rel="up" href="#chap23">= W +=</a> <br> + + +<p><b>wedgie</b> n.</p> + +<p>[Fairchild] A bug. Prob. related to <b><a href="#wedged">wedged</a></b>.</p> + +<hr> +Node:<a name="wedgitude">wedgitude</a>, Next:<a rel="next" href="#weeble">weeble</a>, Previous:<a rel="previous" href="#wedgie">wedgie</a>, Up:<a rel="up" href="#chap23">= W +=</a> <br> + + +<p><b>wedgitude</b> /wedj'i-t[y]ood/ n.</p> + +<p>The quality or state of being <b><a href="#wedged">wedged</a></b>.</p> + +<hr> +Node:<a name="weeble">weeble</a>, Next:<a rel="next" href="#weeds">weeds</a>, Previous:<a rel="previous" href="#wedgitude">wedgitude</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>weeble</b> /weeb'l/ interj.</p> + +<p>[Cambridge] Used to denote frustration, usually at amazing +stupidity. "I stuck the disk in upside down." +"Weeble<small>...</small>." Compare <b><a href="#gurfle">gurfle</a></b>.</p> + +<hr> +Node:<a name="weeds">weeds</a>, Next:<a rel="next" href="#weenie">weenie</a>, Previous:<a rel="previous" href="#weeble">weeble</a>, Up:<a rel="up" href="#chap23">= W +=</a> <br> + + +<p><b>weeds</b> n.</p> + +<p>1. Refers to development projects or algorithms that have no +possible relevance or practical application. Comes from `off in +the weeds'. Used in phrases like "lexical analysis for microcode +is serious weeds<small>...</small>." 2. At CDC/ETA before its +demise, the phrase `go off in the weeds' was equivalent to IBM's +<b><a href="#branchtoFishkill">branch to Fishkill</a></b> +and mainstream hackerdom's <b><a href="#jumpoffintoneverneverland">jump off into +never-never land</a></b>.</p> + +<hr> +Node:<a name="weenie">weenie</a>, Next:<a rel="next" href="#Weenix">Weenix</a>, Previous:<a rel="previous" href="#weeds">weeds</a>, Up:<a rel="up" href="#chap23">= W +=</a> <br> + + +<p><b>weenie</b> n.</p> + +<p>1. [on BBSes] Any of a species of luser resembling a less +amusing version of <b><a href="#B1FF">B1FF</a></b> that infests +many <b><a href="#BBS">BBS</a></b> systems. The typical weenie is +a teenage boy with poor social skills travelling under a +grandiose <b><a href="#handle">handle</a></b> derived from +fantasy or heavy-metal rock lyrics. Among sysops, `the weenie +problem' refers to the marginally literate and profanity-laden +<b><a href="#flamage">flamage</a></b> weenies tend to spew all +over a newly-discovered BBS. Compare <b><a href="#spod">spod</a></b>, <b><a href="#computergeek">computer +geek</a></b>, <b><a href="#terminaljunkie">terminal +junkie</a></b>, <b><a href="#warezd00dz">warez d00dz</a></b>. +2. [Among hackers] When used with a qualifier (for example, as in +<b><a href="#Unixweenie">Unix weenie</a></b>, VMS weenie, IBM +weenie) this can be either an insult or a term of praise, +depending on context, tone of voice, and whether or not it is +applied by a person who considers him or herself to be the same +sort of weenie. Implies that the weenie has put a major +investment of time, effort, and concentration into the area +indicated; whether this is good or bad depends on the hearer's +judgment of how the speaker feels about that area. See also <b><a +href="#bigot">bigot</a></b>. 3. The semicolon character, +<code>;</code> (ASCII 0111011).</p> + +<hr> +Node:<a name="Weenix">Weenix</a>, Next:<a rel="next" href="#well-behaved">well-behaved</a>, Previous:<a rel="previous" +href="#weenie">weenie</a>, Up:<a rel="up" href="#chap23">= +W =</a> <br> + + +<p><b>Weenix</b> /wee'niks/ n.</p> + +<p>1. [ITS] A derogatory term for <b><a href="#Unix">Unix</a></b>, derived from <b><a href="#Unixweenie">Unix weenie</a></b>. According to one noted +ex-ITSer, it is "the operating system preferred by Unix Weenies: +typified by poor modularity, poor reliability, hard file +deletion, no file version numbers, case sensitivity everywhere, +and users who believe that these are all advantages". (Some ITS +fans behave as though they believe Unix stole a future that +rightfully belonged to them. See <b><a href="#ITS">ITS</a></b>, +sense 2.) 2. [Brown University] A Unix-like OS developed for +tutorial purposes at Brown University. See http://www.cs.brown.edu/courses/cs167/weenix.html. +Named independently of the ITS usage.</p> + +<hr> +Node:<a name="well-behaved">well-behaved</a>, Next:<a rel="next" +href="#well-connected">well-connected</a>, Previous:<a rel="previous" href="#Weenix">Weenix</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>well-behaved</b> adj.</p> + +<p>1. [primarily <b><a href="#MS-DOS">MS-DOS</a></b>] Said of +software conforming to system interface guidelines and standards. +Well-behaved software uses the operating system to do chores such +as keyboard input, allocating memory and drawing graphics. Oppose +<b><a href="#ill-behaved">ill-behaved</a></b>. 2. Software that +does its job quietly and without counterintuitive effects. Esp. +said of software having an interface spec sufficiently simple and +well-defined that it can be used as a <b><a href="#tool">tool</a></b> by other software. See <b><a href="#cat">cat</a></b>. 3. Said of an algorithm that doesn't <b><a +href="#crash">crash</a></b> or <b><a href="#blowup">blow +up</a></b>, even when given <b><a href="#pathological">pathological</a></b> input. Implies that the +stability of the algorithm is intrinsic, which makes this +somewhat different from <b><a href="#bulletproof">bulletproof</a></b>.</p> + +<hr> +Node:<a name="well-connected">well-connected</a>, Next:<a rel="next" href="#wetware">wetware</a>, Previous:<a rel="previous" +href="#well-behaved">well-behaved</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>well-connected</b> adj.</p> + +<p>Said of a computer installation, asserts that it has reliable +email links with the network and/or that it relays a large +fraction of available <b><a href="#Usenet">Usenet</a></b> +newsgroups. `Well-known' can be almost synonymous, but also +implies that the site's name is familiar to many (due perhaps to +an archive service or active Usenet users).</p> + +<hr> +Node:<a name="wetware">wetware</a>, Next:<a rel="next" href="#whack">whack</a>, Previous:<a rel="previous" href="#well-connected">well-connected</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>wetware</b> /wet'weir/ n.</p> + +<p>[prob. from the novels of Rudy Rucker] 1. The human nervous +system, as opposed to computer hardware or software. "Wetware has +7 plus or minus 2 temporary registers." 2. Human beings +(programmers, operators, administrators) attached to a computer +system, as opposed to the system's hardware or software. See +<b><a href="#liveware">liveware</a></b>, <b><a href="#meatware">meatware</a></b>.</p> + +<hr> +Node:<a name="whack">whack</a>, Next:<a rel="next" href="#whack-a-mole">whack-a-mole</a>, Previous:<a rel="previous" +href="#wetware">wetware</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>whack</b> v.</p> + +<p>According to arch-hacker James Gosling (designer of <b><a +href="#NeWS">NeWS</a></b>, <b><a href="#GOSMACS">GOSMACS</a></b> +and Java), to "...modify a program with no idea whatsoever how it +works." (See <b><a href="#whacker">whacker</a></b>.) It is +actually possible to do this in nontrivial circumstances if the +change is small and well-defined and you are very good at <b><a +href="#glark">glark</a></b>ing things from context. As a trivial +example, it is relatively easy to change all <code>stderr</code> +writes to <code>stdout</code> writes in a piece of C filter code +which remains otherwise mysterious.</p> + +<hr> +Node:<a name="whack-a-mole">whack-a-mole</a>, Next:<a rel="next" +href="#whacker">whacker</a>, Previous:<a rel="previous" href="#whack">whack</a>, Up:<a rel="up" href="#chap23">= W +=</a> <br> + + +<p><b>whack-a-mole</b> n.</p> + +<p>[from the carnival game which involves quickly and repeatedly +hitting the heads of mechanical moles with a mallet as they pop +up from their holes.] 1. The practice of repeatedly causing +spammers' <b><a href="#throwawayaccount">throwaway +account</a></b>s and drop boxes to be terminated. 2. After sense +1 became established in the mid-1990s the term passed into more +generalized use, and now is commonly found in such combinations +as `whack-a-mole windows'; the obnoxious pop-ip advertisement +windows spawned in flocks when you surg to sites like Geocities +or Tripod.</p> + +<hr> +Node:<a name="whacker">whacker</a>, Next:<a rel="next" href="#whales">whales</a>, Previous:<a rel="previous" href="#whack-a-mole">whack-a-mole</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>whacker</b> n.</p> + +<p>[University of Maryland: from <b><a href="#hacker">hacker</a></b>] 1. A person, similar to a <b><a href="#hacker">hacker</a></b>, who enjoys exploring the details of +programmable systems and how to stretch their capabilities. +Whereas a hacker tends to produce great hacks, a whacker only +ends up whacking the system or program in question. Whackers are +often quite egotistical and eager to claim <b><a href="#wizard">wizard</a></b> status, regardless of the views of their +peers. 2. A person who is good at programming quickly, though +rather poorly and ineptly.</p> + +<hr> +Node:<a name="whales">whales</a>, Next:<a rel="next" href="#whalesong">whalesong</a>, Previous:<a rel="previous" href="#whacker">whacker</a>, Up:<a rel="up" href="#chap23">= W +=</a> <br> + + +<p><b>whales</b> n.</p> + +<p>See <b><a href="#likekickingdeadwhalesdownthebeach">like +kicking dead whales down the beach</a></b>.</p> + +<hr> +Node:<a name="whalesong">whalesong</a>, +Next:<a rel="next" href="#Whatsaspline">What's a spline?</a>, +Previous:<a rel="previous" href="#whales">whales</a>, +Up:<a rel="up" href="#chap23">= W =</a> <br> + +<p><b>whalesong</b> n.</p> + +<p>The peculiar clicking and whooshing sounds made by a PEP modem +such as the Telebit Trailblazer as it tries to synchronize with +another PEP modem for their special high-speed mode. This sound +isn't anything like the normal two-tone handshake between +conventional V-series modems and is instantly recognizable to +anyone who has heard it more than once. It sounds, in fact, very +much like whale songs. This noise is also called "the moose call" +or "moose tones".</p> + +<hr> +Node:<a name="Whatsaspline">What's a spline?</a>, +Next:<a rel="next" href="#wheel">wheel</a>, Previous:<a rel="previous" href="#whalesong">whalesong</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>What's a spline?</b></p> + +<p>[XEROX PARC] This phrase expands to: "You have just used a +term that I've heard for a year and a half, and I feel I should +know, but don't. My curiosity has finally overcome my guilt." The +PARC lexicon adds "Moral: don't hesitate to ask questions, even +if they seem obvious."</p> + +<hr> +Node:<a name="wheel">wheel</a>, Next:<a rel="next" href="#wheelbit">wheel bit</a>, Previous:<a rel="previous" href="#Whatsaspline">What's a spline?</a>, Up:<a rel="up" +href="#chap23">= W =</a> <br> + + +<p><b>wheel</b> n.</p> + +<p>[from slang `big wheel' for a powerful person] A person who +has an active <b><a href="#wheelbit">wheel bit</a></b>. "We +need to find a wheel to unwedge the hung tape drives." (See <b><a +href="#wedged">wedged</a></b>, sense 1.) The traditional name of +security group zero in <b><a href="#BSD">BSD</a></b> (to which +the major system-internal users like <b><a href="#root">root</a></b> belong) is `wheel'. Some vendors have +expanded on this usage, modifying Unix so that only members of +group `wheel' can <b><a href="#goRoot">go root</a></b>.</p> + +<hr> +Node:<a name="wheelbit">wheel bit</a>, Next:<a rel="next" +href="#wheelofreincarnation">wheel of reincarnation</a>, +Previous:<a rel="previous" href="#wheel">wheel</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>wheel bit</b> n.</p> + +<p>A privilege bit that allows the possessor to perform some +restricted operation on a timesharing system, such as read or +write any file on the system regardless of protections, change or +look at any address in the running monitor, crash or reload the +system, and kill or create jobs and user accounts. The term was +invented on the TENEX operating system, and carried over to +TOPS-20, XEROX-IFS, and others. The state of being in a +privileged logon is sometimes called `wheel mode'. This term +entered the Unix culture from TWENEX in the mid-1980s and has +been gaining popularity there (esp. at university sites). See +also <b><a href="#root">root</a></b>.</p> + +<hr> +Node:<a name="wheelofreincarnation">wheel of +reincarnation</a>, Next:<a rel="next" href="#wheelwars">wheel +wars</a>, Previous:<a rel="previous" href="#wheelbit">wheel +bit</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>wheel of reincarnation</b></p> + +<p>[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.</p> + +<p>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 <b><a href="#blitter">blitter</a></b>, <b><a href="#bitbang">bit +bang</a></b>.</p> + +<hr> +Node:<a name="wheelwars">wheel wars</a>, Next:<a rel="next" +href="#WhiteBook">White Book</a>, Previous:<a rel="previous" +href="#wheelofreincarnation">wheel of reincarnation</a>, +Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>wheel wars</b> n.</p> + +<p>[Stanford University] A period in <b><a href="#larvalstage">larval stage</a></b> during which student +hackers hassle each other by attempting to log each other out of +the system, delete each other's files, and otherwise wreak havoc, +usually at the expense of the lesser users.</p> + +<hr> +Node:<a name="WhiteBook">White Book</a>, Next:<a rel="next" +href="#whitelist">whitelist</a>, Previous:<a rel="previous" href="#wheelwars">wheel wars</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>White Book</b> n.</p> + +<p>1. Syn. <b><a href="#KandR">K&R</a></b>. 2. Adobe's +fourth book in the PostScript series, describing the +previously-secret format of Type 1 fonts; "Adobe Type 1 Font +Format, version 1.1", (Addison-Wesley, 1990, ISBN 0-201-57044-0). +See also <b><a href="#RedBook">Red Book</a></b>, <b><a href="#GreenBook">Green Book</a></b>, <b><a href="#BlueBook">Blue Book</a></b>.</p> + +<hr> +Node:<a name="whitelist">whitelist</a>, Next:<a rel="next" href="#whizzy">whizzy</a>, Previous:<a rel="previous" href="#WhiteBook">White Book</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>whitelist</b> n.</p> + +<p>The opposite of a blacklist. That is, instead of being an +explicit list of people who are banned, it's an explicit list of +people who are to be admitted. Hackers use this especially of +lists of email addresses that are explicitly enabled to get past +strict anti-spam filters.</p> + +<hr> +Node:<a name="whizzy">whizzy</a>, Next:<a rel="next" href="#wibble">wibble</a>, Previous:<a rel="previous" href="#whitelist">whitelist</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>whizzy</b> adj.</p> + +<p>(alt. `wizzy') [Sun] Describes a <b><a href="#cuspy">cuspy</a></b> program; one that is feature-rich and well +presented.</p> + +<hr> +Node:<a name="wibble">wibble</a>, Next:<a rel="next" href="#WIBNI">WIBNI</a>, Previous:<a rel="previous" href="#whizzy">whizzy</a>, Up:<a rel="up" href="#chap23">= W +=</a> <br> + + +<p><b>wibble</b></p> + +<p>[UK, perh. originally from the first "Roger Irrelevant" strip +in "VIZ" comics, spread via "Your Sinclair magazine in the 1980s +and early 1990s"] 1. n.,v. Commonly used to describe chatter, +content-free remarks or other essentially meaningless +contributions to threads in newsgroups. "Oh, rspence is wibbling +again". 2. [UK IRC] An explicit on-line no-op equivalent to <b><a +href="#humma">humma</a></b>. 3. One of the preferred <b><a href="#metasyntacticvariable">metasyntactic variable</a></b>s in +the UK, forming a series with <code>wobble</code>, +<code>wubble</code>, and <code>flob</code> (attributed to the +hilarious historical comedy "Blackadder"). 4. A pronounciation of +the letters "www", as seen in URLs; i.e., www.<b><a href="#foo">foo</a></b>.com may be pronounced "wibble dot foo dot com" +(compare <b><a href="#dubdubdub">dub dub dub</a></b>).</p> + +<p>The ancestral sense of this word is reported to have been "My +brain is packing it in now. I give up. <i>Tilt! Tilt! +Tilt!</i>"</p> + +<hr> +Node:<a name="WIBNI">WIBNI</a>, Next:<a rel="next" href="#widget">widget</a>, Previous:<a rel="previous" href="#wibble">wibble</a>, Up:<a rel="up" href="#chap23">= W +=</a> <br> + + +<p><b>WIBNI</b> // n.</p> + +<p>[Bell Labs: Wouldn't It Be Nice If] What most requirements +documents and specifications consist entirely of. Compare <b><a +href="#IWBNI">IWBNI</a></b>.</p> + +<hr> +Node:<a name="widget">widget</a>, Next:<a rel="next" href="#wiggles">wiggles</a>, Previous:<a rel="previous" href="#WIBNI">WIBNI</a>, Up:<a rel="up" href="#chap23">= W +=</a> <br> + + +<p><b>widget</b> n.</p> + +<p>1. A meta-thing. Used to stand for a real object in didactic +examples (especially database tutorials). Legend has it that the +original widgets were holders for buggy whips. "But suppose the +parts list for a widget has 52 entries<small>...</small>." 2. +[poss. evoking `window gadget'] A user interface object in <b><a +href="#X">X</a></b> graphical user interfaces.</p> + +<hr> +Node:<a name="wiggles">wiggles</a>, Next:<a rel="next" href="#WIMPenvironment">WIMP environment</a>, Previous:<a rel="previous" href="#widget">widget</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>wiggles</b> n.</p> + +<p>[scientific computation] In solving partial differential +equations by finite difference and similar methods, wiggles are +sawtooth (up-down-up-down) oscillations at the shortest +wavelength representable on the grid. If an algorithm is +unstable, this is often the most unstable waveform, so it grows +to dominate the solution. Alternatively, stable (though +inaccurate) wiggles can be generated near a discontinuity by a +Gibbs phenomenon.</p> + +<hr> +Node:<a name="WIMPenvironment">WIMP environment</a>, Next:<a +rel="next" href="#win">win</a>, Previous:<a rel="previous" href="#wiggles">wiggles</a>, Up:<a rel="up" href="#chap23">= W +=</a> <br> + + +<p><b>WIMP environment</b> n.</p> + +<p>[acronym: `Window, Icon, Menu, Pointing device (or Pull-down +menu)'] A graphical-user-interface environment such as <b><a +href="#X">X</a></b> or the Macintosh interface, esp. as described +by a hacker who prefers command-line interfaces for their +superior flexibility and extensibility. However, it is also used +without negative connotations; one must pay attention to voice +tone and other signals to interpret correctly. See <b><a href="#menuitis">menuitis</a></b>, <b><a href="#user-obsequious">user-obsequious</a></b>.</p> + +<hr> +Node:<a name="win">win</a>, Next:<a rel="next" href="#winbig">win big</a>, Previous:<a rel="previous" href="#WIMPenvironment">WIMP environment</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>win</b></p> + +<p>[MIT; now common everywhere] 1. vi. To succeed. A program wins +if no unexpected conditions arise, or (especially) if it +sufficiently <b><a href="#robust">robust</a></b> to take +exceptions in stride. 2. n. Success, or a specific instance +thereof. A pleasing outcome. "So it turned out I could use a +<b><a href="#lexer">lexer</a></b> generator instead of +hand-coding my own pattern recognizer. What a win!" Emphatic +forms: `moby win', `super win', `hyper-win' (often used +interjectively as a reply). For some reason `suitable win' is +also common at MIT, usually in reference to a satisfactory +solution to a problem. Oppose <b><a href="#lose">lose</a></b>; +see also <b><a href="#bigwin">big win</a></b>, which isn't +quite just an intensification of `win'.</p> + +<hr> +Node:<a name="winbig">win big</a>, Next:<a rel="next" href="#winwin">win win</a>, Previous:<a rel="previous" href="#win">win</a>, Up:<a rel="up" href="#chap23">= W =</a> +<br> + + +<p><b>win big</b> vi.</p> + +<p>To experience serendipity. "I went shopping and won big; there +was a 2-for-1 sale." See <b><a href="#bigwin">big +win</a></b>.</p> + +<hr> +Node:<a name="winwin">win win</a>, Next:<a rel="next" href="#Winchester">Winchester</a>, Previous:<a rel="previous" href="#winbig">win big</a>, Up:<a rel="up" href="#chap23">= +W =</a> <br> + + +<p><b>win win</b> excl.</p> + +<p>Expresses pleasure at a <b><a href="#win">win</a></b>.</p> + +<hr> +Node:<a name="Winchester">Winchester</a>, Next:<a rel="next" +href="#windoid">windoid</a>, Previous:<a rel="previous" href="#winwin">win win</a>, Up:<a rel="up" href="#chap23">= +W =</a> <br> + + +<p><b>Winchester</b> n.</p> + +<p>Informal generic term for sealed-enclosure magnetic-disk +drives in which the read-write head planes over the disk surface +on an air cushion. There is a legend that the name arose because +the original 1973 engineering prototype for what later became the +IBM 3340 featured two 30-megabyte volumes; 30-30 became +`Winchester' when somebody noticed the similarity to the common +term for a famous Winchester rifle (in the latter, the first 30 +referred to caliber and the second to the grain weight of the +charge). (It is sometimes incorrectly claimed that Winchester was +the laboratory in which the technology was developed.)</p> + +<hr> +Node:<a name="windoid">windoid</a>, Next:<a rel="next" href="#windowshopping">window shopping</a>, Previous:<a rel="previous" href="#Winchester">Winchester</a>, Up:<a rel="up" +href="#chap23">= W =</a> <br> + + +<p><b>windoid</b> n.</p> + +<p>In the Macintosh world, a style of window with much less +adornment (smaller or missing title bar, zoom box, etc, etc) than +a standard window.</p> + +<hr> +Node:<a name="windowshopping">window shopping</a>, Next:<a +rel="next" href="#Windoze">Windoze</a>, Previous:<a rel="previous" href="#windoid">windoid</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>window shopping</b> n.</p> + +<p>[US Geological Survey] Among users of <b><a href="#WIMPenvironment">WIMP environment</a></b>s like <b><a href="#X">X</a></b> or the Macintosh, extended experimentation with +new window colors, fonts, and icon shapes. This activity can take +up hours of what might otherwise have been productive working +time. "I spent the afternoon window shopping until I found the +coolest shade of green for my active window borders -- now they +perfectly match my medium slate blue background." Serious window +shoppers will spend their days with bitmap editors, creating new +and different icons and background patterns for all to see. Also: +`window dressing', the act of applying new fonts, colors, etc. +See <b><a href="#fritterware">fritterware</a></b>, compare <b><a +href="#macdink">macdink</a></b>.</p> + +<hr> +Node:<a name="Windoze">Windoze</a>, Next:<a rel="next" href="#wingedcomments">winged comments</a>, Previous:<a rel="previous" href="#windowshopping">window shopping</a>, Up:<a +rel="up" href="#chap23">= W =</a> <br> + + +<p><b>Windoze</b> /win'dohz/ n.</p> + +<p>See <b><a href="#MicroslothWindows">Microsloth +Windows</a></b>.</p> + +<hr> +Node:<a name="wingedcomments">winged comments</a>, Next:<a +rel="next" href="#winkey">winkey</a>, Previous:<a rel="previous" +href="#Windoze">Windoze</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>winged comments</b> n.</p> + +<p>Comments set on the same line as code, as opposed to <b><a +href="#boxedcomments">boxed comments</a></b>. In C, for +example:</p> + +<pre> +d = sqrt(x*x + y*y); /* distance from origin */ +</pre> + +<p>Generally these refer only to the action(s) taken on that +line.</p> + +<hr> +Node:<a name="winkey">winkey</a>, Next:<a rel="next" href="#winnage">winnage</a>, Previous:<a rel="previous" href="#wingedcomments">winged comments</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>winkey</b> n.</p> + +<p>(alt. `winkey face') See <b><a href="#emoticon">emoticon</a></b>.</p> + +<hr> +Node:<a name="winnage">winnage</a>, Next:<a rel="next" href="#winner">winner</a>, Previous:<a rel="previous" href="#winkey">winkey</a>, Up:<a rel="up" href="#chap23">= W +=</a> <br> + + +<p><b>winnage</b> /win'*j/ n.</p> + +<p>The situation when a lossage is corrected, or when something +is winning.</p> + +<hr> +Node:<a name="winner">winner</a>, Next:<a rel="next" href="#winnitude">winnitude</a>, Previous:<a rel="previous" href="#winnage">winnage</a>, Up:<a rel="up" href="#chap23">= W +=</a> <br> + + +<p><b>winner</b></p> + +<p>1. n. An unexpectedly good situation, program, programmer, or +person. 2. `real winner': Often sarcastic, but also used as high +praise (see also the note under <b><a href="#user">user</a></b>). +"He's a real winner -- never reports a bug till he can duplicate +it and send in an example."</p> + +<hr> +Node:<a name="winnitude">winnitude</a>, Next:<a rel="next" href="#Wintel">Wintel</a>, Previous:<a rel="previous" href="#winner">winner</a>, Up:<a rel="up" href="#chap23">= W +=</a> <br> + + +<p><b>winnitude</b> /win'*-t[y]ood/ n.</p> + +<p>The quality of winning (as opposed to <b><a href="#winnage">winnage</a></b>, which is the result of winning). +"Guess what? They tweaked the microcode and now the LISP +interpreter runs twice as fast as it used to." "That's really +great! Boy, what winnitude!" "Yup. I'll probably get a +half-hour's winnage on the next run of my program." Perhaps +curiously, the obvious antonym `lossitude' is rare.</p> + +<hr> +Node:<a name="Wintel">Wintel</a>, Next:<a rel="next" href="#wired">wired</a>, Previous:<a rel="previous" href="#winnitude">winnitude</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>Wintel</b> n.</p> + +<p>Microsoft Windows plus Intel - the tacit alliance that +dominated desktop computing in the 1990s. Now (1999) possibly on +the verge of breaking up under pressure from <b><a href="#Linux">Linux</a></b>; see <b><a href="#Lintel">Lintel</a></b>.</p> + +<hr> +Node:<a name="wired">wired</a>, Next:<a rel="next" href="#wirehead">wirehead</a>, Previous:<a rel="previous" href="#Wintel">Wintel</a>, Up:<a rel="up" href="#chap23">= W +=</a> <br> + + +<p><b>wired</b> n.</p> + +<p>See <b><a href="#hardwired">hardwired</a></b>.</p> + +<hr> +Node:<a name="wirehead">wirehead</a>, Next:<a rel="next" href="#wirewater">wirewater</a>, Previous:<a rel="previous" href="#wired">wired</a>, Up:<a rel="up" href="#chap23">= W +=</a> <br> + + +<p><b>wirehead</b> /wi:r'hed/ n.</p> + +<p>[prob. from SF slang for an electrical-brain-stimulation +addict] 1. A hardware hacker, especially one who concentrates on +communications hardware. 2. An expert in local-area networks. A +wirehead can be a network software wizard too, but will always +have the ability to deal with network hardware, down to the +smallest component. Wireheads are known for their ability to lash +up an Ethernet terminator from spare resistors, for example.</p> + +<hr> +Node:<a name="wirewater">wirewater</a>, Next:<a rel="next" href="#wishlist">wish list</a>, Previous:<a rel="previous" href="#wirehead">wirehead</a>, Up:<a rel="up" href="#chap23">= +W =</a> <br> + + +<p><b>wirewater</b> n.</p> + +<p>Syn. <b><a href="#programmingfluid">programming +fluid</a></b>. This melds the mainstream slang adjective `wired' +(stimulated, up, hyperactive) with `firewater'; however, it +refers to caffeinacious rather than alcoholic beverages.</p> + +<hr> +Node:<a name="wishlist">wish list</a>, Next:<a rel="next" +href="#withindeltaof">within delta of</a>, Previous:<a rel="previous" href="#wirewater">wirewater</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>wish list</b> n.</p> + +<p>A list of desired features or bug fixes that probably won't +get done for a long time, usually because the person responsible +for the code is too busy or can't think of a clean way to do it. +"OK, I'll add automatic filename completion to the wish list for +the new interface." Compare <b><a href="#ticklistfeatures">tick-list features</a></b>.</p> + +<hr> +Node:<a name="withindeltaof">within delta of</a>, Next:<a +rel="next" href="#withinepsilonof">within epsilon of</a>, +Previous:<a rel="previous" href="#wishlist">wish list</a>, +Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>within delta of</b> adj.</p> + +<p>See <b><a href="#delta">delta</a></b>.</p> + +<hr> +Node:<a name="withinepsilonof">within epsilon of</a>, +Next:<a rel="next" href="#wizard">wizard</a>, Previous:<a rel="previous" href="#withindeltaof">within delta of</a>, Up:<a +rel="up" href="#chap23">= W =</a> <br> + + +<p><b>within epsilon of</b> adj.</p> + +<p>See <b><a href="#epsilon">epsilon</a></b>.</p> + +<hr> +Node:<a name="wizard">wizard</a>, Next:<a rel="next" href="#WizardBook">Wizard Book</a>, Previous:<a rel="previous" +href="#withinepsilonof">within epsilon of</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>wizard</b> n.</p> + +<p>1. Transitively, a person who knows how a complex piece of +software or hardware works (that is, who <b><a href="#grok">grok</a></b>s it); esp. someone who can find and fix bugs +quickly in an emergency. Someone is a <b><a href="#hacker">hacker</a></b> if he or she has general hacking +ability, but is a wizard with respect to something only if he or +she has specific detailed knowledge of that thing. A good hacker +could become a wizard for something given the time to study it. +2. The term `wizard' is also used intransitively of someone who +has extremely high-level hacking or problem-solving ability. 3. A +person who is permitted to do things forbidden to ordinary +people; one who has <b><a href="#wheel">wheel</a></b> privileges +on a system. 4. A Unix expert, esp. a Unix systems programmer. +This usage is well enough established that `Unix Wizard' is a +recognized job title at some corporations and to most +headhunters. See <b><a href="#guru">guru</a></b>, <b><a href="#lordhighfixer">lord high fixer</a></b>. See also <b><a +href="#deepmagic">deep magic</a></b>, <b><a href="#heavywizardry">heavy wizardry</a></b>, <b><a href="#incantation">incantation</a></b>, <b><a href="#magic">magic</a></b>, <b><a href="#mutter">mutter</a></b>, +<b><a href="#raindance">rain dance</a></b>, <b><a href="#voodooprogramming">voodoo programming</a></b>, <b><a href="#waveadeadchicken">wave a dead chicken</a></b>.</p> + +<hr> +Node:<a name="WizardBook">Wizard Book</a>, Next:<a rel="next" +href="#wizardhat">wizard hat</a>, Previous:<a rel="previous" +href="#wizard">wizard</a>, Up:<a rel="up" href="#chap23">= +W =</a> <br> + + +<p><b>Wizard Book</b> n.</p> + +<p>"Structure and Interpretation of Computer Programs" (Hal +Abelson, Jerry Sussman and Julie Sussman; MIT Press, 1984, 1996; +ISBN 0-262-01153-0), an excellent computer science text used in +introductory courses at MIT. So called because of the wizard on +the jacket. One of the <b><a href="#bible">bible</a></b>s of the +LISP/Scheme world. Also, less commonly, known as the <b><a href="#PurpleBook">Purple Book</a></b>.</p> + +<hr> +Node:<a name="wizardhat">wizard hat</a>, Next:<a rel="next" +href="#wizardmode">wizard mode</a>, Previous:<a rel="previous" +href="#WizardBook">Wizard Book</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>wizard hat</b> n.</p> + +<p>[also, after Terry Pratchett, `pointy hat'] Notional headgear +worn by whoever is the <b><a href="#wizard">wizard</a></b> in a +particular context. The implication is that it's a transferable +role. "Talk to Alice, she's wearing the TCP/IP wizard hat while +Bob is on vacation." This metaphor is sufficiently live that one +may actually see hackers miming the act of putting on, taking +off, or transferring a phantom hat. Compare <b><a href="#patchpumpkin">patch pumpkin</a></b>.</p> + +<hr> +Node:<a name="wizardmode">wizard mode</a>, Next:<a rel="next" +href="#wizardly">wizardly</a>, Previous:<a rel="previous" href="#wizardhat">wizard hat</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>wizard mode</b> n.</p> + +<p>[from <b><a href="#rogue">rogue</a></b>] A special access mode +of a program or system, usually passworded, that permits some +users godlike privileges. Generally not used for operating +systems themselves (`root mode' or `wheel mode' would be used +instead). This term is often used with respect to games that have +editable state.</p> + +<hr> +Node:<a name="wizardly">wizardly</a>, Next:<a rel="next" href="#wok-on-the-wall">wok-on-the-wall</a>, Previous:<a rel="previous" href="#wizardmode">wizard mode</a>, Up:<a rel="up" +href="#chap23">= W =</a> <br> + + +<p><b>wizardly</b> adj.</p> + +<p>Pertaining to wizards. A wizardly <b><a href="#feature">feature</a></b> is one that only a wizard could +understand or use properly.</p> + +<hr> +Node:<a name="wok-on-the-wall">wok-on-the-wall</a>, Next:<a rel="next" href="#wombbox">womb box</a>, Previous:<a rel="previous" href="#wizardly">wizardly</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>wok-on-the-wall</b> n.</p> + +<p>A small microwave dish antenna used for cross-campus private +network circuits, from the obvious resemblance between a +microwave dish and the Chinese culinary utensil.</p> + +<hr> +Node:<a name="wombbox">womb box</a>, Next:<a rel="next" href="#WOMBAT">WOMBAT</a>, Previous:<a rel="previous" href="#wok-on-the-wall">wok-on-the-wall</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>womb box</b> n.</p> + +<p>1. [TMRC] Storage space for equipment. 2. [proposed] A variety +of hard-shell equipment case with heavy interior padding and/or +shaped carrier cutouts in a foam-rubber matrix; mundanely called +a `flight case'. Used for delicate test equipment, electronics, +and musical instruments.</p> + +<hr> +Node:<a name="WOMBAT">WOMBAT</a>, Next:<a rel="next" href="#womble">womble</a>, Previous:<a rel="previous" href="#wombbox">womb box</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>WOMBAT</b> /wom'bat/ adj.</p> + +<p>[acronym: Waste Of Money, Brains, And Time] Applied to +problems which are both profoundly <b><a href="#uninteresting">uninteresting</a></b> in themselves and unlikely +to benefit anyone interesting even if solved. Often used in +fanciful constructions such as `wrestling with a wombat'. See +also <b><a href="#crawlinghorror">crawling horror</a></b>, +<b><a href="#SMOP">SMOP</a></b>. Also note the rather different +usage as a metasyntactic variable in <b><a href="#CommonwealthHackish">Commonwealth Hackish</a></b>.</p> + +<p>Users of the PDP-11 database program DATATRIEVE adopted the +wombat as their notional mascot; the program's help file +responded to "HELP WOMBAT" with factual information about Real +World wombats.</p> + +<hr> +Node:<a name="womble">womble</a>, Next:<a rel="next" href="#wonky">wonky</a>, Previous:<a rel="previous" href="#WOMBAT">WOMBAT</a>, Up:<a rel="up" href="#chap23">= W +=</a> <br> + + +<p><b>womble</b> n.</p> + +<p>[Unisys UK: from British animated characters] A user who has +great difficulty in communicating their requirements and/or in +using the resulting software. Extreme case of <b><a href="#luser">luser</a></b>. An especially senior or high-ranking +womble is referred to as Great-Uncle Bulgaria.</p> + +<hr> +Node:<a name="wonky">wonky</a>, Next:<a rel="next" href="#woofer">woofer</a>, Previous:<a rel="previous" href="#womble">womble</a>, Up:<a rel="up" href="#chap23">= W +=</a> <br> + + +<p><b>wonky</b> /wong'kee/ adj.</p> + +<p>[from Australian slang] Yet another approximate synonym for +<b><a href="#broken">broken</a></b>. Specifically connotes a +malfunction that produces behavior seen as crazy, humorous, or +amusingly perverse. "That was the day the printer's font logic +went wonky and everybody's listings came out in Tengwar." Also in +`wonked out'. See <b><a href="#funky">funky</a></b>, <b><a href="#demented">demented</a></b>, <b><a href="#bozotic">bozotic</a></b>.</p> + +<hr> +Node:<a name="woofer">woofer</a>, Next:<a rel="next" href="#workaround">workaround</a>, Previous:<a rel="previous" href="#wonky">wonky</a>, Up:<a rel="up" href="#chap23">= W +=</a> <br> + + +<p><b>woofer</b> n.</p> + +<p>[University of Waterloo] Some varieties of wide paper for +printers have a perforation 8.5 inches from the left margin that +allows the excess on the right-hand side to be torn off when the +print format is 80 columns or less wide. The right-hand excess +may be called `woofer'. This term (like <b><a href="#tweeter">tweeter</a></b>) has been in use at Waterloo since +1972, but is elsewhere unknown. In audio jargon, the word refers +to the bass speaker(s) on a hi-fi.</p> + +<hr> +Node:<a name="workaround">workaround</a>, Next:<a rel="next" +href="#workingasdesigned">working as designed</a>, +Previous:<a rel="previous" href="#woofer">woofer</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>workaround</b> n.</p> + +<p>1. A temporary <b><a href="#kluge">kluge</a></b> used to +bypass, mask, or otherwise avoid a <b><a href="#bug">bug</a></b> +or <b><a href="#misfeature">misfeature</a></b> in some system. +Theoretically, workarounds are always replaced by <b><a href="#fix">fix</a></b>es; in practice, customers often find +themselves living with workarounds for long periods of time. "The +code died on NUL characters in the input, so I fixed it to +interpret them as spaces." "That's not a fix, that's a +workaround!" 2. A procedure to be employed by the user in order +to do what some currently non-working feature should do. +Hypothetical example: "Using META-F7 <b><a href="#crash">crash</a></b>es the 4.43 build of Weemax, but as a +workaround you can type CTRL-R, then SHIFT-F5, and delete the +remaining <b><a href="#cruft">cruft</a></b> by hand."</p> + +<hr> +Node:<a name="workingasdesigned">working as designed</a>, +Next:<a rel="next" href="#worm">worm</a>, Previous:<a rel="previous" href="#workaround">workaround</a>, Up:<a rel="up" +href="#chap23">= W =</a> <br> + + +<p><b>working as designed</b> adj.</p> + +<p>[IBM] 1. In conformance to a wrong or inappropriate +specification; useful, but misdesigned. 2. Frequently used as a +sardonic comment on a program's utility. 3. Unfortunately also +used as a bogus reason for not accepting a criticism or +suggestion. At <b><a href="#IBM">IBM</a></b>, this sense is used +in official documents! See <b><a href="#BAD">BAD</a></b>.</p> + +<hr> +Node:<a name="worm">worm</a>, Next:<a rel="next" href="#wormhole">wormhole</a>, Previous:<a rel="previous" href="#workingasdesigned">working as designed</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>worm</b> n.</p> + +<p>[from `tapeworm' in John Brunner's novel "The Shockwave +Rider", via XEROX PARC] A program that propagates itself over a +network, reproducing itself as it goes. Compare <b><a href="#virus">virus</a></b>. Nowadays the term has negative +connotations, as it is assumed that only <b><a href="#cracker">cracker</a></b>s write worms. Perhaps the best-known +example was Robert T. Morris's <b><a href="#GreatWorm">Great +Worm</a></b> of 1988, a `benign' one that got out of control and +hogged hundreds of Suns and VAXen across the U.S. See also <b><a +href="#cracker">cracker</a></b>, <b><a href="#RTM">RTM</a></b>, +<b><a href="#Trojanhorse">Trojan horse</a></b>, <b><a href="#ice">ice</a></b>.</p> + +<hr> +Node:<a name="wormhole">wormhole</a>, Next:<a rel="next" href="#woundaroundtheaxle">wound around the axle</a>, +Previous:<a rel="previous" href="#worm">worm</a>, Up:<a rel="up" +href="#chap23">= W =</a> <br> + + +<p><b>wormhole</b> /werm'hohl/ n.</p> + +<p>[from the `wormhole' singularities hypothesized in some +versions of General Relativity theory] 1. [n.,obs.] A location in +a monitor which contains the address of a routine, with the +specific intent of making it easy to substitute a different +routine. This term is now obsolescent; modern operating systems +use clusters of wormholes extensively (for modularization of I/O +handling in particular, as in the Unix device-driver +organization) but the preferred techspeak for these clusters is +`device tables', `jump tables' or `capability tables'. 2. +[Amateur Packet Radio] A network path using a commercial +satellite link to join two or more amateur VHF networks. So +called because traffic routed through a wormhole leaves and +re-enters the amateur network over great distances with usually +little clue in the message routing header as to how it got from +one relay to the other. Compare <b><a href="#gopherhole">gopher hole</a></b> (sense 2).</p> + +<hr> +Node:<a name="woundaroundtheaxle">wound around the +axle</a>, Next:<a rel="next" href="#wrapAround">wrap +around</a>, Previous:<a rel="previous" href="#wormhole">wormhole</a>, Up:<a rel="up" href="#chap23">= +W =</a> <br> + + +<p><b>wound around the axle</b> adj.</p> + +<p>In an infinite loop. Often used by older computer types.</p> + +<hr> +Node:<a name="wrapAround">wrap around</a>, Next:<a rel="next" +href="#writeonlycode">write-only code</a>, Previous:<a rel="previous" href="#woundaroundtheaxle">wound around the +axle</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>wrap around</b> vi.</p> + +<p>(also n. `wraparound' and v. shorthand `wrap') 1. [techspeak] +The action of a counter that starts over at zero or at `minus +infinity' (see <b><a href="#infinity">infinity</a></b>) after its +maximum value has been reached, and continues incrementing, +either because it is programmed to do so or because of an +overflow (as when a car's odometer starts over at 0). 2. To +change <b><a href="#phase">phase</a></b> gradually and +continuously by maintaining a steady wake-sleep cycle somewhat +longer than 24 hours, e.g., living six long (28-hour) days in a +week (or, equivalently, sleeping at the rate of 10 microhertz). +This sense is also called <b><a href="#phase-wrapping">phase-wrapping</a></b>.</p> + +<hr> +Node:<a name="writeonlycode">write-only code</a>, Next:<a +rel="next" href="#writeonlylanguage">write-only language</a>, +Previous:<a rel="previous" href="#wrapAround">wrap around</a>, +Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>write-only code</b> n.</p> + +<p>[a play on `read-only memory'] Code so arcane, complex, or +ill-structured that it cannot be modified or even comprehended by +anyone but its author, and possibly not even by him/her. A <b><a +href="#BadThing">Bad Thing</a></b>.</p> + +<hr> +Node:<a name="writeonlylanguage">write-only language</a>, +Next:<a rel="next" href="#write-onlymemory">write-only +memory</a>, Previous:<a rel="previous" href="#writeonlycode">write-only code</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>write-only language</b> n.</p> + +<p>A language with syntax (or semantics) sufficiently dense and +bizarre that any routine of significant size is automatically +<b><a href="#writeonlycode">write-only code</a></b>. A +sobriquet applied occasionally to C and often to APL, though +<b><a href="#INTERCAL">INTERCAL</a></b> and <b><a href="#TECO">TECO</a></b> certainly deserve it more. See also <b><a +href="#Befunge">Befunge</a></b>.</p> + +<hr> +Node:<a name="write-onlymemory">write-only memory</a>, Next:<a +rel="next" href="#WrongThing">Wrong Thing</a>, Previous:<a +rel="previous" href="#writeonlylanguage">write-only +language</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>write-only memory</b> n.</p> + +<p>The obvious antonym to `read-only memory'. Out of frustration +with the long and seemingly useless chain of approvals required +of component specifications, during which no actual checking +seemed to occur, an engineer at Signetics once created a +specification for a write-only memory and included it with a +bunch of other specifications to be approved. This inclusion came +to the attention of Signetics <b><a href="#management">management</a></b> only when regular customers +started calling and asking for pricing information. Signetics +published a corrected edition of the data book and requested the +return of the `erroneous' ones. Later, in 1972, Signetics bought +a double-page spread in "Electronics" magazine's April issue and +used the spec as an April Fools' Day joke. Instead of the more +conventional characteristic curves, the 25120 "fully encoded, +9046 x N, Random Access, write-only-memory" data sheet included +diagrams of "bit capacity vs. Temp.", "Iff vs. Vff", "Number of +pins remaining vs. number of socket insertions", and "AQL vs. +selling price". The 25120 required a 6.3 VAC VFF supply, a +10V +VCC, and VDD of 0V, +/- 2%.</p> + +<hr> +Node:<a name="WrongThing">Wrong Thing</a>, Next:<a rel="next" +href="#wuggawugga">wugga wugga</a>, Previous:<a rel="previous" +href="#write-onlymemory">write-only memory</a>, Up:<a rel="up" +href="#chap23">= W =</a> <br> + + +<p><b>Wrong Thing</b> n.</p> + +<p>A design, action, or decision that is clearly incorrect or +inappropriate. Often capitalized; always emphasized in speech as +if capitalized. The opposite of the <b><a href="#RightThing">Right Thing</a></b>; more generally, anything +that is not the Right Thing. In cases where `the good is the +enemy of the best', the merely good -- although good -- is +nevertheless the Wrong Thing. "In C, the default is for +module-level declarations to be visible everywhere, rather than +just within the module. This is clearly the Wrong Thing."</p> + +<hr> +Node:<a name="wuggawugga">wugga wugga</a>, Next:<a rel="next" +href="#wumpus">wumpus</a>, Previous:<a rel="previous" href="#WrongThing">Wrong Thing</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>wugga wugga</b> /wuh'g* wuh'g*/ n.</p> + +<p>Imaginary sound that a computer program makes as it labors +with a tedious or difficult task.<b><a href="#grind">grind</a></b> (sense 4).</p> + +<hr> +Node:<a name="wumpus">wumpus</a>, Next:<a rel="next" href="#WYSIAYG">WYSIAYG</a>, Previous:<a rel="previous" href="#wuggawugga">wugga wugga</a>, Up:<a rel="up" href="#chap23">= W =</a> <br> + + +<p><b>wumpus</b> /wuhm'p*s/ n.</p> + +<p>The central monster (and, in many versions, the name) of a +famous family of very early computer games called "Hunt The +Wumpus'. The original was invented in 1970 (several years before +<b><a href="#ADVENT">ADVENT</a></b>) by Gregory Yob. The wumpus +lived somewhere in a cave with the topology of an dodecahedron's +edge/vertex graph (later versions supported other topologies, +including an icosahedron and Möbius strip). The player +started somewhere at random in the cave with five `crooked +arrows'; these could be shot through up to three connected rooms, +and would kill the wumpus on a hit (later versions introduced the +wounded wumpus, which got very angry). Unfortunately for players, +the movement necessary to map the maze was made hazardous not +merely by the wumpus (which would eat you if you stepped on him) +but also by bottomless pits and colonies of super bats that would +pick you up and drop you at a random location (later versions +added `anaerobic termites' that ate arrows, bat migrations, and +earthquakes that randomly changed pit locations).</p> + +<p>This game appears to have been the first to use a non-random +graph-structured map (as opposed to a rectangular grid like the +even older Star Trek games). In this respect, as in the +dungeon-like setting and its terse, amusing messages, it +prefigured <b><a href="#ADVENT">ADVENT</a></b> and <b><a href="#Zork">Zork</a></b> and was directly ancestral to the latter +(Zork acknowledged this heritage by including a super-bat +colony). A C emulation of the original Basic game is available at +the Retrocomputing Museum, http://www.ccil.org/retro.</p> + +<hr> +Node:<a name="WYSIAYG">WYSIAYG</a>, Next:<a rel="next" href="#WYSIWYG">WYSIWYG</a>, Previous:<a rel="previous" href="#wumpus">wumpus</a>, Up:<a rel="up" href="#chap23">= W +=</a> <br> + + +<p><b>WYSIAYG</b> /wiz'ee-ayg/ adj.</p> + +<p>Describes a user interface under which "What You See Is +<i>All</i> You Get"; an unhappy variant of <b><a href="#WYSIWYG">WYSIWYG</a></b>. Visual, `point-and-shoot'-style +interfaces tend to have easy initial learning curves, but also to +lack depth; they often frustrate advanced users who would be +better served by a command-style interface. When this happens, +the frustrated user has a WYSIAYG problem. This term is most +often used of editors, word processors, and document formatting +programs. WYSIWYG `desktop publishing' programs, for example, are +a clear win for creating small documents with lots of fonts and +graphics in them, especially things like newsletters and +presentation slides. When typesetting book-length manuscripts, on +the other hand, scale changes the nature of the task; one quickly +runs into WYSIAYG limitations, and the increased power and +flexibility of a command-driven formatter like <b><a href="#TeX">TeX</a></b> or Unix's <b><a href="#troff">troff</a></b> +becomes not just desirable but a necessity. Compare <b><a href="#YAFIYGI">YAFIYGI</a></b>.</p> + +<hr> +Node:<a name="WYSIWYG">WYSIWYG</a>, Next:<a rel="next" href="#X">X</a>, Previous:<a rel="previous" href="#WYSIAYG">WYSIAYG</a>, Up:<a rel="up" href="#chap23">= W +=</a> <br> + + +<p><b>WYSIWYG</b> /wiz'ee-wig/ adj.</p> + +<p>[Traced to Flip Wilson's "Geraldine" character c.1970] +Describes a user interface under which "What You See Is What You +Get", as opposed to one that uses more-or-less obscure commands +that do not result in immediate visual feedback. True WYSIWYG in +environments supporting multiple fonts or graphics is a a +rarely-attained ideal; there are variants of this term to express +real-world manifestations including WYSIAWYG (What You See Is +<i>Almost</i> What You Get) and WYSIMOLWYG (What You See Is +More or Less What You Get). All these can be mildly derogatory, +as they are often used to refer to dumbed-down <b><a href="#user-friendly">user-friendly</a></b> interfaces targeted at +non-programmers; a hacker has no fear of obscure commands +(compare <b><a href="#WYSIAYG">WYSIAYG</a></b>). On the other +hand, <b><a href="#EMACS">EMACS</a></b> was one of the very first +WYSIWYG editors, replacing (actually, at first overlaying) the +extremely obscure, command-based <b><a href="#TECO">TECO</a></b>. +See also <b><a href="#WIMPenvironment">WIMP +environment</a></b>. [Oddly enough, WYSIWYG has already made it +into the OED, in lower case yet. --ESR]</p> + +<hr> +Node:<a name="chap24">= X =</a>, Next:<a rel="next" href="#chap25">= Y =</a>, Previous:<a rel="previous" href="#chap23">= W =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= X =</h2> + +<ul> +<li><a href="#X">X</a>:</li> + +<li><a href="#XEROXPARC">XEROX PARC</a>:</li> + +<li><a href="#XOFF">XOFF</a>:</li> + +<li><a href="#XON">XON</a>:</li> + +<li><a href="#xor">xor</a>:</li> + +<li><a href="#xref">xref</a>:</li> + +<li><a href="#XXX">XXX</a>:</li> + +<li><a href="#xyzzy">xyzzy</a>:</li> +</ul> + +<hr> +Node:<a name="X">X</a>, Next:<a rel="next" href="#XEROXPARC">XEROX PARC</a>, Previous:<a rel="previous" href="#WYSIWYG">WYSIWYG</a>, Up:<a rel="up" href="#chap24">= X +=</a> <br> + + +<p><b>X</b> /X/ n.</p> + +<p>1. Used in various speech and writing contexts (also in +lowercase) in roughly its algebraic sense of `unknown within a +set defined by context' (compare <b><a href="#N">N</a></b>). +Thus, the abbreviation 680x0 stands for 68000, 68010, 68020, +68030, or 68040, and 80x86 stands for 80186, 80286, 80386, 80486, +80586 or 80686 (note that a Unix hacker might write these as +680[0-6]0 and 80[1-6]86 or 680?0 and 80?86 respectively; see +<b><a href="#glob">glob</a></b>). 2. [after the name of an +earlier window system called `W'] An over-sized, over-featured, +over-engineered and incredibly over-complicated window system +developed at MIT and widely used on Unix systems.</p> + +<hr> +Node:<a name="XEROXPARC">XEROX PARC</a>, Next:<a rel="next" +href="#XOFF">XOFF</a>, Previous:<a rel="previous" href="#X">X</a>, Up:<a rel="up" href="#chap24">= X =</a> <br> + + +<p><b>XEROX PARC</b> /zee'roks park'/ n.</p> + +<p>The famed Palo Alto Research Center. For more than a decade, +from the early 1970s into the mid-1980s, PARC yielded an +astonishing volume of groundbreaking hardware and software +innovations. The modern mice, windows, and icons style of +software interface was invented there. So was the laser printer +and the local-area network; and PARC's series of D machines +anticipated the powerful personal computers of the 1980s by a +decade. Sadly, the prophets at PARC were without honor in their +own company, so much so that it became a standard joke to +describe PARC as a place that specialized in developing brilliant +ideas for everyone else.</p> + +<p>The stunning shortsightedness and obtusity of XEROX's +top-level <b><a href="#suit">suit</a></b>s has been well +anatomized in "Fumbling The Future: How XEROX Invented, Then +Ignored, the First Personal Computer" by Douglas K. Smith and +Robert C. Alexander (William Morrow & Co., 1988, ISBN +0-688-09511-9).</p> + +<hr> +Node:<a name="XOFF">XOFF</a>, Next:<a rel="next" href="#XON">XON</a>, Previous:<a rel="previous" href="#XEROXPARC">XEROX PARC</a>, Up:<a rel="up" href="#chap24">= X =</a> <br> + + +<p><b>XOFF</b> /X-of/ n.</p> + +<p>Syn. <b><a href="#control-S">control-S</a></b>.</p> + +<hr> +Node:<a name="XON">XON</a>, Next:<a rel="next" href="#xor">xor</a>, Previous:<a rel="previous" href="#XOFF">XOFF</a>, +Up:<a rel="up" href="#chap24">= X =</a> <br> + + +<p><b>XON</b> /X-on/ n.</p> + +<p>Syn. <b><a href="#control-Q">control-Q</a></b>.</p> + +<hr> +Node:<a name="xor">xor</a>, Next:<a rel="next" href="#xref">xref</a>, Previous:<a rel="previous" href="#XON">XON</a>, +Up:<a rel="up" href="#chap24">= X =</a> <br> + + +<p><b>xor</b> /X'or/, /kzor/ conj.</p> + +<p>Exclusive or. `A xor B' means `A or B, but not both'. "I want +to get cherry pie xor a banana split." This derives from the +technical use of the term as a function on truth-values that is +true if exactly one of its two arguments is true.</p> + +<hr> +Node:<a name="xref">xref</a>, Next:<a rel="next" href="#XXX">XXX</a>, Previous:<a rel="previous" href="#xor">xor</a>, +Up:<a rel="up" href="#chap24">= X =</a> <br> + + +<p><b>xref</b> /X'ref/ v.,n.</p> + +<p>Hackish standard abbreviation for `cross-reference'.</p> + +<hr> +Node:<a name="XXX">XXX</a>, Next:<a rel="next" href="#xyzzy">xyzzy</a>, Previous:<a rel="previous" href="#xref">xref</a>, Up:<a rel="up" href="#chap24">= X =</a> +<br> + + +<p><b>XXX</b> /X-X-X/ n.</p> + +<p>A marker that attention is needed. Commonly used in program +comments to indicate areas that are kluged up or need to be. Some +hackers liken `XXX' to the notional heavy-porn movie rating. +Compare <b><a href="#FIXME">FIXME</a></b>.</p> + +<hr> +Node:<a name="xyzzy">xyzzy</a>, Next:<a rel="next" href="#YA-">YA-</a>, Previous:<a rel="previous" href="#XXX">XXX</a>, +Up:<a rel="up" href="#chap24">= X =</a> <br> + + +<p><b>xyzzy</b> /X-Y-Z-Z-Y/, /X-Y-ziz'ee/, /ziz'ee/, or +/ik-ziz'ee/ adj.</p> + +<p>[from the ADVENT game] The <b><a href="#canonical">canonical</a></b> `magic word'. This comes from +<b><a href="#ADVENT">ADVENT</a></b>, in which the idea is to +explore an underground cave with many rooms and to collect the +treasures you find there. If you type `xyzzy' at the appropriate +time, you can move instantly between two otherwise distant +points. If, therefore, you encounter some bit of <b><a href="#magic">magic</a></b>, you might remark on this quite succinctly +by saying simply "Xyzzy!" "Ordinarily you can't look at someone +else's screen if he has protected it, but if you type +quadruple-bucky-clear the system will let you do it anyway." +"Xyzzy!" It's traditional for xyzzy to be an <b><a href="#Easteregg">Easter egg</a></b> in games with text +interfaces.</p> + +<p>Xyzzy has actually been implemented as an undocumented no-op +command on several OSes; in Data General's AOS/VS, for example, +it would typically respond "Nothing happens", just as <b><a href="#ADVENT">ADVENT</a></b> did if the magic was invoked at the +wrong spot or before a player had performed the action that +enabled the word. In more recent 32-bit versions, by the way, +AOS/VS responds "Twice as much happens".</p> + +<p>Early versions of the popular `minesweeper' game under +Microsoft Windows had a cheat mode triggered by the command +`xyzzy<enter><right-shift>' that turns the top-left +pixel of the screen different colors depending on whether or not +the cursor is over a bomb. This feature temporarily diasappeared +in Windows 98, but reappeared in Windows 2000.</p> + +<p>The following passage from "The Wonderful Wizard of Oz" by L. +Frank Baum, suggesting a possible pre-ADVENT origin, has recently +come to light:</p> + +<p>"Ziz-zy, zuz-zy, zik!" said Dorothy, who was now standing on +both feet. This ended the saying of the charm, and they heard a +great chattering and flapping of wings, as the band of Winged +Monkeys flew up to them.</p> + +<hr> +Node:<a name="chap25">= Y =</a>, Next:<a rel="next" href="#chap26">= Z =</a>, Previous:<a rel="previous" href="#chap24">= X =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= Y =</h2> + +<ul> +<li><a href="#YA-">YA-</a>:</li> + +<li><a href="#YABA">YABA</a>:</li> + +<li><a href="#YAFIYGI">YAFIYGI</a>:</li> + +<li><a href="#YAUN">YAUN</a>:</li> + +<li><a href="#YellowBook">Yellow Book</a>:</li> + +<li><a href="#yellowcard">yellow card</a>:</li> + +<li><a href="#yellowwire">yellow wire</a>:</li> + +<li><a href="#YetAnother">Yet Another</a>:</li> + +<li><a href="#YHBT">YHBT</a>:</li> + +<li><a href="#YKYBHTLW">YKYBHTLW</a>:</li> + +<li><a href="#YMMV">YMMV</a>:</li> + +<li><a href="#Youarenotexpectedtounderstandthis">You are not expected to understand this</a>:</li> + +<li><a href="#Youknowyouvebeenhackingtoolongwhen">You know you've been hacking too long when</a>:</li> + +<li><a href="#Yourmileagemayvary">Your mileage may vary</a>:</li> + +<li><a href="#Yowx">Yow!</a>:</li> + +<li><a href="#yoyomode">yoyo mode</a>:</li> + +<li><a href="#YuShiangWholeFish">Yu-Shiang Whole Fish</a>:</li> +</ul> + +<hr> +Node:<a name="YA-">YA-</a>, Next:<a rel="next" href="#YABA">YABA</a>, Previous:<a rel="previous" href="#xyzzy">xyzzy</a>, Up:<a rel="up" href="#chap25">= Y +=</a> <br> + + +<p><b>YA-</b> abbrev.</p> + +<p>[Yet Another] In hackish acronyms this almost invariably +expands to <b><a href="#YetAnother">Yet Another</a></b>, +following the precedent set by Unix <code>yacc(1)</code> (Yet +Another Compiler-Compiler). See <b><a href="#YABA">YABA</a></b>.</p> + +<hr> +Node:<a name="YABA">YABA</a>, Next:<a rel="next" href="#YAFIYGI">YAFIYGI</a>, Previous:<a rel="previous" href="#YA-">YA-</a>, Up:<a rel="up" href="#chap25">= Y =</a> +<br> + + +<p><b>YABA</b> /ya'b*/ n.</p> + +<p>[Cambridge] Yet Another Bloody Acronym. Whenever some program +is being named, someone invariably suggests that it be given a +name that is acronymic. The response from those with a trace of +originality is to remark ironically that the proposed name would +then be `YABA-compatible'. Also used in response to questions +like "What is WYSIWYG?" See also <b><a href="#TLA">TLA</a></b>.</p> + +<hr> +Node:<a name="YAFIYGI">YAFIYGI</a>, Next:<a rel="next" href="#YAUN">YAUN</a>, Previous:<a rel="previous" href="#YABA">YABA</a>, Up:<a rel="up" href="#chap25">= Y =</a> +<br> + + +<p><b>YAFIYGI</b> /yaf'ee-y*-gee/ adj.</p> + +<p>[coined in response to WYSIWYG] Describes the command-oriented +ed/vi/nroff/TeX style of word processing or other user interface, +the opposite of <b><a href="#WYSIWYG">WYSIWYG</a></b>. Stands for +"You asked for it, you got it", because what you actually asked +for is often not apparent until long after it is too late to do +anything about it. Used to denote perversity ("Real Programmers +use YAFIYGI tools<small>...</small>and <i>like</i> it!") or, +less often, a necessary tradeoff ("Only a YAFIYGI tool can have +full programmable flexibility in its interface.").</p> + +<p>This precise sense of "You asked for it, you got it" seems to +have first appeared in Ed Post's classic parody "Real Programmers +don't use Pascal" (see <b><a href="#RealProgrammer">Real +Programmer</a></b>s); the acronym is a more recent invention.</p> + +<hr> +Node:<a name="YAUN">YAUN</a>, Next:<a rel="next" href="#YellowBook">Yellow Book</a>, Previous:<a rel="previous" +href="#YAFIYGI">YAFIYGI</a>, Up:<a rel="up" href="#chap25">= Y =</a> <br> + + +<p><b>YAUN</b> /yawn/ n.</p> + +<p>[Acronym for `Yet Another Unix Nerd'] Reported from the San +Diego Computer Society (predominantly a microcomputer users' +group) as a good-natured punning insult aimed at Unix +zealots.</p> + +<hr> +Node:<a name="YellowBook">Yellow Book</a>, Next:<a rel="next" +href="#yellowcard">yellow card</a>, Previous:<a rel="previous" +href="#YAUN">YAUN</a>, Up:<a rel="up" href="#chap25">= Y +=</a> <br> + + +<p><b>Yellow Book</b> n.</p> + +<p>The print version of this Jargon File; "The New Hacker's +Dictionary" from MIT Press; The book includes essentially all the +material the File, plus a Foreword by Guy L. Steele Jr. and a +Preface by Eric S. Raymond. Most importantly, the book version is +nicely typeset and includes almost all of the infamous Crunchly +cartoons by the Great Quux, each attached to an appropriate +entry. The first edition (1991, ISBN 0-262-68069-6) corresponded +to the Jargon File version 2.9.6. The second edition (1993, ISBN +0-262-68079-3) corresponded to the Jargon File 3.0.0. The third +(1996, ISBN 0-262-68092-0) corresponded to 4.0.0.</p> + +<hr> +Node:<a name="yellowcard">yellow card</a>, Next:<a rel="next" +href="#yellowwire">yellow wire</a>, Previous:<a rel="previous" +href="#YellowBook">Yellow Book</a>, Up:<a rel="up" href="#chap25">= Y =</a> <br> + + +<p><b>yellow card</b> n.</p> + +<p>See <b><a href="#greencard">green card</a></b>.</p> + +<hr> +Node:<a name="yellowwire">yellow wire</a>, Next:<a rel="next" +href="#YetAnother">Yet Another</a>, Previous:<a rel="previous" +href="#yellowcard">yellow card</a>, Up:<a rel="up" href="#chap25">= Y =</a> <br> + + +<p><b>yellow wire</b> n.</p> + +<p>[IBM] Repair wires used when connectors (especially ribbon +connectors) got broken due to some schlemiel pinching them, or to +reconnect cut traces after the FE mistakenly cut one. Compare +<b><a href="#bluewire">blue wire</a></b>, <b><a href="#purplewire">purple wire</a></b>, <b><a href="#redwire">red wire</a></b>.</p> + +<hr> +Node:<a name="YetAnother">Yet Another</a>, Next:<a rel="next" +href="#YHBT">YHBT</a>, Previous:<a rel="previous" href="#yellowwire">yellow wire</a>, Up:<a rel="up" href="#chap25">= Y =</a> <br> + + +<p><b>Yet Another</b> adj.</p> + +<p>[From Unix's <code>yacc(1)</code>, `Yet Another +Compiler-Compiler', a LALR parser generator] 1. Of your own work: +A humorous allusion often used in titles to acknowledge that the +topic is not original, though the content is. As in `Yet Another +AI Group' or `Yet Another Simulated Annealing Algorithm'. 2. Of +others' work: Describes something of which there are already far +too many. See also <b><a href="#YA-">YA-</a></b>, <b><a href="#YABA">YABA</a></b>, <b><a href="#YAUN">YAUN</a></b>.</p> + +<hr> +Node:<a name="YHBT">YHBT</a>, Next:<a rel="next" href="#YKYBHTLW">YKYBHTLW</a>, Previous:<a rel="previous" href="#YetAnother">Yet Another</a>, Up:<a rel="up" href="#chap25">= Y =</a> <br> + + +<p><b>YHBT</b> //</p> + +<p>[Usenet: very common] Abbreviation: You Have Been Trolled (see +<b><a href="#troll">troll</a></b>, sense 1). Especially used in +"YHBT. YHL. HAND.", which is widely understood to expand to "You +Have Been Trolled. You Have Lost. Have A Nice Day". You are quite +likely to see this if you respond incautiously to a +flame-provoking post that was obviously floated as sucker +bait.</p> + +<hr> +Node:<a name="YKYBHTLW">YKYBHTLW</a>, Next:<a rel="next" href="#YMMV">YMMV</a>, Previous:<a rel="previous" href="#YHBT">YHBT</a>, Up:<a rel="up" href="#chap25">= Y =</a> +<br> + + +<p><b>YKYBHTLW</b> // abbrev.</p> + +<p>Abbreviation of `You know you've been hacking too long +when...', which became established on the Usenet group +<i>alt.folklore.computers</i> during extended discussion of the +indicated entry in the Jargon File.</p> + +<hr> +Node:<a name="YMMV">YMMV</a>, Next:<a rel="next" href="#Youarenotexpectedtounderstandthis">You are +not expected to understand this</a>, Previous:<a rel="previous" +href="#YKYBHTLW">YKYBHTLW</a>, Up:<a rel="up" href="#chap25">= Y =</a> <br> + + +<p><b>YMMV</b> // cav.</p> + +<p>Abbreviation for <b><a href="#Yourmileagemayvary">Your mileage may vary</a></b> +common on Usenet.</p> + +<hr> +Node:<a name="Youarenotexpectedtounderstandthis">You are not +expected to understand this</a>, Next:<a rel="next" href="#Youknowyouvebeenhackingtoolongwhen">You +know you've been hacking too long when</a>, Previous:<a rel="previous" href="#YMMV">YMMV</a>, Up:<a rel="up" href="#chap25">= Y =</a> <br> + + +<p><b>You are not expected to understand this</b> [Unix] cav.</p> + +<p>The canonical comment describing something <b><a href="#magic">magic</a></b> or too complicated to bother explaining +properly. From an infamous comment in the context-switching code +of the V6 Unix kernel. Dennis Ritchie has explained this +in detail.</p> + +<hr> +Node:<a name="Youknowyouvebeenhackingtoolongwhen">You +know you've been hacking too long when</a>, Next:<a rel="next" +href="#Yourmileagemayvary">Your mileage may vary</a>, +Previous:<a rel="previous" href="#Youarenotexpectedtounderstandthis">You are +not expected to understand this</a>, Up:<a rel="up" href="#chap25">= Y =</a> <br> + + +<p><b>You know you've been hacking too long when</b></p> + +<p>The set-up line for a genre of one-liners told by hackers +about themselves. These include the following:<br> +</p> + +<ul> +<li>not only do you check your email more often than your paper +mail, but you remember your <b><a href="#networkaddress">network address</a></b> faster than your +postal one.</li> + +<li>your <b><a href="#SO">SO</a></b> kisses you on the neck and +the first thing you think is "Uh, oh, <b><a href="#priorityinterrupt">priority interrupt</a></b>."</li> + +<li>you go to balance your checkbook and discover that you're +doing it in octal.</li> + +<li>your computers have a higher street value than your car.</li> + +<li>in your universe, `round numbers' are powers of 2, not +10.</li> + +<li>more than once, you have woken up recalling a dream in some +programming language.</li> + +<li>you realize you have never seen half of your best +friends.</li> +</ul> + +<br> +<p>A list +list of these can be found by searching for this phrase on the +web.</p> + +<p>[An early version of this entry said "All but one of these +have been reliably reported as hacker traits (some of them quite +often). Even hackers may have trouble spotting the ringer." The +ringer was balancing one's checkbook in octal, which I made up +out of whole cloth. Although more respondents picked that one out +as fiction than any of the others, I also received multiple +independent reports of its actually happening, most famously to +Grace Hopper while she was working with BINAC in 1949. --ESR]</p> + +<hr> +Node:<a name="Yourmileagemayvary">Your mileage may +vary</a>, Next:<a rel="next" href="#Yowx">Yow!</a>, Previous:<a +rel="previous" href="#Youknowyouvebeenhackingtoolongwhen">You +know you've been hacking too long when</a>, Up:<a rel="up" href="#chap25">= Y =</a> <br> + + +<p><b>Your mileage may vary</b> cav.</p> + +<p>[from the standard disclaimer attached to EPA mileage ratings +by American car manufacturers] 1. A ritual warning often found in +Unix freeware distributions. Translates roughly as "Hey, I tried +to write this portably, but who <i>knows</i> what'll happen on +your system?" 2. More generally, a qualifier attached to advice. +"I find that sending flowers works well, but your mileage may +vary."</p> + +<hr> +Node:<a name="Yowx">Yow!</a>, Next:<a rel="next" href="#yoyomode">yoyo mode</a>, Previous:<a rel="previous" href="#Yourmileagemayvary">Your mileage may vary</a>, Up:<a +rel="up" href="#chap25">= Y =</a> <br> + + +<p><b>Yow!</b> /yow/ interj.</p> + +<p>[from "Zippy the Pinhead" comix] A favored hacker expression +of humorous surprise or emphasis. "Yow! Check out what happens +when you twiddle the foo option on this display hack!" Compare +<b><a href="#gurfle">gurfle</a></b>.</p> + +<hr> +Node:<a name="yoyomode">yoyo mode</a>, Next:<a rel="next" +href="#YuShiangWholeFish">Yu-Shiang Whole Fish</a>, +Previous:<a rel="previous" href="#Yowx">Yow!</a>, Up:<a rel="up" +href="#chap25">= Y =</a> <br> + + +<p><b>yoyo mode</b> n.</p> + +<p>The state in which the system is said to be when it rapidly +alternates several times between being up and being down. +Interestingly (and perhaps not by coincidence), many hardware +vendors give out free yoyos at Usenix exhibits.</p> + +<p>Sun Microsystems gave out logoized yoyos at SIGPLAN '88. +Tourists staying at one of Atlanta's most respectable hotels were +subsequently treated to the sight of 200 of the country's top +computer scientists testing yo-yo algorithms in the lobby.</p> + +<hr> +Node:<a name="YuShiangWholeFish">Yu-Shiang Whole Fish</a>, +Next:<a rel="next" href="#zap">zap</a>, Previous:<a rel="previous" href="#yoyomode">yoyo mode</a>, Up:<a rel="up" +href="#chap25">= Y =</a> <br> + + +<p><b>Yu-Shiang Whole Fish</b> /yoo-shyang hohl fish/ n. obs.</p> + +<p>The character gamma (extended SAIL ASCII 0001001), which with +a loop in its tail looks like a little fish swimming down the +page. The term is actually the name of a Chinese dish in which a +fish is cooked whole (not <b><a href="#parse">parse</a></b>d) and +covered with Yu-Shiang (or Yu-Hsiang) sauce. Usage: primarily by +people on the MIT LISP Machine, which could display this +character on the screen. Tends to elicit incredulity from people +who hear about it second-hand.</p> + +<hr> +Node:<a name="chap26">= Z =</a>, Previous:<a rel="previous" href="#chap25">= Y =</a>, Up:<a rel="up" href="#TheJargonLexicon">The Jargon Lexicon</a> <br> + + +<h2>= Z =</h2> + +<ul> +<li><a href="#zap">zap</a>:</li> + +<li><a href="#zapped">zapped</a>:</li> + +<li><a href="#ZawinskisLaw">Zawinski's Law</a>:</li> + +<li><a href="#zbeba">zbeba</a>:</li> + +<li><a href="#zen">zen</a>:</li> + +<li><a href="#zero">zero</a>:</li> + +<li><a href="#zero-content">zero-content</a>:</li> + +<li><a href="#ZeroOneInfinityRule">Zero-One-Infinity +Rule</a>:</li> + +<li><a href="#zeroth">zeroth</a>:</li> + +<li><a href="#zigamorph">zigamorph</a>:</li> + +<li><a href="#zip">zip</a>:</li> + +<li><a href="#zipperhead">zipperhead</a>:</li> + +<li><a href="#zombie">zombie</a>:</li> + +<li><a href="#zorch">zorch</a>:</li> + +<li><a href="#Zork">Zork</a>:</li> + +<li><a href="#zorkmid">zorkmid</a>:</li> +</ul> + +<hr> +Node:<a name="zap">zap</a>, Next:<a rel="next" href="#zapped">zapped</a>, Previous:<a rel="previous" href="#YuShiangWholeFish">Yu-Shiang Whole Fish</a>, Up:<a rel="up" href="#chap26">= Z =</a> <br> + + +<p><b>zap</b></p> + +<p>1. n. Spiciness. 2. vt. To make food spicy. 3. vt. To make +someone `suffer' by making his food spicy. (Most hackers love +spicy food. Hot-and-sour soup is considered wimpy unless it makes +you wipe your nose for the rest of the meal.) See <b><a href="#zapped">zapped</a></b>. 4. vt. To modify, usually to correct; +esp. used when the action is performed with a debugger or binary +patching tool. Also implies surgical precision. "Zap the debug +level to 6 and run it again." In the IBM mainframe world, binary +patches are applied to programs or to the OS with a program +called `superzap', whose file name is `IMASPZAP' (possibly +contrived from I M A SuPerZAP). 5. vt. To erase or reset. 6. To +<b><a href="#fry">fry</a></b> a chip with static electricity. "Uh +oh -- I think that lightning strike may have zapped the disk +controller."</p> + +<hr> +Node:<a name="zapped">zapped</a>, Next:<a rel="next" href="#ZawinskisLaw">Zawinski's Law</a>, Previous:<a rel="previous" href="#zap">zap</a>, Up:<a rel="up" href="#chap26">= Z =</a> <br> + + +<p><b>zapped</b> adj.</p> + +<p>Spicy. This term is used to distinguish between food that is +hot (in temperature) and food that is <i>spicy</i>-hot. For +example, the Chinese appetizer Bon Bon Chicken is a kind of +chicken salad that is cold but zapped; by contrast, <b><a href="#vanilla">vanilla</a></b> wonton soup is hot but not zapped. See +also <b><a href="#orientalfood">oriental food</a></b>, <b><a +href="#laserchicken">laser chicken</a></b>. See <b><a href="#zap">zap</a></b>, senses 1 and 2.</p> + +<hr> +Node:<a name="ZawinskisLaw">Zawinski's Law</a>, Next:<a rel="next" href="#zbeba">zbeba</a>, Previous:<a rel="previous" href="#zapped">zapped</a>, Up:<a rel="up" href="#chap26">= Z +=</a> <br> + + +<p><b>Zawinski's Law</b></p> + +<p>"Every program attempts to expand until it can read mail. +Those programs which cannot so expand are replaced by ones which +can." Coined by Jamie Zawinski (who called it the "Law of +Software Envelopment") to express his belief that all truly +useful programs experience pressure to evolve into toolkits and +application platforms (the mailer thing, he says, is just a side +effect of that). It is commonly cited, though with widely varying +degrees of accuracy.</p> + +<hr> +Node:<a name="zbeba">zbeba</a>, Next:<a rel="next" href="#zen">zen</a>, Previous:<a rel="previous" href="#ZawinskisLaw">Zawinski's Law</a>, Up:<a rel="up" href="#chap26">= Z =</a> <br> + + +<p><b>zbeba</b> n.</p> + +<p>[USENET] The word `moron' in <b><a href="#rot13">rot13</a></b>. Used to describe newbies who are behaving +with especial cluelessness.</p> + +<hr> +Node:<a name="zen">zen</a>, Next:<a rel="next" href="#zero">zero</a>, Previous:<a rel="previous" href="#zbeba">zbeba</a>, Up:<a rel="up" href="#chap26">= Z +=</a> <br> + + +<p><b>zen</b> vt.</p> + +<p>To figure out something by meditation or by a sudden flash of +enlightenment. Originally applied to bugs, but occasionally +applied to problems of life in general. "How'd you figure out the +buffer allocation problem?" "Oh, I zenned it." Contrast <b><a +href="#grok">grok</a></b>, which connotes a time-extended version +of zenning a system. Compare <b><a href="#hackmode">hack +mode</a></b>. See also <b><a href="#guru">guru</a></b>.</p> + +<hr> +Node:<a name="zero">zero</a>, Next:<a rel="next" href="#zero-content">zero-content</a>, Previous:<a rel="previous" +href="#zen">zen</a>, Up:<a rel="up" href="#chap26">= Z +=</a> <br> + + +<p><b>zero</b> vt.</p> + +<p>1. To set to 0. Usually said of small pieces of data, such as +bits or words (esp. in the construction `zero out'). 2. To erase; +to discard all data from. Said of disks and directories, where +`zeroing' need not involve actually writing zeroes throughout the +area being zeroed. One may speak of something being `logically +zeroed' rather than being `physically zeroed'. See <b><a href="#scribble">scribble</a></b>.</p> + +<hr> +Node:<a name="zero-content">zero-content</a>, Next:<a rel="next" +href="#ZeroOneInfinityRule">Zero-One-Infinity Rule</a>, +Previous:<a rel="previous" href="#zero">zero</a>, Up:<a rel="up" +href="#chap26">= Z =</a> <br> + + +<p><b>zero-content</b> adj.</p> + +<p>Syn. <b><a href="#content-free">content-free</a></b>.</p> + +<hr> +Node:<a name="ZeroOneInfinityRule">Zero-One-Infinity +Rule</a>, Next:<a rel="next" href="#zeroth">zeroth</a>, +Previous:<a rel="previous" href="#zero-content">zero-content</a>, +Up:<a rel="up" href="#chap26">= Z =</a> <br> + + +<p><b>Zero-One-Infinity Rule</b> prov.</p> + +<p>"Allow none of <b><a href="#foo">foo</a></b>, one of <b><a +href="#foo">foo</a></b>, or any number of <b><a href="#foo">foo</a></b>." A rule of thumb for software design, which +instructs one to not place <b><a href="#random">random</a></b> +limits on the number of instances of a given entity (such as: +windows in a window system, letters in an OS's filenames, etc.). +Specifically, one should either disallow the entity entirely, +allow exactly one instance (an "exception"), or allow as many as +the user wants - address space and memory permitting.</p> + +<p>The logic behind this rule is that there are often situations +where it makes clear sense to allow one of something instead of +none. However, if one decides to go further and allow N (for N +> 1), then why not N+1? And if N+1, then why not N+2, and so +on? Once above 1, there's no excuse not to allow any N; hence, +<b><a href="#infinity">infinity</a></b>.</p> + +<p>Many hackers recall in this connection Isaac Asimov's SF novel +"The Gods Themselves" in which a character announces that the +number 2 is impossible - if you're going to believe in more than +one universe, you might as well believe in an infinite number of +them.</p> + +<hr> +Node:<a name="zeroth">zeroth</a>, Next:<a rel="next" href="#zigamorph">zigamorph</a>, Previous:<a rel="previous" href="#ZeroOneInfinityRule">Zero-One-Infinity Rule</a>, Up:<a +rel="up" href="#chap26">= Z =</a> <br> + + +<p><b>zeroth</b> /zee'rohth/ adj.</p> + +<p>First. Among software designers, comes from C's and LISP's +0-based indexing of arrays. Hardware people also tend to start +counting at 0 instead of 1; this is natural since, e.g., the 256 +states of 8 bits correspond to the binary numbers 0, 1, +<small>...</small>, 255 and the digital devices known as +`counters' count in this way.</p> + +<p>Hackers and computer scientists often like to call the first +chapter of a publication `Chapter 0', especially if it is of an +introductory nature (one of the classic instances was in the +First Edition of <b><a href="#KandR">K&R</a></b>). In +recent years this trait has also been observed among many pure +mathematicians (who have an independent tradition of numbering +from 0). Zero-based numbering tends to reduce <b><a href="#fenceposterror">fencepost error</a></b>s, though it cannot +eliminate them entirely.</p> + +<hr> +Node:<a name="zigamorph">zigamorph</a>, Next:<a rel="next" href="#zip">zip</a>, Previous:<a rel="previous" href="#zeroth">zeroth</a>, Up:<a rel="up" href="#chap26">= Z +=</a> <br> + + +<p><b>zigamorph</b> /zig'*-morf/ n.</p> + +<p>1. Hex FF (11111111) when used as a delimiter or <b><a href="#fence">fence</a></b> character. Usage: primarily at IBM shops. +2. [proposed] n. The Unicode non-character U+FFFF +(1111111111111111), a character code which is not assigned to any +character, and so is usable as end-of-string. (Unicode is a +16-bit character code intended to cover all of the world's +writing systems, including Latin, Greek, Cyrillic, Chinese, +hiragana, katakana, Devanagari, Thai, Laotian and many other +scripts - support for <b><a href="#elvish">elvish</a></b> is +planned for a future release).</p> + +<hr> +Node:<a name="zip">zip</a>, Next:<a rel="next" href="#zipperhead">zipperhead</a>, Previous:<a rel="previous" href="#zigamorph">zigamorph</a>, Up:<a rel="up" href="#chap26">= Z =</a> <br> + + +<p><b>zip</b> vt.</p> + +<p>[primarily MS-DOS] To create a compressed archive from a group +of files using PKWare's PKZIP or a compatible archiver. Its use +is spreading now that portable implementations of the algorithm +have been written. Commonly used as follows: "I'll zip it up and +send it to you." See <b><a href="#tarandfeather">tar and +feather</a></b>.</p> + +<hr> +Node:<a name="zipperhead">zipperhead</a>, Next:<a rel="next" +href="#zombie">zombie</a>, Previous:<a rel="previous" href="#zip">zip</a>, Up:<a rel="up" href="#chap26">= Z =</a> +<br> + + +<p><b>zipperhead</b> n.</p> + +<p>[IBM] A person with a closed mind.</p> + +<hr> +Node:<a name="zombie">zombie</a>, Next:<a rel="next" href="#zorch">zorch</a>, Previous:<a rel="previous" href="#zipperhead">zipperhead</a>, Up:<a rel="up" href="#chap26">= Z =</a> <br> + + +<p><b>zombie</b> n.</p> + +<p>[Unix] A process that has died but has not yet relinquished +its process table slot (because the parent process hasn't +executed a <code>wait(2)</code> for it yet). These can be seen in +<code>ps(1)</code> listings occasionally. Compare <b><a href="#orphan">orphan</a></b>.</p> + +<hr> +Node:<a name="zorch">zorch</a>, Next:<a rel="next" href="#Zork">Zork</a>, Previous:<a rel="previous" href="#zombie">zombie</a>, Up:<a rel="up" href="#chap26">= Z +=</a> <br> + + +<p><b>zorch</b> /zorch/</p> + +<p>1. [TMRC] v. To attack with an inverse heat sink. 2. [TMRC] v. +To travel, with v approaching c [that is, with velocity +approaching lightspeed --ESR]. 3. [MIT] v. To propel something +very quickly. "The new comm software is very fast; it really +zorches files through the network." 4. [MIT] n. Influence. +Brownie points. Good karma. The intangible and fuzzy currency in +which favors are measured. "I'd rather not ask him for that just +yet; I think I've used up my quota of zorch with him for the +week." 5. [MIT] n. Energy, drive, or ability. "I think I'll <b><a +href="#punt">punt</a></b> that change for now; I've been up for +30 hours and I've run out of zorch." 6. [MIT] v. To flunk an exam +or course.</p> + +<hr> +Node:<a name="Zork">Zork</a>, Next:<a rel="next" href="#zorkmid">zorkmid</a>, Previous:<a rel="previous" href="#zorch">zorch</a>, Up:<a rel="up" href="#chap26">= Z +=</a> <br> + + +<p><b>Zork</b> /zork/ n.</p> + +<p>The second of the great early experiments in computer fantasy +gaming; see <b><a href="#ADVENT">ADVENT</a></b>. Originally +written on MIT-DM during 1977-1979, later distributed with BSD +Unix (as a patched, sourceless RT-11 FORTRAN binary; see <b><a +href="#retrocomputing">retrocomputing</a></b>) and commercialized +as `The Zork Trilogy' by <b><a href="#Infocom">Infocom</a></b>. +The FORTRAN source was later rewritten for portability and +released to Usenet under the name "Dungeon". Both FORTRAN +"Dungeon" and translated C versions are available at many FTP +sites. See also <b><a href="#grue">grue</a></b>.</p> + +<hr> +Node:<a name="zorkmid">zorkmid</a>, Previous:<a rel="previous" +href="#Zork">Zork</a>, Up:<a rel="up" href="#chap26">= Z +=</a> <br> + + +<p><b>zorkmid</b> /zork'mid/ n.</p> + +<p>The canonical unit of currency in hacker-written games. This +originated in <b><a href="#Zork">Zork</a></b> but has spread to +<b><a href="#nethack">nethack</a></b> and is referred to in +several other games.</p> + +<p><b>(Lexicon Entries End Here)</b></p> + +<hr> +Node:<a name="AppendixA">Appendix A</a>, Next:<a rel="next" href="#AppendixB">Appendix B</a>, Previous:<a rel="previous" href="#TheJargonLexicon">The Jargon Lexicon</a>, Up:<a rel="up" href="#Top">Top</a> <br> + + +<h2>Hacker Folklore</h2> + +<p>This appendix contains several legends and fables that +illuminate the meaning of various entries in the lexicon.</p> + +<ul> +<li><a href="#TheMeaningofHack">The Meaning of Hack</a>: +<small>...</small>and three famous ones</li> + +<li><a href="#TVTypewriters">TV Typewriters</a>: A Tale of +Hackish Ingenuity</li> + +<li><a href="#AStoryAboutMagic">A Story About Magic</a>: +By Guy Steele</li> + +<li><a href="#SomeAIKoans">Some AI Koans</a>: Wit and +Wisdom of the Masters</li> + +<li><a href="#OSandJEDGAR">OS and JEDGAR</a>: Intrigue and +mayhem under ITS</li> + +<li><a href="#TheStoryofMel">The Story of Mel</a>: One +of hackerdom's great myths</li> +</ul> + +<hr> +Node:<a name="TheMeaningofHack">The Meaning of Hack</a>, +Next:<a rel="next" href="#TVTypewriters">TV Typewriters</a>, +Previous:<a rel="previous" href="#AppendixA">Appendix A</a>, +Up:<a rel="up" href="#AppendixA">Appendix A</a> <br> + + +<h2>The Meaning of `Hack'</h2> + +<p>"The word <b><a href="#hack">hack</a></b> doesn't really have +69 different meanings", according to MIT hacker Phil Agre. "In +fact, <b><a href="#hack">hack</a></b> has only one meaning, an +extremely subtle and profound one which defies articulation. +Which connotation is implied by a given use of the word depends +in similarly profound ways on the context. Similar remarks apply +to a couple of other hacker words, most notably <b><a href="#random">random</a></b>."</p> + +<p>Hacking might be characterized as `an appropriate application +of ingenuity'. Whether the result is a quick-and-dirty patchwork +job or a carefully crafted work of art, you have to admire the +cleverness that went into it.</p> + +<p>An important secondary meaning of <b><a href="#hack">hack</a></b> is `a creative practical joke'. This kind of +hack is easier to explain to non-hackers than the programming +kind. Of course, some hacks have both natures; see the lexicon +entries for <b><a href="#pseudo">pseudo</a></b> and <b><a href="#kgbvax">kgbvax</a></b>. But here are some examples of pure +practical jokes that illustrate the hacking spirit:</p> + +<blockquote>In 1961, students from Caltech (California Institute +of Technology, in Pasadena) hacked the Rose Bowl football game. +One student posed as a reporter and `interviewed' the director of +the University of Washington card stunts (such stunts involve +people in the stands who hold up colored cards to make pictures). +The reporter learned exactly how the stunts were operated, and +also that the director would be out to dinner later. + +<p>While the director was eating, the students (who called +themselves the `Fiendish Fourteen') picked a lock and stole a +blank direction sheet for the card stunts. They then had a +printer run off 2300 copies of the blank. The next day they +picked the lock again and stole the master plans for the stunts +-- large sheets of graph paper colored in with the stunt +pictures. Using these as a guide, they made new instructions for +three of the stunts on the duplicated blanks. Finally, they broke +in once more, replacing the stolen master plans and substituting +the stack of diddled instruction sheets for the original set.</p> + +<p>The result was that three of the pictures were totally +different. Instead of `WASHINGTON', the word ``CALTECH' was +flashed. Another stunt showed the word `HUSKIES', the Washington +nickname, but spelled it backwards. And what was supposed to have +been a picture of a husky instead showed a beaver. (Both Caltech +and MIT use the beaver -- nature's engineer -- as a mascot.)</p> + +<p>After the game, the Washington faculty athletic representative +said: "Some thought it ingenious; others were indignant." The +Washington student body president remarked: "No hard feelings, +but at the time it was unbelievable. We were amazed."</p> +</blockquote> + +<p>This is now considered a classic hack, particularly because +revising the direction sheets constituted a form of +programming.</p> + +<p>Here is another classic hack:</p> + +<blockquote>On November 20, 1982, MIT hacked the Harvard-Yale +football game. Just after Harvard's second touchdown against +Yale, in the first quarter, a small black ball popped up out of +the ground at the 40-yard line, and grew bigger, and bigger, and +bigger. The letters `MIT' appeared all over the ball. As the +players and officials stood around gawking, the ball grew to six +feet in diameter and then burst with a bang and a cloud of white +smoke. + +<p>The "Boston Globe" later reported: "If you want to know the +truth, MIT won The Game."</p> + +<p>The prank had taken weeks of careful planning by members of +MIT's Delta Kappa Epsilon fraternity. The device consisted of a +weather balloon, a hydraulic ram powered by Freon gas to lift it +out of the ground, and a vacuum-cleaner motor to inflate it. They +made eight separate expeditions to Harvard Stadium between 1 and +5 <small>A.M.</small>, locating an unused 110-volt circuit in the +stadium and running buried wires from the stadium circuit to the +40-yard line, where they buried the balloon device. When the time +came to activate the device, two fraternity members had merely to +flip a circuit breaker and push a plug into an outlet.</p> + +<p>This stunt had all the earmarks of a perfect hack: surprise, +publicity, the ingenious use of technology, safety, and +harmlessness. The use of manual control allowed the prank to be +timed so as not to disrupt the game (it was set off between +plays, so the outcome of the game would not be unduly affected). +The perpetrators had even thoughtfully attached a note to the +balloon explaining that the device was not dangerous and +contained no explosives.</p> + +<p>Harvard president Derek Bok commented: "They have an awful lot +of clever people down there at MIT, and they did it again." +President Paul E. Gray of MIT said: "There is absolutely no truth +to the rumor that I had anything to do with it, but I wish there +were."</p> +</blockquote> + +<p>The hacks above are verifiable history; they can be proved to +have happened. Many other classic-hack stories from MIT and +elsewhere, though retold as history, have the characteristics of +what Jan Brunvand has called `urban folklore' (see <b><a href="#FOAF">FOAF</a></b>). Perhaps the best known of these is the +legend of the infamous trolley-car hack, an alleged incident in +which engineering students are said to have welded a trolley car +to its tracks with thermite. Numerous versions of this have been +recorded from the 1940s to the present, most set at MIT but at +least one very detailed version set at CMU.</p> + +<p>Brian Leibowitz has researched MIT hacks both real and +mythical extensively; the interested reader is referred to his +delightful pictorial compendium "The Journal of the Institute for +Hacks, Tomfoolery, and Pranks" (MIT Museum, 1990; ISBN +0-917027-03-5). The Institute has a World Wide Web page at <a +href="http://hacks.mit.edu/Hacks/Gallery.html">http://hacks.mit.edu/Hacks/Gallery.html</a>. +There is rumored to be a sequel entitled "Is This The Way To +Baker Street?". The Caltech Alumni Association has published two +similar books titled "Legends of Caltech" and "More Legends of +Caltech".</p> + +<p>Finally, here is a story about one of the classic computer +hacks.</p> + +<blockquote>Back in the mid-1970s, several of the system support +staff at Motorola discovered a relatively simple way to crack +system security on the Xerox CP-V timesharing system. Through a +simple programming strategy, it was possible for a user program +to trick the system into running a portion of the program in +`master mode' (supervisor state), in which memory protection does +not apply. The program could then poke a large value into its +`privilege level' byte (normally write-protected) and could then +proceed to bypass all levels of security within the +file-management system, patch the system monitor, and do numerous +other interesting things. In short, the barn door was wide open. + +<p>Motorola quite properly reported this problem to Xerox via an +official `level 1 SIDR' (a bug report with an intended urgency of +`needs to be fixed yesterday'). Because the text of each SIDR was +entered into a database that could be viewed by quite a number of +people, Motorola followed the approved procedure: they simply +reported the problem as `Security SIDR', and attached all of the +necessary documentation, ways-to-reproduce, etc.</p> + +<p>The CP-V people at Xerox sat on their thumbs; they either +didn't realize the severity of the problem, or didn't assign the +necessary operating-system-staff resources to develop and +distribute an official patch.</p> + +<p>Months passed. The Motorola guys pestered their Xerox +field-support rep, to no avail. Finally they decided to take +direct action, to demonstrate to Xerox management just how easily +the system could be cracked and just how thoroughly the security +safeguards could be subverted.</p> + +<p>They dug around in the operating-system listings and devised a +thoroughly devilish set of patches. These patches were then +incorporated into a pair of programs called `Robin Hood' and +`Friar Tuck'. Robin Hood and Friar Tuck were designed to run as +`ghost jobs' (daemons, in Unix terminology); they would use the +existing loophole to subvert system security, install the +necessary patches, and then keep an eye on one another's statuses +in order to keep the system operator (in effect, the superuser) +from aborting them.</p> + +<p>One fine day, the system operator on the main CP-V software +development system in El Segundo was surprised by a number of +unusual phenomena. These included the following:</p> + +<ul> +<li>Tape drives would rewind and dismount their tapes in the +middle of a job.</li> + +<li>Disk drives would seek back and forth so rapidly that they +would attempt to walk across the floor (see <b><a href="#walkingdrives">walking drives</a></b>).</li> + +<li>The card-punch output device would occasionally start up of +itself and punch a <b><a href="#lacecard">lace card</a></b>. +These would usually jam in the punch.</li> + +<li>The console would print snide and insulting messages from +Robin Hood to Friar Tuck, or vice versa.</li> + +<li>The Xerox card reader had two output stackers; it could be +instructed to stack into A, stack into B, or stack into A (unless +a card was unreadable, in which case the bad card was placed into +stacker B). One of the patches installed by the ghosts added some +code to the card-reader driver<small>...</small> after reading a +card, it would flip over to the opposite stacker. As a result, +card decks would divide themselves in half when they were read, +leaving the operator to recollate them manually.</li> +</ul> + +<p>Naturally, the operator called in the operating-system +developers. They found the bandit ghost jobs running, and <b><a +href="#gun">gun</a></b>ned them<small>...</small> and were once +again surprised. When Robin Hood was gunned, the following +sequence of events took place:</p> + +<pre> +!X id1 + +id1: Friar Tuck... I am under attack! Pray save me! +id1: Off (aborted) + +id2: Fear not, friend Robin! I shall rout the Sheriff + of Nottingham's men! + +id1: Thank you, my good fellow! +</pre> + +<p>Each ghost-job would detect the fact that the other had been +killed, and would start a new copy of the recently slain program +within a few milliseconds. The only way to kill both ghosts was +to kill them simultaneously (very difficult) or to deliberately +crash the system.</p> + +<p>Finally, the system programmers did the latter -- only to find +that the bandits appeared once again when the system rebooted! It +turned out that these two programs had patched the boot-time OS +image (the kernel file, in Unix terms) and had added themselves +to the list of programs that were to be started at boot time +(this is similar to the way MS-DOS viruses propagate).</p> + +<p>The Robin Hood and Friar Tuck ghosts were finally eradicated +when the system staff rebooted the system from a clean boot-tape +and reinstalled the monitor. Not long thereafter, Xerox released +a patch for this problem.</p> + +<p>It is alleged that Xerox filed a complaint with Motorola's +management about the merry-prankster actions of the two employees +in question. It is not recorded that any serious disciplinary +action was taken against either of them.</p> +</blockquote> + +<hr> +Node:<a name="TVTypewriters">TV Typewriters</a>, Next:<a rel="next" href="#AStoryAboutMagic">A Story About Magic</a>, +Previous:<a rel="previous" href="#TheMeaningofHack">The +Meaning of Hack</a>, Up:<a rel="up" href="#AppendixA">Appendix +A</a> <br> + + +<h2>TV Typewriters A Tale of Hackish Ingenuity</h2> + +<p>Here is a true story about a glass tty: One day an MIT hacker +was in a motorcycle accident and broke his leg. He had to stay in +the hospital quite a while, and got restless because he couldn't +<b><a href="#hack">hack</a></b>. Two of his friends therefore +took a terminal and a modem for it to the hospital, so that he +could use the computer by telephone from his hospital bed.</p> + +<p>Now this happened some years before the spread of home +computers, and computer terminals were not a familiar sight to +the average person. When the two friends got to the hospital, a +guard stopped them and asked what they were carrying. They +explained that they wanted to take a computer terminal to their +friend who was a patient.</p> + +<p>The guard got out his list of things that patients were +permitted to have in their rooms: TV, radio, electric razor, +typewriter, tape player, <small>...</small> no computer +terminals. Computer terminals weren't on the list, so the guard +wouldn't let it in. Rules are rules, you know. (This guard was +clearly a <b><a href="#droid">droid</a></b>.)</p> + +<p>Fair enough, said the two friends, and they left again. They +were frustrated, of course, because they knew that the terminal +was as harmless as a TV or anything else on the +list<small>...</small> which gave them an idea.</p> + +<p>The next day they returned, and the same thing happened: a +guard stopped them and asked what they were carrying. They said: +"This is a TV typewriter!" The guard was skeptical, so they +plugged it in and demonstrated it. "See? You just type on the +keyboard and what you type shows up on the TV screen." Now the +guard didn't stop to think about how utterly useless a typewriter +would be that didn't produce any paper copies of what you typed; +but this was clearly a TV typewriter, no doubt about it. So he +checked his list: "A TV is all right, a typewriter is all right +<small>...</small> okay, take it on in!"</p> + +<p>[Historical note: Many years ago, "Popular Electronics" +published solder-it-yourself plans for a TV typewriter. Despite +the essential uselessness of the device, it was an enormously +popular project. Steve Ciarcia, the man behind "Byte" magazine's +"Circuit Cellar" feature, resurrected this ghost in one of his +books of the early 1980s. He ascribed its popularity (no doubt +correctly) to the feeling of power the builder could achieve by +being able to decide himself what would be shown on the TV. +--ESR]</p> + +<p>[Antihistorical note: On September 23rd, 1992, the L.A. Times +ran the following bit in Steve Harvey's `Only in L.A.' +column:</p> + +<blockquote>It must have been borrowed from a museum: Solomon +Waters of Altadena, a 6-year-old first-grader, came home from his +first day of school and excitedly told his mother how he had +written on "a machine that looks like a computer-but without the +TV screen." + +<p>She asked him if it could have been a "typewriter."</p> + +<p>"Yeah! Yeah!" he said. "That's what it was called."</p> +</blockquote> + +<p>I have since investigated this matter and determined that many +of today's teenagers have never seen a slide rule, +either<small>...</small>. - ESR]</p> + +<hr> +Node:<a name="AStoryAboutMagic">A Story About Magic</a>, +Next:<a rel="next" href="#SomeAIKoans">Some AI Koans</a>, +Previous:<a rel="previous" href="#TVTypewriters">TV +Typewriters</a>, Up:<a rel="up" href="#AppendixA">Appendix +A</a> <br> + + +<h2>A Story About `Magic'</h2> + +<p>Some years ago, I (GLS) was snooping around in the cabinets +that housed the MIT AI Lab's PDP-10, and noticed a little switch +glued to the frame of one cabinet. It was obviously a homebrew +job, added by one of the lab's hardware hackers (no one knows +who).</p> + +<p>You don't touch an unknown switch on a computer without +knowing what it does, because you might crash the computer. The +switch was labeled in a most unhelpful way. It had two positions, +and scrawled in pencil on the metal switch body were the words +`magic' and `more magic'. The switch was in the `more magic' +position.</p> + +<p>I called another hacker over to look at it. He had never seen +the switch before either. Closer examination revealed that the +switch had only one wire running to it! The other end of the wire +did disappear into the maze of wires inside the computer, but +it's a basic fact of electricity that a switch can't do anything +unless there are two wires connected to it. This switch had a +wire connected on one side and no wire on its other side.</p> + +<p>It was clear that this switch was someone's idea of a silly +joke. Convinced by our reasoning that the switch was inoperative, +we flipped it. The computer instantly crashed.</p> + +<p>Imagine our utter astonishment. We wrote it off as +coincidence, but nevertheless restored the switch to the `more +magic' position before reviving the computer.</p> + +<p>A year later, I told this story to yet another hacker, David +Moon as I recall. He clearly doubted my sanity, or suspected me +of a supernatural belief in the power of this switch, or perhaps +thought I was fooling him with a bogus saga. To prove it to him, +I showed him the very switch, still glued to the cabinet frame +with only one wire connected to it, still in the `more magic' +position. We scrutinized the switch and its lone connection, and +found that the other end of the wire, though connected to the +computer wiring, was connected to a ground pin. That clearly made +the switch doubly useless: not only was it electrically +nonoperative, but it was connected to a place that couldn't +affect anything anyway. So we flipped the switch.</p> + +<p>The computer promptly crashed.</p> + +<p>This time we ran for Richard Greenblatt, a long-time MIT +hacker, who was close at hand. He had never noticed the switch +before, either. He inspected it, concluded it was useless, got +some diagonal cutters and <b><a href="#dike">dike</a></b>d it +out. We then revived the computer and it has run fine ever +since.</p> + +<p>We still don't know how the switch crashed the machine. There +is a theory that some circuit near the ground pin was marginal, +and flipping the switch changed the electrical capacitance enough +to upset the circuit as millionth-of-a-second pulses went through +it. But we'll never know for sure; all we can really say is that +the switch was <b><a href="#magic">magic</a></b>.</p> + +<p>I still have that switch in my basement. Maybe I'm silly, but +I usually keep it set on `more magic'.</p> + +<p>1994: Another explanation of this story has since been +offered. Note that the switch body was metal. Suppose that the +non-connected side of the switch was connected to the switch body +(usually the body is connected to a separate earth lug, but there +are exceptions). The body is connected to the computer case, +which is, presumably, grounded. Now the circuit ground within the +machine isn't necessarily at the same potential as the case +ground, so flipping the switch connected the circuit ground to +the case ground, causing a voltage drop/jump which reset the +machine. This was probably discovered by someone who found out +the hard way that there was a potential difference between the +two, and who then wired in the switch as a joke.</p> + +<hr> +Node:<a name="SomeAIKoans">Some AI Koans</a>, Next:<a rel="next" href="#OSandJEDGAR">OS and JEDGAR</a>, Previous:<a +rel="previous" href="#AStoryAboutMagic">A Story About +Magic</a>, Up:<a rel="up" href="#AppendixA">Appendix A</a> +<br> + + +<h2>Some AI Koans</h2> + +<p>These are some of the funniest examples of a genre of jokes +told at the MIT AI Lab about various noted hackers. The original +koans were composed by Danny Hillis, who would later found +Connection Machines, Inc. In reading these, it is at least useful +to know that Minsky, Sussman, and Drescher are AI researchers of +note, that Tom Knight was one of the Lisp machine's principal +designers, and that David Moon wrote much of Lisp Machine +Lisp.</p> + +<p align="center">* * *</p> + +<p>A novice was trying to fix a broken Lisp machine by turning +the power off and on.</p> + +<p>Knight, seeing what the student was doing, spoke sternly: "You +cannot fix a machine by just power-cycling it with no +understanding of what is going wrong."</p> + +<p>Knight turned the machine off and on.</p> + +<p>The machine worked.</p> + +<p align="center">* * *</p> + +<p>One day a student came to Moon and said: "I understand how to +make a better garbage collector. We must keep a reference count +of the pointers to each cons."</p> + +<p>Moon patiently told the student the following story:</p> + +<blockquote>"One day a student came to Moon and said: `I +understand how to make a better garbage +collector<small>...</small></blockquote> + +<p>[Ed. note: Pure reference-count garbage collectors have +problems with circular structures that point to themselves.]</p> + +<p align="center">* * *</p> + +<p>In the days when Sussman was a novice, Minsky once came to him +as he sat hacking at the PDP-6.</p> + +<p>"What are you doing?", asked Minsky.</p> + +<p>"I am training a randomly wired neural net to play +Tic-Tac-Toe" Sussman replied.</p> + +<p>"Why is the net wired randomly?", asked Minsky.</p> + +<p>"I do not want it to have any preconceptions of how to play", +Sussman said.</p> + +<p>Minsky then shut his eyes.</p> + +<p>"Why do you close your eyes?", Sussman asked his teacher.</p> + +<p>"So that the room will be empty."</p> + +<p>At that moment, Sussman was enlightened.</p> + +<p align="center">* * *</p> + +<p>A disciple of another sect once came to Drescher as he was +eating his morning meal.</p> + +<p>"I would like to give you this personality test", said the +outsider, "because I want you to be happy."</p> + +<p>Drescher took the paper that was offered him and put it into +the toaster, saying: "I wish the toaster to be happy, too."</p> + +<hr> +Node:<a name="OSandJEDGAR">OS and JEDGAR</a>, Next:<a rel="next" href="#TheStoryofMel">The Story of Mel</a>, +Previous:<a rel="previous" href="#SomeAIKoans">Some AI +Koans</a>, Up:<a rel="up" href="#AppendixA">Appendix A</a> +<br> + + +<h2>OS and JEDGAR</h2> + +<p>This story says a lot about the ITS ethos.</p> + +<p>On the ITS system there was a program that allowed you to see +what was being printed on someone else's terminal. It spied on +the other guy's output by examining the insides of the monitor +system. The output spy program was called OS. Throughout the rest +of the computer science world (and at IBM too) OS means +`operating system', but among old-time ITS hackers it almost +always meant `output spy'.</p> + +<p>OS could work because ITS purposely had very little in the way +of `protection' that prevented one user from trespassing on +another's areas. Fair is fair, however. There was another program +that would automatically notify you if anyone started to spy on +your output. It worked in exactly the same way, by looking at the +insides of the operating system to see if anyone else was looking +at the insides that had to do with your output. This `counterspy' +program was called JEDGAR (a six-letterism pronounced as two +syllables: /jed'gr/), in honor of the former head of the FBI.</p> + +<p>But there's more. JEDGAR would ask the user for `license to +kill'. If the user said yes, then JEDGAR would actually <b><a +href="#gun">gun</a></b> the job of the <b><a href="#luser">luser</a></b> who was spying. Unfortunately, people +found that this made life too violent, especially when tourists +learned about it. One of the systems hackers solved the problem +by replacing JEDGAR with another program that only pretended to +do its job. It took a long time to do this, because every copy of +JEDGAR had to be patched. To this day no one knows how many +people never figured out that JEDGAR had been defanged.</p> + +<p>Interestingly, there is still a security module named JEDGAR +alive as of late 1994 -- in the Unisys MCP for large systems. It +is unknown to us whether the name is tribute or independent +invention.</p> + +<hr> +Node:<a name="TheStoryofMel">The Story of Mel</a>, +Previous:<a rel="previous" href="#OSandJEDGAR">OS and +JEDGAR</a>, Up:<a rel="up" href="#AppendixA">Appendix A</a> +<br> + +<h2>The Story of Mel</h2> + +<p> +This was posted to Usenet by its author, Ed Nather (utastro!nather), on May 21, +1983. +</p> + +<pre> +A recent article devoted to the <i>macho</i> side of programming +made the bald and unvarnished statement: + + Real Programmers write in FORTRAN. + +Maybe they do now, +in this decadent era of +Lite beer, hand calculators, and ``user-friendly'' software +but back in the Good Old Days, +when the term ``software'' sounded funny +and Real Computers were made out of drums and vacuum tubes, +Real Programmers wrote in machine code. +Not FORTRAN. Not RATFOR. Not, even, assembly language. +Machine Code. +Raw, unadorned, inscrutable hexadecimal numbers. +Directly. + +Lest a whole new generation of programmers +grow up in ignorance of this glorious past, +I feel duty-bound to describe, +as best I can through the generation gap, +how a Real Programmer wrote code. +I'll call him Mel, +because that was his name. + +I first met Mel when I went to work for Royal McBee Computer Corp., +a now-defunct subsidiary of the typewriter company. +The firm manufactured the LGP-30, +a small, cheap (by the standards of the day) +drum-memory computer, +and had just started to manufacture +the RPC-4000, a much-improved, +bigger, better, faster --- drum-memory computer. +Cores cost too much, +and weren't here to stay, anyway. +(That's why you haven't heard of the company, +or the computer.) + +I had been hired to write a FORTRAN compiler +for this new marvel and Mel was my guide to its wonders. +Mel didn't approve of compilers. + +``If a program can't rewrite its own code'', +he asked, ``what good is it?'' + +Mel had written, +in hexadecimal, +the most popular computer program the company owned. +It ran on the LGP-30 +and played blackjack with potential customers +at computer shows. +Its effect was always dramatic. +The LGP-30 booth was packed at every show, +and the IBM salesmen stood around +talking to each other. +Whether or not this actually sold computers +was a question we never discussed. + +Mel's job was to re-write +the blackjack program for the RPC-4000. +(Port? What does that mean?) +The new computer had a one-plus-one +addressing scheme, +in which each machine instruction, +in addition to the operation code +and the address of the needed operand, +had a second address that indicated where, on the revolving drum, +the next instruction was located. + +In modern parlance, +every single instruction was followed by a GO TO! +Put <i>that</i> in Pascal's pipe and smoke it. + +Mel loved the RPC-4000 +because he could optimize his code: +that is, locate instructions on the drum +so that just as one finished its job, +the next would be just arriving at the ``read head'' +and available for immediate execution. +There was a program to do that job, +an ``optimizing assembler'', +but Mel refused to use it. + +``You never know where it's going to put things'', +he explained, ``so you'd have to use separate constants''. + +It was a long time before I understood that remark. +Since Mel knew the numerical value +of every operation code, +and assigned his own drum addresses, +every instruction he wrote could also be considered +a numerical constant. +He could pick up an earlier ``add'' instruction, say, +and multiply by it, +if it had the right numeric value. +His code was not easy for someone else to modify. + +I compared Mel's hand-optimized programs +with the same code massaged by the optimizing assembler program, +and Mel's always ran faster. +That was because the ``top-down'' method of program design +hadn't been invented yet, +and Mel wouldn't have used it anyway. +He wrote the innermost parts of his program loops first, +so they would get first choice +of the optimum address locations on the drum. +The optimizing assembler wasn't smart enough to do it that way. + +Mel never wrote time-delay loops, either, +even when the balky Flexowriter +required a delay between output characters to work right. +He just located instructions on the drum +so each successive one was just <i>past</i> the read head +when it was needed; +the drum had to execute another complete revolution +to find the next instruction. +He coined an unforgettable term for this procedure. +Although ``optimum'' is an absolute term, +like ``unique'', it became common verbal practice +to make it relative: +``not quite optimum'' or ``less optimum'' +or ``not very optimum''. +Mel called the maximum time-delay locations +the ``most pessimum''. + +After he finished the blackjack program +and got it to run +(``Even the initializer is optimized'', +he said proudly), +he got a Change Request from the sales department. +The program used an elegant (optimized) +random number generator +to shuffle the ``cards'' and deal from the ``deck'', +and some of the salesmen felt it was too fair, +since sometimes the customers lost. +They wanted Mel to modify the program +so, at the setting of a sense switch on the console, +they could change the odds and let the customer win. + +Mel balked. +He felt this was patently dishonest, +which it was, +and that it impinged on his personal integrity as a programmer, +which it did, +so he refused to do it. +The Head Salesman talked to Mel, +as did the Big Boss and, at the boss's urging, +a few Fellow Programmers. +Mel finally gave in and wrote the code, +but he got the test backwards, +and, when the sense switch was turned on, +the program would cheat, winning every time. +Mel was delighted with this, +claiming his subconscious was uncontrollably ethical, +and adamantly refused to fix it. + +After Mel had left the company for greener pa$ture$, +the Big Boss asked me to look at the code +and see if I could find the test and reverse it. +Somewhat reluctantly, I agreed to look. +Tracking Mel's code was a real adventure. + +I have often felt that programming is an art form, +whose real value can only be appreciated +by another versed in the same arcane art; +there are lovely gems and brilliant coups +hidden from human view and admiration, sometimes forever, +by the very nature of the process. +You can learn a lot about an individual +just by reading through his code, +even in hexadecimal. +Mel was, I think, an unsung genius. + +Perhaps my greatest shock came +when I found an innocent loop that had no test in it. +No test. <i>None</i>. +Common sense said it had to be a closed loop, +where the program would circle, forever, endlessly. +Program control passed right through it, however, +and safely out the other side. +It took me two weeks to figure it out. + +The RPC-4000 computer had a really modern facility +called an index register. +It allowed the programmer to write a program loop +that used an indexed instruction inside; +each time through, +the number in the index register +was added to the address of that instruction, +so it would refer +to the next datum in a series. +He had only to increment the index register +each time through. +Mel never used it. + +Instead, he would pull the instruction into a machine register, +add one to its address, +and store it back. +He would then execute the modified instruction +right from the register. +The loop was written so this additional execution time +was taken into account --- +just as this instruction finished, +the next one was right under the drum's read head, +ready to go. +But the loop had no test in it. + +The vital clue came when I noticed +the index register bit, +the bit that lay between the address +and the operation code in the instruction word, +was turned on --- +yet Mel never used the index register, +leaving it zero all the time. +When the light went on it nearly blinded me. + +He had located the data he was working on +near the top of memory --- +the largest locations the instructions could address --- +so, after the last datum was handled, +incrementing the instruction address +would make it overflow. +The carry would add one to the +operation code, changing it to the next one in the instruction set: +a jump instruction. +Sure enough, the next program instruction was +in address location zero, +and the program went happily on its way. + +I haven't kept in touch with Mel, +so I don't know if he ever gave in to the flood of +change that has washed over programming techniques +since those long-gone days. +I like to think he didn't. +In any event, +I was impressed enough that I quit looking for the +offending test, +telling the Big Boss I couldn't find it. +He didn't seem surprised. + +When I left the company, +the blackjack program would still cheat +if you turned on the right sense switch, +and I think that's how it should be. +I didn't feel comfortable +hacking up the code of a Real Programmer. +</pre> + +<br> +<p><br> +</p> + +<p>This is one of hackerdom's great heroic epics, free verse or +no. In a few spare images it captures more about the esthetics +and psychology of hacking than all the scholarly volumes on the +subject put together. For an opposing point of view, see the +entry for <b><a href="#RealProgrammer">Real +Programmer</a></b>.</p> + +<p>[1992 postscript -- the author writes: "The original +submission to the net was not in free verse, nor any +approximation to it -- it was straight prose style, in +non-justified paragraphs. In bouncing around the net it +apparently got modified into the `free verse' form now popular. +In other words, it got hacked on the net. That seems appropriate, +somehow." The author adds that he likes the `free-verse' version +better...]</p> + +<p>[1999 update: Mel's last name is now known. The manual for the +LGP-30 refers to "Mel Kaye of Royal McBee who did the bulk of the +programming [...] of the ACT 1 system".]</p> + +<hr> +Node:<a name="AppendixB">Appendix B</a>, Next:<a rel="next" href="#AppendixC">Appendix C</a>, Previous:<a rel="previous" +href="#AppendixA">Appendix A</a>, Up:<a rel="up" href="#Top">Top</a> <br> + + +<h2>A Portrait of J. Random Hacker</h2> + +<p>This profile reflects detailed comments on an earlier `trial +balloon' version from about a hundred Usenet respondents. Where +comparatives are used, the implicit `other' is a randomly +selected segment of the non-hacker population of the same size as +hackerdom.</p> + +<p>An important point: Except in some relatively minor respects +such as slang vocabulary, hackers don't get to be the way they +are by imitating each other. Rather, it seems to be the case that +the combination of personality traits that makes a hacker so +conditions one's outlook on life that one tends to end up being +like other hackers whether one wants to or not (much as bizarrely +detailed similarities in behavior and preferences are found in +genetic twins raised separately).</p> + +<ul> +<li><a href="#GeneralAppearance">General Appearance</a>:</li> + +<li><a href="#Dress">Dress</a>:</li> + +<li><a href="#ReadingHabits">Reading Habits</a>:</li> + +<li><a href="#OtherInterests">Other Interests</a>:</li> + +<li><a href="#PhysicalActivityandSports">Physical Activity and Sports</a>:</li> + +<li><a href="#Education">Education</a>:</li> + +<li><a href="#ThingsHackersDetestandAvoid">Things Hackers Detest and Avoid</a>:</li> + +<li><a href="#Food">Food</a>:</li> + +<li><a href="#Politics">Politics</a>:</li> + +<li><a href="#GenderandEthnicity">Gender and Ethnicity</a>:</li> + +<li><a href="#Religion">Religion</a>:</li> + +<li><a href="#CeremonialChemicals">Ceremonial Chemicals</a>:</li> + +<li><a href="#CommunicationStyle">Communication Style</a>:</li> + +<li><a href="#GeographicalDistribution">Geographical Distribution</a>:</li> + +<li><a href="#SexualHabits">Sexual Habits</a>:</li> + +<li><a href="#PersonalityCharacteristics">Personality Characteristics</a>:</li> + +<li><a href="#WeaknessesoftheHackerPersonality">Weaknesses of the Hacker Personality</a>:</li> + +<li><a href="#Miscellaneous">Miscellaneous</a>:</li> +</ul> + +<hr> +Node:<a name="GeneralAppearance">General Appearance</a>, +Next:<a rel="next" href="#Dress">Dress</a>, Up:<a rel="up" href="#AppendixB">Appendix B</a> <br> + + +<h2>General Appearance</h2> + +<p>Intelligent. Scruffy. Intense. Abstracted. Surprisingly for a +sedentary profession, more hackers run to skinny than fat; both +extremes are more common than elsewhere. Tans are rare.</p> + +<hr> +Node:<a name="Dress">Dress</a>, Next:<a rel="next" href="#ReadingHabits">Reading Habits</a>, Previous:<a rel="previous" href="#GeneralAppearance">General Appearance</a>, +Up:<a rel="up" href="#AppendixB">Appendix B</a> <br> + + +<h2>Dress</h2> + +<p>Casual, vaguely post-hippie; T-shirts, jeans, running shoes, +Birkenstocks (or bare feet). Long hair, beards, and moustaches +are common. High incidence of tie-dye and intellectual or +humorous `slogan' T-shirts (only rarely computer related; that +would be too obvious).</p> + +<p>A substantial minority prefers `outdoorsy' clothing -- hiking +boots ("in case a mountain should suddenly spring up in the +machine room", as one famous parody put it), khakis, lumberjack +or chamois shirts, and the like.</p> + +<p>Very few actually fit the "National Lampoon" Nerd stereotype, +though it lingers on at MIT and may have been more common before +1975. At least since the late Seventies backpacks have been more +common than briefcases, and the hacker `look' has been more +whole-earth than whole-polyester.</p> + +<p>Hackers dress for comfort, function, and minimal maintenance +hassles rather than for appearance (some, perhaps unfortunately, +take this to extremes and neglect personal hygiene). They have a +very low tolerance of suits and other `business' attire; in fact, +it is not uncommon for hackers to quit a job rather than conform +to a dress code.</p> + +<p>Female hackers almost never wear visible makeup, and many use +none at all.</p> + +<hr> +Node:<a name="ReadingHabits">Reading Habits</a>, Next:<a rel="next" href="#OtherInterests">Other Interests</a>, Previous:<a +rel="previous" href="#Dress">Dress</a>, Up:<a rel="up" href="#AppendixB">Appendix B</a> <br> + + +<h2>Reading Habits</h2> + +<p>Omnivorous, but usually includes lots of science and science +fiction. The typical hacker household might subscribe to +"Analog", "Scientific American", "Whole-Earth Review", and +"Smithsonian" (most hackers ignore "Wired" and other +self-consciously `cyberpunk' magazines, considering them <b><a +href="#wannabee">wannabee</a></b> fodder). Hackers often have a +reading range that astonishes liberal arts people but tend not to +talk about it as much. Many hackers spend as much of their spare +time reading as the average American burns up watching TV, and +often keep shelves and shelves of well-thumbed books in their +homes.</p> + +<hr> +Node:<a name="OtherInterests">Other Interests</a>, Next:<a +rel="next" href="#PhysicalActivityandSports">Physical +Activity and Sports</a>, Previous:<a rel="previous" href="#ReadingHabits">Reading Habits</a>, Up:<a rel="up" href="#AppendixB">Appendix B</a> <br> + + +<h2>Other Interests</h2> + +<p>Some hobbies are widely shared and recognized as going with +the culture: science fiction, music, medievalism (in the active +form practiced by the Society for Creative Anachronism and +similar organizations), chess, go, backgammon, wargames, and +intellectual games of all kinds. (Role-playing games such as +Dungeons and Dragons used to be extremely popular among hackers +but they lost a bit of their luster as they moved into the +mainstream and became heavily commercialized. More recently, +"Magic: The Gathering" has been widely popular among hackers.) +Logic puzzles. Ham radio. Other interests that seem to correlate +less strongly but positively with hackerdom include linguistics +and theater teching.</p> + +<hr> +Node:<a name="PhysicalActivityandSports">Physical +Activity and Sports</a>, Next:<a rel="next" href="#Education">Education</a>, Previous:<a rel="previous" href="#OtherInterests">Other Interests</a>, Up:<a rel="up" href="#AppendixB">Appendix B</a> <br> + + +<h2>Physical Activity and Sports</h2> + +<p>Many (perhaps even most) hackers don't follow or do sports at +all and are determinedly anti-physical. Among those who do, +interest in spectator sports is low to non-existent; sports are +something one <i>does</i>, not something one watches on TV.</p> + +<p>Further, hackers avoid most team sports like the plague. +Volleyball was long a notable exception, perhaps because it's +non-contact and relatively friendly; Ultimate Frisbee has become +quite popular for similar reasons. Hacker sports are almost +always primarily self-competitive ones involving concentration, +stamina, and micromotor skills: martial arts, bicycling, auto +racing, kite flying, hiking, rock climbing, aviation, +target-shooting, sailing, caving, juggling, skiing, skating, +skydiving, scuba diving. Hackers' delight in techno-toys also +tends to draw them towards hobbies with nifty complicated +equipment that they can tinker with.</p> + +<p>The popularity of martial arts in the hacker culture deserves +special mention. Many observers have noted it, and the connection +has grown noticeably stronger over time. In the 1970s, many +hackers admired martial arts disciplines from a distance, sensing +a compatible ideal in their exaltation of skill through rigorous +self-discipline and concentration. As martial arts became +increasingly mainstreamed in the U.S. and other western +countries, hackers moved from admiring to doing in large numbers. +In 1997, for example, your humble editor recalls sitting down +with five strangers at the first Perl conference and discovering +that four of us were in active training in some sort of martial +art - and, what is more interesting, nobody at the table found +this particularly odd.</p> + +<p>Today (2000), martial arts seems to have become established as +the hacker exercise form of choice, and the martial-arts culture +combining skill-centered elitism with a willingness to let +anybody join seems a stronger parallel to hacker behavior than +ever. Common usages in hacker slang un-ironically analogize +programming to kung fu (thus, one hears talk of "code-fu" or in +reference to specific skills like "HTML-fu"). Albeit with +slightly more irony, today's hackers readily analogize +assimilation into the hacker culture with the plot of a Jet Li +movie: the aspiring newbie studies with masters of the tradition, +develops his art through deep meditation, ventures forth to +perform heroic feats of hacking, and eventually becomes a master +who trains the next generation of newbies.</p> + +<hr> +Node:<a name="Education">Education</a>, Next:<a rel="next" href="#ThingsHackersDetestandAvoid">Things Hackers Detest +and Avoid</a>, Previous:<a rel="previous" href="#PhysicalActivityandSports">Physical Activity and +Sports</a>, Up:<a rel="up" href="#AppendixB">Appendix B</a> +<br> + + +<h2>Education</h2> + +<p>Nearly all hackers past their teens are either college-degreed +or self-educated to an equivalent level. The self-taught hacker +is often considered (at least by other hackers) to be +better-motivated, and may be more respected, than his +school-shaped counterpart. Academic areas from which people often +gravitate into hackerdom include (besides the obvious computer +science and electrical engineering) physics, mathematics, +linguistics, and philosophy.</p> + +<hr> +Node:<a name="ThingsHackersDetestandAvoid">Things +Hackers Detest and Avoid</a>, Next:<a rel="next" href="#Food">Food</a>, Previous:<a rel="previous" href="#Education">Education</a>, Up:<a rel="up" href="#AppendixB">Appendix B</a> <br> + + +<h2>Things Hackers Detest and Avoid</h2> + +<p>IBM mainframes. All the works of Microsoft. Smurfs, Ewoks, and +other forms of offensive cuteness. Bureaucracies. Stupid people. +Easy listening music. Television (with occasional exceptions for +cartoons, movies, and good SF like "Star Trek" classic or Babylon +5). Business suits. Dishonesty. Incompetence. Boredom. COBOL. +BASIC. Character-based menu interfaces.</p> + +<hr> +Node:<a name="Food">Food</a>, Next:<a rel="next" href="#Politics">Politics</a>, Previous:<a rel="previous" href="#ThingsHackersDetestandAvoid">Things Hackers Detest +and Avoid</a>, Up:<a rel="up" href="#AppendixB">Appendix B</a> +<br> + + +<h2>Food</h2> + +<p>Ethnic. Spicy. Oriental, esp. Chinese and most esp. Szechuan, +Hunan, and Mandarin (hackers consider Cantonese vaguely +<i>déclassé</i>). Hackers prefer the exotic; for +example, the Japanese-food fans among them will eat with gusto +such delicacies as fugu (poisonous pufferfish) and whale. Thai +food has experienced flurries of popularity. Where available, +high-quality Jewish delicatessen food is much esteemed. A visible +minority of Southwestern and Pacific Coast hackers prefers +Mexican.</p> + +<p>For those all-night hacks, pizza and microwaved burritos are +big. Interestingly, though the mainstream culture has tended to +think of hackers as incorrigible junk-food junkies, many have at +least mildly health-foodist attitudes and are fairly +discriminating about what they eat. This may be generational; +anecdotal evidence suggests that the stereotype was more on the +mark before the early 1980s.</p> + +<hr> +Node:<a name="Politics">Politics</a>, Next:<a rel="next" href="#GenderandEthnicity">Gender and Ethnicity</a>, Previous:<a +rel="previous" href="#Food">Food</a>, Up:<a rel="up" href="#AppendixB">Appendix B</a> <br> + + +<h2>Politics</h2> + +<p>Vaguely liberal-moderate, except for the strong libertarian +contingent which rejects conventional left-right politics +entirely. The only safe generalization is that hackers tend to be +rather anti-authoritarian; thus, both conventional conservatism +and `hard' leftism are rare. Hackers are far more likely than +most non-hackers to either (a) be aggressively apolitical or (b) +entertain peculiar or idiosyncratic political ideas and actually +try to live by them day-to-day.</p> + +<hr> +Node:<a name="GenderandEthnicity">Gender and Ethnicity</a>, +Next:<a rel="next" href="#Religion">Religion</a>, Previous:<a +rel="previous" href="#Politics">Politics</a>, Up:<a rel="up" +href="#AppendixB">Appendix B</a> <br> + + +<h2>Gender and Ethnicity</h2> + +<p>Hackerdom is still predominantly male. However, the percentage +of women is clearly higher than the low-single-digit range +typical for technical professions, and female hackers are +generally respected and dealt with as equals.</p> + +<p>In the U.S., hackerdom is predominantly Caucasian with strong +minorities of Jews (East Coast) and Orientals (West Coast). The +Jewish contingent has exerted a particularly pervasive cultural +influence (see <b><a href="#Food">Food</a></b>, above, and note +that several common jargon terms are obviously mutated +Yiddish).</p> + +<p>The ethnic distribution of hackers is understood by them to be +a function of which ethnic groups tend to seek and value +education. Racial and ethnic prejudice is notably uncommon and +tends to be met with freezing contempt.</p> + +<p>When asked, hackers often ascribe their culture's gender- and +color-blindness to a positive effect of text-only network +channels, and this is doubtless a powerful influence. Also, the +ties many hackers have to AI research and SF literature may have +helped them to develop an idea of personhood that is inclusive +rather than exclusive -- after all, if one's imagination readily +grants full human rights to future AI programs, robots, dolphins, +and extraterrestrial aliens, mere color and gender can't seem +very important any more.</p> + +<hr> +Node:<a name="Religion">Religion</a>, Next:<a rel="next" href="#CeremonialChemicals">Ceremonial Chemicals</a>, Previous:<a +rel="previous" href="#GenderandEthnicity">Gender and +Ethnicity</a>, Up:<a rel="up" href="#AppendixB">Appendix B</a> +<br> + + +<h2>Religion</h2> + +<p>Agnostic. Atheist. Non-observant Jewish. Neo-pagan. Very +commonly, three or more of these are combined in the same person. +Conventional faith-holding Christianity is rare though not +unknown.</p> + +<p>Even hackers who identify with a religious affiliation tend to +be relaxed about it, hostile to organized religion in general and +all forms of religious bigotry in particular. Many enjoy `parody' +religions such as Discordianism and the Church of the +SubGenius.</p> + +<p>Also, many hackers are influenced to varying degrees by Zen +Buddhism or (less commonly) Taoism, and blend them easily with +their `native' religions.</p> + +<p>There is a definite strain of mystical, almost Gnostic +sensibility that shows up even among those hackers not actively +involved with neo-paganism, Discordianism, or Zen. Hacker +folklore that pays homage to `wizards' and speaks of incantations +and demons has too much psychological truthfulness about it to be +entirely a joke.</p> + +<hr> +Node:<a name="CeremonialChemicals">Ceremonial Chemicals</a>, +Next:<a rel="next" href="#CommunicationStyle">Communication +Style</a>, Previous:<a rel="previous" href="#Religion">Religion</a>, Up:<a rel="up" href="#AppendixB">Appendix B</a> <br> + + +<h2>Ceremonial Chemicals</h2> + +<p>Most hackers don't smoke tobacco, and use alcohol in +moderation if at all. However, there has been something of a +trend towards exotic beers since about 1995, especially among +younger Linux hackers apparently influenced by Linus Torvalds's +fondness for Guiness.</p> + +<p>Limited use of non-addictive psychedelic drugs, such as +cannabis, LSD, psilocybin, nitrous oxide, etc., used to be +relatively common and is still regarded with more tolerance than +in the mainstream culture. Use of `downers' and opiates, on the +other hand, appears to be particularly rare; hackers seem in +general to dislike drugs that make them stupid. But <b><a href="#onthegrippinghand">on the gripping hand</a></b>, many +hackers regularly wire up on caffeine and/or sugar for all-night +hacking runs.</p> + +<hr> +Node:<a name="CommunicationStyle">Communication Style</a>, +Next:<a rel="next" href="#GeographicalDistribution">Geographical Distribution</a>, +Previous:<a rel="previous" href="#CeremonialChemicals">Ceremonial Chemicals</a>, Up:<a rel="up" href="#AppendixB">Appendix B</a> <br> + + +<h2>Communication Style</h2> + +<p>See the discussions of speech and writing styles near the +beginning of this File. Though hackers often have poor +person-to-person communication skills, they are as a rule quite +sensitive to nuances of language and very precise in their use of +it. They are often better at writing than at speaking.</p> + +<hr> +Node:<a name="GeographicalDistribution">Geographical +Distribution</a>, Next:<a rel="next" href="#SexualHabits">Sexual Habits</a>, Previous:<a rel="previous" +href="#CommunicationStyle">Communication Style</a>, Up:<a rel="up" href="#AppendixB">Appendix B</a> <br> + + +<h2>Geographical Distribution</h2> + +<p>In the United States, hackerdom revolves on a Bay +Area-to-Boston axis; about half of the hard core seems to live +within a hundred miles of Cambridge (Massachusetts) or Berkeley +(California), although there are significant contingents in Los +Angeles, in the Pacific Northwest, and around Washington DC. +Hackers tend to cluster around large cities, especially +`university towns' such as the Raleigh-Durham area in North +Carolina or Princeton, New Jersey (this may simply reflect the +fact that many are students or ex-students living near their alma +maters).</p> + +<hr> +Node:<a name="SexualHabits">Sexual Habits</a>, Next:<a rel="next" href="#PersonalityCharacteristics">Personality +Characteristics</a>, Previous:<a rel="previous" href="#GeographicalDistribution">Geographical Distribution</a>, +Up:<a rel="up" href="#AppendixB">Appendix B</a> <br> + + +<h2>Sexual Habits</h2> + +<p>Hackerdom easily tolerates a much wider range of sexual and +lifestyle variation than the mainstream culture. It includes a +relatively large gay and bisexual contingent. Hackers are +somewhat more likely to live in polygynous or polyandrous +relationships, practice open marriage, or live in communes or +group houses. In this, as in general appearance, hackerdom +semi-consciously maintains `counterculture' values.</p> + +<hr> +Node:<a name="PersonalityCharacteristics">Personality +Characteristics</a>, Next:<a rel="next" href="#WeaknessesoftheHackerPersonality">Weaknesses of the +Hacker Personality</a>, Previous:<a rel="previous" href="#SexualHabits">Sexual Habits</a>, Up:<a rel="up" href="#AppendixB">Appendix B</a> <br> + + +<h2>Personality Characteristics</h2> + +<p>The most obvious common `personality' characteristics of +hackers are high intelligence, consuming curiosity, and facility +with intellectual abstractions. Also, most hackers are +`neophiles', stimulated by and appreciative of novelty +(especially intellectual novelty). Most are also relatively +individualistic and anti-conformist.</p> + +<p>Although high general intelligence is common among hackers, it +is not the <i>sine qua non</i> one might expect. Another trait is +probably even more important: the ability to mentally absorb, +retain, and reference large amounts of `meaningless' detail, +trusting to later experience to give it context and meaning. A +person of merely average analytical intelligence who has this +trait can become an effective hacker, but a creative genius who +lacks it will swiftly find himself outdistanced by people who +routinely upload the contents of thick reference manuals into +their brains. [During the production of the first book version of +this document, for example, I learned most of the rather complex +typesetting language TeX over about four working days, mainly by +inhaling Knuth's 477-page manual. My editor's flabbergasted +reaction to this genuinely surprised me, because years of +associating with hackers have conditioned me to consider such +performances routine and to be expected. --ESR]</p> + +<p>Contrary to stereotype, hackers are <i>not</i> usually +intellectually narrow; they tend to be interested in any subject +that can provide mental stimulation, and can often discourse +knowledgeably and even interestingly on any number of obscure +subjects -- if you can get them to talk at all, as opposed to, +say, going back to their hacking.</p> + +<p>It is noticeable (and contrary to many outsiders' +expectations) that the better a hacker is at hacking, the more +likely he or she is to have outside interests at which he or she +is more than merely competent.</p> + +<p>Hackers are `control freaks' in a way that has nothing to do +with the usual coercive or authoritarian connotations of the +term. In the same way that children delight in making model +trains go forward and back by moving a switch, hackers love +making complicated things like computers do nifty stuff for them. +But it has to be <i>their</i> nifty stuff. They don't like +tedium, nondeterminism, or most of the fussy, boring, ill-defined +little tasks that go with maintaining a normal existence. +Accordingly, they tend to be careful and orderly in their +intellectual lives and chaotic elsewhere. Their code will be +beautiful, even if their desks are buried in 3 feet of crap.</p> + +<p>Hackers are generally only very weakly motivated by +conventional rewards such as social approval or money. They tend +to be attracted by challenges and excited by interesting toys, +and to judge the interest of work or other activities in terms of +the challenges offered and the toys they get to play with.</p> + +<p>In terms of Myers-Briggs and equivalent psychometric systems, +hackerdom appears to concentrate the relatively rare INTJ and +INTP types; that is, introverted, intuitive, and thinker types +(as opposed to the extroverted-sensate personalities that +predominate in the mainstream culture). ENT[JP] types are also +concentrated among hackers but are in a minority.</p> + +<hr> +Node:<a name="WeaknessesoftheHackerPersonality">Weaknesses of the +Hacker Personality</a>, Next:<a rel="next" href="#Miscellaneous">Miscellaneous</a>, Previous:<a rel="previous" +href="#PersonalityCharacteristics">Personality +Characteristics</a>, Up:<a rel="up" href="#AppendixB">Appendix +B</a> <br> + + +<h2>Weaknesses of the Hacker Personality</h2> + +<p>Hackers have relatively little ability to identify emotionally +with other people. This may be because hackers generally aren't +much like `other people'. Unsurprisingly, hackers also tend +towards self-absorption, intellectual arrogance, and impatience +with people and tasks perceived to be wasting their time.</p> + +<p>As cynical as hackers sometimes wax about the amount of idiocy +in the world, they tend by reflex to assume that everyone is as +rational, `cool', and imaginative as they consider themselves. +This bias often contributes to weakness in communication skills. +Hackers tend to be especially poor at confrontation and +negotiation.</p> + +<p>Because of their passionate embrace of (what they consider to +be) the <b><a href="#RightThing">Right Thing</a></b>, hackers +can be unfortunately intolerant and bigoted on technical issues, +in marked contrast to their general spirit of camaraderie and +tolerance of alternative viewpoints otherwise. Old-time <b><a +href="#ITS">ITS</a></b> partisans look down on the ever-growing +hordes of <b><a href="#Unix">Unix</a></b> hackers; Unix +aficionados despise <b><a href="#VMS">VMS</a></b> and <b><a href="#MS-DOS">MS-DOS</a></b>; and hackers who are used to +conventional command-line user interfaces loudly loathe +mouse-and-menu based systems such as the Macintosh. Hackers who +don't indulge in <b><a href="#Usenet">Usenet</a></b> consider it +a huge waste of time and <b><a href="#bandwidth">bandwidth</a></b>; fans of old adventure games such +as <b><a href="#ADVENT">ADVENT</a></b> and <b><a href="#Zork">Zork</a></b> consider <b><a href="#MUD">MUD</a></b>s to +be glorified chat systems devoid of atmosphere or interesting +puzzles; hackers who are willing to devote endless hours to +Usenet or MUDs consider <b><a href="#IRC">IRC</a></b> to be a +<i>real</i> waste of time; IRCies think MUDs might be okay if +there weren't all those silly puzzles in the way. And, of course, +there are the perennial <b><a href="#holywars">holy +wars</a></b> -- <b><a href="#EMACS">EMACS</a></b> vs. <b><a href="#vi">vi</a></b>, <b><a href="#big-endian">big-endian</a></b> vs. +<b><a href="#little-endian">little-endian</a></b>, RISC vs. CISC, +etc., etc., etc. As in society at large, the intensity and +duration of these debates is usually inversely proportional to +the number of objective, factual arguments available to buttress +any position.</p> + +<p>As a result of all the above traits, many hackers have +difficulty maintaining stable relationships. At worst, they can +produce the classic <b><a href="#computergeek">computer +geek</a></b>: withdrawn, relationally incompetent, sexually +frustrated, and desperately unhappy when not submerged in his or +her craft. Fortunately, this extreme is far less common than +mainstream folklore paints it -- but almost all hackers will +recognize something of themselves in the unflattering paragraphs +above.</p> + +<p>Hackers are often monumentally disorganized and sloppy about +dealing with the physical world. Bills don't get paid on time, +clutter piles up to incredible heights in homes and offices, and +minor maintenance tasks get deferred indefinitely.</p> + +<p>1994-95's fad behavioral disease was a syndrome called +Attention Deficit Disorder (ADD), supposedly characterized by +(among other things) a combination of short attention span with +an ability to `hyperfocus' imaginatively on interesting tasks. In +1998-1999 another syndrome that is said to overlap with many +hacker traits entered popular awareness: Asperger's syndrome +(AS). This disorder is also sometimes called `high-function +autism', though researchers are divided on whether AS is in fact +a mild form of autism or a distinct syndrome with a different +etiology. AS patients exhibit mild to severe deficits in +interpreting facial and body-language cues and in modeling or +empathizing with others' emotions. Though some AS patients +exhibit mild retardation, others compensate for their deficits +with high intelligence and analytical ability, and frequently +seek out technical fields where problem-solving abilities are at +a premium and people skills are relatively unimportant. Both +syndromes are thought to relate to abnormalities in +neurotransmitter chemistry, especially the brain's processing of +serotonin.</p> + +<p>Many hackers have noticed that mainstream culture has shown a +tendency to pathologize and medicalize normal variations in +personality, especially those variations that make life more +complicated for authority figures and conformists. Thus, hackers +aware of the issue tend to be among those questioning whether ADD +and AS actually exist; and if so whether they are really +`diseases' rather than extremes of a normal genetic variation +like having freckles or being able to taste DPT. In either case, +they have a sneaking tendency to wonder if these syndromes are +over-diagnosed and over-treated. After all, people in authority +will always be inconvenienced by schoolchildren or workers or +citizens who are prickly, intelligent individualists - thus, any +social system that depends on authority relationships will tend +to helpfully ostracize and therapize and drug such `abnormal' +people until they are properly docile and stupid and +`well-socialized'.</p> + +<p>So hackers tend to believe they have good reason for +skepticism about clinical explanations of the hacker personality. +That being said, most would also concede that some hacker traits +coincide with indicators for ADD and AS - the status of caffeeine +as a hacker beverage of choice may be connected to the fact that +it bonds to the same neural receptors as Ritalin, the drug most +commonly prescribed for ADD. It is probably true that boosters of +both would find a rather higher rate of clinical ADD among +hackers than the supposedly mainstream-normal 3-5% (AS is rarer +and there are not yet good estimates of incidence as of +2000).</p> + +<hr> +Node:<a name="Miscellaneous">Miscellaneous</a>, Previous:<a rel="previous" href="#WeaknessesoftheHackerPersonality">Weaknesses of the +Hacker Personality</a>, Up:<a rel="up" href="#AppendixB">Appendix B</a> <br> + + +<h2>Miscellaneous</h2> + +<p>Hackers are more likely to have cats than dogs (in fact, it is +widely grokked that cats have the hacker nature). Many drive +incredibly decrepit heaps and forget to wash them; richer ones +drive spiffy Porsches and RX-7s and then forget to have them +washed. Almost all hackers have terribly bad handwriting, and +often fall into the habit of block-printing everything like +junior draftsmen.</p> + +<hr> +Node:<a name="AppendixC">Appendix C</a>, Next:<a rel="next" +href="#Bibliography">Bibliography</a>, Previous:<a rel="previous" +href="#AppendixB">Appendix B</a>, Up:<a rel="up" href="#Top">Top</a> <br> + + +<h2>Helping Hacker Culture Grow</h2> + +<p>If you enjoyed the Jargon File, please help the culture that +created it grow and flourish. Here are several ways you can +help:</p> + +<p>• If you are a writer or journalist, don't say or write +<b><a href="#hacker">hacker</a></b> when you mean <b><a href="#cracker">cracker</a></b>. If you work with writers or +journalists, educate them on this issue and push them to do the +right thing. If you catch a newspaper or magazine abusing the +work `hacker', write them and straighten them out (this appendix +includes a model letter).</p> + +<p>• If you're a techie or computer hobbyist, get involved +with one of the free Unixes. Toss out that lame Microsoft OS, or +confine it to one disk partition and put Linux or FreeBSD or +NetBSD on the other one. And the next time your friend or boss is +thinking about some proprietary software `solution' that costs +more than it's worth, be ready to blow the competition away with +open-source software running over a Unix.</p> + +<p>• Contribute to organizations like the Free Software +Foundation that promote the production of high-quality free and +open-source software. You can reach the Free Software Foundation +at <i>gnu@gnu.org</i>, by phone at +1-617-542-5942, or by +snail-mail at 59 Temple Place, Suite 330, Boston, MA 02111-1307 +USA.</p> + +<p>• Support the League for Programming Freedom, which +opposes over-broad software patents that constantly threaten to +blow up in hackers' faces, preventing them from developing +innovative software for tomorrow's needs. You can reach the +League for Programming Freedom at <i>lpf@uunet.uu.net</i>. by +phone at +1 617 621 7084, or by snail-mail at 1 Kendall Square +#143, P.O.Box 9171, Cambridge, Massachusetts 02139 USA.</p> + +<p> +• Join the continuing fight against Internet censorship, visit the Center for +Democracy and Technology Home Page at http://www.cdt.org. +</p> + +<p> +• If you do nothing else, please help fight government attempts to seize +political control of Internet content and restrict strong cryptography. The +so-called `Communications Decency Act' was declared unconstitutional by the +Supreme Court, but U.S. cryptography policy still infringes our First Amendment +rights. Surf to the Center for Democracy and technology's home page at +http://www.cdt.org to see what you can do to help fight censorship of the net. +</p> + +<p>Here's the text of a letter RMS wrote to the Wall Street +Journal to complain about their policy of using "hacker" only in +a pejorative sense. We hear that most major newspapers have the +same policy. If you'd like to help change this situation, send +your favorite newspaper the same letter - or, better yet, write +your own letter.</p> + +<blockquote>Dear Editor: + +<p>This letter is not meant for publication, although you can +publish it if you wish. It is meant specifically for you, the +editor, not the public.</p> + +<p>I am a hacker. That is to say, I enjoy playing with computers +-- working with, learning about, and writing clever computer +programs. I am not a cracker; I don't make a practice of breaking +computer security.</p> + +<p>There's nothing shameful about the hacking I do. But when I +tell people I am a hacker, people think I'm admitting something +naughty -- because newspapers such as yours misuse the word +"hacker", giving the impression that it means "security breaker" +and nothing else. You are giving hackers a bad name.</p> + +<p>The saddest thing is that this problem is perpetuated +deliberately. Your reporters know the difference between "hacker" +and "security breaker". They know how to make the distinction, +but you don't let them! You insist on using "hacker" +pejoratively. When reporters try to use another word, you change +it. When reporters try to explain the other meanings, you cut +it.</p> + +<p>Of course, you have a reason. You say that readers have become +used to your insulting usage of "hacker", so that you cannot +change it now. Well, you can't undo past mistakes today; but that +is no excuse to repeat them tomorrow.</p> + +<p>If I were what you call a "hacker", at this point I would +threaten to crack your computer and crash it. But I am a hacker, +not a cracker. I don't do that kind of thing! I have enough +computers to play with at home and at work; I don't need yours. +Besides, it's not my way to respond to insults with violence. My +response is this letter.</p> + +<p>You owe hackers an apology; but more than that, you owe us +ordinary respect.</p> + +<p>Sincerely, etc.</p> +</blockquote> + +<hr> +Node:<a name="Bibliography">Bibliography</a>, Previous:<a rel="previous" href="#AppendixC">Appendix C</a>, Up:<a rel="up" +href="#Top">Top</a> <br> + + +<h2>Bibliography</h2> + +<p>Here are some other books you can read to help you understand +the hacker mindset.<br> +</p> + +<p> +Escher, Bach: An Eternal Golden Braid<b>Gödel, Escher, Bach: An Eternal Golden +Braid</b><br> +Douglas Hofstadter<br> +Basic Books, 1979<br> +ISBN 0-394-74502-7 +</p> + +<p>This book reads like an intellectual Grand Tour of hacker +preoccupations. Music, mathematical logic, programming, +speculations on the nature of intelligence, biology, and Zen are +woven into a brilliant tapestry themed on the concept of encoded +self-reference. The perfect left-brain companion to +"Illuminatus".<br> +</p> + +<p> +<b>Illuminatus!</b><br> + I. "The Eye in the Pyramid"<br> + II. "The Golden Apple"<br> + III. "Leviathan".<br> +Robert Shea and Robert Anton Wilson<br> +Dell, 1988<br> +ISBN 0-440-53981-1</p> + +<p>This work of alleged fiction is an incredible +berserko-surrealist rollercoaster of world-girdling conspiracies, +intelligent dolphins, the fall of Atlantis, who really killed +JFK, sex, drugs, rock'n'roll, and the Cosmic Giggle Factor. First +published in three volumes, but there is now a one-volume trade +paperback, carried by most chain bookstores under SF. The perfect +right-brain companion to Hofstadter's "Gödel, Escher, Bach". +See <b><a href="#Eris">Eris</a></b>, <b><a href="#Discordianism">Discordianism</a></b>, <b><a href="#randomnumbers">random numbers</a></b>, <b><a href="#ChurchoftheSubGenius">Church of the +SubGenius</a></b>.<br> +</p> + +<p> +<a name="TheHitchhikersGuidetotheGalaxy"></a><b>The +Hitchhiker's Guide to the Galaxy</b><br> +Douglas Adams<br> +Pocket Books, 1981<br> +ISBN 0-671-46149-4</p> + +<p>This `Monty Python in Space' spoof of SF genre traditions has +been popular among hackers ever since the original British radio +show. Read it if only to learn about Vogons (see <b><a href="#bogon">bogon</a></b>) and the significance of the number 42 +(see <b><a href="#randomnumbers">random numbers</a></b>) -- +and why the winningest chess program of 1990 was called `Deep +Thought'.<br> +</p> + +<p> +<b>The Tao of Programming</b><br> +James Geoffrey<br> +Infobooks, 1987<br> +ISBN 0-931137-07-1</p> + +<p>This gentle, funny spoof of the "Tao Te Ching" contains much +that is illuminating about the hacker way of thought. "When you +have learned to snatch the error code from the trap frame, it +will be time for you to leave."<br> +</p> + +<p> +<b>Hackers</b><br> +Steven Levy<br> +Anchor/Doubleday 1984<br> +ISBN 0-385-19195-2</p> + +<p>Levy's book is at its best in describing the early MIT hackers +at the Model Railroad Club and the early days of the +microcomputer revolution. He never understood Unix or the +networks, though, and his enshrinement of Richard Stallman as +"the last true hacker" turns out (thankfully) to have been quite +misleading. Despite being a bit dated and containing some minor +errors (many fixed in the paperback edition), this remains a +useful and stimulating book that captures the feel of several +important hacker subcultures.<br> +</p> + +<p> +<b>The Computer Contradictionary</b><br> +Stan Kelly-Bootle<br> +MIT Press, 1995<br> +ISBN 0-262-61112-0</p> + +<p>This pastiche of Ambrose Bierce's famous work is similar in +format to the Jargon File (and quotes several entries from +TNHD-2) but somewhat different in tone and intent. It is more +satirical and less anthropological, and is largely a product of +the author's literate and quirky imagination. For example, it +defines `computer science' as "a study akin to numerology and +astrology, but lacking the precision of the former and the +success of the latter" and `implementation' as "The fruitless +struggle by the talented and underpaid to fulfill promises made +by the rich and ignorant"; `flowchart' becomes "to obfuscate a +problem with esoteric cartoons". Revised and expanded from "The +Devil's DP Dictionary", McGraw-Hill 1981, ISBN 0-07-034022-6; +that work had some stylistic influence on TNHD-1.<br> +</p> + +<p><b>The Devouring Fungus: Tales from the Computer Age</b><br> +Karla Jennings<br> +Norton, 1990<br> +ISBN 0-393-30732-8</p> + +<p>The author of this pioneering compendium knits together a +great deal of computer- and hacker-related folklore with good +writing and a few well-chosen cartoons. She has a keen eye for +the human aspects of the lore and is very good at illuminating +the psychology and evolution of hackerdom. Unfortunately, a +number of small errors and awkwardnesses suggest that she didn't +have the final manuscript checked over by a native speaker; the +glossary in the back is particularly embarrassing, and at least +one classic tale (the Magic Switch story, retold here under <b><a +href="#AStoryAboutMagic">A Story About Magic</a></b> in +Appendix A is given in incomplete and badly mangled form. +Nevertheless, this book is a win overall and can be enjoyed by +hacker and non-hacker alike.<br> +</p> + +<p> +<b>The Soul of a New Machine</b><br> +Tracy Kidder<br> +Little, Brown, 1981<br> +(paperback: Avon, 1982<br> +ISBN 0-380-59931-7)</p> + +<p>This book (a 1982 Pulitzer Prize winner) documents the +adventure of the design of a new Data General computer, the +MV-8000 Eagle. It is an amazingly well-done portrait of the +hacker mindset -- although largely the hardware hacker -- done by +a complete outsider. It is a bit thin in spots, but with enough +technical information to be entertaining to the serious hacker +while providing non-technical people a view of what day-to-day +life can be like -- the fun, the excitement, the disasters. +During one period, when the microcode and logic were glitching at +the nanosecond level, one of the overworked engineers departed +the company, leaving behind a note on his terminal as his letter +of resignation: "I am going to a commune in Vermont and will deal +with no unit of time shorter than a season."<br> +</p> + +<p> +<b>Life with UNIX: a Guide for Everyone</b><br> +Don Libes and Sandy Ressler<br> +Prentice-Hall, 1989<br> +ISBN 0-13-536657-7</p> + +<p>The authors of this book set out to tell you all the things +about Unix that tutorials and technical books won't. The result +is gossipy, funny, opinionated, downright weird in spots, and +invaluable. Along the way they expose you to enough of Unix's +history, folklore and humor to qualify as a first-class source +for these things. Because so much of today's hackerdom is +involved with Unix, this in turn illuminates many of its in-jokes +and preoccupations.<br> +</p> + +<p> +<b>True Names <small>...</small> and Other Dangers</b><br> +Vernor Vinge<br> +Baen Books, 1987<br> +ISBN 0-671-65363-6</p> + +<p>Hacker demigod Richard Stallman used to say that the title +story of this book "expresses the spirit of hacking best". Until +the subject of the next entry came out, it was hard to even +nominate another contender. The other stories in this collection +are also fine work by an author who has since won multiple Hugos +and is one of today's very best practitioners of hard SF.<br> +</p> + +<p> +<b>Snow Crash</b><br> +Neal Stephenson<br> +Bantam, 1992<br> +ISBN 0-553-56261-4</p> + +<p>Stephenson's epic, comic cyberpunk novel is deeply knowing +about the hacker psychology and its foibles in a way no other +author of fiction has ever even approached. His imagination, his +grasp of the relevant technical details, and his ability to +communicate the excitement of hacking and its results are +astonishing, delightful, and (so far) unsurpassed.<br> +</p> + +<p><b>Cyberpunk: Outlaws and Hackers on the Computer +Frontier</b><br> +Katie Hafner & John Markoff<br> +Simon & Schuster 1991<br> +ISBN 0-671-68322-5</p> + +<p>This book gathers narratives about the careers of three +notorious crackers into a clear-eyed but sympathetic portrait of +hackerdom's dark side. The principals are Kevin Mitnick, "Pengo" +and "Hagbard" of the Chaos Computer Club, and Robert T. Morris +(see <b><a href="#RTM">RTM</a></b>, sense 2) . Markoff and Hafner +focus as much on their psychologies and motivations as on the +details of their exploits, but don't slight the latter. The +result is a balanced and fascinating account, particularly useful +when read immediately before or after Cliff Stoll's <b><a href="#TheCuckoosEgg">The Cuckoo's Egg</a></b>. It is +especially instructive to compare RTM, a true hacker who +blundered, with the sociopathic phone-freak Mitnick and the +alienated, drug-addled crackers who made the Chaos Club +notorious. The gulf between <b><a href="#wizard">wizard</a></b> +and <b><a href="#wannabee">wannabee</a></b> has seldom been made +more obvious.<br> +</p> + +<p> +<b>Technobabble</b><br> +John Barry<br> +MIT Press 1991<br> +ISBN 0-262-02333-4</p> + +<p>Barry's book takes a critical and humorous look at the +`technobabble' of acronyms, neologisms, hyperbole, and metaphor +spawned by the computer industry. Though he discusses some of the +same mechanisms of jargon formation that occur in hackish, most +of what he chronicles is actually suit-speak -- the obfuscatory +language of press releases, marketroids, and Silicon Valley CEOs +rather than the playful jargon of hackers (most of whom wouldn't +be caught dead uttering the kind of pompous, passive-voiced word +salad he deplores).<br> +</p> + +<p><a name="TheCuckoosEgg"></a><b>The Cuckoo's Egg</b><br> +Clifford Stoll<br> +Doubleday 1989<br> +ISBN 0-385-24946-2</p> + +<p>Clifford Stoll's absorbing tale of how he tracked Markus Hess +and the Chaos Club cracking ring nicely illustrates the +difference between `hacker' and `cracker'. Stoll's portrait of +himself, his lady Martha, and his friends at Berkeley and on the +Internet paints a marvelously vivid picture of how hackers and +the people around them like to live and how they think.</p> + +<pre> +#===================== THE JARGON FILE ENDS HERE ====================# +</pre> + +<pre> + + + + + +End of the Project Gutenberg EBook of The New Hacker's Dictionary version 4.2.2, by various editors + +*** END OF THIS PROJECT GUTENBERG EBOOK THE NEW HACKER'S DICTIONARY 4.2.2 *** + +***** This file should be named 3008-h.htm or 3008-h.zip ***** +This and all associated files of various formats will be found in: + http://www.gutenberg.org/3/0/0/3008/ + +Updated editions will replace the previous one--the old editions will +be renamed. + +Creating the works from print editions not protected by U.S. copyright +law means that no one owns a United States copyright in these works, +so the Foundation (and you!) can copy and distribute it in the United +States without permission and without paying copyright +royalties. Special rules, set forth in the General Terms of Use part +of this license, apply to copying and distributing Project +Gutenberg-tm electronic works to protect the PROJECT GUTENBERG-tm +concept and trademark. Project Gutenberg is a registered trademark, +and may not be used if you charge for the eBooks, unless you receive +specific permission. If you do not charge anything for copies of this +eBook, complying with the rules is very easy. You may use this eBook +for nearly any purpose such as creation of derivative works, reports, +performances and research. They may be modified and printed and given +away--you may do practically ANYTHING in the United States with eBooks +not protected by U.S. copyright law. Redistribution is subject to the +trademark license, especially commercial redistribution. + +START: FULL LICENSE + +THE FULL PROJECT GUTENBERG LICENSE +PLEASE READ THIS BEFORE YOU DISTRIBUTE OR USE THIS WORK + +To protect the Project Gutenberg-tm mission of promoting the free +distribution of electronic works, by using or distributing this work +(or any other work associated in any way with the phrase "Project +Gutenberg"), you agree to comply with all the terms of the Full +Project Gutenberg-tm License available with this file or online at +www.gutenberg.org/license. + +Section 1. General Terms of Use and Redistributing Project +Gutenberg-tm electronic works + +1.A. By reading or using any part of this Project Gutenberg-tm +electronic work, you indicate that you have read, understand, agree to +and accept all the terms of this license and intellectual property +(trademark/copyright) agreement. If you do not agree to abide by all +the terms of this agreement, you must cease using and return or +destroy all copies of Project Gutenberg-tm electronic works in your +possession. If you paid a fee for obtaining a copy of or access to a +Project Gutenberg-tm electronic work and you do not agree to be bound +by the terms of this agreement, you may obtain a refund from the +person or entity to whom you paid the fee as set forth in paragraph +1.E.8. + +1.B. "Project Gutenberg" is a registered trademark. It may only be +used on or associated in any way with an electronic work by people who +agree to be bound by the terms of this agreement. There are a few +things that you can do with most Project Gutenberg-tm electronic works +even without complying with the full terms of this agreement. See +paragraph 1.C below. There are a lot of things you can do with Project +Gutenberg-tm electronic works if you follow the terms of this +agreement and help preserve free future access to Project Gutenberg-tm +electronic works. See paragraph 1.E below. + +1.C. The Project Gutenberg Literary Archive Foundation ("the +Foundation" or PGLAF), owns a compilation copyright in the collection +of Project Gutenberg-tm electronic works. Nearly all the individual +works in the collection are in the public domain in the United +States. If an individual work is unprotected by copyright law in the +United States and you are located in the United States, we do not +claim a right to prevent you from copying, distributing, performing, +displaying or creating derivative works based on the work as long as +all references to Project Gutenberg are removed. Of course, we hope +that you will support the Project Gutenberg-tm mission of promoting +free access to electronic works by freely sharing Project Gutenberg-tm +works in compliance with the terms of this agreement for keeping the +Project Gutenberg-tm name associated with the work. You can easily +comply with the terms of this agreement by keeping this work in the +same format with its attached full Project Gutenberg-tm License when +you share it without charge with others. + +1.D. The copyright laws of the place where you are located also govern +what you can do with this work. Copyright laws in most countries are +in a constant state of change. If you are outside the United States, +check the laws of your country in addition to the terms of this +agreement before downloading, copying, displaying, performing, +distributing or creating derivative works based on this work or any +other Project Gutenberg-tm work. The Foundation makes no +representations concerning the copyright status of any work in any +country outside the United States. + +1.E. Unless you have removed all references to Project Gutenberg: + +1.E.1. The following sentence, with active links to, or other +immediate access to, the full Project Gutenberg-tm License must appear +prominently whenever any copy of a Project Gutenberg-tm work (any work +on which the phrase "Project Gutenberg" appears, or with which the +phrase "Project Gutenberg" is associated) is accessed, displayed, +performed, viewed, copied or distributed: + + This eBook is for the use of anyone anywhere in the United States and + most other parts of the world at no cost and with almost no + restrictions whatsoever. You may copy it, give it away or re-use it + under the terms of the Project Gutenberg License included with this + eBook or online at www.gutenberg.org. If you are not located in the + United States, you'll have to check the laws of the country where you + are located before using this ebook. + +1.E.2. If an individual Project Gutenberg-tm electronic work is +derived from texts not protected by U.S. copyright law (does not +contain a notice indicating that it is posted with permission of the +copyright holder), the work can be copied and distributed to anyone in +the United States without paying any fees or charges. If you are +redistributing or providing access to a work with the phrase "Project +Gutenberg" associated with or appearing on the work, you must comply +either with the requirements of paragraphs 1.E.1 through 1.E.7 or +obtain permission for the use of the work and the Project Gutenberg-tm +trademark as set forth in paragraphs 1.E.8 or 1.E.9. + +1.E.3. If an individual Project Gutenberg-tm electronic work is posted +with the permission of the copyright holder, your use and distribution +must comply with both paragraphs 1.E.1 through 1.E.7 and any +additional terms imposed by the copyright holder. Additional terms +will be linked to the Project Gutenberg-tm License for all works +posted with the permission of the copyright holder found at the +beginning of this work. + +1.E.4. Do not unlink or detach or remove the full Project Gutenberg-tm +License terms from this work, or any files containing a part of this +work or any other work associated with Project Gutenberg-tm. + +1.E.5. Do not copy, display, perform, distribute or redistribute this +electronic work, or any part of this electronic work, without +prominently displaying the sentence set forth in paragraph 1.E.1 with +active links or immediate access to the full terms of the Project +Gutenberg-tm License. + +1.E.6. You may convert to and distribute this work in any binary, +compressed, marked up, nonproprietary or proprietary form, including +any word processing or hypertext form. However, if you provide access +to or distribute copies of a Project Gutenberg-tm work in a format +other than "Plain Vanilla ASCII" or other format used in the official +version posted on the official Project Gutenberg-tm web site +(www.gutenberg.org), you must, at no additional cost, fee or expense +to the user, provide a copy, a means of exporting a copy, or a means +of obtaining a copy upon request, of the work in its original "Plain +Vanilla ASCII" or other form. Any alternate format must include the +full Project Gutenberg-tm License as specified in paragraph 1.E.1. + +1.E.7. Do not charge a fee for access to, viewing, displaying, +performing, copying or distributing any Project Gutenberg-tm works +unless you comply with paragraph 1.E.8 or 1.E.9. + +1.E.8. You may charge a reasonable fee for copies of or providing +access to or distributing Project Gutenberg-tm electronic works +provided that + +* You pay a royalty fee of 20% of the gross profits you derive from + the use of Project Gutenberg-tm works calculated using the method + you already use to calculate your applicable taxes. The fee is owed + to the owner of the Project Gutenberg-tm trademark, but he has + agreed to donate royalties under this paragraph to the Project + Gutenberg Literary Archive Foundation. Royalty payments must be paid + within 60 days following each date on which you prepare (or are + legally required to prepare) your periodic tax returns. Royalty + payments should be clearly marked as such and sent to the Project + Gutenberg Literary Archive Foundation at the address specified in + Section 4, "Information about donations to the Project Gutenberg + Literary Archive Foundation." + +* You provide a full refund of any money paid by a user who notifies + you in writing (or by e-mail) within 30 days of receipt that s/he + does not agree to the terms of the full Project Gutenberg-tm + License. You must require such a user to return or destroy all + copies of the works possessed in a physical medium and discontinue + all use of and all access to other copies of Project Gutenberg-tm + works. + +* You provide, in accordance with paragraph 1.F.3, a full refund of + any money paid for a work or a replacement copy, if a defect in the + electronic work is discovered and reported to you within 90 days of + receipt of the work. + +* You comply with all other terms of this agreement for free + distribution of Project Gutenberg-tm works. + +1.E.9. If you wish to charge a fee or distribute a Project +Gutenberg-tm electronic work or group of works on different terms than +are set forth in this agreement, you must obtain permission in writing +from both the Project Gutenberg Literary Archive Foundation and The +Project Gutenberg Trademark LLC, the owner of the Project Gutenberg-tm +trademark. Contact the Foundation as set forth in Section 3 below. + +1.F. + +1.F.1. Project Gutenberg volunteers and employees expend considerable +effort to identify, do copyright research on, transcribe and proofread +works not protected by U.S. copyright law in creating the Project +Gutenberg-tm collection. Despite these efforts, Project Gutenberg-tm +electronic works, and the medium on which they may be stored, may +contain "Defects," such as, but not limited to, incomplete, inaccurate +or corrupt data, transcription errors, a copyright or other +intellectual property infringement, a defective or damaged disk or +other medium, a computer virus, or computer codes that damage or +cannot be read by your equipment. + +1.F.2. LIMITED WARRANTY, DISCLAIMER OF DAMAGES - Except for the "Right +of Replacement or Refund" described in paragraph 1.F.3, the Project +Gutenberg Literary Archive Foundation, the owner of the Project +Gutenberg-tm trademark, and any other party distributing a Project +Gutenberg-tm electronic work under this agreement, disclaim all +liability to you for damages, costs and expenses, including legal +fees. YOU AGREE THAT YOU HAVE NO REMEDIES FOR NEGLIGENCE, STRICT +LIABILITY, BREACH OF WARRANTY OR BREACH OF CONTRACT EXCEPT THOSE +PROVIDED IN PARAGRAPH 1.F.3. YOU AGREE THAT THE FOUNDATION, THE +TRADEMARK OWNER, AND ANY DISTRIBUTOR UNDER THIS AGREEMENT WILL NOT BE +LIABLE TO YOU FOR ACTUAL, DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE OR +INCIDENTAL DAMAGES EVEN IF YOU GIVE NOTICE OF THE POSSIBILITY OF SUCH +DAMAGE. + +1.F.3. LIMITED RIGHT OF REPLACEMENT OR REFUND - If you discover a +defect in this electronic work within 90 days of receiving it, you can +receive a refund of the money (if any) you paid for it by sending a +written explanation to the person you received the work from. If you +received the work on a physical medium, you must return the medium +with your written explanation. The person or entity that provided you +with the defective work may elect to provide a replacement copy in +lieu of a refund. If you received the work electronically, the person +or entity providing it to you may choose to give you a second +opportunity to receive the work electronically in lieu of a refund. If +the second copy is also defective, you may demand a refund in writing +without further opportunities to fix the problem. + +1.F.4. Except for the limited right of replacement or refund set forth +in paragraph 1.F.3, this work is provided to you 'AS-IS', WITH NO +OTHER WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT +LIMITED TO WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PURPOSE. + +1.F.5. Some states do not allow disclaimers of certain implied +warranties or the exclusion or limitation of certain types of +damages. If any disclaimer or limitation set forth in this agreement +violates the law of the state applicable to this agreement, the +agreement shall be interpreted to make the maximum disclaimer or +limitation permitted by the applicable state law. The invalidity or +unenforceability of any provision of this agreement shall not void the +remaining provisions. + +1.F.6. INDEMNITY - You agree to indemnify and hold the Foundation, the +trademark owner, any agent or employee of the Foundation, anyone +providing copies of Project Gutenberg-tm electronic works in +accordance with this agreement, and any volunteers associated with the +production, promotion and distribution of Project Gutenberg-tm +electronic works, harmless from all liability, costs and expenses, +including legal fees, that arise directly or indirectly from any of +the following which you do or cause to occur: (a) distribution of this +or any Project Gutenberg-tm work, (b) alteration, modification, or +additions or deletions to any Project Gutenberg-tm work, and (c) any +Defect you cause. + +Section 2. Information about the Mission of Project Gutenberg-tm + +Project Gutenberg-tm is synonymous with the free distribution of +electronic works in formats readable by the widest variety of +computers including obsolete, old, middle-aged and new computers. It +exists because of the efforts of hundreds of volunteers and donations +from people in all walks of life. + +Volunteers and financial support to provide volunteers with the +assistance they need are critical to reaching Project Gutenberg-tm's +goals and ensuring that the Project Gutenberg-tm collection will +remain freely available for generations to come. In 2001, the Project +Gutenberg Literary Archive Foundation was created to provide a secure +and permanent future for Project Gutenberg-tm and future +generations. To learn more about the Project Gutenberg Literary +Archive Foundation and how your efforts and donations can help, see +Sections 3 and 4 and the Foundation information page at +www.gutenberg.org + + + +Section 3. Information about the Project Gutenberg Literary Archive Foundation + +The Project Gutenberg Literary Archive Foundation is a non profit +501(c)(3) educational corporation organized under the laws of the +state of Mississippi and granted tax exempt status by the Internal +Revenue Service. The Foundation's EIN or federal tax identification +number is 64-6221541. Contributions to the Project Gutenberg Literary +Archive Foundation are tax deductible to the full extent permitted by +U.S. federal laws and your state's laws. + +The Foundation's principal office is in Fairbanks, Alaska, with the +mailing address: PO Box 750175, Fairbanks, AK 99775, but its +volunteers and employees are scattered throughout numerous +locations. Its business office is located at 809 North 1500 West, Salt +Lake City, UT 84116, (801) 596-1887. Email contact links and up to +date contact information can be found at the Foundation's web site and +official page at www.gutenberg.org/contact + +For additional contact information: + + Dr. Gregory B. Newby + Chief Executive and Director + gbnewby@pglaf.org + +Section 4. Information about Donations to the Project Gutenberg +Literary Archive Foundation + +Project Gutenberg-tm depends upon and cannot survive without wide +spread public support and donations to carry out its mission of +increasing the number of public domain and licensed works that can be +freely distributed in machine readable form accessible by the widest +array of equipment including outdated equipment. Many small donations +($1 to $5,000) are particularly important to maintaining tax exempt +status with the IRS. + +The Foundation is committed to complying with the laws regulating +charities and charitable donations in all 50 states of the United +States. Compliance requirements are not uniform and it takes a +considerable effort, much paperwork and many fees to meet and keep up +with these requirements. We do not solicit donations in locations +where we have not received written confirmation of compliance. To SEND +DONATIONS or determine the status of compliance for any particular +state visit www.gutenberg.org/donate + +While we cannot and do not solicit contributions from states where we +have not met the solicitation requirements, we know of no prohibition +against accepting unsolicited donations from donors in such states who +approach us with offers to donate. + +International donations are gratefully accepted, but we cannot make +any statements concerning tax treatment of donations received from +outside the United States. U.S. laws alone swamp our small staff. + +Please check the Project Gutenberg Web pages for current donation +methods and addresses. Donations are accepted in a number of other +ways including checks, online payments and credit card donations. To +donate, please visit: www.gutenberg.org/donate + +Section 5. General Information About Project Gutenberg-tm electronic works. + +Professor Michael S. Hart was the originator of the Project +Gutenberg-tm concept of a library of electronic works that could be +freely shared with anyone. For forty years, he produced and +distributed Project Gutenberg-tm eBooks with only a loose network of +volunteer support. + +Project Gutenberg-tm eBooks are often created from several printed +editions, all of which are confirmed as not protected by copyright in +the U.S. unless a copyright notice is included. Thus, we do not +necessarily keep eBooks in compliance with any particular paper +edition. + +Most people start at our Web site which has the main PG search +facility: www.gutenberg.org + +This Web site includes information about Project Gutenberg-tm, +including how to make donations to the Project Gutenberg Literary +Archive Foundation, how to help produce our new eBooks, and how to +subscribe to our email newsletter to hear about new eBooks. + + + +</pre> + + +</body> +</html> + + + |