Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 13 Dec 2001 13:14:30 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 13 Dec 2001 13:14:19 -0500 Received: from vsat-148-63-243-254.c3.sb4.mrt.starband.net ([148.63.243.254]:260 "HELO ns1.ltc.com") by vger.kernel.org with SMTP id ; Thu, 13 Dec 2001 13:14:03 -0500 Message-ID: <07cd01c18401$fa397db0$5601010a@prefect> From: "Bradley D. LaRonde" To: Cc: "Thomas Capricelli" , In-Reply-To: Subject: Re: Mounting a in-ROM filesystem efficiently Date: Thu, 13 Dec 2001 13:14:16 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org ----- Original Message ----- From: "Richard B. Johnson" To: "Bradley D. LaRonde" Cc: "Thomas Capricelli" ; Sent: Thursday, December 13, 2001 1:02 PM Subject: Re: Mounting a in-ROM filesystem efficiently > Generally, ROM based stuff is compressed before being written to > NVRAM. It's uncompressed into a RAM-Disk and the RAM-Disk is mounted. > > That way, you can use, say, 2 megabytes of NVRAM to get a 10 to 20 > megabyte root file-system. This also allows /tmp and /var/log to be > writable, which is a great help because the development environment > closely approximates the run-time environment. That's perfect if you have plenty of RAM to spare. > FYI, generally NVRAM access is sooooo slow. I don't think you'd > like to use it directly as a file-system and access-time will be > a problem unless you modify the kernel. Modify the kernel how? Regards, Brad - 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/