| 1 |
On Thu, May 21, 2015 at 4:33 AM, Neil Bothwick <neil@××××××××××.uk> wrote: |
| 2 |
> That's a GRUB1 file, GRUB2 uses a different syntax so your first entry |
| 3 |
> would become |
| 4 |
> |
| 5 |
> menuentry "Gentoo Linux 3.18.12" { |
| 6 |
> linux /boot/kernel-x86_64-3.18.12-gentoo root=/dev/md5 net.ifnames=0 irqpoll |
| 7 |
> } |
| 8 |
|
| 9 |
Correct. |
| 10 |
|
| 11 |
> |
| 12 |
> Also, you need to copy 40_custom and then add your lines to that. This is |
| 13 |
> because files in /etc/grub.d are executed, so it needs to be a shell |
| 14 |
> script. |
| 15 |
> |
| 16 |
|
| 17 |
If you're just going to hand-edit your config file, I don't see much |
| 18 |
point in sticking this stuff in /etc/grub.d. Just hand-edit your |
| 19 |
config file and forget about grub2-mkconfig. |
| 20 |
|
| 21 |
40_custom is more about adding one more entry to an auto-generated |
| 22 |
menu, such as having an entry for booting another OS, or a rescue CD |
| 23 |
image, or whatever. |
| 24 |
|
| 25 |
-- |
| 26 |
Rich |
Archives