Hacker News Reader

Comment by js2 | Hacker News Reader

I believe you're confusing the .DS_Store files which are per-directory and used for storing Finder window metadata with the "._" prefixed files (so-called AppleDouble format) which are used to store a file's resource fork. (These also show up in zip files created via the Finder.)

You can configure Samba to store resource forks using xattrs instead. See fruit:resource:

https://www.samba.org/samba/docs/current/man-html/vfs_fruit....

You can veto the .DS_Store files. The consequence to Mac users is that the Finder won't remember any display changes they make to windows that correspond to network folders.

https://www.samba.org/samba/docs/current/man-html/smb.conf.5...

View on HN

This is the configuration I use:

  veto files = /._*/.DS_Store/.Trashes/.TemporaryItems/
  delete veto files = yes

The second line allows vetoed files to be deleted. Otherwise, already existing vetoed files would be stuck on the drive.

(Note that "._*" prevents HFS+/APFS extended attributes from being stored on the SMB drive.)

> You can veto the .DS_Store files. The consequence to Mac users is that the Finder won't remember any display changes they make to windows that correspond to network folders.

Good. Why would one user's view preferences have an effect on another user? That is what happens if .DS_Store files are left on the server.

It makes a weird sort of sense if you consider the folder to be like a stockroom - when you tell someone the box they want is “on the right as you enter” you expect it to be in the same place you saw it.

Well, it depends on who has write permission on the . DS_Store file.

If you have readonly access to the folders you can't persist a change to the layout.

You don't need samba for that, you can (and should!) configure you Mac not to write them in the first place. See e.g. https://support.studionetworksolutions.com/hc/en-us/articles... (random google result).

    defaults write com.apple.desktopservices DSDontWriteNetworkStores -bool TRUE

You can't, as far as I know, do the same for locally mounted/connected drives, though.

Reply on news.ycombinator.com