--> ap/xxxxx

* __

and more pipes: (2007.01.22:3 pipes#2 research#4)

1] tee and tpipe app

2] using lsof to find open pipes and then cat file descriptor a la cat /proc/18952/fd/29

see also:

http://www-128.ibm.com/developerworks/aix/library/au-lsof.html

http://www.vias.org/linux-knowhow/bbg_sect_08_02_03.html

http://www.math.temple.edu/~rivin/software/schemeprogs/bipipes.sc

pipes and pipes... (2007.01.22:2 pipes#1 research#3 workshop_notes#1)

for workshopping also:

1] Listenpipe: http://www.vanheusden.com/listenpipe/ - lp01

2] Pd. piperead~ and pipewrite~ externals and our sample patches for plenum

3] pipes in ap0202 software

4] pipes in our own commandline software: OSC, neuronal, devdisplay, jekyll software

5] pipes in promiscuOS: promiscuOS_notes#7 (pipe.c in the kernel)

6] pluggability: plugging

7] pipes and process: OS -

pipes p.776+ (Understanding Linux Kernel) also the pipe code we found: lp-01 which copies file descriptors (pipe is only accessible to parent process). FIFO allows for arbitrary piping and is associated with a kernel buffer.

8] proposed leaking pipes and pools

9]

lsof | grep FIFO

10] (netcat) and for workshop:

1) basic understanding GNU/Linux and networking:

d) cat, dd and ls

i) what are pipes and how they work

j) what is a FIFO and how we can use named pipes

3) audio on Linux

a) what is a device?

b) what is /dev/dsp and how we can input and output on the command line

c) how we can use stuff like cat with /dev/dsp

d) what is sample rate. 8 bit/16 bit audio

3) netcat and pd

a) is basically networked cat but need to understand ports

b) maybe also pd in relation to netcat and pipes

c) how we can interface ap to pd

see also unix