--- Ed Wilts <[EMAIL PROTECTED]> wrote:
> On Tuesday 03 April 2001 15:42, John Cavan wrote:
>
> > > what's wrong with .rpmnew ?
> >
> > Nothing for me, but think about it from a newbie perspective. They will
> > likely think that something went wrong during installation and around a
> > rather critical file.
> >
> > Basically, all I'm suggesting is that we treat /etc/passwd and similar
> > files like XF86Config... create it, never install it. After that, specific
> > packages can add or remove as needed, including setup.
>
> I disagree. I regularly go through and search for .rpmnew files and then
> compare what's in them with my own versions. Sometimes there are new
> defaults or options that weren't there when I did my own customizations. I
> then decide to either toss my file and start with the .rpmnew version, or
> apply some changes to my own.
I do the same as you with rpmnew, rpmorig and rpmsave files, but I think you
are wrong. The diff technique is difficult to apply to the password or group
files, just because of the nature of those files. For instance, there may be
entries that are not on the defult file, but where *not* created by you,
instead by some rpm or non-rpm software package install. These issues may be
easy to sort out by a competent admin that knows each and every one of the IDs
byu memory, but can become very confusing for the average Unix competent joe.
They issue at hand is that having an rpmnew file implies there are changes to
be made, when in fact the setup rpm package runs the update-password utility.
You do one of the two, but not both ... Besides, the default master lists are
always available as:
/usr/share/base-passwd/group.master
/usr/share/base-passwd/passwd.master
So why also have them as rpmnew?
=====
________________________
Eugenio Diaz, BSEE/BSCE
Linux Engineer
[EMAIL PROTECTED]
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
