1 |
William Hubbs posted on Sun, 09 Oct 2016 11:05:43 -0500 as excerpted: |
2 |
|
3 |
> On Sun, Oct 09, 2016 at 03:45:11AM +0100, M. J. Everitt wrote: |
4 |
>> On 09/10/16 00:57, Ben Kohler wrote: |
5 |
>> > |
6 |
>> > |
7 |
>> > On Sat, Oct 8, 2016 at 9:28 AM, Tom H <tomh0665@×××××.com |
8 |
>> > <mailto:tomh0665@×××××.com>> wrote: |
9 |
>> > |
10 |
>> > On Tue, Oct 4, 2016 at 11:34 PM, William Hubbs |
11 |
>> > <williamh@g.o <mailto:williamh@g.o>> wrote: |
12 |
>> > > |
13 |
>> > > You don't have to use grub-mkconfig. You can write |
14 |
>> > > /boot/grub/grub.cfg by hand if you want |
15 |
>> > |
16 |
>> > If you write "/boot/grub/grub.cfg" by hand and run grub-mkconfig |
17 |
>> > by mistake, you'll wipe out your config. It's safer to write it |
18 |
>> > to "/etc/grub.d/40_custom" and "chmod -x" the other files in |
19 |
>> > "/etc/grub.d/". |
20 |
>> > |
21 |
>> > Well "grub2-mkconfig" by itself doesn't write anywhere unless you |
22 |
>> > pass a -o parameter. If you are "accidentally" running |
23 |
>> > "grub2-mkconfig -o /boot/grub/grub.cfg" and it catches you by |
24 |
>> > surprise that /boot/grub/grub.cfg is overwritten, you have bigger |
25 |
>> > problems. |
26 |
>> > |
27 |
>> > Let's not make up problems where there are none. |
28 |
>> > |
29 |
>> +1 |
30 |
> |
31 |
> +1000 |
32 |
|
33 |
What I was worried most about was some so-called "helper" app deciding it |
34 |
could run grub-mkconfig for me. |
35 |
|
36 |
Anyway, the functionality isn't going to be used, so best security |
37 |
practices say the executable shouldn't even be on the system. |
38 |
|
39 |
If it's not there, it can't be run, a great solution to both the above. |
40 |
=:^) |
41 |
|
42 |
Tho the point that it needs a -o parameter to write somewhere is a good |
43 |
one as well, certainly ameliorating the problem to some extent. =:^) |
44 |
|
45 |
-- |
46 |
Duncan - List replies preferred. No HTML msgs. |
47 |
"Every nonfree program has a lord, a master -- |
48 |
and if you use the program, he is your master." Richard Stallman |