Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'SMB on 10.1 and the' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
SMB on 10.1 and the
Authored by: jcalchi on Oct 02, '01 06:08:31PM

Thank you all for the help mounting to Window$ shares with OS X 10.1. I was able to use it only for a short while. Upon mounting the shares, I got a nasty call from my IT dept. They do not appreciate all the "._.Trashes" files etc. being created on all the shares that I visit. I have since been shut down from mounting shares via SMB on 10.1. I was using Dave, but that doesn't work now in 10.1. Does anyone know what these files are for, and what I can do about them? Until I get this fixed, I am forbidden from mounting shares with my Mac. (Of course no one even knew I was doing it for the last six months with Dave for OS X.)

[ Reply to This | # ]
SMB on 10.1 and the
Authored by: myersm on Oct 04, '01 10:08:43AM

The "special" files are a bit annoying.

I am saving PDFs to a WinNT sharevolume from within Acrobat Reader. In addition to the data file, it is also creating a separate file for the resource fork:


Is this a behavior that the OS could perform conditionally? It's all unix under the hood, right? Couldn't programs check to see if the fstype of the destination volume was smbfs and act accordingly -- omit the resource fork?

In the meantime, I will have an agent delete these special files on an hourly basis.

[ Reply to This | # ]
Authored by: myersm on Oct 04, '01 10:23:28AM

Ok, now I discover that if I delete the special resource file associated with the data file, the Mac can no longer open the file.

Whether I double click the file in a finder window, or try to open the file from within Acrobat Reader, I get an error:

"There was a Macintosh system error (-39)."

Of course, the PDF file is intact and will open just fine on the WindowsNT side.

[ Reply to This | # ]
my experiments
Authored by: sfhipster on Oct 16, '01 03:20:17AM

1. from smb://$computername/$share
does leave the ._ trashes files
also saves resource forks

2. from sharity (free for individual use)
does not leave ._trashes type files
but does do the resource fork thing.
however, i deleted the resource fork file, and could still open files from the mac.

3. thought that with os X, we'd be done with the resource fork thing, or is is a hfs+ file system thing? wonder if my driver were formatted ufs, would there still be the issue of resource forks?


[ Reply to This | # ]