From owner-freebsd-current Tue Sep 11 2:43: 2 2001 Delivered-To: freebsd-current@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id A79BC37B412 for ; Tue, 11 Sep 2001 02:42:58 -0700 (PDT) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id LAA14511; Tue, 11 Sep 2001 11:42:55 +0200 (MET DST) Date: Tue, 11 Sep 2001 11:42:55 +0200 (CEST) From: Harti Brandt To: Peter Wemm Cc: Subject: Re: vfsload appearse broken after new changes In-Reply-To: <20010911125211.A43970@nagual.pp.ru> Message-ID: <20010911113824.B78712-100000@beagle.fokus.gmd.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Sep 11, 2001 at 00:25:34 -0700, Peter Wemm wrote: > > Also, check that the kern.module_path sysctl has got a trailing / on > each component. You can do a 'ktrace kldload msdosfs' and you should be > able to see the path searching for linker.hints and the .ko files > as NAMI calls. > This is rather annoying. For ages the the module path has been without trailing / and the default loader.conf (/sys/boot/forth/loader.conf) still contains the default without slashes. And there may be people with local loader.conf that have also no trailing slash. Not beeing able to load msdosfs is one thing, but not beeing able to load your interface driver and the nfs module to get access to the NFS mounted source to figure out what is happening is really bad. A little HEADS UP in such cases would save a lot of work for people (fortunately I have red my e-mail before rebooting my current system). harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.fhg.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message