From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by ozlabs.org (Postfix) with ESMTP id 3556367B6F for ; Thu, 17 Aug 2006 09:28:56 +1000 (EST) Received: by ug-out-1314.google.com with SMTP id e2so342916ugf for ; Wed, 16 Aug 2006 16:28:54 -0700 (PDT) Message-ID: <528646bc0608161628t2dc068d0g8862d8e8dd202170@mail.gmail.com> Date: Wed, 16 Aug 2006 17:28:54 -0600 From: "Grant Likely" Sender: glikely@gmail.com To: "Jeff Angielski" Subject: Re: Linux hanging on Xilinx SystemACE In-Reply-To: <1155766078.10357.16.camel@sumo-jaa> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed References: <3C02138692C13C4BB675FE7EA240952918DBED@bluefin.Soneticom.local> <1155766078.10357.16.camel@sumo-jaa> Cc: linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 8/16/06, Jeff Angielski wrote: > And like somebody else mentioned, if you are really going to use this > for an embedded system, you are going to want to rethink your > partitioning scheme. > > Maybe something like: > > p1 fat12 - kernel and binary image > p2 ext2 - read only rootfs > p3 ext3 - non volatile, slow rate data rootfs > p4 tmpfs - volatile, high rate data rootfs Or, if you have enough ram (and a small enough rootfs footprint); put the rootfs into an initramfs and leave the CF alone entirely after boot. On small systems, I store all config parameters in a flat file on the fat partition, and only write it out when it needs to save a new configuration. That way the entire system consists of three files; a kernel, a rootfs image and a config file. Makes managing updates very easy. :) g. -- Grant Likely, B.Sc. P.Eng. Secret Lab Technologies Ltd. grant.likely@secretlab.ca (403) 399-0195