Re: du --files-from feature request

[Aaron Peterson]

Wow, You guys seem to really care.

 6.10 is the version of du  that I'm using. (Ubuntu Ibex)

I understand enough now to get my task done using existing tools, and
it looks like ya'll fixed some documentation as well.

(There are many newer messages that I'm not reading fully)

So, I understand that newline /CR is a complicated way to delimit
lists  lists because of system variations, but did somebody tackle
this by determining what the (possibly multi byte) newline sequence is
and make a --from-files work?

Either way, I'm impressed by the enthusiasm.
-AP


On Sun, Nov 30, 2008 at 5:44 PM, Brian Dessent <address@hidden> wrote:
> Aaron Peterson wrote:
>
>> I spend many hours trying to figure this out / and searching for solution.
>> It turns out that the \0 delimited list requirement was very painful.
>> I wish I could cat the output of find  into du and get the total
>
> It's meant to be used like:
>
> $ find . -type f -print0 | du --files0-from=-
>
> Note also that xargs takes -0 for the same reason:
>
> $ find . -type f -print0 | xargs -0 command
>
> Using tr is not the intended use pattern, as it completely misses the
> point.  \0 is the only character that cannot be part of a filename
> (other than '/'), so the only reliable way to deal with arbitrary
> filenames without complicated quoting is to \0-delimit them.  Using tr
> to convert newlines to \0 fails if you have filenames with newlines in
> them, not to mention that it's pointless overhead.
>
> Brian
>