From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Claudius Heine" <claudius.heine.ext@siemens.com>,
Alexander Smirnov <asmirnov@ilbers.de>,
isar-users <isar-users@googlegroups.com>
Subject: Re: Overview over my outstanding patches
Date: Thu, 24 May 2018 15:38:14 +0200 [thread overview]
Message-ID: <9b19e51b-7ddc-e1c3-9aef-e48f89c01563@siemens.com> (raw)
In-Reply-To: <f4581569-4c7f-8591-f360-fb9ad6ad5e92@siemens.com>
On 2018-05-24 15:34, [ext] Claudius Heine wrote:
> Hi,
>
> On 2018-05-24 11:21, [ext] Claudius Heine wrote:
>> Hi Alex,
>>
>> On 2018-05-14 15:47, Alexander Smirnov wrote:
>>> Remaining:
>>> ==========
>>> - meta-isar/isar-image-base: added removal of qemu-*-static binaries:
>>>
>>> Here is the question about case, when user wants to install
>>> qemu-user-static package to target rootfs.
>>
>> If the user wants to install qemu-user-static to the image, apt
>> overwrites the one already there and then the linux kernel complains
>> about infinite symlink since it wants to execute the new foreign
>> 'qemu-*-static' binary with the foreign 'qemu-*-static' binary on and on.
>>
>> Installing qemu-user-static is simply forbidden until qemu-debootstrap
>> changes the deployment path and binfmt settings to avoid this conflict.
>
> With Hennings help we further investigated this. The binfmt_misc flag
> 'F' would prevent this issue [1]. So installing qemu-user-static could
> be possible if that flag is used.
Do we have that under our control, or would we have to patch the
upstream binfmt debian package to tune that flag?
Jan
>
> I will prepare a patch that removes the qemu-*-static binaries only if
> that package is not installed.
>
> Claudius
>
> [1]
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/admin-guide/binfmt-misc.rst?h=v4.16#n83
>
>
next prev parent reply other threads:[~2018-05-24 13:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 10:52 Claudius Heine
2018-04-26 13:57 ` Claudius Heine
2018-05-14 13:47 ` Alexander Smirnov
2018-05-24 9:21 ` Claudius Heine
2018-05-24 13:34 ` Claudius Heine
2018-05-24 13:38 ` Jan Kiszka [this message]
2018-05-24 14:50 ` Claudius Heine
2018-05-24 14:52 ` Jan Kiszka
2018-05-24 15:02 ` Claudius Heine
2018-05-24 15:10 ` Henning Schild
2018-05-24 15:20 ` Claudius Heine
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=9b19e51b-7ddc-e1c3-9aef-e48f89c01563@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=asmirnov@ilbers.de \
--cc=claudius.heine.ext@siemens.com \
--cc=isar-users@googlegroups.com \
/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