kre a6dacc2280 Use fork() rather than vfork() when forking to run a background ... process with redirects. If we use vfork() and a redirect hangs (eg: opening a fifo) which the parent was intended to unhang, then the parent never gets to continue to unhang the child. eg: mkfifo f; cat <f &; echo foo>f The parent should not be waiting for a background process, even just for its exec() to complete. if there are no redirects there is (should be) nothing left that might be done that will cause any noticeable delay, so vfork() should be safe in all other cases.		2019-12-21 18:54:15 +00:00
..
cat
chio
chmod
cp	PR/54564: Jan Schaumann: cp of a fifo yields an empty file	2019-09-23 18:01:09 +00:00
csh
date
dd	copy libc's swab.c into dd as dd_swab(), and remove the restrict.	2019-10-04 08:57:37 +00:00
df	we don't need root anymore.	2019-09-23 15:24:44 +00:00
domainname
echo
ed
expr
hostname
kill
ksh	Avoid arithmetics on strings.	2019-10-29 16:19:59 +00:00
ln
ls
mkdir
mt
mv
pax	introduce some common variables for use in GCC warning disables:	2019-10-13 07:28:04 +00:00
ps	ps(1): Guard freeing the memory of pinfo with __NO_LEAKS.	2019-09-15 15:27:50 +00:00
pwd
rcmd
rcp
rm
rmdir
sh	Use fork() rather than vfork() when forking to run a background	2019-12-21 18:54:15 +00:00
sleep
stty	Don't fail when the line discipline ioctl fails (since it secondary	2019-09-06 16:28:53 +00:00
sync
test
Makefile
Makefile.inc