From: "Boyd Roberts" <boyd@planete.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Df command in Plan9?
Date: Sun, 22 Oct 2000 02:25:29 +0200 [thread overview]
Message-ID: <005201c03bbe$95ac5ca0$b6c784c3@cybercable.fr> (raw)
In-Reply-To: <200010220013.UAA10279@smarty.smart.net>
From: Rick Hohensee <humbubba@smarty.smart.net>
> > > df, BTW, is one of those design flaws of unix that is so
> > > obvious nobody sees it. A directory has a size. It is the
> > > size of it's contents, not the size of the "file" containing
> > > the dirnames and so on. The size of a directory, it's "du-size",
> > > is something the filesystem should keep track of.
> >
> > Sigh... Rick, we've been through that how many times?
>
> Who's "we"? I don't recall mentioning this here. You and I haven't
> been over this at all that I recall. I did have some considered criticism
> of this in comp.unix.programmer, where a regular there breached the name
> Dyn-du.
oh nonsense. directories are the size of their meta-data.
> This drops nothing. This points up the one thing you SHOULD have called me
> on, which is that the term "design flaw" is an exaggeration. Dyndufs is
> more like a design opportunity.
this is exactly the problem with linux; everything is a 'design opportunity'.
it's never ending and has not advanced the state of the art by one iota.
>
> True. When was the last time you did a du on / ? Or /usr ? Why?
>
not for a while, but when i needed to tar up a tree on multiple floppies
i used du, before invoking tar. i see that SCO broke tar so it would
know about multiple volumes. i wrote a script. it's called a 'tools
approach'.
> > * Non-local operations are prone to races. Even cross-directory
> > rename(2) is a major PITA. The thing you are proposing is going to be
> > much worse.
> > * Programs that might benefit from that "du-size" are either
> > going to scan the tree anyway or belong to very small class -
> > filemanagers.
>
> You've just promoted ls to a filemanager. How Microsoftian.
kirk said that it took multiple iterations to get rename(2)
right, because it's a nasty problem.
next prev parent reply other threads:[~2000-10-22 0:25 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-20 20:31 Russ Cox
2000-10-20 21:44 ` Alexander Viro
2000-10-20 21:51 ` Boyd Roberts
2000-10-21 0:37 ` Rick Hohensee
2000-10-21 10:13 ` Alexander Viro
2000-10-22 0:13 ` Rick Hohensee
2000-10-22 0:25 ` Boyd Roberts [this message]
2000-10-22 15:41 ` Rick Hohensee
2000-10-23 9:02 ` Douglas A. Gwyn
2000-10-23 10:30 ` Alexander Viro
2000-10-24 11:37 ` Boyd Roberts
2000-10-25 8:30 ` Douglas A. Gwyn
2000-10-26 4:54 ` Alexander Viro
2000-10-26 5:44 ` Boyd Roberts
2000-10-22 11:34 ` Alexander Viro
2000-10-22 15:59 ` Rick Hohensee
2000-10-22 16:43 ` Alexander Viro
2000-10-23 5:06 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2000-10-22 17:06 forsyth
2000-10-23 2:23 ` Rick Hohensee
2000-10-22 11:04 forsyth
2000-10-22 12:49 ` Boyd Roberts
2000-10-22 13:16 ` Alexander Viro
2000-10-22 16:07 ` Rick Hohensee
2000-10-22 16:31 ` Alexander Viro
2000-10-23 2:07 ` Rick Hohensee
2000-10-22 16:05 ` Rick Hohensee
2000-10-20 21:51 presotto
2000-10-20 20:22 Mark C. Otto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='005201c03bbe$95ac5ca0$b6c784c3@cybercable.fr' \
--to=boyd@planete.net \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).