3 ms·
Adding an interface to access the tag store won't be very hard. It would be harder to make it so that all the tag-oblivious programs, like mv or vi, to say not
by nine_k 8y ago
Adding an interface to access the tag store won't be very hard.
It would be harder to make it so that all the tag-oblivious programs, like mv or vi, to say nothing of rsync, would preserve the attributes when moving or modifying a file.
- netsec_burn 8y agoSounds like you might need to hook rename() if you'd like to add that feature too, but I would still say it's straightforward.
- nine_k 8y agoThe way most editors save a file is like this: f = open("the_file.new") write(f, new_contents); close(f); rename("the_file", "the_file~"); rename("the_file.new", "the_file"); So the old file is never modified, it's renamed to the backup copy, and an entirely new file is created to take its place. This has a number of advantages, but does not play well with any extended info the old file used to have, unless they are copied explicitly. And in a tagging-oblivious program, they won't be.
- netsec_burn 8y agoThanks for teaching me this! I wasn't aware. So, the original xattr (and the program that created it) would be deleted and replaced by vi for example. Still technically right, but I'm unsure how you'd keep a history.
- 6c696e7578 8y agoI see a lot of saves work like this: f = open( "the_file.new.$$" ); write( f, new_contents ); close( f ); rename( "the_file.new.$$", "the_file.new" ) If not implemented like this, then something that attempts to read "the_file.new" may get partial contents, normally truncated along the file system block size. Backups often take place, too, like you mentioned, depending on editor.
- notyourday 8y agoIf you do not rename files while holding their open file descriptors there's no guarantee that you are renaming the file you just wrote to.
- JdeBP 8y agoThere is no guarantee of that if one does retain the open file descriptor.
- notyourday 8y agobefore rename: fstat the fd, get st_dev and st_ino. rename stat the new name. Compare st_dev and st_ino. If the value matches, you renamed the right file. If it does not match, you renamed a wrong file. Without holding the fd, it is impossible to know if it is the right file.
- JdeBP 8y ago"you renamed a wrong file" shows that "there's no guarantee that you are renaming the file you just wrote to".
- notyourday 8y agoIn this case you know that you renamed a wrong file. In the close before rename you do not know that you have renamed a wrong file.
- JdeBP 8y agoKnowing that something bad happened after the fact is not the same as your idea that there's a guarantee that something bad will not happen.
- sneak 8y agoSidecar files might work, and would also be filesystem-portable.
- netsec_burn 8y agoThis is what Mac does to track download locations, if I remember correctly (._file).
- amaccuish 8y agoPlease no. This article is literally "Dotfile madness", don't make it worse! I have to deal already with these on file shares, specifically for Apple: .DS_Store, .Trashes and .AppleDouble, or for Windows: Thumbs.db, $RECYCLE.BIN (for some reason Windows sometimes ignores the fact I've disabled the recycle bin on a share and creates this instead) and desktop.ini. Please don't drop crap around directories where there exist a multitude of tidier alternatives.
- sneak 8y agoHow do you have to “deal with” them? What are the portable tidier alternatives?
- featherrust 8y agoA daemon with a CLI and a programmatic interface, backed by a SQLite store, hooked into Linux audit and perhaps an LD_PRELOAD?
- amaccuish 8y agoBecause when you have multiple OSs accessing the same shared folder, they all create their own crap, which is then visible to the other OSs, and fills up directories with stuff that confuses normal users.
- sneak 8y agoNormal users don’t run multiple OSes.