12.07.2015 Views

Red Hat Enterprise Linux 5 Administration Unleashed

Red Hat Enterprise Linux 5 Administration Unleashed

Red Hat Enterprise Linux 5 Administration Unleashed

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

134CHAPTER 5Working with RPM SoftwareLISTING 5.6Continuedmissing /usr/lib/mozilla-1.7.12/chrome/overlayinfo/cookie/contentmissing /usr/lib/mozilla-1.7.12/chrome/overlayinfo/editormissing /usr/lib/mozilla-1.7.12/chrome/overlayinfo/editor/contentmissing /usr/lib/mozilla-1.7.12/chrome/overlayinfo/globalmissing /usr/lib/mozilla-1.7.12/chrome/overlayinfo/global/contentmissing /usr/lib/mozilla-1.7.12/chrome/overlayinfo/global/skinS.5....T c /etc/ntp/ntpserversS.5....T c /etc/audit.rulesIn Listing 5.5, the c to the left of the filename indicates that the file is a configurationfile. Other possible attribute markers include d for documentation files, g for ghost files(file contents are not included in the package payload), l for license files, and r forreadme files.The letters, numbers, and dots at the beginning of each line detail how the file differsfrom the original state of the file. As shown in Listing 5.6, if a file is no longer installed,the word missing appears instead of the sequence of codes. Otherwise the eight letters,numbers, and dots represent eight different tests performed to verify the file. Table 5.3explains the codes that appear in the sequence in the order in which they appear if anyof the tests fail. If a dot is shown instead of a code letter or number, the test passed.TABLE 5.3 RPM Verification CodesCode ExplanationSFile size has changedMMode has changed, including file permissions and file type5 MD5 sum has changedDDevice major or minor number has changedLThe path of the symbolic link has changedUThe owner of the file has changedGThe group of the file has changedTThe last modified time has changedQuerying Package FilesYou now know that an RPM database on the system keeps track of which files are associatedwith each RPM installed, but how do you know which files are associated withwhich RPM packages? You can query the RPM database and find out with the followingcommand:rpm -qf The must be the full path to the file. If the file is associated with an RPMpackage installed, the name of the package and the version installed is displayed. For

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!