Re:Merge tag 'inclusive-terminology' into Linux kernel
by fanf2 on Sunday July 12, 2020 @05:33PM
(#23814939)
This is a really good list of examples, thank you! I have collected a few other cases where master/slave doesn't make much sense:
-- In an active/standby replication setup, the master does all the work and the slave just watches and accumulates the results. This seems backwards.
-- In many replication setups (PostgreSQL and DNS work this way) the replica voluntarily connects to an upstream source. Slavery isn't voluntary.
-- In DNS zone transfers, the downstream replica is in control of replication; the upstream can't tell it to do anything. This is not a master/slave relationship either.
-- In a hardware bus system in which any device can be an initiator and can choose its target device, this isn't a master/slave system because the roles change from one transaction to the next.
-- In an active/standby replication setup, the master does all the work and the slave just watches and accumulates the results. This seems backwards.
-- In many replication setups (PostgreSQL and DNS work this way) the replica voluntarily connects to an upstream source. Slavery isn't voluntary.
-- In DNS zone transfers, the downstream replica is in control of replication; the upstream can't tell it to do anything. This is not a master/slave relationship either.
-- In a hardware bus system in which any device can be an initiator and can choose its target device, this isn't a master/slave system because the roles change from one transaction to the next.
--