On Tuesday 17 April 2007 13:08, David Bolt wrote: > On Tue, 17 Apr 2007, Mike Diehl <[EMAIL PROTECTED]> wrote:- > >I'm trying to build a custom install CD, but I just can't get the > > resulting disk to boot. I want to be able to put a disk in a system, > > boot the system and come back to a fully configured machine. > > Does it have to be a CD, or would you be able to work with a DVD > instead? A DVD would be much more in keeping with the "insert disc, walk > away, come back to fully working system" desire so, if you can use a > DVD, check out makeSUSEdvd.
No, eventually, it WILL be a DVD. But if I can't get a CD to work, there's no point in burning a DVD, just yet. > My guess would be that kiso doesn't know how to recreate the necessary > bits to make the resultant image bootable. I agree. So, I've fallen back to cdrecord. Since I'm mastering this disk on a non-SUSE machine, I don't have makeSUSEdvd and downloading it led to some dependancy issues..... So, I extracted the "guts" of the script and continued on. So, here is the script I'm using....: =========================================== export BOOT_IMAGE=/home/mdiehl/newstart/raw/boot/loader mkisofs -v -V "SNL INSTALLER" -r -J -l -L -b "$BOOT_IMAGE/isolinux.bin" -c $BOOT_IMAGE/boot.cat \ -no-emul-boot -boot-load-size 4 -boot-info-table -graft-points -iso-level 4 -pad -allow-leading-dots -o b.iso ./raw =========================================== I've extracted the original CD into ./raw and I'm expecting to build a file called b.iso. (this is plan B, right?) When I run this script I get: =========================================== Warning: creating filesystem that does not conform to ISO-9660. Warning: Creating ISO-9660:1999 (version 2) filesystem. Warning: ISO-9660 filenames longer than 31 may cause buffer overflows in the OS. genisoimage 1.1.2 (Linux) Scanning ./raw Scanning ./raw/SLES-LICENSE Scanning ./raw/SLES-LICENSE/it Scanning ./raw/SLES-LICENSE/nl ... snip ... Scanning ./raw/yast/core9/suse Scanning ./raw/yast/core9/suse/setup Scanning ./raw/yast/core9/suse/setup/descr genisoimage: Uh oh, I cant find the boot catalog directory './raw/boot/loader'! =========================================== So it's complaining that it can't find the ./raw/boot/loader directory! But *I* can: workstation newstart # ls -la ./raw/boot/loader/ total 7056 dr-xr-xr-x 2 root root 4096 Jul 2 2004 . dr-xr-xr-x 3 root root 4096 Jul 2 2004 .. -r--r--r-- 1 root root 33043 Jul 2 2004 06400480.spl -r--r--r-- 1 root root 46989 Jul 2 2004 08000600.spl -r--r--r-- 1 root root 63015 Jul 2 2004 10240768.spl -r--r--r-- 1 root root 69943 Jul 2 2004 12801024.spl -r--r--r-- 1 root root 99571 Jul 2 2004 14001050.spl -r--r--r-- 1 root root 120205 Jul 2 2004 16001200.spl -r--r--r-- 1 root root 230400 Jul 2 2004 bootlogo -r--r--r-- 1 root root 4885034 Jul 2 2004 initrd -r--r--r-- 1 root root 15340 Jul 2 2004 isolinux.bin -r--r--r-- 1 root root 824 Jul 2 2004 isolinux.cfg -r--r--r-- 1 root root 1503455 Jul 2 2004 linux -r--r--r-- 1 root root 71744 Jul 2 2004 memtest -r--r--r-- 1 root root 510 Jul 2 2004 message So what am I doing wrong? Also, the command line above refers to a boot.cat file, but I've not been able to find one and don't know how to produce it. I've studied the makeSUSEdvd script and can't see how it creates this file, either. HELP! <grin> Mike. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
