From: Rob Landley <rob@landley.net>
To: "Alexander E. Patrakov" <alexander@linuxfromscratch.org>
Cc: "Alexander E. Patrakov" <patrakov@ums.usu.ru>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: tmpfs (documentation?) bug
Date: Wed, 2 Nov 2005 16:58:57 -0600 [thread overview]
Message-ID: <200511021658.57552.rob@landley.net> (raw)
In-Reply-To: <4368485C.3050505@linuxfromscratch.org>
On Tuesday 01 November 2005 23:02, Alexander E. Patrakov wrote:
> Alexander E. Patrakov wrote:
> > Hello,
> >
> > Documentation/filesystems/tmpfs.c currently says:
> >
> > If nr_blocks=0 (or size=0), blocks will not be limited in that instance;
> > if nr_inodes=0, inodes will not be limited.
> >
> > However, mounting a tmpfs with "mount -t tmpfs -o size=0 tmpfs
> > /root/tmpfs" results in a tmpfs where only zero-sized files can live.
> > So either this behaviour should be fixed to be in accordance with the
> > documentation, or the documentation should reflect the current behaviour.
>
> Please ignore, that applies to old kernels only, not to 2.6.14.
So what's the new way to specify "this tmpfs mount should just be a directory
hierarchy with no data blocks" for those of us who _want_ the old behavior?
Rob
next prev parent reply other threads:[~2005-11-03 1:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 5:00 tmpfs (documentation?) bug Alexander E. Patrakov
2005-11-02 5:02 ` Alexander E. Patrakov
2005-11-02 22:58 ` Rob Landley [this message]
2005-11-03 14:41 ` Hugh Dickins
2005-11-03 18:36 ` Rob Landley
2005-11-02 22:57 ` Rob Landley
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=200511021658.57552.rob@landley.net \
--to=rob@landley.net \
--cc=alexander@linuxfromscratch.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patrakov@ums.usu.ru \
/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