Date: Mon, 30 Dec 2002 22:19:13 -0700 From: Marc Butler <marcbutler@timing.com> To: Robert Watson <rwatson@FreeBSD.org> Cc: freebsd-current@FreeBSD.org Subject: Re: Problem with /dev/stdout in a chroot environment. Message-ID: <20021230221913.A90125@timing.com> In-Reply-To: <Pine.NEB.3.96L.1021230205237.1065A-100000@fledge.watson.org>; from rwatson@FreeBSD.org on Mon, Dec 30, 2002 at 08:54:14PM -0500 References: <20021230161339.A89641@timing.com> <Pine.NEB.3.96L.1021230205237.1065A-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I'm sorry, I have realised that nothing in the /dev directory is being
populated in the chroot by the buildworld attempt, so there is
something problematic further down the chain.
I'm an idiot - thanks and sorry for the bother.
On Mon, Dec 30, 2002 at 08:54:14PM -0500, Robert Watson wrote:
>
> On Mon, 30 Dec 2002, Marc Butler wrote:
>
> > I'm currently trying to build CURRENT (DEC 29 2002) within a chroot
> > environment under CURRENT (DEC 17 2002). Presently I am stuck on an
> > error which appears to be related to /dev/stdout in a chroot environment
> > (devfs?).
>
> Could you provide a bit more detail on what's actually in the chroot
> directory? Have you mounted devfs in chroot/dev, or did you manually
> stick in the device nodes? In -STABLE, /dev/std* were actual device
> nodes, whereas in -CURRENT, devfs makes them symlinks to fd/{0,1,2}, so
> the details here are important...
>
> Robert N M Watson FreeBSD Core Team, TrustedBSD Projects
> robert@fledge.watson.org Network Associates Laboratories
>
--
Marc Butler <marcbutler@timing.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021230221913.A90125>