Skip to content
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

How to access external partition #253

Open
clemencyworld1 opened this issue Aug 17, 2020 · 4 comments
Open

How to access external partition #253

clemencyworld1 opened this issue Aug 17, 2020 · 4 comments

Comments

@clemencyworld1
Copy link

clemencyworld1 commented Aug 17, 2020

I installed spacefm in the junest environment but i could not access my data partition from it. I tried unmounting the partition and mounting it inside junest but no success. The partition is actually mounted but appears empty in junest but from the home folder it shows everything. I there a special way to mount external partition under junest or is it not possible.

Thanks

@fsquillace
Copy link
Owner

Where is the directory located. Can you show me the command you run and the error?

@clemencyworld1
Copy link
Author

Sorry, I moved on to Antix Linux after encountering many boot fails with Arch Linux. I will see if junest can run on Debian based Antix and try again.

Sorry for long silence. This project inzpirez me

@clemencyworld1
Copy link
Author

Ok. So i mounted my Data partition located in /dev/sda5 on /media/Data while my root partition is /dev.sda1. I could access the mounted partition in the host system but in junest it says it does not exist. In fact, there is no /media folder listed in junest folder tree.

Apparently, junest can only access the home folder so i made a link of the partition to my home folder, While the linked folder shows in commandline; it doesn't show in the file manager. Trying to cd into the linked folder returns "No such file or directory".

I ran "sudo fdisk -l " in junest and got:

$ sudo fdisk -l
fdisk: cannot open /dev/ram0: Permission denied
fdisk: cannot open /dev/ram1: Permission denied
fdisk: cannot open /dev/ram2: Permission denied
fdisk: cannot open /dev/ram3: Permission denied
fdisk: cannot open /dev/ram4: Permission denied
fdisk: cannot open /dev/ram5: Permission denied
fdisk: cannot open /dev/ram6: Permission denied
fdisk: cannot open /dev/ram7: Permission denied
fdisk: cannot open /dev/ram8: Permission denied
fdisk: cannot open /dev/ram9: Permission denied
fdisk: cannot open /dev/ram10: Permission denied
fdisk: cannot open /dev/ram11: Permission denied
fdisk: cannot open /dev/ram12: Permission denied
fdisk: cannot open /dev/ram13: Permission denied
fdisk: cannot open /dev/ram14: Permission denied
fdisk: cannot open /dev/ram15: Permission denied
fdisk: cannot open /dev/sda: Permission denied

@fsquillace
Copy link
Owner

fsquillace commented Mar 29, 2022

For that you'd need to explictly tell junest to bind that directory. By default only a subset of directory are bind to a JuNest session.
The bind depends on which mode (backend program) you are using. If you are using the default one (ns and not proot) then you can run:

junest -b "--bind /media/Data /home/myuser/Data"

To see the options available for the ns (which uses bwrap):

junest -b "--help"

For proot backend:

junest proot -b "--help"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants