*BSD News Article 56148


Return to BSD News archive

#! rnews 2275 bsd
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!nntp.coast.net!swidir.switch.ch!in2p3.fr!oleane!tank.news.pipex.net!pipex!news.mathworks.com!newsfeed.internetmci.com!EU.net!Germany.EU.net!news.dfn.de!news.ruhr-uni-bochum.de!news.rwth-aachen.de!comnets.rwth-aachen.de!news
From: Martin Ostermann <ost@comnets.rwth-aachen.de>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Running linux code on FreeBSD
Date: Wed, 29 Nov 1995 22:24:41 +0100
Organization: Communication Networks, Aachen U of Technology
Lines: 43
Message-ID: <30BCCF99.2781E494@comnets.rwth-aachen.de>
References: <48cefu$108o@macro.stanford.edu> <imybtcomkw.fsf@waldrog.cs.uidaho.edu> <DIFy5D.2E7@pegasus.com> <imybt7lhb9.fsf@waldrog.cs.uidaho.edu> <DIr6HK.8HC@pegasus.com>
NNTP-Posting-Host: lula.comnets.rwth-aachen.de
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 2.0b3 (X11; I; FreeBSD 2.1.0-RELEASE i386)
CC: Richard Foulk <richard@pegasus.com>

Richard Foulk wrote:
> 
> >$ >3 run `/usr/sbin/linux' before you start up any linux programs.
> >$ >
> >$
> >$ Where can /usr/sbin/linux be acquired?  It doesn't appear to come

> >i can see /usr/bin/linux on my machine (freebsd-current).  it's a simple
> >shell script:
> >
> >#!/bin/sh
> ># $Id$: linux,v 1.2 1995/10/28 12:35:06 peter Exp $
> >modload -e linux_mod -u -q -o /tmp/linux_mod /lkm/linux_mod.o
> >
> >
> >sorry about that.
> >
> 
> Unfortunately, when I run it I get the following response:
> 
>         Undefined entry symbol `_linux_mod'
>         ld: Spurious undefined symbols: # undefined symbols 1, reported 0
>         modload: /usr/bin/ld: return code 1
> 

I had  the same problems, and tried linux_init instead (like in the
screensaver Module), and that was it:

/sbin/modload -e linux_init -u -q -o /tmp/linux_mod /lkm/linux_mod.o

Seems like they fixed the name to obey some standards from -2.1 to
-current.

Also it should be noted, that the COMPAT_LINUX must be added to the
kernel config options, *not* LINUX_COMPAT, as it is erroneously stated
in the linux_lib port.

Hope that helps, Martin

-- 
Martin Ostermann	mailto:ost@comnets.rwth-aachen.de
Bogenstr. 9             http://www.comnets.rwth-aachen.de/~ost
52080 Aachen		Germany