Comment 3 for bug 1470170

Laurent,

I just encountered the same missing syscall on qemu-m68k:

Unpacking udev (228-2) over (227-2) ...
Preparing to unpack .../libsystemd0_228-2_m68k.deb ...
Unpacking libsystemd0:m68k (228-2) over (227-2) ...
Processing triggers for man-db (2.7.5-1) ...
Not building database; man-db/auto-update is not 'true'.
Processing triggers for libc-bin (2.21-3) ...
Setting up libsystemd0:m68k (228-2) ...
Processing triggers for libc-bin (2.21-3) ...
(Reading database ... 26780 files and directories currently installed.)
Preparing to unpack .../systemd_228-2_m68k.deb ...
Unpacking systemd (228-2) over (227-2) ...
Processing triggers for man-db (2.7.5-1) ...
Not building database; man-db/auto-update is not 'true'.
Setting up systemd (228-2) ...
Installing new version of config file /etc/pam.d/systemd-user ...
Installing new version of config file /etc/systemd/logind.conf ...
Installing new version of config file /etc/systemd/system.conf ...
qemu: Unsupported syscall: 352
qemu: Unsupported syscall: 352
qemu: Unsupported syscall: 352
addgroup: The group `systemd-journal' already exists as a system group. Exiting.
qemu: Unsupported syscall: 352
(Reading database ... 26779 files and directories currently installed.)
Preparing to unpack .../systemd-sysv_228-2_m68k.deb ...
Unpacking systemd-sysv (228-2) over (227-2) ...
Processing triggers for man-db (2.7.5-1) ...
Not building database; man-db/auto-update is not 'true'.
Setting up systemd-sysv (228-2) ...
Setting up udev (228-2) ...
qemu: Unsupported syscall: 352
addgroup: The group `input' already exists as a system group. Exiting.
A chroot environment has been detected, udev not started.
Reading package lists... Done
Building dependency tree
Reading state information... Done

This just happened for the first time and it's apparently related to very recent versions of systemd (228).

Adrian