> That makes the question really "should the iso9660 filesystem code
> learn how to write iso9660 images?"  I don't know how hard this would
> be...

I don't know much about how isofs is laid out, but two points come to mind:

- On a read-only filesystem, you don't need a free/in-use bitmap.
- You also don't need indirect blocks, since each file could conceivably
  be laid out linearly.

A truly read/write isofs would need to maintain the above - the first is
obvious, and the second is required to support independent writes from
more than one process.

So the question really is: "**can** the iso9660 filesystem code be made to
write iso9660 images as a general-purpose filesystem?"

-- 
David Jones, M.A.Sc student, Electronics Group (VLSI), University of Toronto
           email: dej@eecg.toronto.edu, finger for PGP public key
         For a good time, telnet torfree.net and log in as `guest'.
          Click me!