Re: Access External Hard Drive - Local and Network

[Mark Wheeler]

That's great. I made the switches in the perl script. Everything was 
great, but then I ran into a problem I did not expect. When I mounted 
the shared PC folder, it came up on my desktop, but when I checked the 
/Volumes/ directory, it gave me the Workgroup name and computer name 
separated by a semi-colon. I can't seem to view the directory in the 
command line OR in the perl script. There must be a pathway I'm missing 
somewhere. When I mount the shared folder using the I.P. number (it's a 
static I.P.), I was able to traverse the directories just fine - both 
in the command line and in perl.

The perl script will be accessing the files over a small network - all 
the computers (Mac and PC) - are hooked into a hub. How do I get into 
directories with my perl script. In the Volumes directory, it lists the 
following as the mounted folder:

PRINCETON;DELLSERVER
How do I get into the server? The pathway I tried is:
/Volumes/PRINCETON;DELLSERVER/........
That didn't work.
PRINCETON is the name of the network and DELLSERVER is the computer 
name - I'm guessing. Do I need to use another perl module to get into 
the PC drive over the network? Or is there some sort of back door I 
need to go through. I can't imagine that it's this difficult.

Thanks again for your help.
Mark
On Apr 29, 2004, at 9:35 AM, Chris Devers wrote:
On Thu, 29 Apr 2004, Mark Wheeler wrote:
I'm not on the network right now, but I'm presuming that the PC
drive(s) would appear in the /Volumes/ directory as well. Can you
confirm that?
Yes -- as a general rule, OSX mounts all filesystems other than the one
you booted from under the /Volumes tree. This includes external drives,
other locally attached physical discs (CD/DVD drives, Zip drives, etc),
network shared drives (AFP, Samba, FTP, WebDAV, etc), and mounted disc
images. I may have omitted some, but that gives you the idea.
The only way this is typically overridden is when, for example, you 
have
a NFS mounted /home directory tree, but that's probably more common 
with
bigger networks than home machines (I assume). That or when you have an
alias or symlink from /Volumes/$foo to /path/to/$bar, but even then 
it's
not that /Volumes isn't being used, it's just being supplemented.

So as the earlier mail you got suggested, everything is in /Volumes.
--
Chris Devers