<programming> One of a sequence of copies of a program, each
	incorporating new modifications.  Each version is usually
	identified by a number, commonly of the form X.Y where X is
	the major version number and Y is the release number.
	Typically an increment in X (with Y reset to zero) signifies a
	substantial increase in the function of the program or a
	partial or total re-implementation, whereas Y increases each
	time the progam is changed in any way and re-released.

	Version numbers are useful so that the user can know if the
	program has changed ({bugs} have been fixed or new functions
	added) since he obtained his copy and the programmer can tell
	if a bug report relates to the current version.  It is thus
	always important to state the version when reporting bugs.
	Statements about compatibility between different software
	components should always say which versions they apply to.

	See {change management}.

	(1997-12-07)

1. A program which provides some service to other ({client})
	programs.  The connection between client and server is
	normally by means of {message passing}, often over a
	{network}, and uses some {protocol} to encode the client's
	requests and the server's responses.  The server may run
	continuously (as a {daemon}), waiting for requests to arrive
	or it may be invoked by some higher level daemon which
	controls a number of specific servers ({inetd} on {Unix}).

	There are many servers associated with the {Internet}, such as
	those for {HTTP}, {Network File System}, {Network Information
	Service} (NIS), {Domain Name System} (DNS), {FTP}, {news},
	{finger}, {Network Time Protocol}.  On Unix, a long list can
	be found in /etc/services or in the {NIS} database "services".
	See {client-server}.

	2. A computer which provides some service for other computers
	connected to it via a network.  The most common example is a
	{file server} which has a local disk and services requests
	from remote clients to read and write files on that disk,
	often using {Sun}'s {Network File System} (NFS) {protocol} or
	{Novell Netware} on {PCs}.  Another common example is a {web
	server}.

	[{Jargon File}]

	(2003-12-29)

<operating system, compiler> To load and initialise the
	{operating system} on a computer.  Normally abbreviated to
	"{boot}".  From the curious expression "to pull oneself up by
	one's bootstraps", one of the legendary feats of Baron von
	Munchhausen.  The {bootstrap loader} is the program that runs
	on the computer before any (normal) program can run.  Derived
	terms include {reboot}, {cold boot}, {warm boot}, {soft boot}
	and {hard boot}.

	The term also applies to the use of a {compiler} to compile
	itself.  The usual process is to write an {interpreter} for a
	language, L, in some other existing language.  The compiler is
	then written in L and the interpreter is used to run it.  This
	produces an {executable} for compiling programs in L from the
	source of the compiler in L.  This technique is often used to
	verify the correctness of a compiler.  It was first used in
	the {LISP} community.

	See also {My Favourite Toy Language}.

	[{Jargon File}]

	(2005-04-12)

1. <operating system, software> The sequence of states of an
	executing {program}.  A process consists of the program {code}
	(which may be shared with other processes which are executing
	the same program), private data, and the state of the
	{processor}, particularly the values in its {registers}.  It
	may have other associated resources such as a {process
	identifier}, open files, {CPU time} limits, {shared memory},
	{child processes}, and {signal handlers}.

	One process may, on some {platforms}, consist of many
	{threads}.  A {multitasking} {operating system} can run
	multiple processes {concurrently} or in {parallel}, and allows
	a process to spawn "child" processes.

	(2001-06-16)

	2. <business> The sequence of activities, people, and systems
	involved in carrying out some business or achieving some
	desired result.  E.g. software development process, project
	management process, configuration management process.

	(2001-06-16)

<electronics> The quantity of {charge} per unit time, measured
	in Amperes (Amps, A).  By historical convention, the sign of
	current is positive for currents flowing from positive to
	negative {potential}, but experience indicates that electrons
	are negatively charged and flow in the opposite direction.

	(1995-10-05)

<jargon, programming> A temporary {kluge} used to bypass, mask
	or otherwise avoid a {bug} or {misfeature} in some system.
	Customers often find themselves living with workarounds for
	long periods of time rather than getting a {bug fix}.

	[{Jargon File}]

	(1998-06-25)

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 *not* a joke or
	exaggeration).  A hacker's idea of "support" is a tte--tte
	or exchange of {electronic mail} with the software's designer.

	[{Jargon File}]

	(1995-02-15)

<jargon> {Marketroid} jargon for "{software}", "{hardware}",
	"{protocol}" or something else too technical to name.

	The most flagrant abuse of this word has to be "{Windows NT}"
	(New Technology) - {Microsoft}'s attempt to make the
	incorporation of some ancient concepts into their OS sound
	like real progress.  The irony, and even the meaning, of this
	seems to be utterly lost on Microsoft whose {Windows 2000}
	start-up screen proclaims "Based on NT Technology", (meaning
	yet another version of NT, including some {Windows 95}
	features at last).

	See also: {solution}.

	(2001-06-28)

<operating system> All activities involved in completing any
	project on a computer from start to finish.  A job may involve
	several {processes} and several {programs}.

	This term originates from a time when a user would manually
	submit a job as a deck of {punched cards} which would
	typically include {source code} interspersed with {job control
	language} instructions to guide phases of the job such as
	{compilation}, {linking}, {execution} and printing.

	(2005-03-16)

<company> (IBM) The best known American computer manufacturer,
	founded by Thomas J. Watson (born 1874-02-17), known as "Big
	Blue" after the colour of its logo.  IBM makes everything from
	{mainframes} to {personal computers} (PCs) and has been
	immensely successful in selling them, chiefly to business.  It
	has often been said that "Nobody has ever been sacked for
	buying IBM".

	The {IBM PC} in its various versions has been so successful
	that unqualified reference to a "PC" almost certainly means a
	PC from IBM, or one of the many brands of {clone} produced by
	other manufacturers to cash in on IBM's original success.

	Alternative expansions of "IBM" such as Inferior But
	Marketable; It's Better Manually; Insidious Black Magic; It's
	Been Malfunctioning; Incontinent Bowel Movement, illustrate
	the considerable antipathy most hackers have long felt toward
	the "industry leader" (see {fear and loathing}).

	Quarterly sales $15351M, profits $689M (Aug 1994).

	{Home (http://www.ibm.com/)}.

	(1999-04-07)

<World-Wide Web, project> A {open source} {HTTP} server for
	{Unix}, {Windows NT}, and other {platforms}.  Apache was
	developed in early 1995, based on code and ideas found in the
	most popular HTTP server of the time, {NCSA httpd} 1.3.  It
	has since evolved to rival (and probably surpass) almost any
	other {Unix} based HTTP server in terms of functionality, and
	speed.  Since April 1996 Apache has been the most popular HTTP
	server on the {Internet}, in May 1999 it was running on 57% of
	all web servers.

	It features highly configurable error messages, {DBM}-based
	{authentication} {databases}, and {content negotiation}.

	Latest version: 1.3.9, as of 1999-10-27.

	{Home (http://www.apache.org/httpd.html)}.

	{FAQ (http://www.apache.org/docs/misc/FAQ.html)}.

	(1999-10-27)

<jargon> A {marketroid} term for something he wants to sell
	you without bothering you with the often dizzying distinctions
	between {hardware}, {software}, {services}, {applications},
	{file formats}, companies, brand names and {operating
	systems}.

	"{Flash} is a perfect image-streaming solution."  "What is
	it?"  "Um...  about a thousand dollars."

	See also: {technology}.

	(1998-07-07)

1. <storage> {Main memory} or {RAM}.  This term dates from the
	days of {ferrite core memory}; now archaic 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" ({paged in}, as opposed to "on disk", {paged
	out}), and both {core dump} and the "core image" or "core
	file" produced by one are terms in favour.  Some varieties of
	Commonwealth hackish prefer {store}.

	[{Jargon File}]

	(1995-03-03)

	2. <processor> An {integrated circuit} design, usually for a
	{microprocessor}, which includes only the {CPU} and which is
	intended to form part of a complete circuit design which
	incorporates other circuits on the same chip such as {cache},
	{memory management unit}, I/O ports and timers.

	The {ARM6}, {ARM7} and {ARM8} are examples.

	3. <language> A varient on {kernel} as used to describe
	features built into a language as opposed to those provided by
	{libraries}.

	(1995-03-03)

(Or "REDL") A language proposed by {Intermetrics} to meet the
	{Ironman} requirements which led to {Ada}.

	["On the RED Language Submitted to the DoD", E.W. Dijkstra,
	SIGPLAN Notices 13(10):27 (Oct 1978)].

	["RED Language Reference Manual", J. Nestor and M. van Deusen,
	Intermetrics 1979].

	(1995-01-19)