Linux

More Thoughts on Clone

I’ve recently mentioned my issues with clone(), though I stopped short of proposing something better. A big part of that is that if I were to propose something better, I’d have to address the other major issues with process creation on *nix.

Clone Needs a Better Wrapper

The clone system call needs a better wrapper, at least on Linux. See, you might have heard about this neat containers thing. Run processes with some actual separation and (the start of) security! Let yourself feel the freedom! And they’re great… as long as you’re not calling the libc functions yourself.

disabling irq 18

I use Linux (with KDE) as my primary desktop, and I have done so or years. I have written SysV, Upstart, and systemd init scripts/units/whatever. I know what a udev rule is and how to write them. I’ve mucked around with kernel modules, and I’ve dipped my toe into kernel development once or twice. And I have no friging clue what’s going wrong with my computer. At random, as often as a half hour apart or with weeks in between, I get a line like: