public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Felix Oxley <lkml@oxley.org>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>,
	trivial@rustcorp.com.au
Subject: Re: [PATCH 1/1] Kconfig help text for RAM Disk & initrd
Date: Mon, 17 Oct 2005 00:37:36 -0500	[thread overview]
Message-ID: <200510170037.37034.rob@landley.net> (raw)
In-Reply-To: <200510170102.19717.lkml@oxley.org>

On Sunday 16 October 2005 19:02, Felix Oxley wrote:
> 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.

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

  reply	other threads:[~2005-10-17  5:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-17  0:02 [PATCH 1/1] Kconfig help text for RAM Disk & initrd Felix Oxley
2005-10-17  5:37 ` Rob Landley [this message]
2005-10-17  7:12   ` Felix Oxley
2005-10-17  7:33     ` Rob Landley
2005-10-17 12:44       ` Felix Oxley
2005-10-17 21:32         ` Rob Landley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200510170037.37034.rob@landley.net \
    --to=rob@landley.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@oxley.org \
    --cc=torvalds@osdl.org \
    --cc=trivial@rustcorp.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox