SJ, To date, /security is used by the initramfs and firmware to store the developer key and activation lease. We also considered using it to communicate with the initramfs, e.g. to install a developer key found on a USB key but this has not been implemented.
/activities arose to be Rainbow's 'spool directory', in which it records resource reservations (for uids and gids) and in which it stores the filesystem skeleton (home dirs, instance dirs, data dirs, and tmp dirs) used by the activities it is launching. Some details of /security are scattered throughout http://wiki.laptop.org/go/Firmware_Security Also, a decent idea of how the spool is constructed and used can be gleaned from the links in http://wiki.laptop.org/go/Taste_the_Rainbow#Activity_Launching specifically the configure_home() function and the check_spool() function at http://tinyurl.com/ys2nsb Does this suffice to satisfy your curiosity? Michael On Wed, Jan 02, 2008 at 09:13:15PM -0500, Samuel Klein wrote: > Michael, > > Can you point me to docs that lay out what /activities and /security > semantics are meant to be? > > Thanks, > SJ _______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel