News for hackers. Stuff that matters.

A comment on Winding down my Debian involvement. Parent comment

Re:Winding down my Debian involvement by perlgeek on Sunday March 10, 2019 @06:51PM (#19355236)
> dpkg -S path/to/file

In the case of config files, this only seems to work sometimes -- maybe if it wasn't modified by the user? Or if it came from a package directly, and wasn't generated from its {pre,post}inst scripts?

    $ dpkg -S /etc/hosts
    dpkg-query: no path found matching pattern /etc/hosts
    $ dpkg -S /etc/resolv.conf
    dpkg-query: no path found matching pattern /etc/resolv.conf
    $ dpkg -S /etc/bash_completion
    bash-completion: /etc/bash_completion
[ Parent | on HN ]
Re:Winding down my Debian involvement by JoshTriplett on Sunday March 10, 2019 @08:14PM (#19355671)
`dpkg -S /path/to/file` only works if the file belongs to a package. `/etc/resolv.conf` gets created dynamically at runtime. `/etc/hosts` gets created at installation time because it includes the hostname (which ought to get replaced with nss-myhostname).
[ Parent | on HN ]