From 520ec8572dade0a9b1b063c105bddd1a557c1141 Mon Sep 17 00:00:00 2001
From: okuji <okuji@localhost>
Date: Sun, 30 Jul 2000 09:18:46 +0000
Subject: [PATCH] add the answer for the separate boot partition problem into
 the faq.

---
 ChangeLog            |  5 +++++
 docs/appendices.texi | 39 +++++++++++++++++++++++++++++++++++++++
 2 files changed, 44 insertions(+)

diff --git a/ChangeLog b/ChangeLog
index 63a9272d6..9cd4ba0b1 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2000-07-30  OKUJI Yoshinori  <okuji@gnu.org>
+
+	* docs/appendices.texi (FAQ): Added the answer for the separate
+	boot partition problem.
+	
 2000-07-30  OKUJI Yoshinori  <okuji@gnu.org>
 
 	Update the network support to Etherboot-4.6.4.
diff --git a/docs/appendices.texi b/docs/appendices.texi
index ed576b587..93e29b15b 100644
--- a/docs/appendices.texi
+++ b/docs/appendices.texi
@@ -56,11 +56,13 @@ Copy the GRUB images to @file{/mnt/boot/grub}. Only @file{stage1},
 Run the following command:
 
 @example
+@group
 $ /sbin/grub --batch <<EOT
 root (fd0)
 setup (fd0)
 quit
 EOT
+@end group
 @end example
 @end enumerate
 
@@ -142,6 +144,43 @@ grub> kernel /vmlinuz mem=128M
 You may pass other options in the same way. See @xref{GNU/Linux}, for
 more details.
 
+@item I have a separate boot partition and GRUB doesn't recognize it.
+
+This is often reported as a @dfn{bug}, but this is not a bug
+really. This is a feature.
+
+Because GRUB is a boot loader and it normally runs under no operating
+system, it doesn't know where a partition is mounted under your
+operating systems. So, if you have the partition @file{/boot} and you
+install GRUB images into the directory @file{/boot/grub}, GRUB
+recognizes that the images lies under the directory @file{/grub} but not
+@file{/boot/grub}. That's fine, since there is no guarantee that all of
+your operating systems mount the same partition as @file{/boot}.
+
+There are several solutions for this situation.
+
+@enumerate
+@item
+Install GRUB into the directory @file{/boot/boot/grub} instead of
+@file{/boot/grub}. This may sound ugly but should work fine.
+
+@item
+Create a symbolic link before installing GRUB, like @samp{cd /boot && ln
+-s . boot}. This works only if the filesystem of the boot partition
+supports symbolic links and GRUB supports the feature as well.
+
+@item
+Install GRUB with the command @command{install}, to specify the paths of
+GRUB images explicitly. Here is an example:
+
+@example
+@group
+grub> root (hd0,1)
+grub> install /grub/stage1 d (hd0) /grub/stage2 p /grub/menu.lst
+@end group
+@end example
+@end enumerate
+
 @item Why don't Linux, FreeBSD, NetBSD, etc. become Multiboot-compliant?
 
 Please ask the relevant maintainers. If all free kernels were