From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: qemu qemu-user-static: Provide binfmt services
Date: Sat, 15 Oct 2022 04:16:36 +0200 [thread overview]
Message-ID: <20221015021636.XA-XUnmqEtnXheV5CdjlrzzehL_FPAGg5Q_zHkRocyQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37419@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
There's a closed pull request on the void-packages repository
qemu qemu-user-static: Provide binfmt services
https://github.com/void-linux/void-packages/pull/37419
Description:
`binfmt-support` doesn't work as expected, prioritizes randomly (static & non-static binaries in case both `qemu` & `qemu-user-static` is installed), also does not add `F` flag onto the binfmts which are static (that is required to chroot without copying the binaries to chroot's `/usr/bin`). Ref: https://github.com/void-linux/void-mklive/issues/253#issuecomment-1146786352.
This adds up runit services so that one can easily create the binfmts specific to qemu using [scripts/qemu-binfmt-conf.sh](https://github.com/qemu/qemu/blob/master/scripts/qemu-binfmt-conf.sh) provided in the upstream qemu repository. It also prioritizes static service if symlinked to the service dir.
#### Testing the changes
- I tested the changes in this PR: **briefly**
prev parent reply other threads:[~2022-10-15 2:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 3:37 [PR PATCH] " Animeshz
2022-06-06 3:40 ` [PR PATCH] [Updated] " Animeshz
2022-06-06 3:45 ` Animeshz
2022-06-06 5:58 ` CameronNemo
2022-06-06 16:15 ` Animeshz
2022-07-01 5:25 ` AviKav
2022-09-30 2:15 ` github-actions
2022-10-15 2:16 ` github-actions [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=20221015021636.XA-XUnmqEtnXheV5CdjlrzzehL_FPAGg5Q_zHkRocyQ@z \
--to=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).