Hello all :) Very specific question here.
I have a standard mini computer (Intel x86_64) with an internal HDD and an SSD. I wanted to put “big” systems (PS2/PS3…) on SSD and “small” (NES, Megadrive…) systems on HDD. Since Batocera was initially installed on the SSD, I wanted to move /userdata to the HDD (because the vast majority of systems are small, and I didn’t want to create approx. 100 symlinks, but rather 4 or 5 for the big systems).
Being a Linux user, at the time, managing it with an overlay + /etc/fstab seemed the most logical way to do it : basically I edited batocera-boot.conf to point /userdata to the HDD ( sharedevice=DEV 74be2ca5-fd59-4c61-aceb-155161c99742then created a directory to mount the SSD in it ( /mnt/ssd), then created an overlay with batocera-create-overlay, made a few symlinks in /userdata/roms/XXX for the 4 or 5 systems I wanted to put on the SSD, and voilà. Works fine.
Thing is, a user on Reddit told me that this method was unstable and prone to break on upgrade. Is this true ? He recommended to use manual mount commands in batocera-boot.conf (which would also be fine with me), but it doesn’t seem to work :
I first tried this :
sharedevice=DEV 74be2ca5-fd59-4c61-aceb-155161c99742
sharenetwork_cmd1=mkdir /mnt/ssd
sharenetwork_cmd2=mount /dev/nvme0n1p2 /mnt/ssd
then this :
sharedevice=NETWORK
sharenetwork_cmd1=umount /userdata
sharenetwork_cmd2=mount /dev/sda1 /userdata
sharenetwork_cmd3=mkdir /mnt/ssd
sharenetwork_cmd4=mount /dev/nvme0n1p2 /mnt/ssd
I would greatly appreciate some advice 😅
