The Hacker's Dictionary - - (the best novels to read .txt) 📗

be unlikely or impossible. Sometimes used to indicate that the speaker is interested in accomplishing the task, but believes that the opportunity will not arise. "I'll implement the automatic layout stuff in my copious free time." 2. [Archly] Time reserved for bogus or otherwise idiotic tasks, such as implementation of {chrome}, or the stroking of {suit}s. "I'll get back to him on that feature in my copious free time."

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

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

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

:copyleft: /kop'ee-left/ [play on copyright'] n. 1. The copyright notice (General Public License') carried by {GNU}

{EMACS} and other Free Software Foundation software, granting reuse and reproduction rights to all comers (but see also {General Public Virus}). 2. By extension, any copyright notice intended to achieve similar aims.

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

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

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

:core dump: n. [common {Iron Age} jargon, preserved by UNIX]

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

See {core}.

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

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

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

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

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

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

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

:CP/M:: /C-P-M/ n. [Control Program for Microcomputers] An early microcomputer {OS} written by hacker Gary Kildall for 8080- and Z80-based machines, very popular in the late 1970s but virtually wiped out by MS-DOS after the release of the IBM PC in 1981.

Legend has it that Kildall's company blew its chance to write the OS for the IBM PC because Kildall decided to spend a day IBM's reps wanted to meet with him enjoying the perfect flying weather in his private plane. Many of CP/M's features and conventions strongly resemble those of early DEC operating systems such as {{TOPS-10}}, OS/8, RSTS, and RSX-11. See {{MS-DOS}}, {operating system}.

:CPU Wars: /C-P-U worz/ n. A 1979 large-format comic by Chas Andres chronicling the attempts of the brainwashed androids of IPM

(Impossible to Program Machines) to conquer and destroy the peaceful denizens of HEC (Human Engineered Computers). This rather transparent allegory featured many references to {ADVENT} and the immortal line "Eat flaming death, minicomputer mongrels!"

(uttered, of course, by an IPM stormtrooper). It is alleged that the author subsequently received a letter of appreciation on IBM

company stationery from the head of IBM's Thomas J. Watson Research Laboratories (then, as now, one of the few islands of true hackerdom in the IBM archipelago). The lower loop of the B in the IBM logo, it is said, had been carefully whited out. See {eat flaming death}.

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

:cracker: n. One who breaks security on a system. Coined ca. 1985

by hackers in defense against journalistic misuse of {hacker}

(q.v., sense 8). An earlier attempt to establish `worm' in this sense around 1981--82 on USENET was largely a failure.

Both these neologisms reflected a strong revulsion against the theft and vandalism perpetrated by cracking rings. While it is expected that any real hacker will have done some playful cracking and knows many of the basic techniques, anyone past {larval stage} is expected to have outgrown the desire to do so.

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

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

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

:crank: [from automotive slang] vt. 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."

:crash: 1. n. A sudden, usually drastic failure. Most often said of the {system} (q.v., sense 1), esp. of magnetic disk drives (the term originally described what happened when the air gap of a Winchester disk collapses). "Three {luser}s lost their files in last night's disk crash." A disk crash that involves the read/write heads dropping onto the surface of the disks and scraping off the oxide may also be referred to as a head crash', whereas the termsystem crash' usually, though not always, implies that the operating system or other software was at fault.

v. To fail suddenly. "Has the