From owner-freebsd-current Thu Mar 13 00:51:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA14830 for current-outgoing; Thu, 13 Mar 1997 00:51:18 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id AAA14816 for ; Thu, 13 Mar 1997 00:51:12 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA22963 for freebsd-current@FreeBSD.ORG; Thu, 13 Mar 1997 09:51:10 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id JAA03167; Thu, 13 Mar 1997 09:43:17 +0100 (MET) Message-ID: <19970313094317.OQ49355@uriah.heep.sax.de> Date: Thu, 13 Mar 1997 09:43:17 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@FreeBSD.ORG Subject: Re: worm0 and cd imaging References: <199703130421.XAA02473@pent.ibm.net> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Jimbo Bahooli on Mar 12, 1997 23:01:57 -0600 Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Jimbo Bahooli wrote: > Thanks, I'm going to make the images now with 'dd if=/dev/cd0a of=cd.img' > tested it out slightly and it worked great. If you're using dd(1), you might also use bs=64k. This slightly reduces the overhead. With a reasonably fast CD-ROM drive, i think you can even burn directly from a CD, but i haven't tested this. > What are the exact commands > you use to burn it? Does the burncdfs.sh do it right... I think quite a number of people are using it. I'm using another but fairly similar script (the one in examples is Jordan's). If you feel adventurous, and you know how to use Tcl/Tk (i don't), go and write a better user interface around mkisofs, and the burncd script. > But now that this hurdle is > jumped, I can't wait for my Advansys scsi card to be supported. Even with > -current and the SCSI branch my version is not supported yet... There's one solution to this: go and write the driver. :-] -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)