On Monday, November 05 2001, Christoph Plattner said:
> I have problems to understand your point here.
> If I want to checkout things only once, I use the
> command line interface and never the menu file. Just
> press `c' and you can input a "endless" series of commands
> to test whatever you want
[EMAIL PROTECTED] (Eduardo Ochs) writes:
> Allen Bolderoff wrote:
>
> > I would like to be able to create a file called run.once in
> > /boot/grub/ and have grub try to run it, and remove it after it tries
> > it. (whether it succeeds or fails it should not run it again)
>
> What about having G
Hello !
I have problems to understand your point here.
If I want to checkout things only once, I use the
command line interface and never the menu file. Just
press `c' and you can input a "endless" series of commands
to test whatever you want. The menu is only for the all day
use not to repeat se
Allen Bolderoff wrote:
> I would like to be able to create a file called run.once in
> /boot/grub/ and have grub try to run it, and remove it after it tries
> it. (whether it succeeds or fails it should not run it again)
What about having Grub just change some bytes of this file, without
changin
I would like to be able to create a file called run.once in /boot/grub/ and
have grub try to run it, and remove it after it tries it. (whether it succeeds
or fails it should not run it again)
I cannot find whether grub does or does not do this now, but obvious uses of
such a feature would be
