| 1 |
On Sun, Oct 09, 2016 at 03:45:11AM +0100, M. J. Everitt wrote: |
| 2 |
> On 09/10/16 00:57, Ben Kohler wrote: |
| 3 |
> > |
| 4 |
> > |
| 5 |
> > On Sat, Oct 8, 2016 at 9:28 AM, Tom H <tomh0665@×××××.com |
| 6 |
> > <mailto:tomh0665@×××××.com>> wrote: |
| 7 |
> > |
| 8 |
> > On Tue, Oct 4, 2016 at 11:34 PM, William Hubbs |
| 9 |
> > <williamh@g.o <mailto:williamh@g.o>> wrote: |
| 10 |
> > > |
| 11 |
> > > You don't have to use grub-mkconfig. You can write |
| 12 |
> > /boot/grub/grub.cfg |
| 13 |
> > > by hand if you want, and it appears that the syntax is documented in |
| 14 |
> > > the grub info pages. |
| 15 |
> > |
| 16 |
> > If you write "/boot/grub/grub.cfg" by hand and run grub-mkconfig by |
| 17 |
> > mistake, you'll wipe out your config. It's safer to write it to |
| 18 |
> > "/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 pass |
| 22 |
> > a -o parameter. If you are "accidentally" running "grub2-mkconfig -o |
| 23 |
> > /boot/grub/grub.cfg" and it catches you by surprise that |
| 24 |
> > /boot/grub/grub.cfg is overwritten, you have bigger problems. |
| 25 |
> > |
| 26 |
> > Let's not make up problems where there are none. |
| 27 |
> > |
| 28 |
> > -Ben |
| 29 |
> +1 |
| 30 |
|
| 31 |
+1000 |
| 32 |
|
| 33 |
William |
Archives