From e30af0297db09528ca5a9e08aaf31154859e0fe4 Mon Sep 17 00:00:00 2001
From: Colin Watson <cjwatson@ubuntu.com>
Date: Wed, 30 Mar 2011 03:20:09 +0100
Subject: [PATCH] * docs/grub.texi (Simple configuration): Explain some of the
 current limitations of grub-mkconfig.

---
 ChangeLog      |  5 +++++
 docs/grub.texi | 10 ++++++++++
 2 files changed, 15 insertions(+)

diff --git a/ChangeLog b/ChangeLog
index 661f08502..35fd04154 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,8 @@
+2011-03-30  Colin Watson  <cjwatson@debian.org>
+
+	* docs/grub.texi (Simple configuration): Explain some of the
+	current limitations of grub-mkconfig.
+
 2011-03-29  Vladimir Serbinenko  <phcoder@gmail.com>
 
 	Old macs search for boot.efi rather than for bootia32.efi.
diff --git a/docs/grub.texi b/docs/grub.texi
index 368d21f1d..9ff72798b 100644
--- a/docs/grub.texi
+++ b/docs/grub.texi
@@ -1066,6 +1066,16 @@ generates @file{grub.cfg} files suitable for most cases.  It is suitable for
 use when upgrading a distribution, and will discover available kernels and
 attempt to generate menu entries for them.
 
+@command{grub-mkconfig} does have some limitations.  While adding extra
+custom menu entries to the end of the list can be done by editing
+@file{/etc/grub.d/40_custom} or creating @file{/boot/grub/custom.cfg},
+changing the order of menu entries or changing their titles may require
+making complex changes to shell scripts stored in @file{/etc/grub.d/}.  This
+may be improved in the future.  In the meantime, those who feel that it
+would be easier to write @file{grub.cfg} directly are encouraged to do so
+(@pxref{Booting}, and @ref{Shell-like scripting}), and to disable any system
+provided by their distribution to automatically run @command{grub-mkconfig}.
+
 The file @file{/etc/default/grub} controls the operation of
 @command{grub-mkconfig}.  It is sourced by a shell script, and so must be
 valid POSIX shell input; normally, it will just be a sequence of