Well, the hijack code actually waits until the player s/w is initializing before reading in the config.ini (it gets read automatically, by the way). That way, we know the partitions must already be mounted by whatever mounts them (/sbin/init).

So the code is there already, TESTED (rare for me..), and there are some nice big comments pointing out where to insert code to parse the file -- hijack.c just reads the entire file into an allocated char[] buffer.