Bug 147905

Summary: RFE: introduce booleans.d instead of/in addition to booleans file?
Product: [Fedora] Fedora Reporter: Alexandre Oliva <oliva>
Component: policycoreutilsAssignee: Daniel Walsh <dwalsh>
Status: CLOSED RAWHIDE QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: dwalsh, pgraner
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-04-21 15:02:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Alexandre Oliva 2005-02-12 14:16:37 UTC 
A single booleans file is a problem for updates/upgrades that
introduce new booleans, if you've ever modified the booleans file
before.  The new settings will be in booleans.rpmnew, and new `active'
defaults won't take effect.

One possibility to overcome this problem would be to only add booleans
that defaulted to false.

Another possibility is to switch from a single booleans file to a
directory structure: booleans.d/<property> containing either 0/1, or
<property>=0/1.  The latter won't waste space and makes it easier to
cat them all together, but it makes room for introducing unrelated
settings under different filenames.

It's more work in maintaining the rpm, for sure, but it makes for
cleaner upgrades.
Comment 1 Daniel Walsh 2005-04-21 15:02:16 UTC 
I have switched to using booleans.local instead of just booleans.

So now /etc/selinux/TYPE/booleans is config and booleans.local is config(noreplace)