/me just wondering about the "return code" when I run trinity at a chroot image: $ sudo ~/workspace/bin/chr_uml.sh -r ~/virtual/uml/trinity -t "cd /mnt/hostfs/; rm -rf t3; mkdir t3; cd t3; trinity -C 4 -m" ... [7283] [156] vmsplice(fd=385, iov=0x974daa0, nr_segs=183, flags=2) = 5457 child 7283 exiting = -1 (Interrupted system call) child 7237 exiting child 7275 exiting [5638] Bailing main loop. Exit reason: ctrl-c [5637] Watchdog exiting Ran 1238429 syscalls. Successes: 275725 Failures: 960137 $ 1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c1;2c Happened all the time, the chr_uml.sh just creates a ramdisk which is mounted onto a directory known within the chroot (/mnt/hostfs) Does anybody else experienced this ? -- MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3 -- To unsubscribe from this list: send the line "unsubscribe trinity" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html