Date: Tue, 9 May 2000 01:25:09 -0700 (PDT) From: Kris Kennaway <kris@FreeBSD.org> To: Erez Zadok <ezk@cs.columbia.edu> Cc: freebsd-fs@FreeBSD.org Subject: Re: announcing stackable file system templates and code generator Message-ID: <Pine.BSF.4.21.0005090056160.84040-100000@freefall.freebsd.org> In-Reply-To: <200005090740.DAA04200@shekel.mcl.cs.columbia.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 9 May 2000, Erez Zadok wrote:
> It would be excellent news to know that my 4.0 templates work with minor
> changes on 5.0.
>
> Do me a favor and try my standard test case on rot13fs or cryptfs: unpack
> and build the latest am-utils (or emacs, or your favorite large compile job)
> inside the stacked f/s. If it passes a few runs, it's most likely ok.
Unfortunately there do seem to be problems, unless I made another mistake.
I didn't want to potentially trash my FS (I don't yet have a spare
"disposable" disk), so I used a vn, as follows:
vnconfig -S 100m -s labels -e /dev/vn0c
[ Configures a 100m swap-backed vn device ]
disklabel -rw vn0 auto
newfs /dev/vn0c
mount /dev/vn0c /mnt
kldload ./rot13fs.ko
./mount_rot13fs -t rot13fs /mnt /mnt2
cd /mnt2
tar xvfz ${DISTDIR}/xemacs-21.1.9.tar.gz
At this point, /mnt correctly contains a duplicate copy of the xemacs
distribution, rot13-encoded (well, as far as I checked). However, if I do
a `pwd`, I am apparently now in /mnt, no longer /mnt2, and the following
kind of thing happens:
mollari# cd /mnt2/xemacs-21.1.9/
mollari# pwd
/mnt/xemacs-21.1.9
When I try and run ./configure, it dies with the following:
mollari# ./configure
checking host system type... i386-unknown-freebsd5.0
checking whether ln -s works... yes
checking the configuration name
./configure: /mnt/xemacs-21.1.9/config.sub: not found
even though config.sub does exist in both filesystems.
I also had problems unmounting the filesystem on /mnt2 - I'd get a "file
system busy" even when there were no open files referring to it, and even
when I try and umount -f.
The above instructions should also work unchanged on 4.0-R, so you should
be easily able to test whether it's something to do with vn devices, or if
it's 5.0 which is breaking.
Hope this helps,
Kris
----
In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe <forsythe@alum.mit.edu>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0005090056160.84040-100000>