From owner-freebsd-fs Thu Feb 22 13:35:32 2001 Delivered-To: freebsd-fs@freebsd.org Received: from knight.phoenix.volant.org (knight.phoenix.volant.org [205.179.79.194]) by hub.freebsd.org (Postfix) with ESMTP id 2C94B37B401 for ; Thu, 22 Feb 2001 13:35:31 -0800 (PST) (envelope-from patl@phoenix.volant.org) Received: from patl by knight.phoenix.volant.org with local (Exim 3.20 #1) id 14W3Rg-000NBy-00 for freebsd-fs@freebsd.org; Thu, 22 Feb 2001 13:38:40 -0800 To: freebsd-fs@freebsd.org Subject: Status of nullfs Message-Id: From: Pat Lashley Date: Thu, 22 Feb 2001 13:38:40 -0800 Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The man page in -STABLE for mount_null contains dire warnings about its lack of support and potential to cause problems. But how solid/shakey is it really? Is it, in practice, safe to use? Is there any particular usage that is more likely to cause problems, or are the warnings just there because nobody is actively keeping it up to date? In other words, if I'm willing to take the risk of using it, just how big of a risk am I actually taking? Thanks, -Pat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message