From: Dan Kegel <dank@alumni.caltech.edu>
To: linux-kernel@vger.kernel.org, cr@sap.com
Subject: Re: shmem or swapfs? was: [Patch] make shm filesystem part configurable
Date: Sat, 13 Jan 2001 12:58:36 -0800 [thread overview]
Message-ID: <3A60C17C.3929E3F6@alumni.caltech.edu> (raw)
Albert D. Cahalan (acahalan@cs.uml.edu) wrote:
> Christoph Rohland writes:
> > I am quite open about naming, but "shm" is not appropriate any more
> > since the fs does a lot more than shared memory. Solaris calles this
> > "tmpfs" but I did not want to 'steal' their name and I also do not
> > think that it's a very good name.
>
> Admins already know what "tmpfs" means, so you should just call
> your filesystem that. I know it isn't a pretty name, but in the
> interest of reducing confusion, you should use the existing name.
>
> Don't think of it as just "for /tmp". It is for temporary storage.
> The name is a reminder that you shouldn't store archives in tmpfs.
>
> Again for compatibility, Sun's size option would be useful.
I agree with Albert; if it does the same thing as Sun's tmpfs,
let's call it tmpfs, and use the same options.
- Dan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-13 21:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-13 20:58 Dan Kegel [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-13 10:49 [Patch] make shm filesystem part configurable Christoph Rohland
2001-01-13 12:33 ` shmem or swapfs? was: " David Ford
2001-01-13 14:04 ` Christoph Rohland
2001-01-13 14:16 ` David Ford
2001-01-13 16:51 ` Christoph Rohland
2001-01-13 22:39 ` David Ford
2001-01-13 20:14 ` Albert D. Cahalan
2001-01-14 9:56 ` Christoph Rohland
2001-01-14 13:56 ` James H. Cloos Jr.
[not found] ` <20010114134457.A14486@uni-mainz.de>
2001-01-14 21:29 ` 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=3A60C17C.3929E3F6@alumni.caltech.edu \
--to=dank@alumni.caltech.edu \
--cc=cr@sap.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