Your point is basically my point. It takes forever to learn a huge number of cryptic two-letter commands to the point of reflexive keystroking. The problem IMHO was compounded by the inferiority of Unix's "man" pages to VAX-VMS "Help." Exempli gratia: "help search" vs (I think!) "man grep". If you don't already know the name of the Unix command, you'd better have a book or a cheat sheet handy.
If you don't already know the name of the Unix command, you'd better have a book or a cheat sheet handy.
I agree. VAX/VMS 'help' was much better. In fact, there were more than a few things about VAX/VMS that were better, and easier to understand and work with than with Unix. And I almost always had a 'cheat sheet' handy, even after many years.
But since DEC missed the boat, I went where the money was and Unix did grow on me. Even though it is cryptic, I developed the same respect, appreciation, and affection for Unix that I did for VAX/VMS.
>>Your point is basically my point. It takes forever to learn a huge number of cryptic two-letter commands to the point of reflexive keystroking<<
Cryptic? Why, what could possibly be more straightforward than:
NAME
netstat -- show network status
SYNOPSIS
netstat [-AaLlnW] [-f address_family | -p protocol] [-M core] [-N system]
netstat [-gilns] [-f address_family] [-M core] [-N system]
netstat -i | -I interface [-w wait] [-abdgt] [-M core] [-N system]
netstat -s [-s] [-f address_family | -p protocol] [-M core] [-N system]
netstat -i | -I interface -s [-f address_family | -p protocol] [-M core]
[-N system]
netstat -m [-M core] [-N system]
netstat -r [-Aaln] [-f address_family] [-M core] [-N system]
netstat -rs [-s] [-M core] [-N system]