Debian release 0.5-2.

docs/BUGS

@@ -1,6 +1,9 @@
 
 Known problems/bugs:
 
+  - Try `d' to delete the selected line while editing a menu entry
+    (maybe only when deleting the last line).  Everything goes to hell.
+
   - FreeBSD boot command-line options are slightly problematic, and
     OpenBSD options are probably quite wrong.  This is because they
     use options that are bits in a data word passed at boot time, and
@@ -28,4 +31,3 @@ Known problems/bugs:
 
   - Hitting Ctrl-Alt-Delete when in GRUB locks some machines.  Use Reset
     for now.  (This apparently hasn't been observed for a while)
-

docs/NEWS

@@ -1,3 +1,8 @@
+NEWS - list of user-visible changes between releases of GRUB
+
+New in 0.5.2 - 1999-01-31, Gordon Matzigkeit:
+* Bug fixes.
+*
 
 Version 0.5:
 
@@ -210,4 +215,3 @@ Version 0.0 dated 12/10/95:
   - Fixed some documentation (what little there is :-/ and a few assembly
     bugs in the BIOS access routines that nobody reported yet, so I won't
     detail it here.
-

docs/TODO

@@ -1,3 +1,15 @@
+Treat `(hd)/boot/grub/menu.lst' as searching through the hard drives
+for a partition that contains /boot/grub/menu.lst.  Either this, or
+`(hd:0x82)' means the first partition of type 0x82.  We need one of
+these dynamic search mechanisms for clean Hurd install floppies.
+
+Syntax:
+
+ (hd0,0)   -> hd0s1
+ (hd0,1,b) -> hd0s1b
+ (hd0)     -> hd0
+
+Find out the size restrictions for FAT and ext2fs stage1.5 boot blocks.
 
 	Check for other patches sent in e-mail!!!  There are several...
 
@@ -18,4 +30,3 @@
 	???  Add command for modifying partition types.
 
 	Fix-up FreeBSD, NetBSD (and OpenBSD ?) command-line boot parameters
-

docs/boot-proposal.html

@@ -404,7 +404,7 @@ the "top-level" partition number, 'part2' specifies a "sub-partition" in
 the top-level partition, etc.  Partition numbers always start from zero.
 Unused partition bytes must be set to 0xFF.  For example, if the disk is
 partitioned using a simple one-level DOS partitioning scheme, then 'part1'
-contains the DOS partition number, and 'part2' and 'part3' are both zero.
+contains the DOS partition number, and 'part2' and 'part3' are both 0xFF.
 As another example, if a disk is partitioned first into DOS partitions, and
 then one of those DOS partitions is subdivided into several BSD partitions
 using BSD's "disklabel" strategy, then 'part1' contains the DOS partition
@@ -412,13 +412,13 @@ number, 'part2' contains the BSD sub-partition within that DOS partition,
 and 'part3' is 0xFF.<P>
 
 DOS extended partitions are indicated as partition numbers starting from 4
-and increasing, rather than as nested sub-partitions, even though the 
+and increasing, rather than as nested sub-partitions, even though the
 underlying disk layout of extended partitions is hierarchical in nature.
 For example, if the boot loader boots from the second extended partition
 on a disk partitioned in conventional DOS style, then 'part1' will be 5,
 and 'part2' and 'part3' will both be 0xFF.<P>
 
-If bit 2 of the flags longword is set, the 'cmdline' field is valid, and 
+If bit 2 of the flags longword is set, the 'cmdline' field is valid, and
 contains the physical address of the the command line to be passed to the
 kernel.  The command line is a normal C-style null-terminated string.<P>
 
@@ -661,4 +661,3 @@ area.<P>
 
 </BODY>
 </HTML>
-

docs/filesystem.txt

@@ -206,7 +206,7 @@ The variables which can be read by the filesystem backend are:
 
   --  the "#define FSYS_BUF", which points to a filesystem buffer which
 	is 32K in size, to use in any way which the filesystem backend
-	desires. 
+	desires.
 
 The variables which need to be written by a filesystem backend are:
 
@@ -295,5 +295,3 @@ Limitations:
   --  If the "blocksize" is greater than 8Kbytes, various buffers will
       overwrite themselves and the whole thing will come apart at the
       seams.
-
-