From: Robert Millan <rmh@aybabtu.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: RFC: Support Linux command line variants in grub-mkconfig
Date: Tue, 19 Jan 2010 23:26:51 +0100 [thread overview]
Message-ID: <20100119222651.GA8599@thorin> (raw)
In-Reply-To: <20100118210353.u0mrvwbf4cw8o48s@legacy.mxes.net>
On Mon, Jan 18, 2010 at 09:03:53PM +0000, Martin Orr wrote:
> I would like to be able to choose between alternative Linux command
> lines in my GRUB menu (specifically, I want a "selinux=0" option, but I
> can imagine that people might want other things). I could add an extra
> script to /etc/grub.d to do this, but then I have to copy the logic in
> 10_linux to detect what kernel versions are available, and they do not
> appear in the correct place in the menu. It would be simpler if you
> could specify variant command lines in /etc/default/grub and have them
> handled automatically in 10_linux.
>
> The attached patch allows (for example) the following configuration in
> /etc/default/grub:
> GRUB_LINUX_VARIANTS="noselinux kms"
>
> GRUB_CMDLINE_LINUX_noselinux="selinux=0"
> GRUB_LABEL_LINUX_noselinux="SELinux disabled"
>
> GRUB_CMDLINE_LINUX_kms="i915.modesetting=1"
> GRUB_LABEL_LINUX_kms="KMS enabled"
>
> This patch is only intended as a demonstration: various details of the
> implementation still need to be sorted out, such as
> internationalization. Suggestions of wildly different
> approaches/configuration interfaces are welcome.
I think this is growing severely overengineered. It is already more
complex than it needs to be.
The scripts in /etc/grub.d *are* config files. There's no reason you
can't edit them to suit your needs.
--
Robert Millan
"Be the change you want to see in the world" -- Gandhi
next prev parent reply other threads:[~2010-01-19 22:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 21:03 RFC: Support Linux command line variants in grub-mkconfig Martin Orr
2010-01-19 22:26 ` Robert Millan [this message]
2010-01-20 11:01 ` Martin Orr
2010-01-20 17:30 ` Joey Korkames
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100119222651.GA8599@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.