These test cases seem complicated to me. A reporter on IRC reported that doing things within an rpi image chroot like 'mv a b' would report an error message "missing destination file operand":
Fri 05 23:26:13 < five623468263> root@ubuntu:/# mv etc/resolv.conf etc/resolv.conf.bak Fri 05 23:26:13 < five623468263> mv: missing destination file operand after 'etc/resolv.conf.bak' Fri 05 23:26:13 < five623468263> Try 'mv --help' for more information. Fri 05 23:26:13 < five623468263> Trying to nano resolv.conf just opens a blank editor. Fri 05 23:43:31 < five623468263> root@ubuntu:/# \mv /etc/resolv.conf /etc/resolv.conf.bak Fri 05 23:43:32 < five623468263> mv: missing destination file operand after '/etc/resolv.conf.bak' Fri 05 23:43:32 < five623468263> Try 'mv --help' for more information. Fri 05 23:48:31 < five623468263> root@ubuntu:/# /bin/echo a b c Fri 05 23:48:31 < five623468263> b c Thanks for already doing the heavy lifting on this one. I was dreading trying to track this down and was pretty happy to see a bug report with the exact symptoms listed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947860 Title: qemu-arm-static swallows the program name, and shifts all arguments left To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1947860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
