From owner-freebsd-bugs  Fri May 16 00:50:03 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id AAA15246
          for bugs-outgoing; Fri, 16 May 1997 00:50:03 -0700 (PDT)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id AAA15228;
          Fri, 16 May 1997 00:50:01 -0700 (PDT)
Date: Fri, 16 May 1997 00:50:01 -0700 (PDT)
Message-Id: <199705160750.AAA15228@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: Doug Rabson <dfr@nlsystems.com>
Subject: Re: bin/3588: Memory Filesystem unmounting problem
Reply-To: Doug Rabson <dfr@nlsystems.com>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR bin/3588; it has been noted by GNATS.

From: Doug Rabson <dfr@nlsystems.com>
To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de>
Cc: yugawa@orleans.rim.or.jp, FreeBSD-gnats-submit@freebsd.org,
        dfr@freebsd.org
Subject: Re: bin/3588: Memory Filesystem unmounting problem
Date: Fri, 16 May 1997 08:39:51 +0100 (BST)

 On Fri, 16 May 1997, J Wunsch wrote:
 
 > [snip]
 >
 > That's the wrong fix, IMHO.  Umounting other mount points that use the
 > same syntax will still yield the same problem (e.g., amd writes a
 > similar entry to mfs).
 > 
 > Doug recently fixed some problem like:
 > 
 > [snip]
 > 
 > I think the logic should be reversed: only if the type is MOUNT_NFS,
 > there should be a hostname lookup.  Everything else is local.
 
 You're right.  I should have thought of that at the time.  I will fix it
 today.
 
 --
 Doug Rabson				Mail:  dfr@nlsystems.com
 Nonlinear Systems Ltd.			Phone: +44 181 951 1891