From: Miles Bader <miles@lsi.nec.co.jp>
To: Stephen Smalley <sds@epoch.ncsc.mil>
Cc: Greg KH <greg@kroah.com>, Christoph Hellwig <hch@infradead.org>,
James Morris <jmorris@redhat.com>, Andrew Morton <akpm@osdl.org>,
Alexander Viro <viro@parcelfarce.linux.theplanet.co.uk>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][7/7] add xattr support to ramfs
Date: Wed, 25 Aug 2004 16:03:09 +0900 [thread overview]
Message-ID: <buoy8k3pumq.fsf@mctpc71.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <1093346824.1800.34.camel@moss-spartans.epoch.ncsc.mil> (Stephen Smalley's message of "Tue, 24 Aug 2004 07:27:04 -0400")
Stephen Smalley <sds@epoch.ncsc.mil> writes:
> It makes no difference to me whether we use ramfs or tmpfs (I'd favor
> tmpfs myself)
What's the essential difference between ramfs and tmpfs anyway?
I've gotten the impression that ramfs is simpler and lighter-weight than
tmpfs, but doesn't have some features like resource-limiting.
If that's the case, then for something like /dev -- a small in-core
filesystem that won't have arbitrary user files plunked into it -- ramfs
seems an obvious choice.
Also, tmpfs seems to require an MMU, which not all linux systems have
(though I suppose the lack of an MMU makes many security tweaks a bit
pointless :-).
-Miles
--
Occam's razor split hairs so well, I bought the whole argument!
next prev parent reply other threads:[~2004-08-25 7:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-23 18:14 [PATCH][0/7] xattr consolidation and support for ramfs & tmpfs James Morris
2004-08-23 18:15 ` [PATCH][1/7] xattr consolidation - libfs James Morris
2004-08-23 18:16 ` [PATCH][2/7] xattr consolidation - LSM hook changes James Morris
2004-08-23 18:17 ` [PATCH][3/7] xattr consolidation - ext3 James Morris
2004-08-23 18:18 ` [PATCH][4/7] xattr consolidation - ext2 James Morris
2004-08-23 18:19 ` [5/7] xattr consolidation - devpts James Morris
2004-08-23 18:20 ` [PATCH][6/7] add xattr support to tmpfs James Morris
2004-08-23 18:22 ` [PATCH][7/7] add xattr support to ramfs James Morris
2004-08-23 20:26 ` Christoph Hellwig
2004-08-23 20:26 ` Stephen Smalley
2004-08-23 20:46 ` Christoph Hellwig
2004-08-23 20:59 ` Greg KH
2004-08-23 21:27 ` [PATCH][7/7] add xattr support to ramfs [u] Martin Schlemmer [c]
2004-08-24 0:52 ` [PATCH][7/7] add xattr support to ramfs Valdis.Kletnieks
2004-08-24 11:27 ` Stephen Smalley
2004-08-25 7:03 ` Miles Bader [this message]
2004-08-25 13:14 ` James Morris
2004-08-23 19:06 ` [PATCH][6/7] add xattr support to tmpfs Christoph Hellwig
2004-08-23 19:03 ` [PATCH][2/7] xattr consolidation - LSM hook changes Christoph Hellwig
2004-08-23 19:06 ` James Morris
2004-08-23 19:13 ` Stephen Smalley
2004-08-24 0:54 ` James Morris
2004-08-24 2:52 ` viro
2004-08-24 19:27 ` Andreas Gruenbacher
2004-08-23 23:28 ` Andreas Dilger
2004-08-23 18:49 ` [PATCH][1/7] xattr consolidation - libfs Christoph Hellwig
2004-08-24 4:32 ` James Morris
2004-08-24 10:05 ` Christoph Hellwig
2004-08-24 19:42 ` Andreas Gruenbacher
2004-08-24 20:19 ` James Morris
2004-08-24 19:41 ` [PATCH][0/7] xattr consolidation and support for ramfs & tmpfs Andreas Gruenbacher
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=buoy8k3pumq.fsf@mctpc71.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miles@gnu.org \
--cc=sds@epoch.ncsc.mil \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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®