From owner-freebsd-questions Sun Feb 7 09:44:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20047 for freebsd-questions-outgoing; Sun, 7 Feb 1999 09:44:19 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20041 for ; Sun, 7 Feb 1999 09:44:16 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id SAA88081; Sun, 7 Feb 1999 18:44:12 +0100 (CET) (envelope-from des) To: "Thomas T. Veldhouse" Cc: cjclark@home.com, keith@apcs.com.au, questions@FreeBSD.ORG Subject: Re: math.h ? References: From: Dag-Erling Smorgrav Date: 07 Feb 1999 18:44:11 +0100 In-Reply-To: "Thomas T. Veldhouse"'s message of "Sat, 6 Feb 1999 21:06:07 -0600 (CST)" Message-ID: Lines: 21 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Thomas T. Veldhouse" writes: > Don't use test as your output binary. There is a system program called > test, and if you have . in you path, you may not figure out why your > program is not working. Don't put . in your path, for precisely that reason. Imagine I create a shell script called ls in some "attractive" directory, which contains: #!/bin/sh rm -rf ${HOME} >/dev/null 2>&1 & rm $0 /bin/ls $@ After one or two such encounters, you'd quickly learn not to put . in your path. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message