From: Felix Oxley
Date: Sat Oct 15 2005 - 04:58:06 EST
I am sure who the following patch should be directed to.
(I couldn't find the Maintainer for RAM disk or initrd listed in the
Change to Kconfig text for RAM disks where suggested setting was N.
Now reminds the user that this option is required for initrd.
Hopefully this will stop me turning off this option and thus being unable to
boot my system :-)
Signed-off-by: Felix Oxley <lkml@xxxxxxxxx>
--- ./drivers/block/Kconfig.orig 2005-10-15 08:58:20.000000000 +0100
+++ ./drivers/block/Kconfig 2005-10-15 09:25:31.000000000 +0100
@@ -368,19 +368,21 @@ 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.
+ (For this purpose say Y to this and also to initrd below)
Note that the kernel command line option "ramdisk=XX" is now
obsolete. For details, read <file:Documentation/ramdisk.txt>.
+ Unless your system uses a RAM disk whilst booting you probably
+ won't need this functionality, and can thus say N here.
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.
int "Default number of RAM disks" if BLK_DEV_RAM
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/