Date: Tue, 12 Feb 2008 09:55:53 -0800 From: Alfred Perlstein <alfred@freebsd.org> To: "Christian S.J. Peron" <csjp@FreeBSD.org> Cc: arch@freebsd.org, re@freebsd.org, current@freebsd.org Subject: Re: sysv IPC and shminfo ABI [solved] Message-ID: <20080212175553.GU99258@elvis.mu.org> In-Reply-To: <20080212173852.GA27407@sub.vaned.net> References: <20080212014057.GA6027@sub.vaned.net> <20080212051020.GO99258@elvis.mu.org> <20080212173852.GA27407@sub.vaned.net>
next in thread | previous in thread | raw e-mail | index | archive | help
* Christian S.J. Peron <csjp@FreeBSD.org> [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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080212175553.GU99258>