From owner-freebsd-questions Mon Jun 19 4: 6:32 2000 Delivered-To: freebsd-questions@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id 2F8B737BCA2 for ; Mon, 19 Jun 2000 04:06:27 -0700 (PDT) (envelope-from nbm@sunesi.net) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 133zNR-000Gxc-00; Mon, 19 Jun 2000 13:06:01 +0200 Date: Mon, 19 Jun 2000 13:06:01 +0200 From: Neil Blakey-Milner To: "Roberto Nunnari, AGIE" Cc: questions Subject: Re: mount_null vfsload(null) Message-ID: <20000619130601.A65085@mithrandr.moria.org> References: <39491709.4E2630F3@agie.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <39491709.4E2630F3@agie.ch>; from roberto.Nunnari@agie.ch on Thu, Jun 15, 2000 at 06:48:57PM +0100 Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu 2000-06-15 (18:48), Roberto Nunnari, AGIE wrote: > can anybody tell me what can cause this message show up? > > mount_null: vfsload(null): no such file or directory 'man vfsload' for information on vfsload. Basically, you need to have the null filesystem module loaded, since it doesn't seem to pick up /modules/null.ko automatically on your system. > that call is made on a diskless pc like this: > # mount_null /aDirectory /mount_point > > and both /aDirectory and /mount_point are existing > directories as 'ls -l' correctly shows. Note that the null filesystem isn't production-ready, and probably will crash your machine, kill your pet hamster, drive over your favourite petunias, and maybe even do something you won't like. It does warn you in the man page. Neil -- Neil Blakey-Milner Sunesi Clinical Systems nbm@mithrandr.moria.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message