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 binfmt-misc.rst[1] documentation file for more
23       information on registration of additional binary formats and how to
24       write rules.
25
26       Empty lines and lines beginning with ; and # are ignored. Note that
27       this means you may not use ; and # as delimiter in binary format rules.
28

CONFIGURATION DIRECTORIES AND PRECEDENCE

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

EXAMPLE

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

SEE ALSO

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

NOTES

69        1. binfmt-misc.rst
70           https://www.kernel.org/doc/html/latest/admin-guide/binfmt-misc.html
71
72
73
74systemd 249                                                        BINFMT.D(5)
Impressum