From owner-freebsd-doc@freebsd.org Tue Oct 6 17:35:46 2015 Return-Path: Delivered-To: freebsd-doc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A870B9D08E7 for ; Tue, 6 Oct 2015 17:35:46 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 852A3CB8 for ; Tue, 6 Oct 2015 17:35:46 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id 5F3B65A9F13; Tue, 6 Oct 2015 17:35:39 +0000 (UTC) Date: Tue, 6 Oct 2015 17:35:39 +0000 From: Brooks Davis To: Frank Leonhardt Cc: freebsd-doc@freebsd.org Subject: Re: System calls documentation - where's it at? Message-ID: <20151006173539.GA47761@spindle.one-eyed-alien.net> References: <5613D94D.5060408@fjl.co.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dDRMvlgZJXvWKvBx" Content-Disposition: inline In-Reply-To: <5613D94D.5060408@fjl.co.uk> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Oct 2015 17:35:46 -0000 --dDRMvlgZJXvWKvBx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 06, 2015 at 03:23:09PM +0100, Frank Leonhardt wrote: > Sorry for the cross-post but this has remained unanswered in=20 > FreeBSD-Questions for a week now: >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > It's probably obvious, but not quite obvious enough for me right now... >=20 > Where's there a list of FreeBSD kernel (system) calls? >=20 > I can't believe I've never needed one before - I guess I've just used=20 > UNIX calls (remembered from the 1980s) or got lucky with the manual. >=20 > There's obviously man 2, but you really need to know the name of what=20 > you're looking for (or guess from the file names). I could also scan=20 > through the 'C' header files. >=20 > The Developer's Manual mentions HOW to call a system call (and told me=20 > something shocking about Linux I hadn't realised). But nowhere can I=20 > find a list - preferably sorted in to sections with a summary, function= =20 > number, symbolic name, and list of parameters. I'm looking for something= =20 > a bit more informative than sys/syscall.h! >=20 > I bet someone's going to refer me to a man page with a name everyone=20 > else knows but I couldn't guess. Counting down.... No detailed list exists to my knowledge. The source of truth is sys/kern/syscalls.master. Most things have manpages, but not everything (IMO it is a bug in all cases where there is no result from "man 2 "). It wouldn't be crazy to use a system like we do for src.conf.5 to generate a summary page. Sorting them into groups might be hard and would require some extra metadata. -- Brooks --dDRMvlgZJXvWKvBx Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJWFAZqAAoJEKzQXbSebgfACsgH/2EKov+CvbLVqij3hksQ10QI NwoLuh7DZiE9pRXsLuQDkg4+TQN2gX63o5JHWPrktPo1yPfDnOdsxE6hjpaK2WPu 0AIAlU6xjoto9otI4a09MuSc2HY3TTTZMnqtFlFAO3Njqhi8LPiLWwThPEHyhbyW GJdhqnx+rtq58X1Sb9VPOnorJt0ZbYXXdeOcs1BfrFbOCwx62xo71vdkjsg33f14 RddGvYGNp25bG952mxLCBGZozAiTg19LUEJSPwhBu6sPDuu3Y6BEot1HoVbJ1BT6 B5WuNJ59ZvUjzCEhRY/i+bseUNHQdkMpkvoXx7GpFp8+MkOMKWtwKm6LrOCkJtI= =N+qE -----END PGP SIGNATURE----- --dDRMvlgZJXvWKvBx--