From owner-freebsd-questions Sun Jun 24 8:57:40 2001 Delivered-To: freebsd-questions@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 8ED5C37B401; Sun, 24 Jun 2001 08:57:31 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id RAA82599; Sun, 24 Jun 2001 17:57:26 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "Ted Mittelstaedt" Cc: , , , Subject: Re: Kernel Panic References: <004101c0fc8c$44e12280$1401a8c0@tedm.placo.com> From: Dag-Erling Smorgrav Date: 24 Jun 2001 17:57:26 +0200 In-Reply-To: <004101c0fc8c$44e12280$1401a8c0@tedm.placo.com> Message-ID: Lines: 26 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Ted Mittelstaedt" writes: > That would be impossible unless you had "." in your path. If > you did (which is a very BAD thing) then yes your script probably > loaded itself (assuming you named it "pine). This is why the > system defaults to NOT having "." in the path. No: 1) he simply had the script, named "pine", in a directory that was in his search path (e.g. $HOME/bin), and 2) the reason why you shouldn't have any relative path ("." included) in your search path is that you'd get unpredictible and surprising results, and potentially stumble across trojans (imagine an "ls" binary in some random user's home directory that, when you ran it, installed a setuid shell, or sent spam in your name, before giving you a carefully edited directory listing) > However, if the script DID load itself, a recursive script > under an ordinary user ID isn't allowed to crash the > system. Yes it is, unfortunately. FreeBSD doesn't like running out of swap space. Matt Dillon has been trying to correct this in -CURRENT, but it's not completely fixed yet. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message