From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1JAxjy-0000BZ-TC for mharc-grub-devel@gnu.org; Fri, 04 Jan 2008 20:22:22 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JAxjx-00008D-4G for grub-devel@gnu.org; Fri, 04 Jan 2008 20:22:21 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JAxjw-00006c-Gs for grub-devel@gnu.org; Fri, 04 Jan 2008 20:22:20 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JAxjw-00006J-63 for grub-devel@gnu.org; Fri, 04 Jan 2008 20:22:20 -0500 Received: from ns39764.ovh.net ([91.121.25.85] helo=nexedi.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JAxjv-0004dk-TP for grub-devel@gnu.org; Fri, 04 Jan 2008 20:22:20 -0500 Received: from [10.8.0.46] (unknown [10.8.0.46]) by nexedi.com (Postfix) with ESMTP id F0B753EB24 for ; Sat, 5 Jan 2008 02:27:08 +0100 (CET) From: "Yoshinori K. Okuji" Organization: enbug.org To: The development of GRUB 2 Date: Sat, 5 Jan 2008 02:22:17 +0100 User-Agent: KMail/1.9.4 References: <20080103150311.GA20790@thorin> <20080103150558.GA21928@thorin> In-Reply-To: <20080103150558.GA21928@thorin> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200801050222.18057.okuji@enbug.org> X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) Subject: Re: variable hooks & global variables X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jan 2008 01:22:21 -0000 On Thursday 03 January 2008 16:05, Robert Millan wrote: > On Thu, Jan 03, 2008 at 04:03:11PM +0100, Robert Millan wrote: > > When you set a variable hook (grub_register_variable_hook), this hook > > isn't preserved after someone (e.g. configfile command) opens a new > > context (grub_env_context_open), unless the variable has been set as > > global (grub_env_export). > > > > Is this what we want? > > > > The only current user of variable hooks is "root" variable, and that hook > > contains a sanity check that seems to be more suitable for global scope. > > > > The color-related variables for which I wanted to add hooks would also > > like to keep their hooks across contexts. > > > > One option is to export these variables, or to modify > > grub_env_context_open() to preserve hooks as well as exported variables. > > I'm more inclined for the latter. > > > > Comments? > > Erm, ignore the part about global variables. Exporting them doesn't help: > > for (var = context->prev->vars[i]; var; var = var->next) > { > if (var->type == GRUB_ENV_VAR_GLOBAL) > if (grub_env_set (var->name, var->value) != GRUB_ERR_NONE) > { > grub_env_context_close (); > return grub_errno; > } > } > > So, we just preserve hooks ? Global variables should preserve hooks. This is a bug. Local ones should not. If you want to have a variable to be inherited, you must make it global. Okuji