From owner-freebsd-arch@FreeBSD.ORG Tue Feb 12 17:55:54 2008 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2726F16A417; Tue, 12 Feb 2008 17:55:54 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 126F013C442; Tue, 12 Feb 2008 17:55:54 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id E97F31A4D89; Tue, 12 Feb 2008 09:55:53 -0800 (PST) Date: Tue, 12 Feb 2008 09:55:53 -0800 From: Alfred Perlstein To: "Christian S.J. Peron" Message-ID: <20080212175553.GU99258@elvis.mu.org> References: <20080212014057.GA6027@sub.vaned.net> <20080212051020.GO99258@elvis.mu.org> <20080212173852.GA27407@sub.vaned.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080212173852.GA27407@sub.vaned.net> User-Agent: Mutt/1.4.2.3i Cc: arch@freebsd.org, re@freebsd.org, current@freebsd.org Subject: Re: sysv IPC and shminfo ABI [solved] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Feb 2008 17:55:54 -0000 * Christian S.J. Peron [080212 09:39] wrote: > > After having some discussions with jhb, and reviewing the commit logs > that introduced IPC_INFO, this is a non-issue. The whole reason this > was introduced was to satisfy Linux compatability. > > revision 1.67 > date: 2001/10/28 09:29:07; author: mr; state: Exp; lines: +45 -2 > Introduce [IPC|SHM]_[INFO|STAT] to shmctl to make > `/compat/linux/usr/bin/ipcs -m` happy. > > This was never an intented part of the FreeBSD ABI, which explains > why the structure is not made available to the user. Although the size > has changed, it doesn't matter, because the Linux ABI layer will prepare > it's own shminfo structure as send it back out to the user. > > So, I am going to make shmctl(IPC_INFO ...) for the FreeBSD ABI return > EINVAL, and I am going to add some serious comments around various points > in the kernel explaining why things are there, and how they should never > be exported. > > Thanks everyone for the input. Hmm, sorry for the misdirection. Wouldn't it make sense to support the Linux API though for Linux management applications? I guess sometime later if there is demand. -- - Alfred Perlstein