Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!think.com!snorkelwacker.mit.edu!bloom-picayune.mit.edu!athena.mit.edu!jik
From: jik@athena.mit.edu (Jonathan I. Kamens)
Newsgroups: comp.unix.internals
Subject: Re: What, exactly, are stat.st_blocks, statfs.f_b
Message-ID: <1991Mar11.001544.29006@athena.mit.edu>
Date: 11 Mar 91 00:15:44 GMT
References: <6428@auspex.auspex.com> <7235@skye.cs.ed.ac.uk> <2980@cirrusl.UUCP> <6487@auspex.auspex.com> <2992@cirrusl.UUCP>
Sender: news@athena.mit.edu (News system)
Organization: Massachusetts Institute of Technology
Lines: 19


  I'm sorry to be so insistent, but I still haven't seen one clear,
unequivocal answer to this question: If a system has st_blocks in its stat
structure, then how can I tell what the count in st_blocks is in terms of?

  Do I assume it's 512 everywhere?  Do I do statfs on each file?  Or something
else?  I'm willing to use #ifdef magic in order to make it work on various
different types of systems, but I haven't yet seen one clear answer to my
question of *what* the #ifdef magic should do.

  The theoretical discussion is interesting, but it doesn't really help to
solve my particular problem, especially since I don't understand all of it at
first glance and don't have time to read it enough times to understand it :-).

-- 
Jonathan Kamens			              USnail:
MIT Project Athena				11 Ashford Terrace
jik@Athena.MIT.EDU				Allston, MA  02134
Office: 617-253-8085			      Home: 617-782-0710