On Sat, Aug 03, 2019 at 07:58:15PM +0200, Michael Biebl <[email protected]>
wrote:
> systemd-udevd.service uses
> SystemCallArchitectures=native
Thinking about it, this feels like a bug in systemd - if it runs on a
kernel supporting e.g. x32, amd64 and i386 archs, then all those should be
considered native.
The documentation for this feature is aware of this issue:
The special identifier native implicitly maps to the native
architecture of the system (or more precisely: to the architecture the
system manager is compiled for).
I.e. whoever wrote this does understand that the native architecture of a
system might not be the same as the architeture systemd was compiled for.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / [email protected]
-=====/_/_//_/\_,_/ /_/\_\
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
