From owner-freebsd-current Wed Aug 30 07:03:42 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id HAA01878 for current-outgoing; Wed, 30 Aug 1995 07:03:42 -0700 Received: from mail.barrnet.net (mail.barrnet.net [131.119.246.7]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id HAA01871 for ; Wed, 30 Aug 1995 07:03:39 -0700 Received: from outview (betty-p05.netinfo.com.au [203.8.127.197]) by mail.barrnet.net (8.6.10/MAIL-RELAY-LEN) with ESMTP id HAA26957 for ; Wed, 30 Aug 1995 07:03:25 -0700 Received: from localhost (localhost [127.0.0.1]) by outview (8.6.12/8.6.9) with SMTP id XAA07004 for ; Wed, 30 Aug 1995 23:59:51 +1000 Message-Id: <199508301359.XAA07004@outview> X-Authentication-Warning: betty-p05.netinfo.com.au: Host localhost didn't use HELO protocol To: freebsd-current@freebsd.org Reply-To: pdavie@auug.org.au Subject: SYSVMSG support and struct mymsg Date: Wed, 30 Aug 1995 23:59:50 +1000 From: Peter Davie Sender: current-owner@freebsd.org Precedence: bulk On most system V systems I have come across (if not all) the prototype structure for a message to be sent using SYSV msgsnd is called struct msgbuf. This of course has a name clash with the msgbuf structs which are defined in the kernel. However, when compiling the kernel, the SYSV struct and the BSD struct are only ever included in the one file once (hardly surprising.) I have trivial patches which can be supplied if there is sufficient interest to allow the current struct mymsg to be called msgbuf (you may ask why, well it makes porting easier since we don't have a silly difference to need to hack around.) Any interest? Peter Davie