From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Bodo Eggert <7eggert@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] use tmpfs for rootfs
Date: Thu, 16 Oct 2008 15:10:49 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0810161507130.25933@anakin> (raw)
In-Reply-To: <alpine.LSU.0.999.0810161400160.5456@be1.lrz>
On Thu, 16 Oct 2008, Bodo Eggert wrote:
> +config TMPFS_ROOT
> + bool "Use tmpfs instrad of ramfs for initramfs"
> + depends on TMPFS && SHMEM
> + default n
> + help
> + This replaces the ramfs used for unpacking the cpio images
> + with tmpfs.
> +
> + If unsure, say N
> +
> +config RAMFS
> + bool "Ramfs file system support" if TMPFS_ROOT
> + default y
> + ---help---
> + Ramfs is a file system which keeps all files in RAM. Unlike tmpfs,
> + it cannot be swapped to disk, and it has the risk of deadlocking
> + the system by using all memory.
> +
> + Ramfs is used for booting the system and unpacking the cpio if
> + TMPFS_ROOT is not set.
Something seems to be missing, as you add CONFIG_RAMFS, but it's nowhere used?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2008-10-16 13:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 12:03 Bodo Eggert
2008-10-16 13:10 ` Geert Uytterhoeven [this message]
2008-10-16 17:35 ` Bodo Eggert
2008-10-16 17:39 ` [PATCH] use tmpfs for rootfs v2 Bodo Eggert
2008-10-16 20:52 ` Chris Friesen
2008-10-16 22:45 ` Bodo Eggert
2008-10-16 21:03 ` Jeff Schroeder
2008-10-16 22:53 ` Bodo Eggert
2008-10-17 11:16 ` [PATCH] use tmpfs for rootfs v3 Bodo Eggert
2008-10-19 18:12 ` Mike Frysinger
2008-10-20 18:13 ` Bodo Eggert
2008-10-22 19:03 ` Mike Frysinger
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=Pine.LNX.4.64.0810161507130.25933@anakin \
--to=geert@linux-m68k.org \
--cc=7eggert@gmx.de \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®