From owner-freebsd-hackers Sat Jun 24 07:55:26 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id HAA11139 for hackers-outgoing; Sat, 24 Jun 1995 07:55:26 -0700 Received: from whisker.internet-eireann.ie (whisker.internet-eireann.ie [194.9.34.204]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id HAA11129 ; Sat, 24 Jun 1995 07:55:10 -0700 Received: from localhost (localhost [127.0.0.1]) by whisker.internet-eireann.ie (8.6.11/8.6.9) with SMTP id PAA09249; Sat, 24 Jun 1995 15:55:28 +0100 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: apollo@io.org (Andrew Herdman), hackers@FreeBSD.org Subject: Re: Creating iso9660 filesystems In-reply-to: Your message of "Fri, 23 Jun 1995 21:00:51 +0200." <199506231900.VAA00491@uriah.heep.sax.de> Date: Sat, 24 Jun 1995 15:55:28 +0100 Message-ID: <9247.804005728@whisker.internet-eireann.ie> From: "Jordan K. Hubbard" Sender: hackers-owner@FreeBSD.org Precedence: bulk > There'a a ``mkisofs'' command available, but it doesn't act like a > regular file system. Instead, it's supposed to create a single huge > file that can be dumped onto a WORM. Not sure if this is what you're > looking for. Actually, it does generate a `filesystem' which you can then use the VN driver to mount as a virtual CD of sorts; I used this to inspect the 2.0.5R CDROM image before ever burning it to gold. Furthermore, if we ever got a read/write CD9660 filesystem working, one could even "hot-patch" the image generated, doctoring it up a bit before finally taking the image and whapping it onto CD. That would be neat. Any interest out there? Jordan