From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, Russ Cox <rsc@swtch.com>
References: <ACCF003CBA3D09458207DB0CB86AD17D20153F@XMAIL.asuch.cas.cz>
	<20060113164151.ED27C35076@dexter-peak.quanstro.net>
	<20060114121550.4FD0134FFB@dexter-peak.quanstro.net>
	<ee9e417a0601141022g720dd846q6e1148d6100c95b6@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
In-Reply-To: <ee9e417a0601141022g720dd846q6e1148d6100c95b6@mail.gmail.com>
Subject: Re: [9fans] tarfs & 2GB limit
Message-Id: <20060114212732.EA99D11498C@dexter-peak.quanstro.net>
Date: Sat, 14 Jan 2006 15:27:32 -0600
Cc: 
Topicbox-Message-UUID: d7102ace-ead0-11e9-9d60-3106f5b1d025

you're right, of course.

Russ Cox <rsc@swtch.com> writes

| 
| > one question, with tpfs, there's a cast to vlong:
| >         seek(tapefile, 512*(vlong)r->data+off, 0);
| > i cast to (int) because the size is only 3 bytes.
| > is there anything drasticlly wrong with this?
| 
| the cast is there not because r->data is big,
| but so that multiplying by 512 and adding
| off doesn't overflow.