Path: number1.nntp.dca.giganews.com!border1.nntp.dca.giganews.co
!nntp.giganews.com!wns13feed!worldnet.att.net!199.45.49.37!cyclo
e1.gnilink.net!spamkiller2.gnilink.net!gnilink.net!trndny04.POST
D!c7294747!not-for-mail
From: Chris Fasano 
Subject: Re: Question about mount command and location of files
User-Agent: Pan/0.14.2.91 (As She Crawled Across the Table (Debian GNU/Linux))
Message-Id: 
Newsgroups: alt.os.linux.ubuntu
References:   <54pnb4F21pso3U1@mid.individual.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Lines: 33
Date: Fri, 02 Mar 2007 13:23:43 GMT
NNTP-Posting-Host: 70.18.203.110
X-Complaints-To: abuse@verizon.net
X-Trace: trndny04 1172841823 70.18.203.110 (Fri, 02 Mar 2007 08:23:43 EST)
NNTP-Posting-Date: Fri, 02 Mar 2007 08:23:43 EST
Xref: number1.nntp.dca.giganews.com alt.os.linux.ubuntu:11309

On Fri, 02 Mar 2007 04:26:13 +0000, Blue wrote:
> 
> Mounting does not shift the files (phyisically). It just allows them to be
> read. 


Thank you.  This explanation is (somewhat) what's causing my
misunderstanding.  If files aren't physically moved by mounting, then if I
create a directory under hda1 (home/newdirectory) the /newdirectory is
physically located on hda.

So why would any files now created under /newdirectory be physically
located on hdb just because I mounted /dev/hdb1 to /home/newdirectory,
since as you say "mounting does not shift files physically?"

I'm not disputing the answer, just trying to understand how it works, 
and it's driving me nuts.  I won't post again on this issue; thanks
again.

Is there a difference between these two tasks:

1. mkdir under /home
2. add files to /home/newdirectory
3. mount /dev/hdb to /home/newdirectory

and

1. mkdir under /home
2. mount /dev/hdb to /home/newdirectory
3. add files to /home/newdirectory

There must be a difference between these tasks.  I'll experiment tonight
after work.
--- Platinum Xpress/Win/WINServer v3.0pr5
 * Origin: Omicron Theta BBS (1:261/20)