:Full Monty, the: /n./ See {monty}, sense 2.
:fum: /n./ [XEROX PARC] At PARC, often the third of the standard {metasyntactic variable}s (after {foo} and {bar}). Competes with {baz}, which is more common outside PARC.
:funky: /adj./ 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. {TECO} 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."
:funny money: /n./ 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'.
:furrfu: // /excl./ [Usenet] Written-only equivalent of
"Sheesh!"; it is, in fact, "sheesh" modified by {rot13}.
Evolved in mid-1992 as a response to notably silly postings
repeating urban myths on the Usenet newsgroup
alt.folklore.urban, after some posters complained that
"Sheesh!" as a response to {newbie}s was being overused. See
also {FOAF}.
:fuzzball: /n./ [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.
= G = =====
:G: /pref.,suff./ [SI] See {{quantifiers}}.
:g-file: /n./ [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.
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.