Simple test I tried in a test chroot image area: user@host:~/build$ fakechroot user@host:~/build$ chroot test.image Segmentation fault user@host:~/build$ chroot test.image /lib/ld-linux.so.2 /bin/bash user@host:/$ ls Segmentation fault user@host:/$ /lib/ld-linux.so.2 ls ls: error while loading shared libraries: ls: cannot open shared object file: No such file or directory user@host:/$ /lib/ld-linux.so.2 /bin/ls bin debootstrap etc lib proc sbin sys usr boot dev home mnt root selinux tmp var user@host:/$ exit
So, something along these lines is possible. I suspect using the chroot's version of ld-linux.so.2 is a better bet than trying to use the system's libc.so. The one question is, the original argv[0] can be stashed in the environment, but can argv[0] be swaped out by a LD_PRELOAD library? -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | [email protected] PGP F6B23DE0 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ 2477\___\_|_/DC21 03A0 5D61 985B <-PGP-> F2BE 6526 ABD2 F6B2\_|_/___/3DE0 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
