17 ms·
.Trashes, .fseventsd, and .Spotlight-V100
- konsumer 12y agoI do this if I forget to add .DS_Store to .gitignore when working with git repos: find . -name .*DS_Store -delete
- singlow 12y agoJust be careful. A coworker of mine did this recently and forgot the -name part. Accidentally deleted everything, including the .git directory. He sure wished he had pushed that day.
- manicdee 12y ago*that hour. Surely you don't cruise through to the end of a day without pushing at least once before lunch? :(
- jordigh 12y agoI commit often, rewrite mercilessly, and thus I push to the big server infrequently. I do push frequently between local machines and servers. Mercurial Evolve makes propagating these edited commits across my local servers quite nice. Anyways, besides the plug for hg, my point was that I would expect pushing could be a once-a-day kind of thing, whereas commits should be every five minutes. :-)
- singlow 12y agoI agree. Pushing too frequently means you can't rebase and reorganize your commits - unless you each use separate repos.
- manicdee 12y agogit config --global core.excludesfile ~/.config/git/ignore cat >> ~/.config/git/ignore .DS_Store .AppleDouble .LSOverride .AppleDB .AppleDesktop .apdisk .fseventsd .Trashes .Spotlight-V100 ._* Icon Network Trash Folder Temporary Items Icon
- arnehormann 12y agoyou have missed mkdir -p ~/.config/git
- xorcist 12y agoWhy not .* ? I can't think of a good reason to commit hidden files.
- kayoone 12y agoput stuff like this in your global gitignore and you will bever have to worry about these files again. Stuff like this does not belong in a projects gitignore anyway because it's system specific.
- pippy 12y agoIt is annoying when copying a movie to a USB, and having to empty the entire trash bin to fit it on the USB stick. I guess it does enforce you to be a bit cleaner. I don't really care about .DS_store etc as they're hidden, and thumbs.db is just as bad.
- simlevesque 12y ago> I don't really care about .DS_store etc as they're hidden They ain't if you are on Windows.
- derefr 12y agoThat's really just silliness on the part of Apple; if they're creating dotfiles on a FAT32/NTFS/ExtFS disk, they should be setting the Hidden attribute for those same files. This is what e.g. Samba does automatically for network-attached FAT/NTFS folders on OSX/Linux clients, if I recall.
- manicdee 12y agoThere was a patch submitted to the Darwin project to do this: Https://lists.apple.com/archives/Darwin-kernel/2004/Jul/msg00120.html I don't think it ever got reviewed though.
- recursive 12y agoThumbs.db doesn't end up in every zip file ever.
- nkantar 12y agoThis accomplished two things: 1. I now know a few things I've wondered for a long time. 2. I have just been reminded of how little I really know, even about devices I use for most of my waking hours.
- derefr 12y agoA few little arguments in favor of this practice: 1. You plug a USB device into one Mac. It asks you if you want to use it for Time Machine. You say no. Now, no other Mac will ask you this question again—because the preference has been stored on the drive, instead of on the computer. 2. You create a folder with an app you've written in it, and customize it with a cute "drag [this] onto [shortcut to Applications folder]" background, centering the icons on the background positions and sizing the window to perfectly fit the representation. You then copy this folder to another Mac (or any equivalent process, such as converting it into a DMG disk image and having someone download it.) They see exactly what you saw. 3. You keep an external hard disk that you frequently move back-and-forth between two Macs. The first time you plugged it into one of the Macs, it was indexed. Each time you modify it on either Mac, that index gets updated. The most recently created files are the most likely to be the ones you'll want to find through Spotlight when you plug the disk into the other Mac—but if the index was machine-local rather than disk-local, the new Mac wouldn't know about the new files yet, and would have to finish re-indexing to find them. (This is, of course, what happens when you modify the disk on a Windows computer, and it sucks. We really need a "metadata index API" to start being an expected offering of a filesystem, such that all OSes interacting with the filesystem can read and update it!) On the other hand, Windows' Thumbs.db is exactly the sort of thing you don't want cached on the media. It'd be a great innovation if, say, cameras could pre-generate Thumbs.db files so Windows could immediately show the user what was on an SD card the first time it got plugged in... but cameras don't, because Thumbs.db is a random proprietary format. So, instead, it's only useful in the same situation that the Spotlight index is: moving a drive full of photos back and forth between two computers. Which might have separate screen DPI, and thus be set to show different thumbnails, meaning new thumbnails will get generated anyway.
- userbinator 12y agoHopefully users will push back; demanding to be given more options, and more control. We've gotten to a point where the role technology plays in our lives is too integral to keep letting that control slip away, one "harmless" feature at a time. Amen to that. Unfortunately it seems the trend is towards hiding the filesystem/concept of files completely from the user and replacing it with app-specific isolated storage in a proprietary format, which is even worse than unsolicited filesystem modifications. (On the other hand, it could be argued that these modifications would become even less noticeable in such a system... which is good or bad depending on who you ask. I'm firmly on the latter side.) A physical write-protect is something all removable storage should have.
- piersadrian 12y agofor the love of christ, it's OS X, not OS/X
- jordigh 12y agoTo distinguish it from its predecessor, Mac OS IX? Trolling is a art.
- yellowapple 12y agoI want to see someone come out with an OS/2 skin of sorts for OS X, just to make everyone in the world that much more confused.
- delinka 12y agoAnd I hope you're pronouncing that as "Oh Ess Ten" and not "Oh Ess Ecks" ;-)
- angelortega 12y agoSo that .Spotlight-V100 store some kind of index, probably binary. I presume that any Mac reads it on any arbitrary USB drive it's plugged in (or, at least, when a search is triggered). By creating a specially-crafted, corrupted index I see a channel for denial of service attacks.
- dchest 12y agoYou can probably still abuse NSDictionary, causing HashDoS (https://gist.github.com/dchest/4467707 https://gist.github.com/dchest/4467707). I did it with QuickLook a few years ago; don't know if they replaced a hash function there.
- 0x0 12y agoBefore OSX 10.10.2, apparently there was a "heartbleed" style info leak in spotlight where it "may save unexpected information to an external hard drive", according to http://support.apple.com/en-us/HT204244 http://support.apple.com/en-us/HT204244 (CVE-2014-8832). Probably related to this report: https://www.f-secure.com/weblog/archives/00002752.html https://www.f-secure.com/weblog/archives/00002752.html
- nfoz 12y agoIt's just nonsense that this metadata would be dropped as files scattered across the filesystem, rather than simply held in a single location on the host machine. They're a fragment of the OS, not of each directory.
- PinguTS 12y agoWhich would mean that those meta data is only available on this host and not anywhere. The problem is the short coming of those file systems not to allow to store arbitrary meta data to any file.
- nfoz 12y agoThat's exactly what I want though. "Folder display preferences" are a thing that pertain to exactly one instance of one operating system. If I want to share "folder displays" to a different computer (which seems rather unnecessary), that seems like an explicit action I might take between the two computers, and all that metadata should be a single bundled file that is transferred between machines. Not per-directory metadata that is bundled into my filesystem everywhere.
- Doctor_Fegg 12y agoI'd be more inclined to berate Apple for this were it not for the amount of crap that Unix-style tools dump in my home directory. I count 50 .-prefixed files or directories at present, some of which is from Mac developers who should know better (hello, Adobe, Dropbox), some is cryptically-named gunk from other tools (.vegas, .jmf), some various command line histories (bash, fcsh, mysql, psql, pry, sqlite, irb), and so on. OS X is nicer than traditional Unix behaviour here - it puts it all in a well-organised ~/Library directory.
- rat87 12y agoOn Linux things should go in xdg dirs ~/.config ~/.local and ~/.cache instead of ~ but a lot of old unix software and sadly a decent amount of new software(even guis) don't follow the standard.
- __david__ 12y agoEven 50 is nothing. On my Linux machine: $ ls -d ~/.* | wc -l 342
- kedean 12y agoI got the impression that he's not upset about all the dotfiles, he's upset that they put them on external media. Most unix programs will only create those in the users home, which is usually not external.
- blueskin_ 12y agoNever understood why they do this. Surely they should keep junk off removable drives, as they are the most likely to be used in other systems including ones that don't hide data from the user.
- nathanstaines 12y agoEject for Windows (http://www011.upp.so-net.ne.jp/decafish/EjectForWindows/EjectForWindowsE.html http://www011.upp.so-net.ne.jp/decafish/EjectForWindows/Ejec...)
- wampus 12y agoWhat happens when the drive is shared among Macs? Why isn't this a vector for exploitation?
- __david__ 12y agoWell, if you find a buffer overflow that can lead to code execution in spotlight (mds) or fseventsd then it very well could be a vector. Assuming no bugs in those (hah), then I'm not sure what you could exploit…
- chiph 12y agoIt seems to me, that if I insert a removable media that is formatted with one of the FAT filesystem variants, that I probably don't want those hidden files & folders created. As it's a sign that the ultimate destination probably isn't another Mac.