From owner-freebsd-ports  Thu Nov  2 15:55:10 2000
Delivered-To: freebsd-ports@freebsd.org
Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102])
	by hub.freebsd.org (Postfix) with ESMTP
	id 71AFF37B4CF; Thu,  2 Nov 2000 15:55:08 -0800 (PST)
Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26])
	by mail-blue.research.att.com (Postfix) with ESMTP
	id 0F1364CE2A; Thu,  2 Nov 2000 18:55:04 -0500 (EST)
Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46])
	by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id SAA12196;
	Thu, 2 Nov 2000 18:55:03 -0500 (EST)
From: Bill Fenner <fenner@research.att.com>
Received: (from fenner@localhost)
	by windsor.research.att.com (8.8.8+Sun/8.8.5) id PAA21073;
	Thu, 2 Nov 2000 15:55:02 -0800 (PST)
Message-Id: <200011022355.PAA21073@windsor.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: knu@idaemons.org
Subject: Re: /dev/null unwritable problem again?
Cc: asami@freebsd.org, freebsd-ports@freebsd.org
Date: Thu, 2 Nov 2000 15:55:01 -0800
Versions: dmail (solaris) 2.2g/makemail 2.9a
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


Did anything do a "fetch -o /dev/null"?  I've had trouble with fetch
removing /dev/null after a failed fetch.

  Bill


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