Differences between version 8 and revision by previous author of Shell.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 8 | Last edited on Tuesday, December 28, 2004 1:37:49 am | by AristotlePagaltzis | Revert |
| Older page: | version 4 | Last edited on Thursday, November 20, 2003 12:49:51 pm | by JohnMcPherson | Revert |
@@ -1,16 +1,19 @@
-Known as the CommandLine to people nowadays, it is the main program used for interacting with a computer (besides graphical [
DesktopEnvironment]
s). It also implements a very high level ProgrammingLanguage that is available for both interactive and scripted use.
+Known as the CommandLine to people nowadays, it is the main program used for interacting with a computer (besides graphical DesktopEnvironment~
s). It also implements a very high level ProgrammingLanguage that is available for both interactive and scripted use.
-The original Unix
shell is called the "
Bourne shell"
, after its designer Steven Bourne. The executable is just called sh(1), and it's still the foundation of all modern [Shell]s on Unixoid OperatingSystems
.
+The original [UNIX]
shell is called the “
Bourne shell”
, after its designer Steven Bourne. The executable is just called sh(1), and it's still the foundation of all modern [Shell]s on [Unix]oid OperatingSystem~s
.
-The first derivate was Bill Joy's C shell, csh(1), meant to make shell scripting easier for [C] programmers. It was developed at [UCB] as the shell of choice for [BSD] systems. This shell suffered many problems in interactive uses and non, which eventually even prompted a CshProgrammingConsideredHarmful paper. It has not been released under a FreeSoftware license.
+The first derivate was Bill Joy's [
C]
shell, csh(1), meant to make shell scripting easier for [C] programmers. It was developed at [UCB] as the shell of choice for [BSD] systems. This shell suffered many problems in interactive uses and non, which eventually even prompted a CshProgrammingConsideredHarmful paper. It has not been released under a FreeSoftware license.
-At AT&T, David Korn derived the Korn shell, __ksh__, from the Bourne shell. This shell is completely backwards compatible with its predecessor and much more powerful. It is quite common on commercial [Unix] flavours such as [Solaris].
+At [
AT&T]
, David Korn derived the Korn shell, __ksh__, from the Bourne shell. This shell is completely backwards compatible with its predecessor and much more powerful. It is quite common on commercial [Unix] flavours such as [Solaris].
-Since no __ksh__ variant was ever FreeSoftware (although there was eventually a [Free] clone called pdksh (__p__ublic __d__omain) started in the mid 1990s), the [GNU] project wrote their own Bourne compatible shell, and in typical [GNU]ish punstery called it the bash(1), "
Bourne again shell"
. See BashNotes for hints and examples for using bash.
+Since no __ksh__ variant was ever FreeSoftware (although there was eventually a [Free] clone called pdksh (__p__ublic __d__omain __ksh__
) started in the mid 1990s), the [GNU] project wrote their own Bourne compatible shell, and in typical [GNU]ish punstery called it the bash(1), “
Bourne again shell”
. See BashNotes for hints and examples for using bash(1)
.
Meanwhile many of the csh(1)'s shortcomings for interactive use were fixed in the tcsh(1). It is the default shell for modern [BSD] variants.
-Other sh-compatible shells include ash(1), a very minimalistic variant mostly meant for embedded systems and the like were memory is scarce and interactive use is uncommon,
sash(1), which stands for
__S__tand-__A__lone shell which is staticly linked for "
emergency repair work"
when sh(1) won't work, and
zsh(1), which features wildly expanded (but backwards compatible) syntax and many convenience features for interactive use.
+Other sh-compatible shells include:
+*
ash(1), a very minimalistic variant mostly meant for embedded systems and the like were memory is scarce and interactive use is uncommon.
+*
sash(1), the
__S__tand-__A__lone shell which is staticly linked for “
emergency repair work”
when sh(1) won't work.
+*
zsh(1), which features wildly expanded (but backwards compatible) syntax and many convenience features for interactive use.
----
-CategoryProgrammingLanguages, CategoryVeryHighLevelProgrammingLanguages
+Part of
CategoryProgrammingLanguages, CategoryVeryHighLevelProgrammingLanguages
