From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Mon,  2 Sep 1996 21:39:06 -0500
From: Brandon Black photon@nol.net
Subject: ls quibble
Topicbox-Message-UUID: 4c530346-eac8-11e9-9e20-41e7f4b1d025
Message-ID: <19960903023906.HzTiib7AJXvUELuA2sj_Gy-qCFiFAL0d7cORuffbGnA@z>


On Mon, 2 Sep 1996, Russ Cox wrote:

> term% diff /sys/src/cmd/ls.c /sys/clean-src/cmd
> 190c190
> < 		sprint(buf, "%lud", db->length);
> ---
> > 		sprint(buf, "%ld", db->length);
> 220c220
> < 		Bprint(&bin, "%M %C %*d %*s %s %*lud %s %s\n",
> ---
> > 		Bprint(&bin, "%M %C %*d %*s %s %*ld %s %s\n",
> term%
>
> so that big hard drives (>2GB) have positive
> sizes for /dev/hd?disk
>

Going to unsigned takes the limit from 2Gb to 4Gb... what if you have larger
(i.e. 4.8Gb, 9Gb) drives... Or hardware RAID boxes that appear to the operating
system to be gargantuan multi-gigabyte physical drives...?  Obviously, its
just ls output, and doesn't affect anything to do with using the drives, but
still...in such a generally robust operating system, its a shame even in
something as insignificant as the output format of "ls", to be narrowminded
in choosing variable sizes....

What variable type is the internal, real, size value for files?  I would
assume it is probably a 64 bit value, or else the filesystem would be limited
to never having files larger than 4Gb...


..............................................
: Brandon Lee Black  : photon@gnu.ai.mit.edu :
:....................: photon@nol.net        :
: "Sanity is the     : photon@vanity.ops.org :
: trademark of a     : vis_blb@unx1.shsu.edu :
: weak mind. . ."    : +1 713 397 3490       :
:....................:.......................: