From owner-freebsd-fs Sun May 7 1:13:58 2000 Delivered-To: freebsd-fs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 8E49237BA7C; Sun, 7 May 2000 01:13:56 -0700 (PDT) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id BAA64983; Sun, 7 May 2000 01:13:56 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sun, 7 May 2000 01:13:56 -0700 (PDT) From: Kris Kennaway To: Erez Zadok Cc: freebsd-fs@freebsd.org Subject: Re: announcing stackable file system templates and code generator In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 7 May 2000, Kris Kennaway wrote: > Oops, I should have waited a few moments before replying. It was actually > pretty easy to fix - #include just needs to be added to the > headers. Okay, next problem. I'm trying to play with the sample filesystems by using them on a vn, but it doesnt seem to be working. For example, the rot13fs KLD loads fine and I can mount it on my vn partition, but it gives the wrong disk size, and the mountpoint turns into a character-special device: df -k returns: /dev/vn1c 99183 80330 10919 88% /mnt crw-r----- 1 root operator 43, 10 May 7 01:00 /mnt The backing store in this case was a 30M file. Any ideas? Could this have something to do with the removal of block devices? Kris P.S. aclfs seems to have an #if 0'd section which prevents the KLD from loading: aclfs_decode_block is defined out in subr.c, but referenced from elsewhere in the code. ---- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message