1 |
On Fri, Feb 17, 2017 at 4:08 AM, Neil Bothwick <neil@××××××××××.uk> wrote: |
2 |
> On Thu, 16 Feb 2017 19:44:47 -0800, Ian Zimmerman wrote: |
3 |
>>> |
4 |
>>> grub-mkconfig -o /boot/grub/grub.cfg |
5 |
>>> |
6 |
>>> Even a large proportion of Ubuntu users would be able to manage |
7 |
>>> without it. |
8 |
>> |
9 |
>> I think the reason it exists is that it had to do a bit more with legacy |
10 |
>> GRUB. |
11 |
> |
12 |
> That makes sense. |
13 |
|
14 |
Debian and Ubuntu have a few update-* commands that are mostly run by |
15 |
maintainer scripts, update-alternatives, update-grub, |
16 |
update-initramfs, update-locale, update-passwd, update-rc.d, ... |
17 |
|
18 |
Most users weren't aware of grub1's update-grub because it was run |
19 |
from the kernel postinst script and it wouldn't wipe out user changes |
20 |
because there was a note in menu.lst not to modify entries within the |
21 |
"AUTOMAGIC" comments. |
22 |
|
23 |
When grub2 came along, update-grub was turned into a call to grub-mkconfig... |