From owner-freebsd-stable Fri Feb 2 13:31: 4 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (Postfix) with ESMTP id DD07637B401; Fri, 2 Feb 2001 13:30:39 -0800 (PST) Received: from taygeta.dbai.tuwien.ac.at (taygeta [128.130.111.77]) by vexpert.dbai.tuwien.ac.at (8.11.1/8.11.1) with ESMTP id f12LUce14239; Fri, 2 Feb 2001 22:30:38 +0100 (MET) Received: from localhost (pfeifer@localhost) by taygeta.dbai.tuwien.ac.at (8.11.1/8.11.1) with ESMTP id f12LUc015620; Fri, 2 Feb 2001 22:30:39 +0100 (CET) (envelope-from pfeifer@dbai.tuwien.ac.at) X-Authentication-Warning: taygeta.dbai.tuwien.ac.at: pfeifer owned process doing -bs Date: Fri, 2 Feb 2001 22:30:38 +0100 (CET) From: Gerald Pfeifer To: , Subject: AMD, pwd and WRKDIR Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Some time before 4.2-RELEASE AMD has been updated to use /.amd_mnt instead of /amd as mount-point. Now, my ports collection resides in an automounted directory, and when I set WRKDIR for the ports collection to /tmp, the ports build and install fine, but /tmp remains ``empty'', as the port machinery takes the full path as used by AMD and creates /tmp/.amd_mnt/fileserver/disk/dir/... This is bad[TM], but I don't know how this should be fixed. To -STABLE: Ideally, `pwd` would return a *logical* path, that is, /amdtable/dir/... instead of /.amd_mnt/nfsserver/disk/dir, but I don't know whether this can be done. To -PORTS: At the very least, and short-term fix, I recommend `pwd` | sed -e s#^.amd_mnt/## or `pwd` | sed -e s#^.amd_mnt/fileserver## instead of of a plain `pwd` to determine the pathname under $WRKDIR. Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message