add directory study

study/boot/LILO/LILO-FAQ-V1.0.txt

@@ -0,0 +1,228 @@
+LILO  -  Frequently Asked Questions   Version 1                 16-AUG-1993
+===========================================================================
+
+This FAQ consists of two parts: the first part contains a few remarks about
+common sources of confusion. The second part contains questions and
+answers.
+
+Please send comments about this FAQ to almesber@nessie.cs.id.ethz.ch or
+almesber@bernina.ethz.ch
+
+
+General remarks
+---------------
+
+Don't try installing LILO by typing commands like
+/etc/lilo/lilo -i /etc/lilo/boot.b /vmlinux
+  First, this doesn't work with version 0.10 and above. Second, you will
+  have to refresh the installation whenever the kernel or any part of LILO
+  is changed. It is therefore advisable to store the configuration data in
+  a file. (Typically /etc/lilo/config)
+  
+/etc/lilo/install vs. /etc/lilo/config
+  Versions before 0.7 did expect all settings, kernel names, etc. on the
+  command line. Because such command lines usually became complicated and
+  hard to remember, everything was stored in /etc/lilo/install. This script
+  was run whenever the installation had to be refreshed. Version 0.7
+  introduced a more elegant configuration method: the configuration file
+  /etc/lilo/config. When using /etc/lilo/config, /etc/lilo/install only
+  contained the invocation of /etc/lilo/lilo with the necessary option.
+  That "new" /etc/lilo/install also appeared under the name install.new.
+  Starting with LILO 0.10, only the new-style configuration method is
+  supported. Because of that, no additional command-line options are needed
+  anymore and /etc/lilo/install can even be replaced by a link to
+  /etc/lilo/lilo.
+
+/etc/lilo/boot.NNNN installed by your favourite distribution
+  Some Linux distributions install some boot.NNNN files in /etc/lilo before
+  LILO is run. This is dangerous, because a) you may accidentially use
+  those files and b) it prevents LILO from generating the correct boot.NNNN
+  files when installing itself on your system. (boot.NNNN are backup copies
+  of boot sectors.) Just delete any alien boot.NNNN files from your system
+  before using LILO.
+
+QuickInst
+  ... is a shell script that helps you installing and configuring LILO. It
+  doesn't use every single feature of LILO and does not support some exotic
+  configurations, but it's usually a good way to get started. You can also
+  use it to create a sample /etc/lilo/config and modify that later.
+
+
+Q&A
+---
+
+Q: What is LILO ?
+A: LILO is a generic boot loader for Linux. "generic" means that it is able
+   to boot kernels from all Linux file systems. It can also act as a boot
+   manager for non-Linux operating systems.
+
+Q: Which version of LILO should I use ?
+A: Versions before 0.7 are obsolete and should be avoided. Versions since
+   0.8 come with a quick installation script that simplifies "standard"
+   installations. The current version is 0.11.
+
+Q: How do I get LILO ?
+A: LILO can be found in
+   tsx-11.mit.edu:/pub/linux/packages/lilo
+   sunsite.unc.edu:/pub/Linux/system/Linux-boot/lilo
+
+Q: What about documentation ?
+A: LILO documentation exists in the following formats:
+    - LaTeX source, contained in lilo.N.tar.z
+    - plain-ASCII README, contained in lilo.N.tar.z
+    - ready to print PostScript, lilo.u.N.ps.z and lilo.t.N.ps.z
+    - ready to print HP DeskJet and HP LaserJet data, lilo.u.N.dj.z and
+      lilo.t.N.dj.z
+   N is the respective version number. The lilo.u* files are the user's
+   manual, lilo.t* are the technical overview.
+   Note: the README does not contain a few introductory sections of the
+         LaTeX manual.
+
+Q: I don't want to read that many pages only to use a boot loader.
+A: Then you should try to use QuickInst. If your system configuration is
+   too complex for QuickInst or if you run into unexpected problems and
+   this FAQ doesn't help, I'm afraid you can't avoid reading the
+   documentation.
+
+Q: I feel uncertain about that booting stuff. What should I read ?
+A: The first section of the LaTeX documentation of LILO contains an
+   introduction of how PC disks are partitioned and how operating systems
+   are booted. The following sections describe boot concepts and show them
+   on a few examples. Those sections are not included in the plain-ASCII
+   README, because they contain complex drawings.
+
+Q: Can I use LILO as a boot manager ?
+A: Yes. It is known to work with PC/MS-DOS and OS/2. It probably also works
+   with many other operating systems.
+
+Q: How do I boot other operating systems from LILO ?
+A: You simply add sections to /etc/lilo/config, describing the location of
+   the operating system, its name and the partition table, e.g.
+
+    other = /dev/hda1  # partition on which the operating system is located
+      label = dos      # name by which you want it to be identified
+      table = /dev/hda # partition table of that disk
+
+   Then re-run /etc/lilo/install
+
+Q: How do I boot other operating systems from the second drive ?
+A: You have to add the line
+     loader = /etc/lilo/any_d.b         (DOS, etc.)
+   or
+     loader = /etc/lilo/os2_d.b         (OS/2)
+   to the corresponding OTHER = ... section of /etc/lilo/config
+
+Q: I still can't boot DOS from the second drive.
+A: Disable the first drive and verify that you can boot from the second
+   drive if it is the first drive. If you can't, try using SYS to install
+   the system files. If all else fails, use FDISK /MBR and/or FORMAT /S .
+
+Q: How do I set the default kernel/operating system ?
+A: The first kernel or operating system defined in /etc/lilo/config is
+   booted by default. Don't forget to re-run /etc/lilo/install after
+   reordering the sections.
+
+Q: LILO doesn't boot my SCO/ISC/etc. What can I do ?
+A: Verify that your configuration is correct. Re-run /etc/lilo/install. If
+   all else fails, try to use a different boot manager, e.g. bootactv.
+
+Q: Where should I install LILO's boot sector ?
+A: If you have a Linux file system on a primary partition of your first
+   hard disk, you should install the LILO boot sector there and make that
+   partition active (or use some boot manager). Otherwise, you can install
+   the LILO boot sector as your MBR (e.g. on /dev/hda) or possibly on an
+   extended partition (see the LaTeX documentation for details).
+
+Q: How do I uninstall LILO ?
+A: If you've installed LILO as your MBR (/dev/hda or /dev/sda) and if your
+   previous MBR was the "standard" DOS MBR, you can remove LILO from the
+   MBR by simply booting MS-DOS 5.0 and running the command
+   FDISK /MBR
+   (If you're running DR-DOS 6, the FDISK menu offers a similar option.)
+   Otherwise, if you haven't installed LILO as your MBR, you can simply
+   disable it by making a different partition active. The active partition
+   can be changed with MS-DOS' FDISK, Linux fdisk, LILO's activate, etc.
+   Finally, if you've installed LILO as your MBR, but you're using a
+   special MBR, or if your version of DOS does no support replacing the
+   MBR, you should look for a file /etc/lilo/boot.0300 (IDE) or
+   /etc/lilo/boot.0800 (SCSI). See the next item for a description of how
+   to use that file.
+
+Q: I can't access my PC/MS-DOS partition after installing LILO. Am I lost ?
+A: Not necessarily. You've probably only overwritten the boot sector of
+   your MS-DOS partition. That boot sector contains vital information about
+   the file system structure. (Note: unlike MS-DOS, Linux file systems do
+   not use the first sector and LILO can therefore store its boot sector
+   there.) Whenever LILO overwrites a boot sector for the first time, it
+   makes a backup copy in /etc/lilo, named boot.NNNN. The number
+   corresponds to the number of the respective device, e.g. hda is 0300,
+   hda1 is 0301, sda is 0800, sda1 is 0801, etc. You can restore the old
+   boot sector with a command like
+   dd if=/etc/lilo/boot.NNNN of=/dev/XXXX bs=446 count=1
+   E.g. dd if=/etc/lilo/boot.0302 of=/dev/hda2 bs=446 count=1
+
+   WARNING: check the date of the boot.NNNN file. Sometimes, distributions
+            that contain LILO come with boot.NNNN files from the system on
+            which the distribution was created. Those files should be
+            deleted before using LILO.
+
+Q: Why does LILO stop with "Error 0x04" when booting from a floppy ?
+A: Your BIOS may suffer from a bug that generates errors when trying to
+   read more than one sector with a single call. LILO 0.11 is able to
+   correct that problem. When using an older version of LILO, removing the
+   option COMPACT from /etc/lilo/config works around it.  
+
+Q: LILO used to work, but since I've updated LILO/compiled a new kernel/
+   installed a new version of SLS, LILO only prints "LI".
+A: Be sure to re-run /etc/lilo/install whenever the kernel or any part of
+   LILO is changed. Running /etc/lilo/install too often doesn't hurt, but
+   forgetting to run it does. By the way, the kernel Makefile has two
+   targets that automatically run /etc/lilo/install after building a new
+   kernel: "lilo" builds /vmlinux (not compressed) and "zlilo" builds
+   /vmlinuz (compressed). If you're not installing LILO as the MBR, you
+   should also verify that the partition on which LILO puts its boot sector
+   is marked active and that the MBR contains a valid partition loader (and
+   not the remains of an earlier installation of LILO).
+
+Q: LILO only prints "LI" on my SCSI system.
+A: In prehistorical times, SCSI users had to describe the geometry of their
+   disks in a file called /etc/lilo/disktab. Recent kernels are able to
+   provide that information for most SCSI adapters. Hence,
+   /etc/lilo/disktab is not necessary and may only introduce errors. If you
+   have a disktab with non-comment entries, try running /etc/lilo/install
+   with the option  -f /dev/null  If LILO needs a disktab, it will issue an
+   error message.
+
+Q: My kernel boots but dies with "VFS: Unable to mount root".
+A: Your kernel is not properly configured. You can either run rdev on it to
+   set the root device or put the corresponding ROOT=/dev/xxxx entry into
+   /etc/lilo/config and re-run /etc/lilo/install
+
+Q: What does "Device 0xNNNN: Invalid partition table, Nth entry" mean ?
+A: Each partition entry contains linear (Nth sector on the disk) and 3D
+   (sector/head/cylinder) addresses. Both types of addresses must
+   correspond. In your partition table, they don't. This is probably caused
+   by a buggy fdisk using non-cylinder-aligned addresses and some other
+   program later re-aligning one part of the address. LILO can try to fix
+   the partition table. The exact procedure depends on the version of LILO.
+   Please check the documentation. The cleanest (but also most painful)
+   solution to the problem is to re-partition the disk with a version of
+   fdisk that obeys alignment rules (e.g. any current version of Linux
+   fdisk).
+
+Q: Do LILO and OS/2 Boot Manager get along well ?
+A: Yes, but some people have reported they had to (re)install LILO after
+   installing OS/2. A different solution is to avoid OS/2 BM and boot OS/2
+   directly by LILO.
+-- 
+   _________________________________________________________________________
+  / Werner Almesberger, ETH Zuerich, CH      almesber@nessie.cs.id.ethz.ch /
+ /_IFW_A44_______________________________________almesber@bernina.ethz.ch_/
+
+-- 
+Send submissions for comp.os.linux.announce to: linux-announce@tc.cornell.edu
+
+
+
+
+

study/boot/LILO/Laboratoire de R��seaux de Communication Werner Almesberger.htm

@@ -0,0 +1,140 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+<!-- saved from url=(0114)http://www.google.com/search?q=cache:Ck8Z2qND4m4C:lrcwww.epfl.ch/~almesber/+Werner+Almesberger+linux+lilo&hl=zh-CN -->
+<HTML><HEAD><TITLE>Laboratoire de Réseaux de Communication: Werner Almesberger</TITLE>
+<META http-equiv=Content-Type content="text/html; charset=ISO-8859-1">
+<META content="MSHTML 6.00.2600.0" name=GENERATOR></HEAD>
+<BODY>
+<TABLE width="100%" border=1>
+  <TBODY>
+  <TR>
+    <TD>
+      <TABLE cellSpacing=0 cellPadding=10 width="100%" bgColor=#ffffff border=1 
+      color="#ffffff">
+        <TBODY>
+        <TR>
+          <TD><FONT face=arial,sans-serif color=black size=-1>This is <B><FONT 
+            color=#0039b6>G</FONT> <FONT color=#c41200>o</FONT> <FONT 
+            color=#f3c518>o</FONT> <FONT color=#0039b6>g</FONT> <FONT 
+            color=#30a72f>l</FONT> <FONT color=#c41200>e</FONT></B>'s <A 
+            href="http://www.google.com/help/features.html#cached"><FONT 
+            color=blue>cache</FONT></A> of <A 
+            href="http://lrcwww.epfl.ch/~almesber/"><FONT 
+            color=blue>http://lrcwww.epfl.ch/~almesber/</FONT></A>.<BR><B><FONT 
+            color=#0039b6>G</FONT> <FONT color=#c41200>o</FONT> <FONT 
+            color=#f3c518>o</FONT> <FONT color=#0039b6>g</FONT> <FONT 
+            color=#30a72f>l</FONT> <FONT color=#c41200>e</FONT></B>'s cache is 
+            the snapshot that we took of the page as we crawled the web.<BR>The 
+            page may have changed since that time. Click here for the <A 
+            href="http://lrcwww.epfl.ch/~almesber/"><FONT color=blue>current 
+            page</FONT></A> without highlighting.</FONT><BR><BR>
+            <CENTER><FONT size=-1><I>Google is not affiliated with the authors 
+            of this page nor responsible for its 
+        content.</I></FONT></CENTER></TD></TR>
+        <TR>
+          <TD>
+            <TABLE cellSpacing=0 cellPadding=0 border=0>
+              <TBODY>
+              <TR>
+                <TD><FONT face=arial,sans-serif color=black size=-1>These 
+                  search terms have been highlighted:&nbsp;</FONT></TD>
+                <TD bgColor=#ffff66><B><FONT face=arial,sans-serif color=black 
+                  size=-1>werner&nbsp;</FONT></B></TD>
+                <TD bgColor=#a0ffff><B><FONT face=arial,sans-serif color=black 
+                  size=-1>almesberger&nbsp;</FONT></B></TD>
+                <TD bgColor=#99ff99><B><FONT face=arial,sans-serif color=black 
+                  size=-1>linux&nbsp;</FONT></B></TD>
+                <TD bgColor=#ff9999><B><FONT face=arial,sans-serif color=black 
+                  size=-1>lilo&nbsp;</FONT></B></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE>
+<HR>
+<A href="http://icawww1.epfl.ch/~almesber/more.html"><IMG src=""></A> 
+<H1><B style="COLOR: black; BACKGROUND-COLOR: #ffff66">Werner </B><B 
+style="COLOR: black; BACKGROUND-COLOR: #a0ffff">Almesberger</B></H1>
+<P><B style="COLOR: black; BACKGROUND-COLOR: #ffff66">Werner </B><B 
+style="COLOR: black; BACKGROUND-COLOR: #a0ffff">Almesberger</B>, master's in 
+Computer Science from <A href="http://www.ethz.ch/">ETH Zürich</A> in autumn 
+1992, delevoped <A 
+href="http://www.atmforum.com/atmforum/library/notes1.html">ATM</A> switch 
+control software 1993-1994 at the <A href="http://www.zurich.ibm.com/">IBM 
+Zurich Research Lab</A>, since autumn 1994 research assistant at <A 
+href="http://icawww1.epfl.ch/">LRC</A> (Laboratoire de Réseaux de Communication) 
+at <A href="http://www.epfl.ch/">EPFL</A> (École Polytechnique Fédérale de <A 
+href="http://www.lausanne.ch/">Lausanne</A>). LRC has merged with former TCOM 
+and LIT in fall 1997 to become <A href="http://icawww.epfl.ch/">ICA</A> 
+(Institute for computer Communications and Applications). PhD at the end of 
+1999. 
+<P>Participated in design and realization of a site information system (<A 
+href="http://www.ezinfo.ethz.ch/">ezInfo</A>) while at ETH. Also involved in 
+kernel work (file systems, device drivers, etc.) on <A 
+href="http://www.linux.org/"><B 
+style="COLOR: black; BACKGROUND-COLOR: #99ff99">Linux</B></A> since 1992. See 
+below for on-going <B style="COLOR: black; BACKGROUND-COLOR: #99ff99">Linux</B> 
+activities. 
+<P>Past projects (at work): 
+<UL>
+  <LI><A href="http://icawww1.epfl.ch/WebOverATMDir/WOA_homepage.html">Web over 
+  ATM</A> 
+  <LI><A href="http://icawww1.epfl.ch/arequipa/">Arequipa</A> (Application 
+  REQUested IP over ATM) 
+  <LI><A href="http://icawww1.epfl.ch/srp/">SRP</A> (Scalable Reservation 
+  Protocol) SRP was the topic of my PhD thesis. 
+  <LI><A href="http://icawww1.epfl.ch/linux-atm/">ATM on <B 
+  style="COLOR: black; BACKGROUND-COLOR: #99ff99">Linux</B></A> (now maintained 
+  by <A href="mailto:mitch@sfgoth.com">Mitchell Blank Jr</A>) </LI></UL>Current 
+activities (at work): 
+<UL>
+  <LI><A href="http://icawww1.epfl.ch/linux-diffserv/">Differentiated Services 
+  on <B style="COLOR: black; BACKGROUND-COLOR: #99ff99">Linux</B></A> 
+  <LI>Application data synchronization for mobile systems 
+  <LI>Design of a new <B 
+  style="COLOR: black; BACKGROUND-COLOR: #99ff99">Linux</B> traffic control 
+  architecture<BR>I'm piling up development material <A 
+  href="ftp://icaftp.epfl.ch/pub/linux/tcng">here</A>.<BR>There's also a <A 
+  href="ftp://icaftp.epfl.ch/pub/people/almesber/slides/cadley.ps.gz">presentation 
+  of the current design</A>. <IMG src=""> </LI></UL>Past <B 
+style="COLOR: black; BACKGROUND-COLOR: #99ff99">Linux</B> projects (besides 
+those at work): 
+<UL>
+  <LI><A href="ftp://icaftp.epfl.ch/pub/linux/local/lilo"><B 
+  style="COLOR: black; BACKGROUND-COLOR: #ff9999">LILO</B></A> boot loader (now 
+  maintained by <A href="mailto:JohnInSD@san.rr.com">John Coffman</A>) 
+  <LI>work on the Canon PowerShot A50 driver of <A 
+  href="http://www.gphoto.org/">gPhoto</A>. 
+  <LI>original FAT file system 
+  <LI><A href="http://icawww1.epfl.ch/~almesber/ifs.html">Inheriting File 
+  System</A> (abandoned) 
+  <LI>the <A href="ftp://icaftp.epfl.ch/pub/linux/local/psmisc">psmisc</A> tools 
+  (now maintained by <A href="mailto:csmall@eye-net.com.au">Craig Small</A>) 
+  <LI>a bit of hacking in the <A href="http://linux-7110.sourceforge.net/"><B 
+  style="COLOR: black; BACKGROUND-COLOR: #99ff99">linux</B>-7k project</A>. 
+</LI></UL>Current <B style="COLOR: black; BACKGROUND-COLOR: #99ff99">Linux</B> 
+projects (besides those at work): 
+<UL>
+  <LI><A 
+  href="ftp://icaftp.epfl.ch/pub/people/almesber/misc/bootimg-8.tar.gz">bootimg</A> 
+
+  <LI>participation in initrd and bzImage design, implementation, and 
+  maintenance 
+  <LI><A 
+  href="ftp://icaftp.epfl.ch/pub/people/almesber/misc/newlib-linux-2.tar.gz">newlib 
+  on <B style="COLOR: black; BACKGROUND-COLOR: #99ff99">Linux</B></A> 
+</LI></UL>Curious about current project details ? Click <A 
+href="http://icawww1.epfl.ch/~almesber/projects.html">here</A>. 
+<P>
+<HR>
+
+<P>A list of most of my publications can be retrieved via <A 
+href="http://icawww.epfl.ch/ICApublic/asp/publication_selection.asp">this 
+page</A>. 
+<P>
+<HR>
+
+<P>
+<H1>I've left EPFL ! Please use the mail address below.</H1><!-- <P>
+EPFL ICA, INN (Ecublens), CH-1015 Lausanne, Switzerland.
+</P>-->
+<P>E-Mail (<B>changed</B>): <A href="mailto:wa@almesberger.net">wa@<B 
+style="COLOR: black; BACKGROUND-COLOR: #a0ffff">almesberger</B>.net</A> <!-- Tel: +41 21 693 6621 Fax: +41 21 693 6610.--></P>
+<HR>
+Last update: 1-MAY-2001 
+<HR>
+</BODY></HTML>

study/boot/LILO/lilo/lilo-20.announce

@@ -0,0 +1,98 @@
+LILO 20 can be found at
+
+  ftp://lrcftp.epfl.ch/pub/linux/local/lilo/lilo-20.tar.gz
+
+and soon also at
+
+  ftp://sunsite.unc.edu/pub/Linux/system/boot/lilo-20.tar.gz
+  ftp://tsx-11.mit.edu/pub/linux/packages/lilo/lilo-20.tar.gz
+
+On sunsite and lrcftp, there are also pre-built PostScript versions of the
+user's guide and of the technical overview:
+
+  ftp://lrcftp.epfl.ch/pub/linux/local/lilo/lilo-t-20.ps.gz
+  ftp://lrcftp.epfl.ch/pub/linux/local/lilo/lilo-u-20.ps.gz
+  ftp://sunsite.unc.edu/pub/Linux/system/boot/lilo-t-20.ps.gz
+  ftp://sunsite.unc.edu/pub/Linux/system/boot/lilo-u-20.ps.gz
+
+Since the last release, more than one year ago, quite a few changes have
+accumulated. The most important ones:
+
+ - compiles with 2.1 kernels
+ - is nice to NT
+ - almost arbitrary partition table manipulations are possible (that's
+   the successor of FIX_TYPE and HIDE_DOS)
+ - allows for non-US keyboard maps
+
+Given the large number of changes, this version should be considered as
+"beta" and be used with due precautions.
+
+I've attached the complete list of changes.
+
+- Werner
+
+---------------------------------- cut here -----------------------------------
+
+Changes from version 19 to 20 (20-JUN-1996)
+-----------------------------
+
+  Boot loader
+  -----------
+
+    - now supports 19200 bps and 38400 bps on the serial line (UNTESTED)
+    - when reaching the end of the command line buffer, input is ignored
+      instead of being treated like [Enter] (by Martin Mares)
+    - fixed numerous bugs in patching of heap end pointer in setup.S (by Martin
+      Mares)
+    - images can now optionally be launched with a single keystroke (no [Enter]
+      required)
+    - now supports non-US keyboard layouts
+
+  Map installer
+  -------------
+
+    - DISK sections may now also define non-disk devices, e.g. /dev/ram
+    - increased debug level for the "Caching device ..." message
+    - changed the chain loader format to allow sizes > 512 Bytes
+    - chain loader now supports arbitrary drive mappings (option MAP-DRIVE)
+    - chain loader now supports arbitrary partition table modifications (option
+      CHANGE)
+    - removed the configuration option REWRITE-TABLE
+    - removed the build-time options FIX_TABLE and HIDE_DOS
+    - added the global configuration option CHANGE-RULES plus sub-options
+      RESET, TYPE, NORMAL, and HIDDEN
+    - OTHER sections have new configuration option CHANGE plus sub-options
+      PARTITION, SET, ACTIVATE, and DEACTIVATE
+    - OTHER sections have new configuration option MAP-DRIVE with sub-option TO
+    - now only 0x1b8 bytes of the boot sector are overwritten, which preserves
+      some magic numbers NT stores there
+    - compiles with 2.1 kernels (asm/boot.h problem - reported by many people)
+    - should also compile under 0.93 or such again (required NORMAL_VGA etc.,
+      which didn't exist back then)
+    - lilo -q  now prints unknown VGA modes also in hex (by Martin Mares)
+    - option SINGLE-KEY to allow single-key activation
+    - -Wno-parentheses  is no longer needed
+    - didn't complain if image label was equal to alias
+    - removed some ancient dead code
+    - new option KEYTABLE to specify non-standard keyboard mappings
+    - PS/2 ESDI disk (/dev/eda and /dev/edb) support (by Andrew Kroll)
+    - geometry.c:last_dev now only probes for the first two IDE disks
+    - because chain.b is used for everything anyway, specifying the chain
+      loader when booting from a driver other than the first one is no longer
+      mandatory
+
+  Documentation and installation
+  ------------------------------
+
+    - changed all references to nic.funet.fi to ftp.funet.fi
+    - updated the user's guide and did some restructuring (many changes)
+    - QuickInst no longer puts ramdisk=0 into lilo.conf
+    - QuickInst now consistently checks for LILO >= version 15
+    - make clean  and  make spotless  now also remove dump.s and dump.b (by
+      Martin Mares)
+    - changed package names from lilo[.part].<version> to
+      lilo[-part]-<version> for compatibility with sunsite's archive
+      maintenance scripts
+    - new tool keytab-lilo.pl to generate LILO keyboard tables
+    - updated t2a.pl to a version compatible with Perl 5
+    - READONLY implicitly turns off REWRITE_TABLE

study/boot/LILO/lilo/lilo-20.lsm

@@ -0,0 +1,20 @@
+Begin3
+Title:		LILO
+Version:	20
+Entered-date:	20JUN97
+Description:	Generic boot loader for Linux. Distribution includes full
+		source, documentation and support files, but no pre-compiled
+		binaries.
+Keywords:	Linux, boot loader
+Author:		Werner Almesberger <werner.almesberger@lrc.di.epfl.ch>
+Maintained-by:	Werner Almesberger <werner.almesberger@lrc.di.epfl.ch>
+Primary-site:	lrcftp.epfl.ch /pub/linux/local/lilo
+		162 kB lilo-20.tar.gz
+		127 kB lilo-u-20.ps.gz
+		 50 kB lilo-t-20.ps.gz
+Alternate-site:	sunsite.unc.edu /pub/Linux/system/boot/lilo
+Platforms:	Linux 0.99pl12 or newer, gcc and as86 needed to compile.
+		LaTeX and (optionally) Perl and Transfig needed to print the
+		documentation.
+Copying-policy:	BSDish
+End

study/boot/LILO/lilo/lilo-21.announce

@@ -0,0 +1,88 @@
+LILO 21 can be found at
+
+  ftp://lrcftp.epfl.ch/pub/linux/local/lilo/lilo-21.tar.gz
+
+and soon also at
+
+  ftp://sunsite.unc.edu/pub/Linux/system/boot/lilo/lilo-21.tar.gz
+  ftp://tsx-11.mit.edu/pub/linux/packages/lilo/lilo-21.tar.gz
+
+On sunsite and lrcftp, there are also pre-built PostScript versions of the
+user's guide and of the technical overview:
+
+  ftp://lrcftp.epfl.ch/pub/linux/local/lilo/lilo-t-21.ps.gz
+  ftp://lrcftp.epfl.ch/pub/linux/local/lilo/lilo-u-21.ps.gz
+  ftp://sunsite.unc.edu/pub/Linux/system/boot/lilo/lilo-t-21.ps.gz
+  ftp://sunsite.unc.edu/pub/Linux/system/boot/lilo/lilo-u-21.ps.gz
+
+This release fixes a few comparably urgent problems:
+
+ - LINEAR sometimes mis-calculated addresses
+ - NT 4 failed to boot with "INACCESSIBLE_BOOT_DEVICE" in some cases if
+   it didn't find a certain bit pattern in the MBR
+ - LILO's use of the address space below 0x100000 conflicts with some
+   recent MP systems (see option LARGE_EBDA)
+ - various minor problems with change rules
+
+Given the large number of changes, this version should be considered as
+experimental and should be used with due precautions.
+
+I've attached the complete list of changes.
+
+Note that I've queued several less critical changes and enhancements
+which are not part of this release. So if you sent me a patch and you
+don't find it here, this doesn't necessarily mean that I didn't like
+it. It may be a good idea to send it again, though ;-)
+
+- Werner
+
+---------------------------------- cut here -----------------------------------
+
+Changes from version 20 to 21 (5-DEC-1998)
+-----------------------------
+
+  Boot loader
+  -----------
+
+    - cylinder calculation could overflow when using LINEAR (fix by Jonas
+      Aaberg and an anonymous contributor)
+    - first-stage loader code begins with the byte 0xFA (a CLI instruction).
+      This works around the "INACCESSIBLE_BOOT_DEVICE" blue screen bug of
+      Windows NT 4 (reported by too many people to mention)
+    - new build-time option LARGE_EBDA to load boot loader in the 0x8xxxx area
+      instead of the 0x9xxxx area (disabled by default; problem reported by
+      Josef Moellers)
+
+  Map installer
+  -------------
+
+    - new build-time option USE_TMPDIR to honor TMPDIR when creating temporary
+      devices (disabled by default)
+    - now only 0x1b6 bytes of the boot sector are overwritten, which preserves
+      the passwords DR DOS stores there (fixed by Roy Millar)
+    - -u and -U accidently implied -v
+    - "BIOS drive 0xNN may not be accessible" warning was printed in cases
+       where the drive code was never used (fixed by Andries Brouwer)
+    - change rule for DOS16_big incorrectly used DOS16_small_hidden when
+      hiding (fixed by Anthony Richardson)
+    - RESET in CHANGE-RULES did not remove default rules (fixed by Kurt
+      Garloff)
+    - added support for Mylex DAC960 PCI RAID controllers (by Leonard Zubkoff)
+    - added support for third to sixth IDE interface
+    - build-time option READONLY was not used properly
+    - fixed a few harmless compiler warnings
+
+  Documentation and installation
+  ------------------------------
+
+    - user's guide claimed that partitions are hidden by setting the highest
+      bit in the type (i.e. 0x80). The correct value is 0x10, which is also
+      what is used in the code.
+    - removed useless (and potentially harmful) DEFAULT_PATH from
+      keytab-lilo.pl (fixed by Andries Brouwer)
+    - consistency of build-time options is now checked before build starts
+    - QuickInst has now limited knowledge of multi-disk configurations
+    - doc/Makefile: added targets user.ps and tech.ps
+    - user's guide still claimed that kernels can't be larger than 512 kB
+      (reported by Jean-Albert Ferrez)
+    - weird description of the purpose of option BEEP (reported by Tom Toffoli)

study/boot/LILO/lilo/lilo-21.lsm

@@ -0,0 +1,20 @@
+Begin3
+Title:		LILO
+Version:	21
+Entered-date:	05DEC98
+Description:	Generic boot loader for Linux. Distribution includes full
+		source, documentation and support files, but no pre-compiled
+		binaries.
+Keywords:	Linux, boot loader
+Author:		Werner Almesberger <Werner.Almesberger@epfl.ch>
+Maintained-by:	Werner Almesberger <Werner.Almesberger@epfl.ch>
+Primary-site:	lrcftp.epfl.ch /pub/linux/local/lilo
+		166 kB lilo-21.tar.gz
+		128 kB lilo-u-21.ps.gz
+		 50 kB lilo-t-21.ps.gz
+Alternate-site:	sunsite.unc.edu /pub/Linux/system/boot/lilo
+Platforms:	Linux 0.99pl12 or newer, gcc and as86 needed to compile.
+		LaTeX and (optionally) Perl and Transfig needed to print the
+		documentation.
+Copying-policy:	BSD-like
+End

study/boot/LILO/lilo/lilo.16.lsm

@@ -0,0 +1,20 @@
+Begin3
+Title:		LILO
+Version:	0.16
+Entered-date:	February 26, 1995
+Description:	Generic boot loader for Linux. Distribution includes full
+		source, documentation and support files, but no pre-compiled
+		binaries.
+Keywords:	Linux, boot loader
+Author:		Werner Almesberger <werner.almesberger@lrc.di.epfl.ch>
+Maintained-by:	Werner Almesberger <werner.almesberger@lrc.di.epfl.ch>
+Primary-site:	lrcftp.epfl.ch /pub/linux/local/lilo
+		144 kB lilo.16.tar.gz
+		 87 kB lilo.u.16.ps.gz
+		 28 kB lilo.t.16.ps.gz
+Alternate-site:	sunsite.unc.edu /pub/Linux/system/Linux-boot/lilo
+Platforms:	Linux 0.99pl12 or newer, gcc and as86 needed to compile.
+		LaTeX and (optionally) Perl and Transfig needed to print the
+		documentation.
+Copying-Policy:	BSDish
+End

study/boot/LILO/lilo/lilo.17.lsm

@@ -0,0 +1,20 @@
+Begin3
+Title:		LILO
+Version:	0.17
+Entered-date:	December 19, 1995
+Description:	Generic boot loader for Linux. Distribution includes full
+		source, documentation and support files, but no pre-compiled
+		binaries.
+Keywords:	Linux, boot loader
+Author:		Werner Almesberger <werner.almesberger@lrc.di.epfl.ch>
+Maintained-by:	Werner Almesberger <werner.almesberger@lrc.di.epfl.ch>
+Primary-site:	lrcftp.epfl.ch /pub/linux/local/lilo
+		142 kB lilo.16.tar.gz
+		114 kB lilo.u.16.ps.gz
+		 43 kB lilo.t.16.ps.gz
+Alternate-site:	sunsite.unc.edu /pub/Linux/system/Linux-boot/lilo
+Platforms:	Linux 0.99pl12 or newer, gcc and as86 needed to compile.
+		LaTeX and (optionally) Perl and Transfig needed to print the
+		documentation.
+Copying-Policy:	BSDish
+End

study/boot/LILO/lilo/lilo.18.lsm

@@ -0,0 +1,20 @@
+Begin3
+Title:		LILO
+Version:	18
+Entered-date:	May 16, 1996
+Description:	Generic boot loader for Linux. Distribution includes full
+		source, documentation and support files, but no pre-compiled
+		binaries.
+Keywords:	Linux, boot loader
+Author:		Werner Almesberger <werner.almesberger@lrc.di.epfl.ch>
+Maintained-by:	Werner Almesberger <werner.almesberger@lrc.di.epfl.ch>
+Primary-site:	lrcftp.epfl.ch /pub/linux/local/lilo
+		150 kB lilo.18.tar.gz
+		115 kB lilo.u.18.ps.gz
+		 43 kB lilo.t.18.ps.gz
+Alternate-site:	sunsite.unc.edu /pub/Linux/system/Linux-boot/lilo
+Platforms:	Linux 0.99pl12 or newer, gcc and as86 needed to compile.
+		LaTeX and (optionally) Perl and Transfig needed to print the
+		documentation.
+Copying-Policy:	BSDish
+End

study/boot/LILO/lilo/lilo.19.lsm

@@ -0,0 +1,20 @@
+Begin3
+Title:		LILO
+Version:	19
+Entered-date:	21MAY96
+Description:	Generic boot loader for Linux. Distribution includes full
+		source, documentation and support files, but no pre-compiled
+		binaries.
+Keywords:	Linux, boot loader
+Author:		Werner Almesberger <werner.almesberger@lrc.di.epfl.ch>
+Maintained-by:	Werner Almesberger <werner.almesberger@lrc.di.epfl.ch>
+Primary-site:	lrcftp.epfl.ch /pub/linux/local/lilo
+		151 kB lilo.19.tar.gz
+		115 kB lilo.u.19.ps.gz
+		 43 kB lilo.t.19.ps.gz
+Alternate-site:	sunsite.unc.edu /pub/Linux/system/Linux-boot/lilo
+Platforms:	Linux 0.99pl12 or newer, gcc and as86 needed to compile.
+		LaTeX and (optionally) Perl and Transfig needed to print the
+		documentation.
+Copying-policy:	BSDish
+End