Duh. Sorry about that. I was getting "unknown command" errors. I'll try to be a
bit more investigative in the future.
--S
Quoting Vladimir 'phcoder' Serbinenko, who wrote the following on Wed, 2...:
On Wed, Sep 2, 2009 at 7:04 AM, Seth Goldberg<seth.goldb...@sun.com> wrote:
Hi,
Has the idea come up of having a file that maps commands to module names
along with the required code to autoload the corresponding module(s) when
the corresponding commands are used (something like:
Actually it's already implemented. Look a commands.lst and normal/dyncmd.c
<commandname>: <modulename>.mod [, <modulename>.mod ...]
i.e.:
multiboot: multiboot.mod
linux: linux.mod
...
\
(Obviously, we could also have the convention of trying to load
<commandname>.mod, but having an explicit mapping would remove the overhead
of trying to find a module that doesn't exist, and loading multiple modules
may not be needed as well).
--S
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
--
Regards
Vladimir 'phcoder' Serbinenko
Personal git repository: http://repo.or.cz/w/grub2/phcoder.git
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
