DOCSLIB.ORG

Socket() System Call Family: PF INET 0 Family: PF INET Bind the Socket to an Address Using the Bind() System Service:Service: SOCK STREAMSOCK STREAM Call

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Socket() System Call Family: PF INET 0 Family: PF INET Bind the Socket to an Address Using the Bind() System Service:Service: SOCK STREAMSOCK STREAM Call Process Process Process Layer CSCE 515: Computer Network TCP UDP Transport Layer Programming ------ Sockets ICMP, ARP & IP Network Layer Wenyuan Xu RARP Department of Computer Science and Engineering University of South Carolina 802.3 Data-Link Layer 9/8/2008 CSCE515 – Computer Network Programming Network API Network API API - Application Programming Interface API is a set of functionality/services delivered by a Internet OSI model Application programming system. protocol suite details Application User processor Presentation Application Network API Session The services ( often provided by the operating system) Transport TCP UDP that provide the interface between application and Network IPv4, IPv6 protocol software. Data link Data link kernel Physical Physical Communications details 9/8/2008 CSCE515 – Computer Network Programming 9/8/2008 CSCE515 – Computer Network Programming Network API wish list TCP/IP Generic Programming Interface. TCP/IP does not include an API definition. Support multiple communication protocol suites (families). Address (endpoint) representation independence. There are a variety of APIs for use with Provide special services for Client and Server? TCP/IP: Sockets by Berkeley Support for message oriented and connection XTI (X/Open Transport Interface) by AT&T oriented communication. Winsock - Windows Sockets API by Microsoft Work with existing I/O services (when this MacTCP / Open Transport by Apple makes sense). Operating System independence 9/8/2008 CSCE515 – Computer Network Programming 9/8/2008 CSCE515 – Computer Network Programming Client-Server Model Functions needed: Client 1 Specify local and remote communication Server Client 2 endpoints Initiate a connection Client 3 Wait for incoming connection One side of communication is client, and the other side Send and receive data is server Terminate a connection gracefully Server waits for a client request to arrive Server processes the client request and sends the Error handling response back to the client Iterative or concurrent 9/8/2008 CSCE515 – Computer Network Programming 9/8/2008 CSCE515 – Computer Network Programming Berkeley Sockets Elements of a Socket A socket is an abstract representation of a Each socket can be uniquely identified by communication endpoint. Source IP address Generic: Source port number support for multiple protocol families. address representation independence Destination IP address Destination port number Sockets (obviously) have special needs: An end-to-end protocol (TCP or UDP) establishing a connection specifying communication endpoint addresses Sockets work with Unix I/O services just like files, pipes & FIFOs 9/8/2008 CSCE515 – Computer Network Programming 9/8/2008 CSCE515 – Computer Network Programming Types of Sockets Stream Sockets Two different types of sockets Also known as connection-oriented socket Stream sockets Use TCP Datagram sockets Provide reliable, connected networking service Error free; no out-of-order packets Applications: telnet, ssh, http 9/8/2008 CSCE515 – Computer Network Programming 9/8/2008 CSCE515 – Computer Network Programming Datagram Sockets Unix Descriptor Table Also known as connectionless socket Descriptor Table Use UDP Data structure for file 0 Provide unreliable, best-effort networking 0 service 1 Data structure for file 1 Packets may be lost; may arrive out of 2 order 3 Data structure for file 2 Applications: streaming audio/video 4 int fd; int cc, nbytes; char *buf; fd = open (my_filename, O_RDONLY ); cc = write (fd, buf, nbytes); cc = read (fd, buf, nbytes); 9/8/2008 CSCE515 – Computer Network Programming 9/8/2008 CSCE515 – Computer Network Programming Socket Descriptor Data Structure Client-Server Model Server Descriptor Table Create a socket with the socket() system call Family: PF_INET 0 Family: PF_INET Bind the socket to an address using the bind() system Service:Service: SOCK_STREAMSOCK_STREAM call. For a server socket on the Internet, an address 1 LocalLocal IP:IP: 111.22.3.4111.22.3.4 consists of a port number on the host machine. RemoteRemote IP:IP: 123.45.6.78123.45.6.78 2 Listen for connections with the listen() system call LocalLocal Port:Port: 22492249 3 RemoteRemote Port:Port: 37263726 Accept a connection with the accept() system call. This call typically blocks until a client connects with 4 the server. int s, family, type, protocol; Send and receive data s = socket(family, type, protocol); etc... cc = read(s, buf, nbytes); 9/8/2008 CSCE515 – Computer Network Programming 9/8/2008 CSCE515 – Computer Network Programming Client-Server Model Creating a Socket Client int socket(int family,int type,int proto); Create a socket with the socket() system call specifies the protocol family Connect the socket to the address of the family AF_INET: IPv4 protocols server using the connect() system call AF_INET6: IPv6 protocols AF_ROUTE: Routing sockets Send and receive data. There are a number type specifies the type of service SOCK_STREAM of ways to do this, but the simplest is to use SOCK_DGRAM the read() and write() system calls. SOCK_RAW protocol specifies the specific protocol (usually 0, which means the default). IPPROTO_TCP: TCP transport protocol IPPROTO_UDP: UDP transport protocol 9/8/2008 CSCE515 – Computer Network Programming 9/8/2008 CSCE515 – Computer Network Programming socket() Specifying an Endpoint Address The socket() system call returns a Remember that the sockets API is generic socket descriptor (small integer) or -1 on error. There must be a generic way to specify endpoint addresses. socket() allocates resources needed for TCP/IP requires an IP address and a port a communication endpoint - but it does not number for each endpoint address. deal with endpoint addressing. 9/8/2008 CSCE515 – Computer Network Programming 9/8/2008 CSCE515 – Computer Network Programming Necessary Background Information: bind() POSIX data types calling bind() assigns the address specified by the sockaddr structure to the int8_t signed 8bit int socket descriptor. uint8_t unsigned 8 bit int int16_t signed 16 bit int bind( mysock, (struct sockaddr*) &myaddr, uint16_t unsigned 16 bit int sizeof(myaddr) ); int32_t signed 32 bit int uint32_t unsigned 32 bit int 9/8/2008 CSCE515 – Computer Network Programming 9/8/2008 CSCE515 – Computer Network Programming More POSIX data types Generic socket addresses el rn ke y sa_family_t address family struct sockaddr { b ed s socklen_t length of struct uint8_t sa_len; U in_addr_t IPv4 address sa_family_t sa_family; char sa_data[14]; in_port_t IP port number }; sa_family specifies the address type. sa_data specifies the address value. 9/8/2008 CSCE515 – Computer Network Programming 9/8/2008 CSCE515 – Computer Network Programming sockaddr AF_CSCE515 An address that will allow me to use sockets Initializing a sockaddr structure to point to communicate with you. to Henry : address type AF_CSCE515 address values: struct sockaddr henry; Dean 1 Sayan 6 Devon 2 Yuliya 7 henry.sa_family = AF_CSCE515; Samuel 3 Razvan 8 henry.sa_data[0] = 5; Shamik 4 Mythri 9 Henry 5 Femitolu 10 9/8/2008 CSCE515 – Computer Network Programming 9/8/2008 CSCE515 – Computer Network Programming AF_INET struct sockaddr_in (IPv4) For AF_CSCE515 we only needed 1 byte struct sockaddr_in { to specify the address. uint8_t sin_len; sa_family_t sin_family; in_port_t sin_port; For AF_INET we need: ly! on struct in_addr sin_addr; 16 bit port number v4 IP char sin_zero[8]; 32 bit IP address }; A special kind of sockaddr structure 9/8/2008 CSCE515 – Computer Network Programming 9/8/2008 CSCE515 – Computer Network Programming struct in_addr Byte Ordering struct in_addr { Different computer architectures use in_addr_t s_addr; different byte ordering to represent }; multibyte values. 16 bit integer: in_addr just provides a name for the ‘C’ type associated with IP addresses. Low Byte Address A High Byte High Byte Address A+1 Low Byte 9/8/2008 CSCE515 – Computer Network Programming 9/8/2008 CSCE515 – Computer Network Programming Byte Ordering Byte Order and Networking Little-Endian Big-Endian Suppose a Big Endian machine sends a Low Byte High Byte High Byte Low Byte 16 bit integer with the value 2: Addr A Addr A+1 Addr A Addr A+1 0000000000000010 IBM 80x86 IBM 370 A Little Endian machine will think it got DEC VAX Motorola 68000 the number 512: DEC PDP-11 Sun 0000001000000000 9/8/2008 CSCE515 – Computer Network Programming 9/8/2008 CSCE515 – Computer Network Programming Network Byte Order Network Byte Order All values stored in a sockaddr_in must Conversion of application-level data is be in network byte order. left up to the presentation layer. sin_port a TCP/IP port number. But hold on !!! How do lower level layers sin_addr an IP address. communicate if they all represent values differently ? (data length fields in headers) A fixed byte order is used (called network byte order) for all control data. 9/8/2008 CSCE515 – Computer Network Programming 9/8/2008 CSCE515 – Computer Network Programming Network Byte Order Functions TCP/IP Addresses We don’t need to deal with sockaddr ‘h’ : host byte order ‘n’ : network byte order structures since we will only deal with a real protocol family. ‘s’ : short (16bit) ‘l’ : long (32bit) We can use structures. uint16_t htons(uint16_t); sockaddr_in uint16_t ntohs(uint_16_t); BUT: The C functions that make up the sockets uint32_t htonl(uint32_t); API expect structures of type sockaddr. uint32_t ntohl(uint32_t); int bind(int sockfd, struct sockaddr *my_addr, int addrlen); int connect(int sockfd,
Load more

Recommended publications
  • Mac OS 8 Update
    K Service Source Mac OS 8 Update Known problems, Internet Access, and Installation Mac OS 8 Update Document Contents - 1 Document Contents • Introduction • About Mac OS 8 • About Internet Access What To Do First Additional Software Auto-Dial and Auto-Disconnect Settings TCP/IP Connection Options and Internet Access Length of Configuration Names Modem Scripts & Password Length Proxies and Other Internet Config Settings Web Browser Issues Troubleshooting • About Mac OS Runtime for Java Version 1.0.2 • About Mac OS Personal Web Sharing • Installing Mac OS 8 • Upgrading Workgroup Server 9650 & 7350 Software Mac OS 8 Update Introduction - 2 Introduction Mac OS 8 is the most significant update to the Macintosh operating system since 1984. The updated system gives users PowerPC-native multitasking, an efficient desktop with new pop-up windows and spring-loaded folders, and a fully integrated suite of Internet services. This document provides information about Mac OS 8 that supplements the information in the Mac OS installation manual. For a detailed description of Mac OS 8, useful tips for using the system, troubleshooting, late-breaking news, and links for online technical support, visit the Mac OS Info Center at http://ip.apple.com/infocenter. Or browse the Mac OS 8 topic in the Apple Technical Library at http:// tilsp1.info.apple.com. Mac OS 8 Update About Mac OS 8 - 3 About Mac OS 8 Read this section for information about known problems with the Mac OS 8 update and possible solutions. Known Problems and Compatibility Issues Apple Language Kits and Mac OS 8 Apple's Language Kits require an updater for full functionality with this version of the Mac OS.
    [Show full text]
  • Transport Interfaces Programming Guide
    Transport Interfaces Programming Guide Sun Microsystems, Inc. 2550 Garcia Avenue Mountain View, CA 94043-1100 U.S.A. Part No: 802-5886 August 1997 Copyright 1997 Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, California 94303-4900 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, SunSoft, SunDocs, SunExpress, and Solaris are trademarks, registered trademarks, or service marks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. The OPEN LOOK and SunTM Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written license agreements.
    [Show full text]
  • Chapter 1. Origins of Mac OS X
    1 Chapter 1. Origins of Mac OS X "Most ideas come from previous ideas." Alan Curtis Kay The Mac OS X operating system represents a rather successful coming together of paradigms, ideologies, and technologies that have often resisted each other in the past. A good example is the cordial relationship that exists between the command-line and graphical interfaces in Mac OS X. The system is a result of the trials and tribulations of Apple and NeXT, as well as their user and developer communities. Mac OS X exemplifies how a capable system can result from the direct or indirect efforts of corporations, academic and research communities, the Open Source and Free Software movements, and, of course, individuals. Apple has been around since 1976, and many accounts of its history have been told. If the story of Apple as a company is fascinating, so is the technical history of Apple's operating systems. In this chapter,[1] we will trace the history of Mac OS X, discussing several technologies whose confluence eventually led to the modern-day Apple operating system. [1] This book's accompanying web site (www.osxbook.com) provides a more detailed technical history of all of Apple's operating systems. 1 2 2 1 1.1. Apple's Quest for the[2] Operating System [2] Whereas the word "the" is used here to designate prominence and desirability, it is an interesting coincidence that "THE" was the name of a multiprogramming system described by Edsger W. Dijkstra in a 1968 paper. It was March 1988. The Macintosh had been around for four years.
    [Show full text]
  • Mac OS X: an Introduction for Support Providers
    Mac OS X: An Introduction for Support Providers Course Information Purpose of Course Mac OS X is the next-generation Macintosh operating system, utilizing a highly robust UNIX core with a brand new simplified user experience. It is the first successful attempt to provide a fully-functional graphical user experience in such an implementation without requiring the user to know or understand UNIX. This course is designed to provide a theoretical foundation for support providers seeking to provide user support for Mac OS X. It assumes the student has performed this role for Mac OS 9, and seeks to ground the student in Mac OS X using Mac OS 9 terms and concepts. Author: Robert Dorsett, manager, AppleCare Product Training & Readiness. Module Length: 2 hours Audience: Phone support, Apple Solutions Experts, Service Providers. Prerequisites: Experience supporting Mac OS 9 Course map: Operating Systems 101 Mac OS 9 and Cooperative Multitasking Mac OS X: Pre-emptive Multitasking and Protected Memory. Mac OS X: Symmetric Multiprocessing Components of Mac OS X The Layered Approach Darwin Core Services Graphics Services Application Environments Aqua Useful Mac OS X Jargon Bundles Frameworks Umbrella Frameworks Mac OS X Installation Initialization Options Installation Options Version 1.0 Copyright © 2001 by Apple Computer, Inc. All Rights Reserved. 1 Startup Keys Mac OS X Setup Assistant Mac OS 9 and Classic Standard Directory Names Quick Answers: Where do my __________ go? More Directory Names A Word on Paths Security UNIX and security Multiple user implementation Root Old Stuff in New Terms INITs in Mac OS X Fonts FKEYs Printing from Mac OS X Disk First Aid and Drive Setup Startup Items Mac OS 9 Control Panels and Functionality mapped to Mac OS X New Stuff to Check Out Review Questions Review Answers Further Reading Change history: 3/19/01: Removed comment about UFS volumes not being selectable by Startup Disk.
    [Show full text]
  • Outline Network Programming
    Outline Network Programming Definitions Berkeley API Dr. Thaier Hayajneh Computer Engineering Department Socket definition and types Introduction to Sockets 1 2 Network API Process Process Process Layer API - Application Programming Interface API is a set of functionality/services delivered by a programming system. TCP SCTP UDP Transppyort Layer Also API is a set of declaration, definitions, and procedflldbdures followed by programmers titlitto write client- server programs. ICMP, ARP Network API & IP Network Layer The services ( often provided by the operating system) RARP that provide the interface between application and protocol software . 802.3 Data-Link Layer 3 4 Network API Network API wish list Generic Programming Interface. Internet Support multiple communication protocol suites OSI model Application protocol suite details (families). Application User Address (endpoint) representation independence. processor Presentation Application Provide special services for Client and Server Session Transport TCP UDP Support for message oriented and connection Network IPv4, IPv6 oriented communication. kernel Data link Data link Work with existing I/O services Physical Physical Communications Operating System independence details Presentation layer services 5 6 TCP/IP Client-Server Model TCP/IP does not include an API definition. Client 1 Server Client 2 There are a variety of APIs for use with TCP/IP: Client 3 Sockets by Berkeley XTI (X/Open Transport Interface) by AT&T One side of communication is client, and the other side is server Winsock - Windows Sockets API by Microsoft Server waits for a client request to arrive MacTCP / Open Transport by Apple Server processes the client request and sends the response back to the client Iterative or concurrent 7 8 Functions needed: Berkeley Sockets Sppyecify local and remote communication A socket is an abstract representation of a communication endpoint.
    [Show full text]
  • A TCP-Layer Name Service for TCP Ports
    A TCP-layer name service for TCP ports S´ergio Freire Andr´eZ´uquete PT Inovac¸ao˜ / IEETA / Univ. of Aveiro IEETA / IT / Univ. of Aveiro Abstract using this name service are twofold: (i) users may dis- criminate servers using names instead of numbers and This paper presents a simple name service for TCP ports, (ii) TCP port scanners, such as nmap, should not be ca- allowing services to be reached by name instead of num- pable of discovering servers bound to unusual names. ber. Names are arbitrary byte arrays that are bound to listening ports. Name resolutions take place during the Using names for referring ports provides a more intu- TCP three-way handshake, not requiring extra message itive way to refer services, instead of numbers. Service exchanges. The new TCP handshake conforms with names that formerly were bound to static well-known the standard and is fully compatible with existing TCP port numbers may continue to exist but do not need any implementations. A prototype implementation was de- more to be bound to the same ports. For instance, we veloped in Linux, paying special attention to backward can bind the names http to port 8080 and http1 to compatibility with legacy systems (kernels and applica- port 80. Clients access either port specifying their name, tions). Among the many opportunities created by the http or http1, instead of numbers 8080 and 80. Port name service, it allows services with unusual names, names are also useful for uniform and uniquely tagging known only by small communities, to remain undetected ports used by the servers of overlay networks.
    [Show full text]
  • STREAMS Vs. Sockets Performance Comparison for UDP
    STREAMS vs. Sockets Performance Comparison for UDP Experimental Test Results for Linux Brian F. G. Bidulock∗ OpenSS7 Corporation June 16, 2007 Abstract cations facilities of the kernel: With the objective of contrasting performance between Transport Layer Interface (TLI). TLI is an acronym for the STREAMS and legacy approaches to system facilities, a com- Transport Layer Interface [TLI92]. The TLI was the non- parison is made between the tested performance of the Linux Na- standard interface provided by SVR4, later standardized by tive Sockets UDP implementation and STREAMS TPI UDP and X/Open as the XTI described below. This interface is now XTIoS UDP implementations using the Linux Fast-STREAMS deprecated. package [LfS]. X/Open Transport Interface (XTI). XTI is an acronym for the X/Open Transport Interface [XTI99]. The X/Open Trans- 1 Background port Interface is a standardization of the UNIX System V UNIX networking has a rich history. The TCP/IP protocol suite Release 4, Transport Layer Interface. The interface con- was first implemented by BBN using Sockets under a DARPA re- sists of an Application Programming Interface implemented search project on 4.1aBSD and then incorporated by the CSRG as a shared object library. The shared object library com- into 4.2BSD [MBKQ97]. Lachmann and Associates (Legent) sub- municates with a transport provider Stream using a service sequently implemented one of the first TCP/IP protocol suite primitive interface called the Transport Provider Interface. based on the Transport Provider Interface (TPI) [TLI92] and While XTI was implemented directly over STREAMS de- STREAMS [GC94]. Two other predominant TCP/IP implemen- vices supporting the Transport Provider Interface (TPI) tations on STREAMS surfaced at about the same time: Wollon- [TPI99] under SVR4, several non-traditional approaches ex- gong and Mentat.
    [Show full text]
  • Inside Mac OS X: System Overview Is Intended for Anyone Who Wants to Develop Software for Mac OS X
    Inside Mac OS X System Overview July 2002 Apple Computer, Inc. and TrueType are trademarks of THE WARRANTY AND REMEDIES SET © 2000–2002 Apple Computer, Inc. Apple Computer, Inc., registered in FORTH ABOVE ARE EXCLUSIVE AND All rights reserved. the United States and other countries. IN LIEU OF ALL OTHERS, ORAL OR WRITTEN, EXPRESS OR IMPLIED. No No part of this publication may be Carbon, Quartz, and Velocity Engine Apple dealer, agent, or employee is reproduced, stored in a retrieval are trademarks of Apple Computer, authorized to make any modification, system, or transmitted, in any form or Inc. extension, or addition to this warranty. by any means, mechanical, electronic, Enterprise Objects, Enterprise Objects photocopying, recording, or Framework, NeXT, Objective-C, and Some states do not allow the exclusion or otherwise, without prior written OpenStep are registered trademarks limitation of implied warranties or permission of Apple Computer, Inc., of NeXT Software, Inc., registered in liability for incidental or consequential with the following exceptions: Any the United States and other countries. damages, so the above limitation or person is hereby authorized to store Java and all Java-based trademarks exclusion may not apply to you. This documentation on a single computer are trademarks or registered warranty gives you specific legal rights, for personal use only and to print trademarks of Sun Microsystems, and you may also have other rights which copies of documentation for personal Inc., in the United States and other vary from state to state. use provided that the documentation countries. contains Apple’s copyright notice. Netscape Navigator is a trademark of The Apple logo is a trademark of Netscape Communications Apple Computer, Inc.
    [Show full text]
  • Network Programming and Protocol Design What Is a Socket?
    Network Programming and Protocol Design What Is A Socket? • Sockets (also known as Berkeley Sockets) is an application programming interface (API) to the operating system’s TCP/IP stack • Used on all Unixes • Windows Sockets are similar • Some Unixes have XTI (X/Open Transport Interface) and TLI (Transport Layer Interface) (not covered here) • Can be used for other protocol stacks than TCP/IP (not covered here) 2 Socket Functions • Socket functions: – Allocating resources: socket, bind – Opening connections: accept, connect – Closing connections: close, shutdown – Sending and receiving: read, write, recv, send, recvfrom, sendto, recvmsg, sendmsg – Other: getsockopt, setsockopt, getsockname, getpeername • Utilities – Network information (host names, addresses) – Byte order 3 Byte Order • Addresses and port number must be in network byte order – Also known as big-endian, most-significant byte first • Conversion routines for 16 and 32-bit integers: – htons, htonl ("host to network short/long") – ntohs, ntohl ("network to host short/long") • Null macros ("#define htons(x)(x)") on big-endian systems 4 Address Structures struct in_addr { in_addr_t s_addr; /* IPv4 address, network byte order */ }; struct sockaddr_in { sa_family_t sin_family; /* AF_INET */ in_port_t sin_port; /* 16-bit port, network byte order*/ struct in_addr sin_addr; /* IPv4 address */ char sin_zero[8]; /* always zero */ }; 5 Address Functions • From string to address: unsigned long inet_addr(const char *cp) – returns -1 on error • From address to string: char* inet_ntoa(struct
    [Show full text]
  • Kernel Programming
    Inside Mac OS X Kernel Programming November 2002 Apple Computer, Inc. NeXT and OpenStep are trademarks © 2001–2002 Apple Computer, Inc. of NeXT Software, Inc., registered in All rights reserved. the United States and other countries. No part of this publication may be Java and all Java-based trademarks reproduced, stored in a retrieval are trademarks or registered system, or transmitted, in any form or trademarks of Sun Microsystems, by any means, mechanical, electronic, Inc., registsered in the United States photocopying, recording, or and other countries. otherwise, without prior written OpenGL is a registered trademark of permission of Apple Computer, Inc., Silicon Graphics, Inc. with the following exceptions: Any Simultaneously published in the person is hereby authorized to store United States and Canada. documentation on a single computer Even though Apple has reviewed this for personal use only and to print manual, APPLE MAKES NO copies of documentation for personal WARRANTY OR REPRESENTATION, use provided that the documentation EITHER EXPRESS OR IMPLIED, WITH contains Apple’s copyright notice. RESPECT TO THIS MANUAL, ITS The Apple logo is a trademark of QUALITY, ACCURACY, Apple Computer, Inc. MERCHANTABILITY, OR FITNESS Use of the “keyboard” Apple logo FOR A PARTICULAR PURPOSE. AS A (Option-Shift-K) for commercial RESULT, THIS MANUAL IS SOLD “AS purposes without the prior written IS,” AND YOU, THE PURCHASER, ARE consent of Apple may constitute ASSUMING THE ENTIRE RISK AS TO trademark infringement and unfair ITS QUALITY AND ACCURACY. competition in violation of federal and state laws. IN NO EVENT WILL APPLE BE LIABLE FOR DIRECT, INDIRECT, SPECIAL, No licenses, express or implied, are INCIDENTAL, OR CONSEQUENTIAL granted with respect to any of the DAMAGES RESULTING FROM ANY technology described in this book.
    [Show full text]
  • Quickspecs HP Tru64 UNIX Operating System V5.1B
    RETIRED: Retired products sold prior to the November 1, 2015 separation of Hewlett-Packard Company into Hewlett Packard Enterprise Company and HP Inc. may have older product names and model numbers that differ from current models. QuickSpecs HP Tru64 UNIX Operating System V5.1B Overview Introduction The Tru64 UNIX® Operating System is a 64-bit advanced kernel architecture based on Carnegie-Mellon University's Mach V2.5 kernel design, with components from Berkeley Software Distribution (BSD) 4.3 and 4.4, UNIX System V, and other sources. Tru64 UNIX is an implementation of OSF/1 R1.0, R1.1, and R1.2 technology, and the Motif® graphical user interface and programming environment. Tru64 UNIX provides symmetric multiprocessing (SMP), real-time support, and numerous features to assist application programmers in developing applications that use shared libraries, multithread support, and memory-mapped files. The full features of the X Window System, Version 11, Release 6.5 (X11R6.5) from The Open Group are supported. Tru64 UNIX complies with other standards and industry specifications, including major standards sponsored by The Open Group, POSIX, FIPS, and the System V Interface Definition (SVID). By providing support for SVID, Tru64 UNIX supports System V applications. The Tru64 UNIX Operating System is compatible with Berkeley 4.3 programming interfaces. DA - 11939 Worldwide — Version 1 — April 8, 2004 Page 1 RETIRED: Retired products sold prior to the November 1, 2015 separation of Hewlett-Packard Company into Hewlett Packard Enterprise Company and HP Inc. may have older product names and model numbers that differ from current models. QuickSpecs HP Tru64 UNIX Operating System V5.1B System Management Tru64 UNIX System Management (SysMan) includes an easy to use suite of tools for installing, configuring, and managing a Tru64 UNIX system.
    [Show full text]
  • Open Transport/TCP Developer Note
    Open Transport/TCP Developer Note Revision 1.1b14 1/18/96 TCP Dev Note, Rev 1.1b14 1/18/96 page 1 Copyright © 1994-1996 Apple Computer, Inc. All rights reserved. Introduction ...............................................................................................................4 Installation ...........................................................................................................4 Getting started with the Open Transport/TCP API..................................... 4 Opening TCP, UDP, and RawIP Endpoints ...................................................4 Using RawIP......................................................................................................... 5 Internet Addresses ..............................................................................................5 Internet Address Information.......................................................................... 5 Domain Name Resolver (DNR)...................................................................... 5 IP Multicast........................................................................................................... 7 MacTCP Backward Compatibility.................................................................... 7 MDEV Backward Compatibility, SLIP and PPP ............................................7 Known Problems ................................................................................................7 Configuration ............................................................................................................8
    [Show full text]