2009/12/9 Josef Reidinger <jreidinger@suse.cz>:
I think that no one expect, that perl-Bootloader is can parse that configuration file (if it does correct it is halting problem). What is possible to do is parsing /etc/grub/default which is really simple.
As a matter of interest, why does menu.lst file get parsed? I let install create it. Have found an entry using the symlinks work fine, and doesn't need updates to menu.lst on kernel updates. Honestly, most of the reaons I have to go into these files, are to fix mistakes made by the tools software. Things like offering boot option into non-active Windows Recovery partitions on other disk and just cannot be safely booted. On forum there's few users who maintain their own /boot seperate from releases precisely because it is generally less trouble than the auto stuff. May be there's good reason to inspect the file, and modify it? At moment the benefit is not clear to me.? One of the real advantages GRUB brought in 0.97 was wide compatability across distro's and most of the time, solving boot erorrs after an install, was very doable with nothing more than text editor, and occasinally doing a GRUB install by hand. Those file completion options and edit feature of boot line, are widely used by community support. Time I used Live CD and did GRUB re-install using YaST to test it, wasn't really any easier, or less skilled, because I had to understand exactly what it was doing, to know when a version was made that would work. The netconfig stuff, seems to substitute a well understood file, that can partly be dynamically enhanced, but manage to do it in a baffling enough way, that most sysadmins probably just give up and go to static (which is the state once even a small modification is made). Rob -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org