From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <3505d2a562248941e6bb66dbf15c7c86@ladd.quanstro.net> References: <99100159-30FB-4811-87FD-7F960CA7F948@gmail.com> <3505d2a562248941e6bb66dbf15c7c86@ladd.quanstro.net> Date: Fri, 28 Jun 2013 19:43:27 +0200 Message-ID: From: Gorka Guardiola To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=20cf300fb21595735104e03a6ac4 Subject: Re: [9fans] plan9 iso image Topicbox-Message-UUID: 68708408-ead8-11e9-9d60-3106f5b1d025 --20cf300fb21595735104e03a6ac4 Content-Type: text/plain; charset=ISO-8859-1 On Fri, Jun 28, 2013 at 7:19 PM, erik quanstrom wrote: > > Wouldn't surprise me, but it seems to work for me. If anyone has a > > more detailed explanation of what is wrong where, I'll take a look at > > it. > > we're now writing the nwa to disk. this calculation appears to be > incorrect. > here's the check in cdfs: > > /* reconcile differing nwas */ > if (aux->mmcnwa != nwa) { > fprint(2, "%s: nwa from drive %,ld != computed nwa %,ld\n", > argv0, aux->mmcnwa, nwa); > fprint(2, "\tbe careful! assuming computed nwa\n"); > /* the invisible track may still start at the old nwa. */ > // aux->mmcnwa = nwa; > } > > Maybe I am not understanding. We were talking about mkisofs which generates an iso file. This is cdfs check for the first writable block of the track, which has to do with burning it. An iso is burnt inside a track and is mostly independent from the details of what tracks exist. Terry downloaded the iso, and tried to burn it in linux. If something is wrong it would be in the iso file generated, which does not have to do anything with cdfs. G. --20cf300fb21595735104e03a6ac4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On Fri, Jun 28, 2013 at 7:19 PM, erik quanstrom &= lt;quanstro@quan= stro.net> wrote:
> Wouldn't surprise= me, but it seems to work for me. =A0If anyone has a
> more detailed explanation of what is wrong where, I'll take a look= at
> it.

we're now writing the nwa to disk. =A0this calculation appears to= be incorrect.
here's the check in cdfs:

=A0 =A0 =A0 =A0 /* reconcile differing nwas */
=A0 =A0 =A0 =A0 if (aux->mmcnwa !=3D nwa) {
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 fprint(2, "%s: nwa from drive %,ld != =3D computed nwa %,ld\n",
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 argv0, aux->mmcnwa, nwa)= ;
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 fprint(2, "\tbe careful! =A0assuming c= omputed nwa\n");
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 /* the invisible track may still start at t= he old nwa. */
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 // aux->mmcnwa =3D nwa;
=A0 =A0 =A0 =A0 }


Maybe I am not understanding. We were talking about mkisofs wh= ich generates an iso file.
This is cdfs check for the first= writable block of the track, which has to do with burning it.
An iso is burnt inside a track and is mostly independent from th= e details of what tracks exist.
Terry downloaded the iso, a= nd tried to burn it in linux. If something is wrong it would be
in the iso file generated, which does not have to do anything with cdfs.
G.

=A0
=
--20cf300fb21595735104e03a6ac4--