Commands in two Linux systems

In Windows, there are several very practical commands that can be used to locate some network problems. In Linux, the command name is a bit different. 1. NSlookup, which is replaced by Dig in Linux, dig provides more detailed information, and, in turn, has a dig_for_win, and can be used in Windows dig; 2, tracert, can be replaced by traceroute in Linux, however, there is a small problem, that is, when a route is separated, a bunch of *** information is returned and no useful information is found. The following is available: root # traceroute-I 192.168.1.1 (or other IP addresses)-What does I mean? Man knows:-I use ICMP echo instead of UDP batch rams. There are several more common ones, such as dmesg, PS, top, nohub, ifconfig.... I will try again later. Record memo: escapecommfunction

TheEscapecommfunctionFunction directs a specified communications device to perform an extended function.

 
Bool Escapecommfunction (Handle Hfile,DWORD Dwfunc);
 

Ami quotations (http://spaces.msn.com/aimingoo ):
 

 
Any mature technology has its roots in development. If you only look at the surface of a technology, you don't know why ". Therefore, we should investigate the historical root causes, such as why "interface", why "com is binary standard", and "Why TLB is required ". These things have evolved a little in the background of history.

With these foundations, let's look at the theory of COM. every concept of COM should always be related to some problems. --Is it easier to look at the answer in a question than to look at the answer?
The root cause is that you cannot see "where is the problem" or "What is the original problem ".