Xref: utzoo comp.unix.wizards:11835 comp.bugs.sys5:632
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!gatech!ncar!boulder!sunybcs!bingvaxu!leah!uwmcsd1!marque!uunet!mcvax!hp4nl!eutrc3!eutwc1!wzv!wietse
From: wietse@wzv.UUCP (Wietse Z. Venema)
Newsgroups: comp.unix.wizards,comp.bugs.sys5
Subject: Re: System V messages problem
Message-ID: <145@wzv.UUCP>
Date: 19 Oct 88 22:23:12 GMT
References: <1794@runx.ips.oz>
Reply-To: wietse@wzv.UUCP (Wietse Z. Venema)
Organization: Tech. Univ. Eindhoven, The Netherlands
Lines: 21

In article <1794@runx.ips.oz> rosko@runx.ips.oz (Ross McKay) writes:
>	I have been trying to get message passing to work on my Microport
>System (System V.2, uPort version 2.3, a '286 box (yes, I know it's hideous,
>but it's also cheap)).  I tried using an example programme from Bach's book,
>[problem description deleted]
>	I am running the kernel with message passing enabled, so I am wondering
>just what Microport did to message passing ...
>[example program deleted]

Before accusing Microport of anything, it would be a good idea 
to lint your program first, then flame about the example program.

    function argument ( number ) used inconsistently
	msgget( arg 1 )   	llib-lc(84) :: example.c(55)
	msgsnd( arg 2 )   	llib-lc(86) :: example.c(68)
	msgsnd( arg 3 )   	llib-lc(86) :: example.c(68)
	msgctl( arg 3 )   	llib-lc(82) :: example.c(74)
-- 
work:	wswietse@eutrc3.uucp	| Eindhoven University of Technology
ditto:	wswietse@heitue5.bitnet	| Mathematics and Computing Science
home:	wietse@wzv.uucp		| 5600 MB Eindhoven, The Netherlands