Alex Roman escribió:
On 12/06/07, adrian15 <[EMAIL PROTECTED]> wrote:
Once I write a new command like map.c or pause.c how am I
supposed to
add it to the standard grub?
Should I write the makefiles manually?! or should I use some
of the .sh
files at the grub2 source code root
Alex Roman escribió:
On 12/06/07, adrian15 <[EMAIL PROTECTED]> wrote:
Once I write a new command like map.c or pause.c how am I
supposed to
add it to the standard grub?
Should I write the makefiles manually?! or should I use some
of the .sh
files at the grub2 source code root
Robert Millan escribió:
Look at how other commands are hooked in. rgrep(1) is your friend :-)
I already did that and it seemed to me to complicated to add a simple
command compared to grub legacy.
That's why I asked, I'll try with Alex Roman suggestion.
adrian15
_
On 12/06/07, adrian15 <[EMAIL PROTECTED]> wrote:
Once I write a new command like map.c or pause.c how am I supposed to
add it to the standard grub?
Should I write the makefiles manually?! or should I use some of the .sh
files at the grub2 source code root folder?
I've been editi
On Tue, Jun 12, 2007 at 01:56:52PM +0200, adrian15 wrote:
> Once I write a new command like map.c or pause.c how am I supposed to
> add it to the standard grub?
> Should I write the makefiles manually?! or should I use some of the
> .sh
> files at the grub2 source code root folde
Once I write a new command like map.c or pause.c how am I supposed to
add it to the standard grub?
Should I write the makefiles manually?! or should I use some of the .sh
files at the grub2 source code root folder?
adrian15
___
Grub-
