[Angstrom-distro-users] angstrom directory structure

[Rick & Geannitta Jones]

At 02:25 AM 10/5/2006, Guylhem Aznar <guylhem at guylhem.net> wrote:

>On 10/5/06, Rick & Geannitta Jones <ephesians521 at cox.net> wrote:
>>I would like to see a layout where :
>>
>>1) / in NAND partition 1(containing /bin, /sbin)
>>2) /root in NAND partition 2
>
>RThat was reasonnable in the past. No longer now. A single partition
>avoids filling up one while having too many empty space in the other.

Having one partition seems fine to me also for those paths in 
particular.  I think you're right.


>>3) executables and configuration files can be in /bin, frequently
>>manipulated data files should never be stored in NAND (but links can
>>point to data outside of NAND)
>>4) /tmp, /var, /opt, /home should be on the microdrive if available
>>(preferably in the same partition (ext2/3)) partition 1
>
>tmp -> var/tmp and var in a ramdisk or tmpfs
>home in the microdrive makes sense

>>6) optional swap partition (partition 2)
>
>useless

Thanks for mentioning /var, /tmp->/var/tmp.  For a 2.6 kernel, tmpfs 
is the way to go provided it doesn't take too much memory.  Ramdisks 
don't resize... tmpfs will free up memory as it's contents are 
removed.  This is why I was wondering about an optional swap that 
could be activated if memory started to become full.  But I'm not 
familiar with the software demands.. I have heard of people using 
firefox, gimp.. and other memory consumptive apps on the 
zaurus.  What are the typical memory demands of firefox?


>Seems to be like a normal setup, and very sensible too

3) executables and configuration files can be in /bin, frequently
manipulated data files should never be stored in NAND (but links can
point to data outside of NAND)

One file I would like to point out is mtab (in /etc I think).  This 
file modified frequently by mounts.  /etc could be in NAND if this 
and other frequently modified files are linked to files in an 
/alt/etc on the microdrive.  This also brings up some interesting 
possibilities for having an /alt/var on the microdrive where 
persistant /var files and directories are stored - a script could set 
up the links after /var is set up in tmpfs.

Rick