mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mingye Wang <arthur200126@gmail.com>
To: Christian Brauner <brauner@kernel.org>, linux-kernel@vger.kernel.org
Cc: Mingye Wang <arthur200126@gmail.com>
Subject: [PATCH 2/2] Documentation/admin-guide/binfmt-misc/mono: add Caveats
Date: Mon,  3 Nov 2025 18:27:44 +0800	[thread overview]
Message-ID: <20251103102753.462-2-arthur200126@gmail.com> (raw)
In-Reply-To: <20251103102753.462-1-arthur200126@gmail.com>

This will clash with wine. Spell it out.
---
 Documentation/admin-guide/binfmt-misc/mono.rst | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/Documentation/admin-guide/binfmt-misc/mono.rst b/Documentation/admin-guide/binfmt-misc/mono.rst
index c6dab568006..a11655c72b5 100644
--- a/Documentation/admin-guide/binfmt-misc/mono.rst
+++ b/Documentation/admin-guide/binfmt-misc/mono.rst
@@ -68,3 +68,16 @@ other program after you have done the following:
 
       If this fails with a permission denied error, check
       that the ``.exe`` file has execute permissions.
+
+Caveats
+^^^^^^^
+
+You may have noticed that our registration line is virtually the same
+as the one for wine, with ``MZ`` as the magic number and no offset.
+This means that if you have both wine and mono installed, only one
+of them will work, depending on which one was registered last.
+
+To solve this problem, you can use a wrapper script for either wine
+or mono that checks the file type and invokes the correct interpreter.
+For example, ``file`` is able to distinguish between .NET CLR binaries
+and regular Windows binaries.
-- 
2.49.0.windows.1


      reply	other threads:[~2025-11-03 10:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03 10:27 [PATCH 1/2] Documentation/admin-guide/{binfmt-misc,java,mono}: Consolidate into one directory Mingye Wang
2025-11-03 10:27 ` Mingye Wang [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251103102753.462-2-arthur200126@gmail.com \
    --to=arthur200126@gmail.com \
    --cc=brauner@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®