From owner-freebsd-hackers  Sun Feb  7 13:24:09 1999
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA16671
          for freebsd-hackers-outgoing; Sun, 7 Feb 1999 13:24:09 -0800 (PST)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.30.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16403
          for <hackers@freebsd.org>; Sun, 7 Feb 1999 13:22:14 -0800 (PST)
          (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE)
Received: (from kuku@localhost)
	by gilberto.physik.RWTH-Aachen.DE (8.8.8/8.8.7) id WAA15102
	for hackers@freebsd.org; Sun, 7 Feb 1999 22:22:24 +0100 (MET)
	(envelope-from kuku)
Date: Sun, 7 Feb 1999 22:22:24 +0100 (MET)
From: Christoph Kukulies <kuku@gilberto.physik.RWTH-Aachen.DE>
Message-Id: <199902072122.WAA15102@gilberto.physik.RWTH-Aachen.DE>
To: hackers@FreeBSD.ORG
Subject: portability of shm, mmap, pipes and socket IPC
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Does anyone have experience with portability of common
IPC mechanisms between Linux 2.x and FreeBSD?

I'm trying to estimate the risk of a porting project from
Linux to FreeBSD. 
What peculiarities are there? Incompatibilities between the
two OSs WRT to 'clean' implementation of these disciplines?

sockets - feature set compatible?
pipes - ? named pipes?
mmap - stable? limitations?
shmxxx - SYSV compatibility? 

Comments greatly appreciated.

-- 
Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message