Difference between revisions of "ISOLINUX"

From Syslinux Wiki
Jump to: navigation, search
 
(Wiki formatting. Minor rewording. Add resources' links.)
 
(20 intermediate revisions by 11 users not shown)
Line 1: Line 1:
==What is ISOLINUX?==
+
== What is ISOLINUX? ==
ISOLINUX is a boot loader for Linux/i386 that operates off ISO 9660/El Torito CD-ROMs in "no emulation" mode. This avoids the need to create an "emulation disk image" with limited space (for "floppy emulation") or compatibility problems (for "hard disk emulation".)  
+
ISOLINUX is a boot loader for Linux/i386 that operates off  
 +
{{nowrap|ISO 9660/El Torito}} CD-ROMs in {{nowrap|"no emulation"}} mode.  
 +
This avoids the need to create an "emulation disk image" with limited space  
 +
(for "floppy emulation") or compatibility problems (for "hard disk emulation").
  
==How Can I Make a Bootable CD With ISOLINUX?==
+
== How Can I Make a Bootable CD With ISOLINUX? ==
Make sure you have a recent enough version of mkisofs. I recommend mkisofs 1.13 (distributed with cdrecord 1.9), but 1.12 might work as well (not tested.)  
+
* Make sure you have a recent-enough version of mkisofs or equivalent. <!--
 +
--> Regarding mkisofs, version 1.13 or newer is recommended <!--
 +
--> (distributed with [http://cdrecord.org cdrecord]&nbsp;1.9&nbsp;), <!--
 +
--> but 1.12 might work as well (not tested). <!--
 +
--> Binary versions for Windows can be found on the web.  <!--
 +
-->  <!--
 +
-->
 +
* [[Download]] Syslinux  <!--
 +
-->  <!--
 +
-->
 +
* Create a directory called "CD_root". This is the ISO image master file tree  <!--
 +
-->  <!--
 +
-->
 +
** Copy all files you want to have on the CD into this directory  <!--
 +
-->  <!--
 +
-->
 +
* Create a directory called "<tt>isolinux</tt>" underneath the directory "CD_root"  <!--
 +
-->  <!--
 +
-->
 +
** Copy "<tt>[bios/]core/isolinux.bin</tt>" from the Syslinux archive  <!--
 +
-->  <!--
 +
-->
 +
** {{V|5.00+}}For version 5.00 or newer, also copy <!--
 +
--> {{nowrap|1="<tt>[bios/]com32/elflink/ldlinux/[[Library_modules|ldlinux.c32]]</tt>"}} <!--
 +
--> from the Syslinux archive  <!--
 +
-->  <!--
 +
-->
 +
** Create "[[#Path_resolution|isolinux.cfg]]" (see [[isolinux.cfg|example]]) <!--
 +
-->  <!--
 +
-->
 +
* Create directories "images" and "kernel" underneath the directory "CD_root"  <!--
 +
-->  <!--
 +
-->
 +
** Copy any floppy images you want to boot into "images"  <!--
 +
-->  <!--
 +
-->
 +
** Copy "<tt>[bios/]memdisk/memdisk</tt>" from the Syslinux archive into "kernel"  <!--
 +
-->  <!--
 +
-->
 +
* Use the following command to create your ISO image:  <!--
 +
-->  <!--
 +
-->
 +
{|
 +
|
 +
<pre>
 +
mkisofs -o output.iso \
 +
  -b isolinux/isolinux.bin -c isolinux/boot.cat \
 +
  -no-emul-boot -boot-load-size 4 -boot-info-table \
 +
  CD_root
 +
</pre>
 +
|}
 +
The file ''boot.cat'' will be automatically created.
  
To create an image, create a directory called "isolinux" (or, if you prefer, "boot/isolinux") underneath the root directory of your ISO image master file tree. Copy isolinux.bin, a config file called "isolinux.cfg" (see syslinux.doc for details on the configuration file), and all necessary files (kernels, initrd, display files, etc.) into this directory, then use the following command to create your ISO image (add additional options as appropriate, such as -J or -R):
+
=== Notes about building ===
    mkisofs -o output.iso \
+
<span id="note1"></span>
      -b isolinux/isolinux.bin -c isolinux/boot.cat \
+
ISOLINUX:
      -no-emul-boot -boot-load-size 4 -boot-info-table \
+
* only uses ''plain'' ISO 9660 filenames, <!--
      root-of-iso-tree
+
--> i.e. it does not support Rock Ridge<!--
 +
--> <sup><small>&#91;[[#lnote1|1]]&#93;</small></sup>, <!--
 +
--> or Joliet filenames. <!--
 +
--> It can still be used on a disc that uses Rock Ridge and/or Joliet extensions, of course. <!--
 +
--> Under Linux, you can verify the plain filenames by mounting with <!--
 +
--> the {{nowrap|1="<code>-o norock,nojoliet</code>"}} option of the mount command.   <!--
 +
-->  <!--
 +
-->
 +
* supports ''long'' (level 2) ISO 9660 plain filenames, <!--
 +
--> so if compatibility with {{nowrap|short-names-only}} operating systems like {{nowrap|MS-DOS}} <!--
 +
--> is not an issue, you can use the "<tt>-l</tt>" or <!--
 +
--> {{nowrap|"<code>-iso-level 2</code>"}} option of <!--
 +
--> mkisofs to generate long (up to 31 characters) plain filenames.   <!--
 +
-->  <!--
 +
-->
 +
* '''does not support''' discontiguous files, interleaved mode, <!--
 +
--> or logical block and sector sizes other than 2048&nbsp;bytes. <!--
 +
--> This should normally not be a problem.  <!--
 +
-->  <!--
 +
-->
  
(If you named the directory boot/isolinux that should of course be -b boot/isolinux/isolinux.bin -c boot/isolinux/boot.cat.)
+
By default, ISOLINUX is built in two versions; one of them with extra debugging messages enabled.
 +
If you are having problems with ISOLINUX,
 +
please try out the debugging version {{nowrap|(<tt>isolinux-debug.bin</tt>)}}
 +
and [[Contact|report the results]].
  
ISOLINUX resolves pathnames the following way:
+
=== Isohybrid ===
A pathname consists of names separated by slashes, Unix-style.
+
Although disk storage devices are usually booted via SYSLINUX,  
A leading slash means it searches from the root directory; otherwise the search is from the isolinux directory (think of this as the "current directory".)  
+
there is an [[isohybrid]] feature, which makes the ISO bootable from such devices
. and .. in pathname searches are not supported.
+
(e.g. USB stick), in addition to DVD.
The maximum length of any pathname is 255 characters.  
+
  
Note that ISOLINUX only uses the "plain" ISO 9660 filenames, i.e. it does not support Rock Ridge or Joliet filenames. It can still be used on a disk which uses Rock Ridge and/or Joliet extensions, of course. Under Linux, you can verify the plain filenames by mounting with the "-o norock,nojoliet" option to the mount command. Note, however, that ISOLINUX does support "long" (level 2) ISO 9660 plain filenames, so if compatibility with short-names-only operating systems like MS-DOS is not an issue, you can use the "-l" or "-iso-level 2" option to mkisofs to generate long (up to 31 characters) plain filenames.  
+
== Path resolution ==
 +
ISOLINUX resolves pathnames in the following way:
 +
* A pathname consists of names separated by slashes, Unix-style.  
 +
* A leading slash means it searches from the root directory of the ISO9660 filesystem; <!--
 +
--> otherwise the search is performed from the isolinux directory <!--
 +
--> (think of this as the "current [[working directory]]").
 +
* The maximum length of any pathname is 255 characters.
  
ISOLINUX does not support discontiguous files, interleaved mode, or logical block and sector sizes other than 2048. This should normally not be a problem.  
+
Support for relative notation directory paths using dots (periods),  
 +
such as {{nowrap|"<tt>.</tt>"}} and {{nowrap|"<tt>..</tt>"}},  
 +
was initially introduced in version 4.02 and improved in 4.06.  
  
ISOLINUX is by default built in two versions, one version with extra debugging messages enabled. If you are having problems with ISOLINUX, I would greatly appreciate if you could try out the debugging version (isolinux-debug.bin) and let me know what it reports.
+
ISOLINUX will search for the config file directory in the order  
NOTE: ISOLINUX will search for the config file directory in the order /boot/isolinux, /isolinux, /. The first directory that exists is used, even if it contains no files. Therefore, please make sure that these directories don't exist if you don't want ISOLINUX to use them.  
+
<tt>/boot/isolinux</tt>, <tt>/isolinux</tt>, <tt>/</tt>.  
  
==Can I boot other operating systems with ISOLINUX?==
+
{{V|-3.86}}The first directory that exists is used,  
Starting in version 1.65, ISOLINUX supports booting disk images of other operating systems. However, this feature depends on BIOS functionality which is apparently broken in a very large number of BIOSes. Therefore, this may not work on any particular system. No direct workaround is possible; if you find that it doesn't work please complain to your vendor and indicate that "BIOS INT 13h AX=4C00h fails." Note that you can use MEMDISK as an alternative; MEMDISK is not affected by this problem, but limits the size of the disk images, since it has to load them into memory.  
+
even if it contains no files.  
 +
Therefore, please make sure that these directories do not exist
 +
if you don't want ISOLINUX to use them.
  
To boot DOS, or other real-mode operating systems (protected-mode operating systems may or may not work correctly), using ISOLINUX, you need to prepare a disk image (usually a floppy image, but a hard disk image can be used on most systems) with the relevant operating system. This file should be included on the CD-ROM in the /isolinux directory, and have a .img extension. The .img extension does not have to be specified on the command line, but has to be explicitly specified if used in a kernel statement in isolinux.cfg.  
+
{{V|4.02+}}ISOLINUX will also search for the config file
 +
in the respective SYSLINUX directories,
 +
and will search for either
 +
<tt>isolinux.cfg</tt> or <tt>syslinux.cfg</tt> files.
 +
The {{nowrap|"<tt>/[boot/]isolinux/</tt>"}} directories
 +
and the <tt>isolinux.cfg</tt> file will take precedence over their
 +
respective <tt>syslinux</tt> alternatives when using ISOLINUX to boot.
 +
In other words, {{nowrap|"<tt>/[boot/]syslinux/</tt>"}} and <tt>syslinux.cfg</tt>
 +
are now generic terms and valid when booting with ISOLINUX.
 +
 
 +
See also "[[Working directory]]", "[[Configuration location and name]]"
 +
and Syslinux [[config]]uration file.
 +
 
 +
Tip:<br />
 +
Since {{V|4.06+}}, locating the bootloader files under the
 +
{{nowrap|"<tt>/[boot/]syslinux/</tt>"}} directory (instead of using the
 +
{{nowrap|"<tt>/[boot/]isolinux/</tt>"}} directory) can simplify the procedure
 +
to go from ISOLINUX to SYSLINUX
 +
(e.g. to put the content of a bootable ISO image onto a SYSLINUX USB drive):<br />
 +
<!-- Do not use "pre" tags for the following paragraph / command -->
 +
<!-- as "pre" does not parse wiki markup -->
 +
{|
 +
|
 +
mkisofs -o output.iso \
 +
  -b '''sys'''linux/isolinux.bin -c '''sys'''linux/boot.cat \
 +
  -no-emul-boot -boot-load-size 4 -boot-info-table \
 +
  CD_root
 +
|}
 +
<!-- -->
 +
 
 +
== Can I boot other operating systems with ISOLINUX? ==
 +
 
 +
( Note: In [[Syslinux_4_Changelog#Changes_in_4.05|Syslinux 4.05]],
 +
the ".img" support has been removed from ISOLINUX.
 +
Instead, MEMDISK is suggested for this purpose.)
 +
 
 +
{{V|1.65-4.04}}Starting in version {{nowrap|1=1.65<sup><small>[up to 4.04]</small></sup>,}}
 +
ISOLINUX supports booting disk images of other operating systems.
 +
However, this feature depends on BIOS functionality which is apparently
 +
broken in a very large number of BIOSes.
 +
Therefore, this may not work on any particular system.
 +
No direct workaround is possible;
 +
if you find that it doesn't work,
 +
please complain to your vendor and indicate that "BIOS INT 13h AX=4C00h fails".
 +
Note that you can use MEMDISK as a recommended alternative;
 +
MEMDISK is not affected by this problem, but limits the size of the disk images,
 +
since it has to load them into memory.
 +
 
 +
To boot DOS, or other real-mode operating systems  
 +
(protected-mode operating systems may or may not work correctly)  
 +
using ISOLINUX, you need to prepare a disk image  
 +
(usually a floppy image, but a hard disk image can be used on most systems)  
 +
with the relevant operating system.  
 +
This file should be included on the CD-ROM in the <tt>/isolinux/</tt>
 +
(or <tt>/syslinux/</tt>) directory,  
 +
and have an ".img" extension.  
 +
The ".img" extension does not have to be specified on the command line,  
 +
but has to be explicitly specified if used in a kernel statement in isolinux.cfg.  
  
 
For a floppy image, the size of the image should be exactly one of the following:  
 
For a floppy image, the size of the image should be exactly one of the following:  
Line 36: Line 178:
 
   2,949,120 bytes  2880K floppy (enhanced 3.5")  
 
   2,949,120 bytes  2880K floppy (enhanced 3.5")  
  
Any other size is assumed to be a hard disk image. In order to work on as many systems as possible, a hard disk image should have exactly one partition, marked active, that covers the entire size of the disk image file. Even so, hard disk images are not supported on all BIOSes.  
+
Any other size is assumed to be a hard disk image.  
 +
In order to work on as many systems as possible,  
 +
a hard disk image should have exactly one partition, marked active,  
 +
that covers the entire size of the disk image file.  
 +
Even so, hard disk images are not supported on all BIOSes.
  
==ISOLINUX and Windows install disks==
+
== ISOLINUX and Windows install disks ==
ISOLINUX supports the use of so-called "CD-ROM boot sectors", which are used primarily by Microsoft Windows NT (including 2000 and XP.) "CD-ROM boot sectors" need to end in the extension .bin. Some people have used this together with Windows install disks to create combination Windows/Linux install CDs.  
+
ISOLINUX supports the use of {{nowrap|so-called}} "CD-ROM boot sectors",  
 +
which are used primarily by Microsoft Windows NT (including 2000 and XP).
 +
"CD-ROM boot sectors" need to end in the extension ".bin".  
 +
Some people have used this together with Windows install disks  
 +
to create {{nowrap|Windows/Linux}} combination install CDs.  
  
Please see the following message from the SYSLINUX mailing list for some tips:  
+
Please see the following message  
 +
(and some others around the same time)
 +
from the SYSLINUX mailing list for some tips:  
 
http://www.zytor.com/pipermail/syslinux/2002-October/001135.html  
 
http://www.zytor.com/pipermail/syslinux/2002-October/001135.html  
  
==What to do when nothing works...==
+
== What to do when nothing works... ==
Unfortunately, in what seems to be part for the course when dealing with contemporary BIOSes, there are still a fair number of (mostly older) systems on which ISOLINUX simply will not work. On those systems, you may want to try Smart BootManager, a boot floppy which contains a standalone El Torito stack.
+
Unfortunately, in what seems to be par for the course when dealing with contemporary BIOSes,  
 +
there are still a fair number of (mostly older) systems on which ISOLINUX simply will not work.  
 +
On those systems, you may want to try [http://btmgr.sourceforge.net/ Smart BootManager],  
 +
a boot floppy which contains a standalone El Torito stack.
 +
 
 +
== Resources ==
 +
* [http://download.intel.com/support/motherboards/desktop/sb/specscdrom.pdf “El Torito” Bootable CD-ROM Format Specification]
 +
* [http://littlesvr.ca/isomaster/eltoritosuppl.php EL Torito Specification Supplement] from Andrew Smith.
 +
* [https://www.ecma-international.org/publications/standards/Ecma-119-arch.htm ECMA-119], also approved as ISO 9660.
 +
* https://en.wikipedia.org/wiki/ISO_9660
 +
 
 +
== Notes ==
 +
 
 +
* <span id="lnote1">1</span>. <sup><small>[[#note1|&#94;]]</small></sup> <!--
 +
--> {{v|6.03+}} ISOLINUX supports Rock Ridge (too) since version 6.03. <!--

Latest revision as of 08:18, 18 January 2019

What is ISOLINUX?

ISOLINUX is a boot loader for Linux/i386 that operates off ISO 9660/El Torito CD-ROMs in "no emulation" mode. This avoids the need to create an "emulation disk image" with limited space (for "floppy emulation") or compatibility problems (for "hard disk emulation").

How Can I Make a Bootable CD With ISOLINUX?

  • Make sure you have a recent-enough version of mkisofs or equivalent. Regarding mkisofs, version 1.13 or newer is recommended (distributed with cdrecord 1.9 ), but 1.12 might work as well (not tested). Binary versions for Windows can be found on the web.
  • Download Syslinux
  • Create a directory called "CD_root". This is the ISO image master file tree
    • Copy all files you want to have on the CD into this directory
  • Create a directory called "isolinux" underneath the directory "CD_root"
    • Copy "[bios/]core/isolinux.bin" from the Syslinux archive
    • [5.00+] For version 5.00 or newer, also copy "[bios/]com32/elflink/ldlinux/ldlinux.c32" from the Syslinux archive
    • Create "isolinux.cfg" (see example)
  • Create directories "images" and "kernel" underneath the directory "CD_root"
    • Copy any floppy images you want to boot into "images"
    • Copy "[bios/]memdisk/memdisk" from the Syslinux archive into "kernel"
  • Use the following command to create your ISO image:
mkisofs -o output.iso \
   -b isolinux/isolinux.bin -c isolinux/boot.cat \
   -no-emul-boot -boot-load-size 4 -boot-info-table \
   CD_root

The file boot.cat will be automatically created.

Notes about building

ISOLINUX:

  • only uses plain ISO 9660 filenames, i.e. it does not support Rock Ridge [1], or Joliet filenames. It can still be used on a disc that uses Rock Ridge and/or Joliet extensions, of course. Under Linux, you can verify the plain filenames by mounting with the "-o norock,nojoliet" option of the mount command.
  • supports long (level 2) ISO 9660 plain filenames, so if compatibility with short-names-only operating systems like MS-DOS is not an issue, you can use the "-l" or "-iso-level 2" option of mkisofs to generate long (up to 31 characters) plain filenames.
  • does not support discontiguous files, interleaved mode, or logical block and sector sizes other than 2048 bytes. This should normally not be a problem.

By default, ISOLINUX is built in two versions; one of them with extra debugging messages enabled. If you are having problems with ISOLINUX, please try out the debugging version (isolinux-debug.bin) and report the results.

Isohybrid

Although disk storage devices are usually booted via SYSLINUX, there is an isohybrid feature, which makes the ISO bootable from such devices (e.g. USB stick), in addition to DVD.

Path resolution

ISOLINUX resolves pathnames in the following way:

  • A pathname consists of names separated by slashes, Unix-style.
  • A leading slash means it searches from the root directory of the ISO9660 filesystem; otherwise the search is performed from the isolinux directory (think of this as the "current working directory").
  • The maximum length of any pathname is 255 characters.

Support for relative notation directory paths using dots (periods), such as "." and "..", was initially introduced in version 4.02 and improved in 4.06.

ISOLINUX will search for the config file directory in the order /boot/isolinux, /isolinux, /.

[-3.86] The first directory that exists is used, even if it contains no files. Therefore, please make sure that these directories do not exist if you don't want ISOLINUX to use them.

[4.02+] ISOLINUX will also search for the config file in the respective SYSLINUX directories, and will search for either isolinux.cfg or syslinux.cfg files. The "/[boot/]isolinux/" directories and the isolinux.cfg file will take precedence over their respective syslinux alternatives when using ISOLINUX to boot. In other words, "/[boot/]syslinux/" and syslinux.cfg are now generic terms and valid when booting with ISOLINUX.

See also "Working directory", "Configuration location and name" and Syslinux configuration file.

Tip:
Since [4.06+] , locating the bootloader files under the "/[boot/]syslinux/" directory (instead of using the "/[boot/]isolinux/" directory) can simplify the procedure to go from ISOLINUX to SYSLINUX (e.g. to put the content of a bootable ISO image onto a SYSLINUX USB drive):

mkisofs -o output.iso \
  -b syslinux/isolinux.bin -c syslinux/boot.cat \
  -no-emul-boot -boot-load-size 4 -boot-info-table \
  CD_root

Can I boot other operating systems with ISOLINUX?

( Note: In Syslinux 4.05, the ".img" support has been removed from ISOLINUX. Instead, MEMDISK is suggested for this purpose.)

[1.65-4.04] Starting in version 1.65[up to 4.04], ISOLINUX supports booting disk images of other operating systems. However, this feature depends on BIOS functionality which is apparently broken in a very large number of BIOSes. Therefore, this may not work on any particular system. No direct workaround is possible; if you find that it doesn't work, please complain to your vendor and indicate that "BIOS INT 13h AX=4C00h fails". Note that you can use MEMDISK as a recommended alternative; MEMDISK is not affected by this problem, but limits the size of the disk images, since it has to load them into memory.

To boot DOS, or other real-mode operating systems (protected-mode operating systems may or may not work correctly) using ISOLINUX, you need to prepare a disk image (usually a floppy image, but a hard disk image can be used on most systems) with the relevant operating system. This file should be included on the CD-ROM in the /isolinux/ (or /syslinux/) directory, and have an ".img" extension. The ".img" extension does not have to be specified on the command line, but has to be explicitly specified if used in a kernel statement in isolinux.cfg.

For a floppy image, the size of the image should be exactly one of the following:

 1,222,800 bytes   1200K floppy (standard 5.25") 
 1,474,560 bytes   1440K floppy (standard 3.5") 
 2,949,120 bytes   2880K floppy (enhanced 3.5") 

Any other size is assumed to be a hard disk image. In order to work on as many systems as possible, a hard disk image should have exactly one partition, marked active, that covers the entire size of the disk image file. Even so, hard disk images are not supported on all BIOSes.

ISOLINUX and Windows install disks

ISOLINUX supports the use of so-called "CD-ROM boot sectors", which are used primarily by Microsoft Windows NT (including 2000 and XP). "CD-ROM boot sectors" need to end in the extension ".bin". Some people have used this together with Windows install disks to create Windows/Linux combination install CDs.

Please see the following message (and some others around the same time) from the SYSLINUX mailing list for some tips: http://www.zytor.com/pipermail/syslinux/2002-October/001135.html

What to do when nothing works...

Unfortunately, in what seems to be par for the course when dealing with contemporary BIOSes, there are still a fair number of (mostly older) systems on which ISOLINUX simply will not work. On those systems, you may want to try Smart BootManager, a boot floppy which contains a standalone El Torito stack.

Resources

Notes

  • 1. ^ [6.03+] ISOLINUX supports Rock Ridge (too) since version 6.03.