[cap-talk] E persistence & MinorFs private storage

Mark Miller erights at gmail.com
Mon Jul 21 02:29:06 CDT 2008

On Sun, Jul 20, 2008 at 6:17 AM, Rob Meijer <capibara at xs4all.nl> wrote:

> Note: the text below is currently unvalidated !
> MinorFs provides private storage to pseudo persistent processes. The E
> language is an object capability language that provides persistent VATs.
> Given that a persistent VAT is tied to a file on disk, having the file on
> disk made private to the pseudo persistent process by storing it under the
> /mnt/minorfs/priv/home directory should help persistent E VATs in keeping
> their state and capabilities protected at the OS process level of
> granularity.
> An other concern with E ar the OS process level of granularity might be
> leakage of authority through the trace files that E creates. It might be a
> good option to set the "TraceLog_dir" option in /usr/local/e/eprops.txt to
> /mnt/minorfs/priv/home if leakage of authority by means of the tracelog
> might constitute a concern.
> ---------------------------------------------------------------------------
> Given my currently still limited understanding of persistence in E, the
> abouve might be completely based on my misconceptions.
> Anyone with a good understanding of E persistence, please feel free to
> edit the wiki page, and possibly add a simple example.

Hey Rob, this all looks good. Thanks.

Text by me above is hereby placed in the public domain

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.eros-os.org/pipermail/cap-talk/attachments/20080721/2338afa1/attachment.html 

More information about the cap-talk mailing list