From: Andrew Morton <akpm@linux-foundation.org>
To: linux-fsdevel@vger.kernel.org
Cc: bugme-daemon@bugzilla.kernel.org, matimatik@gmail.com
Subject: Re: [Bugme-new] [Bug 12843] New: add mount option 'mode' to ramfs same as tmpfs
Date: Mon, 9 Mar 2009 14:52:19 -0700 [thread overview]
Message-ID: <20090309145219.1bd7072c.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-12843-10286@http.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Sun, 8 Mar 2009 14:16:13 -0700 (PDT)
bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=12843
>
> Summary: add mount option 'mode' to ramfs same as tmpfs
> Product: File System
> Version: 2.5
> KernelVersion: any
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: enhancement
> Priority: P1
> Component: Other
> AssignedTo: fs_other@kernel-bugs.osdl.org
> ReportedBy: matimatik@gmail.com
>
>
> Latest working kernel version:
> Earliest failing kernel version:
> Distribution:
> Hardware Environment:
> Software Environment:
> Problem Description:
>
> I use ramfs instead of tmpfs for /tmp because I don't use swap on my laptop.
> Some apps need 1777 mode for /tmp directory, but ramfs does not support 'mode='
> mount option. I'll be happy if I shall not invent workarounds for this small,
> but offensive truble. I think this feature (mode=) will not increase code too
> much and is not too hard to implement, but will be very usefull.
>
A feature request!
next parent reply other threads:[~2009-03-09 21:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-12843-10286@http.bugzilla.kernel.org/>
2009-03-09 21:52 ` Andrew Morton [this message]
2009-03-11 7:56 ` [Bugme-new] [Bug 12843] New: add mount option 'mode' to ramfs same as tmpfs Wu Fengguang
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=20090309145219.1bd7072c.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=matimatik@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.