The @boot flag wouldn't get read until config.ini is read... which isn't until the player tries to read it and is hence quite a bit after /sbin/init (or the hijack pre-init) gets run... This is why I have to have a different patch in my kernel to detect the presence of a tuner before the player starts rather than just running my previous userland program with this patch... (a work around discussed in a different thread)

With my comment about what would make use of the @boot flag I meant if it is only going to be placed in front of exec= options then I can't see when it isn't going to be wanted in front of exec=... ie it is the same issue as with my exec= vs exec_once=... unless you can think of a different config.ini option @boot would be useful in front of...?

So far running things with exec_once= seems pretty happy with my patch... the only issues I am having at the moment is from kftpd's SITE EXEC... and you could happily use it currently to start a userland launcher...

My current use is:

[hijack]
exec_once=/sbin/swapon /dev/hda6
exec_once=/drive0/bin/viewer

Cheers

Kim