I've managed to get it working now by a manual edit, what is happening is, your script does change the default os number, but it puts three dashes in front of the number so grub cant read it, so it just defaults to the standard default,i removed the dashes and all is fine.
Ah I see - well, obviously if there's a problem with GrubEd on Gutsy I'll do my best to fix it, so thanks for the heads up. If I can track down the problem I'll release a fix for it as soon as I can
I too have this problem with Gutsy, but in my case no matter which OS is selected as the default, GrubEd replaces the current NUMBER with -1. So the next attempt to set the OS gives us --1 and so on. Just thought that this might give you a clue when you get around looking at the problem.
Good luck in sorting this out I've used GrubEd with Feisty and found it good - it would be great to have it for Gutsy too, particularly for less computer literate users.
Thanks Tomosaur I've been having a look at both the Gutsy produced grub menu.lst and your GrubEd script. Will also need a Feisty menu.lst to compare - with an initial look it seems much the same.
Whitespace can be a headache at times!! Some years ago when I was programing and taking input from other systems, I found it useful to parse the text to remove excess whitespace first.
Good luck with GrubEd - great stuff
I've found an interesting thing... If I edit the Feisty grub menu.lst while running Gutsy, it fails in the same way. Editing the Gutsy menu.lst in Feisty works fine. So it seems it's not a difference in the menu.lst but in the implementation of grep in Gutsy.
Last edited by Gina; December 2nd, 2007 at 04:33 PM.