From owner-freebsd-doc  Tue Sep 26 15:38:34 2000
Delivered-To: freebsd-doc@freebsd.org
Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229])
	by hub.freebsd.org (Postfix) with ESMTP
	id 4CCB037B423; Tue, 26 Sep 2000 15:38:32 -0700 (PDT)
Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1])
	by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e8QMcQU81331;
	Tue, 26 Sep 2000 15:38:26 -0700 (PDT)
	(envelope-from jkh@winston.osd.bsdi.com)
To: Nik Clayton <nik@freebsd.org>
Cc: doc@freebsd.org
Subject: Re: Argh, somebody broke docproj and hence make release! 
In-Reply-To: Message from Nik Clayton <nik@freebsd.org> 
   of "Tue, 26 Sep 2000 23:21:07 BST." <20000926232107.A22188@catkin.nothing-going-on.org> 
Date: Tue, 26 Sep 2000 15:38:26 -0700
Message-ID: <81327.970007906@winston.osd.bsdi.com>
From: Jordan Hubbard <jkh@winston.osd.bsdi.com>
Sender: owner-freebsd-doc@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> Can you give me a host name on which it's failed, and the commands I need
> to duplicate the chroot environment.  I can't duplicate this locally, and
> don't have the resources to run a full release.  If I can at least ssh in
> to a build box that's showing the problem then I've got a chance of
> debugging it.

Argh, I was afraid you'd say that.  Everything here is firewalled from
the outside, even to ssh, and I can't get you into any of our "guest
boxes" as root, which is what you'd need to be in order to chroot into
anywhere.

Not being able to do a `make release' locally is a real handicap in
today's increasingly-more-complex FreeBSD, especially for any docs we
bundle automatically into each release.  What sort of resources are
you short on?  If it's just disk, I'm sure the company we both work
for would be happy to buy you a big honkin' IDE drive for just that
purpose. :)

- Jordan


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