<operating system, programming> The process of carrying out
	the {instructions} in a computer program by a computer.

	See also {dry run}.

	(1996-05-13)

Common term for "computer", usually when considered at the
	hardware level.  The {Turing Machine}, an early example of
	this usage, was however neither hardware nor software, but
	only an idea.

	[Earlier use?]

	(1995-02-15)

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)

<file system> An element of data storage in a {file system}.

	The history of computing is rich in varied kinds of files and
	{file systems}, whether ornate (e.g., {Macintosh file system}
	for a well-known case) or deficient (e.g., many simple
	pre-1980s file systems don't allow {directories}).

	However, the prototypical file has these characteristics:

	* It is a single sequence of bytes (but consider {Macintosh}
	{resource forks}).

	* It has a finite length, unlike, e.g. a {Unix} {device}.

	* It is stored in a {non-volatile storage} medium (but see
	{ramdrive}).

	* It exists (nominally) in a {directory}.

	* It has a name that it can be referred to by in file
	operations, possibly in combination with its {path}.

	Additionally, a file system may associate other information
	with a file, such as {permission} bits or other {file
	attributes}; timestamps for file creation, last revision, and
	last access; revision numbers (a` la VMS), and other kinds of
	{magic}.

	Compare: {document}.

	(1997-04-08)

1. <operating system> (Or "erase") To make a file
	inaccessible.

	Usually this operation only deletes information from the
	tables the {file system} uses to locate named files; the
	file's contents still exist on {disk} and can sometimes be
	recovered by scanning the whole disk for strings which are
	known to have been in the file.  Files created subsequently on
	the same disk are quite likely to reuse the same blocks and
	thus overwrite the deleted file's data permanently.

	2. <character> The {control character} with {ASCII} code 127.
	Usually entering this character from the keyboard deletes the
	last character typed from the {input buffer}.  Sadly there is
	great confusion between {operating systems} and keyboard
	manufacturers as to whether this function should be assigned
	to the delete or {backspace} key/character.

	The choice of code 127 (binary 1111111) is not arbitrary but
	dates back to the use of {paper tape} for input.  The delete
	key rewound the tape by one character and punched out all
	seven holes, thus obliterating whatever character was there
	before.  The tape reading software ignored any delete
	characters in the input.

	(1996-12-01)

1. Executable code, especially a "pure code" portion shared
	between multiple instances of a program running in a
	{multitasking} {operating system}.

	Compare {English}.

	2. Textual material in the mainstream sense; data in ordinary
	{ASCII} or {EBCDIC} representation (see {flat ASCII}).  "Those
	are text files; you can review them using the editor."

	These two contradictory senses confuse hackers too.

	[{Jargon File}]

	(1995-03-16)

1. <hardware> An electrical conductor.  For distances larger
	than a breadbox, a single line may consist of two electrical
	conductors in twisted, parallel, or concentric arrangement
	used to transport one logical signal.

	By extension, a (usually physical) medium such as an {optical
	fibre} which carries a signal.

	(1995-09-29)

<programming> A program like {Unix}'s "split" which breaks an
	input file into parts, usually of a pre-set size, e.g. the
	maximum size that can fit on a {floppy}.  The parts can then
	be assembled with a {dechunker}, which is usually just the
	chunker in a different mode.

	(1998-12-15)

1. <chat> {Unix}'s simple {talk} command and {protocol}.
	write has been largely superseded by {talk} and then {irc}.

	An enhancement, {RWP}, has been proposed.

	2. <tool> A simple {text editor} for {Windows}.

	(1998-04-28)

1. <application, algorithm> To arrange a collection of items
	in some specified order.  The items - {records} in a file or
	data structures in memory - consist of one or more {fields} or
	members.  One of these fields is designated as the "sort key"
	which means the records will be ordered according to the value
	of that field.  Sometimes a sequence of key fields is
	specified such that if all earlier keys are equal then the
	later keys will be compared.  Within each field some ordering
	is imposed, e.g. ascending or descending numerical, {lexical
	ordering}, or date.

	Sorting is the subject of a great deal of study since it is a
	common operation which can consume a lot of computer time.
	There are many well-known sorting {algorithms} with different
	time and space behaviour and programming {complexity}.

	Examples are {quicksort}, {insertion sort}, {bubble sort},
	{heap sort}, and {tree sort}.  These employ many different
	data structures to store sorted data, such as {arrays},
	{linked lists}, and {binary trees}.

	2. <tool> The {Unix} utility program for sorting lines of
	files.

	{Unix manual page}: sort(1).

	(1997-02-12)

<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. Not simulated.  Often used as a specific antonym to
	{virtual} in any of its jargon senses.

	2. <mathematics> {real number}.

	[{Jargon File}]

	(1997-03-12)

1. <programming, operating system> A simple item of data that
	identifies a resource.  For example, a {Unix} file handle
	identifies an open file and associated data such as whether it
	was opened for read or write and the current read/write
	position.  On the {Macintosh}, a handle is a pointer to a
	pointer to some dynamically-allocated memory.  The extra level
	of indirection allows on-the-fly {memory compaction} or
	{garbage collection} without invalidating application program
	references to the allocated memory.

	2. <jargon> An alias used intended to conceal a user's true
	identity in an electronic message.  The term is common on
	Citizen's Band and other amateur radio but, in that context
	usually means the user's real name as {FCC} rules forbid
	concealing one's identity.

	Use of grandiose handles is characteristic of {crackers},
	{weenies}, {spods}, and other lower forms of network life;
	true hackers travel on their own reputations.

	Compare {nick}.

	[{Jargon File}]

	(2004-07-20)

<networking> Hardware and software data communication systems.

	The {OSI} seven layer model attempts to provide a way of
	partitioning any computer network into independent modules
	from the lowest (physical) layer to the highest (application)
	layer.  Many different specifications exist at each of these
	layers.

	Networks are often also classified according to their
	geographical extent: {local area network} (LAN), {metropolitan
	area network} (MAN), {wide area network} (WAN) and also
	according to the {protocols} used.

	See {BITNET}, {Ethernet}, {Internet}, {Novell}, {PSTN},
	{network, the}.

	[Tanenbaum, A., "Computer Networks; 2nd ed.", Prentice Hall,
	Englewood Cliffs, NJ, 1989.]

	(1995-03-10)

<tool, cryptography> (PGP) A high security {RSA} {public-key
	encryption} application for {MS-DOS}, {Unix}, {VAX/VMS}, and
	other computers.  It was written by {Philip R. Zimmermann}
	<pkz@acm.org> of Phil's Pretty Good(tm) Software and later
	augmented by a cast of thousands, especially including Hal
	Finney, Branko Lankester, and Peter Gutmann.

	PGP was distributed as "{guerrilla freeware}".  The authors
	don't mind if it is distributed widely, just don't ask Philip
	Zimmermann to send you a copy.  PGP uses a {public-key
	encryption} {algorithm} claimed by US patent #4,405,829.  The
	exclusive rights to this patent are held by a California
	company called {Public Key Partners}, and you may be
	infringing this patent if you use PGP in the USA.  This is
	explained in the PGP User's Guide, Volume II.

	PGP allows people to exchange files or messages with {privacy}
	and {authentication}.  Privacy and authentication are provided
	without managing the keys associated with conventional
	cryptographic software.  No secure channels are needed to
	exchange keys between users, which makes PGP much easier to
	use.  This is because PGP is based on {public-key
	cryptography}.

	PGP encrypts data using the {International Data Encryption
	Algorithm} with a random {session key}, and uses the {RSA}
	algorithm to encrypt the session key.

	In December 1994 Philip Zimmermann faced prosecution for
	"exporting" PGP out of the United States but in January 1996
	the US Goverment dropped the case.  A US law prohibits the
	export of {encryption} software out of the country.
	Zimmermann did not do this, but the US government hoped to
	establish the proposition that posting an encryption program
	on a {BBS} or on the {Internet} constitutes exporting it - in
	effect, stretching export control into domestic censorship.
	If the government had won it would have had a chilling effect
	on the free flow of information on the global network, as well
	as on everyone's privacy from government snooping.

	{FAQ (ftp://ftp.netcom.com/pub/mp/mpj/getpgp.asc)}.  {UK FTP
	(ftp://src.doc.ic.ac.uk/packages/pgp/)}.  {USA FTP
	(http://web.mit.edu/network/pgp-form.html)}.
	{(http://www.pegasus.esprit.ec.org/people/arne/pgp.html)}.

	{Justice Dept. announcement
	(http://www.eff.org/pub/Alerts/usatty_pgp_011196.announce)}.

	["Protect Your Privacy: A Guide for PGP Users", William
	Stallings, Prentice-Hall, ISBN 0-13-185596-4].

	(1996-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)

<operating system, programming> The process of carrying out
	the {instructions} in a computer program by a computer.

	See also {dry run}.

	(1996-05-13)

<operating system> See {Microsoft Windows}, {Windows NT}.

	(1997-11-23)

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)

<networking, programming> Work performed (or offered) by a
	{server}.  This may mean simply serving simple requests for
	data to be sent or stored (as with {file servers}, {gopher} or
	{http} servers, {e-mail} servers, {finger} servers, {SQL}
	servers, etc.); or it may be more complex work, such as that
	of {irc} servers, print servers, {X Windows} servers, or
	process servers.

	E.g. "Access to the finger {service} is restricted to the
	local {subnet}, for security reasons".

	(1997-09-11)