## 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.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.

Each configuration file shall be named in the style of `<program>.conf`. Files in `/etc/` override files with the same name in `/usr/lib/` and `/run/`. Files in `/run/` override files with the same name in `/usr/lib/`. 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 from vendor packages. All files are sorted by their filename in alphabetical order, regardless in which of the directories they reside, to guarantee that a specific configuration file takes precedence over another file with an alphabetically later name.

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 `/etc/binfmt.d/` bearing the same file name.

## 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)