1BINFMT.D(5)                        binfmt.d                        BINFMT.D(5)
2
3
4

NAME

6       binfmt.d - Configure additional binary formats for executables at boot
7

SYNOPSIS

9       /etc/binfmt.d/*.conf
10
11       /run/binfmt.d/*.conf
12
13       /usr/lib/binfmt.d/*.conf
14

DESCRIPTION

16       At boot, systemd-binfmt.service(8) reads configuration files from the
17       above directories to register in the kernel additional binary formats
18       for executables.
19

CONFIGURATION FORMAT

21       Each file contains a list of binfmt_misc kernel binary format rules.
22       Consult the kernel's Kernel Support for miscellaneous Binary Formats
23       (binfmt_misc)[1] documentation file for more information on
24       registration of additional binary formats and how to write rules.
25
26       Empty lines and lines beginning with ";" and "#" are ignored. Note that
27       this means you may not use those symbols as the delimiter in binary
28       format rules.
29

CONFIGURATION DIRECTORIES AND PRECEDENCE

31       Configuration files are read from directories in /etc/, /run/,
32       /usr/local/lib/, and /usr/lib/, in order of precedence, as listed in
33       the SYNOPSIS section above. Files must have the ".conf" extension.
34       Files in /etc/ override files with the same name in /run/,
35       /usr/local/lib/, and /usr/lib/. Files in /run/ override files with the
36       same name under /usr/.
37
38       All configuration files are sorted by their filename in lexicographic
39       order, regardless of which of the directories they reside in. If
40       multiple files specify the same option, the entry in the file with the
41       lexicographically latest name will take precedence. Thus, the
42       configuration in a certain file may either be replaced completely (by
43       placing a file with the same name in a directory with higher priority),
44       or individual settings might be changed (by specifying additional
45       settings in a file with a different name that is ordered later).
46
47       Packages should install their configuration files in /usr/lib/
48       (distribution packages) or /usr/local/lib/ (local installs). Files in
49       /etc/ are reserved for the local administrator, who may use this logic
50       to override the configuration files installed by vendor packages. It is
51       recommended to prefix all filenames with a two-digit number and a dash,
52       to simplify the ordering of the files.
53
54       If the administrator wants to disable a configuration file supplied by
55       the vendor, the recommended way is to place a symlink to /dev/null in
56       the configuration directory in /etc/, with the same filename as the
57       vendor configuration file. If the vendor configuration file is included
58       in the initrd image, the image has to be regenerated.
59

EXAMPLE

61       Example 1. /etc/binfmt.d/wine.conf example:
62
63           # Start WINE on Windows executables
64           :DOSWin:M::MZ::/usr/bin/wine:
65

SEE ALSO

67       systemd(1), systemd-binfmt.service(8), systemd-delta(1), wine(8)
68

NOTES

70        1. Kernel Support for miscellaneous Binary Formats (binfmt_misc)
71           https://www.kernel.org/doc/html/latest/admin-guide/binfmt-misc.html
72
73
74
75systemd 251                                                        BINFMT.D(5)
Impressum