From owner-freebsd-hackers  Mon Apr 21 21:11:02 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA11570
          for hackers-outgoing; Mon, 21 Apr 1997 21:11:02 -0700 (PDT)
Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA11562
          for <freebsd-hackers@FreeBSD.ORG>; Mon, 21 Apr 1997 21:10:55 -0700 (PDT)
Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.7.3) id OAA08899; Tue, 22 Apr 1997 14:10:36 +1000 (EST)
Date: Tue, 22 Apr 1997 14:10:35 +1000 (EST)
From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
To: Adrian Chadd <adrian@staff.psinet.net.au>
cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: 64 bit number definitions?
In-Reply-To: <Pine.LNX.3.93.970422111805.5455C-100000@staff.psinet.net.au>
Message-ID: <Pine.BSF.3.91.970422140745.10264D-100000@panda.hilink.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk



On Tue, 22 Apr 1997, Adrian Chadd wrote:

> Is there anywhere a 64 bit type in C I can get my hands on?
> (the longest i've seen builtin to the compiler is the unsigned long, but I
> commonly write more than 4 gigabytes to tape at once).
> 
> Which reminds me, freebsd's GNU tar apparently uses an "int" type for
> tot_written, that doesn't look like it cant count over 32k bytes.

File offsets are described as off_t which is a quad_t, which is a 'long 
long'.

I don't know why off_t is not u_quad_t (unsigned long long).

Snuggle up and read /usr/include/sys/types.h before going to sleep tonight.

Danny