On Sunday 16 October 2005 19:02, Felix Oxley wrote:
> From: Felix Oxley <[email protected]>
>
> 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 <[email protected]>
> ---
> --- ./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.
Actually if this is a patch against 2.6, between ramfs (including initramfs)
and the ability to loopback mount files, I personally consider ramdisks
semi-obsolete. (This might be _why_ it says most normal users won't need
them.)
> 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.
Again, on 2.6, most users will probably answer N and will instead use
initramfs.
Rob
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
