LX0-103 · Question #137
After modifying GNU GRUB's configuration file, which command must be run for the changes to take effect?
The correct answer is D. No action is required. GRUB reads its configuration file at boot time, so edits to grub.cfg or menu.lst take effect automatically on the next boot without any reload command.
Question
After modifying GNU GRUB's configuration file, which command must be run for the changes to take effect?
Options
- Akill -HUP $(pidof grub)
- Bgrub-install
- Cgrub
- DNo action is required
How the community answered
(21 responses)- B5% (1)
- C5% (1)
- D90% (19)
Why each option
GRUB reads its configuration file at boot time, so edits to grub.cfg or menu.lst take effect automatically on the next boot without any reload command.
GRUB is not a running process, so there is no PID for pidof to find and kill -HUP has no effect on bootloader configuration.
grub-install writes the bootloader to the MBR or a boot partition - it does not reload or apply configuration file changes.
There is no 'grub' command that reloads or applies changes to the GRUB configuration file at runtime.
GRUB is a bootloader, not a running daemon or service. It parses its configuration file (grub.cfg for GRUB2, or menu.lst/grub.conf for GRUB Legacy) each time the system boots, so any saved edits are automatically applied at the next boot with no intermediate command required.
Concept tested: GRUB bootloader configuration file reload behavior
Source: https://www.gnu.org/software/grub/manual/grub/grub.html
Topics
Community Discussion
No community discussion yet for this question.