| 1 |
On Thu, May 21, 2015 at 8:10 AM, Neil Bothwick <neil@××××××××××.uk> wrote: |
| 2 |
> On Thu, 21 May 2015 12:44:42 +0100, Peter Humphrey wrote: |
| 3 |
> |
| 4 |
>> > If you're just going to hand-edit your config file, I don't see much |
| 5 |
>> > point in sticking this stuff in /etc/grub.d. Just hand-edit your |
| 6 |
>> > config file and forget about grub2-mkconfig. |
| 7 |
>> |
| 8 |
>> You mean: copy grub.conf to grub.cfg and change its syntax to suit |
| 9 |
>> GRUB2? I'm well used to hand editing grub.conf, so it'll be no big |
| 10 |
>> change to operate on grub.cfg instead. I can cope with that. |
| 11 |
> |
| 12 |
> You'd need to run grub2-mkconfig once, to generate a grub.cfg to which |
| 13 |
> you can add your entries. |
| 14 |
> |
| 15 |
|
| 16 |
It is just a text file. I think the only challenge is that there |
| 17 |
aren't a lot of decent examples floating around because all the docs |
| 18 |
tend to say to run grub2-mkconfig. I found this extremely frustrating |
| 19 |
when I first migrated to grub2. In my case grub2-mkconfig wouldn't |
| 20 |
find anything, since it looks at filenames and my kernels/initramfs |
| 21 |
files didn't follow any standard naming convention (they were not |
| 22 |
installed using make install). These days I do use grub2-mkconfig. |
| 23 |
|
| 24 |
That said, the canned config files output by grub2-mkconfig are a bit |
| 25 |
smarter about auto-setting things like the grub2 root. I wouldn't |
| 26 |
bother putting anything in 40_custom though. Just run it once and |
| 27 |
edit the file. |
| 28 |
|
| 29 |
-- |
| 30 |
Rich |
Archives