From owner-freebsd-hackers Wed Oct 20 14:37:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from marcy.nas.nasa.gov (marcy.nas.nasa.gov [129.99.113.17]) by hub.freebsd.org (Postfix) with ESMTP id D96EB14CF9 for ; Wed, 20 Oct 1999 14:37:28 -0700 (PDT) (envelope-from wrstuden@marcy.nas.nasa.gov) Received: from localhost (wrstuden@localhost) by marcy.nas.nasa.gov (8.9.3/NAS8.8.7n) with SMTP id OAA09432; Wed, 20 Oct 1999 14:37:11 -0700 (PDT) Date: Wed, 20 Oct 1999 14:37:11 -0700 (PDT) From: Bill Studenmund To: Zhihui Zhang Cc: 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 Sat, 16 Oct 1999, Zhihui Zhang wrote: > 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. In NetBSD, we changed these two references to be to umap_bypass since it is, after all, umapfs. :-) Take care, Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message