Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!olivea!tymix!cirrusl!sunstorm!dhesi From: dhesi%cirrusl@oliveb.ATC.olivetti.com (Rahul Dhesi) Newsgroups: comp.unix.internals Subject: Re: What, exactly, are stat.st_blocks, statfs.f_b Message-ID: <2980@cirrusl.UUCP> Date: 6 Mar 91 09:06:39 GMT References: <1991Mar4.001026.3043@athena.mit.edu> <1991Mar04.015451.10436@kithrup.COM> <6428@auspex.auspex.com> <7235@skye.cs.ed.ac.uk> Sender: news@cirrusl.UUCP Organization: Cirrus Logic Inc. Lines: 16 I think it's safe to say that most users who use "du" and "df" care about the number of kilobytes and not much about the block size. When 4.3BSD seemed to be standardizing on a block size of 1K in such reports, I was happy, especially because the existence of fragments meant, to those wondering about disk space wasted due to fragmentation, that the block size was no longer as important. Then POSIX came along, and SVR4 reared its ugly head too. Now I'm really depressed. Maybe it's time for a new field in the stat struct called something like st_kbytes, and fields in the statfs struct called something like f_kbfree and f_kbavail. -- Rahul Dhesi UUCP: oliveb!cirrusl!dhesi