On 8/16/06, Jeff Angielski <jangiels at speakeasy.net> 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 at secretlab.ca (403) 399-0195
