原帖由 mrfox 于 2007-3-16 05:38 PM 发表
看来没人关心，算了，结束这里的发布，只发博客了
SYSLINUX is a boot loader for the Linux operating system which operates off an MS-DOS/Windows FAT filesystem. It is intended to simplify first-time installation of Linux, and for creation of rescue- and other special-purpose boot disks. SYSLINUX can be used, when properly set up, to completely eliminate the need for distribution of raw diskette images for boot floppies. A SYSLINUX floppy can be manipulated using standard MS-DOS (or any other OS that can access an MS-DOS filesystem) tools once it has been created.
SYSLINUX是一个LINUX系统的引导装载程序，它可以脱离MS-DOS或WINDOWS的FAT格式文件系统。其目的是简化LINUX首次安装，以及创建急救盘或是其他特殊用途的启动盘。
有了正确配置的SYSLINUX，就完全不需要分发启动软盘的原始镜像了。一个SYSLINUX软盘一旦创建，就能用标准的MS-DOS或是任何能读取MS-DOS文件格式的操作系统来操控它。
今天先译一小段，看看反响再继续。希望自己不要虎头蛇尾吼吼，http://hi.baidu.com/feelsofree/blog
{ What SYSLINUX is Not... } SYSLINUX不是什么？
SYSLINUX is probably not suitable as a general purpose boot loader. It can only boot Linux from a FAT filesystem, and not, for example, ext2. Since a native Linux implementation will typically use ext2, another boot loader (e.g. LILO) is probably more suitable. In a system which actually contains DOS or Windows, LOADLIN may be simpler to use. However, SYSLINUX has shown itself to be quite useful in a number of special-purpose applications.
SYSLINUX作为一个通用的引导装载程序来讲并不适合。它只能从一个FAT文件系统上启动Linux，像ext2格式上就不行。由于linux主要是在ext2格式布署的，其他引导装载程序如LILO可能更合适。而如果是DOS和Windows并存的系统，LOADLIN用起来会更简单。然而SYSLINUX在一些特殊应用的情况下是很有用的。
PXELINUX is a SYSLINUX derivative, for booting Linux off a network server, using a network ROM conforming to the Intel PXE (Pre-Execution Environment) specification. PXELINUX is not a program that is intended to be flashed or burned into a PROM on the network card; if you want that, check out Etherboot ( http://www.etherboot.org/). If you want to create PXE-compliant boot PROM for your network card (to use with PXELINUX, for example), check out NetBoot (http://netboot.sourceforge.net/).{ How do I Configure PXELINUX? } 如何配置PXELINUX
PXELINUX是SYSLINUX的延伸，，它使用合乎英特尔PXE(预执行环境）规范的网络只读存储器，使linux可以从网络服务器启动。PXELINUX并不想成为能刷进或烧进网卡的可编程的只读存储器中的程序，如果你想这样做的话，请查阅Etherboot( http://www.etherboot.org/)。若你想给你的网卡创建一个PXE兼容的启动可编程只读存储器，请查阅Netboot (http://netboot.sourceforge.net/).。
PXELINUX operates in many ways like SYSLINUX. If you are not familiar with SYSLINUX, read the SYSLINUX FAQ first, since this documentation only explains the differences. On the TFTP server, create the directory "/tftpboot", and copy pxelinux.0 (from the SYSLINUX distribution) and any kernel or initrd images that you want to boot. Finally, create the directory "/tftpboot/pxelinux.cfg". The configuration file (equivalent of syslinux.cfg -- see the SYSLINUX FAQ for the options here) will live in this directory. Because more than one system may be booted from the same server, the configuration file name depends on the IP address of the booting machine. PXELINUX will search for its config file on the boot server in the following way:
PXELINUX在很多方面都和SYSLINUX很想像。如果你对SYSLINUX不熟悉，请读一下SYSLINUX的常见问题，因此此处仅解释它们之间的不同之处。在TFTP服务器上建立“/tftpboot"目录，将prelinux.0（SYSLINUX发行包中有），和你要启动任何内核或是初始化镜像拷贝到这个目录中。
First, it will search for the config file using the hardware type (using its ARP type code) and address, all in lower case hexadecimal with dash separators; for example, for an Ethernet (ARP type 1) with address 88:99:AA:BB:CC:DD it would search for the filename 01-88-99-aa-bb-cc-dd. Next, it will search for the config file using its own IP address in upper case hexadecimal, e.g. 192.0.2.91 -> C000025B (you can use the included progam gethostip to compute the hexadecimal IP address for any host.) If that file is not found, it will remove one hex digit and try again. Ultimately, it will try looking for a file named default (in lower case). As an example, if the boot file name is /mybootdir/pxelinux.0, the Ethernet MAC address is 88:99:AA:BB:CC:DD and the IP address 192.0.2.91, it will try: /mybootdir/pxelinux.cfg/01-88-99-aa-bb-cc-dd /mybootdir/pxelinux.cfg/C000025B /mybootdir/pxelinux.cfg/C000025 /mybootdir/pxelinux.cfg/C00002 /mybootdir/pxelinux.cfg/C0000 /mybootdir/pxelinux.cfg/C000 /mybootdir/pxelinux.cfg/C00 /mybootdir/pxelinux.cfg/C0 /mybootdir/pxelinux.cfg/C /mybootdir/pxelinux.cfg/default ... in that order.
首先，它会用硬件类型（使用其ARP类型代码）和地址（用小写，含短横线）；例如一个以太网的地址为88:99:AA:BB:CC:DD，它会搜索文件名01-88-99-aa-bb-cc-dd，然后它搜索其对应的IP地址（用大写的十六进制格式，如192.0.2.91为C000025B，你可以用内含的程序gethostip来计算任何主机的IP地址），如果没找到，它会将去掉一位十六进制字符继续尝试。最终它会去找一个名字为default的文件（小写的文件名）。举例来说，如果启动文件名是/mybootdir/pxelinux.0，MAC地址为88:99:AA:BB:CCC:DD，对应IP为192.0.2.91的话，它会以下面的顺序尝试查找：Note that all filename references are relative to the directory pxelinux.0 lives in. PXELINUX generally requires that filenames (including any relative path) are 127 characters or shorter in length. PXELINUX does not support MTFTP, and I have no immediate plans of doing so. It is of course possible to use MTFTP for the initial boot, if you have such a setup. MTFTP server setup is beyond the scope of this document.
/mybootdir/pxelinux.cfg/01-88-99-aa-bb-cc-dd
/mybootdir/pxelinux.cfg/C000025B
/mybootdir/pxelinux.cfg/C000025
/mybootdir/pxelinux.cfg/C00002
/mybootdir/pxelinux.cfg/C0000
/mybootdir/pxelinux.cfg/C000
/mybootdir/pxelinux.cfg/C00
/mybootdir/pxelinux.cfg/C0
/mybootdir/pxelinux.cfg/C
/mybootdir/pxelinux.cfg/default
注意这些文件名都是与pxelinux.0所在的目录相关的。PXELINUX通常要求这些文件名（含相关目录）小于等于127个字符。PXELINUX不支持MTFTP，眼下也没这样做的计划。如果你有配置好的MFTP的话，当然初始启动也是可能的。MTFTP服务设置已经超出了本文的范围。
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? }
ISOLINUX是一个LINUX/i386的启动引导程序，它以ISO 9660/El Torito CD-ROMs为基础，在“非模拟“方式下运行。这就避免了创建一个”模拟磁盘镜像“时的空间限制（模拟软盘）和兼容性问题（模拟硬盘）。
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.) 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): mkisofs -o output.iso \ -b isolinux/isolinux.bin -c isolinux/boot.cat \ -no-emul-boot -boot-load-size 4 -boot-info-table \ root-of-iso-tree(If you named the directory boot/isolinux that should of course be -b boot/isolinux/isolinux.bin -c boot/isolinux/boot.cat.) ISOLINUX resolves pathnames the following way:{ Can I boot other operating systems with ISOLINUX? }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; additionally you may want to use the "-relaxed-filenames" option to allow multiple dots in a filename. ISOLINUX does not support discontiguous files, interleaved mode, or logical block and sector sizes other than 2048. This should normally not be a problem. 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. 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.
- A pathname consists of names separated by slashes, Unix-style.
- 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".)
- . and .. in pathname searches are not supported.
- The maximum length of any pathname is 255 characters.
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. 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. For a floppy image, the size of the image should be exactly one of the following:{ ISOLINUX and Windows install disks }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.
1,222,800 bytes [td]1200K floppy (standard 5.25") 1,474,560 bytes [td]1440K floppy (standard 3.5") 2,949,120 bytes [td]2880K floppy (enhanced 3.5")
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. Please see the following message 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 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.
原帖由 mrfox 于 2007-3-16 05:38 PM 发表
看来没人关心，算了，结束这里的发布，只发博客了
原帖由 mrfox 于 2007-3-16 05:38 PM 发表
看来没人关心，算了，结束这里的发布，只发博客了
原帖由 弄潮儿-NET 于 2007-4-4 10:25 PM 发表
帮顶一下……不过我更喜欢英文
原帖由 弄潮儿-NET 于 2007-4-5 11:34 PM 发表
你能中译英吗？
| 25岁以下勿点击 |
原帖由 弄潮儿-NET 于 2007-4-7 12:00 AM 发表
25岁以下勿点击
原帖由 弄潮儿-NET 于 2007-4-7 09:04 PM 发表
呵呵，楼上的没看到我的个人网站就是法语的吗？
原帖由 mrfox 于 2007-4-9 02:26 AM 发表
今天把CPU弄弯一根针，后来小心弄好了，也没心情了，预计改成周二发
| 欢迎光临 无忧启动论坛 (http://wuyou.net/) | Powered by Discuz! X3.3 |
