LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

Now in proper alphabetical order.

This commit is contained in:
binh 2004-06-21 07:02:01 +00:00
parent f5f7136580
commit 2769be0908
1 changed files with 156 additions and 156 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

312
LDP/guide/docbook/Linux-Filesystem-Hierarchy/Glossary.xml
View File

@ -12,17 +12,6 @@ The Advanced Research and Projects Agency of the United States Department of Def
</glossdef>
</glossentry>
<glossentry>
<glossterm>
Bourne Shell
</glossterm>
<glossdef>
<para>
The Bourne shell is the original Unix shell (command execution program, often called a command interpreter) that was developed at AT&amp;T. Named for its developer, Stephen Bourne, the Bourne shell is also known by its program name, sh. The shell prompt (character displayed to indicate readiness for input) used is the $ symbol. The Bourne shell family includes the Bourne, Korn shell, bash, and zsh shells. Bourne Again Shell (bash) is the free version of the Bourne shell distributed with Linux systems. Bash is similar to the original, but has added features such as command line editing. Its name is sometimes spelled as Bourne Again SHell, the capitalized Hell referring to the difficulty some people have with it.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
BASH
@ -34,6 +23,17 @@ The Bourne Again Shell and is based on the Bourne shell, sh, the original comman
</glossdef>
</glossentry>
<glossentry>
<glossterm>
Bourne Shell
</glossterm>
<glossdef>
<para>
The Bourne shell is the original Unix shell (command execution program, often called a command interpreter) that was developed at AT&amp;T. Named for its developer, Stephen Bourne, the Bourne shell is also known by its program name, sh. The shell prompt (character displayed to indicate readiness for input) used is the $ symbol. The Bourne shell family includes the Bourne, Korn shell, bash, and zsh shells. Bourne Again Shell (bash) is the free version of the Bourne shell distributed with Linux systems. Bash is similar to the original, but has added features such as command line editing. Its name is sometimes spelled as Bourne Again SHell, the capitalized Hell referring to the difficulty some people have with it.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
CLI
@ -45,6 +45,28 @@ A CLI (command line interface) is a user interface to a computer's operating sys
</glossdef>
</glossentry>
<glossentry>
<glossterm>
core
</glossterm>
<glossdef>
<para>
A core file is created when a program terminates unexpectedly, due to a bug, or a violation of the operating system's or hardware's protection mechanisms. The operating system kills the program and creates a core file that programmers can use to figure out what went wrong. It contains a detailed description of the state that the program was in when it died. If would like to determine what program a core file came from, use the file command, like this: $ file core That will tell you the name of the program that produced the core dump. You may want to write the maintainer(s) of the program, telling them that their program dumped core. To Enable or Disable Core Dumps you must use the ulimit command in bash, the limit command in tcsh, or the rlimit command in ksh. See the appropriate manual page for details. This setting affects all programs run from the shell (directly or indirectly), not the whole system. If you wish to enable or disable core dumping for all processes by default, you can change the default setting in /usr/include/linux/sched.h. Refer to definition of INIT_TASK, and look also in /usr/include/linux/resource.h. PAM support optimizes the system's environment, including the amount of memory a user is allowed. In some distributions this parameter is configurable in the /etc/security/limits.conf file. For more information, refer to the Linux Administrator's Security Guide.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
daemon
</glossterm>
<glossdef>
<para>
A process lurking in the background, usually unnoticed, until something triggers it into action. For example, the \cmd{update} daemon wakes up every thirty seconds or so to flush the buffer cache, and the \cmd{sendmail} daemon awakes whenever someone sends mail.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
DARPA
@ -78,6 +100,17 @@ Domain Name System translates Internet domain and host names to IP addresses. DN
</glossdef>
</glossentry>
<glossentry>
<glossterm>
environment variable
</glossterm>
<glossdef>
<para>
A variable that is available to any program that is started by the shell.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
ESD
@ -89,6 +122,17 @@ Enlightened Sound Daemon. This program is designed to mix together several digit
</glossdef>
</glossentry>
<glossentry>
<glossterm>
filesystem
</glossterm>
<glossdef>
<para>
The methods and data structures that an operating system uses to keep track of files on a disk or partition; the way the files are organized on the disk. Also used to describe a partition or disk that is used to store the files or the type of the filesystem.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
FSSTND
@ -111,149 +155,6 @@ Graphical User Interface. The use of pictures rather than just words to represen
</glossdef>
</glossentry>
<glossentry>
<glossterm>
MTA
</glossterm>
<glossdef>
<para>
Mail Transfer Agents. Alongside the web, mail is the top reason for the popularity of the Internet. E-mail is an inexpensive and fast method of time-shifted messaging which, much like the Web, is actually based around sending and receiving plain text files. The protocol used is called the Simple Mail Transfer Protocol (SMTP). The server programs that implement SMTP to move mail from one server to another are called MTAs. Once upon a time users would have to Telnet into an SMTP server and use a command line mail program like 'mutt' or 'pine' to check their mail. Now, GUI based e-mail clients like Mozilla, Kmail and Outlook allow users to check their email off of a local SMTP sever. Additional protocols like POP3 and IMAP4 are used between the SMTP server and desktop mail client to allow clients to manipulate files on, and download from, their local mail server. The programs that implement POP3 and IMAP4 are called Mail Delivery Agents (MDAs). They are generally separate from MTAs.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
NFS
</glossterm>
<glossdef>
<para>
Network File System, is the UNIX equivalent of Server Message Block (SMB). It is a way through which different machines can import and export local files between each other. Like SMB though, NFS sends information including user passwords unencrypted, so it's best to limit its usage to within your local network.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
PAM
</glossterm>
<glossdef>
<para>
Pluggable Authentication Modules. A suite of shared libraries that determine how a user will be authenticated. For example, conventionally UNIX users authenticate themselves by supplying a password at the password prompt after they have typed their name at the login prompt. In many circumstances, such as internal access to workstations, this simple form of authentication is considered sufficient. In other cases, more information is warranted. If a user wants to log in to an internal system from an external source, like the Internet, more or alternative information may be required - perhaps a one-time password. PAM provides this type of capability and much more. Most important, PAM modules allow you to configure your environment with the necessary level of security.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
PATH
</glossterm>
<glossdef>
<para>
The shell looks for commands and programs in a list of file paths stored in the PATH environment variable. An environment variable stores information in a place where other programs and commands can access it. Environment variables store information such as the shell that you are using, your login name, and your current working directory. To see a list of all the environment variables currently defined; type 'set' at the prompt. When you type a command at the shell prompt, the shell will look for that command's program file in each directory listed in the PATH variable, in order. The first program found matching the command you typed will be run. If the command's program file is not in a directory listed in you PATH environment variable, the shell returns a "commands not found" error. By default, the shell does not look in your current working directory or your home directory for commands This is really a security mechanism so that you don't execute programs by accident. What if a malicious user put a harmful program called ls in your home directory? If you typed ls and the shell looked for the fake program in your home directory before the real program in the /bin directory, what do you think would happen? If you thought bad things, you are on the right track. Since your PATH doesn't have the current directory as one of its search locations, programs in your current directory must be called with an absolute path of a relative path specified as './program-name'. To see what directories are part of your PATH enter this command: # echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
SSH
</glossterm>
<glossdef>
<para>
The Secure Shell, or SSH, provides a way of running command line and graphical applications, and transferring files, over an encrypted connection, all that will be seen is junk. It is both a protocol and a suite of small command line applications, which can be used for various functions. SSH replaces the old Telnet application, and can be used for secure remote administration of machines across the Internet. However, it also has other features. SSH increases the ease of running applications remotely by setting up X permissions automatically. If you can log into a machine, it allows you to run a graphical application on it, unlike Telnet, which requires users to have an understanding of the X authentication mechanisms that are manipulated through the xauth and xhost commands. SSH also has inbuilt compression, which allows your graphic applications to run much faster over the network. SCP (Secure Copy) and SFTP (Secure FTP) allow transfer of files over the remote link, either via SSH's own command line utilities or graphical tools like Gnome's GFTP. Like Telnet, SSH is cross-platform. You can find SSH server and clients for Linux, Unix and all flavours of Windows, BeOS, PalmOS, Java and embedded Oses used in routers.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
STDERR
</glossterm>
<glossdef>
<para>
Standard error. A special type of output used for error messages. The file descriptor for STDERR is 2.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
STDIN
</glossterm>
<glossdef>
<para>
Standard input. User input is read from STDIN. The file descriptor for STDIN is 0.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
STDOUT
</glossterm>
<glossdef>
<para>
Standard output. The output of scripts is usually to STDOUT. The file descriptor for STDOUT is 1.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
ZSH
</glossterm>
<glossdef>
<para>
Zsh was developed by Paul Falstad as a replacement for both the Bourne and C shell. It incorporates features of all the other shells (such as file name completion and a history mechanism) as well as new capabilities. Zsh is considered similar to the Korn shell. Falstad intended to create in zsh a shell that would do whatever a programmer might reasonably hope it would do. Zsh is popular with advanced users. Along with the Korn shell and the C shell, the Bourne shell remains among the three most widely used and is included with all UNIX systems. The Bourne shell is often considered the best shell for developing scripts.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
core
</glossterm>
<glossdef>
<para>
A core file is created when a program terminates unexpectedly, due to a bug, or a violation of the operating system's or hardware's protection mechanisms. The operating system kills the program and creates a core file that programmers can use to figure out what went wrong. It contains a detailed description of the state that the program was in when it died. If would like to determine what program a core file came from, use the file command, like this: $ file core That will tell you the name of the program that produced the core dump. You may want to write the maintainer(s) of the program, telling them that their program dumped core. To Enable or Disable Core Dumps you must use the ulimit command in bash, the limit command in tcsh, or the rlimit command in ksh. See the appropriate manual page for details. This setting affects all programs run from the shell (directly or indirectly), not the whole system. If you wish to enable or disable core dumping for all processes by default, you can change the default setting in /usr/include/linux/sched.h. Refer to definition of INIT_TASK, and look also in /usr/include/linux/resource.h. PAM support optimizes the system's environment, including the amount of memory a user is allowed. In some distributions this parameter is configurable in the /etc/security/limits.conf file. For more information, refer to the Linux Administrator's Security Guide.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
daemon
</glossterm>
<glossdef>
<para>
A process lurking in the background, usually unnoticed, until something triggers it into action. For example, the \cmd{update} daemon wakes up every thirty seconds or so to flush the buffer cache, and the \cmd{sendmail} daemon awakes whenever someone sends mail.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
environment variable
</glossterm>
<glossdef>
<para>
A variable that is available to any program that is started by the shell.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
filesystem
</glossterm>
<glossdef>
<para>
The methods and data structures that an operating system uses to keep track of files on a disk or partition; the way the files are organized on the disk. Also used to describe a partition or disk that is used to store the files or the type of the filesystem.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
hard link
@ -331,6 +232,28 @@ Every version of UNIX comes with an extensive collection of online help pages ca
</glossdef>
</glossentry>
<glossentry>
<glossterm>
MTA
</glossterm>
<glossdef>
<para>
Mail Transfer Agents. Alongside the web, mail is the top reason for the popularity of the Internet. E-mail is an inexpensive and fast method of time-shifted messaging which, much like the Web, is actually based around sending and receiving plain text files. The protocol used is called the Simple Mail Transfer Protocol (SMTP). The server programs that implement SMTP to move mail from one server to another are called MTAs. Once upon a time users would have to Telnet into an SMTP server and use a command line mail program like 'mutt' or 'pine' to check their mail. Now, GUI based e-mail clients like Mozilla, Kmail and Outlook allow users to check their email off of a local SMTP sever. Additional protocols like POP3 and IMAP4 are used between the SMTP server and desktop mail client to allow clients to manipulate files on, and download from, their local mail server. The programs that implement POP3 and IMAP4 are called Mail Delivery Agents (MDAs). They are generally separate from MTAs.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
NFS
</glossterm>
<glossdef>
<para>
Network File System, is the UNIX equivalent of Server Message Block (SMB). It is a way through which different machines can import and export local files between each other. Like SMB though, NFS sends information including user passwords unencrypted, so it's best to limit its usage to within your local network.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
operating system
@ -342,6 +265,28 @@ Software that shares a computer system's resources (processor, memory, disk spac
</glossdef>
</glossentry>
<glossentry>
<glossterm>
PAM
</glossterm>
<glossdef>
<para>
Pluggable Authentication Modules. A suite of shared libraries that determine how a user will be authenticated. For example, conventionally UNIX users authenticate themselves by supplying a password at the password prompt after they have typed their name at the login prompt. In many circumstances, such as internal access to workstations, this simple form of authentication is considered sufficient. In other cases, more information is warranted. If a user wants to log in to an internal system from an external source, like the Internet, more or alternative information may be required - perhaps a one-time password. PAM provides this type of capability and much more. Most important, PAM modules allow you to configure your environment with the necessary level of security.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
PATH
</glossterm>
<glossdef>
<para>
The shell looks for commands and programs in a list of file paths stored in the PATH environment variable. An environment variable stores information in a place where other programs and commands can access it. Environment variables store information such as the shell that you are using, your login name, and your current working directory. To see a list of all the environment variables currently defined; type 'set' at the prompt. When you type a command at the shell prompt, the shell will look for that command's program file in each directory listed in the PATH variable, in order. The first program found matching the command you typed will be run. If the command's program file is not in a directory listed in you PATH environment variable, the shell returns a "commands not found" error. By default, the shell does not look in your current working directory or your home directory for commands This is really a security mechanism so that you don't execute programs by accident. What if a malicious user put a harmful program called ls in your home directory? If you typed ls and the shell looked for the fake program in your home directory before the real program in the /bin directory, what do you think would happen? If you thought bad things, you are on the right track. Since your PATH doesn't have the current directory as one of its search locations, programs in your current directory must be called with an absolute path of a relative path specified as './program-name'. To see what directories are part of your PATH enter this command: # echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
pipes and sockets
@ -410,11 +355,44 @@ Software interrupts sent to a program to indicate that an important event has oc
<glossentry>
<glossterm>
symbolic link or soft link
SSH
</glossterm>
<glossdef>
<para>
A special filetype, which is a small pointer file, allowing multiple names for the same file. Unlike hard links, symbolic links can be made for directories and can be made across filesystems. Commands that access the file being pointed to are said to follow the symbolic link. Commands that access the link itself do not follow the symbolic link.
The Secure Shell, or SSH, provides a way of running command line and graphical applications, and transferring files, over an encrypted connection, all that will be seen is junk. It is both a protocol and a suite of small command line applications, which can be used for various functions. SSH replaces the old Telnet application, and can be used for secure remote administration of machines across the Internet. However, it also has other features. SSH increases the ease of running applications remotely by setting up X permissions automatically. If you can log into a machine, it allows you to run a graphical application on it, unlike Telnet, which requires users to have an understanding of the X authentication mechanisms that are manipulated through the xauth and xhost commands. SSH also has inbuilt compression, which allows your graphic applications to run much faster over the network. SCP (Secure Copy) and SFTP (Secure FTP) allow transfer of files over the remote link, either via SSH's own command line utilities or graphical tools like Gnome's GFTP. Like Telnet, SSH is cross-platform. You can find SSH server and clients for Linux, Unix and all flavours of Windows, BeOS, PalmOS, Java and embedded Oses used in routers.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
STDERR
</glossterm>
<glossdef>
<para>
Standard error. A special type of output used for error messages. The file descriptor for STDERR is 2.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
STDIN
</glossterm>
<glossdef>
<para>
Standard input. User input is read from STDIN. The file descriptor for STDIN is 0.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
STDOUT
</glossterm>
<glossdef>
<para>
Standard output. The output of scripts is usually to STDOUT. The file descriptor for STDOUT is 1.
</para>
</glossdef>
</glossentry>
@ -430,6 +408,17 @@ The part of an object table that gives the value of each symbol (usually as a se
</glossdef>
</glossentry>
<glossentry>
<glossterm>
symbolic link or soft link
</glossterm>
<glossdef>
<para>
A special filetype, which is a small pointer file, allowing multiple names for the same file. Unlike hard links, symbolic links can be made for directories and can be made across filesystems. Commands that access the file being pointed to are said to follow the symbolic link. Commands that access the link itself do not follow the symbolic link.
</para>
</glossdef>
</glossentry>
<glossentry>
<glossterm>
system call
@ -463,4 +452,15 @@ Almost all of the services provided through inetd are invoked through tcp-wrappe
</glossdef>
</glossentry>
<glossentry>
<glossterm>
ZSH
</glossterm>
<glossdef>
<para>
Zsh was developed by Paul Falstad as a replacement for both the Bourne and C shell. It incorporates features of all the other shells (such as file name completion and a history mechanism) as well as new capabilities. Zsh is considered similar to the Korn shell. Falstad intended to create in zsh a shell that would do whatever a programmer might reasonably hope it would do. Zsh is popular with advanced users. Along with the Korn shell and the C shell, the Bourne shell remains among the three most widely used and is included with all UNIX systems. The Bourne shell is often considered the best shell for developing scripts.
</para>
</glossdef>
</glossentry>
</glossary>