X-Spam-Check-By: sourceware.org From: ericblake AT comcast DOT net (Eric Blake) To: cygwin AT cygwin DOT com Subject: chroot bug? Date: Thu, 02 Mar 2006 04:56:32 +0000 Message-Id: <030220060456.13296.44067B00000BC6DF000033F022070208530A050E040D0C079D0A@comcast.net> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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/