From owner-freebsd-questions Wed Nov 12 15:38:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA20632 for questions-outgoing; Wed, 12 Nov 1997 15:38:17 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA20611 for ; Wed, 12 Nov 1997 15:38:13 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.7) with SMTP id PAA00726; Wed, 12 Nov 1997 15:38:07 -0800 (PST) (envelope-from dwhite@gdi.uoregon.edu) Date: Wed, 12 Nov 1997 15:38:07 -0800 (PST) From: Doug White Reply-To: Doug White To: Robert Eckardt cc: uzsv2k@uni-bonn.de, questions@FreeBSD.ORG Subject: Re: ELF binary type not known In-Reply-To: <199711122229.XAA01244@ghost.mep.ruhr-uni-bochum.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 12 Nov 1997, Robert Eckardt wrote: > > > I tried to install the linux_lib 2.4, and it tries to run the Linux > > > ldconfig (ldconfig, I think) at the end of the make install process. > > > When it tries to do this, it says "ELF: binary type not known, signal 6: > > > ignored". The make install completes OK, though. > > > > Make sure you're loading the Linux LKM through /etc/rc.conf. You may need > > to run `brandelf -t Linux ldconfig' to have FreeBSD grok the emulation > > properly. The options COMPAT_LINUX / LINUX_COMPAT are no longer needed, > > thankfully. > > Has anybody cooked a hack to avoid branding for a default type > of ELF binaries ? > Like some sysctl to set the default e.g. to Linux to say > "if it's ELF and you didn't find a type, assume Linux". > (Just to be able to install directly from CD.) The problem with this is: 1. The Linux emulator isn't loaded by default. 2. We're leaving the path clear for FreeBSD-native ELF binaries and changing it would be a bad precedent. The solution is probably closer to pointing big fingers at the ``linux_enable'' hook in /etc/rc.conf. Handbook section maybe? Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major