systemd-binfmt.service(8) [php man page]

SYSTEMD-BINFMT.SERVICE(8)				      systemd-binfmt.service					 SYSTEMD-BINFMT.SERVICE(8)

NAME

       systemd-binfmt.service, systemd-binfmt - Configure additional binary formats for executables at boot

SYNOPSIS

       systemd-binfmt.service

       /lib/systemd/systemd-binfmt

DESCRIPTION

       systemd-binfmt.service is an early boot service that registers additional binary formats for executables in the kernel.

       See binfmt.d(5) for information about the configuration of this service.

SEE ALSO

       systemd(1), binfmt.d(5), wine(8)

systemd 237														 SYSTEMD-BINFMT.SERVICE(8)

BINFMT.D(5)                                                          binfmt.d                                                          BINFMT.D(5)

NAME

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

SYNOPSIS

       /etc/binfmt.d/*.conf

       /run/binfmt.d/*.conf

       /usr/lib/binfmt.d/*.conf

DESCRIPTION

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

CONFIGURATION FORMAT

       Each file contains a list of binfmt_misc kernel binary format rules. Consult binfmt-misc.rst[1] 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 /etc/, /run/, and /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 /run/ and
       /lib/. Files in /run/ override files with the same name in /lib/.

       Packages should install their configuration files in /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. If the vendor configuration file is
       included in the initrd image, the image has to be regenerated.

EXAMPLE

       Example 1. /etc/binfmt.d/wine.conf example:

           # Start WINE on Windows executables
           :DOSWin:M::MZ::/usr/bin/wine:

SEE ALSO

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

NOTES

        1. binfmt-misc.rst
           https://www.kernel.org/doc/Documentation/admin-guide/binfmt-misc.rst

systemd 237                                                                                                                            BINFMT.D(5)