From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <20130628173824.GA225@polynum.com> Date: Fri, 28 Jun 2013 20:41:46 +0200 Message-ID: From: Gorka Guardiola To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=20cf300fb21525bb5b04e03b3bda Subject: Re: [9fans] plan9 iso image Topicbox-Message-UUID: 689e220a-ead8-11e9-9d60-3106f5b1d025 --20cf300fb21525bb5b04e03b3bda Content-Type: text/plain; charset=ISO-8859-1 > > the blocks 2M aligned you should be fine with most modern BIOSes. > > I meant 2K aligned. On Fri, Jun 28, 2013 at 7:50 PM, Terry Wendt 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... G. --20cf300fb21525bb5b04e03b3bda Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

=

the blocks 2M aligned you should be fine with most modern BIOSes.

=A0
I m= eant 2K aligned.


On Fri= , Jun 28, 2013 at 7:50 PM, Terry Wendt=A0<silicon.penguin67@gmai= l.com>=A0wrote:
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
a= s 721.7 GB.


This is very interestin= g because it is exactly double

>> =A0 =A0 =A0 =A0 =A0 =A0 =A0setvolsize(cd, cd->iso9660pvd, (vlo= ng)cd->nextblock * Blocksize);

Yes, the volume size is set here, but I don't see an= y at least obvious error. Everything seems to
be counted= rightly in 2K blocks. Are you pointing to an error? because I cannot see i= t...

G.
=A0

=A0
--20cf300fb21525bb5b04e03b3bda--