27.12.2015 00:17, Robin Schneider пишет: > I am sorry for the misunderstanding. I should have explained the indention > behind my patch a bit better then just linking to another patch which makes > use > of the newly introduced variables by this patch. > > My indented use case is to allow to add options like '--unrestricted' or > '--users "Jane"' to each menuentry generated by grub-mkconfig without altering > the scripts itself.
Oh, no, sorry. CLASS is for adding --class option and --class option is for defining icon used to represent menu entry. Please do not misuse it for something else. I try to understand possible use cases. Please get a look at https://lists.gnu.org/archive/html/grub-devel/2015-05/msg00170.html thread. SUSE has actually implemented my suggestion. This gives us "all menu entries unrestricted" case. Do you really have situation where you need separate category of users that won't have access to CLI but will be the *only* users allowed to select non-default menu entry? Moreover, do you really need to allow different users to boot different categories of menu entries? ... > > BTW: The efi menuentry has the class 'windows'. Is that correct? My patch > assumes that this menuentry is indented for UEFI applications. > Well, so far upstream os-prober only detects Windows on EFI. But yes, SUSE includes additional script. See https://lists.gnu.org/archive/html/grub-devel/2015-12/msg00103.html - does it address your concern?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Grub-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/grub-devel
