see crash for future 2006 crash event:
crash will exercise rigourous development of the concerns of the first crash event [London 2005] post-crash (endodata, post-software, neo-constructivism, auto destruction) taking place in a single venue with a different approach; more discussion, performative emphasis to all components, and finegrained input from participants within the conceptual context.
There will be an open call together with a very honed list of invited speakers, demonstrators and artists [including Bruno Marchal, David Deutsch, Friedrich Kittler, Olga Goriunova].
A format of parallel performances/presentations with screenings will disinter crash's rich thematics across a range of spaces, along with additional exterior distributed crash +sub events [walks, talks, workshops] to be programmed around the main event.
older crash notes:
ontology of system/computer crash (-to do)
was be presented as paper at:
http://crash.1010.co.uk - crash symposium/noise event london feb 11th
repository for diverse thoughts and notes after chunks
that paper could be written as software - as functionalities such as node or compression - as mechanisms including that of chunking itself - that we should make no differentiation between paper and (a piece of) software
one thread is simplistic examination of what is implied by a crash. other thread is (supposedly anthro principle - but why such a principle comes about without generali sing - fine to say this is such and such from what perspective?) following pkd, fassbinder (welt am dreht/ world on a wire - based on galouye's simulacron-3 - remade as 13th floor) - reality as a simulation, as a hologram http://twm.co.nz/hologram.html - also note that these are films - link film/computer/simulation/ cgi blah
[ to tie two threads together - fact of the exposure of the simulation - there is only exposure ???? un-showable - revelation]
code exposure types of crash - freeze, bluescreen , oops (OS errors), program crash (relation to OS of such a crash), return to …
→ operating system - is what?
+ types of OS - research into first operating systems http://www.cs.gordon.edu/courses/cs322/lectures/history.html
monolithic operating system - on one hand is single state machine but abstraction implies possible division/multiplicity
state machine - relation to schizophrenia
(notes) - what is X forfunctionality removed / computer as mistaken database functionality
whether geological approach to computing is relevant here p.o.v crashes = ill formed > crash/error/not found messages programmed by program [no necessary nor sufficient condition exigesis]
crash > perturbation - x/or - scale theory
formal: error correcting codes [in noisy probabilistic channels > see shannon coding/converse coding]
exposure to error > i] propogate through autonomous layers [error rectified by layer by layer anlysis] ii] modular nodal components, error propogated through one node [rectifying nodes difficult]
———definitions:
fault - violation of systems [os, hardware, running apps] underlying assumptions error - internal data state that reflects fault > explicit + escaping errors failure - externally visible deviation from specifications
OS + VM
> designed abstract layer for user/programmer that manage [organise/schedules processes] in underlying
hardware/basic system + running apps. > designed to hide problems > hide architecture [but not crashes]
hardware < > kernel < > shell < > apps
[user interface = HCI - GUI/shell> combines with hardware/loware system through kernel]
VM virtual memory [allows software to run in memory address not tied to physical memory space > so hardware generates virt. add. as read add. > allows cpu/memory multip lexing > can run program when physical memory size exceeded [+ protects OS frm erroneous app code]
craSH - when OSapp stops performing expected function stops responding to other parts of the system > effects kernel + may crash OS abstractions + crash > ad hoc strategies eg. "autosave" implemented to hide degree of failure in underlying system [loss of non-file states + processes . ie. user lo ses interactive state [eg. edit mode, cursor position etc], recent changes etc
ORPHANED
Messages > [user output event message] > programmed > ? necessary causal relation between error message + error
1] computations = processes/tasks 2] messages = output event/message visible to user
1] = recovery of crash take place in computation level [process/task resource managed by OS] without manifestation of message 2] > a computation that has no message can never be inconsistent because consistency is abstracted measure at level of HCI > recovery only synonomous with no-fail state iff visibility [V1] is = last message/no- fail state [V] ie. identity equivalence requirement of 2] [where seq. messages/gui is equiv. seq. messages/gui in no-fail state >> though how manifested in 1] is not i mportant because the plain of consistency need only operate at 2]]
ie. V is the plane of committment BETWEEN 1] + 2] where V1 = V [in 2], but where recovery 1] state not required = no-fail 1] state]
committments are processes committed by preceding process in 1] and can be non-deterministic [ie.a transition from a state which has multiple next states possible] orphan = a process that causally depends on an aborted non-deterministic process [ie. no reboot + cyclically fail loop] [where LOG operates > reboot > process @ pre-crash = non-deterministic, @ post-crash = deterministic]
if remove 2] then is non-deterministic only, committment is at plane of consistency in 2] not 1] where is teleological operator [performance related to amount of commit tments visible in 2]]orphange is possible description of a process 1] where strongly linked to 2]; as uncommitted, non-deterministic process [stateless]
i]Future OS design of failure transparency > so OS appears pause and consistent recovery wout user/programmer knowledge/intervention or ii] loss of OS abstractions > user/programmer blind [non-causal teleology] 02.11 autism + crash many isoconic states multi-conjugate states quantum entanglement ----------------------------- *
*07.11 mh*
within history of universe as computation 2 points providing information:
a)los alamos as birth of model applied to universe - computation - input of information theory, entropy and new theory of computation within simulation atomic blah (now)
b) subsequent theory of universe as computer (quantum physics) with 10 megaton h bomb as ultimate contemporary computer
inverse time-line possibly of gravity's rainbow compressing that history
crash/extrusion-revelation and in-turn on fissure of decidability
that given field of equivalance of hardware and software (see re-configurable computing in hardware - some notes to insert here) OS only considered as management and securing of economies/resources in any field - what are consequences of this for crash notion?
see reconfig-hardware?
notes:
drift > leakage of ill formed expressions . iterated > drift in language
ill formed becoming wff [well formed formula] expression [this not frm predicate logic]
[plaquette relations > xpand > medical: abnormal patch on the skin or other organ or tissue.]