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

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.

:JFCL: /jif'kl/, /jaf'kl/, /j*-fi'kl/ vt., obs. (alt.

`jfcl') To cancel or annul something. "Why don't you jfcl that out?" The fastest do-nothing instruction on older models of the PDP-10 happened to be JFCL, which stands for "Jump if Flag set and then CLear the flag"; this does something useful, but is a very fast no-operation if no flag is specified. Geoff Goodfellow, one of the jargon-1 co-authors, had JFCL on the license plate of his BMW for years. Usage: rare except among old-time PDP-10

hackers.

:jiffy: n. 1. The duration of one tick of the system clock on the computer (see {tick}). 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.

Confusingly, the term is sometimes also used for a 1-millisecond {wall time} interval. 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 nanosecond. 3. 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 {nano}. See also {Real Soon Now}.

:job security: n. When some piece of code is written in a particularly {obscure} 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.

:jock: n. 1. A programmer who is characterized by large and somewhat brute-force programs. See {brute force}. 2. When modified by another noun, describes a specialist in some particular computing area. The compounds compiler jock' andsystems jock' seem to be the best-established examples of this.

:joe code: /joh' kohd`/ n. 1. Code that is overly {tense} and unmaintainable. "{Perl} may be a handy program, but if you look at the source, it's complete joe code." 2. Badly written, possibly buggy code.

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.

:jolix: n. /johl'liks/ n.,adj. 386BSD, the freeware port of the BSD Net/2 release to the Intel i386 architecture by Bill Jolitz and friends. Used to differentiate from BSDI's port based on the same source tape, which is called BSD/386. See {BSD}.

:JR[LN]: /J-R-L/, /J-R-N/ n. The names JRL and JRN were sometimes used as example names when discussing a kind of user ID

used under {{TOPS-10}} and {WAITS}; they were understood to be the initials of (fictitious) programmers named `J. Random Loser'

and J. Random Nerd' (see {J. Random}). For example, if one said "To log in, type log one comma jay are en" (that is, "log 1,JRN"), the listener would have understood that he should use his own computer ID in place ofJRN'.

:JRST: /jerst/ [based on the PDP-10 jump instruction] v.,obs. To suddenly change subjects, with no intention of returning to the previous topic. Usage: rather rare except among PDP-10 diehards, and considered silly. See also {AOS}.

:juggling eggs: vi. Keeping a lot of {state} 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 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." That is a very hackish use of language. See also {hack mode}.

:jump off into never-never land: [from J. M. Barrie's Peter Pan'] v. Same as {branch to Fishkill}, but more common in technical cultures associated with non-IBM computers that use the termjump' rather than `branch'. Compare {hyperspace}.

:jupiter: [IRC] vt. To kill an {IRC} {robot} or user, and then take its place by adopting its {nick} 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.

= K =

=====

:K: /K/ [from {kilo-}] n. A kilobyte. This is used both as a spoken word and a written suffix (like {meg} and {gig} for megabyte and gigabyte). See {{quantifiers}}.

:K&R: [Kernighan and Ritchie] n. Brian Kernighan and Dennis Ritchie's book `The C Programming Language', esp. the classic and influential first edition (Prentice-Hall 1978; ISBN 0-113-110163-3). Syn.

{White Book}, {Old Testament}. See also {New Testament}.

:K-line: [IRC] v. To ban a particular person from an {IRC}

server, usually for grossly bad {netiquette}. Comes from the `K' code used to accomplish this in IRC's configuration file.

:kahuna: /k*-hoo'nuh/ [IBM: from the Hawaiian title for a shaman] n.

Synonym for {wizard}, {guru}.

:kamikaze packet: n. The official' jargon for what is more commonly called a {Christmas tree packet}. RFC-1025,TCP and IP Bake Off'

says:

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).

See also {Chernobyl packet}.

:kangaroo code: n. Syn. {spaghetti code}.

:ken: /ken/ n. 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 dmr). See also {demigod}, {{UNIX}}. 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.

:kgbvax: /K-G-B'vaks/ n. See {kremvax}.

:KIBO: /kee'boh/ [acronym] Knowledge In, Bullshit Out. A summary of what happens whenever valid data is passed through an organization (or person) which deliberately or accidentally disregards or ignores its significance. Consider, for example, what advertising campaign can do with a product's actual specifications. Compare {GIGO}; see also {SNAFU principle}.

:kick: [IRC] v. To cause somebody to be removed from a {IRC}

channel, an option only available to {CHOP}s. This is an extreme measure, often used to combat extreme {flamage} or {flood}ing, but sometimes used at the chop's whim.

:kill file: [USENET] n. (alt. KILL file') Per-user file(s) used by some {USENET} reading programs (originally Larry Wall'srn(1)') 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 {plonk}.

:killer micro: [popularized by Eugene Brooks] n. 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.

The popularity of the phrase `attack of the killer micros' is doubtless reinforced by the movie title "Attack Of The Killer Tomatoes" (one of the {canonical} examples of so-bad-it's-wonderful among hackers). This has even more flavor now that killer micros have gone on the offensive not just individually (in workstations) but in hordes (within massively parallel computers).

:killer poke: n. A recipe for inducing hardware damage on a machine via insertion of invalid values (see {poke}) in a memory-mapped control register; used esp. of various fairly well-known tricks on {bitty box}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 {HCF}.

:kilo-: [SI] pref. See {{quantifiers}}.

:KIPS: /kips/ [abbreviation, by analogy with {MIPS} using {K}] n.

Thousands (not 1024s) of Instructions Per Second. Usage: rare.

:KISS Principle: /kis' prin'si-pl/ n. "Keep It Simple, Stupid".

A maxim often invoked when discussing design to fend off {creeping featurism} and control development complexity.

Possibly related to the {marketroid} maxim on sales presentations, "Keep It Short and Simple".

:kit: [USENET; poss. fr. DEC slang for a full software distribution, as opposed to a patch or upgrade] n. 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 {README

file}. The more general