Explain the relationship between port names and numbers.
Relationship Between Port Names and Numbers
Computers are very good with numbers, and, not surprisingly, they handle port numbers without a problem.
Humans, on the other hand, are better with names than numbers.
Assigning names to numbers
Linux allows administrators to assign a name to an actual port number. This way, the administrator or users may refer to the port by name or number.
For example, it's easier to remember the name "ftp" than it is to remember the FTP service port of 21, so the administrator can map the name "ftp" to port 21.
Mapping port names
Linux ships with port names mapped to numbers for many IANA-standard services.
However, if you wish to run services on non-standard ports or if you install a new network service, you might want to update your system's mapping.
The /etc/services text file maps port names to port numbers. In this file, Linux ignores blank lines and all commentary text after a hash ("#")
Otherwise, Linux expects the first field to be the primary service name (e.g., ftp), the second field to be the port number and protocol separated by a slash (e.g., 21/tcp), and all remaining fields to be aliases to the primary name.
Whitespace: As the name implies, any space between text that is empty. Whitespace includes spaces, tabs, new lines, and form feeds,
though programs may restrict what they consider to be whitespace to just a subset of these.