From owner-cvs-src@FreeBSD.ORG Thu Jan 13 03:39:19 2005 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E1C7316A4CE; Thu, 13 Jan 2005 03:39:19 +0000 (GMT) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBBDB43D2D; Thu, 13 Jan 2005 03:39:18 +0000 (GMT) (envelope-from kientzle@freebsd.org) Received: from freebsd.org (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id j0D3dIOZ021587; Wed, 12 Jan 2005 19:39:18 -0800 (PST) (envelope-from kientzle@freebsd.org) Message-ID: <41E5ED66.4070902@freebsd.org> Date: Wed, 12 Jan 2005 19:39:18 -0800 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031006 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <200501120735.j0C7ZABq048856@repoman.freebsd.org> In-Reply-To: <200501120735.j0C7ZABq048856@repoman.freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: cvs-src@freebsd.org cc: src-committers@freebsd.org cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/include fts.h src/lib/libc/gen fts.3 X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jan 2005 03:39:20 -0000 Pawel Jakub Dawidek wrote: > pjd 2005-01-12 07:35:09 UTC > > FreeBSD src repository > > Modified files: (Branch: RELENG_5) > include fts.h > lib/libc/gen fts.3 > Log: > MFC: fts.h 1.11 > fts.3 1.22 > > Introduce new field 'fts_bignum' which is 64bit long and will allow to > make utilities like du(1) 64bit-clean. > When this field is used, one cannot use 'fts_number' and 'fts_pointer' > fields. > > This commit doesn't break API nor ABI. > > This work is part of the BigDisk project: > > http://www.FreeBSD.org/projects/bigdisk/ Any plans to deal with other fts limits, such as the inability to perform a logical traversal of a path longer than PATH_MAX or to reduce memory consumption when dealing with very large directory trees? I've been tinkering with an alternative to fts for use in bsdtar that doesn't have such limits, but would also be interested in fixing fts, also. Tim