Translation(s) : English - Español - Français - Italiano - Português (Brasil)

From its beginnings, Unix was based on basic and simple fundamental building blocks that are at the same time powerful and flexible. The basic components of a Unix system are files, users, processes, and data. Programs are ideally small, simple tools that do one task but do it well. Many programs can act as a pipeline. They read data in one end, and write it out another (stdin and stdout, but there's also stderr which generally receives error output).

By attaching several programs together, it's possible to build complex tools simply and quickly, without worrying about complexity. Programs tend to be highly modular in Unix.

Though these principles haven't been slavishly followed in the 30 years+ that Unix has been around, the fundamental principles still remain at the core of most Unixes, as well as various clones/derivates such as the BSDs and GNU/Linux systems. This modular design philosophy can clearly be seen within many of the programs and subsystems therein.

So again: "Have a small program do only one small task but do that well and efficiently - the "user" (which might actually be the sys-admin) can then combine many of those to get the job done." (I have programmed a C program to count occurrences of words in a text only to find out that "cat file || tr \ \\n || sort || uniq -c" does the same job - just faster ;-) )

System Administration in Unix is generally carried out by either manipulating hardware (swap the tapes, etc.), changing filesystem settings using commands that are front-ends for system calls (chmod, chown, mount, etc.), installing vendor-supplied software and patches, compiling and installing the most recent versions of free software, or -- most importantly -- writing and editing (with a text editor) scripts and configuration files. OS functions that are carried out by invoking shell scripts give the administrator a great deal of control over the behavior of the system. Unix programmers have their programs read configuration files -- in fact, the configuration may implement a scripting language -- as the most straightforward way to give the admin control over the program's features. Occasionally vendors (or a senior admin) will provide an administration menu system or GUI in an effort to simplify the various tasks, but the Unix Way is for there to be little text files being edited and little programs being run. Since no simplification can cover all the intricacies (it's impossible to write real programs by pushbutton) administrators have still needed to know what's going on in the background.

The concept of "shallow complexity" applies here.

System V vs. BSD

Most Unix-like systems can be placed on a continuum between System V and BSD. BSD-like systems tend to follow closely to the Unix Way as described above. They are especially geared toward those who want to have total control in a small package. System V is more geared to the "Enterprise", and is designed with interfaces and subsystems that make it more friendly to . . . environments where a tie is required. In particular, System V is more likely to have ways for third-party software to integrate with the system with a minimum of administration effort. A prime example is the structure of the system initialization scripts, which are run when the system boots. While BSD systems tend to have a small number of scripts that are hand-maintained by the admin, System V has a set of directories containing smaller scripts, each of which do one thing. While the BSD way is more straightforward for the lone admin, the System V way, without contradicting the Unix Way, allows software packages to install themselves with less likelihood of error.

CategorySystemAdministration | CategoryCommandLineInterface | CategoryRedundant: merge some parts with other shell/CLI pages