From: erik quanstrom <quanstro@labs.coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] plan9 iso image
Date: Fri, 28 Jun 2013 14:50:20 -0400 [thread overview]
Message-ID: <1b43a3f01fbc1bc34fbca3e3fd19813a@coraid.com> (raw)
In-Reply-To: <CACm3i_jtHjLtZRnmUUryUhJoK3F061w6gvpM-_wuq6_sivDTnA@mail.gmail.com>
> On Fri, Jun 28, 2013 at 7:50 PM, Terry Wendt <silicon.penguin67@gmail.com>
> wrote:
>
> > If its any help, when I select 9atom.nboot.iso within K3b to burn to
> > disc, it reports the filesize as 360.9 MB but the declared volume size
> > as 721.7 GB.
> >
> >
> This is very interesting because it is exactly double
>
> >> setvolsize(cd, cd->iso9660pvd, (vlong)cd->nextblock *
> Blocksize);
>
> Yes, the volume size is set here, but I don't see any at least obvious
> error. Everything seems to
> be counted rightly in 2K blocks. Are you pointing to an error? because I
> cannot see it...
the original claim was, the size was not set by mk9660. i was
showing where it is set.
and yes, if this calculation is wrong, then here it is. perhaps volsize
is in kb. :-)
- erik
next prev parent reply other threads:[~2013-06-28 18:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 16:27 Terry Wendt
2013-06-28 16:40 ` erik quanstrom
2013-06-28 17:12 ` Terry Wendt
2013-06-28 17:17 ` Paul A. Patience
2013-06-28 17:12 ` Gorka Guardiola
2013-06-28 17:19 ` erik quanstrom
2013-06-28 17:43 ` Gorka Guardiola
2013-06-28 17:50 ` Terry Wendt
2013-06-28 18:13 ` erik quanstrom
2013-06-28 17:38 ` tlaronde
2013-06-28 18:13 ` Gorka Guardiola
2013-06-28 18:16 ` Gorka Guardiola
2013-06-28 18:41 ` Gorka Guardiola
2013-06-28 18:50 ` erik quanstrom [this message]
2013-06-28 18:57 ` Gorka Guardiola
2013-06-28 20:06 ` Gorka Guardiola
2013-06-28 20:13 ` Gorka Guardiola
2013-06-28 20:20 ` Gorka Guardiola
2013-06-28 20:36 ` Gorka Guardiola
2013-06-28 17:06 ` Gorka Guardiola
2013-06-28 17:15 ` Terry Wendt
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=1b43a3f01fbc1bc34fbca3e3fd19813a@coraid.com \
--to=quanstro@labs.coraid.com \
--cc=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).