| Summary: |
grub: need keep 40_custom blank |
| Product: |
[Build System, Metadata & Runtime] OE-Core
|
Reporter: |
Robert Yang <liezhi.yang> |
| Component: |
core | Assignee: |
Robert Yang <liezhi.yang> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
|
| Severity: |
normal
|
|
|
| Priority: |
Medium
|
CC: |
koen, mark.hatle, meta.mr.watcher, meta.watcher, Qi.Chen, sgw
|
| Version: |
1.7 | |
|
| Target Milestone: |
1.7 M1 | |
|
| Hardware: |
x86 | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|
Verified:
|
|
Documentation change:
|
No (bug/feature does not impact docs)
|
We have this in recipes-bsp/grub/grub/40_custom: #!/bin/sh exec tail -n +3 $0 # This file provides an easy way to add custom menu entries. Simply type the # menu entries you want to add after this comment. Be careful not to change # the 'exec tail' line above. menuentry "Linux" { set root=(hd0,1) linux /vmlinuz root=__ROOTFS__ rw __CONSOLE__ __VIDEO_MODE__ __VGA_MODE__ quiet } These lines are for initrdscripts/files/init-install.sh, the side effect is that it would make the target's grub-mkconfig doesn't work well since the 40_custom will be installed to /etc/grub.d/40_custom, the grub-mkconfig will run the 40_custom, and there will always be a 'menuentry "Linux"' menu in grub.cfg no matter it is valid or not, we need do this in init-install.sh rather than grub to fix the problem.