Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758934AbZFMQAM (ORCPT ); Sat, 13 Jun 2009 12:00:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753600AbZFMP75 (ORCPT ); Sat, 13 Jun 2009 11:59:57 -0400 Received: from mail2.shareable.org ([80.68.89.115]:56098 "EHLO mail2.shareable.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751766AbZFMP74 (ORCPT ); Sat, 13 Jun 2009 11:59:56 -0400 Date: Sat, 13 Jun 2009 16:59:57 +0100 From: Jamie Lokier To: Marco Cc: Linux FS Devel , Linux Embedded , linux-kernel@vger.kernel.org, Daniel Walker Subject: Re: [PATCH 00/14] Pramfs: Persistent and protected ram filesystem Message-ID: <20090613155957.GA16220@shareable.org> References: <4A33A7A2.1050608@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A33A7A2.1050608@gmail.com> User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 905 Lines: 22 Marco wrote: > Linux traditionally had no support for a persistent, non-volatile > RAM-based filesystem, persistent meaning the filesystem survives a > system reboot or power cycle intact. The RAM-based filesystems such as > tmpfs and ramfs have no actual backing store but exist entirely in the > page and buffer caches, hence the filesystem disappears after a system > reboot or power cycle. Why is a ramdisk not sufficient for this? Why is an entire filesystem needed, instead of simply a block driver if the ramdisk driver cannot be used? It just struck me as a lot of code which might be completely unnecessary for the desired functionality. -- Jamie -- 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/