> I don't think the suggestion that CPC change that general guidance
because grub.d is less well known that other `.d` directories is a
strong rationale.

While .d directories are a common pattern and CPC should use them where
these are provided, that fundamentally has to be considered on a
package-by-package basis. You must adapt to the packaging provided and
cannot simply expect or demand to use .d where that causes issues and
refuse to budge otherwise.

In the general case, .d directories would override things that are
default because the underlying implementation makes them the default. In
contrast, using .d directories to override what is specified in other
configuration files in /etc by default makes for confusion and should be
avoided. We've already seen that with sshd_config.d/, where file
ordering collides with configuration syntax rules making some .d-based
overrides impossible (that case will hopefully be resolved by moving
more things into .d over time).

In this case, grub packaging provides a default in /etc/default/grub
leads to confusing duplication when overridden by .d, and I can't see
that changing.

In this case, the precise mechanism we need looks like it's already
provided using a well-established debconf mechanism, and if not, appears
to be able to be trivially extended to do so. That would resolve this
bug and all user confusion. Let's not use dogmatic adherence to one
specific pattern to excuse fixing the issue with the appropriate
mechanism.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812752

Title:
  UX: changing GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub has no
  effect in cloud images

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1812752/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to