On Friday 13 March 2009 21:23:19 phcoder wrote: > Look at load_env/save_env commands and grub-editenv util
Thanks. Now I really regret that I didn't find those additions earlier. I do not like this implementation for the following reasons: - The saved file is not plain text, unlike GRUB Legacy. This is a bad choice. Please let me know the reason why it must be binary, if any. - The command names are ugly. Why didn't anybody follow Pavel's advise using "env"? - The utility name is also ugly. I like Pavel's suggestion "grub-env". If nobody stops me, I will rewrite it in one week, without caring about backward compatibility. Regards, Okuji > > Yoshinori K. Okuji wrote: > > On Thursday 05 March 2009 05:59:52 Robert Millan wrote: > >> We don't need a complete match of all the GRUB Legacy features in order > >> to migrate. The things I identified as needed for migration in Debian > >> are listed here: > >> > >> http://wiki.debian.org/GrubTransition > >> > >> I think Xen is fixed now though (someone can confirm?). For grub-reboot > >> / savedefault almost all the pieces are there already (thanks to bean). > >> > >> For lock / password we need to agree on whether the proposed approach is > >> acceptable, or otherwise what needs to be done. > > > > I have the same regression problem as Debian, personally. The > > password-based security feature is not quite important for me, but > > savedefault / fallback are critical to use GRUB in a remote environment > > (to upgrade / replace a kernel safely). > > > > So, I am ready for spending time to review any patch about this. Could > > you pinpoint where the "proposed approach" is? > > > > Regards, > > Okuji > > > > > > _______________________________________________ > > Grub-devel mailing list > > Grub-devel@gnu.org > > http://lists.gnu.org/mailman/listinfo/grub-devel _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
