Only the most important folders are accessible via Samba. Samba is a service that you can enable in Settings->Services which allows other computers on the local network to transfer files to Lakka via the CIFS/SMB protocol. Transferring files via a network connection File transfer via Samba share System shows the content of /tmp/system. Where applicable, SAMBA shows the merged content, e.g. Shaders for rendering various visual postprocessing effectsīIOS files and other files needed by emulators Profiles for automatic configuration of game controllers Changes to these special folders are persistent during reboots. These mount points are present in the /tmp folder, where folder from root file system is overlayed with custom content. Root file system of Lakka is read only, therefore any changes to assets, cores or other files used by RetroArch are made using overlayfs mount points.
Update - copy update files here to update Lakka.Thumbnails - the place where game thumbnails are stored.System - to store BIOSes and other files needed by the emulators.Shaders - shaders for rendering various visual postprocessing effects.Services - configuration files for system services.Screenshots - screenshots made during gameplay.Savestates - ‘quicksave’ states, as opposed to savefiles.Savefiles - save files created by the games.Roms - ROMs, films, music, and other content, including downloads subfolder with files downloaded by the Online Updater → Content Downloader.Remappings - custom controller mappings per game / core.Playlists - custom playlists and playlists created by the scanner.Joypads - joypad autoconfiguration profiles.Database - files used for content matching during automatic scanning of ROMs.Cores - libretro emulator cores and info files.Configfiles - configuration files for RetroArch and other parts of the system.Assets - fonts, icons, background images, themes.Note that these the only folders which are made accessible via SAMBA – accessing other areas of the filesystem requires a different approach. The editable portions of the Lakka system can be found in the following folders. Lakka can also be configured to use ROMs that are served from a NAS for users who are comfortable working in a Linux shell environment. Attaching the Lakka drive to another system.There are two overall approaches to gaining access to the Lakka filesystem:
Access to the filesystem also makes it possible to content like screenshots or savefiles from Lakka. In my opinion adding the option under the CloudHub Configuration screen to put it part of an existing network and connect via LAN using an IP + Subnet would make it easier.It is necessary to access the Lakka filesystem in order to accomplish tasks such as adding ROMs or BIOSes.
There is an an easier way by putting the CloudHub into "part of an existing mode" and then just logging in and modifying /etc/config/network via SSH but without a GUI finding the IP the Pi was assigned can be difficult unless you have access to the network infrastructure.
Assign a static ip to your PC under the same subnet and connect.Reboot pi and hope that you did not make a mistake.Modify /etc/config/network to have the required IP + Netmask.Modify /etc/config/dhcp and add "option ignore '1'" under the eth section.SSH into Pi using Putty (or another client) using the default gateway IP.Plug in via Ethernet and allow the Pi to assign an IP to my PC via DHCP (or use wifi).