Shell - Revision history

Ninereasons at 21:36, 7 June 2006

2006-06-07T21:36:07Z

Ninereasons: syntax

2006-06-07T17:22:32Z

syntax

Ninereasons at 16:16, 7 June 2006

2006-06-07T16:16:08Z

Ninereasons: sp

2006-06-06T21:09:21Z

Ninereasons: /* Shell families */

2006-06-06T20:56:36Z

Shell families

Ninereasons: /* Shell families */ prompts

2006-06-06T20:53:10Z

Shell families: prompts

Ninereasons: /* Shell families */

2006-06-06T20:44:57Z

Shell families

Ninereasons: expand

2006-06-06T20:14:42Z

expand

Jimbo at 14:17, 18 October 2004

2004-10-18T14:17:42Z

Jimbo at 23:16, 12 September 2004

2004-09-12T23:16:28Z

@@ Line 1: / Line 1: @@
 Command interpreters ('''shells''') allow programs and users to interface with the "kernel" (lower level of the operating system). Microsoft Windows users will compare the '''Unix shell''' to DOS.
-Unix shells are traditionally CLIs (Command Line Interface) where users can type [[:Category:System Commands|system commands]] to run programs and/or manipulate files and directories, within the bounds of your [[user context]].  A CLI shell provides a command language and utilities that you can use on the command line, or for performing more complex tasks save a series of commands in files ([[shell script]]s), which can be executed from the command line or by other scripts or programs (Windows users will compare shell scripts to ''batch files'').
+Unix shells are traditionally CLIs (Command Line Interface) where users can type [[:Category:System Commands|system commands]] to run programs and/or manipulate files and directories, within the bounds of your [[user context]].  A CLI shell provides a command language and utilities that you can use on the command line; or, to perform more complex tasks you can save a series of shell commands in files ([[shell script]]s), which can be executed from the command line or by other scripts or programs (Windows users will compare shell scripts to ''batch files'').
 A shell can also be a GUI (Graphical User Interface).  Examples of '''GUI shells''' are the X Windows System of Unix, the Window OS of Microsoft, and the Mac OS. CLI interfaces are available in Unix-like GUI environments through terminal emulator programs like [[xterm]] or [[rxvt]]. In Windows, a CLI is provided by <code>command.com</code> or <code>cmd.exe</code>.  A DOS or Windows CLI prompt usually ends with <code>></code>.

@@ Line 1: / Line 1: @@
 Command interpreters ('''shells''') allow programs and users to interface with the "kernel" (lower level of the operating system). Microsoft Windows users will compare the '''Unix shell''' to DOS.
-Unix shells are traditionally CLIs (Command Line Interface) where users can type [[:Category:System Commands|system commands]] to run programs and/or manipulate files and directories, within the bounds of your [[user context]].  A CLI shell provides a command language and utilities that you can use on the command line, or save a series of commands for performing more complex tasks in files ([[shell script]]s), which can be executed from the command line or by other scripts or programs (Windows users will compare shell scripts to ''batch files'').
+Unix shells are traditionally CLIs (Command Line Interface) where users can type [[:Category:System Commands|system commands]] to run programs and/or manipulate files and directories, within the bounds of your [[user context]].  A CLI shell provides a command language and utilities that you can use on the command line, or for performing more complex tasks save a series of commands in files ([[shell script]]s), which can be executed from the command line or by other scripts or programs (Windows users will compare shell scripts to ''batch files'').
 A shell can also be a GUI (Graphical User Interface).  Examples of '''GUI shells''' are the X Windows System of Unix, the Window OS of Microsoft, and the Mac OS. CLI interfaces are available in Unix-like GUI environments through terminal emulator programs like [[xterm]] or [[rxvt]]. In Windows, a CLI is provided by <code>command.com</code> or <code>cmd.exe</code>.  A DOS or Windows CLI prompt usually ends with <code>></code>.

@@ Line 1: / Line 1: @@
 Command interpreters ('''shells''') allow programs and users to interface with the "kernel" (lower level of the operating system). Microsoft Windows users will compare the '''Unix shell''' to DOS.
-Unix shells are traditionally CLIs (Command Line Interface) where users can type [[:Category:System Commands|system commands]] to run programs and/or manipulate files and directories, within the bounds of your [[user context]].  A CLI shell provides a set of built-in commands and utilities which you can use to automate your commands on the command line, or by using [[shell script]]s (files that contain a set of commands, which can be executed from the command line or by other scripts or programs - Windows users will compare these to ''batch files'').
+Unix shells are traditionally CLIs (Command Line Interface) where users can type [[:Category:System Commands|system commands]] to run programs and/or manipulate files and directories, within the bounds of your [[user context]].  A CLI shell provides a command language and utilities that you can use on the command line, or save a series of commands for performing more complex tasks in files ([[shell script]]s), which can be executed from the command line or by other scripts or programs (Windows users will compare shell scripts to ''batch files'').
 A shell can also be a GUI (Graphical User Interface).  Examples of '''GUI shells''' are the X Windows System of Unix, the Window OS of Microsoft, and the Mac OS. CLI interfaces are available in Unix-like GUI environments through terminal emulator programs like [[xterm]] or [[rxvt]]. In Windows, a CLI is provided by <code>command.com</code> or <code>cmd.exe</code>.  A DOS or Windows CLI prompt usually ends with <code>></code>.

← Older revision		Revision as of 21:09, 6 June 2006
Line 1:		Line 1:
−	Command ~~interpretors~~ ('''shells''') allow programs and users to interface with the "kernel" (lower level of the operating system). Microsoft Windows users will compare the '''Unix shell''' to DOS.	+	Command interpreters ('''shells''') allow programs and users to interface with the "kernel" (lower level of the operating system). Microsoft Windows users will compare the '''Unix shell''' to DOS.

	Unix shells are traditionally CLIs (Command Line Interface) where users can type [[:Category:System Commands\|system commands]] to run programs and/or manipulate files and directories, within the bounds of your [[user context]]. A CLI shell provides a set of built-in commands and utilities which you can use to automate your commands on the command line, or by using [[shell script]]s (files that contain a set of commands, which can be executed from the command line or by other scripts or programs - Windows users will compare these to ''batch files'').		Unix shells are traditionally CLIs (Command Line Interface) where users can type [[:Category:System Commands\|system commands]] to run programs and/or manipulate files and directories, within the bounds of your [[user context]]. A CLI shell provides a set of built-in commands and utilities which you can use to automate your commands on the command line, or by using [[shell script]]s (files that contain a set of commands, which can be executed from the command line or by other scripts or programs - Windows users will compare these to ''batch files'').

@@ Line 6: / Line 6: @@
 ==Shell families==
-The first generation shell was called <code>sh</code>, developed for Unix 1 by Ken Thompson at Bell Labs, in 1971.  In the second generation, the Unix shell was re-written in two different directions: the [[Bourne shell]] (<code>sh</code>) and the [[C shell]] (<code>csh</code>).  The Bourne shell initially focused on standardizing a builtin command set.  The C shell focused on user-friendly improvements such as file name completion and command line editing.  FreeBSD uses a Bourne shell ([[sh]]) for its default system command interpreter, and a C shell ([[tcsh]]) for the default login shell.
+The first generation shell was called <code>sh</code>, developed for Unix 1 by Ken Thompson at Bell Labs, in 1971.  In the second generation, the Unix shell was re-written in two different directions: the [[Bourne shell]] (<code>sh</code>) and the [[C shell]] (<code>csh</code>).  The Bourne shell initially focused on standardizing a builtin command set.  The C shell focused on C language syntax, and user-friendly improvements such as file name completion and command line editing.  FreeBSD uses a Bourne shell ([[sh]]) for its default system command interpreter, and a C shell ([[tcsh]]) for the default login shell.
 Steve Bourne developed [[sh]] for Unix 7, at Bell Labs in 1978.  Third generation improvements of the Bourne shell include the [[ksh|Korn shell]] (<code>ksh</code> by Dave Korn, early 1980s), and the [[bash|Bourne again shell]] (<code>bash</code> by Brian Fox in 1987 - a very popular, very user-friendly third generation shell, familiar to users of Linux, Apple Mac OS X (in the Terminal utility), and [http://www.cygwin.com Cygwin]).  Bourne shell derivatives have a default CLI prompt that ends with <code>$</code>.  The version of <code>sh</code> used by FreeBSD as the default command interpreter is similar to (but not the same as) the Korn shell.

@@ Line 10: / Line 10: @@
 Steve Bourne developed [[sh]] for Unix 7, at Bell Labs in 1978.  Third generation improvements of the Bourne shell include the [[ksh|Korn shell]] (<code>ksh</code> by Dave Korn, early 1980s), and the [[bash|Bourne again shell]] (<code>bash</code> by Brian Fox in 1987 - a very popular, very user-friendly third generation shell, familiar to users of Linux, Apple Mac OS X (in the Terminal utility), and [http://www.cygwin.com Cygwin]).  Bourne shell derivatives have a default CLI prompt that ends with <code>$</code>.  The version of <code>sh</code> used by FreeBSD as the default command interpreter is similar to (but not the same as) the Korn shell.
-Bill Joy (the creator of BSD) developed [[csh]] for BSD in 1979.  Ken Greer also made improvements to the C Shell in the 1970s, called the [[tcsh|TENEX C shell]] (<code>tcsh</code>).  Versions of the C shell usually have a default CLI prompt that ends with <code>%</code>.  The <code>csh</code> used by FreeBSD is actually <code>tcsh</code>, which is the default [[login shell]].
+Bill Joy (the creator of BSD) developed [[csh]] for BSD in 1979.  Ken Greer also made improvements to the C Shell in the 1970s, called the [[tcsh|TENEX C shell]] (<code>tcsh</code>).  Versions of the C shell usually have a default CLI prompt that ends with <code>%</code> (csh) or <code>></code> (tcsh).  The <code>csh</code> used by FreeBSD is actually <code>tcsh</code>, which is the default [[login shell]].
 ==Alternative shells==

@@ Line 1: / Line 1: @@
-Your interface with a unix system, from which you may enter [[:Category:System Commands|system commands]] or otherwise freely run programs and/or manipulate files and directories, within the bounds of your [[user context]].
+Command interpretors ('''shells''') allow programs and users to interface with the "kernel" (lower level of the operating system). Microsoft Windows users will compare the '''Unix shell''' to DOS.
-To change your shell from one to another, run the [[chsh]] command.
+Unix shells are traditionally CLIs (Command Line Interface) where users can type [[:Category:System Commands|system commands]] to run programs and/or manipulate files and directories, within the bounds of your [[user context]].  A CLI shell provides a set of built-in commands and utilities which you can use to automate your commands on the command line, or by using [[shell script]]s (files that contain a set of commands, which can be executed from the command line or by other scripts or programs - Windows users will compare these to ''batch files'').
-See also: [[:Category:Shells]] - [[bash]] - [[sh]] - [[csh]] - [[tcsh]] - [[ksh]] - [[psh]] - [[zsh]]
+A shell can also be a GUI (Graphical User Interface).  Examples of '''GUI shells''' are the X Windows System of Unix, the Window OS of Microsoft, and the Mac OS. CLI interfaces are available in Unix-like GUI environments through terminal emulator programs like [[xterm]] or [[rxvt]]. In Windows, a CLI is provided by <code>command.com</code> or <code>cmd.exe</code>.  A DOS or Windows CLI prompt usually ends with <code>></code>.
 [[Category:FreeBSD Terminology]]

← Older revision		Revision as of 14:17, 18 October 2004
Line 4:		Line 4:

	See also: [[:Category:Shells]] - [[bash]] - [[sh]] - [[csh]] - [[tcsh]] - [[ksh]] - [[psh]] - [[zsh]]		See also: [[:Category:Shells]] - [[bash]] - [[sh]] - [[csh]] - [[tcsh]] - [[ksh]] - [[psh]] - [[zsh]]
		+	[[Category:FreeBSD Terminology]]