-
Notifications
You must be signed in to change notification settings - Fork 1
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
Why do all of the commands require root? #6
Comments
Well, technically it isn't all of them... ;) The reason is that Rootbox three root-only features:
There are non-root alternatives to each one here (fuseext2, schroot, and bindfs, respectively), but they all come with some restrictions:
So...it ends up being a lose-lose scenario. |
Interesting - thanks for the response. I really enjoy the idea, but requiring root is impossible for me in some environments. |
Do you have some examples? |
Well, mostly just environments where I don't have root access 😉 I was hoping to be able to use rootbox as a system-level |
Actually, you got me thinking and I've done some more research, and this might actually be possible... |
@scizzorz As a side note: what exactly are the environments where root access is unavailable like? |
I'm not entirely sure I understand your question. Can you elaborate a bit? |
I'm mostly asking why it is the environments don't have root access. Is it a CI server or online development tool or...? |
Some class / lab machines at a university, compute nodes in various types of clusters, VMs at work, etc - they're all machines that I have an account on, but I am not the administrator or owner. |
It seems like it's working entirely in
~/.rootbox
- why does every command tell me I need to run it as root?The text was updated successfully, but these errors were encountered: