On 2020-05-25 21:52, Patrick O'Callaghan wrote:
> On Mon, 2020-05-25 at 20:35 +0800, Ed Greshko wrote:
>> On 2020-05-25 20:20, Patrick O'Callaghan wrote:
>>> On Mon, 2020-05-25 at 16:56 +0800, Ed Greshko wrote:
On 2020-05-25 15:36, Ron Yorston wrote:
> On 6th May an update to selinux-
On Mon, 2020-05-25 at 20:35 +0800, Ed Greshko wrote:
> On 2020-05-25 20:20, Patrick O'Callaghan wrote:
> > On Mon, 2020-05-25 at 16:56 +0800, Ed Greshko wrote:
> > > On 2020-05-25 15:36, Ron Yorston wrote:
> > >
> > > > On 6th May an update to selinux-policy for Fedora 32 (3.14.5-38.fc32)
> > > >
On 2020-05-25 20:20, Patrick O'Callaghan wrote:
> On Mon, 2020-05-25 at 16:56 +0800, Ed Greshko wrote:
>> On 2020-05-25 15:36, Ron Yorston wrote:
>>
>>> On 6th May an update to selinux-policy for Fedora 32 (3.14.5-38.fc32)
>>> caused all filesystems to be relabelled. In my case this took over
>>>
On Mon, 2020-05-25 at 16:56 +0800, Ed Greshko wrote:
> On 2020-05-25 15:36, Ron Yorston wrote:
>
> > On 6th May an update to selinux-policy for Fedora 32 (3.14.5-38.fc32)
> > caused all filesystems to be relabelled. In my case this took over
> > twelve hours. I was not happy.
>
>
> Thanks for
On 2020-05-25 15:36, Ron Yorston wrote:
> On 6th May an update to selinux-policy for Fedora 32 (3.14.5-38.fc32)
> caused all filesystems to be relabelled. In my case this took over
> twelve hours. I was not happy.
Thanks for the Heads-UP. I suppose we'll soon find out how many people didn't
re
On 6th May an update to selinux-policy for Fedora 32 (3.14.5-38.fc32)
caused all filesystems to be relabelled. In my case this took over
twelve hours. I was not happy.
It appears the developers have a workaround for the problem but the
update that applies it will cause all filesystems to be rela
