cneely@cybermemphis.com
2002-Feb-14 12:07 UTC
[Samba] changing macintosh type and creator codes
Anytime a PC on our network copies a file to our server and a macintosh client goes to view that file, the type and creator codes are incorrect. We are running Samba for Windows clients and Xinet KA-Share for Mac clients. I think it has something to do with the resource forks. I can copy a file to the server from a Mac then copy the file from the server to a windows machine and back again and the type and creator codes will be changed. Any ideas anyone? Thanks, Chris -------------- next part -------------- HTML attachment scrubbed and removed
On Thu, 14 Feb 2002 cneely@cybermemphis.com wrote:> Anytime a PC on our network copies a file to our server and a > macintosh client goes to view that file, the type and creator codes > are incorrect.I think I know what the problem is, but I don't know how to fix it. Macs keep metadata associated with a file -- its type, creator, creation date. etc. The type and creator info are the most important for most uses, as they determine the icon attached to a file / what is run when you double-click on it. Some file sharing systems have a mapping from extension -> type/creator. A partial solution is something on the Mac that assigns type/creator info based on a file's name.> I can copy a file to the server from a Mac then copy the file from the > server to a windows machine and back again and the type and creator > codes will be changed.Maybe the metadata file is not copied back? Dunno. Make sure you're not preventing some files (matbe dotfiles?) from being copied. -- -eben eQbWeEnR@gTaYtUeI.nOePt home.tampabay.rr.com/hactar Logic is a systematic method of coming to the wrong conclusion with confidence.
This is not unusual - a PC has no concept of type and creator - it relies on the extension. This means that when a PC copies a file from a macintosh, it doesn't bother to / can't read that kind of data - it's irrelevant to a PC. Therefore when it copies back to the mac, you don't have any of the information to put back, even if the mac could ask for it. The only way to achieve this is through an extension map. If you use netatalk on the Linux machine, you can define such a map, but that just shares from Linux to macs, not to pcs, you would still need samba to share to the pcs, and all files would have to be transferred to the Linux box, and out again, for use on the mac. At 02:04 PM 2/14/02 -0600, cneely@cybermemphis.com wrote:>Anytime a PC on our network copies a file to our server and a macintosh >client >goes to view that file, the type and creator codes are incorrect. We are >running >Samba for Windows clients and Xinet KA-Share for Mac clients. I think it has >something to do with the resource forks. I can copy a file to the server >from a >Mac then copy the file from the server to a windows machine and back again >and the type and creator codes will be changed. Any ideas anyone? >Thanks, Chris-------------- Martyn Ranyard I am not a member of the samba team, and anything that I say may not be as accurate as a response from one of the team. I reply to save those more qualified time, which can more usefully be spent developing SAMBA further.