From owner-freebsd-hackers Mon Jul 22 22:29:30 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8003E37B400 for ; Mon, 22 Jul 2002 22:29:28 -0700 (PDT) Received: from HAL9000.homeunix.com (12-233-156-170.client.attbi.com [12.233.156.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id C514B43E31 for ; Mon, 22 Jul 2002 22:29:27 -0700 (PDT) (envelope-from dschultz@uclink.Berkeley.EDU) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.3/8.12.3) with ESMTP id g6N5U18g001184; Mon, 22 Jul 2002 22:30:06 -0700 (PDT) (envelope-from dschultz@uclink.Berkeley.EDU) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.3/8.12.3/Submit) id g6N5U0Tc001177; Mon, 22 Jul 2002 22:30:00 -0700 (PDT) (envelope-from dschultz@uclink.Berkeley.EDU) Date: Mon, 22 Jul 2002 22:30:00 -0700 From: David Schultz To: Sean Hamilton Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Linux binary compatibility requires SYSVSEM Message-ID: <20020723053000.GA1025@HAL9000.homeunix.com> Mail-Followup-To: Sean Hamilton , freebsd-hackers@FreeBSD.ORG References: <000501c23205$7aa03460$f019e8d8@slugabed.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000501c23205$7aa03460$f019e8d8@slugabed.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Sean Hamilton : > "kldload linux" dies unless > > options SYSVSEM > > is in the kernel. Is there some way around this? (I have no other use for > it, and try to be minimalist...) The sysvsem support has a very small footprint, so I wouldn't worry about it unless you have good reason to. > Also, are there other approaches to Linux binary compatibility? Is there > some type of wrapper, which will load and execute the code, without all the > compatibility/library mishmash? I'm trying to run a quake3 server, which I > don't believe does anything not in the standard C library. Technically, you don't need any compatability libraries to run a statically-linked Linux binary. The core of the Linux compatability support is a small kernel interface that turns Linux system calls into FreeBSD system calls. But most applications are dynamically linked against glibc or some other god-aweful thing, so you would need the libraries even in Linux. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message