From owner-freebsd-bugs  Fri Feb 16 02:54:23 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id CAA27549
          for bugs-outgoing; Fri, 16 Feb 1996 02:54:23 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA27534
          for <freebsd-bugs@freefall.freebsd.org>; Fri, 16 Feb 1996 02:54:13 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id VAA06609; Fri, 16 Feb 1996 21:43:59 +1100
Date: Fri, 16 Feb 1996 21:43:59 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199602161043.VAA06609@godzilla.zeta.org.au>
To: freebsd-bugs@freefall.freebsd.org, j@uriah.heep.sax.de
Subject: Re: bin/1029: weird behavior after mounting
Sender: owner-bugs@FreeBSD.ORG
Precedence: bulk

> > 	cd /cdrom
> > 	ls
> > 	[Nothing -- cdrom is not mounted]
> > 	mount /cdrom
> 
> I think this should fail with an EBUSY.

Directories are almost never busy in FreeBSD.  E.g.,

	cd /cdrom
	ls
	[Nothing -- cdrom is not mounted]
	mkdir foo
	cd foo
	rmdir .
	[rmdir: .: Invalid argument]	# failure for superstitious reasons
	rmdir /cdrom/foo		# succeeds
	/bin/pwd
	[pwd: No such file or directory]	# duh, which file or directory?

Any other behaviour would be surprising (and the failure to remove "."
is surprising) because it's the inodes that may be busy, not the directory
entries that point to them.

Not failing with EBUSY for union mounts may actually be useful.

Bruce