I think I should have told you my idea, before you have finished the
work. The way you want is quite similar to the diskless images. In the
diskless images (pxegrub and nbgrub), you can specify a configuration
file on a remote host dynamically using the tag 150, so you can
control client machines completely from the remote host. Therefore,
what you need here is not an ad hoc environment variable, but the
functionality that loads a remotely defined configuration file even in
stage2. To do that, you just need to add an option to bootp/dhcp, so
that bootp/dhcp overwrites the name of a configuration file and loads
the file, just like what pxegrub/nbgrub does.
For example, add --with-configfile into bootp, and build your GRUB
images, like this:
$ cat <<EOF >embedded_configfile
bootp --with-configfile
$ ./configure --enable-card --enable-preset-menu=embedded_configfile
Or build GRUB normally and put the file "embedded_configfile" in a
local disk as the default configuration file. Then, you can control
what your client machines do from a remote host, as long as your
BOOTP/DHCP server is set up properly. IMO, this is a cleaner way,
since this doesn't break any of GRUB paradigms.
Okuji
_______________________________________________
Bug-grub mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-grub
