From: ty@kau1.kodak.com (Trevor Yann)
Subject: TEMP environment var and /tmp
24 Nov 1996 18:35:55 -0800
Sender: daemon@cygnus.com
Approved: cygnus.gnu-win32@cygnus.com
Distribution: cygnus
Message-ID: <1.5.4.32.19961125225828.0034d75c.cygnus.gnu-win32@mailhost>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Sender: ty@mailhost
X-Mailer: Windows Eudora Light Version 1.5.4 (32)
Original-To: Gnu-win32@cygnus.com
Original-Sender: owner-gnu-win32@cygnus.com

There is a known problem that is reported on regular basis - many unix
programs assume the existence of /tmp. 

e.g.

Warren & SLS Knight wrote:
}The problem appears to be with how the BASH shell handles the
}the << operator.  You will see what I mean if you try the following 
}in bash:
}  bash$ cat <<EOF 
}  > This is a test
}  > EOF
}  BASH.EXE: 9146372: No such file or directory

Perhaps a mount for /tmp could be created if there is no /tmp. It is not
unusual for the environment variable TEMP or TMP to be set - this could be
used to determine the location of the mount point.

Just my 2c.

Trevor

-
For help on using this list, send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".