Date: 02 Nov 2000 16:26:05 -0800 From: asami@freebsd.org (Satoshi - Ports Wraith - Asami) To: Bill Fenner <fenner@research.att.com> Cc: knu@idaemons.org, freebsd-ports@freebsd.org Subject: Re: /dev/null unwritable problem again? Message-ID: <vqcbsvx9a02.fsf@silvia.hip.berkeley.edu> In-Reply-To: Bill Fenner's message of "Thu, 2 Nov 2000 15:55:01 -0800" References: <200011022355.PAA21073@windsor.research.att.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* From: Bill Fenner <fenner@research.att.com> * 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?vqcbsvx9a02.fsf>