From owner-freebsd-stable@FreeBSD.ORG Wed Jan 25 02:07:06 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 82C9116A420 for ; Wed, 25 Jan 2006 02:07:05 +0000 (GMT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: from gndrsh.dnsmgr.net (gndrsh.dnsmgr.net [205.238.40.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4784C43D4C for ; Wed, 25 Jan 2006 02:07:04 +0000 (GMT) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id SAA76947; Tue, 24 Jan 2006 18:06:52 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200601250206.SAA76947@gndrsh.dnsmgr.net> In-Reply-To: <20060125013542.GA43885@ns.museum.rain.com> from James Long at "Jan 24, 2006 05:35:42 pm" To: list@museum.rain.com (James Long) Date: Tue, 24 Jan 2006 18:06:52 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: How to get custom release CD to boot without floppies? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2006 02:07:06 -0000 ... > Finally, I made an ISO image: > > cd CHROOTDIR > export CHROOTDIR="." > mkisofs -d -D -N -R -T -V "FreeBSD6.0-RELEASE" \ > -P "Test Distribution" \ > -o ~/tinn.iso -b floppies/boot.flp \ > -c floppies/boot.catalog $CHROOTDIR/R/cdrom/disc1 > > # /* -V is your CD name */ > # /* -P is for some comments */ > # /* -o is your image name */ > # /* -b and -c should be left how it is. It's set for auto boot. These paths should not be a full path */ Big concern here is that the -b and -c are NOT part of the isoimage burn requested. This is most likely your problem, mkisofs well actually create and write the boot.catalog file, and I am almost certain that it must appear on the cdrom at that same relative location (ie, the arg to mkisofs should almost always be . ) -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net