7 ms·

What Apple need to do now is make their devices more linux-server friendly out of the box. I have scripts set up on all of my storage servers to scan for and re

• eli 5y ago
  Would an endpoint management system like Jamf let you enforce that policy?
  • angulardragon03 5y ago
    Yeah you can do this with MDM, just target the com.apple.desktopservices preference domain and set DSDontWriteNetworkStores to true.
• MBCook 5y ago
  There’s a command to stop that? What is it?
  • thatoneguy 5y ago
    defaults write com.apple.desktopservices DSDontWriteNetworkStores false and reboot.
    • NorwegianDude 5y ago
      False? Did you mean true? Terrible naming on that one...
      • mypalmike 5y ago
        DSDontForgetNotToWriteNetworkStores = "False"
    • Sidnicious 5y ago
      FYI: I believe this works because it saves the string "false", which is truth-y. You can also use: defaults write com.apple.desktopservices DSDontWriteNetworkStores -bool YES
• st3fan 5y ago
  This feels like a very user-hostile attitude ... Also, these files provide a useful service to Mac users. You could also find a way to support them instead of fighting this.
  • alt227 5y ago
    You hit the nail on the head. It provides a useful service to 'Mac' users. To literally every other OS user these files are considered bloat and slow the system down for everybody. Hell, linux users performing searches on these directories get duplicate results for every file a mac has touched. I appreciate it may come across as a bit hostile towards the users, but in reality in a budget constrained environment where we cant make it perfect for everybody, we must make sacrifices to make the majority of users have a better experience. In my opinion mac users not having metadata of when a file was last modified pales in comparison to the rest of the business searches taking twice as long on samba shares.
    • Tabular-Iceberg 5y ago
      Why is it necessary to index .DS_Store files, though? Isn’t that what’s making searches slow, not that the files exist? Why do you suppose that this isn’t a problem for Macs too?
    • lilyball 5y ago
      .DS_Store is one file per directory, and it's a dotfile too so it should be hidden by default from most *nix commands.
      • alt227 5y ago
        Thankyou for correcting me. I was speaking from old knowledge as this was a while ago I set this up and couldnt quite remember exactly how the .DS_store system worked. I thought it was one .ds_store file per file. That being said, depending on your business and data structure this doesnt detract from the point. Also if you have a deep nested directory structure with no real files in it, would every level contain a .ds_store file?
• Matt3o12_ 5y ago
  Assuming you’re running a smb server, you could just veto the files. Windows isn’t much better since it likes to create thumbs.db almost everywhere too (which I also veto, but vetoing them can increase the load and bandwidth requirements and your server and clients)
  • alt227 5y ago
    Yeah Vetoing is an option, although without testing I do not know how the mac clients would react on saving a file and its metadata was not allowed. Would the mac throw an error? EDIT: I have had people say this to me before about windows and thumbs.db. But I personally have not seen this in the wild. Maybe its what old versions of windows did and people are still remembering this?
    • Matt3o12_ 5y ago
      I haven’t seen any errors and macOS seems to handle it greacefully. You can also disable it on macOS clients for network servers individually but that seems to be a loosing battle (even if you control all clients). They are finder settings after all https://serverfault.com/a/5567 https://serverfault.com/a/5567 Thumbs.db files are created on my windows 11 pc at least. They’re only created for files that have metadata that requires reading those files. Explorer likes to display the metadata (sometimes) for some folders that have a lot of media in it (pictures, music, videos, etc). If the thumbs.db file is missing, windows will partially read every media file on the server to show thumbnails, that obviously creates unnecessary load but it’s really a trade off that might not make sense for most.
  • Avery3R 5y ago
    thumbs.db hasn't been a thing since XP... Vista+ generates thumbcache_xxx.db within the user's temp folder.
• mistrial9 5y ago
  LOL - for fifteen years Apple has refused to allow an ext4 formatted volume to auto-mount on a MacOS X machine.. how hard is that? Apple is non-Apple hostile, and proud of it
  • throwaway894345 5y ago
    As far as I know, MacOS doesn’t support ext4 at all (I vaguely recall some read-only ext4 FUSE thing, but obviously that doesn’t help if you need to write).
    • js2 5y ago
      https://www.paragon-software.com/home/extfs-mac/ https://www.paragon-software.com/home/extfs-mac/ Full ext2/3/4 read-write support. $39.95. There's also fuse-ext2 via macFUSE but its doc still say: "Even though write support is available, please do not mount your filesystems with write support unless you have nothing to lose." https://github.com/alperakcan/fuse-ext2 https://github.com/alperakcan/fuse-ext2
  • js2 5y ago
    I'm not sure what you mean by "refused to allow". It's not like Apple has prevented third-parties from adding support: https://www.paragon-software.com/home/extfs-mac/ https://www.paragon-software.com/home/extfs-mac/ It also doesn't seem surprising to me that Apple itself wouldn't support ext2/3/4. It's something very few Mac users are going to care about. Why would Apple dedicate any resources to it? FWIW, I've been using Linux and Macs for over two decades and I can only recall maybe a single time I even wanted to mount an ext formatted drive onto a Mac, and vice-versa (HFS onto Linux). For exchanging files via floppy disks or thumb drives, various flavors of FAT have been near universal for ages. CDs/DVDs/BluRay use their own filesystem. And FTP/NFS/SMB/AFP/HTTP/SCP/RCP have been around forever for exchanging over a network. (Before ssh/scp, there was unencrypted rlogin/rsh/rcp... I'm dating myself.)
    • lupire 5y ago
      Why does Windows userbase care more about Linux drive interop than Mac userbase does?
• chefandy 5y ago
  What I'd love is a robust, modern, relatively easy-to-configure, focused DAV server— specifically one that includes calendaring and notes. Everything out there is either incomplete, fussy as all getout to set up, dogmatically simple and therefore requires external mitigation, only supports one or two clients, and/or some janky PHP amalgam. What I'd REALLY love is to be able to run all of my own services in place of iCloud. I realize that this stuff isn't free to develop and I'd happily pay for it. They've been moving further away from standard formats and protocols with no way for others to integrate in the same way and I'm curious if there are any legal anticompetitive actions on the table should they continue to do so. Before anybody says it— I have business needs that favor using MacOS directly on Apple Hardware and as a result, iOS is a good choice. Moving from Apple would regularly cause me more grief than these things do. No, you don't know my use case better than me and I have exhaustively explored all alternatives both ancient and modern.
  • NicoJuicy 5y ago
    We can't know, because you're not saying the use-case
  • the_pwner224 5y ago
    I've found that Radicale works very well for DAV calendar, tasks, address book. I combine it with Syncthing for files, and use Obsidian.md as the note-taking application (using the synced folder for storing the notes folder). Of course when you have a synced folder you can use whatever note-taking application/system you want. I'm not sure if that will work on iOS since iOS doesn't really have a filesystem - there are apps available on iOS for Syncthing and Obsidian, but I don't know if Obsidian will be able to access the Syncthing synced folder. But it works great for me on Linux PCs + Android. Much better than Nextcloud which is too complex and is a pain to administer over time. Syncthing is super simple to set up does file sync very well, much better than Nextcloud does. Radicale is also easy to set up and just works.
    • chefandy 5y ago
      iOS only needs to be a client and it has standard CalDAV/CardDAV clients built into the OS. I've used Radicale— it works OK for very basic functionality, but doing something as simple as making a shared calendar involves creating one in the GUI, logging into the server and sym linking them between user directories. The nice thing about the groupware functionality in Apple Server is that it used all of these standard protocols so it was entirely interoperable with other devices AND it had a nice smooth administration experience. At the moment, I just pay $15/mo for Cloudron which handles email, is decently smooth for administration though a little more disjointed between the apps than I'd prefer, and can "one click" deploy Radicale, NextCloud, Sogo, et. al. I used to administer servers but it's not what I do now and I have no interested in sinking non-work time into work-like tasks.
• js2 5y ago
  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.8.html 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.html#VETOFILES https://www.samba.org/samba/docs/current/man-html/smb.conf.5...
  • LaputanMachine 5y ago
    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.)
    • deleted 5y ago
      [deleted]
  • iamtedd 5y ago
    > 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.
    • bombcar 5y ago
      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.
• deleted 5y ago
  [deleted]
• ccouzens 5y ago
  When I used a Mac at work .DS_Store files on shared drives were annoying. It meant directories loaded with someone else's preferences about how it should be shown.
  • earthboundkid 5y ago
    Apple apparently has forgotten that it makes Finder, but that should have changed to a .sqlite file in the user’s preferences approximately fifteen years ago. It’s so annoying.
  • jscipione 5y ago
    I agree that .DS_Store files getting littered everywhere is a constant menace and that Apple could have solved the problem more elegantly years ago.