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
Option for mounting additional local disks #5933
Comments
yes, seems easy to add and nice. |
Thanks a lot! |
done here : #5974 syntax : sharedevice=DEVICESsharedevice_part1=SHARE@abcdefg-1234-5678-hijk-lmnopq0000sharedevice_part2=ROMS@68dc61b8-5008-4659-bde9-5938a547680a:/Documents/romsnote that the device can be a simple uuid or uuid:subdirectory which could be nice to mount /windows/users/you/my_roms for example. |
Thanks a lot! Are there any restrictions regarding filesystems? I will test it with ext4 - but maybe a lot of users have external disks used alongside Windows with ExFAT/NTFS filesystem. |
hum, i use mount instead of batocera-mount , so yes, i should change it while the aim of batocera-mount is to handle them |
Ok, tested it today with an extern USB drive with ext4 filesystems used for ROMS. Works perfectly fine with latest beta (build date 14.04.2022). Thanks! |
Interesting discussion. I would have a different need and that is, I have Batocera installed on a 2TB SATA HDD, on which I have run out of space. I would like to mount a 2nd STATA HDD on the Motherboard and configure Batocera to make it read the ROMS folder, both from HDD1 and HDD2: can this be done? Thank you. |
batocera-boot.conf
has the option to mount full/userdata
or single directories (like/userdata/roms
) via NAS.Example:
It would be nice to have a similar option in
batocera-boot.conf
for additional local disks. For example having two hard disks/userdata/
(fast flash drive)abcdefg-1234-5678-hijk-lmnopq0000
) ("slow" mass storage)HDD2 should be mounted to
/userdata/roms
while the rest of the/userdata
resides on HDD1.Maybe it can be done with a configuration like this:
This can also be done for separate hard disks or partitions for SAVES, BIOS, etc.
I think only some changes to
/etc/init.d/S11share
have to be done.At the moment this could also be accomplished with a "dirty hack" like (not tested yet):
What do you think?
The text was updated successfully, but these errors were encountered: