Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

2017-01-29 Thread Michael Biebl
Dear powerpc porters, it would be great if you could look at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852811 From a cursory glance it seems that seccomp support is broken on ppc64. Your input would be appreciated. Am 27.01.2017 um 16:21 schrieb Michael Biebl: > Am 27.01.2017 um 15:54

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

2017-01-27 Thread Michael Biebl
Am 27.01.2017 um 16:30 schrieb Christian Marillat: > On 27 janv. 2017 16:21, Michael Biebl wrote: > >> Christian, I think it's best if you approach the ppc64 porters about >> this. We need their input regarding seccomp support on that architecture. > > Well the kernel is a ppc64 but the archite

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

2017-01-27 Thread Christian Marillat
On 27 janv. 2017 16:21, Michael Biebl wrote: > Am 27.01.2017 um 15:54 schrieb Christian Marillat: >> #MemoryDenyWriteExecute=yes >> #RestrictRealtime=yes >> #RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6 >> >> But I see others problems after a reboot : > > There are quite a few ser

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

2017-01-27 Thread Michael Biebl
Am 27.01.2017 um 15:54 schrieb Christian Marillat: > #MemoryDenyWriteExecute=yes > #RestrictRealtime=yes > #RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6 > > But I see others problems after a reboot : There are quite a few services which use seccomp features to restrict the service.

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

2017-01-27 Thread Christian Marillat
On 27 janv. 2017 15:48, Felipe Sateler wrote: > On 27 January 2017 at 11:44, Michael Biebl wrote: >> Am 27.01.2017 um 15:40 schrieb Christian Marillat: >>> On 27 janv. 2017 15:26, Michael Biebl wrote: [...] >>> | Jan 27 15:38:52 fabian.marillat.net systemd[1]: systemd-udevd.service: >>> Main

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

2017-01-27 Thread Christian Marillat
On 27 janv. 2017 15:48, Felipe Sateler wrote: > On 27 January 2017 at 11:44, Michael Biebl wrote: >> Am 27.01.2017 um 15:40 schrieb Christian Marillat: >>> On 27 janv. 2017 15:26, Michael Biebl wrote: [...] >>> | Jan 27 15:38:52 fabian.marillat.net systemd[1]: systemd-udevd.service: >>> Main

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

2017-01-27 Thread Christian Marillat
On 27 janv. 2017 15:44, Michael Biebl wrote: > Am 27.01.2017 um 15:40 schrieb Christian Marillat: >> On 27 janv. 2017 15:26, Michael Biebl wrote: [...] >> Still the same : > > The error code is different. > >> | Jan 27 15:38:52 fabian.marillat.net systemd[1]: systemd-udevd.service: >> Main pr

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

2017-01-27 Thread Felipe Sateler
On 27 January 2017 at 11:44, Michael Biebl wrote: > Am 27.01.2017 um 15:40 schrieb Christian Marillat: >> On 27 janv. 2017 15:26, Michael Biebl wrote: >> >>> Am 27.01.2017 um 15:21 schrieb Debian Bug Tracking System: >> >> [...] >> >>> seccomp is supposed to work on ppc64 [1], but maybe it's not.

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

2017-01-27 Thread Michael Biebl
Am 27.01.2017 um 15:40 schrieb Christian Marillat: > On 27 janv. 2017 15:26, Michael Biebl wrote: > >> Am 27.01.2017 um 15:21 schrieb Debian Bug Tracking System: > > [...] > >> seccomp is supposed to work on ppc64 [1], but maybe it's not. >> >> Christian, could comment out >> RestrictAddressFam

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

2017-01-27 Thread Christian Marillat
On 27 janv. 2017 15:26, Michael Biebl wrote: > Am 27.01.2017 um 15:21 schrieb Debian Bug Tracking System: [...] > seccomp is supposed to work on ppc64 [1], but maybe it's not. > > Christian, could comment out > RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6 > > in systemd-udevd.ser

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

2017-01-27 Thread Christian Marillat
On 27 janv. 2017 15:29, Michael Biebl wrote: [...] > The output of grep SECCOMP /boot/config-$(uname -r) > would be helpful as well. , | $ grep SECCOMP /boot/config-$(uname -r) | CONFIG_HAVE_ARCH_SECCOMP_FILTER=y | CONFIG_SECCOMP_FILTER=y | CONFIG_SECCOMP=y ` Christian __

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

2017-01-27 Thread Michael Biebl
Am 27.01.2017 um 15:26 schrieb Michael Biebl: > Am 27.01.2017 um 15:21 schrieb Debian Bug Tracking System: >>> Maybe the problem is because / is a RAID0 ? >>> >>> Setting up udev (232-14) ... >> No. This is the problem: >> >>> addgroup: The group `input' already exists as a system group. Exiting. >

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

2017-01-27 Thread Michael Biebl
Am 27.01.2017 um 15:21 schrieb Debian Bug Tracking System: >> Maybe the problem is because / is a RAID0 ? >> >> Setting up udev (232-14) ... > No. This is the problem: > >> addgroup: The group `input' already exists as a system group. Exiting. I suspect this to be the problem: Jan 27 14:51:23 fa

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

2017-01-27 Thread Debian Bug Tracking System
Your message dated Fri, 27 Jan 2017 15:16:57 +0100 with message-id <20170127141657.dzvo2skczyex6...@bongo.bofh.it> and subject line Re: Bug#852811: udev: Doesn't start after upgrade powerpc has caused the Debian Bug report #852811, regarding udev: Doesn't start after upgrade powerpc to be marked as