Messages in this thread | | | From | Rob Landley <> | Subject | Re: tmpfs (documentation?) bug | Date | Wed, 2 Nov 2005 16:58:57 -0600 |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |