From owner-freebsd-hackers Sun Oct 6 08:07:55 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA23468 for hackers-outgoing; Sun, 6 Oct 1996 08:07:55 -0700 (PDT) Received: from veda.is (root@veda.is [193.4.230.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA23442 for ; Sun, 6 Oct 1996 08:07:46 -0700 (PDT) Received: (from adam@localhost) by veda.is (8.7.6/8.7.3) id PAA04362; Sun, 6 Oct 1996 15:07:26 GMT Date: Sun, 6 Oct 1996 15:07:26 GMT From: Adam David Message-Id: <199610061507.PAA04362@veda.is> To: jonny@mailhost.coppe.ufrj.BR (Joao Carlos Mendes Luis) Cc: freebsd-hackers@freebsd.org Subject: Re: nullfs: Panicing... Newsgroups: list.freebsd.hackers References: <199610060359.AAA00618@mailhost.coppe.ufrj.br> X-Newsreader: NN version 6.5.0 #2 (NOV) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I want to make parts of a file system available to anon ftp, whose >chrooted directory is located at another file system. My first >approach was to use nullfs, but everytime I try to edit (vi) >a file in the nullfs mounted directory, the system panics. Everything >else works (or seens to work) ok. > I already had problems with vi and nullfs in NetBSD, caused by the >mmap nature of vi. Maybe this is the case, too. > This problem happens at 2.1.0 and 2.1.5 releases. Does not matter >if the nullfs is mounted read-only or if vi is called in the its read- >only from (view). Probably mmap then, since read-only access typically worked already otherwise. >PS: I'm now using NFS to localhost, as a workaround. I had to abandon this approach and use symlinks instead, once the directory had outgrown a certain size. Perhaps there is no longer any such size limit, but I don't have the stomach at the moment to risk it. -- Adam David