From owner-freebsd-current  Tue Sep 26 19: 4:47 2000
Delivered-To: freebsd-current@freebsd.org
Received: from merc95.us.sas.com (merc95.us.sas.com [149.173.6.5])
	by hub.freebsd.org (Postfix) with ESMTP id 55D4137B42C
	for <freebsd-current@freebsd.org>; Tue, 26 Sep 2000 19:04:41 -0700 (PDT)
Received: from merc95.us.sas.com ([127.0.0.1]) by merc95.us.sas.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2651.58)
	id TA8F4K0G; Tue, 26 Sep 2000 22:04:35 -0400
Received: from 10.28.149.26 by merc95.us.sas.com (InterScan E-Mail VirusWall NT); Tue, 26 Sep 2000 22:04:34 -0400 (Eastern Daylight Time)
Received: from bb01f39.unx.sas.com (bb01f39.unx.sas.com [10.16.2.246])
	by mozart.unx.sas.com (8.9.3 (PHNE_18979)/8.9.3) with ESMTP id WAA20369
	for <freebsd-current@freebsd.org>; Tue, 26 Sep 2000 22:04:34 -0400 (EDT)
Received: (from jwd@localhost)
	by bb01f39.unx.sas.com (8.9.3/8.9.1) id WAA80399
	for freebsd-current@freebsd.org; Tue, 26 Sep 2000 22:04:34 -0400 (EDT)
	(envelope-from jwd)
Date: Tue, 26 Sep 2000 22:04:34 -0400
From: John DeBoskey <jwd@unx.sas.com>
To: freebsd-current@freebsd.org
Subject: /modules vs. /boot/kernel
Message-ID: <20000926220434.A80300@unx.sas.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,

   Just a heads up on a minor problem I ran into...

   I've had a system running 5.0-current from about 3 months
ago... that system kept modules in /modules.

   After upgrading to -current as of today, vinum would nolonger
load, complaining about: link_elf: symbol tsleep undefined

   Well, kldload -v vinum also complained... and sysctl reports:

kern.module_path: /boot/modules/;/modules/;/boot/kernel/

   To make a long story short, there was an old vinum module
in /modules from the previous system/kernel. After rm'ing the
/modules area everything works again.

   Question, is /modules still valid? I haven't seen any real
discussion of it amoungst the kernel discussions...

-John


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message