Date: Thu, 24 Apr 2008 22:43:42 +0000 From: Kris Kennaway <kris@FreeBSD.org> To: David Naylor <naylor.b.david@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: init_chroot broken Message-ID: <20080424224342.GB47671@hub.freebsd.org> In-Reply-To: <200804242134.57772.naylor.b.david@gmail.com> References: <200804242134.57772.naylor.b.david@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <forsythe@alum.mit.edu>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080424224342.GB47671>