| 1 |
On Tue, 2016-10-18 at 12:45 -0400, Tom H wrote: |
| 2 |
> On Tue, Oct 11, 2016 at 10:54 AM, M. J. Everitt <m.j.everitt@×××.org> wrote: |
| 3 |
> > |
| 4 |
> > On 11/10/16 15:42, Tom H wrote: |
| 5 |
> > > |
| 6 |
> > > |
| 7 |
> > > You can use exactly the same text in 40_grub that you'd use in |
| 8 |
> > > grub.cfg and have the latter generated. |
| 9 |
> > |
| 10 |
> > That's a useful tit-bit .. thanks! |
| 11 |
> |
| 12 |
> You're welcome. |
| 13 |
> |
| 14 |
> I doubt that the grub developers intended 40_custom to be the only |
| 15 |
> "/etc/grub.d/" file to be executed but it's practical for generating a |
| 16 |
> simple grub.cfg. This is what I use in a Debian VM: |
| 17 |
> |
| 18 |
|
| 19 |
We still use grub-1 and I really like the automatic generation of new grub |
| 20 |
menu entries using genkernel --bootloader=grub, does this work with grub2 as well? |
| 21 |
|
| 22 |
Jocke |
Archives