Desktop applications and system services exchange method calls and signals through a common message bus.
This mechanism does not directly create device nodes.
Which mechanism is appropriate?
D-Bus mediates interprocess messages between clients and services through system and session buses.
Detailed explanation
/etc/rpm.confIncorrect. udev manages device nodes and links in response to device events.
Incorrect. udev manages device nodes and links in response to device events.
/var/lib/yum.confIncorrect. sysfs exposes kernel objects and device attributes.
Incorrect. sysfs exposes kernel objects and device attributes.
/etc/yum.repos.d/main.repoIncorrect. procfs exposes process and kernel state through virtual files.
Incorrect. procfs exposes process and kernel state through virtual files.
/etc/yum.confCorrect. D-Bus brokers method calls and signals between processes.
Correct. D-Bus brokers method calls and signals between processes.
Try it yourself
An example you can run in a temporary verification environment.
printf '%s
' /etc/yum.confExpected result
/etc/yum.confKey points
- D-Bus is an IPC message bus
- System and session buses differ
- It is distinct from udev
Notes
- Environment: YUM設定構造の確認のみ
- Command output formatting can vary slightly by distribution or tool version.
- Run the example in a temporary directory or process when possible.
Foundation review
Read the scope first
Check whether the command acts on the current shell, a new process, an existing process, or a file.
Verify the observable result
Use the supplied command and compare the output with the expected result.