[Angstrom-distro-users] angstrom directory structure

[Rick & Geannitta Jones]

I'm used to linux configurations on pc's.  I'm planning on purchasing 
a C3200 soon.

I was working on a mobile system and resigned it's development in 
favor of a more convienient, almost as powerful, C3200.  In designing 
my system I studied read-only systems, jffs2, unionfs...  much of 
this I see as being very pertinent to the zaurus platform.

I've been reading about several distributions and have read about the 
directory structures being fairly convoluted (particularly Sharps - 
which includes Cacko).  pdaXrom appears to require users and security 
to be added - but it's fast and takes advantage of the NAND (to 
uncertain risk, at this point).  I'm not sure if this is why Angstrom 
has avoided NAND, but it's  a reasonable one until the proper 
configuration is established.  I know a few tricks but with these 
altered configurations ... /home/root/bin???  It makes me wonder how 
simple it is to implement the configuration I have in mind.

Also how does Angstrom handle /devfs, /proc with the 2.6 kernel.  Are 
these in a tmpfs?

I would like to see a layout where :

1) / in NAND partition 1(containing /bin, /sbin)
2) /root in NAND partition 2
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
5) /usr could be in NAND or microdrive depending how the above rules are used
6) optional swap partition (partition 2)
7) third microdrive partition for vfat (usb access)(partition 3)

How complicated would this be to configure... does anyone know how 
this compares to  other distributions (most of which it looks like 
I'd have to move or link some in the microdrive).

Any insight  of the distributions... Timeline of a decent beta of 
Angstrom... Is there any reason the above structure won't work???  I 
think this configuration would reduce the porting necessary 
(especially for the C3100 and C3200).