From owner-freebsd-stable Sat Jan 12 17:45:19 2002 Delivered-To: freebsd-stable@freebsd.org Received: from glass.dnsart.com (L028211.ppp.dion.ne.jp [211.126.28.211]) by hub.freebsd.org (Postfix) with ESMTP id B69A037B41A for ; Sat, 12 Jan 2002 17:45:16 -0800 (PST) Received: from localhost ([127.0.0.1]) by glass.dnsart.com with esmtp (Exim 3.33 #1) id 16PZhr-00043m-00; Sun, 13 Jan 2002 10:45:07 +0900 Date: Sun, 13 Jan 2002 10:45:04 +0900 (JST) From: Tod McQuillin X-X-Sender: devin@glass.pun-pun.prv To: Edvard Fagerholm Cc: freebsd-stable@freebsd.org Subject: Re: mount_null problems In-Reply-To: <1010875546.1942.0.camel@ryssa.cyberland.fi> Message-ID: <20020113104154.G78412-100000@glass.pun-pun.prv> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 12 Jan 2002, Edvard Fagerholm wrote: > Any ideas, why this doesn't work or why it's stupid or impossible to do I would love to use mount_null too because it seems like a good solution for a number of problems. However, did you read the BUGS section of the man page? BUGS THIS FILESYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T WORK) AND USING IT MAY, IN FACT, DESTROY DATA ON YOUR SYSTEM. USE AT YOUR OWN RISK. BEWARE OF DOG. SLIPPERY WHEN WET. This code also needs an owner in order to be less dangerous - serious hackers can apply by sending mail to and announcing their intent to take it over. I crashed FreeBSD quite a few times trying to use nullfs. Now I know better. -- Tod McQuillin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message