(another of those "dang, i never noticed that before" questions inspired by teaching last week.)
currently, my fedora 27 system has the file /etc/issue.net, which i casually explained last week was what was printed when you tried to connect to the system over the network (as opposed to /etc/issue). but while my fedora system has the man page "man -s 5 issue", it does *not* have "man -s 5 issue.net".
i thought this was odd since both of the files appear to be installed by the same package:
$ rpm -qf /etc/issue fedora-release-27-1.noarch $ rpm -qf /etc/issue.net fedora-release-27-1.noarch $
so why would the man pages not similarly both be there? well, the man page for /etc/issue comes from here:
$ rpm -qf /usr/share/man/man5/issue.5.gz man-pages-4.12-1.fc27.noarch $
while a yum query points out where the man page for /etc/issue.net would come from:
$ yum whatprovides /usr/share/man/man5/issue.net.5.gz telnet-server-1:0.17-71.fc27.x86_64 : The server program for the Telnet remote login protocol Repo : fedora Matched from: Filename : /usr/share/man/man5/issue.net.5.gz
i guess that makes sense since i can see from online that man page, which explains that /etc/issue.net is related to telnet only:
https://linux.die.net/man/5/issue.net
which specifically claims, "The file /etc/issue.net is a text file which contains a message or system identification to be printed before the login prompt of a telnet session."
so, apparently, /etc/issue.net is telnet-specific? i had no idea. in any event, it still seems odd to generically install the file /etc/issue.net, while the man page for the same file needs the installation of telnet-server to show up. is this worth a bugzilla filing, or is there something else happening here i don't understand?
rday
-
Robert P. J. Day