Re: grub2-mkconfig doesn't take parameters from /etc/default/grub

[Colin Walters <walters verbum org>]

On Sun, Apr 3, 2016, at 03:10 PM, Chris Murphy wrote:
> On Sun, Apr 3, 2016 at 9:07 AM, Li, Chengyuan <chengyli ebay com> wrote:
> > Hi,
> >
> >
> >
> > I’m using Atomic fedora 23, and try to add extra Linux cmdline parameters in
> > /etc/default/grub, e.g.

Yeah, this is a bug.

> https://bugzilla.redhat.com/show_bug.cgi?id=1267956

Not sure how that bug is related.

> But the upstream bug is closed as not a bug. So I don't know what to
> make of that when user space tools fail but it's not a bug.
>
> The work around I'm using is just make sure the all the .conf files in
> /boot/loader have the change you want made already; it seems like this
> is just being copied when making the .conf file for a new tree.

This is a bug, we need an administrator-friendly way to manipulate
the kernel arguments for sure.  And it is definitely confusing that /etc/default/grub
exists on ostree systems but we don't respect it.

I think the best fix here is:

# ostree admin set-kargs  (like the existing ostree admin instutil set-kargs but would work interactively)

And we teach Anaconda to delete /etc/default/grub for rpmostreepayload systems?

In the meantime, it does work to just `vi /boot/loader/foo.conf`, but I know this
isn't really documented well and doesn't have a lot of historical momenum
behind it.

Maybe instead of deleting /etc/default/grub we replace it with a document
that points to `ostree admin set-kargs`.