9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Paweł Lasek" <pawel.lasek@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] scuzz doesn't like CD-RW?
Date: Tue, 10 Oct 2006 23:56:10 +0200	[thread overview]
Message-ID: <9f3897940610101456w42b3699k6e71ec8d6ee386f@mail.gmail.com> (raw)
In-Reply-To: <97010a14b9b45544faa19a7117f18316@plan9.bell-labs.com>

On 10/10/06, geoff@plan9.bell-labs.com <geoff@plan9.bell-labs.com> wrote:
> Depending on the drive, you may also need to write multiples of 2048
> bytes, padded if necessary.  tar writes multiples of 512 bytes, so
> using dd to pad it might be necessary.  Even then, if you write
> directly to /dev/sdD0/data, you'll need to fixate (close) the disc.

Typical drives accept only 2048 bytes/sector (or variations for
certain types of recording where you write not only data but also have
to supply all that additional data which makes CD a 700 MB instead of
full 1 GB :>).

IIRC 2048 b/s is standard sector size for data in CD-ROM standard

>From what I know, drives supporting 512 bytes/sector are mostly (If
not only) SCSI (and similar, although I don't think anybody made
FiberChannel CD-RW ;-) ) drives.

On such drives you can find additional jumper which sets either 512 or
2048 bytes per sector. Example of such drive is Yamaha 16x4x4 Fast
SCSI-II CD-RW. AFAIK the only system which requires such setting is
VMS, which uses only 512 mode. I'm not sure, but I think that
specification doesn't have option for switching sector size on the fly
and propably has fixed data structures which break if incompatible
modes are selected.

> I'm not sure what there is to fear about iso 9660 format.  It doesn't
> encrypt your data and files tend to be written contiguously (I'm not
> sure if that's required by the format or just a good idea to make
> reading faster), so digging the data out by hand shouldn't be
> difficult if suddenly all the world's 9660-reading programs stopped
> working.

As long as nobody starts to put important data in subchannels or uses
some of the wierder aspects of ISO9660 (Multiple disk filesystems? Is
there any program which is capable of making those at all??). Most
common, single session CD's have metadata at the beginning, then
files. Multi-session add pointer for 'updated descriptor' or something
like that which is address of next descriptor in chain (next session).

At least I think it should be much easier to decode (as long as it's
pure-data track, without any subchannel craziness) than NTFS (which,
to my big surprise, was much easier to decode by hand than ext2....).

-- 
Paul Lasek


  reply	other threads:[~2006-10-10 21:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-09  5:01 cej
2006-10-09 18:12 ` geoff
2006-10-09 18:34   ` geoff
2006-10-10  4:28     ` cej
2006-10-10  7:29       ` Bruce Ellis
2006-10-10  7:44         ` Charles Forsyth
2006-10-10  7:50         ` cej
2006-10-10  8:09           ` Charles Forsyth
2006-10-10  8:13             ` Charles Forsyth
2006-10-10  8:23               ` Charles Forsyth
2006-10-10  8:37                 ` Bruce Ellis
2006-10-10 19:50       ` geoff
2006-10-10 21:56         ` Paweł Lasek [this message]
2006-10-10 22:14           ` Martin Neubauer
2006-10-11 10:46         ` cej

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=9f3897940610101456w42b3699k6e71ec8d6ee386f@mail.gmail.com \
    --to=pawel.lasek@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).