Well when squash becomes good enough of a port to stand on it's own, will having squash named '/empeg/bin/player' and having squash read 'config.ini' be sufficient to trigger the kernel?

Even so, what if I still want to use a script to launch squash (It makes the most sense to use other small utitlites to do one-time things like setup the network card, etc.). So the kernel would need to be modified. How receptive are hijack patches? No point in making on if I'll be the only one with that kernel.

Oh I just thought of something I will try. I wonder if I issue a shell command (not like cat) to read config.ini would work. The problem with the shell script seems to be that hijack doesn't detect children reading config.ini only the parent process. I'll try this out soon.