> du(1) stands for Disk Usage. But does this, with the "historical" use,
> has any real sense now, with a namespace that can be, not only built by
> presenting a same file via different paths, but a combination of local
> storage (including memory one...) and remote storage?
i agree with charles. while one may need to take into account what
you're du'ing, du works as advertized. -s adds up all the directly-used
storage under the given path. now if one points it at something that
might include things one is not interested in, i would say the way to
correct that is by changing the path handed to du.
i think another way to state what you're getting at might be, why
doesn't du have some ai to figure out the exact on-disk footprint
under some path? clearly du can't do that since it's a 9p program,
and won't know a thing about the file server(s) it's talking to.
sort of reminds me of the holy grail, there's no way for du to be
the 1st soldier:
1st soldier: Who goes there?
King Arthur: It is I, Arthur, son of Uther Pendragon, from the castle of
Camelot.
King of the Britons, defeater of the Saxons, Sovereign of all
England!
1st soldier: Pull the other one!
King Arthur: I am, and this is my trusty servant Patsy. We have ridden the
length and breadth
of the land in search of knights who will join me in my court
at Camelot.
I must speak with your lord and master.
1st soldier: What? Ridden on a horse?
King Arthur: Yes!
1st soldier: You're using coconuts!
- erik
