Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!uakari.primate.wisc.edu!ames!amelia!sun217!truesdel
From: truesdel@sun217..nas.nasa.gov (David A. Truesdell)
Newsgroups: comp.unix.wizards
Subject: Re: bigger longs (64 bits)
Message-ID: <4812@amelia.nas.nasa.gov>
Date: 7 Feb 90 08:02:36 GMT
References: <11071@encore.Encore.COM>
Sender: news@amelia.nas.nasa.gov
Lines: 22

peralta@pinocchio.Encore.COM (Rick Peralta) writes:

>Does anyone have arguments (applications) for using 64 bits?
>
>A few that come to mind are:
>
>	. larger disk storage
>	  (no joke single volumes will be breaking lseek() soon)

lseek is already "broken" here.  I'm in the process of testing a striped
filesystem which currently weighs in at 20 GigaBytes, with a production size
expected to be 200+ GB.  Our fsck needs a special "long lseek" (64 bits) to
move around.

Also, I believe the cray allows files of more than 2 GB.  It already has
64 bit longs.

T.T.F.N.,
dave truesdell (truesdel@prandtl.nas.nasa.gov)

"Testing can show the presense of bugs, but not their absence." -- Dijkstra
"Each new user of a new system uncovers a new class of bugs." -- Kernighan