public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Rohland <cr@sap.com>
To: "mirabilos" <eccesys@topmail.de>
Cc: <linux-kernel@vger.kernel.org>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: ramdisk/tmpfs/ramfs/memfs ?
Date: 27 Apr 2001 15:41:35 +0200	[thread overview]
Message-ID: <m34rvah33k.fsf@linux.local> (raw)
In-Reply-To: <3AE879AE.387D3B78@antefacto.com> <Pine.LNX.3.96.1010426203656.22847A-100000@medusa.sparta.lu.se> <20010426223950.C3683@l-t.ee> <9caevn$65j$1@cesium.transmeta.com> <025f01c0cf0e$5feb1eb0$de00a8c0@homeip.net>
In-Reply-To: <025f01c0cf0e$5feb1eb0$de00a8c0@homeip.net>

On Fri, 27 Apr 2001, eccesys@topmail.de wrote:
>> > tmpfs is basically ramfs with limits.
>> > 
>> 
>> ... and swappable.
>> 
>> -hpa
> 
> Hmmm and what's shmfs? Precedessor of tmpfs?

Yes.

> I even cant remember which one I use for /tmp ;-)

You can mount tmpfs also with type "shm" for compatibility. Type "shm"
will be marked as obsolete in 2.5

Greetings
		Christoph



  reply	other threads:[~2001-04-27 13:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-26 19:40 ramdisk/tmpfs/ramfs/memfs ? Padraig Brady
2001-04-26 18:48 ` Bjorn Wesen
2001-04-26 20:39   ` Marko Kreen
2001-04-27  0:37     ` H. Peter Anvin
2001-04-27 11:32       ` mirabilos
2001-04-27 13:41         ` Christoph Rohland [this message]
2001-04-26 20:49   ` H. Peter Anvin
2001-04-26 22:25     ` Ingo Oeser
2001-04-27  9:36   ` David Woodhouse
2001-04-27 11:36     ` mirabilos
2001-06-22  8:15     ` Padraig Brady
2001-04-27 15:56   ` David Woodhouse
2001-04-27 16:19     ` mirabilos
2001-04-27 17:39     ` David L. Parsley
2001-04-27 17:53     ` Padraig Brady
2001-04-27 17:23       ` Xavier Bestel
2001-04-28 10:30     ` David Woodhouse
2001-04-27 16:23   ` Padraig Brady
2001-04-27 14:31     ` Bjorn Wesen
2001-04-27 15:38     ` Christoph Rohland
2001-04-27  7:58 ` Christoph Rohland

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=m34rvah33k.fsf@linux.local \
    --to=cr@sap.com \
    --cc=eccesys@topmail.de \
    --cc=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