Where is UNIX applied presently Post: 302195564

Sponsored Content

Special Forums UNIX and Linux Applications Where is UNIX applied presently Post 302195564 by Neo on Thursday 15th of May 2008 11:10:43 AM

05-15-2008

Administrator

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

Neo

View Public Profile for Neo

Visit Neo's homepage!

Find all posts by Neo

4 More Discussions You Might Find Interesting

1. SuSE

HOSTNAME not being applied

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

2. Shell Programming and Scripting

Check latest patch applied on UNIX server

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?

3. Linux

[archLinux] keymap not applied?

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 *...

4. UNIX for Advanced & Expert Users

Bash-Completion, installed but not applied

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. <...> + '' +...

LEARN ABOUT MOJAVE

getpeereid

GETPEEREID(3)						   BSD Library Functions Manual 					     GETPEEREID(3)

NAME

     getpeereid -- get the effective credentials of a UNIX-domain peer

LIBRARY

     Standard C Library (libc, -lc)

SYNOPSIS

     #include <sys/types.h>
     #include <unistd.h>

     int
     getpeereid(int s, uid_t *euid, gid_t *egid);

DESCRIPTION

     The getpeereid() function returns the effective user and group IDs of the peer connected to a UNIX-domain socket.	The argument s must be a
     UNIX-domain socket (unix(4)) of type SOCK_STREAM on which either connect(2) or listen(2) have been called.  The effective used ID is placed
     in euid, and the effective group ID in egid.

     The credentials returned to the listen(2) caller are those of its peer at the time it called connect(2); the credentials returned to the
     connect(2) caller are those of its peer at the time it called listen(2).  This mechanism is reliable; there is no way for either side to
     influence the credentials returned to its peer except by calling the appropriate system call (i.e., either connect(2) or listen(2)) under
     different effective credentials.

     One common use of this routine is for a UNIX-domain server to verify the credentials of its client.  Likewise, the client can verify the cre-
     dentials of the server.

IMPLEMENTATION NOTES

     On FreeBSD, getpeereid() is implemented in terms of the LOCAL_PEERCRED unix(4) socket option.

RETURN VALUES

     The getpeereid() function returns the value 0 if successful; otherwise the value -1 is returned and the global variable errno is set to indi-
     cate the error.

ERRORS

     The getpeereid() function fails if:

     [EBADF]		The argument s is not a valid descriptor.

     [ENOTSOCK] 	The argument s is a file, not a socket.

     [ENOTCONN] 	The argument s does not refer to a socket on which connect(2) or listen(2) have been called.

     [EINVAL]		The argument s does not refer to a socket of type SOCK_STREAM, or the kernel returned invalid data.

SEE ALSO

     connect(2), getpeername(2), getsockname(2), getsockopt(2), listen(2), unix(4)

HISTORY

     The getpeereid() function appeared in FreeBSD 4.6.

BSD
								   July 15, 2001							       BSD