From owner-freebsd-hackers Sun Oct 11 12:18:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27165 for freebsd-hackers-outgoing; Sun, 11 Oct 1998 12:18:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (castles306.castles.com [208.214.167.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27158 for ; Sun, 11 Oct 1998 12:18:21 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00824; Sun, 11 Oct 1998 12:23:06 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810111923.MAA00824@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Etienne de Bruin cc: freebsd-hackers@FreeBSD.ORG (Hackers FreeBSD) Subject: Re: ioctl naming conventions In-reply-to: Your message of "Sun, 11 Oct 1998 10:50:33 +0200." <199810110850.KAA10939@borg.kryptokom.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 11 Oct 1998 12:23:04 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > what are the ioctl signals supposed to be called? > > #define SIOxxxxxxx _IO('i',200,type) > > i presume SIO stands for socket io? i know that what i end up > defining the signals as doesn't really matter, but i'd like to > follow protocol. SIOC - socket I/O control. S/G - set/get xxxx - whatever you're manipulating. eg. SIOCGHWADDR gets the hardware address. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message