From owner-freebsd-bugs  Fri Feb 13 18:20:03 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA04927
          for freebsd-bugs-outgoing; Fri, 13 Feb 1998 18:20:03 -0800 (PST)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id SAA04921;
          Fri, 13 Feb 1998 18:20:02 -0800 (PST)
          (envelope-from gnats)
Date: Fri, 13 Feb 1998 18:20:02 -0800 (PST)
Message-Id: <199802140220.SAA04921@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: Tor Egge <Tor.Egge@idi.ntnu.no>
Subject: re: kern/1067: panic: ufs_lock: recursive lock not expected, pid: 27195
Reply-To: Tor Egge <Tor.Egge@idi.ntnu.no>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

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

From: Tor Egge <Tor.Egge@idi.ntnu.no>
To: freebsd-gnats-submit@FreeBSD.ORG
Cc:  Subject: re: kern/1067: panic: ufs_lock: recursive lock not expected, pid: 27195
Date: Sat, 14 Feb 1998 03:12:05 +0100

 I wrote:
 > Then	
 > 	mount /dev/fd0 /
 > would give 
 > 	/dev/fd0 on /: Device busy
 
 Incorrect.
 
 The mount command (not the system call) handles "/" specially, and adds
 an implicit MNT_UPDATE option, thus the result is normally
 	/dev/fd0 on /: Specified device does not match mounted device.
 with or without the suggested fix.
 
 - Tor Egge

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message