> When the policy rpm is installed(or updated) it puts the .rpmnew files > in place. (the date is from when they were built on the build system). > Then the policy-source package is installed and the files (policy.n and > file_contexts) are built as part of the install(or update). > > I always delete the .rpmnew file. OK, so now I am confused again. I moved all the rpmnew files to /tmp and did an rpm -V policy. I got the following: [root@dad root]# rpm -V policy .......TC c /etc/security/default_contexts .......TC c /etc/security/default_type .......TC c /etc/security/failsafe_context .......TC c /etc/security/initrc_context S.5....TC c /etc/security/selinux/file_contexts ..5....T. c /etc/security/selinux/policy.15 ..5....T. c /etc/security/selinux/policy.16 ..5....T. c /etc/security/selinux/policy.17 .......TC c /root/.default_contexts Then I moved the "regular" files to /tmp and moved the rpmnew files into their places and got the following: [root@dad root]# rpm -V policy .......TC c /etc/security/default_contexts .......TC c /etc/security/default_type .......TC c /etc/security/failsafe_context .......TC c /etc/security/initrc_context .......T. c /etc/security/selinux/file_contexts .......TC c /root/.default_contexts Which seems to indicate that the rpmnew files should be copied over the "old" files. As I recall, there are rpmorig and rpmnew files that get installed with an rpm. rpmorig files are put into place when the new config file replaces the old one and the old one is saved as the rpmorig. The rpmnew file should then be where the old file is kept in place, but the new file is saved "on the side". Is there "official" word? This is really dumb that this bugs me this much.
