Review Upstart, an init implementation distinct from SysVinit and systemd.
Choose how it determines when services should start and stop.
Which description is correct?
Upstart is event-driven: changes such as filesystems or networking can generate events that trigger job start and stop conditions.
Detailed explanation
Incorrect. MBR partition data does not define service startup.
Incorrect. MBR partition data does not define service startup.
Incorrect. Upstart is not limited to one fixed rc.local script.
Incorrect. Upstart is not limited to one fixed rc.local script.
Correct. Upstart starts and stops jobs in response to system events.
Correct. Upstart starts and stops jobs in response to system events.
Incorrect. An EFI application runs during firmware boot, not as an init implementation.
Incorrect. An EFI application runs during firmware boot, not as an init implementation.
Try it yourself
An example you can run in a temporary verification environment.
command -v initctl || echo 'Upstart is not installed'Expected result
Upstart環境ではinitctlのパス。一般的な現行環境では未導入の表示Key points
- Upstart is event-driven
- It is a user-space init implementation
- Jobs react to system events
Notes
- Environment: Linux / Upstart概念
- 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.