Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!uw-beaver!tektronix!reed!psu-cs!mmason
From: mmason@psu-cs.UUCP (Mark C. Mason)
Newsgroups: comp.os.minix
Subject: Re: Problem with "mount"
Message-ID: <430@psu-cs.UUCP>
Date: Sat, 29-Aug-87 10:48:36 EDT
Article-I.D.: psu-cs.430
Posted: Sat Aug 29 10:48:36 1987
Date-Received: Sun, 30-Aug-87 09:20:17 EDT
References: <4242@ncoast.UUCP> <271NU070156@NDSUVM1> <1418@galbp.LBP.HARRIS.COM>
Reply-To: mmason@psu-cs.UUCP (Mark C. Mason)
Organization: Dept. of Computer Science, Portland State University; Portland OR
Lines: 16

In article <1418@galbp.LBP.HARRIS.COM> bing@galbp.UUCP (Bing Bang) writes:
>Am I missing something here? You do know that you can't mount anything to a
>directory unless it is completely empty, don't you? Try

Wrong.  All mount does is set a flag in the inode of the directory being
mounted on and make a mapping of old/new devices/directories in /etc/mtab.
It makes no difference whether the directory is empty or not.

The most probable reasons for the error message are 1. some process
has an open file in /tmp, or 2. the device is mounted elsewhere.  In this
case check for open files (there was a program which did just this
posted to the net a while back called ofiles; I use it all the time
on VAX/BSD).


					Mark