From owner-freebsd-hardware Fri Aug 2 19:41:27 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id TAA18967 for hardware-outgoing; Fri, 2 Aug 1996 19:41:27 -0700 (PDT) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA18956 for ; Fri, 2 Aug 1996 19:41:21 -0700 (PDT) Received: from localhost.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.7.5/8.7.3) with SMTP id WAA01978; Fri, 2 Aug 1996 22:40:03 -0400 (EDT) Message-Id: <199608030240.WAA01978@whizzo.transsys.com> X-Authentication-Warning: whizzo.transsys.com: Host localhost.transsys.com [127.0.0.1] didn't use HELO protocol To: Darryl Okahata cc: freebsd-hardware@freebsd.org From: "Louis A. Mamakos" Subject: Re: h/w requirements for CD-R writing? References: <199608030212.AA085678338@hpnmhjw.sr.hp.com> In-reply-to: Your message of "Fri, 02 Aug 1996 19:12:17 PDT." <199608030212.AA085678338@hpnmhjw.sr.hp.com> Date: Fri, 02 Aug 1996 22:40:03 -0400 Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just curious, but is there any reason why you couldn't create the CD image on a bulk sequential medium, like a tape? I believe that the mkisofs program doesn't do random I/O, just sequential, so this ought to work, right? You might have to burn the CD in "slow" mode given the transfer rate of the DAT drive. louie > Note that burning a CD is a disk-space-intensive, two-step process: > (1) you create an CDROM image file from the files that you want to go > onto the CD, and (2) you burn the CD using the image file (and NOT the > original directory tree). The bottom line is that you'll need again as > much disk space as that used to hold the files that you want to place > onto the CD. In a worst-case scenario (a completely full CDROM), you'll > need 650MB+650MB==> ~1.3GB of disk space. However, if you're only > placing ~400MB of files onto the CDROM, you'll only need around ~800MB > of space.