From owner-freebsd-current@FreeBSD.ORG Thu Apr 24 22:43:42 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 1DDFC1065673; Thu, 24 Apr 2008 22:43:42 +0000 (UTC) Date: Thu, 24 Apr 2008 22:43:42 +0000 From: Kris Kennaway To: David Naylor Message-ID: <20080424224342.GB47671@hub.freebsd.org> References: <200804242134.57772.naylor.b.david@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200804242134.57772.naylor.b.david@gmail.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: init_chroot broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Apr 2008 22:43:42 -0000 On Thu, Apr 24, 2008 at 09:34:53PM +0200, David Naylor wrote: > Hi, > > init_chroot appears to be broken when used with unionfs (it did work sometime > before RELENG_7 [definitely before the BETA's]). When using -current (with > the vaps patch :-) I get the following message before the system stops: > > [...] > stat(c2d3fcc0,d3ceccfc,8,c0b094e7,c0bbc0a0,...) at stat+0x2f > syscall(d3cecd38) at syscall+0x2a3 > Xint0x80_syscall() at Xint0x80_syscall+0x20 > --- syscall (188, FreeBSD ELF32, stat), eip = 0x826fe23, esp = 0x9bfbfe9bc, > ebp = 0xbfbee98 > > I tracked the stop to line 320 of init.c: > if (chdir(kenv_value) != 0 || chroot(".") != 0) The [...] was the important part. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe