X-Git-Url: http://git.annexia.org/?a=blobdiff_plain;f=febootstrap-to-initramfs.pod;h=be5985cd0b9ce428e2e3311556bcfdbd20f0a765;hb=c435d4d0275db66ba3d1b8583d31c87f44236110;hp=ce0296dfdf38885e7f03e31a954e1915a940f9e2;hpb=c408cc553f0b420e82f3ed4f62722bd40148520e;p=febootstrap.git

diff --git a/febootstrap-to-initramfs.pod b/febootstrap-to-initramfs.pod
index ce0296d..be5985c 100644
--- a/febootstrap-to-initramfs.pod
+++ b/febootstrap-to-initramfs.pod
@@ -25,7 +25,9 @@ page).  You do I<not> need to run this command as root.
 Normal initramfs images start by executing the program or script
 called C</init>.  febootstrap does not create this script, so you may
 wish to, particularly for very minimal bootstraps that don't have the
-normal SysVinit/upstart machinery.
+normal SysVinit/upstart machinery.  It's also required if the kernel
+cannot find a "real" root filesystem (the root filesystem that we
+built and placed in an initramfs doesn't count).
 
 Linux will try to run the following commands in turn, unless you
 override it using the C<init=I<cmd>> kernel option:
@@ -63,7 +65,6 @@ this in mind when creating very large filesystems.
 
 =head1 SEE ALSO
 
-L<febootstrap-fix-root(8)>,
 L<febootstrap(8)>,
 L<cpio(1)>.