--> ap/xxxxx


Switch/CPU execution tested using: (switch#5)


[TODO: integrate with cur-rme - collect 16 8-bit values and send to switch - only send when 16 is way to get stepping - test on t20 in hdsp backup directory with rme code uncommented]

free software and gnosticism - code exposure and light (makeart_notes#1)

black-box economy

no open source/no algorithms and restricted view of live coding/computation but rather software as an active descriptive means untethered from ownership (an interning)

free software goes some way towards the description of another economy

Philip K Dick: pink light - see trilogy

Thomas Pynchon: light and doubling - a spectral realm (the future past the entropic)

find quotes



To begin with light:

1] ap/xxxxx - a journey from free software to open hardware

from description to making

a fictional history of ap/xxxxx (in software. in description)

speculative hardware:

How speculative, open hardware can operate, be imagined along an expressive line of (to be exposed) functionality - a reasoning in the evident, the means of description (software) and the EXISTENT.

2] the CPU is mapped over the world (where that execution happens):

the forest clearing (Heidegger)

We call this openness that grants a possible letting-appear and show 'opening.' In the history of language the German word Lichtung is a translation derived from the French clairiere It is formed in accordance with the older words Waldung [foresting] and Feldung [fielding].

The forest clearing [or opening] is experienced in contrast to dense forest, called Dickung in our older language. The substantive Lichtung goes back to the verb lichten. The adjective licht is the same word as 'open.' To open something means to make it light, free and open, e.g., to make the forest free of trees at one place. The free space thus originating is the clearing. What is light in the sense of being free and open has nothing in common with the adjective �light� which means �bright,� neither linguistically nor factually. This is to be observed for the difference between openness and light. Still, it is possible that a factual relation between the two exists. Light can stream into the clearing, into its openness, and let brightness play with darkness in it. But light never first creates openness. Rather, light presupposes openness. However, the clearing, the open region, is not only free for brightness and darkness but also for resonance and echo, for sound and the diminishing of sound. The clearing is the open region for everything that becomes present and absent.

[Martin Heidegger.The End of Philosophy and the Task of Thinking. Routledge p.441]

The CPU is the black boxed (after Edison's black mariah studio) theatre where the action takes place (also to expand further the limbs of that primal studio as our pinouts and some kind of internal sunlight, through the roof is there in the darkness - we can see all operations there; cats dancing, emotions). The script is performed and to some extent improvised (compiler and interpreter).

3] the vanishing point of the pinned-down executable

an horizon-line dividing software from hardware. again, seperating a description from an active circuit

Our model for the CPU, and the question that the idea of the CPU renders is precisely where we draw the line, where we mark a division or passage between hardware and software, a false and delirious division which could be imagined as between the analogue and the digital - the digital and/as a reining in of the analogue - not so much in terms of discretisation but of a forbidden zone.

4] CPU as pure economy/short circuit and what takes place between - in that time?

quotations for that economy: what drives the design of a computer architecture - the very design which is reflected in language and construction - in that non-transparent medium which is code

an economy of that which "does" (what does it do?)

quotations from early byte: - images

operating system is mapped over the CPU - it is that (Babel tower) of compilers, interpreters, assemblers, microcompilers, languages, of acronyms - that which hides but which are the terms of that which we find ourselves within

The operating system as entry point into the economic in all senses - economies of usability and of narrowed so-called interface (user becoming a subject of the OS, under the OS and to be coded for), economies of time-sharing (the original purpose) made plain here:

The large computer, being a very expensive resource, quickly justified the capital required to investigate optimum use of that resource. Among the principle results of these projects was the development of batch mode multiprocessing. The computer itself would save up the various tasks it had to do then change from one to the other at computer speeds. This minimised the wasted time between jobs and spawned the concept of an operating system (itals).

[Byte Magazine 1979]

(shell-command "display /root/scryer/sa4mc1.gif") ;; for example only

5] a story as software (Alice in Wonderland - we will come to)

a demonstrative history of (necessarily free) software/code - what that could be:

driven by process

The story of an Operating System (OS):

an artistic OS inspired by the free software movement

a history IN code

--- using eev and Emacs Lisp to demonstrate

how we can work with sequences - steps

(eesteps '("C-x C-f /root/Plans/promiscuOS RET" "C-x C-f /root/Plans/life_coding RET"


F12 step in eev

presentation buffer - buffer disturbed

a presentation format in Emacs Lisp - the devoted buffer where actions are directed?

or in Lisp and with SLIME but do we then not lose buffer control?

past works:

1) ap

- eev tests for channels - we want a green terminal! - or channel results should be diverted to a specific buffer

shell commands can be diverted to a specific buffer

(eebg-channel-xterm "monk") (eechannel "monk") echo 9 ls pwd



how process is made evident?

2) ap0201, ap0202, ap0204

fragmented code base - commandline tools

used to construct a performance or a text


i_am, devdisplay, jekyll, osctrans/dump,

(shell-command "cat /dev/mem/root/devdisplay 240 240 &" "makeart")

;; use C- M- u to put in corner. C- M- f to unfix mouse

(shell-command "killall -9 devdisplay")

;; (shell-command COMMAND &optional OUTPUT-BUFFER ERROR-BUFFER)


;; (start-process-shell-command NAME BUFFER COMMAND &rest COMMAND-ARGS)

3) xxxxx - a future/life coding:

the three levels (see langlois) for an artistic operating system:

a) CPU (black box text):

The CPU is concerned with the black-boxing of technology and a notion of a hidden interior, technology as an interiority.

We are interested in the idea of open hardware, and equally in a mapping of such interiority into the world as a philosophical question concerned with rationalism. The project here is concerned with a certain impossibility of exposure. Within a climate of intense (intellectual) property rights management which relies on locking the so-called user out of access to hardware the political concerns here are also important. These will be well mapped out through the documented construction in soft hardware of a functioning Central Processing Unit. The history of computing hardware will be examined in elaborating our artistic platform. Equally there is a relationship to alternative artistic hardware such as Marcel Duchamp's Large Glass and other such bachelor machines.

b) promiscuOS. software

The promiscuous operating system presents the next level in our model of abstraction proceeding from open hardware to open software. Further interrogating the political concerns of a denial of access to materiality, a politics which can easily be extrapolated from the realm of computation, such a locking-out is equally mimed by software. Users and software are heavily segregated in a universal operating system design which is haunted by the specter of the viral and thus denies the potential of active, shared and networked playful environments. Particular economies are very much present within this model of closed systems and a concern for the politics of control is essential here. This sub-project is concerned with the elaboration, in software, of an active networked operating system which exposes and interrogates control. This OS is concerned with non-functional artistic generation at socially-implied levels of code and production, favouring promiscuous, leaky code and data over security and division by function or task. The highly technical nature of some of the research here means that collaboration on a practical level is essential. This subproject will be launched as a fully-fledged open source software project to highlight the issues at stake here.

leaks demonstration in buffer

;;(require 'leaks) (leaking)

and http://www.1010.co.uk/prmscnet.el for collaborative/viral coding - remote execution and code share

promiscuOS text also:

c) wonderland environment - high level language.

The final subproject, the wonderland environment, is the most playful and perhaps loosely specified part of the artistic computing platform. The wonderland environment runs on the OS component and is primarily textual, allowing for language-based manipulation and play with networked instances of highly mobile code and data. The now active, artistic computing system embeds further social systems. The development of a relational language of description and process is implied as well as the question of a meeting between software and fiction; software above all as a means of representation rather than a tool or medium. Again, we are concerned with defining a new artistic practice which is concerned with both science and literature. The working title of a wonderland environment hints at the rich concerns here.

Alice, life coding:

closing Alice text:

A boat beneath a sunny sky, Lingering onward dreamily In an evening of July -

Children three that nestle near, Eager eye and willing ear, Pleased a simple tale to hear -

Long has paled that sunny sky: Echoes fade and memories die: Autumn frosts have slain July.

Still she haunts me, phantomwise, Alice moving under skies Never seen by waking eyes.

Children yet, the tale to hear, Eager eye and willing ear, Lovingly shall nestle near.

In a Wonderland they lie, Dreaming as the days go by, Dreaming as the summers die:

Ever drifting down the stream - Lingering in the golden dream - Life, what is it but a dream?

scrying boards (an image?)

the future: scrying boards and relation to hidden electromagnetic waves - the bringing into light and Gnosticism again

Working on a new presentation format for makeart: (makeart_tech_notes#1)

Making use of:

1] Emacs Lisp and interface to the shell by way of:

(shell-command COMMAND &optional OUTPUT-BUFFER ERROR-BUFFER)


(start-process-shell-command NAME BUFFER COMMAND &rest COMMAND-ARGS)
2] eev mode: http://www.emacswiki.org/cgi-bin/wiki/

(eesteps '("C-x C-f ~/Plans/promiscuOS RET" "C-x C-f ~/Plans/life_coding RET" )) Execute this with the usual C-x C-e and then step through this list of actions with F12 - Also hyperlinking as documented in [[emacs]] - Use as: <fontlock mode="emacs-lisp-mode"> (eebg-channel-xterm "monk") (eechannel "monk") echo 9 ls pwd Where the first two commands are executed with F9 (if we mark first with C-x C-o I think or just execute) - first opens new xterm and second attaches Emacs link and then we use F9 to send commands

eev mode as for process control, ordering and remembering but seems a bit opaque to use.

3] Goby presentation mode: http://www.mew.org/~kazu/proj/goby/index.html.en

With Edit and View mode - from edit mode we can arrange text and ordering of pages seperated by a Ctrl-L character which is input by way of C-c;l - the prefix there used throughout eg:

C-c;v to enter view (simple keys such as q to exit mode, up and down for pages in that major mode)

In Edit mode we can use Emacs Lisp and eev... and also have formatting


Next stage is to integrate with promiscuOS and also change goby defaults usw.