This particular ask was originally formed in a bug about the network stack taking roughly 20 ~ 45 seconds after RetroArch starts, specifically on the raspberry pi images but after conversation with @ToKe79 we discovered that the issue exists in LibreELEC for their Raspberry Pi builds as well, seemingly specific to the pi kernel or supplemental drivers.
But, the issue as it is, on the Pi images, if you use the nas-mount service as we describe in the Lakka docs (https://www.lakka.tv/doc/Serving-ROMs-from-a-NAS/) the service fails to mount because the network stack does not fully initialize until after RetroArch starts. If you SSH into the device and restart the service (systemctl restart storage-nas.mount) it mounts the share just fine and you can go your merry way.
However, it's not terribly convenient to have a terminal or puTTY handy to ssh in and execute the command, which is where the feature request comes in:
As a decent workaround, I feel like if the service to mount a nas share is present, we can have a service in the list of services to manually start / restart the service from the RetroArch GUI. Not only will this allow Raspberry Pi users the ability to use the feature without having to SSH, it can be used to great effect on other devices.
I see a value-add here for handheld devices, especially ones that have wifi capability. A great use-case (and one that I employ often as I do a lot of testing) I use the nas mount service, connect to my NAS and mount the network share and use the settings -> directory menu to change the locations of my default/file browser path, system, thumbnails, and playlists. I mount the nas share on /storage/nas. But, I also have a set of ROMs and BIOS files that i keep locally and when I am away from my home wifi I can still play games, I simply load an alternate retroatch.cfg that has previously mentioned directories in their default locations on /storage so that I can play them offline .
I imagine that others would see value in having a default "offline" config with the ability to manually mount a share via the services menu and then load an alternate config that points the directories to the NAS drive and as an added bonus, maybe even sync savesfiles and savestates using the cloud sync feature when back online
I don't know how much of that we can automate (immediately and down the road) but I see a lot of value in offering at least that manual invocation of that mount service, then the user can manually load the alternate config and enjoy an 'online' experience when they want to.
thoughts? concerns? arguments? I welcome them all
This particular ask was originally formed in a bug about the network stack taking roughly 20 ~ 45 seconds after RetroArch starts, specifically on the raspberry pi images but after conversation with @ToKe79 we discovered that the issue exists in LibreELEC for their Raspberry Pi builds as well, seemingly specific to the pi kernel or supplemental drivers.
But, the issue as it is, on the Pi images, if you use the nas-mount service as we describe in the Lakka docs (https://www.lakka.tv/doc/Serving-ROMs-from-a-NAS/) the service fails to mount because the network stack does not fully initialize until after RetroArch starts. If you SSH into the device and restart the service (
systemctl restart storage-nas.mount) it mounts the share just fine and you can go your merry way.However, it's not terribly convenient to have a terminal or puTTY handy to ssh in and execute the command, which is where the feature request comes in:
As a decent workaround, I feel like if the service to mount a nas share is present, we can have a service in the list of services to manually start / restart the service from the RetroArch GUI. Not only will this allow Raspberry Pi users the ability to use the feature without having to SSH, it can be used to great effect on other devices.
I see a value-add here for handheld devices, especially ones that have wifi capability. A great use-case (and one that I employ often as I do a lot of testing) I use the nas mount service, connect to my NAS and mount the network share and use the settings -> directory menu to change the locations of my default/file browser path, system, thumbnails, and playlists. I mount the nas share on
/storage/nas. But, I also have a set of ROMs and BIOS files that i keep locally and when I am away from my home wifi I can still play games, I simply load an alternate retroatch.cfg that has previously mentioned directories in their default locations on/storageso that I can play them offline .I imagine that others would see value in having a default "offline" config with the ability to manually mount a share via the services menu and then load an alternate config that points the directories to the NAS drive and as an added bonus, maybe even sync savesfiles and savestates using the cloud sync feature when back online
I don't know how much of that we can automate (immediately and down the road) but I see a lot of value in offering at least that manual invocation of that mount service, then the user can manually load the alternate config and enjoy an 'online' experience when they want to.
thoughts? concerns? arguments? I welcome them all