On a SysVinit system, init has started and must launch services for the configured runlevel.
Use the traditional initialization scripts.
Which mechanism is central to this startup?
SysVinit uses configuration and runlevels to execute service start and stop scripts under /etc/init.d/ in the configured order.
Detailed explanation
Incorrect. EFI variables are part of firmware boot configuration, not SysVinit service startup.
Incorrect. EFI variables are part of firmware boot configuration, not SysVinit service startup.
Correct. Runlevel links and /etc/init.d scripts provide the traditional service startup mechanism.
Correct. Runlevel links and /etc/init.d scripts provide the traditional service startup mechanism.
Incorrect. default.target is a systemd target concept.
Incorrect. default.target is a systemd target concept.
Incorrect. Kernel modules do not start all user-space daemons.
Incorrect. Kernel modules do not start all user-space daemons.
Try it yourself
An example you can run in a temporary verification environment.
test -d /etc/init.d && find /etc/init.d -maxdepth 1 -type f | head || echo 'SysVinit scripts are not installed'Expected result
互換スクリプトの一覧、または未導入の表示Key points
- init.d contains service scripts
- Runlevels select start and stop actions
- This differs from systemd units
Notes
- Environment: Linux / SysVinit概念
- 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.