home *** CD-ROM | disk | FTP | other *** search
- Submitted-by: djm@eng.umd.edu (David J. MacKenzie)
-
- > However, the argument that 1024 8-bit bytes is somehow an optimum unit
- > of measurement for file sizes needs to be shot down. It's just one of
- > many possible arbitrary choices. Most users of AT&T UNIX are
- > accustomed to 512 8-bit bytes and most users of BSD are accustomed to
- > 1024 8-bit bytes.
-
- Users of System V may be "used" to 512-byte units, but the results of
- the poll seem to indicate that most of them hate them nonetheless and
- would rather have 1024-byte units.
-
- People think and count naturally in powers of 10; since 1024 is close
- to a power of 10, it has become a standard unit for measuring disk
- space on most operating systems, even when selling disks (especially
- floppies). It is therefore not arbitrary; it is a de facto standard.
-
- > I did note that not all
- > file sizes (expressed as number of bits) are exactly divisible by 8,
- > which would make the 8-bit byte rather a silly unit of measure. And
- > other-size bytes more appropriate for such systems aren't necessarily
- > any more useful. While a 9-bit byte may be ideal for an 18-bit system,
- > what would you use on a 60-bit system?
-
- GNU and probably POSIX.2 will never run on systems with byte sizes
- other than 8 bits, so there is realistically no point in bothering to
- consider them. No filesystems allocate or measure space in units of
- less than a byte, either.
-
- > I must say that attempts to force "solutions" based on popularity
- > polls rather than careful reasoning about the actual relevant
- > factors is disgusting.
-
- POSIX committees have engaged in much invention of untested schemes
- because of philosophies like this one.
-
- --
- David J. MacKenzie <djm@eng.umd.edu> <djm@ai.mit.edu>
-
- Volume-Number: Volume 24, Number 96
-
-