grub-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RFC] Support menuentry options in simple configuration interface


From: Michael Chang
Subject: Re: [RFC] Support menuentry options in simple configuration interface
Date: Mon, 1 Jun 2015 11:35:49 +0800
User-agent: Mutt/1.5.21 (2010-09-15)

On Sat, May 30, 2015 at 10:39:06AM +0300, Andrei Borzenkov wrote:
> В Tue, 26 May 2015 15:53:14 +0800
> Michael Chang <address@hidden> пишет:
> 
> > This patch provides settings in simple configuration interface that can set
> > common options to menuentry. One of the use cases is specifying the security
> > settings thus it won't be overwritten by grub-mkconfig. For eg.
> > 
> > GRUB_MENU_ENTRY_OPTION_LINUX="--unrestricted"
> > GRUB_MENU_ENTRY_OPTION_OSPROBER="--users user1"
> > 
> 
> I'm not sure. I actually feel like configurations that need detailed
> per user authorizations simply do not fit into simplistic
> grub-mkconfig. Next someone will miss per-menuentry user list.

Thanks for comment. I'm also not sure as per menu entry options not fit
well with global options context provided by simple interface. But from
my understanding, generic options settings maybe more welcome from
upstream POV, so that's why I send it here as RFC patch. :)

> 
> Most common request is really to allow menu boot while restricting
> command line, so I think that adding support for this to grub-mkconfig
> would be fine. 

Yes. We have quite many users request the password protection to work
the same way as legacy grub, that is actually what --unrestricted could
provide them, but they need to manually patch grub scripts to keep their
settings persist as currently distribution tools have no way to
integrate it by lacking of inteface in simple config. We can extend that
on our own, of course, but it seems better to coordinated on upstream if
possible.

How do you think proposed option like this ?

  GRUB_UNRESTRICTED_MENU_ENTRY="true"

to have generated menu-entry with --unrestricted options set?

> Otherwise something more detailed should really be left
> to distribution specific tools or manual creation of grub.cfg.

Agreed.

Thanks,
Michael

> 
> _______________________________________________
> Grub-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/grub-devel



reply via email to

[Prev in Thread] Current Thread [Next in Thread]