cp -R didn't work correctly for FIFO's (programmer head space error)
From: "Charles M. Hannum" <mycroft@gnu.ai.mit.edu>

too many arguments to err() function
From: Charles Hannum <mycroft@NetBSD.ORG>

add the documented in the manual but not implemented variable
expansions.
From: Christos Zoulas <christos@deshaw.com>

add the -o option to the usage statement
From: "Charles M. Hannum" <mycroft@gnu.ai.mit.edu>

prettiness police
From: Charles Hannum <mycroft@NetBSD.ORG>

getwd(3) is deprecated, and pwd(1) uses getcwd(3) internally anyway.
From: Charles Hannum <mycroft@NetBSD.ORG>

POSIX.2 compliance
From: Charles Hannum <mycroft@NetBSD.ORG>

prettiness police
From: Charles Hannum <mycroft@NetBSD.ORG>

prettiness police
From: Charles Hannum <mycroft@NetBSD.ORG>

POSIX.2 states that user-defined formats are always followed by a
<newline>
From: Charles Hannum <mycroft@NetBSD.ORG>

The sin_zero field of one of the sockaddr's wasn't being zeroed.
From: Charles Hannum <mycroft@NetBSD.ORG>

POSIX.2 states that user-defined formats are always followed by a
<newline>
From: Charles Hannum <mycroft@NetBSD.ORG>

don't overwrite a directory with some other type of file, i.e.
don't attempt to unlink a directory
From: Charles Hannum <mycroft@NetBSD.ORG>

prettiness police
From: Charles Hannum <mycroft@NetBSD.ORG>

Correct test for return value of getopt(3).
Don't prompt twice to remove a directory.
Don't print two error messages if a directory could not be removed.
Get rid of bogus extra variable in rm_file().

Correct test for return value of getopt(3).
Don't prompt twice to remove a directory.
Don't print two error messages if a directory could not be removed.
Get rid of bogus extra variable in rm_file().
Add `-P' and -W options to usage string; random lint and prettiness police
From: Charles Hannum <mycroft@NetBSD.ORG>

show more ...

This patch fixes some broken behavior with empty commands in sh,
e.g. ";<CR>", ">foo;<CR>", "(>foo)" are now correct
From: Charles Hannum <mycroft@sun-lamp.cs.berkeley.edu>

don't add an extra space between the process's args and the
parenthesized p_comm
From: "Chris G. Demetriou" <cgd@sun-lamp.cs.berkeley.edu>

J.T. Conklin's changes for signals mean that we don't need all
of the random signal crap any longer

J.T. Conklin's changes for signals mean that we don't need all
of the random signal crap any longer

getpgrp no longer takes an argument
the copyright notice was messed up quite a bit

POSIX.2 says that a successful variable assignment should set the status
variable ($?) to 0.
From: "J.T. Conklin" <jtc@sun-lamp.cs.berkeley.edu>

POSIX.2 (and common sense) dictates that the file specified by $ENV
should not be sourced when running a setuid or setgid shell script.
From: "J.T. Conklin" <jtc@sun-lamp.cs.berkeley.edu>
NOTE: Dave

POSIX.2 (and common sense) dictates that the file specified by $ENV
should not be sourced when running a setuid or setgid shell script.
From: "J.T. Conklin" <jtc@sun-lamp.cs.berkeley.edu>
NOTE: Dave Korn noted at a recent POSIX meeting that ENV should be ignored
for all scripts, so this is likely to go further in the near future.

show more ...

Don't dump core when evaluating X % 0.
Simplify lexer by using %prec feature in yacc grammar.
Implement most of the operators required by POSIX.2.
From: "J.T. Conklin" <jtc@sun-lamp.cs.berkeley.edu>

This patch changes the shell to use the sys_siglist[] array in libc
instead of the list generated by the mksignames program.
From: "J.T. Conklin" <jtc@sun-lamp.cs.berkeley.edu>

When a "&" is encountered in a list, all the prior commands
are grouped together and backgrounded, instead of only the previous
and-or construct being backgrounded. Typing "sleep 1; sleep 10 &" exe

When a "&" is encountered in a list, all the prior commands
are grouped together and backgrounded, instead of only the previous
and-or construct being backgrounded. Typing "sleep 1; sleep 10 &" executes
the equivalent (roughly) of "{ sleep 1; sleep 10; } &".
From: "J.T. Conklin" <jtc@sun-lamp.cs.berkeley.edu>

show more ...