From owner-freebsd-stable Sun Jan 13 4:53:19 2002 Delivered-To: freebsd-stable@freebsd.org Received: from cyberland.fi (mail.cyberland.fi [62.142.63.103]) by hub.freebsd.org (Postfix) with SMTP id C3E4837B405 for ; Sun, 13 Jan 2002 04:53:10 -0800 (PST) Received: (qmail 56240 invoked from network); 13 Jan 2002 13:06:20 -0000 Received: from unknown (HELO ryssa) (62.142.63.76) by 0 with SMTP; 13 Jan 2002 13:06:20 -0000 Subject: Re: mount_null problems From: Edvard Fagerholm To: Tod McQuillin Cc: freebsd-stable@freebsd.org In-Reply-To: <20020113104154.G78412-100000@glass.pun-pun.prv> References: <20020113104154.G78412-100000@glass.pun-pun.prv> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.99.0 (Preview Release) Date: 13 Jan 2002 10:52:49 -0200 Message-Id: <1010926373.4008.0.camel@ryssa.cyberland.fi> Mime-Version: 1.0 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 Yeah, I never looked at the man page for known bugs. After seeing so many people advertise it on -questions and in several other places I thought it would have been stable. Well, I was wrong, now I know better. I already got one suggestion as a solution to this problem which is to locally export the filesystem with NFS and mount it from the localhost i.e. "loopback" NFS. This seems stable and I haven't been able to crash anything using it. And it really doesn't hurt in any way either as I'm already running portmapper etc. on the host. Another suggestion was automounter. I've never really used it in practice and it seems to be a solution to limit the amount of mounts needed, as I don't need to permanently mount each directory, only when they are actually needed. Anyways, thanks for the replies. - Edvard On Sun, 2002-01-13 at 03:45, Tod McQuillin wrote: > 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