| 1 |
On 09/10/16 00:57, Ben Kohler wrote: |
| 2 |
> |
| 3 |
> |
| 4 |
> On Sat, Oct 8, 2016 at 9:28 AM, Tom H <tomh0665@×××××.com |
| 5 |
> <mailto:tomh0665@×××××.com>> wrote: |
| 6 |
> |
| 7 |
> On Tue, Oct 4, 2016 at 11:34 PM, William Hubbs |
| 8 |
> <williamh@g.o <mailto:williamh@g.o>> wrote: |
| 9 |
> > |
| 10 |
> > You don't have to use grub-mkconfig. You can write |
| 11 |
> /boot/grub/grub.cfg |
| 12 |
> > by hand if you want, and it appears that the syntax is documented in |
| 13 |
> > the grub info pages. |
| 14 |
> |
| 15 |
> If you write "/boot/grub/grub.cfg" by hand and run grub-mkconfig by |
| 16 |
> mistake, you'll wipe out your config. It's safer to write it to |
| 17 |
> "/etc/grub.d/40_custom" and "chmod -x" the other files in |
| 18 |
> "/etc/grub.d/". |
| 19 |
> |
| 20 |
> Well "grub2-mkconfig" by itself doesn't write anywhere unless you pass |
| 21 |
> a -o parameter. If you are "accidentally" running "grub2-mkconfig -o |
| 22 |
> /boot/grub/grub.cfg" and it catches you by surprise that |
| 23 |
> /boot/grub/grub.cfg is overwritten, you have bigger problems. |
| 24 |
> |
| 25 |
> Let's not make up problems where there are none. |
| 26 |
> |
| 27 |
> -Ben |
| 28 |
+1 |
Archives