HOW TO MAKE A BOOTABLE Bluewhite64 Linux DVD ISO IMAGE To make a bootable Bluewhite64 install DVD, get into the top level Bluewhite64 directory (The one with ChangeLog.txt in it) and issue a command like this to build the ISO image in /tmp: mkisofs -o /tmp/bluewhite64-dvd.iso \ -R -J -A "Bluewhite64 Install" \ -hide-rr-moved \ -v -d -N \ -no-emul-boot -boot-load-size 32 -boot-info-table \ -sort isolinux/iso.sort \ -b isolinux/isolinux.bin \ -c isolinux/isolinux.boot \ -V "SlackDVD" . Use growisofs to burn the resulting DVD ISO: growisofs -speed=2 -dvd-compat -Z /dev/dvd=bluewhite64-dvd.iso If your burner is not /dev/dvd, replace the device with the one your system uses. I find discs burned at 2x are more reliable than ones burned at higher speeds, but you may see completely different results depending on media and burner type. The -dvd-compat option is also used so that a complete lead-out is written to the media for maximum compatibility. Or, you can burn directly from the Bluewhite64 tree to a DVD(-/+)R(W): growisofs \ -Z /dev/dvd \ -R -J -A "Bluewhite64 Install" \ -hide-rr-moved \ -v -d -N \ -no-emul-boot -boot-load-size 4 -boot-info-table \ -sort isolinux/iso.sort \ -b isolinux/isolinux.bin \ -c isolinux/isolinux.boot \ -dvd-compat \ -V "BW64DVD" . HOW TO MAKE A SET OF BOOTABLE / INSTALLABLE CDROMS This is a little bit more tricky. Step one will be to split the tree into portions that will fit on the media that you plan to burn to. The first disc must contain these directories: /isolinux/ /kernels/ /bluewhite64/ You'll need to make other /bluewhite64/ directories on discs 2, 3, and maybe more, moving some of the disc series from disc 1 to other discs to make things fit. It is also possible to split a series to make more efficient use of the CD media. See the README_SPLIT.TXT example and instructional file in this directory for details about how to set that up. The rest of the splitting up of discs is left as an exercise for the reader. To make the first (bootable) ISO, a command like this is used within the directory where the disc tree is. Let's say the directory is 'd1' and you wish to output the ISO image in /tmp: cd d1 mkisofs -o /tmp/bluewhite64-install-1.iso \ -R -J -A "Bluewhite64 Install CD 1" \ -hide-rr-moved \ -v -d -N \ -no-emul-boot -boot-load-size 4 -boot-info-table \ -sort isolinux/iso.sort \ -b isolinux/isolinux.bin \ -c isolinux/isolinux.boot \ -V "SlackCD1" . Making a non-bootable disc is similar. Just omit a few options: cd d2 mkisofs -o /tmp/bluewhite64-install-2.iso \ -R -J -A "Bluewhite64 Install CD 2" \ -hide-rr-moved \ -v -d -N \ -V "SlackCD2" . To burn an ISO image to CD-R(W), the cdrecord command is used. For complete instructions, see the man page ('man cdrecord'). On my own machine where the burner is /dev/cdrw, disc one would be burned with the following command: cat /tmp/bluewhite64-install-1.iso | cdrecord -v dev=/dev/cdrw speed=10 fs=8m -tao -eject -data - As before, it's possible to burn from the disc trees without the intermediate step of creating iso images by omitting the -o option to mkisofs and piping the output directly to cdrecord: cd d1 mkisofs \ -R -J -A "Bluewhite64 Install 1" \ -hide-rr-moved \ -v -d -N \ -no-emul-boot -boot-load-size 4 -boot-info-table \ -sort isolinux/iso.sort \ -b isolinux/isolinux.bin \ -c isolinux/isolinux.boot \ -V "SlackCD1" . | cdrecord -v dev=/dev/cdrw speed=10 fs=8m -tao -eject -data - ----- NOTE: The isolinux/isolinux.boot file will be created on the disc; it's not supposed to be in the source tree. I mention this only because so many people report the "missing" isolinux/isolinux.boot file as a bug. Modified for Bluewhite64 Linux by Arny. Based on README from Slackware.