Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revisionBoth sides next revision
modify_the_system_while_it_s_running [2020/02/01 00:13] lbrpdxmodify_the_system_while_it_s_running [2021/03/29 18:22] – [Cases when you don't need to modify the system] Put a link to the newer page dedicated to customizing systems instead of (slightly out of date) instructions. fishou
Line 1: Line 1:
- +====== Modify the system while it's running ======
-===== Modify the system while it's running =====+
 By default, batocera.linux is like a firmware. It's a file called ''/boot/batocera''. By default, batocera.linux is like a firmware. It's a file called ''/boot/batocera''.
 You cannot modify it directly, and for most use cases, you shouldn't need to modify it. All the user data is stored in ''/userdata/'', which is writable. You cannot modify it directly, and for most use cases, you shouldn't need to modify it. All the user data is stored in ''/userdata/'', which is writable.
Line 6: Line 5:
 That said, in case you need to modify the system, there are tips to do it. That said, in case you need to modify the system, there are tips to do it.
  
-=== /boot/ directory ===+===== /boot/ directory =====
 For any modification in ''/boot'': For any modification in ''/boot'':
  
-  mount -o remount,rw /boot+  mount -o remount,rw /boot
      
  
-=== Other system files ===+===== Other system files =====
 For any other modifications, you can directly edit the files in their directory (for example if you want to play with the configgen scripts in ''/usr/lib/python2.7/site-packages/configgen/generators/''). Once the modifications are done, you can save them with the command: For any other modifications, you can directly edit the files in their directory (for example if you want to play with the configgen scripts in ''/usr/lib/python2.7/site-packages/configgen/generators/''). Once the modifications are done, you can save them with the command:
  
-  batocera-save-overlay+  batocera-save-overlay
      
-This script creates a file at ''/boot/boot/overlay'' file that stores all the modifications you made. **WARNING**: this overlay file is automatically removed at the next upgrade.+This script creates a file at ''/boot/boot/overlay'' file that stores all the modifications you made. 
 + 
 +<WRAP center round important 50%>**WARNING**: This overlay file is automatically removed at the next upgrade.</WRAP>
  
 If you don't use the ''batocera-save-overlay'' script, you can still edit the files in ''/usr/'' but any modification will be lost on reboot. If you don't use the ''batocera-save-overlay'' script, you can still edit the files in ''/usr/'' but any modification will be lost on reboot.
  
 If you want to remove all your customizations, just remove this ''/boot/boot/overlay'' file. If you want to remove all your customizations, just remove this ''/boot/boot/overlay'' file.
 +
 +By default, Batocera overlay files are limited to 50MB. If your modifications are over 50MB, you can specify the size of the overlay with the command. Keep always a bit of margin, the overlay will embed a few more files than those you were expecting (some system files created on-the-fly at boot time). For example, if you need to save 120MB of data on the system, you can type ''batocera-save-overlay 120''.
  
 **Note** : it cannot be done for the current Odroid xu4 version. **Note** : it cannot be done for the current Odroid xu4 version.
  
-=== Cases when you don't need to modify the system ===+===== Cases when you don't need to modify the system =====
 Some best practices here: Some best practices here:
   * You generally don't need to edit ''/etc/fstab'', use [[store_games_on_a_nas]] instead.   * You generally don't need to edit ''/etc/fstab'', use [[store_games_on_a_nas]] instead.
-  * You should not modify ''/usr/share/emulationstation/es_systems.cfg''. Instead, copy this file to ''/userdata/system/configs/emulationstation/es_systems.cfg'' and customize it from there. At startup, EmulationStation prefers the latter file if it exists.+  * You should not modify ''/usr/share/emulationstation/es_systems.cfg''. Instead, follow the instructions in [[emulationstation:customize_systems|the Customize sytems page]].
  • modify_the_system_while_it_s_running.txt
  • Last modified: 12 months ago
  • by maximumentropy