--> ap/xxxxx


two sides/faces

to promiscuOS project across range of instances:

ref: http://download.plt-scheme.org/mzscheme/mz-103p1-bin-i386-kernel-tgz.html

possibly also expressed as:


[look into further for processes and networking in Emacs Lisp using Distel: http://fresh.homeunix.net/~luke/distel/]

where do we arrive? to specify an architecture of pipes, leaks and pools - shared, networked and promiscuous with intentional and automated data and code generation, network transport and sloughing off of neighbouring data. transparent, non-segmented memory as an option. how would this look and how far do we go in specifying the environment (see 0 above)