Process forking, signal handling, socket communication and race conditions. If I smoked I would have gone through a carton today.

A game taking place inside an operating system. Like Tron but needs to have much more solid analogies. User's body as tty process. Some representation of scheduler priority and memory allocation. Forking. Children and zombies. Init.

Some process-ownable token representing file handles.

Network ports as portals through which data may be sent by acquiring a file handle and using it.

/proc, /mem, etc are extreme stretch goals.

Never really started because I couldn't decide how to represent all the different parts so they would all be consistent *and* entertaining

As an extension of the extreme stretch goals, a multiplayer functionality where players can shell into each other's game worlds ("computers")

Trying to explain to (a more experienced) dev why it's not a god idea to do a exec( php '/var/www/xxx >> /dev/null) and then redirect the visitor.

The script is running a query that take some time and he want's to redirect the visitor and then fetch the result with jquery.

Tried to explain parent and child processes and pointed him in the direction with pipes and bakground process. After some discussion about forking and all the cons with that.

yes its PHP ;)

Gonna be exiting to see his next idea :S

while(1) fork();