From owner-freebsd-ports Thu Nov 2 16:28:26 2000 Delivered-To: freebsd-ports@freebsd.org Received: from granger.mail.mindspring.net (granger.mail.mindspring.net [207.69.200.148]) by hub.freebsd.org (Postfix) with ESMTP id 85E0037B4D7 for ; Thu, 2 Nov 2000 16:28:24 -0800 (PST) Received: from silvia.hip.berkeley.edu (sji-ca5-234.ix.netcom.com [209.109.234.234]) by granger.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id TAA00829; Thu, 2 Nov 2000 19:28:13 -0500 (EST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.11.1/8.11.0) id eA30Qqn30325; Thu, 2 Nov 2000 16:26:52 -0800 (PST) (envelope-from asami) To: Bill Fenner Cc: knu@idaemons.org, freebsd-ports@freebsd.org Subject: Re: /dev/null unwritable problem again? References: <200011022355.PAA21073@windsor.research.att.com> From: asami@freebsd.org (Satoshi - Ports Wraith - Asami) Date: 02 Nov 2000 16:26:05 -0800 In-Reply-To: Bill Fenner's message of "Thu, 2 Nov 2000 15:55:01 -0800" Message-ID: Lines: 19 X-Mailer: Gnus v5.7/Emacs 20.7 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * From: Bill Fenner * Did anything do a "fetch -o /dev/null"? I've had trouble with fetch * removing /dev/null after a failed fetch. I don't think that is very likely. I can't find any evidence that postgresql7 has built even once in the package build cluster. The chroot environments are reused over the course of one package set build. Unless hundreds of other ports are removing /dev/null, I find it very unlikely that postgres keeps running into chroot environments with missing /dev/null's. If it is postgresql itself that is removing /dev/null, that is a different matter. I'll put in a "ls" in the Makefile so we'll see what's happening. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message