We can “ignore” (but dare not “disregard”) that notice.
It serves as a reminder ~~ programs running on linux-based O/Ses expect, sometimes presume, that a case-sensitive aware filesystem is in use.
If you “ignore” case when choosing filenames (mynotes.txt vs myNotes.txt), you’ll eventually encounter problems/confusion. Similarly, if someone {shudder} chooses to use filenames which contain %$# characters, or “space” characters… problems will ensue.
ah, websearch. Top result links to a debian “bug” ticket
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483781
Ignore the warning, it is completely bogus
Ok, I regard it as a being “notice” vs a warning… and I would choose to say “once you understand what it means/implies, disregard it” vs worrying about, how to “(re)solve” it or silence/suppress it.
utf8 is not a recommended IO charset for FAT filesystems
Files being written to FAT32, only ascii characters can be used to represent their filenames. Most of us migrate away from using a FAT32 formatted partition. In the meantime, choose filenames bearing only ascii characters for any files which will be sent to a/the FAT32 storage partition.
___________________________________________
When requesting help, pasting the output from inxi -Fzr command will provide important relevant details:
antiX version//edition ~~ stable vs testing repos ~~ live vs installed vs virtualbox ~~ hardware specs