1 |
On Sun, Oct 9, 2016 at 12:05 PM, William Hubbs <williamh@g.o> wrote: |
2 |
> On Sun, Oct 09, 2016 at 03:45:11AM +0100, M. J. Everitt wrote: |
3 |
>> On 09/10/16 00:57, Ben Kohler wrote: |
4 |
>>> On Sat, Oct 8, 2016 at 9:28 AM, Tom H <tomh0665@×××××.com |
5 |
>>> <mailto:tomh0665@×××××.com>> wrote: |
6 |
>>> On Tue, Oct 4, 2016 at 11:34 PM, William Hubbs |
7 |
>>> <williamh@g.o <mailto:williamh@g.o>> wrote: |
8 |
>>>> |
9 |
>>>> You don't have to use grub-mkconfig. You can write |
10 |
>>> /boot/grub/grub.cfg |
11 |
>>>> by hand if you want, and it appears that the syntax is documented in |
12 |
>>>> the grub info pages. |
13 |
>>> |
14 |
>>> If you write "/boot/grub/grub.cfg" by hand and run grub-mkconfig by |
15 |
>>> mistake, you'll wipe out your config. It's safer to write it to |
16 |
>>> "/etc/grub.d/40_custom" and "chmod -x" the other files in |
17 |
>>> "/etc/grub.d/". |
18 |
>>> |
19 |
>>> Well "grub2-mkconfig" by itself doesn't write anywhere unless you pass |
20 |
>>> a -o parameter. If you are "accidentally" running "grub2-mkconfig -o |
21 |
>>> /boot/grub/grub.cfg" and it catches you by surprise that |
22 |
>>> /boot/grub/grub.cfg is overwritten, you have bigger problems. |
23 |
>>> |
24 |
>>> Let's not make up problems where there are none. |
25 |
>> |
26 |
>> +1 |
27 |
> |
28 |
> +1000 |
29 |
|
30 |
I was sharing what I do because I've overwritten a manually-edited |
31 |
grub.cfg by running grub-mkconfig/grub2-mkconfig/update-grub (re |
32 |
grub2-mkconfig, I use grub-mkconfig on Gentoo because I set |
33 |
"-multislot") more than once - and I know other sysadmins who've made |
34 |
the same mistake. |
35 |
|
36 |
You can use exactly the same text in 40_grub that you'd use in |
37 |
grub.cfg and have the latter generated. I don't see why anyone would |
38 |
be opposed to that, unless you hate that tool - and hate's never a |
39 |
good rationale for an MO. |