[976] in arla-drinkers
Re: Problem starting arla on OpenBSD 2.5
daemon@ATHENA.MIT.EDU (Assar Westerlund)
Thu Jul 15 05:21:17 1999
From owner-arla-drinkers@stacken.kth.se Thu Jul 15 09:21:17 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 10320 invoked from network); 15 Jul 1999 09:21:16 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 15 Jul 1999 09:21:16 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id LAA02809
for arla-drinkers-list; Thu, 15 Jul 1999 11:15:28 +0200 (MET DST)
Received: from assaris.sics.se (dhcp31162.ietf.uninett.no [128.39.31.162])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id LAA02805
for <arla-drinkers@stacken.kth.se>; Thu, 15 Jul 1999 11:15:24 +0200 (MET DST)
Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.7.3) id LAA01753; Thu, 15 Jul 1999 11:15:41 +0200 (CEST)
From: Assar Westerlund <assar@stacken.kth.se>
To: Bjorn Lindgren <nr@birdie.sekure.net>
Cc: arla-drinkers@stacken.kth.se
Subject: Re: Problem starting arla on OpenBSD 2.5
References: <Pine.BSO.4.10.9907151056300.6956-100000@birdie.sekure.net>
Mime-Version: 1.0 (generated by tm-edit 7.68)
Content-Type: text/plain; charset=US-ASCII
Date: 15 Jul 1999 11:15:40 +0200
In-Reply-To: Bjorn Lindgren's message of "Thu, 15 Jul 1999 11:05:51 +0200 (CEST)"
Message-ID: <5lwvw246kj.fsf@assaris.sics.se>
Lines: 18
X-Mailer: Gnus v5.5/Emacs 19.34
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
Bjorn Lindgren <nr@birdie.sekure.net> writes:
> Hi, have have some serious problems then trying to start Arla on my
> OpenBSD 2.5 system using the standard kernel. Then I run 'startarla' I get
> these error messages, I get the same errors then trying to manualy load
> the xfs_mod.o module with 'modload'. It seams to build ok, only minor
> compile warnings.
> xfs_message.c:190: Undefined symbol `_VOP_UNLOCK' referenced from text
> segment
That's strange, doesn't your kernel have a function VOP_UNLOCK?
: datan$ ; nm /bsd | grep VOP_UNLOCK
f0161650 T _VOP_UNLOCK
: datan$ ; uname -a
OpenBSD datan 2.5 DATAN#0 i386
/assar
