__

two sides/faces

to promiscuOS project across range of instances:

• 0] a totally handcoded OS embodying design principles below - Unix bias of small apps and pipes.

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

possibly also expressed as:

• 1] divide of functional found object(system) and custom code (for example a VM ranging across the entire application space
• 2] kernel and user space divide
• 3] functional and dysfunctional (restating zero) - applications failing on a (non sandboxed) system. the flipside, a sandboxing, replacing the original existent.
• 4] automated self-display and promiscuous code generation sitting against collaborative VM/any language coding (example app would be shbuf running with Distel:

http://fresh.homeunix.net/~luke/shbuf/

[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)