-
Notifications
You must be signed in to change notification settings - Fork 369
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mv does not work on binded folder #211
Comments
Are you joking? You are using Debian 7 which is very old. You had better upgrade the system to the latest version. |
That's sadly not an option. |
I don't think Debian 7 is too old for PRoot. Especially since there are some issues with running on newer kernels at the moment. I am, however, having trouble finding an image to use for creating a virtual machine for testing. |
However,it seemed that the kernel is too old,or the folder is read-only,try to use chmod at first.(I'm sorry that I can't speak English well.) |
I have the same issue, it seems one of the paths must be absolute for it work:
The last couple of lines reproduce OP's commands which works fine for me - so either OP made a typo or I have a closely related but not identical bug. This is on a very recent Void Linux install inside VirtualBox using
This is causing an issue updating system packages, which then leaves my system in a broken state:
Edit: to clarify, this happens even on the rootfs bind, I'm not even using the |
I just checked it again, i did not made a type :p. I tried with the absolute path for the file to move, I got the same error. |
Additionally I just found that globs don't work either:
|
@erdnaxeli can you test again using either the v5.2.0 release or on the master branch? |
It's not better :(
|
Hi,
I use a very old Linux (3.14) on a very old Debian (7) for… some reasons. I am not root on it. I expected to use proot to be able to do thing on it (every package is years outdated), but it seems that mv does not work.
Expected Behavior
mv work
Actual Behavior
mv does not.
Steps to Reproduce the Problem
Specifications
Command Output
The text was updated successfully, but these errors were encountered: