Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 23 Feb 2005 13:14:06 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: coreutils wishlist Message-ID: <20050223121406.GL18314@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <421C0C16 DOT 80702 AT byu DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <421C0C16.80702@byu.net> User-Agent: Mutt/1.4.2i On Feb 22 21:52, Eric Blake wrote: > The following two wishes are not essential, but would improve coreutils. > Unfortunately, I am not in a position to assign copyright to Red Hat at the > moment, so I can't contribute an implementation. Too bad. We could need help. > POSIX requires statvfs() in , but cygwin currently only > provides statfs() in . stat(1) can print more accurate > information from a working statvfs than it currently does with the existing > statfs interface. Which is weird since statvfs doesn't contain much more information than statfs. > Linux provides /dev/full at major device 1, minor 7, and the properties of > world readable/writable, writes error out with ENOSPC, reads behave like > /dev/zero, seeks succeed. The coreutils testsuite tries to use /dev/full > to ensure that utilities behave correctly in the face of write errors. It > looks like it would not be too hard to extend the existing fhandler_zero > functionality into supporting /dev/full. Did you try to create a symlink? mkdir -p /dev ln -s /dev/null /dev/full Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/