From owner-freebsd-current  Thu Jun 27 15:43:53 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id PAA03128
          for current-outgoing; Thu, 27 Jun 1996 15:43:53 -0700 (PDT)
Received: from rocky.mt.sri.com (rocky.sri.MT.net [204.182.243.10])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA03120
          for <current@freebsd.org>; Thu, 27 Jun 1996 15:43:48 -0700 (PDT)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id QAA12001; Thu, 27 Jun 1996 16:43:29 -0600 (MDT)
Date: Thu, 27 Jun 1996 16:43:29 -0600 (MDT)
Message-Id: <199606272243.QAA12001@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Cc: Nate Williams <nate@mt.sri.com>, Scott Blachowicz <scott@statsci.com>,
        current@freebsd.org
Subject: Re: Building inside of /usr/src? 
In-Reply-To: <7235.835914709@time.cdrom.com>
References: <199606272210.QAA11833@rocky.mt.sri.com>
	<7235.835914709@time.cdrom.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> 
> There's absolutely *no* reason to ignore the output of getcwd() and it
> does check the directory returned for errors / permission problems.

Except that it might make things that a symlinked 'shorter' and/or
easier to understand.  That's my suspicion.

> The only thing I can figure out was that someone found AMD's path
> mangling to be non-intuitive (though functional) or something and
> figured they'd substitite in the value of $PWD.

I think the above is similar to my symlink explanation above.  Having a
*really* ugly /usr/obj/foo/bar/ug/ick/wiglle/usr.sbin/traceroute can be
a bit obnoxious for the obj stuff.


Nate