On Wed, Feb 25, 2015 at 12:17 AM, Marc Espie <es...@nerim.net> wrote: > For instance, here's what pkg_check says on a somewhat older machine > I haven't cleansed in a while, along with my commentary. > > (warning, long post).
Indeed. > Like they said, the devil lies in the details. There are about 10 (or more) > special cases I haven't taken care of yet... > > Not found: > /.install_started > (fun, old bsd.rd stuff) > /basename.core > (fun, a core) > /bin/badsh > (okay, my bad, pie fuckup) > /bin/rcp > /bin/rmail > /bin/sum > (now, those are old things) > /boot Okay, I think I see that I don't need to worry about the unknown files/directories it reports. > (that one should be an exception) > /bsd > /bsd.120320 > /bsd.120828 > /bsd.120927 > /bsd.121106 > /bsd.130423 > /bsd.130430 > /bsd.130514 > /bsd.130711 > /bsd.130723 > /bsd.131015 > /bsd.131113 > /bsd.131210 > /bsd.140715 > /bsd.150121 > /bsd.rd > /bsd.sp > (should I ignore everything as bsd* ?) Depends on the purpose, I'd guess. > /dos Is that a mount point in your system, too? > /etc/X11/app-defaults/Beforelight > [...] So the file system is the package management system? Is, perhaps, pkg_check trying to do too many things, maybe? Anyway, now I'm pretty sure I can safely assume that, since pkg_info is working again, I don't have to scratch my ports partition and re-populate it from scratch. Still not sure why pkg_info and pkg_add were geting stuck until I used pkg_check. Thanks, Joel Rees
