Brad Stockdale <bradsprt@greenepa.net> [2004:01:08:13:32:36-0500] scribed: > Hello all, > > I am a newbie to Debian and I made a booboo.. While prepping a system > for production use, I accidentally overwrote /usr/include/unix.h with the > unix.h that comes from the imap2002e library (used by PHP to enable it to > use POP and IMAP protocols)... > > So, now I cant get some stuff to compile due to the header file being > wrong... > > My initial thought was "Well, if Debian's package management is > anything like Redhat's, I should be able to find out what package owns that > file, and then I can reinstall the package." > > So, I do a: > > dpkg -S unix.h > > And it gives me no results... Well, gives me an auth_unix.h file, which > isnt what I'm looking for... > > My question is: If Debian packages are just as good if not better than > Redhat RPM's, then why can I not find out what package owns that file? > > Am I using the wrong command? I suggest, if you know the full path to a file, then _first_ use that with dpkg: dpkg -S /usr/include/unix.h That way, you will get the definitive answer -- in this case: dpkg: /usr/include/unix.h not found. Without the path to a file, dpkg -S gives you every package that has a file that matches the regular expression, in your case: unix.h which happens to match: libc6-dev: /usr/include/rpc/auth_unix.h hth -- Best Regards, mds mds resource 877.596.8237 - Dare to fix things before they break . . . - Our capacity for understanding is inversely proportional to how much we think we know. The more I know, the more I know I don't know . . . --
Attachment:
pgp7ReeiFL50c.pgp
Description: PGP signature