05-15-2008
This is a good link:
History of the Internet - Wikipedia, the free encyclopedia
Quote:
The term "Internet" was adopted in the first RFC published on the TCP protocol (RFC 675[1]: Internet Transmission Control Program, December 1974). It was around the time when ARPANET was interlinked with NSFNet, that the term Internet came into more general use,[13] with "an internet" meaning any network using TCP/IP. "The Internet" came to mean a global and large network using TCP/IP. Previously "internet" and "internetwork" had been used interchangeably, and "internet protocol" had been used to refer to other networking systems such as Xerox Network Services.[14]
As interest in wide spread networking grew and new applications for it arrived, the Internet's technologies spread throughout the rest of the world. TCP/IP's network-agnostic approach meant that it was easy to use any existing network infrastructure, such as the IPSS X.25 network, to carry Internet traffic. In 1984, University College London replaced its transatlantic satellite links with TCP/IP over IPSS.
Many sites unable to link directly to the Internet started to create simple gateways to allow transfer of e-mail, at that time the most important application. Sites which only had intermittent connections used UUCP or FidoNet and relied on the gateways between these networks and the Internet. Some gateway services went beyond simple e-mail peering, such as allowing access to FTP sites via UUCP or e-mail
4 More Discussions You Might Find Interesting
1. SuSE
I have set up my hostname in dhcp and my dns server, but I cannot get the client to pick up the hostname that is listed for the ip.
IE. 10.32.23.4 hostname should be client4
Anyone know why?
It was working before and just stopped working (1 Reply)
Discussion started by: 3junior
1 Replies
2. Shell Programming and Scripting
hi all,
i need to check the latest patch applied on my unix server. here is the server info:
bash-3.2$ uname -a
SunOS usa0300uz1226 5.10 Generic_148888-01 sun4u sparc SUNW,SPARC-Enterprise
please tell which is the command for checking patch? (1 Reply)
Discussion started by: lovelysethii
1 Replies
3. Linux
Heyas
-Just- installed Arch, and having difficulties to understand why my keyboard layout still is en_US, eventhough i had set it to be de_CH. *UTF-8 obviously*
This applies to console AND X.
* https://wiki.archlinux.org/index.php/Beginners%27_guide#Console_font_and_keymap
*... (0 Replies)
Discussion started by: sea
0 Replies
4. UNIX for Advanced & Expert Users
Heyas
For my project TUI i had prepared bash completion.
Bash-completion works, at least if i source that file manualy.
However, when i'm installing it, it wont apply, not even for new opened terminals.
Allthough i had it working once, i dont get why it doesnt work now.
<...>
+ ''
+... (0 Replies)
Discussion started by: sea
0 Replies
LEARN ABOUT NETBSD
sockstat
SOCKSTAT(1) BSD General Commands Manual SOCKSTAT(1)
NAME
sockstat -- list open sockets
SYNOPSIS
sockstat [-46clnu] [-f address_family] [-p ports]
DESCRIPTION
The sockstat command lists open Internet or UNIX domain sockets.
The following options are available:
-4 Show AF_INET (IPv4) sockets.
-6 Show AF_INET6 (IPv6) sockets.
-c Show connected sockets.
-f address_family
Limit listed sockets to those of the specified address_family. The following address families are recognized: inet, for AF_INET;
inet6, for AF_INET6; and local or unix, for AF_LOCAL.
-l Show listening sockets.
-n Numeric output only. No attempt will be made to look up symbolic names for addresses and ports.
-p ports Only show Internet sockets if either the local or foreign port number is on the specified list. The ports argument is a comma-
separated list of port numbers and ranges specified as first and last port separated by a dash.
-u Show AF_LOCAL (UNIX) sockets.
If neither -4, -6, nor -u are specified, sockstat will list sockets in all three domains.
If neither -c nor -l are specified, sockstat will list both listening and connected sockets, as well as those sockets that are in neither
state.
The information listed for each socket is:
USER The user who owns the socket.
COMMAND The command which holds the socket.
PID The process ID of the command which holds the socket.
FD The file descriptor number of the socket.
PROTO The transport protocol associated with the socket for Internet sockets, or the type of socket (stream, seqpacket or data-
gram) for UNIX sockets.
LOCAL ADDRESS For Internet sockets, this is the address to which the local end of the socket is bound (see getsockname(2)). For bound
UNIX sockets, it is the socket's filename or ``-''.
FOREIGN ADDRESS The address to which the foreign end of the socket is bound (see getpeername(2)) or ``-'' for unconnected UNIX sockets.
SEE ALSO
fstat(1), netstat(1), inet(4), inet6(4), unix(4)
HISTORY
The sockstat command appeared in FreeBSD 3.1. It was then rewritten for NetBSD 3.0.
AUTHORS
This version of the sockstat command was written by Andrew Brown <atatat@NetBSD.org>. This manual page was written by Dag-Erling Smorgrav
<des@FreeBSD.org> and was adapted to match the NetBSD implementation by Andrew Brown <atatat@NetBSD.org>.
BSD
July 14, 2006 BSD