[PATCH 1/1] Kconfig help text for RAM Disk & initrd

[Felix Oxley <lkml@oxley.org>]

From: Felix Oxley <lkml@oxley.org>

Amend Kconfig help text for RAM Disk & initrd to suggest that
these features should be answered Y.
Remove loadlin as an example of a boot loader, replace with grub.

Signed-off-by: Felix Oxley <lkml@oxley.org>
---
--- ./drivers/block/Kconfig.orig	2005-10-17 00:20:18.000000000 +0100
+++ ./drivers/block/Kconfig	2005-10-16 23:57:18.000000000 +0100
@@ -368,9 +368,11 @@ config BLK_DEV_RAM
 	  Saying Y here will allow you to use a portion of your RAM memory as
 	  a block device, so that you can make file systems on it, read and
 	  write to it and do all the other things that you can do with normal
-	  block devices (such as hard drives). It is usually used to load and
-	  store a copy of a minimal root file system off of a floppy into RAM
-	  during the initial install of Linux.
+	  block devices (such as hard drives).
+
+	  It is usually used to load and store a copy of a minimal root file
+	  system into RAM during the boot sequence. "Inital RAM disk support"
+	  must also be enabled for this option to work.
 
 	  Note that the kernel command line option "ramdisk=XX" is now
 	  obsolete. For details, read <file:Documentation/ramdisk.txt>.
@@ -378,8 +380,10 @@ config BLK_DEV_RAM
 	  To compile this driver as a module, choose M here: the
 	  module will be called rd.
 
-	  Most normal users won't need the RAM disk functionality, and can
-	  thus say N here.
+	  Say Y here if your system uses a RAM disk whilst booting, or if you
+	  know you require a RAM disk for another purpose. Otherwise, say N.
+
+	  If unsure, say Y.
 
 config BLK_DEV_RAM_COUNT
 	int "Default number of RAM disks" if BLK_DEV_RAM
@@ -403,11 +407,12 @@ config BLK_DEV_INITRD
 	depends on BLK_DEV_RAM=y
 	help
 	  The initial RAM disk is a RAM disk that is loaded by the boot loader
-	  (loadlin or lilo) and that is mounted as root before the normal boot
+	  (lilo or grub) and that is mounted as root before the normal boot
 	  procedure. It is typically used to load modules needed to mount the
 	  "real" root file system, etc. See <file:Documentation/initrd.txt>
 	  for details.
 
+	  Most users will answer Y here.
 
 #XXX - it makes sense to enable this only for 32-bit subarch's, not for x86_64
 #for instance.