From owner-freebsd-questions@FreeBSD.ORG Tue Nov 2 13:39:08 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D1CE16A4CF for ; Tue, 2 Nov 2004 13:39:08 +0000 (GMT) Received: from gaia.nimnet.asn.au (nimbin.lnk.telstra.net [139.130.45.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAC3143D4C for ; Tue, 2 Nov 2004 13:39:04 +0000 (GMT) (envelope-from smithi@nimnet.asn.au) Received: from localhost (smithi@localhost) by gaia.nimnet.asn.au (8.8.8/8.8.8R1.4) with SMTP id AAA20770; Wed, 3 Nov 2004 00:39:00 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Wed, 3 Nov 2004 00:39:00 +1100 (EST) From: Ian Smith To: freebsd-questions@freebsd.org In-Reply-To: <20041102120103.2C85216A4D6@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: "Michael C. Shultz" cc: Jonathon McKitrick Subject: Re: Question about ISO filesystems and CD-R's X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Nov 2004 13:39:08 -0000 On Tue, 2 Nov 2004 freebsd-questions-request@freebsd.org wrote: > Message: 18 > Date: Mon, 1 Nov 2004 18:43:02 -0800 > From: "Michael C. Shultz" > On Monday 01 November 2004 06:29 pm, Jonathon McKitrick wrote: > > Question: If I have an iso image smaller than the CD-R I am burning > > it to, what happens to that extra space? Is it useless? Can I burn > > another iso fs to it later, overwriting the first? > > > > jm > > The extra space on a CD-R is useless once burned, to burn another iso > over the first you need a CD-RW. Well yes, you'll need a CD-RW to overwrite the first (after erasure), but you can keep on adding further ISO images to a CD-R (or CD-RW) until it's full, using mkisofs + burncd at least. Very handy here for certain types of backups, especially on a remote box visited weekly. My cdappend script's full of paranoid parameter and error checking and such, but is based on this simple and likely more illustrative one: #!/bin/sh # original googled at http://www.opennet.ru/base/sys/cd_session.txt.html # indecipherable Russian (including author's name) except for: if [ "$1" = "-n" ]; then echo -- New disk -- mkisofs -J -jcharset koi8-r $2 | burncd -m data - fixate else echo -- Add session -- msinfo=`burncd msinfo 2>&1 | sed "s/ //g"` sleep 3 mkisofs -M /dev/acd0c -C $msinfo -J -jcharset koi8-r -o tmp.iso $1 burncd -m data tmp.iso fixate rm tmp.iso fi It probably depends on the burner, but I found I had to add the below to reliably reset the device after burning on a 4.8-RELEASE system. YMMV. echo -n "CD " # eject / inject needed _after_ session (or reset?) cdcontrol -f $dev eject; echo -n "ejected .. " cdcontrol -f $dev close; echo "closed" sleep 10 # 5 secs not enough to spin up ready for 'info' cdcontrol -f $dev info Cheers, Ian