Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1763480AbXJEPno (ORCPT ); Fri, 5 Oct 2007 11:43:44 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1761332AbXJEPnb (ORCPT ); Fri, 5 Oct 2007 11:43:31 -0400 Received: from extu-mxob-2.symantec.com ([216.10.194.135]:62077 "EHLO extu-mxob-2.symantec.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760395AbXJEPna (ORCPT ); Fri, 5 Oct 2007 11:43:30 -0400 Date: Fri, 5 Oct 2007 16:43:17 +0100 (BST) From: Hugh Dickins X-X-Sender: hugh@blonde.wat.veritas.com To: Guennadi Liakhovetski cc: linux-kernel@vger.kernel.org Subject: Re: tmpfs disabled in .config but in /proc/filesystems In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 736 Lines: 19 On Fri, 5 Oct 2007, Guennadi Liakhovetski wrote: > Am I running crazy here (some 2.6.23-rc6-ish)? > > $ zcat /proc/config.gz | grep TMPFS > # CONFIG_TMPFS is not set > $ grep tmpfs /proc/filesystems > nodev tmpfs tmpfs (mm/shmem.c) is used by the kernel to support shared memory of various kinds even when CONFIG_TMPFS is not set. But only when CONFIG_TMPFS=y can users mount a tmpfs as a fully capable filesystem. Confusing, yes: sorry for putting the fear of craziness upon you. Hugh - 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/