Saturday, 16 March 2019

Telnet

One of the driving forces behind the development of ARPAnet was the desire to afford researchers at various locations the ability to log on to remote computers and run programs. At the time, there were very few computers in existence and only a handful of powerful supercomputers (though the supercomputers of the early 1970s were nowhere near as powerful as the desktop machines of today).
Along with e-mail, remote logon was one of the very first capabilities built into the ARPAnet.
Today, there is less reason for logging on to a remote system and running programs there. Most major government agencies, colleges, and research facilities have their own computers, each of which is as powerful as the computers at other sites.
TCP/IP provides a remote logon capability through the Telnet protocol. Users generally log in to a UNIX shell account on the remote system using a text-based or graphics-based terminal program. With Telnet, the user can list and navigate through directories on the remote system and run programs.
The most popular programs run on shell accounts are probably e-mail programs, such as PINE; Usenet news readers, such as nn or rn; and text editors, such as vi or Emacs. Students are the most common users of Telnet these days; professors, scientists, and administrators are more likely to have a more direct means of access to powerful computers, such as an X Windows terminal.
Most Web browsers don't include built-in Telnet capabilities. Telnet connections are usually established using a stand-alone terminal program, such as that shown in figure 1.4. These programs can also be used by those who want Telnet capabilities on the Web by configuring them as browser helper applications. 

No comments:

Post a Comment