A colleague writes: "I put the reporting program on the server, in /srv/package-lab. Run lab-pkg-report and send me the output." See what is in the directory and run the program.
Run your colleague's program
You are in /srv/package-lab. See what the directory holds and run lab-pkg-report.
First, predict
Your colleague is sure the program is already on the server. What will lab-pkg-report print?
Now start the exercise, run the command and compare your prediction with the output.
Why did the shell not find lab-pkg-report, although files with that name are in /srv/package-lab?
-
Read access is there:
lsprinted the directory contents. The shell found no program by that name, so permissions never came into play. -
A new terminal finds the same: the directory holds two
.debfiles, and there is nolab-pkg-reportprogram file anywhere. -
The shell would find and start a broken program, and it would print an error of its own. Here the program was not found:
command not found.
The .deb files are archives: the program sits inside them until the package is installed.