[bug #28642] GRUB2 1.97.1 - Strange behavior after using configfile command

2010-01-20 Thread Vladimir Serbinenko
Update of bug #28642 (project grub): Status:None = Fixed Open/Closed:Open = Closed Release: other = Bazaar - trunk

[bug #28642] GRUB2 1.97.1 - Strange behavior after using configfile command

2010-01-17 Thread Alexey Loukianov
URL: http://savannah.gnu.org/bugs/?28642 Summary: GRUB2 1.97.1 - Strange behavior after using configfile command Project: GNU GRUB Submitted by: lexa2 Submitted on: Sun 17 Jan 2010 08:40:40 AM GMT Category: Booting

[bug #28642] GRUB2 1.97.1 - Strange behavior after using configfile command

2010-01-17 Thread Andreas Born
Follow-up Comment #1, bug #28642 (project grub): That behaviour is caused by a bug in the export behaviour. Therefore the essential variables root and prefix are not properly exported all the time. It's fixed as of revision 1951. You can workaround it by always exporting prefix and root like

[bug #28642] GRUB2 1.97.1 - Strange behavior after using configfile command

2010-01-17 Thread Alexey Loukianov
Follow-up Comment #2, bug #28642 (project grub): Thanks for clarifications. I was unaware about export command. For now I will use it, as it is a bit uncomfortable for me now to use trunk branch in production environment. Will the fixes from the r1951 go to next stable release?

[bug #28642] GRUB2 1.97.1 - Strange behavior after using configfile command

2010-01-17 Thread Alexey Loukianov
Follow-up Comment #3, bug #28642 (project grub): Hmm, still no success: sh:grub set prefix=(hd0,5)/boot/grub sh:grub export prefix sh:grub configfile (hd0,5)/boot/grub/grub.cfg sh:grub set prefix=(hd0,5)/boot/grub sh:grub export prefix sh:grub configfile (hd0,5)/boot/grub/grub.cfg sh:grub set

[bug #28642] GRUB2 1.97.1 - Strange behavior after using configfile command

2010-01-17 Thread Alexey Loukianov
Follow-up Comment #4, bug #28642 (project grub): Figured it out! Main point is that it looks like that: a) export statement should be specified before the set statement for that variable; b) export statement should be supplied no matter is the variable set or not in current configfile context.