Digging the old abbreviations in Linux

"2005-06-22 15:23" "Nigel McFarlane" "TechTarget"
<< Read the original >>

UNIX has been a 35-year history. Many people think it began in the Middle Ages, the Middle Ages is relative to the generation and development of computer technology. Over the past time, UNIX and its sub-branches of Linux have collected many histories and some completely ancient languages. In this tip, we'll cover a few ancient languages and their purpose and role, as well as their true origins.

RC

In Linux, the most commonly used abbreviation may be "RC", which is the abbreviation for "Runcomm"-the shorthand for the term "Run command". Today, "RC" is the suffix of any script class file that is usually called during the startup phase of the program, usually when the Linux system starts. As/etc/rs is the main script for Linux startup, and. BASHRC is the script that runs when the Linux bash Shell starts: the prefix ". BASHRC". is a naming standard that is designed to hide special files specified by users in user files; " ls command does not list such files by default, and RM does not delete them by default. Many programs start with the "RC" suffix of the initial file or configuration file, which is no mystery to the Unix file system view.

ETC

"etc" in "etc/bin" really stands for "etcetera" (add-on). In the early Unix system, the most important directory is the "bin" directory ("Bin" is the "binaries" binary file-the compiled program abbreviation), "etc" contains trivial programs, such as startup, shutdown and management. The list of things to run a Linux must be: A binary program, etcetera,etcetera―― in other words, is an important project at the bottom, usually adding some minor and trivial things. Today, etc contains a wide range of system configuration files that contain almost every aspect of the system configuration and are equally important.

Bin

Today, many large subsystems running on Linux, such as Gnome or Oracle, are compiled with programs that use their own "bin" directories (or/usr/bin, or/usr/local/bin) as the standard place of storage. Similarly, it is now possible to see script files in these directories because the "bin" directory is usually added to the user's path path so that they can use the program normally. So running the script usually works well in the bin.

Tty

In Linux, TTY may be the most confusing term to have a connection to a terminal. TTY is an old acronym for Teletype. Teletypes, or teletypewriters, originally refers to a telex typewriter, is a serial line with a printer keyboard by reading and sending messages, and the old Telegraph difference is not very large. Then, when the computer can only run in batch mode (when the punch card reader is the only way to get the program to run), the telex typewriter becomes the only "real-time" input/output device that can be used. Eventually, the telex is replaced by a keyboard and display terminal, but in the terminal or TTY plug-in, the operating system still needs a program to monitor the serial port. A Getty "Get TTY" process is a program that monitors the physical tty/terminal interface. For a virtual network frustrated server (VNC), a disguised TTY (Pseudo-tty, the Home cat's TTY, also called "PTY") is an equivalent terminal. When you run a xterm (terminal emulator) or GNOME Terminal program, Pty is like a TTY running on a virtual user or a pseudo-terminal like xterm. "Pseudo" means "duplicating in a fake way" (copied by forgery method), which is more realistic than "virtual" or "emulated" to illustrate the problem. In the present calculation, it is in the stage of being abandoned.

Dev

The command left from TTY has "Stty", which is the abbreviation for "Set TTY" (setting TTY), which can generate a profile/etc/initab ("Initialization table", the initial tables) to configure which serial port to use for Gettys. In modern times, the only terminal attached directly to a Linux window is usually the console, which is named "console" because it is a special tty. Of course, once you start X11, the "console" TTY disappears and you can't use the serial protocol. All TTY are stored in the "/dev" directory, which is an abbreviation for "[Physical] devices" ([physical] device). Previously, you had to manually modify and configure each device file when you had access to a new terminal in a string at the back of your computer. Now, Linux (and Unix) has created the files for each of the devices it can guide in this directory during the installation process. This means that you rarely need to create it yourself.

As hardware moves out of the computer, the names become more blurred. Fortunately, today's high-grade software blocks on Linux use easy-to-understand names for history and hardware. For example, well, Pango (http://www.pango.org/) is one of them.

If you are interested in these things, then I suggest you read the grand, but some of US English history-centric, written by Eric S. Raymond Jargon File. It does not explain all the terminology used in Unix, but it gives a general picture of how these are formed.

Digging the old abbreviations in Linux