From owner-freebsd-hackers Sat Oct 16 11:40:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id E6BD915227 for ; Sat, 16 Oct 1999 11:40:55 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id OAA08334 for ; Sat, 16 Oct 1999 14:40:55 -0400 (EDT) Date: Sat, 16 Oct 1999 13:38:14 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@FreeBSD.ORG Subject: Re: Status of UMAPFS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 15 Oct 1999, Zhihui Zhang wrote: > > Is the UMAPFS working? I add "options UMAPFS" to the configuration file > of FreeBSD 3.3-Release and rebuilt the kernel. I got the following > errors: > > loading kernel > umap_vnops.o: In function `umap_lock': > umap_vnops.o(.text+0x568): undefined reference to `null_bypass' > umap_vnops.o: In function `umap_unlock': > umap_vnops.o(.text+0x58e): undefined reference to `null_bypass' > *** Error code 1 > > Stop. > I find out that you must also include NULLFS in the kernel to compile. I have tested NULLFS and UMAPFS with some trivial commands. Both works. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message