From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030416AbVKCSgz (ORCPT ); Thu, 3 Nov 2005 13:36:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030417AbVKCSgz (ORCPT ); Thu, 3 Nov 2005 13:36:55 -0500 Received: from dsl092-053-140.phl1.dsl.speakeasy.net ([66.92.53.140]:46555 "EHLO grelber.thyrsus.com") by vger.kernel.org with ESMTP id S1030416AbVKCSgy (ORCPT ); Thu, 3 Nov 2005 13:36:54 -0500 From: Rob Landley Organization: Boundaries Unlimited To: Hugh Dickins Subject: Re: tmpfs (documentation?) bug Date: Thu, 3 Nov 2005 12:36:35 -0600 User-Agent: KMail/1.8 Cc: "Alexander E. Patrakov" , "Alexander E. Patrakov" , LKML References: <436847DD.5050504@ums.usu.ru> <200511021658.57552.rob@landley.net> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200511031236.35452.rob@landley.net> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thursday 03 November 2005 08:41, Hugh Dickins wrote: > On Wed, 2 Nov 2005, Rob Landley wrote: > > 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? > > Sorry about that. I guess you'll have to do the unaesthetic > > mount -t tmpfs -o nr_blocks=1 tmpfs /mountpoint > echo full >/mountpoint/.full Hmmm... I suppose as long as I have the sucker mounted "noexec" I can live with that. Rob