Pete's Log: stupid mona
Entry #1047, (Coding, Hacking, & CS stuff)(posted when I was 22 years old.)
well, on the one hand, I really deserve punishment for the following line of code:
if ((pid_file = fopen("/.monad.pid","w")) == NULL) {
but on the other hand, I did write it like two years ago, when my system programming knowledge was still ... pathetic. So I'll forgive myself. besides, it's mona. It's meant to have things hardcoded to absurd values.
oof. Well I finally got mona compiled and running. woo. and then I wasted time adding a non-export-related feature I thought would be useful: a /proc/fs/mona directory containing a file that lists the kernel transformations available. Much easier than poking through the mona source to figure out which kernel transformations exist. woo.
It makes me sad to look at system code I wrote two years ago. It makes me even sadder that it's more readable than most of the export code that wasn't written by me.
hmmm. either I'm just not getting something, or I have discovered the stupidest thing ever: so the monad at some point is given some information by the kernel. It then creates a pipe, fork()s, and then writes the information it got from the kernel, through the pipe, to the child. the child never does an exec() or anything. So what's the point of the pipe? The child should have the information, since it was read from the kernel before the fork() occured. huh what? maybe it's some kinda efficiency thing. ha!
I've consumed 2.591 liters of mountain dew today.
I just got my first kernel panic of the night. Time to go home.