| Both sides previous revision Previous revision Next revision | Previous revision |
| modify_the_system_while_it_s_running [2022/03/08 01:31] – rephrase to be more relevant to the topic at hand atari | modify_the_system_while_it_s_running [2023/04/09 14:10] (current) – [Creating a Batocera filesystem overlay] maximumentropy |
|---|
| ===== Creating a Batocera filesystem overlay ===== | ===== Creating a Batocera filesystem overlay ===== |
| |
| For modifications to the regular Batocera filesystem, you can directly edit the files in their directory using [[:built_file_manager|the built-in file manager]] while booted (for example if you want to play with the configgen scripts in ''/usr/lib/python3.9/site-packages/configgen/generators/'' or change the default platform parameters in ''/usr/share/batocera/configgen/configgen-defaults-arch.yml'') or sign in [[:access_the_batocera_via_ssh|via SSH]] or [[:winscp|SCP/FTP]] to make those alterations. Once the modifications are done, you can save them with [[:access_the_batocera_via_ssh|the command]] ''batocera-save-overlay''. This command script creates a patch file at ''/boot/boot/overlay'' which stores the differences between the current mounted filesystem and the one stored in ''/boot/batocera''. | For modifications to the regular Batocera filesystem, you can directly edit the files in their directory using [[:built_file_manager|the built-in file manager]] while booted (for example if you want to play with the configgen scripts in ''/usr/lib/pythonX.X/site-packages/configgen/generators/'' or change the default platform parameters in ''/usr/share/batocera/configgen/configgen-defaults-arch.yml'') or sign in [[:access_the_batocera_via_ssh|via SSH]] or [[:winscp|SCP/FTP]] to make those alterations. Once the modifications are done, you can save them with [[:access_the_batocera_via_ssh|the command]] ''batocera-save-overlay''. This command script creates a patch file at ''/boot/boot/overlay'' which stores the differences between the current mounted filesystem and the one stored in ''/boot/batocera''. |
| |
| <WRAP center round tip> | <WRAP center round tip> |
| <WRAP center round important> | <WRAP center round important> |
| This overlay file is automatically removed at the next upgrade. | This overlay file is automatically removed at the next upgrade. |
| | </WRAP> |
| | |
| | <WRAP center round tip> |
| | To view the contents of the overlay independently from the underlying filesystem, it can be mounted in a separate location: |
| | |
| | <code> |
| | mount /boot/boot/overlay /mnt |
| | find /mnt |
| | umount /mnt |
| | </code> |
| | |
| </WRAP> | </WRAP> |
| |
| ===== I want to modify something in the boot folder though ===== | ===== I want to modify something in the boot folder though ===== |
| |
| The boot partition is mounted with read-only permissions at ''/boot/'', but can be [[:edit_boot_partition#editing_the_boot_partition_while_batocera_is_running|remounted with write permissions post-boot]]. All the user data is stored in a separate userdata partition, which is mounted with write permissions at the path ''/userdata/''. | The boot partition is mounted with read-only permissions at ''/boot/'', but can be [[:edit_boot_partition#editing_the_boot_partition_while_batocera_is_running|remounted with write permissions post-boot]]. You do not need to save an overlay for file edits made in the boot partition, as this is a physical partition where your edits are permanent (and because of that, any edits you make here are more dangerous and can result in a non-booting machine, always make backups before attempting this). All the user data is stored in a separate userdata partition, which is mounted with write permissions at the path ''/userdata/'' (like the boot partition, this is just your regular userdata storage partition, no need to save overlays for this either). |
| |