From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] tarfs & 2GB limit
Date: Fri, 13 Jan 2006 14:33:28 -0800 [thread overview]
Message-ID: <ac4f1be2e68c1cf16740673b12ef5c8e@collyer.net> (raw)
In-Reply-To: <20060113164151.ED27C35076@dexter-peak.quanstro.net>
The tar archive format limits archive members to 2 bytes = 8GB.
There are 11 octal digits for file size. The current Plan 9 tar will
complain and refuse to add a file to a tar archive if its size exceeds
8GB-1.
The p9p tarfs is older than the Plan 9 one; in particular, the change
to cast seek's second argument to vlong is already in the Plan 9
tarfs, though not all of the other changes are.
next prev parent reply other threads:[~2006-01-13 22:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 14:11 cej
2006-01-13 16:41 ` erik quanstrom
2006-01-13 22:33 ` geoff [this message]
2006-01-14 0:30 ` erik quanstrom
2006-01-13 22:36 ` C H Forsyth
2006-01-13 22:43 ` geoff
2006-01-14 0:03 ` erik quanstrom
2006-01-14 0:33 ` Devon H. O'Dell
2006-01-14 0:59 ` Paul Lalonde
2006-01-14 1:07 ` erik quanstrom
2006-01-14 12:15 ` erik quanstrom
2006-01-14 18:22 ` Russ Cox
2006-01-14 21:27 ` erik quanstrom
2006-01-16 2:57 ` erik quanstrom
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=ac4f1be2e68c1cf16740673b12ef5c8e@collyer.net \
--to=geoff@collyer.net \
--cc=9fans@cse.psu.edu \
/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).