769
99% of Windows usability issues would be fixed if Windows had the guts to add this button
(media.piefed.social)
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Real answer: it depends.
lsofcan tell you which process has which files open. There's nuance with lazy unmounts and whatnot but that should not be used in most cases.Now in practice you should be wary of one very important thing that changes compared to Windows: Writes are asynchronous on Linux. First the kernel writes to RAM, then it flushes to disk at a later time for performance reasons (this is one of the reasons why writing a bunch of small files is many times faster on Linux than Windows). The upshot is that just because your file copy is "done" doesn't mean you can just yank the USB cable. Always safely unmount before unplugging a storage device on Linux.
Unless I mount it with
sync, which I wish would be default for non-system drives (which are going to be in fstab anyway). I didn't notice any difference, aside from the lack of guessing when the magic is over. 2GiB goes into black hole, now what?You can also use the
synccommand to flush cached writes and wait for completion, but I agree that it is a bit cumbersome.Strongly disagreed. A lot of removable storage benefits very strongly from async writes. The performance benefits are night-and-day and worth the hassle of explicitly unmounting.
I think a better compromise would be to mount non-journaled + removable storage (e.g. vfat USB keys) as sync.