So the Linux kernel will no longer use the terminology 'blacklist' or 'slave'. The problem from changes like this arise from user and sysadmin scripts that rely on the terms for functionality. If a script uses blacklist to auto lock a process and now that term changes, older systems that rely on that (think bank, insurance company and government mainframes) will crash.
The term slave / master for drive assignment is more a semantic thing and can easily be switched to parent / child or some such without much hassle, but older BIOS chips aren't going to get the message, and thus slave / master will be here to stay for decades to come.
Finally, there is now a call to remove the terms blackhat, whitehat and man in the middle from the hacking community. Terms which don't even have a historical significance other than old cowboy westerns.
These changes are multi level and the impact will be cascading. When this stuff starts hitting the science and programming community, it's ...
BLM Effect: Linux Kernel to Adopt an Inclusive Code Language, Blocks Terms like Blacklist and SlaveAfter the Black Lives Matter movement, Linux Kernel developers are also implementing inclusive coding guidelines by dropping words like blacklist and slave....