Make future normal boots enter a multi-user, network-service state without requiring a GUI.
Do not switch the current target immediately.
Which command is appropriate?
systemctl set-default multi-user.target changes the persistent default target for future boots; it does not isolate the current system immediately.
Detailed explanation
systemctl isolate multi-user.targetIncorrect. isolate changes the current target immediately.
systemctl get-default multi-user.targetIncorrect. get-default displays the setting and does not change it.
systemctl start default.target multi-user.targetIncorrect. start operates on units and the syntax does not set a persistent default.
systemctl set-default multi-user.targetCorrect. set-default multi-user.target changes the default for future boots.
Try it yourself
An example you can run in a temporary verification environment.
systemctl set-default --help 2>/dev/null | head || trueExpected result
set-defaultのhelp。設定変更は行わないKey points
- set-default
- multi-user.target
- Next boot
Notes
- Environment: systemctl helpのみ
- Use read-only commands or a disposable Linux instance when checking boot metadata.
- Exact unit names and command output can vary slightly by distribution.
Foundation review
Place the operation
set-default changes the default target for future boots, while isolate changes the current transaction.
Check the side effect
Verify the resulting default with get-default and avoid isolating a remote host unintentionally.