diff options
| author | Gerrit Pape <pape@smarden.org> | 2009-05-23 10:05:15 +0800 |
|---|---|---|
| committer | Herbert Xu <herbert@gondor.apana.org.au> | 2009-05-23 10:05:15 +0800 |
| commit | 956b4bd209a9d17613e419e2b50e0f533600497b (patch) | |
| tree | ac13f4cf2254e43082d2387468eab8151c19691c /src | |
| parent | [PARSER] Use CHKNL to parse case statements (diff) | |
| download | dash-956b4bd209a9d17613e419e2b50e0f533600497b.tar.gz dash-956b4bd209a9d17613e419e2b50e0f533600497b.zip | |
[MAN] Update manual page to differentiate dash from ash
Rename sh to dash in the header and synopsis; remove reference to the 4.4 BSD release in the description, and replace the history information with a reference to NetBSD's ash. Suggested by jaalto through http://bugs.debian.org/499838 Signed-off-by: Gerrit Pape <pape@smarden.org> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to '')
| -rw-r--r-- | src/dash.1 | 19 |
1 files changed, 10 insertions, 9 deletions
diff --git a/src/dash.1 b/src/dash.1 index 5a8e2fe..c7771d0 100644 --- a/src/dash.1 +++ b/src/dash.1 @@ -34,9 +34,9 @@ .\" .Dd January 19, 2003 .Os -.Dt SH 1 +.Dt DASH 1 .Sh NAME -.Nm sh +.Nm dash .Nd command interpreter (shell) .Sh SYNOPSIS .Nm @@ -93,9 +93,6 @@ but it is not a Korn shell clone (see Only features designated by .Tn POSIX , plus a few Berkeley extensions, are being incorporated into this shell. -We expect -.Tn POSIX -conformance by the time 4.4 BSD is released. This man page is not intended to be a tutorial or a complete specification of the shell. .Ss Overview @@ -2333,11 +2330,15 @@ The process ID of the parent process of the shell. .Xr environ 7 , .Xr sysctl 8 .Sh HISTORY -A .Nm -command appeared in -.At v1 . -It was, however, unmaintainable so we wrote this one. +is a POSIX-compliant implementation of /bin/sh that aims to be as small as +possible. +.Nm +is a direct descendant of the NetBSD version of ash (the Almquist SHell), +ported to Linux in early 1997. +It was renamed to +.Nm +in 2002. .Sh BUGS Setuid shell scripts should be avoided at all costs, as they are a significant security risk. |