chroot bug?
Eric Blake
ericblake@comcast.net
Thu Mar 2 04:56:00 GMT 2006
I noticed the following strange behavior in chroot:
$ chroot /bin /sleep 60 &
[1] 16220539
$ readlink /proc/${!}/root # simple test of whether chroot worked
/bin
$ chroot //EBLAKE/share /cygwin/bin/sleep 60 &
[2] 566487
$ readlink /proc/${!}/root # Good - chrooted to a share
//EBLAKE/share
$ chroot // //EBLAKE/share/cygwin/bin/sleep 60 &
[3] 529435
$ readlink /proc/${!}/root # Oops - should be //, not /
/
$ chroot //EBLAKE/share/cygwin/bin/sleep 60 & # Oops, failed to chroot
[4] 566487
$ chroot: cannot chdir to root directory: No such file or directory
Why is chroot failing to find //EBLAKE, when it worked with // (at
least, it slept correctly, although root linked to the wrong place),
and did just fine with //EBLAKE/share?
--
Eric Blake
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
More information about the Cygwin
mailing list