Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!fu-berlin.de!zrz.TU-Berlin.DE!zib-berlin.de!irz401!uriah.heep!bonnie.heep!not-for-mail
From: j@bonnie.heep.sax.de (J Wunsch)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Bug in shmget()???
Date: 23 Aug 1995 16:09:15 +0200
Organization: Private U**x site, Dresden.
Lines: 19
Message-ID: <41fcqb$69a@bonnie.tcd-dresden.de>
References: <419adk$k60@botan.shimane-u.ac.jp> <41dm2s$u8@jraynard.demon.co.uk>
Reply-To: joerg_wunsch@uriah.heep.sax.de
NNTP-Posting-Host: 192.109.108.139
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
James Raynard <james@jraynard.demon.co.uk> wrote:
>>2. Why no man pages on shmget(), shmat(), msgget(), ... ?
>
>An oversight? I believe that -current now has them.
Not yet. Someone started to write them however...
James: those facilites are mainly included for compatibility in
porting applications from SysV. Most BSD developers believe that they
are rather a gross hack not worth putting too much effort into.
SysV shared memory can easily be replaced by something based on
mmap(2). The most trickiest part to replace would be the semaphores.
--
cheers, J"org private: joerg_wunsch@uriah.heep.sax.de
http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)