- cross-posted to:
- programmer_humor@programming.dev
- cross-posted to:
- programmer_humor@programming.dev
- Same when you try to remove an external drive. - And on Kubuntu it’s always endlessly writing to the drive, but it doesn’t say what process is doing it and there’s no way to figure it out. - To be fair, this happens to me also in Debian Gnome, but very very rarely. On Windows, it keeps me from ejecting the drive until after I try it 4-5 times. Every time. In any case, lsof can help identify the culprit. - lsof | grep DRIVENAMEshould give which program is keeping it.- That didn’t come up in my searching, I’ll try it next time. 
 
 
 
- On Linux it just sticks around as a ghost until it’s closed. Less noticeable but frustrating in its own way. - Allows the very important ‘overwrite files while they’re open’ functionality used during update. Write all the new files for a service then restart it. No need to reboot the whole machine for that. - Looking at you, Windows, and your bullshit scheduled reboots. 
 
- install powertoys, there’s an addon called file locksmith that does exactly that - Sure, that ‘fixes’ it. The real question is, if that information is retrievable anyways… Why is it not a built-in part of windows. You get the error popup and it should just show two buttons: "Ok and “Find which program is using it” - Powertoys is basically all the things the engineers internally couldn’t stand not having but the business won’t allow to be officially integrated. - Well for a ton of the more niche tools I can see why they wouldn’t integrate them. I say that even though I can’t live without them at this point haha. - But file locksmith, env variable viewer, basic stuff like that… Really should be built-in 
 
 
 




