| 1 | <?xml version="1.0" encoding="iso-8859-1"?>
|
|---|
| 2 | <!DOCTYPE glossary PUBLIC "-//Samba-Team//DTD DocBook V4.2-Based Variant V1.0//EN" "http://www.samba.org/samba/DTD/samba-doc">
|
|---|
| 3 | <glossary>
|
|---|
| 4 | <title>Glossary</title>
|
|---|
| 5 |
|
|---|
| 6 | <glossentry>
|
|---|
| 7 | <glossterm>Access Control List</glossterm>
|
|---|
| 8 | <acronym>ACL</acronym>
|
|---|
| 9 | <glossdef><para>
|
|---|
| 10 | A detailed list of permissions granted to users or groups with respect to file and network resource access.
|
|---|
| 11 | See <link linkend="AccessControls"/>,
|
|---|
| 12 | for details.</para></glossdef>
|
|---|
| 13 | </glossentry>
|
|---|
| 14 |
|
|---|
| 15 | <glossentry>
|
|---|
| 16 | <glossterm>Active Directory Service</glossterm>
|
|---|
| 17 | <acronym>ADS</acronym>
|
|---|
| 18 | <glossdef><para>
|
|---|
| 19 | A service unique to Microsoft Windows 200x servers that provides a centrally managed
|
|---|
| 20 | directory for management of user identities and computer objects, as well as the permissions
|
|---|
| 21 | each user or computer may be granted to access
|
|---|
| 22 | distributed network resources. ADS uses Kerberos-based
|
|---|
| 23 | authentication and LDAP over Kerberos for directory access.
|
|---|
| 24 | </para></glossdef>
|
|---|
| 25 | </glossentry>
|
|---|
| 26 |
|
|---|
| 27 | <glossentry>
|
|---|
| 28 | <glossterm>Common Internet File System</glossterm>
|
|---|
| 29 | <acronym>CIFS</acronym>
|
|---|
| 30 | <glossdef><para>The new name for SMB. Microsoft renamed the
|
|---|
| 31 | SMB protocol to CIFS during the Internet hype in the nineties.
|
|---|
| 32 | At about the time that the SMB protocol was renamed to CIFS, an
|
|---|
| 33 | additional dialect of the SMB protocol was in development.
|
|---|
| 34 | The need for the deployment of the NetBIOS layer was also
|
|---|
| 35 | removed, thus paving the way for use of the SMB protocol natively
|
|---|
| 36 | over TCP/IP (known as NetBIOS-less SMB or <quote>naked</quote> TCP transport).
|
|---|
| 37 | </para></glossdef>
|
|---|
| 38 | </glossentry>
|
|---|
| 39 |
|
|---|
| 40 | <glossentry>
|
|---|
| 41 | <glossterm>Common UNIX Printing System</glossterm>
|
|---|
| 42 | <acronym>CUPS</acronym>
|
|---|
| 43 | <glossdef><para>
|
|---|
| 44 | A recent implementation of a high capability printing system for UNIX developed by
|
|---|
| 45 | <ulink url="http://www.easysw.com/"></ulink>. The design objective of CUPS was to provide
|
|---|
| 46 | a rich print processing system that has built-in intelligence capable of correctly rendering (processing)
|
|---|
| 47 | a file that is submitted for printing even if it was formatted for an entirely different printer.
|
|---|
| 48 | </para>
|
|---|
| 49 | </glossdef>
|
|---|
| 50 | </glossentry>
|
|---|
| 51 |
|
|---|
| 52 | <glossentry>
|
|---|
| 53 | <glossterm>Domain Master Browser</glossterm>
|
|---|
| 54 | <acronym>DMB</acronym>
|
|---|
| 55 | <glossdef><para>The domain master browser maintains a list of all the servers that
|
|---|
| 56 | have announced their services within a given workgroup or NT domain. See <link linkend="DMB"/> for details.
|
|---|
| 57 | </para></glossdef>
|
|---|
| 58 | </glossentry>
|
|---|
| 59 |
|
|---|
| 60 | <glossentry>
|
|---|
| 61 | <glossterm>Domain Name Service</glossterm>
|
|---|
| 62 | <acronym>DNS</acronym>
|
|---|
| 63 | <glossdef><para>
|
|---|
| 64 | A protocol by which computer hostnames may be resolved to the matching IP address/es. DNS is implemented
|
|---|
| 65 | by the Berkeley Internet Name Daemon. There exists a recent version of DNS that allows dynamic name registration
|
|---|
| 66 | by network clients or by a DHCP server. This recent protocol is known as dynamic DNS (DDNS).
|
|---|
| 67 | </para></glossdef>
|
|---|
| 68 | </glossentry>
|
|---|
| 69 |
|
|---|
| 70 | <glossentry>
|
|---|
| 71 | <glossterm>Dynamic Host Configuration Protocol</glossterm>
|
|---|
| 72 | <acronym>DHCP</acronym>
|
|---|
| 73 | <glossdef><para>
|
|---|
| 74 | A protocol that was based on the BOOTP protocol that may be used to dynamically assign an IP address,
|
|---|
| 75 | from a reserved pool of addresses, to a network client or device. Additionally, DHCP may assign all
|
|---|
| 76 | network configuration settings and may be used to register a computer name and its address with a
|
|---|
| 77 | dynamic DNS server.
|
|---|
| 78 | </para></glossdef>
|
|---|
| 79 | </glossentry>
|
|---|
| 80 | <glossentry>
|
|---|
| 81 | <glossterm>Extended Meta-file Format</glossterm>
|
|---|
| 82 | <acronym>EMF</acronym>
|
|---|
| 83 | <glossdef>
|
|---|
| 84 | <para>
|
|---|
| 85 | An intermediate file format used by Microsoft Windows-based servers and clients. EMF files may be
|
|---|
| 86 | rendered into a page description language by a print processor.
|
|---|
| 87 | </para>
|
|---|
| 88 | </glossdef>
|
|---|
| 89 | </glossentry>
|
|---|
| 90 |
|
|---|
| 91 | <glossentry>
|
|---|
| 92 | <glossterm>Graphical Device Interface</glossterm>
|
|---|
| 93 | <acronym>GDI</acronym>
|
|---|
| 94 | <glossdef><para>
|
|---|
| 95 | Device-independent format for printing used by Microsoft Windows.
|
|---|
| 96 | It is quite similar to what PostScript is for UNIX. Printing jobs are first generated in GDI and
|
|---|
| 97 | then converted to a device-specific format. See <link linkend="gdipost"/> for details.
|
|---|
| 98 | </para></glossdef>
|
|---|
| 99 | </glossentry>
|
|---|
| 100 |
|
|---|
| 101 | <glossentry>
|
|---|
| 102 | <glossterm>Group IDentifier</glossterm>
|
|---|
| 103 | <acronym>GID</acronym>
|
|---|
| 104 | <glossdef><para>
|
|---|
| 105 | The UNIX system group identifier; on older systems, a 32-bit unsigned integer, and on newer systems
|
|---|
| 106 | an unsigned 64-bit integer. The GID is used in UNIX-like operating systems for all group-level access
|
|---|
| 107 | control.
|
|---|
| 108 | </para></glossdef>
|
|---|
| 109 | </glossentry>
|
|---|
| 110 |
|
|---|
| 111 | <glossentry>
|
|---|
| 112 | <glossterm>Internet Print Protocol</glossterm>
|
|---|
| 113 | <acronym>IPP</acronym>
|
|---|
| 114 | <glossdef><para>An IETF standard for network printing. CUPS
|
|---|
| 115 | implements IPP.</para></glossdef>
|
|---|
| 116 | </glossentry>
|
|---|
| 117 |
|
|---|
| 118 | <glossentry>
|
|---|
| 119 | <glossterm>Key Distribution Center</glossterm>
|
|---|
| 120 | <acronym>KDC</acronym>
|
|---|
| 121 | <glossdef><para>The Kerberos authentication protocol makes use of security keys (also called a ticket)
|
|---|
| 122 | by which access to network resources is controlled. The issuing of Kerberos tickets is effected by
|
|---|
| 123 | a KDC.</para></glossdef>
|
|---|
| 124 | </glossentry>
|
|---|
| 125 |
|
|---|
| 126 | <glossentry>
|
|---|
| 127 | <glossterm>NetBIOS Extended User Interface</glossterm>
|
|---|
| 128 | <acronym>NetBEUI</acronym>
|
|---|
| 129 | <glossdef><para>
|
|---|
| 130 | Very simple network protocol invented by IBM and Microsoft. It is used
|
|---|
| 131 | to do NetBIOS over Ethernet with low overhead. NetBEUI is a nonroutable
|
|---|
| 132 | protocol.
|
|---|
| 133 | </para></glossdef>
|
|---|
| 134 | </glossentry>
|
|---|
| 135 |
|
|---|
| 136 | <glossentry>
|
|---|
| 137 | <glossterm>Network Basic Input/Output System</glossterm>
|
|---|
| 138 | <acronym>NetBIOS</acronym>
|
|---|
| 139 | <glossdef><para>
|
|---|
| 140 | NetBIOS is a simple application programming interface (API) invented in the 1980s
|
|---|
| 141 | that allows programs to send data to certain network names.
|
|---|
| 142 | NetBIOS is always run over another network protocol such
|
|---|
| 143 | as IPX/SPX, TCP/IP, or Logical Link Control (LLC). NetBIOS run over LLC
|
|---|
| 144 | is best known as NetBEUI (NetBIOS Extended User Interface &smbmdash; a complete misnomer!).
|
|---|
| 145 | </para></glossdef>
|
|---|
| 146 | </glossentry>
|
|---|
| 147 |
|
|---|
| 148 |
|
|---|
| 149 | <glossentry>
|
|---|
| 150 | <glossterm>NetBT</glossterm>
|
|---|
| 151 | <acronym>NBT</acronym>
|
|---|
| 152 | <glossdef><para>Protocol for transporting NetBIOS frames over TCP/IP. Uses ports 137, 138, and 139.
|
|---|
| 153 | NetBT is a fully routable protocol.
|
|---|
| 154 | </para></glossdef>
|
|---|
| 155 | </glossentry>
|
|---|
| 156 |
|
|---|
| 157 | <glossentry>
|
|---|
| 158 | <glossterm>Local Master Browser</glossterm>
|
|---|
| 159 | <acronym>LMB</acronym>
|
|---|
| 160 | <glossdef><para>The local master browser maintains a list
|
|---|
| 161 | of all servers that have announced themselves within a given workgroup or NT domain on a particular
|
|---|
| 162 | broadcast-isolated subnet. See <link linkend="DMB"/> for details.
|
|---|
| 163 | </para></glossdef>
|
|---|
| 164 | </glossentry>
|
|---|
| 165 |
|
|---|
| 166 | <glossentry>
|
|---|
| 167 | <glossterm>Printer Command Language</glossterm>
|
|---|
| 168 | <acronym>PCL</acronym>
|
|---|
| 169 | <glossdef><para>
|
|---|
| 170 | A printer page description language that was developed by Hewlett-Packard
|
|---|
| 171 | and is in common use today.
|
|---|
| 172 | </para></glossdef>
|
|---|
| 173 | </glossentry>
|
|---|
| 174 |
|
|---|
| 175 | <glossentry>
|
|---|
| 176 | <glossterm>Portable Document Format</glossterm>
|
|---|
| 177 | <acronym>PDF</acronym>
|
|---|
| 178 | <glossdef>
|
|---|
| 179 | <para>
|
|---|
| 180 | A highly compressed document format, based on PostScript, used as a document distribution format
|
|---|
| 181 | that is supported by Web browsers as well as many applications. Adobe also distributes an application
|
|---|
| 182 | called <quote>Acrobat,</quote> which is a PDF reader.
|
|---|
| 183 | </para>
|
|---|
| 184 | </glossdef>
|
|---|
| 185 | </glossentry>
|
|---|
| 186 |
|
|---|
| 187 | <glossentry>
|
|---|
| 188 | <glossterm>Page Description Language</glossterm>
|
|---|
| 189 | <acronym>PDL</acronym>
|
|---|
| 190 | <glossdef><para>A language for describing the layout and contents of a printed page.
|
|---|
| 191 | The best-known PDLs are Adobe PostScript and Hewlett-Packard PCL (Printer Control Language),
|
|---|
| 192 | both of which are used to control laser printers.</para></glossdef>
|
|---|
| 193 | </glossentry>
|
|---|
| 194 |
|
|---|
| 195 | <glossentry>
|
|---|
| 196 | <glossterm>PostScript Printer Description</glossterm>
|
|---|
| 197 | <acronym>PPD</acronym>
|
|---|
| 198 | <glossdef><para>
|
|---|
| 199 | PPDs specify and control options supported by PostScript printers, such as duplexing, stapling,
|
|---|
| 200 | and DPI. See also <link linkend="post-and-ghost"/>. PPD files can be read by printing applications
|
|---|
| 201 | to enable correct PostScript page layout for a particular PostScript printer.
|
|---|
| 202 | </para></glossdef>
|
|---|
| 203 | </glossentry>
|
|---|
| 204 |
|
|---|
| 205 | <glossentry>
|
|---|
| 206 | <glossterm>Remote Procedure Call</glossterm>
|
|---|
| 207 | <acronym>RPC</acronym>
|
|---|
| 208 | <glossdef><para>
|
|---|
| 209 | RPCs are a means for executing network operations. The RPC protocol is independent of transport protocols. RPC
|
|---|
| 210 | does not try to implement any kind of reliability and the application that uses RPCs must be aware of the type
|
|---|
| 211 | of transport protocol underneath RPC. An RPC is like a programmatic jump subroutine over a network. RPCs used
|
|---|
| 212 | in the UNIX environment are specified in RFC 1050. RPC is a powerful technique for constructing distributed,
|
|---|
| 213 | client-server based applications. It is based on extending the notion of conventional, or local procedure
|
|---|
| 214 | calling, so that the called procedure need not exist in the same address space as the calling procedure. The
|
|---|
| 215 | two processes may be on the same system, or they may be on different systems with a network connecting them.
|
|---|
| 216 | By using RPC, programmers of distributed applications avoid the details of the interface with the network. The
|
|---|
| 217 | transport independence of RPC isolates the application from the physical and logical elements of the data
|
|---|
| 218 | communications mechanism and allows the application to use a variety of transports.
|
|---|
| 219 | </para></glossdef>
|
|---|
| 220 | </glossentry>
|
|---|
| 221 |
|
|---|
| 222 | <glossentry>
|
|---|
| 223 | <glossterm>Server Message Block</glossterm>
|
|---|
| 224 | <acronym>SMB</acronym>
|
|---|
| 225 | <glossdef><para>
|
|---|
| 226 | SMB was the original name of the protocol `spoken' by
|
|---|
| 227 | Samba. It was invented in the 1980s by IBM and adopted
|
|---|
| 228 | and extended further by Microsoft. Microsoft
|
|---|
| 229 | renamed the protocol to CIFS during the Internet hype in the
|
|---|
| 230 | 1990s.
|
|---|
| 231 | </para></glossdef>
|
|---|
| 232 | </glossentry>
|
|---|
| 233 |
|
|---|
| 234 | <glossentry>
|
|---|
| 235 | <glossterm>User IDentifier</glossterm>
|
|---|
| 236 | <acronym>UID</acronym>
|
|---|
| 237 | <glossdef><para>
|
|---|
| 238 | The UNIX system user identifier; on older systems a 32-bit unsigned integer, and on newer systems,
|
|---|
| 239 | an unsigned 64-bit integer. The UID is used in UNIX-like operating systems for all user-level access
|
|---|
| 240 | control.
|
|---|
| 241 | </para></glossdef>
|
|---|
| 242 | </glossentry>
|
|---|
| 243 |
|
|---|
| 244 | <glossentry>
|
|---|
| 245 | <glossterm>Universal Naming Convention</glossterm>
|
|---|
| 246 | <acronym>UNC</acronym>
|
|---|
| 247 | <glossdef><para>A syntax for specifying the location of network resources (such as file shares).
|
|---|
| 248 | The UNC syntax was developed in the early days of MS DOS 3.x and is used internally by the SMB protocol.
|
|---|
| 249 | </para></glossdef>
|
|---|
| 250 | </glossentry>
|
|---|
| 251 |
|
|---|
| 252 |
|
|---|
| 253 |
|
|---|
| 254 | </glossary>
|
|---|
