From owner-freebsd-stable Tue Sep 28 22:13:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id D260414EE4 for ; Tue, 28 Sep 1999 22:13:09 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA26226; Tue, 28 Sep 1999 22:12:43 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Ed Watkeys Cc: stable@FreeBSD.ORG Subject: Re: Cdrecord problems to record 1 CD In-reply-to: Your message of "Tue, 28 Sep 1999 23:50:43 EDT." Date: Tue, 28 Sep 1999 22:12:43 -0700 Message-ID: <26222.938581963@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is not the most helpful response. At your urging, I read the El > Torito spec, and what you're saying above does not appear to be true > of the Walnut Creek 3.2 install CD I have or the ISO image for the 3.3 All bootable Walnut Creek CDROM FreeBSD CDs use the El Torrito boot hack to accomplish their purpose. It's the -b flag to mkisofs. > Reading through the mkisofs man page, it that that the ISO image > should contain all of the information necessary to make this CD-R > bootable. Has anyone actually booted off of a CD-R that they've burnt > from the September 17, 1999, image? The disc works fine for installing Yes. However, it seems to have problems with ATAPI CDROM drives (where it works fine with SCSI) and we're still scratching our heads over that one. What works for one should work for both, but no. It would be a lot easier to debug if it just plain didn't work for *anyone*, you know? :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message