Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

EAs on directories causing problems with vista users



I've been doing some mucking around with my Leopard 10.5.2 dev server and came across something that I'd like to get feedback/verification from other users. It seems that if you have a folder on a 10.5.2 sharepoint, shared via Samba, and the folder has (certain, common) extended attributes, Vista users will get an error when they try to download the folder. The error the Vista user will get is: "Error 0x800700FE: The specified extended attribute name was invalid."

To state it plainly, if you 1) have extended attributes on 2) a directory that 3) has a colon in the attribute's key or value, Vista will produce an error and prohibit downloading.

It's pretty easy to duplicate. Create a folder on your Mac OS X desktop. Do a "get info" on the folder and type something in the Spotlight metadata field. Now drag the folder to a share on your Leopard server (using AFP). Over on your Vista workstation, try to download it (obviously using SMB). It should invoke the above error. If you do the same thing except substituting a file instead of a folder, you should *not* get the error.

I figured this out from a VMWare virtual machine. The "file" called ubuntu.vmwarevm on my Mac, was uploaded via AFP to a Leopard server. I tried downloading it to a Vista client, and it balked. The ubuntu.vmwarevm is actually a bundle or a package, an opaque directory[1]. Here's its extended attribute, which tells Time Machine not to back this up:

[nbfa@crc-img-back 16:00:51 ~/Library/Virtual Machines]# exattr -l ubuntu.vmwarevm [2]
com.apple.metadata:com_apple_backup_excludeItem: bplist00_com.apple.backup


If I created a directory on my Vista machine, I could download the components in the package, like the .vmx configuration file, virtual hard drives, etc -- even though those files have the same EA.

Additionally, if I deleted the EA on the object, then added an EA with something like "color" "red" via command line, so that the EA on the directory doesn't have a colon, Vista doesn't complain. It's a legal name for an EA.

The problem is, just about any EA created by Mac OS X will have a colon in at least the key field, because it follows the reverse-DNS convention and uses a colon to separate fields. Like Finder meta- information for example;

[nbfa@crc-img-back 17:29:41 ~/Library/Virtual Machines]$ exattr -l my_installer.pkg
my_installer.pkg
com.apple.metadata:kMDItemFinderComment bplist00[hello worl




[1] Curiously, other packages, like .mpkg files, are understood by both Mac OS X and Vista as a true file, not an opaque directory. VMWare virtual machines on the other hand -- directories that have the .vmwarevm extension, gain the behavior of a bundle, so that you can double-click on this directory and Fusion will launch.

[2] You can use the xattr tool to view extended attributes. I used a third-party tool of the same name, which I renamed exattr to differentiate the two. See <http://arstechnica.com/reviews/os/macosx-10-4.ars/7 > and <http://dev.bignerdranch.com/public/bnr/>.



Noah


------------------- Noah Abrahamson Stanford University


Attachment: smime.p7s
Description: S/MIME cryptographic signature

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden

This email sent to email@hidden



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.