From owner-freebsd-hackers Fri Mar 17 10: 4:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from stronghold.guild.ab.ca (kerberos.guild.ab.ca [209.91.118.68]) by hub.freebsd.org (Postfix) with ESMTP id 4C77537BF7A for ; Fri, 17 Mar 2000 10:04:03 -0800 (PST) (envelope-from davidc@stronghold.guild.ab.ca) Received: from localhost (davidc@localhost) by stronghold.guild.ab.ca (8.9.3/8.9.3) with ESMTP id KAA77654 for ; Fri, 17 Mar 2000 10:33:25 -0700 (MST) (envelope-from davidc@stronghold.guild.ab.ca) Date: Fri, 17 Mar 2000 10:33:25 -0700 (MST) From: Chad David To: freebsd-hackers@freebsd.org Subject: Bootable CD Question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a custom kernel that I need to have boot from a cd across as many machines as possible. I currently build the cd using scripts adapted from what is in src/release, (I now owe Poul-Henning more than one beer), and it boots every time in the lab, but people testing are reporting that it will not boot on even newer machines. I realize that having a cd boot in the PC world is an ify proposition, but does anybody have any tips on how how to burn a more "reliable" bootable cd. I am using mkisofs 1.12 with the following flags: mkisofs -b floppies/boot.flp -c floppies/boot.catalog -d -N -D -R -T -l -V '"Test"' -P '"Copyright"' -o ${BASE}/../../isoimages/image.iso ${BASE} and cdrecord 1.8 with the following flags: cdrecord speed=4 -v -data -multi dev=0,4,0 image.iso I realize this might be more apropriate on questions, but if I don't solve or at least have a better story about this problem very soon there may be one less application available for FreeBSD, and I am working very hard trying to prevent that :). Thanks. Chad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message