Re: non-interactive usage

[Narayan Desai]

OK. To get into painful detail, we have a daemon that watches serial
console logfiles and triggers scripts based on text strings it sees on
the console of particular machines. So it is pretty straight-forward
to make this daemon run a grub module to generate the proper boot
commands to setup the system properly. The problem is that this
daemon isn't stateful, so the first grub prompt triggers the script,
and then the commands are sent down the serial line, and then prompt
for the second grub line (in this case the boot line) triggers another
grub module run. So I am trying to fit all of the commands into a
single line so as to not double trigger a module run. (I know that
this is sub-optimal, but I could prefer not to have to fix this daemon
to make it stateful) 

It certainly sounds like what I want to do is impossible from the
docs, so I am curious about one other detail: if I were to set things
up in the way i described above, and commands were issues twice to the
machine (in a non-interleaved fashion; the daemon is single-threaded,
so only one module is run at a time) would commands be ignored by the
machine in the time between the grub boot command and the time the
kernel configures serial support (This is linux if it matters)
thanks for all of your help in this.
 -nld