9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Terry Wendt <silicon.penguin67@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] plan9 iso image
Date: Fri, 28 Jun 2013 12:50:27 -0500	[thread overview]
Message-ID: <CAD_JZaoTjNKiN2=WEGmjrBqwq5q_SNrS235iRXtvZ3zgK3aR6g@mail.gmail.com> (raw)
In-Reply-To: <CACm3i_hiJkfxL8dz9Zgjo=_SvvtUwpjCv+_TLv=P9TKOXgRR9Q@mail.gmail.com>

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.

Interesting.
Terry.

On Fri, Jun 28, 2013 at 12:43 PM, Gorka Guardiola <paurea@gmail.com> wrote:
>
>
>
> On Fri, Jun 28, 2013 at 7:19 PM, erik quanstrom <quanstro@quanstro.net>
> 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.
>
>



  reply	other threads:[~2013-06-28 17: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 [this message]
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
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='CAD_JZaoTjNKiN2=WEGmjrBqwq5q_SNrS235iRXtvZ3zgK3aR6g@mail.gmail.com' \
    --to=silicon.penguin67@gmail.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).