New answers tagged libraries
A quick and dirty way on Linux (thanks to Lekensteyn): grep '/usr/lib/libssl1.*(deleted)' /proc/*/maps For precise parsing, you can call lsof with the -F option to get parsable output. Include the f field to filter on deleted files (fDEL) and the n field to get the path to the file. Note that the snippet below chokes on file names containing newlines. ...
I found two ways to do this: Debian-specific, lists most deleted/replaced files held by processes (with the exception of certain files known to be transient, e.g. stuff in /tmp): The debian-goodies package contains checkrestart, which accomplishes something like what I've described by scraping the output of lsof to find open files that are gone or replaced ...
Where do application layer protocols reside? Protocols are an abstraction, so they don't really "reside" anywhere beyond specifications and other documentation. If you mean, where are they implemented, there's a few common patterns: They may be implemented first in native C as libraries which can be wrapped by for use in other languages (since most ...
If you delete /usr/lib, you will kill your system as very crucial libraries reside in this directory. Like the LibC library which is used by all binaries. So it is unlikely that you will be able to something. (If you are lucky and interrupted the command with a quick CTRL+C before is comletion, maybe only sub-dirs are deleted and the LibC is still there) If ...
extundelete --restore-all when having your file system mounted as read-only. (Be sure you have a ext filesystem.) ! Be sure not to install it on the device you want to recover !
So this is how I get information in order to provide explicit dependencies for the spec file: Requires: see my script here; BuildRequires: use auti-buildrequires tool from Richard Jones;
Top 50 recent answers are included