From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030254AbVKCBgw (ORCPT ); Wed, 2 Nov 2005 20:36:52 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030253AbVKCBgl (ORCPT ); Wed, 2 Nov 2005 20:36:41 -0500 Received: from dsl092-053-140.phl1.dsl.speakeasy.net ([66.92.53.140]:57483 "EHLO grelber.thyrsus.com") by vger.kernel.org with ESMTP id S1030251AbVKCBgk (ORCPT ); Wed, 2 Nov 2005 20:36:40 -0500 From: Rob Landley Organization: Boundaries Unlimited To: "Alexander E. Patrakov" Subject: Re: tmpfs (documentation?) bug Date: Wed, 2 Nov 2005 16:58:57 -0600 User-Agent: KMail/1.8 Cc: "Alexander E. Patrakov" , LKML References: <436847DD.5050504@ums.usu.ru> <4368485C.3050505@linuxfromscratch.org> In-Reply-To: <4368485C.3050505@linuxfromscratch.org> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511021658.57552.rob@landley.net> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.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