9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Brandon Black photon@nol.net
Subject: ls quibble
Date: Mon,  2 Sep 1996 21:39:06 -0500	[thread overview]
Message-ID: <19960903023906.HzTiib7AJXvUELuA2sj_Gy-qCFiFAL0d7cORuffbGnA@z> (raw)


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       :
:....................:.......................:






             reply	other threads:[~1996-09-03  2:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-09-03  2:39 Brandon [this message]
  -- strict thread matches above, loose matches on Subject: below --
1996-09-03  2:48 Scott
1996-09-03  2:36 Scott
1996-09-03  2:12 Russ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19960903023906.HzTiib7AJXvUELuA2sj_Gy-qCFiFAL0d7cORuffbGnA@z \
    --to=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).