On Thu, 2010-01-07 at 08:28 -0500, Matthew Saltzman wrote:
> On Thu, 2010-01-07 at 16:31 +1030, Tim wrote:
> > On Wed, 2010-01-06 at 17:40 +1100, Cameron Simpson wrote:
> > > The best approach is usually to identify your own change, make the
> > > same change in the .rpmnew file, then mv the .rpmnew file into place.
> >
> > What about SELinux issues when you mv instead of create new files?
>
> I conjecture that it's not a problem in this case, as the perms are the
> same for the new and old files:
>
> $ ls -lZ /etc/login.defs*
> -rw-r--r--. root root system_u:object_r:etc_t:s0 /etc/login.defs
> -rw-r--r--. root root system_u:object_r:etc_t:s0 /etc/login.defs.rpmnew
>
Should also have pointed out that running restorecon after mv would
solve any such problems, at least for these system files.
--
Matthew Saltzman
Clemson University Math Sciences
mjs AT clemson DOT edu
http://www.math.clemson.edu/~mjs
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
