Index of /ftp/mirror/Slackware/isolinux

Icon  Name                    Last modified      Size  Description
[DIR] Parent Directory - [TXT] f2.txt 19-Jun-2004 19:52 1.0K [TXT] f3.txt 06-Sep-2005 18:09 1.3K [   ] initrd.img 08-Sep-2005 10:19 2.5M [   ] iso.sort 18-Jan-2003 00:02 50 [   ] isolinux.bin 01-Aug-2005 11:18 9.8K [   ] isolinux.cfg 06-Sep-2005 18:07 2.8K [TXT] message.txt 09-Jul-2005 23:37 897 [   ] network.dsk 05-Jun-2005 23:58 1.4M [   ] pcmcia.dsk 06-Jun-2005 00:01 1.4M [DIR] sbootmgr/ 03-Jun-2003 20:58 - [   ] setpkg 01-May-2005 20:53 2.8K

To make a bootable Slackware install CD, get into the top level Slackware
directory (The one with ChangeLog.txt in it) and issue a command like this
to build the ISO image in /tmp:

mkisofs -o /tmp/slackware.iso \
-R -J -V "Slackware Install" \
-x ./bootdisks \
-x ./extra \
-x ./slackware/kde \
-x ./slackware/kdei \
-x ./slackware/t \
-x ./pasture \
-x ./patches \
-x ./rootdisks \
-x ./source \
-x ./zipslack \
-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 \
-A "Slackware Install CD" . 

Then use 'cdrecord' to burn it.  (See 'man cdrecord')

Notice that to fit the install image on one CD, you must exclude KDE and TeX:

-x ./slackware/kde \
-x ./slackware/kdei \
-x ./slackware/t \

These can go on a second CD.  If you are planning to burn the ISO image onto
a DVD, the entire tree should fit and you can leave out all the -x exclude

   The isolinux/isolinux.boot file will be created on the CD;  it's not
   supposed to be in the source tree.  I mention this only because so many
   people reported the "missing" isolinux/isolinux.boot file as a bug.

  I don't know how to create a bootable Slackware ISO on operating systems
  other than Linux, but it should be easy to burn the Linux-created ISO with
  most CD burning software on any operating system.

  UPDATE:  I've now been informed that there's a Windows version of mkisofs
  available from if you want
  to try to make the ISO image under Windows.  I haven't tried this.

  Techincally the --boot-load-size should be a lot bigger, like 20 or so
  in order to hold the isolinux.bin boot block.  However, setting it to
  4 causes it to load on more BIOSes.  I don't know why, but I've had so
  many people report this to me that I'm inclined to believe it.  But, if
  the resulting discs don't boot in your machine and you find that using
  a more correct value here fixes it, please let me know!  If it's going
  to be broken for some BIOSes either way, I'd rather be correct.