…what else could fool me? I see this other thread:
But hasn’t been updated since 2015.
So per the first thread:
Linux disk cache might make you think a write operation has been completed when it does not, specially on slow USB drives.
Let me add:
In many file managers disk operations are not atomic and interrupting a copy might leave half copied files. Some file managers have an option to mitigate that -I learned it asking on this forum-.
By default when you want to use ARP to know the IP associated to a MAC address all interfaces can answer regardless of which one owns the IP, sometimes giving you the wrong answer. You can set a different value to arp_ignore/arp_announce in /stc/sysctl.conf to fix that.
At least on Debian about a year ago the installer created a profile for the first wired connection named “Wired connection 1” which should be limited to that interface. Instead the profile is kind of generic and applies to all new network interfaces! Since by default multiple connections cannot share a single profile, the newly added one does not have any connectivity.
What other small quirks that might drive you nuts if you don’t know them have you found out?
“In Windows, write caching is disabled for USB drives by default, except for those using the NTFS format.” So, any USB.stick that has more than 4 gigs of space. Unless you use ExFAT instead.
So write-caching, files not being completely written might happen on Windows too.
On Linux (and I assume Windows), this is why you “Safely remove” USB-stick before unplugging it. You can also run “sync” in terminal on Linux. Once that returns, it should be done, you can unplug the stick.
There’s lots of quirks, even between distros. A small but significant difference is Fedora vs just about everything else. Fedora uses /usr/libexec, others use /usr/lib. Took me 2 days to realise on my custom install of MangoWM + Noctalia because PolKit would not launch/work. So I couldn’t authenticate when the OS asked for password. Well, was supposed to IIRC.
Docker tends to default to Iptables. Ran into this today again. Other Docker containers worked just fine but Joplin server self-hosted would not. I could not connect to admin-interface. Until I changed it to nftables in Docker’s daemon.json. A file which, btw, does not exist by default on Garuda. Had to create the directory and the file. /etc/docker/daemon.json. With the contents:
{
“firewall-backend”: “nftables”
}
Restarted Docker afterwards.
What seems to get most on Linux vs Windows is copy/paste in terminal. On Linux it is Shift+Ctrl+C/V. Might be middlemouse-button too, to paste. Ctrl+C quits/kills a command.