Birmingham mumbai

[
 88 
]
Figure 3.2: Checking the location of the nmap binary
Now, when we run 
nmap
, we're actually running it from 
/snap/bin/nmap
. If we were 
to install 
nmap
 via 
apt
, it would run from 
/usr/bin/nmap
 instead. If we also have 
the 
nmap
 utility installed from Ubuntu's APT repositories, then we can run either 
one at any time by calling out the full path to the binary we want to run, since 
Snap packages are independent of the APT packages. For example, if we had 
nmap
 
installed via both 
snap
 and 
apt
, we could run Ubuntu's version by running 
/usr/
bin/nmap
 and the Snap version by running 
/snap/bin/nmap
.
Removing an installed Snap package is easy. We simply use the 
remove
 option:
sudo snap remove nmap
If we issue that command, then 
nmap
 (or whichever Snap package we designate) is 
removed from the system.
To update a package, we use the 
refresh
 option along with the name of a package to 
update:
sudo snap refresh
With that command, the package will be updated to the newest version available. 
Going even further, we can attempt to update every Snap on our server with the 
same command (without specifying a package):
sudo snap refresh
As you can see, managing Snap packages is fairly straightforward. Using the 
snap
 
suite of commands, we can install, update, or remove packages from our server 
or workstation. The 
snap find
 command allows us to find new Snap packages to 
install. Perhaps as the technology matures, we may find
 ourselves installing more 
Snap packages than Debian packages, but that remains to be seen. For now, it's a nice 
benefit to have two options to consider when installing new software.

---

Chapter 3