From owner-freebsd-current Mon Jan 27 18:03:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA07445 for current-outgoing; Mon, 27 Jan 1997 18:03:21 -0800 (PST) Received: from po1.glue.umd.edu (root@po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA07436 for ; Mon, 27 Jan 1997 18:03:18 -0800 (PST) Received: from uplink.eng.umd.edu (uplink.eng.umd.edu [129.2.98.181]) by po1.glue.umd.edu (8.8.5/8.7.3) with ESMTP id VAA05249; Mon, 27 Jan 1997 21:03:09 -0500 (EST) Received: from localhost (chuckr@localhost) by uplink.eng.umd.edu (8.8.5/8.7.3) with SMTP id VAA02496; Mon, 27 Jan 1997 21:03:08 -0500 (EST) X-Authentication-Warning: uplink.eng.umd.edu: chuckr owned process doing -bs Date: Mon, 27 Jan 1997 21:03:08 -0500 (EST) From: Chuck Robey X-Sender: chuckr@uplink.eng.umd.edu To: Randy DuCharme cc: dg@root.com, Peter Korsten , current@freebsd.org Subject: Re: Can't get `.' off of root's path In-Reply-To: <32ED5069.167EB0E7@nconnect.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 27 Jan 1997, Randy DuCharme wrote: > David Greenman wrote: > > > > >> What's even worse... if I do an... > > >> > > >> echo $PATH > > >> > > >> dot isn't there. > > > > > >No idea about that. Not even at the very end? > > > > Make sure you don't have a ":" (a null path component) at the end, either, > > since this is equivalent to the current directory ("."). Also make sure that > > there are no relative path specifications (no leading "/" or contains a ".."). > > I've taken the path(s) completely out of .login, .cshrc, /etc/csh.login, > /etc/csh.cshrc, and, .profile & /etc/profile (just in case I've missed > some change that made csh read .profile) and it's still there. Only on > my current machines, not on my 2.1.5, 2.1.6, or 2.2SNAP machines. > > Format and start over ?? :) I have a new machine that I booted from a 2.2 snap, then moved to current. Root's path (echo $PATH) doesn't include ".", but I get that warning anyhow. Functionally speaking, root's path really doesn't include ".", it can't see executable in the current dir (except via ./), I doublechecked just in case csh was playing games with me. The warning seems to be bogus. I doublechecked everything, I haven't made a mistake on this. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+-----------------------------------------------