From owner-freebsd-bugs@FreeBSD.ORG Sun Mar 21 08:50:08 2010 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 42E15106566B for ; Sun, 21 Mar 2010 08:50:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 313148FC08 for ; Sun, 21 Mar 2010 08:50:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id o2L8o7lM018237 for ; Sun, 21 Mar 2010 08:50:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id o2L8o7nW018236; Sun, 21 Mar 2010 08:50:07 GMT (envelope-from gnats) Date: Sun, 21 Mar 2010 08:50:07 GMT Message-Id: <201003210850.o2L8o7nW018236@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Garrett Cooper Cc: Subject: Re: bin/109334: pkg_add(1) using chroot exits with error if wrong directory X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Garrett Cooper List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Mar 2010 08:50:08 -0000 The following reply was made to PR bin/109334; it has been noted by GNATS. From: Garrett Cooper To: bug-followup@freebsd.org, nick@anywi.com Cc: Subject: Re: bin/109334: pkg_add(1) using chroot exits with error if wrong directory Date: Sun, 21 Mar 2010 01:42:52 -0700 On Sat, Mar 20, 2010 at 6:36 PM, Garrett Cooper wrote: > Hi Nick, > =A0 =A0I realize that this PR has been sitting around for a long time, > but is it possible that you can dig up more details, like filesystem > layout and/or environment variables used when trying to run pkg_add? I > know this seems like a lot, and yes I might be able to reproduce the > issue on my own, but the fact is that there are a large number of > potential failures that could occur based on what you had set in your > environment and what did not exist on your chrooted filesystem. Nevermind. This is easy to produce and I know why it's happening. From chroot(2): It should be noted that chroot() has no effect on the process's curren= t directory. Let me think about the best way to resolve this issue and I'll get back to you by Monday or Tuesday. Thanks, -Garrett