Re: Has the boot param syntax/semantics changed?

[Tom London <selinux@xxxxxxxxxxx>]

Yeah, you don't want to set SELINUXTYPE to permissive. That appears to 
be the
same as selecting the 'targeted' policy. (I guess, 'not strict').
(The comment in the config file says SELINUXTYPE can take one of two
values, targeted or strict).

To select permissive mode, you set SELINUX=permissive. For me, setting
SELINUX to permissive is the same as booting with 'enforcing=0'.

tom

> ------------------------------------------------------------------------
>
>     * /From/: Bob Gustafson <bobgus rcn com>
>
> If POLICYTYPE is no longer used, then the file that contains that
> deprecated param should be either overwritten during the 'yum update'
> process, or a note or message should show up somewhere (visibly) during the
> 'yum update' process.
>
> If the user's config file is not changed, but the program changes in the
> 'yum update', then there is a problem (perhaps even a 'process bug').
>
> Is there a 'permissive' value for SELINUXTYPE?
>
> Using the boot param 'enforcing=0' seems to be different than setting the
> SELINUXTYPE=permissive for me.
>
> enforcing=0 was less permissive...
>
> BobG
>