Re: init_chroot broken

On Fri, Apr 25, 2008 at 11:23:07PM +0200, David Naylor wrote:
> On Friday 25 April 2008 00:43:42 you wrote:
> > 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.
> It is a lot to type out, is there perhaps an easier way to get the output.  I 
> do not have access to a serial cable but I do have VMWare?  Also, do you 
> really need all the parameters or just some (and if so which ones).  

Configure dumps and/or textdumps, or if you cannot do that then a screenshot.

Kris

--
In God we Trust -- all others must submit an X.509 certificate.
    -- Charles Forsythe <forsythe_at_alum.mit.edu>