2035 lines
57 KiB
XML
2035 lines
57 KiB
XML
<?xml version="1.0" encoding="iso-8859-1"?>
|
|
<!--
|
|
$FreeBSD$
|
|
|
|
FreeBSD Glossary Terms
|
|
Please keep this file sorted alphabetically/ASCIIly by glossterm.
|
|
|
|
glossterms that are acronyms should have two entries - one for
|
|
the expanded acronym and another for the acronym itself. The
|
|
second of these should reference the entry for the expanded acronym
|
|
via a glosssee element. For example:
|
|
|
|
<glossentry>
|
|
<glossterm>FUBAR</glossterm>
|
|
<glosssee otherterm="fubar-glossary">
|
|
</glossentry>
|
|
|
|
<glossentry id="fubar-glossary">
|
|
<glossterm>Fuc... Up Beyond All Recognition</glossterm>
|
|
<acronym>FUBAR</acronym>
|
|
<glossdef>
|
|
<para>Broken.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
Note that in this instance, the expanded acronym sorts below the
|
|
unexpanded acronym. That's OK.
|
|
|
|
Finally, id attribute values should end in the string
|
|
"-glossary" to avoid conflicting with id attribute values in
|
|
the main text.
|
|
|
|
-->
|
|
|
|
<!ENTITY freebsd-glossary '
|
|
<glossary status="draft" id="freebsd-glossary">
|
|
<title>&os; Glossary</title>
|
|
<para>This glossary contains terms and acronyms used within the &os;
|
|
community and documentation.</para>
|
|
|
|
<glossdiv>
|
|
<title>A</title>
|
|
|
|
<glossentry>
|
|
<glossterm>ACL</glossterm>
|
|
<glosssee otherterm="acl-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>ACPI</glossterm>
|
|
<glosssee otherterm="acpi-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>AMD</glossterm>
|
|
<glosssee otherterm="amd-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>AML</glossterm>
|
|
<glosssee otherterm="aml-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>API</glossterm>
|
|
<glosssee otherterm="api-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>APIC</glossterm>
|
|
<glosssee otherterm="apic-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>APM</glossterm>
|
|
<glosssee otherterm="apm-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>APOP</glossterm>
|
|
<glosssee otherterm="apop-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>ASL</glossterm>
|
|
<glosssee otherterm="asl-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>ATA</glossterm>
|
|
<glosssee otherterm="ata-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>ATM</glossterm>
|
|
<glosssee otherterm="atm-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry id="aml-glossary">
|
|
<glossterm><acronym>ACPI</acronym> Machine Language</glossterm>
|
|
<acronym>AML</acronym>
|
|
<glossdef>
|
|
<para>Pseudocode, interpreted by a virtual machine within an
|
|
<acronym>ACPI</acronym>-compliant operating system, providing a
|
|
layer between the underlying hardware and the documented
|
|
interface presented to the <acronym>OS</acronym>.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="asl-glossary">
|
|
<glossterm><acronym>ACPI</acronym> Source Language</glossterm>
|
|
<acronym>ASL</acronym>
|
|
<glossdef>
|
|
<para>The programming language <acronym>AML</acronym> is written in.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="acl-glossary">
|
|
<glossterm>Access Control List</glossterm>
|
|
<acronym>ACL</acronym>
|
|
<glossdef>
|
|
<para>A list of permissions attached to an object, usually either a
|
|
file or a network device.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="acpi-glossary">
|
|
<glossterm>Advanced Configuration and Power Interface</glossterm>
|
|
<acronym>ACPI</acronym>
|
|
<glossdef>
|
|
<para>A specification which provides an abstraction of the
|
|
interface the hardware presents to the operating system, so
|
|
that the operating system should need to know nothing about
|
|
the underlying hardware to make the most of it. <acronym>ACPI</acronym>
|
|
evolves and supersedes the functionality provided previously by
|
|
<acronym>APM</acronym>, <acronym>PNPBIOS</acronym> and other technologies, and
|
|
provides facilities for controlling power consumption, machine
|
|
suspension, device enabling and disabling, etc.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="api-glossary">
|
|
<glossterm>Application Programming Interface</glossterm>
|
|
<acronym>API</acronym>
|
|
<glossdef>
|
|
<para>A set of procedures, protocols and tools that specify the
|
|
canonical interaction of one or more program parts; how, when
|
|
and why they do work together, and what data they share or
|
|
operate on.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="apm-glossary">
|
|
<glossterm>Advanced Power Management</glossterm>
|
|
<acronym>APM</acronym>
|
|
<glossdef>
|
|
<para>An <acronym>API</acronym> enabling the operating system to work
|
|
in conjunction with the <acronym>BIOS</acronym> in order to achieve
|
|
power management. <acronym>APM</acronym> has been superseded by
|
|
the much more generic and powerful <acronym>ACPI</acronym>
|
|
specification for most applications.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="apic-glossary">
|
|
<glossterm>Advanced Programmable Interrupt Controller</glossterm>
|
|
<acronym>APIC</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="ata-glossary">
|
|
<glossterm>Advanced Technology Attachment</glossterm>
|
|
<acronym>ATA</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="atm-glossary">
|
|
<glossterm>Asynchronous Transfer Mode</glossterm>
|
|
<acronym>ATM</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="apop-glossary">
|
|
<glossterm>Authenticated Post Office Protocol</glossterm>
|
|
<acronym>APOP</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="amd-glossary">
|
|
<glossterm>Automatic Mount Daemon</glossterm>
|
|
<acronym>AMD</acronym>
|
|
<glossdef>
|
|
<para>A daemon that automatically mounts a filesystem when a file
|
|
or directory within that filesystem is accessed.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
</glossdiv>
|
|
|
|
<glossdiv>
|
|
<title>B</title>
|
|
|
|
<glossentry>
|
|
<glossterm>BAR</glossterm>
|
|
<glosssee otherterm="bar-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>BIND</glossterm>
|
|
<glosssee otherterm="bind-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>BIOS</glossterm>
|
|
<glosssee otherterm="bios-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>BSD</glossterm>
|
|
<glosssee otherterm="bsd-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry id="bar-glossary">
|
|
<glossterm>Base Address Register</glossterm>
|
|
<acronym>BAR</acronym>
|
|
<glossdef>
|
|
<para>The registers that determine which address range a <acronym>PCI</acronym> device
|
|
will respond to.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="bios-glossary">
|
|
<glossterm>Basic Input/Output System</glossterm>
|
|
<acronym>BIOS</acronym>
|
|
<glossdef>
|
|
<para>The definition of <acronym>BIOS</acronym> depends a bit on
|
|
the context. Some people refer to it as the <acronym>ROM</acronym>
|
|
chip with a basic set of routines to provide an interface between
|
|
software and hardware. Others refer to it as the set of routines
|
|
contained in the chip that help in bootstrapping the system. Some
|
|
might also refer to it as the screen used to configure the
|
|
boostrapping process. The <acronym>BIOS</acronym> is PC-specific
|
|
but other systems have something similar.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="bind-glossary">
|
|
<glossterm>Berkeley Internet Name Domain</glossterm>
|
|
<acronym>BIND</acronym>
|
|
<glossdef>
|
|
<para>An implementation of the <acronym>DNS</acronym> protocols.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="bsd-glossary">
|
|
<glossterm>Berkeley Software Distribution</glossterm>
|
|
<acronym>BSD</acronym>
|
|
<glossdef>
|
|
<para>This is the name that the Computer Systems Research Group
|
|
(CSRG) at <ulink url="http://www.berkeley.edu">The University
|
|
of California at Berkeley</ulink>
|
|
gave to their improvements and modifications to
|
|
AT&T's 32V &unix;.
|
|
&os; is a descendant of the CSRG work.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="bikeshed-glossary">
|
|
<glossterm>Bikeshed Building</glossterm>
|
|
<glossdef subject="FreeBSD">
|
|
<para>A phenomenon whereby many people will give an opinion on
|
|
an uncomplicated topic, whilst a complex topic receives little
|
|
or no discussion. See the
|
|
<ulink url="&url.books.faq;/misc.html#BIKESHED-PAINTING">FAQ</ulink> for
|
|
the origin of the term.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
</glossdiv>
|
|
|
|
<glossdiv>
|
|
<title>C</title>
|
|
|
|
<glossentry>
|
|
<glossterm>CD</glossterm>
|
|
<glosssee otherterm="cd-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>CHAP</glossterm>
|
|
<glosssee otherterm="chap-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>CLIP</glossterm>
|
|
<glosssee otherterm="clip-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>COFF</glossterm>
|
|
<glosssee otherterm="coff-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>CPU</glossterm>
|
|
<glosssee otherterm="cpu-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>CTS</glossterm>
|
|
<glosssee otherterm="cts-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>CVS</glossterm>
|
|
<glosssee otherterm="cvs-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry id="cd-glossary">
|
|
<glossterm>Carrier Detect</glossterm>
|
|
<acronym>CD</acronym>
|
|
<glossdef>
|
|
<para>An <acronym>RS232C</acronym> signal indicating that a carrier
|
|
has been detected.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="cpu-glossary">
|
|
<glossterm>Central Processing Unit</glossterm>
|
|
<acronym>CPU</acronym>
|
|
<glossdef>
|
|
<para>Also known as the processor. This is the brain of the
|
|
computer where all calculations take place. There are a number of
|
|
different architectures with different instruction sets. Among
|
|
the more well-known are the Intel-x86 and derivatives, Sun SPARC,
|
|
PowerPC, and Alpha.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="chap-glossary">
|
|
<glossterm>Challenge Handshake Authentication Protocol</glossterm>
|
|
<acronym>CHAP</acronym>
|
|
<glossdef>
|
|
<para>A method of authenticating a user, based on a secret shared
|
|
between client and server.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="clip-glossary">
|
|
<glossterm>Classical <acronym>IP</acronym> over <acronym>ATM</acronym></glossterm>
|
|
<acronym>CLIP</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="cts-glossary">
|
|
<glossterm>Clear To Send</glossterm>
|
|
<acronym>CTS</acronym>
|
|
<glossdef>
|
|
<para>An <acronym>RS232C</acronym> signal giving the remote system
|
|
permission to send data.</para>
|
|
<glossseealso otherterm="rts-glossary"/>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="coff-glossary">
|
|
<glossterm>Common Object File Format</glossterm>
|
|
<acronym>COFF</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="cvs-glossary">
|
|
<glossterm>Concurrent Versions System</glossterm>
|
|
<acronym>CVS</acronym>
|
|
<glossdef>
|
|
<para>A version control system, providing a method of working with and
|
|
keeping track of many different revisions of files. CVS provides the
|
|
ability to extract, merge and revert individual changes or sets of
|
|
changes, and offers the ability to keep track of which changes were
|
|
made, by who and for what reason.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
</glossdiv>
|
|
|
|
<glossdiv>
|
|
<title>D</title>
|
|
|
|
<glossentry>
|
|
<glossterm>DAC</glossterm>
|
|
<glosssee otherterm="dac-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>DDB</glossterm>
|
|
<glosssee otherterm="ddb-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>DES</glossterm>
|
|
<glosssee otherterm="des-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>DHCP</glossterm>
|
|
<glosssee otherterm="dhcp-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>DNS</glossterm>
|
|
<glosssee otherterm="dns-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>DSDT</glossterm>
|
|
<glosssee otherterm="dsdt-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>DSR</glossterm>
|
|
<glosssee otherterm="dsr-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>DTR</glossterm>
|
|
<glosssee otherterm="dtr-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>DVMRP</glossterm>
|
|
<glosssee otherterm="dvmrp-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry id="dac-glossary">
|
|
<glossterm>Discretionary Access Control</glossterm>
|
|
<acronym>DAC</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="des-glossary">
|
|
<glossterm>Data Encryption Standard</glossterm>
|
|
<acronym>DES</acronym>
|
|
<glossdef>
|
|
<para>A method of encrypting information, traditionally used as the
|
|
method of encryption for &unix; passwords and the &man.crypt.3;
|
|
function.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="dsr-glossary">
|
|
<glossterm>Data Set Ready</glossterm>
|
|
<acronym>DSR</acronym>
|
|
<glossdef>
|
|
<para>An <acronym>RS232C</acronym> signal sent from the modem to the
|
|
computer or terminal indicating a readiness to send and receive
|
|
data.</para>
|
|
<glossseealso otherterm="dtr-glossary"/>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="dtr-glossary">
|
|
<glossterm>Data Terminal Ready</glossterm>
|
|
<acronym>DTR</acronym>
|
|
<glossdef>
|
|
<para>An <acronym>RS232C</acronym> signal sent from the computer or
|
|
terminal to the modem indicating a readiness to send and receive
|
|
data.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="ddb-glossary">
|
|
<glossterm>Debugger</glossterm>
|
|
<acronym>DDB</acronym>
|
|
<glossdef>
|
|
<para>An interactive in-kernel facility for examining the status of
|
|
a system, often used after a system has crashed to establish the
|
|
events surrounding the failure.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="dsdt-glossary">
|
|
<glossterm>Differentiated System Description Table</glossterm>
|
|
<acronym>DSDT</acronym>
|
|
<glossdef>
|
|
<para>An <acronym>ACPI</acronym> table, supplying basic configuration
|
|
information about the base system.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="dvmrp-glossary">
|
|
<glossterm>Distance-Vector Multicast Routing Protocol</glossterm>
|
|
<acronym>DVMRP</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="dns-glossary">
|
|
<glossterm>Domain Name System</glossterm>
|
|
<acronym>DNS</acronym>
|
|
<glossdef>
|
|
<para>The system that converts humanly readable hostnames (i.e.,
|
|
mail.example.net) to Internet addresses and vice versa.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="dhcp-glossary">
|
|
<glossterm>Dynamic Host Configuration Protocol</glossterm>
|
|
<acronym>DHCP</acronym>
|
|
<glossdef>
|
|
<para>A protocol that dynamically assigns IP addresses to a computer
|
|
(host) when it requests one from the server. The address assignment
|
|
is called a <quote>lease</quote>.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
</glossdiv>
|
|
|
|
<glossdiv>
|
|
<title>E</title>
|
|
|
|
<glossentry>
|
|
<glossterm>ECOFF</glossterm>
|
|
<glosssee otherterm="ecoff-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>ELF</glossterm>
|
|
<glosssee otherterm="elf-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>ESP</glossterm>
|
|
<glosssee otherterm="esp-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry id="esp-glossary">
|
|
<glossterm>Encapsulated Security Payload</glossterm>
|
|
<acronym>ESP</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="elf-glossary">
|
|
<glossterm>Executable and Linking Format</glossterm>
|
|
<acronym>ELF</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="ecoff-glossary">
|
|
<glossterm>Extended <acronym>COFF</acronym></glossterm>
|
|
<acronym>ECOFF</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
</glossdiv>
|
|
|
|
<glossdiv>
|
|
<title>F</title>
|
|
|
|
<glossentry>
|
|
<glossterm>FADT</glossterm>
|
|
<glosssee otherterm="fadt-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>FAT</glossterm>
|
|
<glosssee otherterm="fat-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>FAT16</glossterm>
|
|
<glosssee otherterm="fat16-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>FTP</glossterm>
|
|
<glosssee otherterm="ftp-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry id="fat-glossary">
|
|
<glossterm>File Allocation Table</glossterm>
|
|
<acronym>FAT</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="fat16-glossary">
|
|
<glossterm>File Allocation Table (16-bit)</glossterm>
|
|
<acronym>FAT16</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="ftp-glossary">
|
|
<glossterm>File Transfer Protocol</glossterm>
|
|
<acronym>FTP</acronym>
|
|
<glossdef>
|
|
<para>A member of the family of high-level protocols implemented
|
|
on top of <acronym>TCP</acronym> which can be used to transfer
|
|
files over a <acronym>TCP/IP</acronym> network.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="fadt-glossary">
|
|
<glossterm>Fixed <acronym>ACPI</acronym> Description Table</glossterm>
|
|
<acronym>FADT</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
</glossdiv>
|
|
|
|
<glossdiv>
|
|
<title>G</title>
|
|
|
|
<glossentry>
|
|
<glossterm>GUI</glossterm>
|
|
<glosssee otherterm="gui-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry id="giant-glossary">
|
|
<glossterm>Giant</glossterm>
|
|
<glossdef subject="FreeBSD">
|
|
<para>The name of a mutual exclusion mechanism
|
|
(a <literal>sleep mutex</literal>) that protects a large
|
|
set of kernel resources. Although a simple locking mechanism
|
|
was adequate in the days where a machine might have only
|
|
a few dozen processes, one networking card, and certainly
|
|
only one processor, in current times it is an unacceptable
|
|
performance bottleneck. &os; developers are actively working
|
|
to replace it with locks that protect individual resources,
|
|
which will allow a much greater degree of parallelism for
|
|
both single-processor and multi-processor machines.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="gui-glossary">
|
|
<glossterm>Graphical User Interface</glossterm>
|
|
<acronym>GUI</acronym>
|
|
<glossdef>
|
|
<para>A system where the user and computer interact with
|
|
graphics.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
</glossdiv>
|
|
|
|
<glossdiv>
|
|
<title>H</title>
|
|
|
|
<glossentry>
|
|
<glossterm>HTML</glossterm>
|
|
<glosssee otherterm="html-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>HUP</glossterm>
|
|
<glosssee otherterm="hup-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry id="hup-glossary">
|
|
<glossterm>HangUp</glossterm>
|
|
<acronym>HUP</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="html-glossary">
|
|
<glossterm>HyperText Markup Language</glossterm>
|
|
<acronym>HTML</acronym>
|
|
<glossdef>
|
|
<para>The markup language used to create web pages.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
</glossdiv>
|
|
|
|
<glossdiv>
|
|
<title>I</title>
|
|
|
|
<glossentry>
|
|
<glossterm>I/O</glossterm>
|
|
<glosssee otherterm="io-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>IASL</glossterm>
|
|
<glosssee otherterm="iasl-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>IMAP</glossterm>
|
|
<glosssee otherterm="imap-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>IP</glossterm>
|
|
<glosssee otherterm="ip-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>IPFW</glossterm>
|
|
<glosssee otherterm="ipfw-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>IPP</glossterm>
|
|
<glosssee otherterm="ipp-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>IPv4</glossterm>
|
|
<glosssee otherterm="ipv4-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>IPv6</glossterm>
|
|
<glosssee otherterm="ipv6-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>ISP</glossterm>
|
|
<glosssee otherterm="isp-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry id="ipfw-glossary">
|
|
<glossterm><acronym>IP</acronym> Firewall</glossterm>
|
|
<acronym>IPFW</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="ipv4-glossary">
|
|
<glossterm><acronym>IP</acronym> Version 4</glossterm>
|
|
<acronym>IPv4</acronym>
|
|
<glossdef>
|
|
<para>The <acronym>IP</acronym> protocol version 4, which uses 32 bits
|
|
for addressing. This version is still the most widely used, but it
|
|
is slowly being replaced with <acronym>IPv6</acronym>.</para>
|
|
<glossseealso otherterm="ipv6-glossary"/>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="ipv6-glossary">
|
|
<glossterm><acronym>IP</acronym> Version 6</glossterm>
|
|
<acronym>IPv6</acronym>
|
|
<glossdef>
|
|
<para>The new <acronym>IP</acronym> protocol. Invented because the
|
|
address space in <acronym>IPv4</acronym> is running out. Uses 128
|
|
bits for addressing.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="io-glossary">
|
|
<glossterm>Input/Output</glossterm>
|
|
<acronym>I/O</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="iasl-glossary">
|
|
<glossterm>Intel’s <acronym>ASL</acronym> compiler</glossterm>
|
|
<acronym>IASL</acronym>
|
|
<glossdef>
|
|
<para>Intel’s compiler for converting <acronym>ASL</acronym> into
|
|
<acronym>AML</acronym>.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="imap-glossary">
|
|
<glossterm>Internet Message Access Protocol</glossterm>
|
|
<acronym>IMAP</acronym>
|
|
<glossdef>
|
|
<para>A protocol for accessing email messages on a mail server,
|
|
characterised by the messages usually being kept on the server as
|
|
opposed to being downloaded to the mail reader client.</para>
|
|
<glossseealso otherterm="pop3-glossary"/>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="ipp-glossary">
|
|
<glossterm>Internet Printing Protocol</glossterm>
|
|
<acronym>IPP</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="ip-glossary">
|
|
<glossterm>Internet Protocol</glossterm>
|
|
<acronym>IP</acronym>
|
|
<glossdef>
|
|
<para>The packet transmitting protocol that is the basic protocol on
|
|
the Internet. Originally developed at the U.S. Department of
|
|
Defense and an extremely important part of the <acronym>TCP/IP
|
|
</acronym> stack. Without the Internet Protocol, the Internet
|
|
would not have become what it is today. For more information, see
|
|
<ulink url="ftp://ftp.rfc-editor.org/in-notes/rfc791.txt">
|
|
RFC 791</ulink>.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="isp-glossary">
|
|
<glossterm>Internet Service Provider</glossterm>
|
|
<acronym>ISP</acronym>
|
|
<glossdef>
|
|
<para>A company that provides access to the Internet.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
</glossdiv>
|
|
|
|
<glossdiv>
|
|
<title>K</title>
|
|
|
|
<glossentry id="kame-glossary">
|
|
<glossterm>KAME</glossterm>
|
|
<glossdef>
|
|
<para>Japanese for <quote>turtle</quote>, the term KAME is used
|
|
in computing circles to refer to the <ulink
|
|
url="http://www.kame.net/">KAME Project</ulink>, who work on
|
|
an implementation of <acronym>IPv6</acronym>.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>KDC</glossterm>
|
|
<glosssee otherterm="kdc-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>KLD</glossterm>
|
|
<glosssee otherterm="kld-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>KSE</glossterm>
|
|
<glosssee otherterm="kse-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>KVA</glossterm>
|
|
<glosssee otherterm="kva-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>Kbps</glossterm>
|
|
<glosssee otherterm="kbps-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry id="kld-glossary">
|
|
<glossterm>Kernel &man.ld.1;</glossterm>
|
|
<acronym>KLD</acronym>
|
|
<glossdef>
|
|
<para>A method of dynamically loading functionality into a &os; kernel
|
|
without rebooting the system.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="kse-glossary">
|
|
<glossterm>Kernel Scheduler Entities</glossterm>
|
|
<acronym>KSE</acronym>
|
|
<glossdef>
|
|
<para>A kernel-supported threading system. See the <ulink
|
|
url="http://www.FreeBSD.org/kse">project home page</ulink>
|
|
for further details.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="kva-glossary">
|
|
<glossterm>Kernel Virtual Address</glossterm>
|
|
<acronym>KVA</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="kdc-glossary">
|
|
<glossterm>Key Distribution Center</glossterm>
|
|
<acronym>KDC</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="kbps-glossary">
|
|
<glossterm>Kilo Bits Per Second</glossterm>
|
|
<acronym>Kbps</acronym>
|
|
<glossdef>
|
|
<para>Used to measure bandwidth (how much data can pass a given
|
|
point at a specified amount of time). Alternates to the Kilo
|
|
prefix include Mega, Giga, Tera, and so forth.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
</glossdiv>
|
|
|
|
<glossdiv>
|
|
<title>L</title>
|
|
|
|
<glossentry>
|
|
<glossterm>LAN</glossterm>
|
|
<glosssee otherterm="lan-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>LOR</glossterm>
|
|
<glosssee otherterm="lor-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>LPD</glossterm>
|
|
<glosssee otherterm="lpd-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry id="lpd-glossary">
|
|
<glossterm>Line Printer Daemon</glossterm>
|
|
<acronym>LPD</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="lan-glossary">
|
|
<glossterm>Local Area Network</glossterm>
|
|
<acronym>LAN</acronym>
|
|
<glossdef>
|
|
<para>A network used on a local area, e.g. office, home, or so forth.
|
|
</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="lor-glossary">
|
|
<glossterm>Lock Order Reversal</glossterm>
|
|
<acronym>LOR</acronym>
|
|
<glossdef>
|
|
<para>The &os; kernel uses a number of resource locks to
|
|
arbitrate contention for those resources. A run-time
|
|
lock diagnostic system found in &os.current; kernels
|
|
(but removed for releases), called &man.witness.4;,
|
|
detects the potential for deadlocks due to locking errors.
|
|
(&man.witness.4; is actually slightly conservative, so
|
|
it is possible to get false positives.) A true positive
|
|
report indicates that <quote>if you were unlucky, a deadlock would
|
|
have happened here</quote>.</para>
|
|
|
|
<para>True positive LORs tend to get fixed quickly, so
|
|
check &a.current.url; and the
|
|
<ulink url="http://sources.zabbadoz.net/freebsd/lor.html">
|
|
LORs Seen</ulink> page before posting to the mailing lists.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
</glossdiv>
|
|
|
|
<glossdiv>
|
|
<title>M</title>
|
|
|
|
<glossentry>
|
|
<glossterm>MAC</glossterm>
|
|
<glosssee otherterm="mac-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>MADT</glossterm>
|
|
<glosssee otherterm="madt-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>MFC</glossterm>
|
|
<glosssee otherterm="mfc-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>MFP4</glossterm>
|
|
<glosssee otherterm="mfp4-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>MFS</glossterm>
|
|
<glosssee otherterm="mfs-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>MIT</glossterm>
|
|
<glosssee otherterm="mit-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>MLS</glossterm>
|
|
<glosssee otherterm="mls-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>MOTD</glossterm>
|
|
<glosssee otherterm="motd-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>MTA</glossterm>
|
|
<glosssee otherterm="mta-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>MUA</glossterm>
|
|
<glosssee otherterm="mua-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry id="mta-glossary">
|
|
<glossterm>Mail Transfer Agent</glossterm>
|
|
<acronym>MTA</acronym>
|
|
<glossdef>
|
|
<para>An application used to transfer email. An
|
|
<acronym>MTA</acronym> has traditionally been part of the BSD
|
|
base system. Today Sendmail is included in the base system, but
|
|
there are many other <acronym>MTA</acronym>s, such as postfix,
|
|
qmail and Exim.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="mua-glossary">
|
|
<glossterm>Mail User Agent</glossterm>
|
|
<acronym>MUA</acronym>
|
|
<glossdef>
|
|
<para>An application used by users to display and write email.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="mac-glossary">
|
|
<glossterm>Mandatory Access Control</glossterm>
|
|
<acronym>MAC</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="mit-glossary">
|
|
<glossterm>Massachusetts Institute of Technology</glossterm>
|
|
<acronym>MIT</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="mfc-glossary">
|
|
<glossterm>Merge From Current</glossterm>
|
|
<acronym>MFC</acronym>
|
|
<glossdef subject="FreeBSD">
|
|
<para>To merge functionality or a patch from the -CURRENT
|
|
branch to another, most often -STABLE.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="mfp4-glossary">
|
|
<glossterm>Merge From Perforce</glossterm>
|
|
<acronym>MFP4</acronym>
|
|
<glossdef subject="FreeBSD">
|
|
<para>To merge functionality or a patch from the Perforce
|
|
repository to the -CURRENT branch.</para>
|
|
<glossseealso otherterm="perforce-glossary"/>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="mfs-glossary">
|
|
<glossterm>Merge From Stable</glossterm>
|
|
<acronym>MFS</acronym>
|
|
<glossdef subject="FreeBSD">
|
|
<para>In the normal course of FreeBSD development, a change will
|
|
be committed to the -CURRENT branch for testing before being
|
|
merged to -STABLE. On rare occasions, a change will go into
|
|
-STABLE first and then be merged to -CURRENT.</para>
|
|
|
|
<para>This term is also used when a patch is merged from -STABLE
|
|
to a security branch.</para>
|
|
<glossseealso otherterm="mfc-glossary"/>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="motd-glossary">
|
|
<glossterm>Message Of The Day</glossterm>
|
|
<acronym>MOTD</acronym>
|
|
<glossdef>
|
|
<para>A message, usually shown on login, often used to
|
|
distribute information to users of the system.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="mls-glossary">
|
|
<glossterm>Multi-Level Security</glossterm>
|
|
<acronym>MLS</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="madt-glossary">
|
|
<glossterm>Multiple <acronym>APIC</acronym> Description Table</glossterm>
|
|
<acronym>MADT</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
</glossdiv>
|
|
|
|
<glossdiv>
|
|
<title>N</title>
|
|
|
|
<glossentry>
|
|
<glossterm>NAT</glossterm>
|
|
<glosssee otherterm="nat-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>NDISulator</glossterm>
|
|
<glosssee otherterm="projectevil-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>NFS</glossterm>
|
|
<glosssee otherterm="nfs-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>NTFS</glossterm>
|
|
<glosssee otherterm="ntfs-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>NTP</glossterm>
|
|
<glosssee otherterm="ntp-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry id="nat-glossary">
|
|
<glossterm>Network Address Translation</glossterm>
|
|
<acronym>NAT</acronym>
|
|
<glossdef>
|
|
<para>A technique where <acronym>IP</acronym> packets are rewritten
|
|
on the way through a gateway, enabling many machines behind the
|
|
gateway to effectively share a single <acronym>IP</acronym> address.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="nfs-glossary">
|
|
<glossterm>Network File System</glossterm>
|
|
<acronym>NFS</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="ntfs-glossary">
|
|
<glossterm>New Technology File System</glossterm>
|
|
<acronym>NTFS</acronym>
|
|
<glossdef>
|
|
<para>A filesystem developed by Microsoft and available in its
|
|
<quote>New Technology</quote> operating systems, such as
|
|
&windows2k;, &windowsnt; and &windowsxp;.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="ntp-glossary">
|
|
<glossterm>Network Time Protocol</glossterm>
|
|
<acronym>NTP</acronym>
|
|
<glossdef>
|
|
<para>A means of synchronizing clocks over a network.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
</glossdiv>
|
|
|
|
<glossdiv>
|
|
<title>O</title>
|
|
|
|
<glossentry>
|
|
<glossterm>OBE</glossterm>
|
|
<glosssee otherterm="obe-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>ODMR</glossterm>
|
|
<glosssee otherterm="odmr-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>OS</glossterm>
|
|
<glosssee otherterm="os-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry id="odmr-glossary">
|
|
<glossterm>On-Demand Mail Relay</glossterm>
|
|
<acronym>ODMR</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="os-glossary">
|
|
<glossterm>Operating System</glossterm>
|
|
<acronym>OS</acronym>
|
|
<glossdef>
|
|
<para>A set of programs, libraries and tools that provide access to
|
|
the hardware resources of a computer. Operating systems range
|
|
today from simplistic designs that support only one program
|
|
running at a time, accessing only one device to fully
|
|
multi-user, multi-tasking and multi-process systems that can
|
|
serve thousands of users simultaneously, each of them running
|
|
dozens of different applications.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="obe-glossary">
|
|
<glossterm>Overtaken By Events</glossterm>
|
|
<acronym>OBE</acronym>
|
|
<glossdef>
|
|
<para>Indicates a suggested change (such as a Problem Report
|
|
or a feature request) which is no longer relevant or
|
|
applicable due to such things as later changes to &os;,
|
|
changes in networking standards, the affected hardware
|
|
having since become obsolete, and so forth.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
</glossdiv>
|
|
|
|
<glossdiv>
|
|
<title>P</title>
|
|
|
|
<glossentry>
|
|
<glossterm>p4</glossterm>
|
|
<glosssee otherterm="perforce-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>PAE</glossterm>
|
|
<glosssee otherterm="pae-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>PAM</glossterm>
|
|
<glosssee otherterm="pam-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>PAP</glossterm>
|
|
<glosssee otherterm="pap-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>PC</glossterm>
|
|
<glosssee otherterm="pc-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>PCNSFD</glossterm>
|
|
<glosssee otherterm="pcnfsd-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>PDF</glossterm>
|
|
<glosssee otherterm="pdf-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>PID</glossterm>
|
|
<glosssee otherterm="pid-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>POLA</glossterm>
|
|
<glosssee otherterm="pola-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>POP</glossterm>
|
|
<glosssee otherterm="pop-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>POP3</glossterm>
|
|
<glosssee otherterm="pop3-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>PPD</glossterm>
|
|
<glosssee otherterm="ppd-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>PPP</glossterm>
|
|
<glosssee otherterm="ppp-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>PPPoA</glossterm>
|
|
<glosssee otherterm="pppoa-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>PPPoE</glossterm>
|
|
<glosssee otherterm="pppoe-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry id="pppoa-glossary">
|
|
<glossterm><acronym>PPP</acronym> over <acronym>ATM</acronym></glossterm>
|
|
<acronym>PPPoA</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="pppoe-glossary">
|
|
<glossterm><acronym>PPP</acronym> over <acronym>Ethernet</acronym></glossterm>
|
|
<acronym>PPPoE</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>PR</glossterm>
|
|
<glosssee otherterm="pr-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>PXE</glossterm>
|
|
<glosssee otherterm="pxe-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry id="pap-glossary">
|
|
<glossterm>Password Authentication Protocol</glossterm>
|
|
<acronym>PAP</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="perforce-glossary">
|
|
<glossterm>Perforce</glossterm>
|
|
<glossdef>
|
|
<para>A source code control product made by
|
|
<ulink url="http://www.perforce.com/">Perforce Software</ulink>
|
|
which is more advanced than CVS. Although not open source, its use
|
|
is free of charge to open-source projects such as &os;.</para>
|
|
|
|
<para>Some &os; developers use a Perforce repository as a staging
|
|
area for code that is considered too experimental for the
|
|
-CURRENT branch.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="pc-glossary">
|
|
<glossterm>Personal Computer</glossterm>
|
|
<acronym>PC</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="pcnfsd-glossary">
|
|
<glossterm>Personal Computer Network File System Daemon</glossterm>
|
|
<acronym>PCNFSD</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="pae-glossary">
|
|
<glossterm>Physical Address Extensions</glossterm>
|
|
<acronym>PAE</acronym>
|
|
<glossdef>
|
|
<para>A method of enabling access to up to 64 GB of <acronym>RAM</acronym> on
|
|
systems which only physically have a 32-bit wide address space
|
|
(and would therefore be limited to 4 GB without PAE).</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="pam-glossary">
|
|
<glossterm>Pluggable Authentication Modules</glossterm>
|
|
<acronym>PAM</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="ppp-glossary">
|
|
<glossterm>Point-to-Point Protocol</glossterm>
|
|
<acronym>PPP</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="pointyhat">
|
|
<glossterm>Pointy Hat</glossterm>
|
|
<glossdef subject="FreeBSD">
|
|
<para>A mythical piece of headgear, much like a
|
|
<literal>dunce cap</literal>, awarded to any &os;
|
|
committer who breaks the build, makes revision numbers
|
|
go backwards, or creates any other kind of havoc in
|
|
the source base. Any committer worth his or her salt
|
|
will soon accumulate a large collection. The usage is
|
|
(almost always?) humorous.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="pdf-glossary">
|
|
<glossterm>Portable Document Format</glossterm>
|
|
<acronym>PDF</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="pop-glossary">
|
|
<glossterm>Post Office Protocol</glossterm>
|
|
<acronym>POP</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
<glossseealso otherterm="pop3-glossary"/>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="pop3-glossary">
|
|
<glossterm>Post Office Protocol Version 3</glossterm>
|
|
<acronym>POP3</acronym>
|
|
<glossdef>
|
|
<para>A protocol for accessing email messages on a mail server,
|
|
characterised by the messages usually being downloaded from the
|
|
server to the client, as opposed to remaining on the server.</para>
|
|
<glossseealso otherterm="imap-glossary"/>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="ppd-glossary">
|
|
<glossterm>PostScript Printer Description</glossterm>
|
|
<acronym>PPD</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="pxe-glossary">
|
|
<glossterm>Preboot eXecution Environment</glossterm>
|
|
<acronym>PXE</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="pola-glossary">
|
|
<glossterm>Principle Of Least Astonishment</glossterm>
|
|
<acronym>POLA</acronym>
|
|
<glossdef>
|
|
<para>As &os; evolves, changes visible to the user should be
|
|
kept as unsurprising as possible. For example, arbitrarily
|
|
rearranging system startup variables in
|
|
<filename>/etc/defaults/rc.conf</filename> violates
|
|
<acronym>POLA</acronym>. Developers consider
|
|
<acronym>POLA</acronym> when contemplating user-visible
|
|
system changes.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="pr-glossary">
|
|
<glossterm>Problem Report</glossterm>
|
|
<acronym>PR</acronym>
|
|
<glossdef>
|
|
<para>A description of some kind of problem that has been
|
|
found in either the &os; source or documentation. See
|
|
<ulink url="&url.articles.problem-reports;/index.html">
|
|
Writing &os; Problem Reports</ulink>.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="pid-glossary">
|
|
<glossterm>Process ID</glossterm>
|
|
<acronym>PID</acronym>
|
|
<glossdef>
|
|
<para>A number, unique to a particular process on a system,
|
|
which identifies it and allows actions to be taken against it.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="projectevil-glossary">
|
|
<glossterm>Project Evil</glossterm>
|
|
<glossdef subject="FreeBSD">
|
|
<para>The working title for the <acronym>NDISulator</acronym>,
|
|
written by Bill Paul, who named it referring to how awful
|
|
it is (from a philosophical standpoint) to need to have
|
|
something like this in the first place. The
|
|
<acronym>NDISulator</acronym> is a special compatibility
|
|
module to allow Microsoft Windows™ NDIS miniport
|
|
network drivers to be used with &os;/i386. This is usually
|
|
the only way to use cards where the driver is closed-source.
|
|
See <filename>src/sys/compat/ndis/subr_ndis.c</filename>.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
</glossdiv>
|
|
|
|
<glossdiv>
|
|
<title>R</title>
|
|
|
|
<glossentry>
|
|
<glossterm>RA</glossterm>
|
|
<glosssee otherterm="ra-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>RAID</glossterm>
|
|
<glosssee otherterm="raid-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>RAM</glossterm>
|
|
<glosssee otherterm="ram-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>RD</glossterm>
|
|
<glosssee otherterm="rd-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>RFC</glossterm>
|
|
<glosssee otherterm="rfc-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>RISC</glossterm>
|
|
<glosssee otherterm="risc-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>RPC</glossterm>
|
|
<glosssee otherterm="rpc-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>RS232C</glossterm>
|
|
<glosssee otherterm="rs232c-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>RTS</glossterm>
|
|
<glosssee otherterm="rts-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry id="ram-glossary">
|
|
<glossterm>Random Access Memory</glossterm>
|
|
<acronym>RAM</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="rcs-glossary">
|
|
<glossterm>Revision Control System</glossterm>
|
|
<acronym>RCS</acronym>
|
|
<glossdef>
|
|
<para>The <emphasis>Revision Control System</emphasis>
|
|
(<acronym>RCS</acronym>) is one of the oldest software suites
|
|
that implement <quote>revision control</quote> for plain
|
|
files. It allows the storage, retrieval, archival, logging,
|
|
identification and merging of multiple revisions for each
|
|
file. RCS consists of many small tools that work together.
|
|
It lacks some of the features found in more modern revision
|
|
control systems, like CVS or Subversion, but it is very simple
|
|
to install, configure, and start using for a small set of
|
|
files. Implementations of RCS can be found on every major
|
|
UNIX-like OS.</para>
|
|
|
|
<glossseealso otherterm="cvs-glossary"/>
|
|
<glossseealso otherterm="svn-glossary"/>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="rd-glossary">
|
|
<glossterm>Received Data</glossterm>
|
|
<acronym>RD</acronym>
|
|
<glossdef>
|
|
<para>An <acronym>RS232C</acronym> pin or wire that data is
|
|
received on.</para>
|
|
<glossseealso otherterm="td-glossary"/>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="rs232c-glossary">
|
|
<glossterm>Recommended Standard 232C</glossterm>
|
|
<acronym>RS232C</acronym>
|
|
<glossdef>
|
|
<para>A standard for communications between serial devices.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="risc-glossary">
|
|
<glossterm>Reduced Instruction Set Computer</glossterm>
|
|
<acronym>RISC</acronym>
|
|
<glossdef>
|
|
<para>An approach to processor design where the operations the hardware
|
|
can perform are simplified but made as general purpose as possible.
|
|
This can lead to lower power consumption, fewer transistors and in
|
|
some cases, better performance and increased code density. Examples
|
|
of RISC processors include the Alpha, &sparc;, &arm; and
|
|
&powerpc;.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="raid-glossary">
|
|
<glossterm>Redundant Array of Inexpensive Disks</glossterm>
|
|
<acronym>RAID</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="rpc-glossary">
|
|
<glossterm>Remote Procedure Call</glossterm>
|
|
<acronym>RPC</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>repocopy</glossterm>
|
|
<glosssee otherterm="repocopy-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry id="repocopy-glossary">
|
|
<glossterm>Repository Copy</glossterm>
|
|
<glossdef>
|
|
<para>A direct copying of files within the CVS repository.</para>
|
|
|
|
<para>Without a repocopy, if a file needed to be copied or
|
|
moved to another place in the repository, the committer would
|
|
run <command>cvs add</command> to put the file in its new
|
|
location, and then <command>cvs rm</command> on the old file
|
|
if the old copy was being removed.</para>
|
|
|
|
<para>The disadvantage of this method is that the history
|
|
(i.e. the entries in the CVS logs) of the file would not be
|
|
copied to the new location. As the &os; Project considers
|
|
this history very useful, a repository copy is often used
|
|
instead. This is a process where one of the repository meisters
|
|
will copy the files directly within the repository, rather than
|
|
using the &man.cvs.1; program.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="rfc-glossary">
|
|
<glossterm>Request For Comments</glossterm>
|
|
<acronym>RFC</acronym>
|
|
<glossdef>
|
|
<para>A set of documents defining Internet standards, protocols, and
|
|
so forth. See
|
|
<ulink url="http://www.rfc-editor.org/">www.rfc-editor.org</ulink>.
|
|
</para>
|
|
|
|
<para>Also used as a general term when someone has a suggested change
|
|
and wants feedback.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="rts-glossary">
|
|
<glossterm>Request To Send</glossterm>
|
|
<acronym>RTS</acronym>
|
|
<glossdef>
|
|
<para>An <acronym>RS232C</acronym> signal requesting that the remote
|
|
system commences transmission of data.</para>
|
|
<glossseealso otherterm="cts-glossary"/>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="ra-glossary">
|
|
<glossterm>Router Advertisement</glossterm>
|
|
<acronym>RA</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
</glossdiv>
|
|
|
|
<glossdiv>
|
|
<title>S</title>
|
|
|
|
<glossentry>
|
|
<glossterm>SCI</glossterm>
|
|
<glosssee otherterm="sci-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>SCSI</glossterm>
|
|
<glosssee otherterm="scsi-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>SG</glossterm>
|
|
<glosssee otherterm="sg-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>SMB</glossterm>
|
|
<glosssee otherterm="smb-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>SMP</glossterm>
|
|
<glosssee otherterm="smp-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>SMTP</glossterm>
|
|
<glosssee otherterm="smtp-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>SMTP AUTH</glossterm>
|
|
<glosssee otherterm="smtpauth-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>SSH</glossterm>
|
|
<glosssee otherterm="ssh-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>STR</glossterm>
|
|
<glosssee otherterm="str-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>SVN</glossterm>
|
|
<glosssee otherterm="svn-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry id="smtpauth-glossary">
|
|
<glossterm><acronym>SMTP</acronym> Authentication</glossterm>
|
|
<acronym>SMTP AUTH</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="smb-glossary">
|
|
<glossterm>Server Message Block</glossterm>
|
|
<acronym>SMB</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="sg-glossary">
|
|
<glossterm>Signal Ground</glossterm>
|
|
<acronym>SG</acronym>
|
|
<glossdef>
|
|
<para>An <acronym>RS232</acronym> pin or wire that is the ground
|
|
reference for the signal.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="smtp-glossary">
|
|
<glossterm>Simple Mail Transfer Protocol</glossterm>
|
|
<acronym>SMTP</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="ssh-glossary">
|
|
<glossterm>Secure Shell</glossterm>
|
|
<acronym>SSH</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="scsi-glossary">
|
|
<glossterm>Small Computer System Interface</glossterm>
|
|
<acronym>SCSI</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="svn-glossary">
|
|
<glossterm>Subversion</glossterm>
|
|
<acronym>SVN</acronym>
|
|
<glossdef>
|
|
<para>Subversion is a version control system, similar to CVS, but
|
|
with an expanded feature list.</para>
|
|
<glossseealso otherterm="cvs-glossary"/>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="str-glossary">
|
|
<glossterm>Suspend To <acronym>RAM</acronym></glossterm>
|
|
<acronym>STR</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="smp-glossary">
|
|
<glossterm>Symmetric MultiProcessor</glossterm>
|
|
<acronym>SMP</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="sci-glossary">
|
|
<glossterm>System Control Interrupt</glossterm>
|
|
<acronym>SCI</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
</glossdiv>
|
|
|
|
<glossdiv>
|
|
<title>T</title>
|
|
|
|
<glossentry>
|
|
<glossterm>TCP</glossterm>
|
|
<glosssee otherterm="tcp-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>TCP/IP</glossterm>
|
|
<glosssee otherterm="tcpip-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>TD</glossterm>
|
|
<glosssee otherterm="td-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>TFTP</glossterm>
|
|
<glosssee otherterm="tftp-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>TGT</glossterm>
|
|
<glosssee otherterm="tgt-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>TSC</glossterm>
|
|
<glosssee otherterm="tsc-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry id="tgt-glossary">
|
|
<glossterm>Ticket-Granting Ticket</glossterm>
|
|
<acronym>TGT</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="tsc-glossary">
|
|
<glossterm>Time Stamp Counter</glossterm>
|
|
<acronym>TSC</acronym>
|
|
<!-- From dg@, 20040814125503.GF40460@nexus.dglawrence.com -->
|
|
<glossdef>
|
|
<para>A profiling counter internal to modern &pentium; processors
|
|
that counts core frequency clock ticks.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="tcp-glossary">
|
|
<glossterm>Transmission Control Protocol</glossterm>
|
|
<acronym>TCP</acronym>
|
|
<glossdef>
|
|
<para>A protocol that sits on top of (e.g.) the <acronym>IP</acronym>
|
|
protocol and guarantees that packets are delivered in a reliable,
|
|
ordered, fashion.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="tcpip-glossary">
|
|
<glossterm>Transmission Control Protocol/Internet Protocol</glossterm>
|
|
<acronym>TCP/IP</acronym>
|
|
<glossdef>
|
|
<para>The term for the combination of the <acronym>TCP</acronym>
|
|
protocol running over the <acronym>IP</acronym> protocol. Much of
|
|
the Internet runs over <acronym>TCP/IP</acronym>.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="td-glossary">
|
|
<glossterm>Transmitted Data</glossterm>
|
|
<acronym>TD</acronym>
|
|
<glossdef>
|
|
<para>An <acronym>RS232C</acronym> pin or wire that data is transmitted
|
|
on.</para>
|
|
<glossseealso otherterm="rd-glossary"/>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="tftp-glossary">
|
|
<glossterm>Trivial <acronym>FTP</acronym></glossterm>
|
|
<acronym>TFTP</acronym>
|
|
<glossdef>
|
|
<para></para>
|
|
</glossdef>
|
|
</glossentry>
|
|
</glossdiv>
|
|
|
|
<glossdiv>
|
|
<title>U</title>
|
|
|
|
<glossentry>
|
|
<glossterm>UDP</glossterm>
|
|
<glosssee otherterm="udp-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>UFS1</glossterm>
|
|
<glosssee otherterm="ufs1-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>UFS2</glossterm>
|
|
<glosssee otherterm="ufs2-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>UID</glossterm>
|
|
<glosssee otherterm="uid-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>URL</glossterm>
|
|
<glosssee otherterm="url-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry>
|
|
<glossterm>USB</glossterm>
|
|
<glosssee otherterm="usb-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry id="url-glossary">
|
|
<glossterm>Uniform Resource Locator</glossterm>
|
|
<acronym>URL</acronym>
|
|
<glossdef>
|
|
<para>A method of locating a resource, such as a document on
|
|
the Internet and a means to identify that resource.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="ufs1-glossary">
|
|
<glossterm>Unix File System Version 1</glossterm>
|
|
<acronym>UFS1</acronym>
|
|
<glossdef>
|
|
<para>The original &unix; file system, sometimes called the
|
|
Berkeley Fast File System.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="ufs2-glossary">
|
|
<glossterm>Unix File System Version 2</glossterm>
|
|
<acronym>UFS2</acronym>
|
|
<glossdef>
|
|
<para>An extension to <acronym>UFS1</acronym>, introduced in
|
|
&os; 5-CURRENT. <acronym>UFS2</acronym> adds 64 bit block
|
|
pointers (breaking the 1T barrier), support for extended file
|
|
storage and other features.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="usb-glossary">
|
|
<glossterm>Universal Serial Bus</glossterm>
|
|
<acronym>USB</acronym>
|
|
<glossdef>
|
|
<para>A hardware standard used to connect a wide variety of
|
|
computer peripherals to a universal interface.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="uid-glossary">
|
|
<glossterm>User ID</glossterm>
|
|
<acronym>UID</acronym>
|
|
<glossdef>
|
|
<para>A unique number assigned to each user of a computer,
|
|
by which the resources and permissions assigned to that
|
|
user can be identified.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
|
|
<glossentry id="udp-glossary">
|
|
<glossterm>User Datagram Protocol</glossterm>
|
|
<acronym>UDP</acronym>
|
|
<glossdef>
|
|
<para>A simple, unreliable datagram protocol which is used
|
|
for exchanging data on a TCP/IP network. <acronym>UDP</acronym>
|
|
does not provide error checking and correction like
|
|
<acronym>TCP</acronym>.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
</glossdiv>
|
|
|
|
<glossdiv>
|
|
<title>V</title>
|
|
|
|
<glossentry>
|
|
<glossterm>VPN</glossterm>
|
|
<glosssee otherterm="vpn-glossary"/>
|
|
</glossentry>
|
|
|
|
<glossentry id="vpn-glossary">
|
|
<glossterm>Virtual Private Network</glossterm>
|
|
<acronym>VPN</acronym>
|
|
<glossdef>
|
|
<para>A method of using a public telecommunication
|
|
such as the Internet, to provide remote access to a
|
|
localized network, such as a corporate
|
|
<acronym>LAN</acronym>.</para>
|
|
</glossdef>
|
|
</glossentry>
|
|
</glossdiv>
|
|
</glossary>
|
|
'>
|