Differences

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

--- edit_boot_partition [2021/09/09 00:51] – [Editing the boot/ partition while Batocera is running] formatting fix atari
+++ edit_boot_partition [2022/07/07 03:01] (current) – atom is being depreciated in dec 2022 atari
@@ Line 1: / Line 1: @@
 ====== Editing the boot partition ======
-This is the platform-specific boot partition, usually FAT32 but can depend on the device. This partition can be read and edited by most other operating systems should you plug the drive into another machine.
+This is the platform-specific boot partition, usually FAT32 but can depend on the device. This partition can be read and edited by most other operating systems should you plug the drive into another machine. The most common file that might need to be edited is the ''batocera-boot.conf'' file, but others too might be required to be changed depending on what you're doing.
-<WRAP center round important 60%>
+<WRAP center round important>
 Be careful; changing these files can affect Batocera's ability to boot, so always make backups of these files before changing them.
 </WRAP>
@@ Line 13: / Line 13: @@
 {{ :boot-partition1.png?nolink&500 |There he is!}}
-<WRAP center round important 60%>
+This is the equivalent of looking into the ''/boot'' folder in Batocera while Batocera is running.
-If you edit any text file under Windows, make sure you have an editor that respects Unix line terminators. <wrap em>Don't use Notepad</wrap>, use a text editor like Notepad++ or Atom, that doesn't replace the Unix line terminations (LF) with DOS/Windows line terminations (CR/LF). Wordpad has also been reported to corrupt Unix text files.
+<WRAP center round important>
+If you edit any text file under Windows, make sure you have an editor that respects Unix line terminators. <wrap em>Don't use Notepad</wrap>, use a text editor like Notepad++, that doesn't replace the Unix line terminations (LF) with DOS/Windows line terminations (CR/LF). Wordpad has also been reported to corrupt Unix text files.
+</WRAP>
+<WRAP center round tip>
+The ''batocera-boot.conf'' file uses the same [[:batocera_conf_syntax|syntax]] as the batocera.conf file, however different keys are available.
+The default ''batocera-boot.conf'' can be found [[https://raw.githubusercontent.com/batocera-linux/batocera.linux/master/package/batocera/core/batocera-system/batocera-boot.conf|here on the Github]]. Right click and "Save Link As...", making sure the name is ''batocera-boot.conf''.
 </WRAP>
@@ Line 28: / Line 36: @@
 {{ :boot-partition2.png?nolink&500 |Read its readme file first!}}
-===== Editing the boot/ partition while Batocera is running =====
+===== Editing the /boot partition while Batocera is running =====
-In contrast to how Windows mounts drives as letters like ''C:\'', Linux 'mounts' partitions to folders when connected, allowing you to access partitions by looking in the assigned folder. In other Linux-based distributions that aren't Batocera, this will typically be in ''/mnt/sda#'' where # is a number. Batocera has set up the FAT32 boot partition to appear as the ''/boot/'' folder in the root directory when booted up, and can be accessed through this folder in its file manager (F1). You'll find if you attempt to do so, however, you'll be met with a "no write permissions error" or something similar. Batocera boots with ''/boot/'' as read-only, so you'll need to remount it with the read-write permissions instead:
+In contrast to how Windows mounts drives as letters like ''C:\'', Linux 'mounts' partitions to folders when connected, allowing you to access partitions by looking in the assigned folder. In other Linux-based distributions that aren't Batocera, this will typically be in ''/mnt/sda#'' where # is a number. Batocera has set up the FAT32 boot partition to appear as the ''/boot'' folder in the root directory when booted up, and can be accessed through this folder in its file manager (F1). You'll find if you attempt to do so, however, you'll be met with a "no write permissions error" or something similar. Batocera boots with ''/boot'' as read-only, so you'll need to remount it with the read-write permissions instead:
 Run the following command (in either Xterm (F1 > Applications) or [[access_the_batocera_via_ssh|SSH]]):
@@ Line 46: / Line 54: @@
 If an error message comes up, you've either misspelled the command, your installation has been corrupted or you're not in the Batocera terminal.
-This will make the ''/boot/'' partition writable until next boot. No need to do anything to change it back, as Batocera will default to mounting it as read-only on next boot.
+This will make the ''/boot'' partition writable until next boot. No need to do anything to change it back, as Batocera will default to mounting it as read-only on next boot.
-<WRAP center round info 60%>
+<WRAP center round info>
 This is not required if you are intending to edit files in the Batocera virtual filesystem. Refer to the [[:modify_the_system_while_it_s_running|overlays page]] for info on that. Note that almost all configuration can be done within Batocera or ''batocera.conf'' and editing overlays should not be required in most cases.
 </WRAP>