From owner-freebsd-hackers Thu Jul 25 12:53:48 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA26695 for hackers-outgoing; Thu, 25 Jul 1996 12:53:48 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA26679 for ; Thu, 25 Jul 1996 12:53:35 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id VAA19901; Thu, 25 Jul 1996 21:53:19 +0200 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA23914; Thu, 25 Jul 1996 21:53:14 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id VAA22917; Thu, 25 Jul 1996 21:39:43 +0200 (MET DST) From: J Wunsch Message-Id: <199607251939.VAA22917@uriah.heep.sax.de> Subject: Re: Bootable CD roms To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Thu, 25 Jul 1996 21:39:43 +0200 (MET DST) Cc: erich@lodgenet.com (Eric L. Hernes) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199607251315.IAA03601@jake.lodgenet.com> from "Eric L. Hernes" at "Jul 25, 96 08:15:26 am" 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 X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Eric L. Hernes wrote: > I understood that the bios would search the CD-ROM for the El Torito > signature before considering booting. Yep, no problem. > Stop me if I'm wrong here, but here's what I was expecting > (following the 4-page thing): Thou shalt not follow it. :) > > 1) take boot.flp, or any bootable (FBSD) floppy > 2) create BVD.BIN and BOOTCAT.BIN with dd, emacs, beav, mkisofs, whatever... > 3) rename boot.flp OSBOOT.IMG Nah, we've got the sources. The above really only obfuscates things, it's better to put this into `biosboot', or create a new boot subdir for `cdboot'. > >No need to hack mkisofs in the first place. We do already have the > >tool to merge the bootcode into an existing isofs. It's called dd(1). We perhaps need to tweak it, btw., since we are required to create a ``boot record volume descriptor'' which must follow the ``primary volume descriptor''. > Well, a simple hack. It looks like the spec wants > `EL TORITO SPECIFICATION' in place of `FreeBSD' in the BVD.BIN > amongst placing the proper links and stuff on the iso9660. Nope, you're confusing the primary volume descriptor (where all the optional strings go to) with the (not yet existent) boot record volume descriptor. I haven't looked yet, but i assume that the current isofs layout from mkisofs(1) has just the primary volume descriptor, immediately followed by the terminate volume descriptor. -- 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. ;-)