On Sep 12, 2017 12:49 PM, "Christian Göttsche" <cgzones@xxxxxxxxxxxxxx> wrote:
> This seems to revert what was an intentional change to avoid noise inIn my opinion, it's a helpful noise, which is triggered by an intended
> fixfiles check output. See the mailing list discussions that preceded and
> followed the patch.
file context `<<none>>`.
Is there any hack to get the old behavior back other than `find /run
-exec restorecon -n {} \;`?
Why is that helpful/useful? It seems counterintuitive to warn the user that you didn't label a file that was explicitly configured to not be labeled. The only case where it makes sense is if the user explicitly requested to label that particular file.