Search results
Results from the WOW.Com Content Network
In computing, redirection is a form of interprocess communication, and is a function common to most command-line interpreters, including the various Unix shells that can redirect standard streams to user-specified locations. The concept of redirection is quite old, dating back to the earliest operating systems (OS).
Make is widely used, especially in Unix and Unix-like operating systems, even though many competing technologies and tools are available, including similar tools that perform actions based on dependencies, some compilers and interactively via an integrated development environment.
Process substitution can also be used to capture output that would normally go to a file, and redirect it to the input of a process. The Bash syntax for writing to a process is >(command). Here is an example using the tee, wc and gzip commands that counts the lines in a file with wc -l and compresses it with gzip in one pass:
Version 1 AT&T UNIX dd: Filesystem Mandatory Convert and copy a file Version 5 AT&T UNIX delta: SCCS Optional (XSI) Make a delta (change) to an SCCS file PWB UNIX df: Filesystem Mandatory Report free disk space Version 1 AT&T UNIX diff: Text processing Mandatory Compare two files; see also cmp Version 5 AT&T UNIX dirname: Filesystem Mandatory
The Thompson shell was the first Unix shell, introduced in the first version of Unix in 1971, and was written by Ken Thompson. [1] It was a simple command interpreter, not designed for scripting, but nonetheless introduced several innovative features to the command-line interface and led to the development of the later Unix shells.
Console redirection Stream redirection Configurability Startup/shutdown scripts Batch scripts Logging Available as statically linked, independent single file executable Thompson shell: UNIX: sh 1971 — UNIX: UNIX — Yes Text-based CLI: No No — Yes — — — — — — Bourne shell 1977 version 7th Ed. UNIX: sh 1977 Yes [1] 7th Ed. UNIX ...
m4 is a general-purpose macro processor included in most Unix-like operating systems, and is a component of the POSIX standard. The language was designed by Brian Kernighan and Dennis Ritchie for the original versions of UNIX. It is an extension of an earlier macro processor, m3, written by Ritchie for an unknown AP-3 minicomputer. [1]
An important aspect of this, setting Unix pipes apart from other pipe implementations, is the concept of buffering: for example a sending program may produce 5000 bytes per second, and a receiving program may only be able to accept 100 bytes per second, but no data is lost. Instead, the output of the sending program is held in the buffer.