From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: CONFIG_RAMFS in 2.4.19-pre7-ac2 ???
Date: 22 Apr 2002 12:43:41 -0700 [thread overview]
Message-ID: <aa1p5d$qki$1@cesium.transmeta.com> (raw)
In-Reply-To: <3CC1A1EF.AF524412@kegel.com>
Followup to: <3CC1A1EF.AF524412@kegel.com>
By author: Dan Kegel <dank@kegel.com>
In newsgroup: linux.dev.kernel
>
> Roy wrote:
> > After upgrading to 2.4.19-pre7-ac2, I can't get CONFIG_RAMFS
>
> Gee, I hope CONFIG_RAMFS isn't going away. I need it to
> do loopback mounts of cramfs on an embedded system that
> uses tmpfs as its main filesystem. (tmpfs doesn't support
> loopback mounts.)
>
CONFIG_RAMFS is probably going away, but that doesn't mean ramfs is
going away. At least in Linux 2.5 ramfs will end up being required
core code.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-04-22 19:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-20 17:14 CONFIG_RAMFS in 2.4.19-pre7-ac2 ??? Dan Kegel
2002-04-20 20:56 ` Dan Kegel
2002-04-21 16:11 ` Roy Sigurd Karlsbakk
2002-04-22 19:43 ` H. Peter Anvin [this message]
2002-04-23 11:43 ` Roy Sigurd Karlsbakk
2002-04-23 12:01 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2002-04-20 16:51 Roy Sigurd Karlsbakk
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='aa1p5d$qki$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--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