2 files changed, 30 insertions, 16 deletions
@@ -8,7 +8,16 @@ Changes in 3.32:
* MEMDISK: Turn on EDD support by default.
* MEMDISK: Try to work on some machines on which it would not
work when there was no floppy drive in the system.
- * Simple menu system: fix serial console support (broken in 3.30).
+ * Simple menu system: fix serial console support (broken in
+ * SYSLINUX: Support subdirectories. Like ISOLINUX, the
+ "current directory" is the directory in which syslinux.cfg
+ is found; this is searched for in the sequence
+ /boot/syslinux, /syslinux, /. As a side benefit, label names
+ like "linux-2.6.18" and "linux-2.6.19" are now supported.
+ To install ldlinux.sys in a subdirectory, pass the -d
+ directory option to the SYSLINUX installer.
Changes in 3.31:
* The simple menu system (menu.c32 and vesamenu.c32) now
diff --git a/syslinux.doc b/syslinux.doc
index 356c2898..9fc0ee6f 100644
@@ -36,9 +36,9 @@ In order to create a bootable Linux floppy using SYSLINUX, prepare a
normal MS-DOS formatted floppy. Copy one or more Linux kernel files to
it, then execute the DOS command:
- syslinux [-s] a:
+ syslinux [-sfma][-d directory] a:
-(or whichever drive letter is appropriate; the  meaning -s is optional)
+(or whichever drive letter is appropriate; the  meaning optional.)
Use "syslinux.com" (in the dos subdirectory of the distribution) for
plain DOS (MS-DOS, DR-DOS, PC-DOS, FreeDOS...) or Win9x/ME.
@@ -48,12 +48,13 @@ WinNT/2000/XP.
Under Linux, execute the command:
- syslinux [-s] [-o offset] /dev/fd0
+ syslinux [-sf][-d directory][-o offset] /dev/fd0
(or, again, whichever device is the correct one.)
This will alter the boot sector on the disk and copy a file named
-LDLINUX.SYS into its root directory.
+LDLINUX.SYS into its root directory (or a subdirectory, if the -d
+option is specified.)
The -s option, if given, will install a "safe, slow and stupid"
version of SYSLINUX. This version may work on some very buggy BIOSes
@@ -65,6 +66,10 @@ mode.
The -o option is used with a disk image file and specifies the byte
offset of the filesystem image in the file.
+For the DOS and Windows installers, the -m and -a options can be used
+on hard drives to write a Master Boot Record (MBR), and to mark the
+specific partition active.
On boot time, by default, the kernel will be loaded from the image named
LINUX on the boot floppy. This default can be changed, see the section
on the SYSLINUX config file.
@@ -174,14 +179,11 @@ LABEL label
- Notes: Labels are mangled as if they were filenames, and must be
- unique after mangling. For example, two labels
- "v2.1.30" and "v2.1.31" will not be distinguishable
- under SYSLINUX, since both mangle to the same DOS filename.
- This is also true for "foo bar" and "foo baz".
+ Note: The "kernel" doesn't have to be a Linux kernel; it can
+ be a boot sector or a COMBOOT file (see below.)
- The "kernel" doesn't have to be a Linux kernel; it can
- be a boot sector or a COMBOOT file (see below.)
+ Since version 3.32 label names are no longer mangled into DOS
+ format (for SYSLINUX.)
Append nothing. APPEND with a single hyphen as argument in a
@@ -671,10 +673,13 @@ The Linux boot protocol supports a "boot loader ID", a single byte
where the upper nybble specifies a boot loader family (3 = SYSLINUX)
and the lower nybble is version or, in the case of SYSLINUX, media:
- 0x31 = SYSLINUX
- 0x32 = PXELINUX
- 0x33 = ISOLINUX
- 0x34 = EXTLINUX
+ 0x31 (49) = SYSLINUX
+ 0x32 (50) = PXELINUX
+ 0x33 (51) = ISOLINUX
+ 0x34 (52) = EXTLINUX
+In recent versions of Linux, this ID is available as
++++ BUG REPORTS ++++