From owner-freebsd-questions Tue Oct 19 23:33:17 1999 Delivered-To: freebsd-questions@freebsd.org Received: from monkeys.com (i180.value.net [206.14.136.180]) by hub.freebsd.org (Postfix) with ESMTP id EDCAB1AE38 for ; Tue, 19 Oct 1999 23:33:11 -0700 (PDT) (envelope-from rfg@monkeys.com) Received: from monkeys.com (LOCALHOST [127.0.0.1]) by monkeys.com (8.9.3/8.9.3) with ESMTP id XAA16910; Tue, 19 Oct 1999 23:33:41 -0700 To: Phil Homewood Cc: Tony Finch , freebsd-questions@FreeBSD.ORG Subject: Re: Stupid file system tricks. In-reply-to: Your message of Wed, 20 Oct 1999 09:52:45 +1000. <19991020095245.P8842@mincom.com> From: "Ronald F. Guilmette" Date: Tue, 19 Oct 1999 23:33:41 -0700 Message-ID: <16908.940401221@monkeys.com> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991020095245.P8842@mincom.com>, you wrote: >Tony Finch wrote: >> nullfs would be great for this situation if it worked. > >Or NFS, if nullfs is still broke. > >mount localhost:/some/mounted/dir /some/other/location > >Obviously a nullfs is (theoretically) more efficient, but NFS >has been working for me for years. Thanks. That _would_ work, if I was willing to trust NFS. But my (admittedly limited) understanding of it suggests that it is too much of a security risk to run NFS on anything that is connected to the public Internet. nullfs would be marvelous, if it was reliable. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message