From owner-freebsd-stable Fri Oct 1 6:44: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mel.alcatel.fr (mel.alcatel.fr [212.208.74.132]) by hub.freebsd.org (Postfix) with ESMTP id 4F368151F7 for ; Fri, 1 Oct 1999 06:43:52 -0700 (PDT) (envelope-from thierry.herbelot@alcatel.fr) Received: from aifhs2.alcatel.fr (mailhub.alcatel.fr [155.132.180.80]) by mel.alcatel.fr (ALCANET/SMTP) with ESMTP id OAA06260 for ; Fri, 1 Oct 1999 14:38:43 +0200 Received: from lune.telspace.alcatel.fr (lune.telspace.alcatel.fr [155.132.144.65]) by aifhs2.alcatel.fr (ALCANET/SMTP2) with ESMTP id PAA22667 for ; Fri, 1 Oct 1999 15:43:14 +0200 (MET DST) Received: from telss1 (telss1.telspace.alcatel.fr [155.132.51.4]) by lune.telspace.alcatel.fr (8.9.1a/8.9.1) with ESMTP id OAA05759 for ; Fri, 1 Oct 1999 14:34:35 +0200 (MEST) Received: from alcatel.fr by telss1 (8.8.8+Sun/SMI-SVR4) id OAA27856; Fri, 1 Oct 1999 14:47:24 +0200 (MET DST) Message-ID: <37F4ACC9.E169B4F9@alcatel.fr> Date: Fri, 01 Oct 1999 14:44:57 +0200 From: Thierry Herbelot Reply-To: thierry.herbelot@alcatel.fr Organization: ALCATEL CIT Nanterre X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 Cc: stable@FreeBSD.ORG Subject: what CD size for 3.3Rel CD1 ?(Was Re: Cdrecord problems to record 1 CD) References: <199910010716.AAA02259@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, what is the last word on how to write the full 3.3-Rel on a single CD (is it necessary to use a 80-minute CD ? - I've tried with a normal 74-min CD and the latest CD-RECORD18a29 under 3.3-Stable, and the resulting CD is not readable) TfH Mike Smith wrote: > > > On Tue, 28 Sep 1999, Jeremy McMillan wrote: > > > > > You need to read the spec for El-Torito. > > > > > > Basically, you need a boot image written to block 0 of your raw CD-R. That > > > boot image needs to know how to access your hardware (ie. load a kernel from > > > somewhere?). Bootable CDROM supporting BIOS just looks at the first block of > > > your CDROM and uses it *just* like the boot blocks from a floppy. > > > > 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 > > install CD. What you're describing seems to be the "multiple boot > > image configuration" that's discussed in the spec. The 3.2 and 3.3 CDs > > appear to be of the "single boot image configuration" variety. > > We just use mkisofs to creat the bootable images, same as everyone else. > > The problem, which was resolved this evening, seems to be that mkisofs > space-pads the copyright text in the boot catalog. If you have no > copyright text (like eg. the 3.2 image), it's all-0 and boots properly > on most systems. > > If you have copyright text, it's space-filled and terminated with a > single 0 byte, and this fails. > > Interestingly, the Windows NT CDROM has copyright text in the boot > catalog that is nul-filled, and this CDROM (probably the only benchmark > for bootable CDROMs in the industry) boots just fine, leading to the > conjecture that someone got sloppy in their BIOS code, which has been > widely replicated. > > In effect, it's the fact that Jordan was _more_ careful cutting the 3.3 > images that lead to this problem. Damn that quality control process. > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message