No - I don’t have any empirical data for this. But …
if I should name the top 5 frustrations of Linux beginners, then the “command-not-found” errors would be most certainly on this list.
Especially if you are new to the Linux command line, it’s not always obvious what is causing this error.
First: You simply don’t know all the tools
As you start exploring the Linux command line (aka “the Linux shell”), you simply don’t yet know the tools that are available there.
There are a load of them and unfortunately not every tool is available on every Linux distribution. And don’t worry - you will get to know them step-by-step once you proceed through your Linux journey.
(I’ll show you a shortcut for getting all the really essential tools later on - but that’s _not_ the point of this post at all)
The point here is …
The shell searches in it’s own way …
To understand (and really overcome) these “command not found” errors, we need to understand what causes them, don’t we?
So let’s face the challenge and let’s have a look how the shell searches for a command to run.