9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] how to burn iso
Date: Mon, 24 Oct 2011 11:58:28 -0400	[thread overview]
Message-ID: <CADSkJJXn2G=KyAjZaH18JXa1ePBkdWdwLi_6kCRj_Z6QsrQWNA@mail.gmail.com> (raw)
In-Reply-To: <CAOEdRO149BJJf+yPtgPTw9Eh-QCU=zGouEcWTUTANkbYMm-r2A@mail.gmail.com>

On Mon, Oct 24, 2011 at 9:41 AM, Rudolf Sykora <rudolf.sykora@gmail.com> wrote:
> My current understanding is that I need as if 3 different views on a CD:
> -- if audio CD is to be written, I need to follow some structure in
> which audio tracks should be written, so that other audio readers
> understand it,
> -- if data files are to be written, I first need some filesystem
> (iso9660) on the CD and then write the data files into this
> filesystem,
> -- if I have an ISO image, I'd expect that this is, without any
> translation, just somehow raw-copied to the CD (similarly to a way a
> dd command works).
>
> While writing to cd/wa may solve the audio case, I don't understand
> how the data file vs ISO is coped with, as the example just writes an
> ISO to cd/wd...

cdfs only provides the 'ISO image raw-copied to the CD' case.
You have an ISO image, so the scripts that have been posted
will do the burn to the CD.

If data files are to be written, you have the order of operations
backward: you don't start with a file system on the CD and then
write the files to that file system, because the CD is write-once
and the file system is not really set up for that.  Instead, you
create an ISO image from the files you care about and then
you write that directly to the CD.

Russ


  parent reply	other threads:[~2011-10-24 15:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-24  7:43 Rudolf Sykora
2011-10-24  8:04 ` Peter A. Cejchan
     [not found] ` <CAM6ozu6MQ5G83VPr9-0ucbL-m0bOA9BQucVH0KzTCTKDVD+8ZA@mail.gmail.c>
2011-10-24 12:15   ` erik quanstrom
2011-10-24 13:41     ` Rudolf Sykora
2011-10-24 13:54       ` Peter A. Cejchan
     [not found]       ` <CAM6ozu4=Ym4SEL07n_MZ9B2u38vQt9Oid9SjuWHpy4dGzxyhQA@mail.gmail.c>
2011-10-24 14:13         ` erik quanstrom
2011-10-24 15:58       ` Russ Cox [this message]
     [not found]     ` <CAOEdRO149BJJf+yPtgPTw9Eh-QCU=zGouEcWTUTANkbYMm-r2A@mail.gmail.c>
2011-10-24 13:47       ` 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='CADSkJJXn2G=KyAjZaH18JXa1ePBkdWdwLi_6kCRj_Z6QsrQWNA@mail.gmail.com' \
    --to=rsc@swtch.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).