View Single Post
Posts: 362 | Thanked: 426 times | Joined on Nov 2010 @ Italy, Lombardia
#2361
Originally Posted by qole View Post
Fabry was right, "none" didn't work as a parameter of qchroot.

I've uploaded version 0.3.5 to Extras-Devel. It works now, I think.
I am trying but it seems that closechroot search for a lock created by qmount.
But qmount isn't executed if we use "none" option and so closechroot not works

EDIT:
Problems found:
  • I confirm that closechroot not works but there is a simple workaround (waiting a new release of EasyChroot).
    After entering on chroot execute echo "none" > /var/lock/qmount-complete as first command.
    Now closechroot will work with only a negligible error (it still tries to umount with qumount the chroot target folder).
  • Some scripts work with relative path but others need always absolute path.
    • qchroot works with relative path
      Code:
      cd /home/user
      sudo qchroot /dev/mmcblk1p2 my-chroot-folder/
    • qmount work with relative path
      Code:
      cd /home/user
      sudo qmount /dev/mmcblk1p2 my-chroot-folder/
      Still works with sudo qmount /dev/mmcblk1p2 ./my-chroot-folder but not with sudo qmount /dev/mmcblk1p2 my-chroot-folder
    • qumount not works with relative path, it works only with
      Code:
      cd /home/user
      sudo qumount /home/user/my-chroot-folder/
    • closechroot not works with relative path, it works only with
      Code:
      cd /home/user
      sudo closechroot /home/user/my-chroot-folder/

Last edited by Fabry; 2011-07-27 at 18:11.
 

The Following 2 Users Say Thank You to Fabry For This Useful Post: