On Sat, May 21 2016, Laurent Bigonville wrote:
> Le 21/05/16 à 21:53, Yuri D'Elia a écrit :
>> Sorry for the delay, but I wanted to actually give it a try before
>> giving feedback.
>>
>> Indeed, that obviously fixes the problem.
>>
>> So is this actually a patch local to debian
Le 21/05/16 à 21:53, Yuri D'Elia a écrit :
On Fri, May 13 2016, Laurent Bigonville wrote:
Can you please try the patch that has been attached to the bug and tell
me if it's fixing your issue?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823184#44
Sorry for the delay,
On Fri, May 13 2016, Laurent Bigonville wrote:
> Can you please try the patch that has been attached to the bug and tell
> me if it's fixing your issue?
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823184#44
Sorry for the delay, but I wanted to actually give it a try
Can you please try the patch that has been attached to the bug and tell
me if it's fixing your issue?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823184#44
Le 13/05/16 à 17:49, Laurent Bigonville a écrit :
Le 13/05/16 à 17:16, Yuri D'Elia a écrit :
On Fri, May 13 2016, Laurent
Le 13/05/16 à 17:16, Yuri D'Elia a écrit :
On Fri, May 13 2016, Laurent Bigonville wrote:
Again this is supposed to happen at early boot, and at this stage, only
PID1 exists. So I doubt there is a lot of concurrent processes at that time.
But this is not checked in the
On Fri, May 13 2016, Laurent Bigonville wrote:
> Again this is supposed to happen at early boot, and at this stage, only
> PID1 exists. So I doubt there is a lot of concurrent processes at that time.
But this is not checked in the source.
In fact, this behavior will happen
Le 13/05/16 à 15:12, Yuri D'Elia a écrit :
On Fri, May 13 2016, Laurent Bigonville wrote:
libselinux mounts /proc, check is the machine supports SELinux and then
unmounts it. This is supposed to happen at early boot.
I don't understand what selinux is trying to solve here.
On Fri, May 13 2016, Laurent Bigonville wrote:
> libselinux mounts /proc, check is the machine supports SELinux and then
> unmounts it. This is supposed to happen at early boot.
I don't understand what selinux is trying to solve here. It's not the
job of a library to mount
reassign 823184 libselinux1 2.5-1
affects 823184 mount
thanks
On Sun, 1 May 2016 23:06:54 +0200 Yuri D'Elia wrote:
>
> Amusing, right? But not too much.
>
> It does actually happen due to a new behavior in libselinux, which
mount links against.
> The same is true for any
Package: mount
Version: 2.28-1
Severity: important
Amusing, right? But not too much.
It does actually happen due to a new behavior in libselinux, which mount links
against.
The same is true for any binary in util-linux and coreutils (and so on)
See bug #822679
I consider this behavior
10 matches
Mail list logo