.8 part of the page name is indicating it's in section 8 of the man pages. Section
#8 is the manpage section that is specific to System administration commands... usually commands own or controlled by root.
man will load that page as long as it in a proper manpath. For Ubuntu, this path is configured in
You will find
/usr/share/man as one of the manpath locations. If you put that file (named.8) in the
/usr/share/man/man8 section it can be loaded with the command:
$ man named
This is assuming the file is located:
You can be more specific in loading that section with this command (which will load the same page:
$ man 8 named
You can see other examples of the structure by exploring the various man pages that have automatically been placed in the
/usr/share/man directory hierarchy.
If you properly compile and install the github package, it will place the manual in one of the manpath locations and be loaded with one of these two commands:
$ man named
$ man 8 named
The second of the two commands are specifying (as your question asks) how to open a.8 file.
Of course, you can get lots of other details about the man page commands and structure with the commands:
$ man man
$ man manpath
Each one of the document pages will have links at the bottom to explain in more details other related commands, of which you can followup with:
$ man [name of other references in the page]
Other ways of calling man pages/man files include:
You can also open any man page by specifying the direct namepath of the page. For instance:
$ man /usr/share/man/man8/named.8
$ man ./named.8
Since named.8 doesn't exist in a default ubuntu install, you can test this option on a page that actually exist (
$ man /usr/share/man/man8/apt.8.gz
$ man ./apt.8gz
When opening a page directly, rather than a page in the manpath, but keep in mind that if you are in the same folder as the page you would have to use
man ./manpagename.8, whereas
man manpagename.8 will search the manpath. It wouldn't see it, just as trying to call an execute file wouldn't see the command in the current directory unless that current directory was in the search path.
Related to your Google search for the
.8 extension, your hits would have been more specific to your question had you put quotes (") around the ".8" part of the question. Since it was a man page you were working with including the word man in the filter would have been even better.
This formatted question may help the next time you perform a Google search:
how to open a ".8" man file
Or, using the same search filter you put for your AU question:
How to open ".8" file with man?