Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 31 Aug 2002 12:59:13 -0700
From:      Kris Kennaway <kris@obsecurity.org>
To:        Matthew Hunt <mph@astro.caltech.edu>
Cc:        Kris Kennaway <kris@obsecurity.org>, esoha@attbi.com, ports@freebsd.org
Subject:   Re: Bento errorlogs and /dev/fd/*
Message-ID:  <20020831195913.GA2144@xor.obsecurity.org>
In-Reply-To: <20020329163546.A81336@wopr.caltech.edu>
References:  <20020330002019.YFXS2928.rwcrmhc53.attbi.com@rwcrwbc55> <20020329162447.A81231@wopr.caltech.edu> <20020329162707.A56793@xor.obsecurity.org> <20020329163546.A81336@wopr.caltech.edu>

next in thread | previous in thread | raw e-mail | index | archive | help

--7JfCtLOvnd9MIVvH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Mar 29, 2002 at 04:35:46PM -0800, Matthew Hunt wrote:
> Hi Kris,
>=20
> On Fri, Mar 29, 2002 at 04:27:07PM -0800, Kris Kennaway wrote:
>=20
> > > This has to be an input to the program.  And book-building is already
> > > on stdin, so we need another input.
> >=20
> > Looks like we're missing some context on this discussion.
>=20
> OK, I thought I provided a pretty thorough explanation in my original
> email, but I will try again.
>=20
> We want crafty to analyse all of the games in an enormous file, in
> order to produce an "opening book" which is much smaller than the enormous
> file.
>=20
> We have the enormous file in zipped form.  We could unzip it, but it
> would take up a great deal of space (300+ MB) which would be inconvenient
> for the user, and shouldn't really be necessary.
>=20
> In order to instruct crafty to build an opening book, we need to give
> it a command on stdin, specifying the name of the enormous file and
> a couple of other parameters.  This precludes us from supplying the
> enormous file on stdin.
>=20
> My solution has been to use the shell's redirection syntax to gzcat
> the zipped enormous file into crafty's file descriptior #3.  Then, in
> the command we give crafty, tell it that the enormous input file is
> "/dev/fd/3".
>=20
> This works extremely well, except that "/dev/fd/3" does not exist in
> the chroot'ed package building environment.  I proposed several possible
> solutions in my original email, and welcome opinions as to which are the
> best.

FYI, I have just (belatedly) added devfs mounts to the chroot
environment, so problems like this will no longer occur (this also
fixes some other ports which require /dev/random).

Kris

--7JfCtLOvnd9MIVvH
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (FreeBSD)

iD8DBQE9cSAQWry0BWjoQKURAmY+AJ9xS/bDJPL2VQrrXcuMkEDIZaZx5wCg0uxL
6Wwl1bPj5GRxfoGbAn73tlw=
=Qoqb
-----END PGP SIGNATURE-----

--7JfCtLOvnd9MIVvH--

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020831195913.GA2144>