Development:Setting up RootFS - Revision history

Neobrain at 14:47, 13 January 2026

2026-01-13T14:47:15Z

2026-01-12T22:53:33Z

Chrooting in to rootfs with FEX-Emu Rootfs

2026-01-12T22:53:18Z

Chrooting in to rootfs with FEX-Emu Rootfs

2026-01-12T22:51:09Z

Chrooting in to rootfs with FEX-Emu Rootfs

2026-01-12T22:50:50Z

Rewritten to update information, as well as adding information that is relevant to getting

2025-09-22T14:11:50Z

Update for FEXConfig changes

2025-09-22T14:02:51Z

FEXInterpreter -> FEX

2023-12-13T02:15:20Z

If you want to install packages in the squashfs

2023-05-19T22:12:46Z

2022-09-29T21:20:29Z

@@ Line 72: / Line 72: @@
 * Once you have binfmt_misc running and FEX-Emu installed in to it, you can chroot in to an x86-64 rootfs
+== Chrooting into FEX-provided RootFS ==
-== Chrooting in to rootfs with FEX-Emu Rootfs ==
+* If you're using a FEX-provided RootFS, we provide a script to handle this:
-* If you're using a FEX-Emu provided RootFS then we provide a script to handle this.
+** To enter, use '''./chroot.py chroot''' inside the root directory of the RootFS
-** This script can be called uing '''./chroot.py chroot''' inside the root directory of the RootFS.
+** When you finish, make sure to exit the chroot cleanly
 If the chroot is working, the remaining steps of this guide can safely be skipped.
@@ Line 84: / Line 83: @@
 ** The solution is to copy "/usr/bin/FEXInterpreter" to "/usr/bin/FEX".
-== Chrooting in to custom rootfs with FEX-Emu ==
+== Chrooting into custom RootFS ==
 * If you're setting up your own rootfs then you need to follow the binding steps that are following.
 ** We have a script that if you know what you're doing you can cherry pick parts from [https://github.com/FEX-Emu/RootFS/blob/main/unbreak_chroot.sh here]

@@ Line 79: / Line 79: @@
 If the chroot is working, the remaining steps of this guide can safely be skipped.
-Issues
+* Issues
-* As of January 12th, 2026, Fedora packages for FEX-Emu are a few months out of date.
+** As of January 12th, 2026, Fedora packages for FEX-Emu are a few months out of date.
-* This causes the chroot script to fail, saying "Host program 'FEX' isn't available and is required!".
+** This causes the chroot script to fail, saying "Host program 'FEX' isn't available and is required!".
-* The solution is to copy "/usr/bin/FEXInterpreter" to "/usr/bin/FEX".
+** The solution is to copy "/usr/bin/FEXInterpreter" to "/usr/bin/FEX".
 == Chrooting in to custom rootfs with FEX-Emu ==

@@ Line 79: / Line 79: @@
 If the chroot is working, the remaining steps of this guide can safely be skipped.
-* Issues
+Issues
-** As of January 12th, 2026, Fedora packages for FEX-Emu are a few months out of date.
+* As of January 12th, 2026, Fedora packages for FEX-Emu are a few months out of date.
-** This causes the chroot script to fail, saying "Host program 'FEX' isn't available and is required!".
+* This causes the chroot script to fail, saying "Host program 'FEX' isn't available and is required!".
-** The solution is to copy "/usr/bin/FEXInterpreter" to "/usr/bin/FEX".
+* The solution is to copy "/usr/bin/FEXInterpreter" to "/usr/bin/FEX".
 == Chrooting in to custom rootfs with FEX-Emu ==

@@ Line 76: / Line 76: @@
 * If you're using a FEX-Emu provided RootFS then we provide a script to handle this.
 ** This script can be called uing '''./chroot.py chroot''' inside the root directory of the RootFS.
-** Make sure to exit the chroot cleanly.
+** When you finish, make sure to exit the chroot cleanly.
 If the chroot is working, the remaining steps of this guide can safely be skipped.

@@ Line 71: / Line 71: @@
 ** If there are files in this folder then your host supports binfmt_misc
 * Once you have binfmt_misc running and FEX-Emu installed in to it, you can chroot in to an x86-64 rootfs
 == Chrooting in to rootfs with FEX-Emu Rootfs ==
-* If you're using a FEX-Emu provided rootfs then we provide two scripts at the start to handle this
+* If you're using a FEX-Emu provided RootFS then we provide a script to handle this.
-** '''unbreak_chroot.sh''' - This sets up the rootfs and chroots inside of it
+** This script can be called uing '''./chroot.py chroot''' inside the root directory of the RootFS.
-** '''break_chroot.sh''' - This sets up the rootfs for using with FEX generally.
+** Make sure to exit the chroot cleanly.
-*** '''Make sure to run this after leaving the chroot!'''
+If the chroot is working, the remaining steps of this guide can safely be skipped.
-*** The '''unbreak_chroot.sh''' script will run this if you exit safely.
-** The remaining steps in this guide can be skipped
+* Issues
 == Chrooting in to custom rootfs with FEX-Emu ==

@@ Line 103: / Line 103: @@
 * sudo umount -R ${ROOTFS}/lib/aarch64-linux-gnu
-= Using the rootfs with FEX =
+= Using the RootFS with FEX =
-== Setting RootFS with FEXConfig ==
+Run the graphical FEXConfig tool to select and change the active RootFS. Any file or folder in $HOME/.fex-emu/RootFS will be detected automatically.
 = Additional Steps for building a custom rootfs =

@@ Line 218: / Line 218: @@
 ** This will forcibly terminate FEXMountDaemon which should also take out the child mounted process
 * If any instances of the mount still exists then you may need to kill more FEX processes.
-** Any FEXInterpreter process will end up keeping the folder mounted and keep it busy
+** Any ''FEX'' process will end up keeping the folder mounted and keep it busy
 '''strace breaks squashfs'''

@@ Line 197: / Line 197: @@
 * `apt-get install <Whatever you want>`
 * `exit` to leave the chroot
 * Use the new extracted chroot directly, or follow the previous steps to recompress it to a squashfs format.

@@ Line 45: / Line 45: @@
 * '''Where is the raw list of images at?'''
 ** The image links live on our website at the following link
-** https://rootfs.fex-emu.com/file/fex-rootfs/RootFS_links.json
+** https://rootfs.fex-emu.gg/RootFS_links.json
 ** This file is in a format that our tool understands
 ** Generally the format is: