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 r
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 system
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 system
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]: s
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
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
__
On 27 janv. 2017 15:16, m...@linux.it (Marco d'Itri) wrote:
> On Jan 27, Christian Marillat wrote:
>
>> Maybe the problem is because / is a RAID0 ?
>>
>> Setting up udev (232-14) ...
> No. This is the problem:
>
>> addgroup: The group `input' alr
Package: udev
Version: 232-14
Severity: important
Dear Maintainer,
Maybe the problem is because / is a RAID0 ?
Setting up udev (232-14) ...
addgroup: The group `input' already exists as a system group. Exiting.
Job for systemd-udevd.service failed because the control process exited with
error c
On 14 août 2016 23:38, Pete Batard wrote:
> Didn't fix it for me... :(
Same for me, still broken.
Christian
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listin
On 31 juil. 2016 10:50, Rick Thomas wrote:
> Can you send the output of ‘uname -a ; systemd —version’ on that box?
Linux rpi3.XXX 4.4.0-1-rpi2 #1 SMP Debian 4.4.6-1+rpi14 (2016-05-05) armv7l
GNU/Linux
,
| $ systemd -—version
| systemd: invalid option -- 'â'
`
Anyway I've downgraded s
On 31 juil. 2016 08:50, Rick Thomas wrote:
> Thanks, Christian!
>
> What is your armel box? I *do* see it on my SheevaPlug (armel), so
> there may be a clue. Is your armel kernel customized in some way?
Raspberry Pi 2 kernel 4.1.12
Christian
___
Pk
On 30 juil. 2016 23:02, Rick Thomas wrote:
> Has anyone else noticed this bug?
>
> Bug#832713: systemd: after "systemd (231-1) unstable" update
> systemd-jurnald.service fails to start
>
> I’ve tried it on armel (SheevaPlug) and armmp (Cubox-i4Pro). It fails on
> both.
> I’ve also tried it on a
12 matches
Mail list logo
