SCIENTIFIC-LINUX-USERS Archives

May 2013

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"David G.Miller" <[log in to unmask]>
Reply To:
David G.Miller
Date:
Thu, 23 May 2013 05:59:50 +0000
Content-Type:
text/plain
Parts/Attachments:
text/plain (36 lines)
Elias Persson <delreich@...> writes:
<SNIP>
> On 2013-05-22 17:45, Joseph Thomas Szep wrote:
> > On Wed, May 22, 2013 at 08:06:47AM -0700, Yasha Karant wrote:
> >> Is there a single list of the various "stock" configuration files
> >> and directories used by the various applications that come with EL?

> If it's config files you're interested in, `rpm -qc ...` should
> limit that to just files the packager considers config'able.
> 
> Taking that one step further, this should get you a list of all
> such files:
> 
>      rpm -qac | grep -v -e '(contains no files)'
> 
> Keep in mind though that what the packager considers to be a
> config file (or for some other reason has marked as such) does
> not always correspond to what normally would be considered such.
> I certainly wouldn't have thought of /var/lib/rpm/* as configs...
> 
> 
In rpmbuild speak configuration files typically have two characteristics:

1) The file will usually be modified after installation, and
2) The modified file contains information that shouldn't be overwritten by
an update.

What we think of as configuration data fits this criteria but so do lots of
other files.  Probably a better name would be something like "user
configurable" or "configuration dependent."  Classifying a file as a config
file also gives the user a way to do rpm --verify and filter files that are
expected to not match what was installed.

Cheers,
Dave

ATOM RSS1 RSS2