- https://en.wikipedia.org/wiki/Dpkg
- https://en.wikipedia.org/wiki/Dpkg#Database: /var/lib/dpkg/…
- https://en.wikipedia.org/wiki/Rpm_(software)
- https://en.wikipedia.org/wiki/Rpm_(software)#Local_RPM_installation_database: /var/lib/rpm/…
- https://unix.stackexchange.com/questions/634/what-are-the-pros-cons-of-deb-vs-rpm
RPM based environments support verifying and resetting permissions and user/group ownerships of files in a package:
- https://www.cyberciti.biz/tips/reset-rhel-centos-fedora-package-file-permission.html –
- https://ashok-linux-tips.blogspot.de/2011/12/how-to-reset-permissions-of-installed.html
- https://www.novell.com/coolsolutions/feature/16238.html
But what about Debian based ones? On Debian there is a file for every (installed) package:
/var/lib/dpkg/info/package.list
That file only includes filenames and directory names (and no details at all). Directories are not marked as directories (as opposed to files). Files within those directories do not necessarily get listed themselves.
That file gets searched for:
- “
dpkg --search” – which Debian package does a given file belong to? - “
dpkg --listfiles” – which files belong to a given Debian package?
What about the Debian utility cruft:
- https://wiki.debian.org/Cruft
- https://en.wikipedia.org/wiki/Cruft_(software)
- https://packages.debian.org/stretch/cruft
- https://alioth.debian.org/projects/cruft/
cruft cannot really be able to provide details not contained in that file.
Other Unix-like operating systems:
Leave a Reply