3 ms·

> [Jenkins] "Coordinator/worker" works well here. Agreed, although my mind immediately went to "manager" and how that is one of the most useless names. See e.g

> [Jenkins] "Coordinator/worker" works well here. Agreed, although my mind immediately went to "manager" and how that is one of the most useless names. See e.g. https://stackoverflow.com/questions/1866794 https://stackoverflow.com/questions/1866794. Need to be careful with this type of naming. > [MySQL] "Primary/replica" works well here. Agreed. > [ZFS] Terms that would make sense include things like "bond device/bonded member" (the members being bonded to each other), "logical volume/physical volume", etc. In this pull request they seem to use "dependency." These names more than double number of syllables/characters, which will severely hamper adoption. I find "dependency" to be a bad descriptor for individual components fully making up a whole, but I expect that the ZFS people deliberated over that name and that my extremely limited familiarity with the topic(s) is the reason why I find "dependency" weird. > [disk drives] "Primary/secondary" works well here. Agreed. > [pseudoterminals] I don't know of a standard term here, but I'd sort of suggest "monitor" and "application" (or perhaps "monitor" and "session" if you want to keep the initials). I would strongly discourage overloading the meaning of "monitor" in the context of terminals. Otherwise, you all but guarantee confusion.

geofft 6y ago
For bonding devices I usually say "bond" and "member" at work, or things like "I added eth4 to bond0," which seems at least as clear as "I enslaved eth4 to bond0". For disks I usually write and say "LV" and "PV" for LVM and "LD" and "PD" for MegaRAID, which matches what the respective CLIs use. Re terminals, it's the end that's connected to the monitor (or terminal emulator), just like the other end is connected to the application/session. There aren't two actual pseudoterminals in any sense, just two views of the same thing, so the idea of "the pty master"/"the pty slave" doesn't quite make sense unless you're very careful to realize you're talking about the open FD and not the actual thing. I'd probably say something like "the monitor end" and "the session end" (and continue to abbreviate them as "ptm"/"pts").

geofft 6y ago

For bonding devices I usually say "bond" and "member" at work, or things like "I added eth4 to bond0," which seems at least as clear as "I enslaved eth4 to bond0". For disks I usually write and say "LV" and "PV" for LVM and "LD" and "PD" for MegaRAID, which matches what the respective CLIs use. Re terminals, it's the end that's connected to the monitor (or terminal emulator), just like the other end is connected to the application/session. There aren't two actual pseudoterminals in any sense, just two views of the same thing, so the idea of "the pty master"/"the pty slave" doesn't quite make sense unless you're very careful to realize you're talking about the open FD and not the actual thing. I'd probably say something like "the monitor end" and "the session end" (and continue to abbreviate them as "ptm"/"pts").