Re: Automatic backup with grub
> On Thursday 27 Oct 2005 17:03, E Leibovich wrote: > > As I'm planning to use it as a recovery console I > > prefer loading linux won't be dependable of loading > > windows, but that it'll be loaded on its on each week > > or each 10 boots. It seems to me that grub requires a > > very small patch in order to make partitionX loaded 10 > > times and then to go back to default - am I correct? > > No, you can use GRUB Legacy's savedefault command. See: > http://www.gnu.org/software/grub/manual/grub.html#Booting-once_002donly > That way requires 10 menu entries for booting Windows. Hi! What have you done at the end? Have you tried my solution (http://lists.gnu.org/archive/html/bug- grub/2005-10/msg00049.html ) or do you prefer the savedefault one (the one above here) because you do not depend on windows xp? adrian15 ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: Scripting support (PATCH)
> > I think also. Because theese modifications are lost after boot they > > are generally modified only to boot one time an OS with specifical > > parameters and you don't need scripts for this. > > Right. The only reason I see for editing the script in general is to > edit some menu generation routine. But that is a very rare case I > think. If it turns out not to be a rare case, we can provide this > feature later on. I'm not quite sure if this discussion will affect my next development of GSD based on grub2 but I'll tell you my opinnion: Grub2 config files should be interpreted as if you were running a bash script. (I actually don't know if it corresponds to approach #1 or #2 or if it hasn't any relation with it) The thing is that for developing GSD easily I will need some menu generation routines... althought... now that I think it better... I can made these routines from normal bash scripts. In conclusion, I'm quite confused but try to help further GSD development. adrian15 Grub Super Disk (GSD) : http://adrian15.raulete.net/grub/ ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: [GRUB1] Accessibility: Add beep support
> Hi, > > I know that no new feature are added to grub1, but this really small > feature (it can be just implemented as "echo ^G") would be _much_ useful > for blind people. Please see details on > https://savannah.gnu.org/bugs/?func=detailitem&item_id=14661 > I proposed a patch adding an "echo" command: > https://savannah.gnu.org/bugs/download.php?item_id=14661&item_file_id=30 > 77 > Could this be commited? > > Regards, > Samuel Hi Samuel, if you happen to build a grub cdrom with this feature in it please send it to me or tell me an url to it. I think that the beep thing should be easily OFF or ON. Why don't you make a beep ON OFF command. My idea for GSD would be default entry (in 5 seconds) activates beep and not default entry do not activates it. (Useful in Offices where there are a lot of people) Then I could assign each GSD option a sound or something. Well, I'm not quite sure. Do you think GSD is useful for a blind person? adrian15 GSD is found at http://adrian15.raulete.net/grub/ ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Fix for strange characters in GRUB 1.91
A picture says a 1000 words : http://www.blastwave.org/dclarke/grub/grub_1.91/day_01/img_1280.jpg I was thinking that perhaps simple line drawing with "-" and "+" could be used for now and that would also work nicely on serial consoles and old DEV VT units that some of us still use on headless hardware. So perhaps a config option in the grub.cfg for charset would be useful. Dennis ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: Fix for strange characters in GRUB 1.91
Dennis Clarke <[EMAIL PROTECTED]> writes: > A picture says a 1000 words : > > http://www.blastwave.org/dclarke/grub/grub_1.91/day_01/img_1280.jpg > > I was thinking that perhaps simple line drawing with "-" and "+" could > be used for now and that would also work nicely on serial consoles and > old DEV VT units that some of us still use on headless hardware. So > perhaps a config option in the grub.cfg for charset would be useful. This was on the pegasos, right? I have a pegasos myself and this is on my todo list. It is just that not the correct characters are used to draw the menu. I suspect this is a bug in the firmware (IOW: it does not use ANSI, which IIRC is in the IEEE 1275 spec.), so we need to come up with a workaround. -- Marco ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: Fix for strange characters in GRUB 1.91
On 11/2/05, Marco Gerards <[EMAIL PROTECTED]> wrote: > Dennis Clarke <[EMAIL PROTECTED]> writes: > > > A picture says a 1000 words : > > > > http://www.blastwave.org/dclarke/grub/grub_1.91/day_01/img_1280.jpg > > > > I was thinking that perhaps simple line drawing with "-" and "+" could > > be used for now and that would also work nicely on serial consoles and > > old DEV VT units that some of us still use on headless hardware. So > > perhaps a config option in the grub.cfg for charset would be useful. > > This was on the pegasos, right? Yes : http://www.blastwave.org/dclarke/grub/grub_1.91/day_01/img_1275.jpg > I have a pegasos myself and this is on my todo list. > It is just that not the correct characters are used > to draw the menu. I suspect this is a bug in the firmware (IOW: it > does not use ANSI, which IIRC is in the IEEE 1275 spec.), so we need > to come up with a workaround. Everything works fine. Just looks wrong. Do you know anything about the possibility for support of a background graphic image also or is that still a major leap with many ramifications ? Dennis ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: Fix for strange characters in GRUB 1.91
Dennis Clarke <[EMAIL PROTECTED]> writes: > Do you know anything about the possibility for support of a background > graphic image also or is that still a major leap with many > ramifications ? For that we need to have framebuffer support. Framebuffer support is planned for GRUB 2. After that new features like a background image can be added. On the pegasos the firmware does not support a framebuffer. But I think if we add an ATI driver, most pegasos users will have a framebuffer. If there is a framebuffer the menu borders will always look nice. -- Marco ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Bison error handling
Hi, Hopefully any of you have either a clue about bison or an idea how to solve this problem. What happens now is that during parsing memory is allocated. If everything is parsed there is a set of malloc'ed memory all pointing to each other, etc. The main problem is in case of a syntax error. In that case all of the state should be released (free all memory structures). But I have no idea how to do that; yyparse just returns an error. I need a way to make bison return a valid structure so I can check if parsing failed and release all of the memory. One solution to this problem is making a big list of all memory allocated while scanning and parsing. When parsing fails you just free all of this memory. Otherwise everything is freed when the datastructures are about to be de-allocated. But I prefer a solution using bison stuff, otherwise I'll just use the solution I described above. -- Marco ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: Bison error handling
Marco Gerards <[EMAIL PROTECTED]> writes: > The main problem is in case of a syntax error. In that case all of > the state should be released (free all memory structures). But I have > no idea how to do that; yyparse just returns an error. I need a way > to make bison return a valid structure so I can check if parsing > failed and release all of the memory. Because the bash people were not able to solve this problem (bash leaks memory when a syntax error occurs!), I think I should assume I can't either. So I just use my other solution for now. :-) -- Marco ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
singleboot
I've been wanting for quite some time a method to be in linux, and reboot into windows for just this one time and keep linux as my default boot. My only solution so far has been to have a boot disk with one grub.conf with windows as the default and the other grub.conf on the hard drive to have linux as the default. Then I push in the disk to go to windows and pop it out to go to linux. I have a two part questions. Is there something that I can write to the grub.conf that will be acted upon once, and then removed? And if not, is anyone opposed to me adding it? Something like a "singleboot = #" directive that would override default and then be removed after grub executes it? Thanks Paul Tarjan ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: Fix for strange characters in GRUB 1.91
On Nov 2, 2005, at 11:19 AM, Marco Gerards wrote: On the pegasos the firmware does not support a framebuffer. But I think if we add an ATI driver, most pegasos users will have a framebuffer. If there is a framebuffer the menu borders will always look nice. Pegasos firmware doesn't provide a framebuffer? That is very ungood. Writing and maintaining our own ATI driver does not sound like fun. We would also need a PCI driver (how will you access config space?) and infrastructure that is otherwise unneeded, such as memory barriers. And *then* we get to talk about initializing and running the video driver itself, which as far as I've seen is not a simple task with modern graphics hardware... -Hollis ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
Re: singleboot
Paul Tarjan wrote: > I've been wanting for quite some time a method to be in linux, and > reboot into windows for just this one time and keep linux as my > default boot. What about : default saved title windows root ... makeactive chainloader +1 title linux root ... kernel ... initrd ... savedefault boot Then you can select windows and it will only boot once in windows (as long as you don't select it again sometime). Another solution would be, if your bios can do that, to define disk boot order as : windows disk linux disk Then if the windows disk is plugged in, it will not even run grub but directly the windows bootloader. If nothing is plugged in place of the windows drive, it will just skip and boot grub on the second. I'm not sure I got your request right : Do you want to "physically" remove the boot entry so no one can use it later ? Do you want it to be 100% automatic (like used as some remote automation) ? Vincent Pelletier signature.asc Description: OpenPGP digital signature ___ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
