> 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)...
I'm a little bit confused, since neither of my Woody nor Sid systems has /usr/include/unix.h. Also, using apt-file I don't see *any* package that has it. > So, now I cant get some stuff to compile due to the header file > being wrong... What stuff? Perhaps that will answer my above question. > 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." True enough. > 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... Sometimes this happens because a file (usually a configuration file) is created in a package's post-install step. However, like I said before, I don't see any likely candidates; I'm wondering how this file came to be in the first place. > 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? That is called "trolling." Please don't. Lucas -- Lucas Bergman <[EMAIL PROTECTED]> Tired of getting duplicate copies of mailing list messages? I respect the 'mail-followup-to' header field: http://cr.yp.to/proto/replyto.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
