Date: Fri, 7 Jul 2000 01:33:12 +0200 (CEST) From: Paul Herman <pherman@frenchfries.net> To: Bill Fumerola <billf@chimesnet.com> Cc: Sheldon Hearn <sheldonh@uunet.co.za>, freebsd-bugs@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: bin/19635: add -c for grand total to df(1), like du(1) does Message-ID: <Pine.BSF.4.21.0007070010190.4627-100000@bagabeedaboo.security.at12.de> In-Reply-To: <20000706163400.T4034@jade.chc-chimes.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 6 Jul 2000, Bill Fumerola wrote: > On Thu, Jul 06, 2000 at 06:09:54PM +0200, Paul Herman wrote: > > > Naturally, "no reason not to put it in" is most certainly *not* a > > reason to put it in. I would like to hear some to sway me one way or > > the other. > > > > [...] > [hawk-billf] /home/billf > du -cs /usr/src/sys/i386 /usr/ports/math > 6282 /usr/src/sys/i386 > 15288 /usr/ports/math > 21570 total > > Precedence. > OK, I'm with ya, I could go with Precedence, but you have to admit, it's pretty weak. Just because "it's been done before"...? Hmmm. Well, I was hoping for something concrete about the program like "because this option gives us something never seen by sysadmins before without massive contortions", or "this option does correctly what XXX program never could..." etc. Unfortunately, I can't think of any myself. For what one person's opinion is worth, I still haven't heard a strong reason for this. Sorry guys, you can still color me undecided on this one. :( On a side note, look what I found: bash-2.03# cd bash-2.03# ln -s /dev/ad0s6e "Heh? What's this?" bash-2.03# mount "Heh? What's this?" /mnt bash-2.03# ln -s /dev/ad0s6f total bash-2.03# mount total /mnt2 bash-2.03# mkdir whut_thuh_hey; cd whut_thuh_hey bash-2.03# ln -s /dev/ad0s6g total bash-2.03# mount total /mnt3 bash-2.03# df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad0s2a 446503 30922 379861 8% / /dev/ad0s9e 1453615 758910 578416 57% /usr /dev/ad0s9f 968983 357403 534062 40% /usr/local /dev/ad0s9g 242239 9945 212915 4% /var /dev/ad0s9h 2013515 1242447 609987 67% /u01 procfs 4 4 0 100% /proc Heh? What's this? 242239 9945 212915 4% /mnt total 1581144 505684 995140 34% /mnt2 total 1391380 414168 906528 31% /mnt3 bash-2.03# Hee, hee. Yes, this is probably no big deal (and not put forth as any strong argument for not commiting this) but who knows what some cronjob scripts might expect. Hmmm, let me give constructive criticism a shot and see how far it goes: Perhaps if it were expected that the "df -c" output were completly different? Then "total" would be less likely to be counted as some other filesystem by mistake? Perhaps something along the lines: bash-2.0.3# df -c /usr /usr/local Totals for: /usr /usr/local 1K-Blocks: 2422598 Used: 1116313 Avail: 1306285 Capacity: 46% Dunno how that would go over with the purists, though... after all 'df' is in one of the holiest of directories... /bin. <g> -Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0007070010190.4627-100000>