Date: Sat, 14 Feb 1998 04:59:15 +0100 From: Tor Egge <Tor.Egge@idi.ntnu.no> To: wollman@khavrinen.lcs.mit.edu Cc: freebsd-bugs@hub.freebsd.org Subject: re: kern/1067: panic: ufs_lock: recursive lock not expected, pid: 27195 Message-ID: <199802140359.EAA02579@pat.idi.ntnu.no> In-Reply-To: Your message of "Fri, 13 Feb 1998 21:45:12 -0500 (EST)" References: <199802140245.VAA28222@khavrinen.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> Gack. I don't see any good reason for such a change (other than the > dubious example of compatibility with Slowaris). Mount points should > not be treated any differently than any other directories. Since MNT_UPDATE is implicit for "/" (which I did not notice when I started writing my reply to kern/1067) and the "-a" option for the mount command does not cause already-mounted filesystems to be mounted again, you are correct. Based upon the manual page and the system call implementation, I mistakenly concluded that the change was useful in order to prevent an accidental mount of a different file system at '/'. This is indeed impossible using the mount command. Those using the mount system call directly probably knows what they are doing. Consider that part of the suggested fix withdrawn. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802140359.EAA02579>