Comment 4 for bug 1635181

On Fri, Oct 21, 2016 at 6:10 AM, Mark Shuttleworth <
<email address hidden>> wrote:

> On 20/10/16 17:30, Ryan Harper wrote:
> > 3) to avoid upgrade issues, curtin did not modify /etc/default/grub
> > directly
>
> Does this avoid upgrade issues? Or does it make them inevitable?
> Essentially what you're saying is "we don't want the user to be asked a
> question during an upgrade". That's fine. But if there is stuff in
>

That's the upgrade issue that I'm aware of which was the reason for the
change. Details are here:

https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/901600

> /etc/default/grub.d/ then whatever we change during upgrade in
> /etc/default/grub is operating under the *delusion* that it is in
> control. Therefor, all we're doing is making it harder for people to
> *know* what the situation is, *especially* during an upgrade.
>

> Or have I misunderstood what's going on?
>

Your understanding is correct. It currently _is_ harder to know what's
going
on because the current behavior is NOT documented in the configuration files
themselves.

Comments in the bug I linked to above confirm that as do other bugs being
filed related to user confusion.

> Debian config file handling has this as a base problem, I accept that's
> not a problem we created, but we need to grapple with it properly, not
> kick the can elsewhere.
>

Agreed.

> --
> You received this bug notification because you are subscribed to curtin.
> Matching subscriptions: curtin-bugs-all
> https://bugs.launchpad.net/bugs/1635181
>
> Title:
> Curtin sneaks config into /etc/default/grub.d/
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1635181/+subscriptions
>