From: Christoph Hellwig <hch@infradead.org>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: CONFIG_RAMFS in 2.4.19-pre7-ac2 ???
Date: Tue, 23 Apr 2002 13:01:11 +0100 [thread overview]
Message-ID: <20020423130111.A14849@infradead.org> (raw)
In-Reply-To: <aa1p5d$qki$1@cesium.transmeta.com> <Pine.LNX.4.44.0204231341480.10981-100000@mustard.heime.net>
On Tue, Apr 23, 2002 at 01:43:23PM +0200, Roy Sigurd Karlsbakk wrote:
> > 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.
>
> According to what I was told by a guy at #KernelNewbies, CONFIG_RAMFS
> isn't there in (menu|x)?config after -pre7, but in by default. problem is
> - it doesn't work
fs/Config.in (2.4.19-pre7):
define_bool CONFIG_RAMFS y
[root@sb root]# uname -a
Linux sb.bsdonline.org 2.4.19-pre7-rmap13 #1 SMP Mon Apr 22 22:04:13 CEST 2002 i686 unknown
[root@sb root]# mount -tramfs none /mnt/
[root@sb root]# cp ~/mcslock.h /mnt/
[root@sb root]# ls -l /mnt/
total 0
-rw-r--r-- 1 root root 1275 Apr 23 14:58 mcslock.h
[root@sb root]#
next prev parent reply other threads:[~2002-04-23 12:01 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
2002-04-23 11:43 ` Roy Sigurd Karlsbakk
2002-04-23 12:01 ` Christoph Hellwig [this message]
-- 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=20020423130111.A14849@infradead.org \
--to=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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