From owner-freebsd-hackers Wed Mar 28 22:21:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from chopper.Poohsticks.ORG (chopper.poohsticks.org [63.227.60.73]) by hub.freebsd.org (Postfix) with ESMTP id AE87837B71B for ; Wed, 28 Mar 2001 22:21:46 -0800 (PST) (envelope-from drew@chopper.Poohsticks.ORG) Received: from chopper.Poohsticks.ORG (drew@localhost.poohsticks.org [127.0.0.1]) by chopper.Poohsticks.ORG (8.10.1/8.10.1) with ESMTP id f2T6LjO21874; Wed, 28 Mar 2001 23:21:45 -0700 Message-Id: <200103290621.f2T6LjO21874@chopper.Poohsticks.ORG> To: "Arthur Munn" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: header files for sockets In-reply-to: Your message of "Wed, 28 Mar 2001 22:25:30 EST." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <21870.985846904.1@chopper.Poohsticks.ORG> Date: Wed, 28 Mar 2001 23:21:44 -0700 From: Drew Eckhardt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , netbsdadvocate@hotmail.co m writes: >the header files they tell you to include are no longer correct. The header files are pretty much standard. >So >what I would like to know is the header files I will need to include to work >with sockets. If that is not specific enough, here is a brief summary of the >system calls i will need to use: Most if not all of the relevant system calls are prototyped in . For reasons that made since when cave men wrote code on stone tablets, usually don't include , so putting that first would be a good idea. Of course, for all properly documented library functions the man pages give the header files, and you could always type man command For example drew@revolt% man socketpair NAME socketpair - create a pair of connected sockets LIBRARY Standard C Library (libc, -lc) SYNOPSIS #include #include ... etc. -- Home Page For those who do, no explanation is necessary. For those who don't, no explanation is possible. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message