binfmt.d man page
binfmt.d — Configure additional binary formats for executables at boot
At boot, systemd-binfmt.service(8) reads configuration files from the above directories to register in the kernel additional binary formats for executables.
Each file contains a list of binfmt_misc kernel binary format rules. Consult binfmt_misc.txt for more information on registration of additional binary formats and how to write rules.
Empty lines and lines beginning with ; and # are ignored. Note that this means you may not use ; and # as delimiter in binary format rules.
Configuration Directories and Precedence
Configuration files are read from directories in
/usr/lib/, in order of precedence. Each configuration file in these configuration directories shall be named in the style of
filename.conf. Files in
/etc/ override files with the same name in
/usr/lib/. Files in
/run/ override files with the same name in
Packages should install their configuration files in
/usr/lib/. Files in
/etc/ are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same option, the entry in the file with the lexicographically latest name will take precedence. It is recommended to prefix all filenames with a two-digit number and a dash, to simplify the ordering of the files.
If the administrator wants to disable a configuration file supplied by the vendor, the recommended way is to place a symlink to
/dev/null in the configuration directory in
/etc/, with the same filename as the vendor configuration file.
Example 1. /etc/binfmt.d/wine.conf example:
# Start WINE on Windows executables :DOSWin:M::MZ::/usr/bin/wine:
systemd(1), systemd-binfmt.service(8), systemd-delta(1), wine(8)
systemd-binfmt.service(8), systemd.directives(7), systemd.index(7).
Explore man page connections for binfmt.d(5).