Earlier quoted context omitted.
> Master/slave is a model of asymmetric communication or control where one device or process controls one or more other devices or processes and serves as their communication hub. Exactly. That's why it's a bad choice of name for IDE controllers and for the main boot record, where the master does not control the slave. > inb4 we can sacrifice accuracy over feeling Firmly agree that we should not sacrifice accuracy ov…
Actually it makes sense because the slave always ask the master whether they're currently communicating with the controller. Master boot record also, because the program from the record controls the boot process of associated partitions.
And yes, the master makes no decisions on his own, the master simply sees which of the slaves has indicated that he wishes to be passed control, and then the master passes all control onto that slave and leaves.
I completely forgot what slavery means. I thought that slavery meant that masters controlled the slaves and the slaves didn't have freedom. Thanks for correcting my misunderstanding.