__

PromiscuOS notes2: (2006.12.05:2 promiscuOS_notes#3 research#116)

1] Simple Grid Protocol (which certainly is simple) - runs on CLisp and consists of network code, querying, and eval.

/etc/services and then inetd start cpur.lisp. Tracking (server) and notify (process) maintain local list of IPs for code import/eval.

but eval doesn't give us a shared/promiscuous environment.

...for promiscuOS we need to maintain a list of local and otherwise promiscuOS'ers - exported to a central accessible list which can be downloaded regularly. zeroconf for local.

2] obvious differentiation between promiscuOS'ers and code environment of other machines/networks which equally well be probed and executed.

3] extent of VM layer if we modify kernel and strip down overlying OS

• a split approach apps/environment as is and VM - set of code-promiscuous apps written in CL, Python and so on

further paper circuit: (2006.12.05:1 paper#1 research#115)

embedding 40106 invertor/Schmitt trigger:

ogg vorbis recording:

http://plot.bek.no/~crash2005/paper1_12_2006.ogg