I disagree racb -- using the `.d` directory is generally the approach
CPC has used for all configuration. that way users can easily see what
is package maintained and what is changed in the build process. 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. It seems fairly "normal" for Ubuntu packages to have
$PACKAGE_CONF.d directories to add additional configuration.

I think mkukri has the correct solution. we should add a comment to the
top level file, and ensure all man pages correctly state how the grub
handles the `.d` directory. And any official Ubuntu docs should be
updated. we can't change the history of everyone that's posted online
about every version of Ubuntu, but changing how we configure things
because information online isn't strictly correct (because it predates
grub.d, posters didn't know about grub.d, etc) doesn't seem like strong
reason.

-- 
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