OS: Ubuntu 19.10
When I ran locate plymouth, I got
dkb@dkb-uee:~$ locate plymouth
Command 'locate' not found, but can be installed with:
sudo apt install mlocate
dkb@dkb-uee:~$
So I installed mlocate and now locate works.
As far as I can remember, since Ubuntu 11.04, locate has always been there.
Why was it excluded in Ubuntu 19.10?
There are the commands find and locate to search for files on the disk.
I know that find recursively processes all needed subdirectories to search files and therefore is slow but up-to-date, whereas locate uses a database that gets updated every now and then (when exactly?) to quickly show results which might be outdated though.
Are there any other differences? In which situations would one prefer the one or the other? And when does the locate database get updated usually?
I'm wondering to know that what difference is the between using + and ; at the end of -exec command when I use in find command?
find .... -exec ... \;
VS
find .... -exec ... +
I have a directory somewhere on my server wth the name "exampledocs". I tried to find it's location using:
ls -d */ | grep -E 'exampledocs'
and
find * -regextype posix-extended \-regex 'exampledocs' \-type d
and
grep "exampledocs" * --recursive
Nothing worked. How can I do this from the command line? I'm using Ubuntu Server 11.0.
Background: I'm trying to build my program but first I need to set up libraries in NetBeans. My project is using GLU and therefore I installed libglu-dev. I didn't note the location where the libraries were located and now I can't find them.
I've switched to Linux just a few days ago and so far I'm very content with it, however I couldn't google this one out and became frustrated. Is there way to find out where files of package were installed without running the installation again? I mean if I got library xxx and installed it some time ago, is there some-command xxx that will print this info?
I've already tried locate, find and whereis commands, but either I'm missing something or I just can't do it correctly. For libglu, locate returns:
/usr/share/bug/libglu1-mesa
/usr/share/bug/libglu1-mesa/control
/usr/share/bug/libglu1-mesa/script
/usr/share/doc/libglu1-mesa
/usr/share/doc/libglu1-mesa/changelog.Debian.gz
/usr/share/doc/libglu1-mesa/copyright
/usr/share/lintian/overrides/libglu1-mesa
/var/lib/dpkg/info/libglu1-mesa:i386.list
/var/lib/dpkg/info/libglu1-mesa:i386.md5sums
/var/lib/dpkg/info/libglu1-mesa:i386.postinst
/var/lib/dpkg/info/libglu1-mesa:i386.postrm
/var/lib/dpkg/info/libglu1-mesa:i386.shlibs
The other two commands fail to find anything. Now locate did its job, but I'm sure none of those paths is where the library actually resides (at least everything I was linking so far was in /usr/lib or /usr/local/lib).
libglu was introduced just as example. I'm looking for a general solution for this problem.