initial idea about oscp was 'no or minimal deps', setting build tree to be that way would need packages in the size of tens of megs, or splitting them in subparts, which again would be 'Requires:' hell

as for the possible commands check this file:
http://sourceforge.net/projects/oscp...e.txt/download
command protocol doesn't provide loading arbitrary paths, only numbers from the list sent earlier from core to remote. the worst someone could do would be changing volume or track. and think about it, n900 usually is connected to home wifi network or gsm (no external ip). still, yes, acl is on the TODO.