My question now becomes:-
What can prevent register_misc_runner registering any runners, after
I install new scratchbox binaries?
On my scratchbox installation which can run binaries in my target:-
[ppearse]# ls -l /proc/sys/fs/binfmt_misc
total 0
--w------- 1 root root 0 Apr 17 02:13 register
-rw-r--r-- 1 root root 0 Apr 17 02:13 sbox-arm
-rw-r--r-- 1 root root 0 Apr 17 02:13 sbox-armeb
-rw-r--r-- 1 root root 0 Apr 17 02:13 sbox-cris
-rw-r--r-- 1 root root 0 Apr 17 02:13 sbox-mips
-rw-r--r-- 1 root root 0 Apr 17 02:13 sbox-mipsel
-rw-r--r-- 1 root root 0 Apr 17 02:13 sbox-powerpc
-rw-r--r-- 1 root root 0 Apr 17 02:13 sbox-sh
-rw-r--r-- 1 root root 0 Apr 17 02:13 sbox-sparc
-rw-r--r-- 1 root root 0 Apr 13 18:33 status
On the one that cant:-
[work]# ls -l /proc/sys/fs/binfmt_misc
total 0
-r-------- 1 root root 0 Apr 16 14:16 register
-rw-r--r-- 1 root root 0 Apr 16 14:16 status
Peter
_______________________________________________
Scratchbox-users mailing list
[email protected]
http://lists.scratchbox.org/cgi-bin/mailman/listinfo/scratchbox-users