From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Fri, 1 Jan 2010 21:02:28 -0500 To: 9fans@9fans.net Message-ID: <64836771fc63328bf50220409c7b3b45@brasstown.quanstro.net> In-Reply-To: <> References: <> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Subject: Re: [9fans] du and find Topicbox-Message-UUID: b59238ce-ead5-11e9-9d60-3106f5b1d025 > because the limit is big enough that cases that break the > limit almost never happen except in this case? we can easily fit all the files in most any system in memory. why shouldn't that be the limit? see below. > > i'm not sure i understand when and why this would be useful.  nobody > > has a real worm anymore.  i can walk /sys/src in 0.5s. > > you've got a fast system. > in at least one system i use, du -a of /sys/src takes about 25s. i have a humble 2y.o. single-core 35w celeron as a fileserver. > and /sys/src isn't by any means the largest tree i like to grep > (for instance, searching for lost files with a name i longer remember, > i've been known to search through all the files in my home directory, > ~425000 files at last count) > > sometimes i think it would be nice if du had a breadth-first option. aren't you contridicting yourself? at 128 characters/file, that's only 52mb -- 2% of memory on a typical system these days. why can't it be passed as an argument list? - erik