All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Automagic command loading
Date: Wed, 6 Oct 2004 10:43:08 +0200	[thread overview]
Message-ID: <200410061043.09605.okuji@enbug.org> (raw)
In-Reply-To: <20041001215653.GA19015@artax.karlin.mff.cuni.cz>

On Friday 01 October 2004 23:56, Tomas Ebenlendr wrote:
> But I have folowing questions:
>
>     1.) Should I throw away current implementation, or should there
> be a module with this implementation (e.g. autocmd_elf.mod).

If you think it is useful, you can commit it. But I don't see any 
benefit if we have another implementation.

>     2.) I think, that having information about supported commands in
>     module is not bad. I can write tool, to read it (and generate
>     autocmd.lst from this information). Advantage will be following:
>     User1 compiles his own module and sends it to User2. User2 will
> copy the module on proper location and run:
> 	grub-mod-read-cmds the_module.mod >> autocmd.lst

It sounds to me the same as telling User2 this:

echo foo foo.mod >> autocmd.lst

But it is up to you how to build autocmd.lst. If you think it is easier 
to use an ELF section, why not. But I'm a bit afraid of a too much 
dependency upon ELF.

Okuji



      reply	other threads:[~2004-10-06  8:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-28 19:05 Automagic command loading Tomas Ebenlendr
2004-09-29 12:16 ` Marco Gerards
2004-09-29 22:14   ` Tomas Ebenlendr
2004-09-29 15:02 ` Yoshinori K. Okuji
2004-09-29 21:38   ` Tomas Ebenlendr
2004-09-29 22:00     ` Marco Gerards
2004-09-29 22:23       ` Tomas Ebenlendr
2004-09-30 13:33     ` Yoshinori K. Okuji
2004-09-30 15:05       ` Marco Gerards
2004-09-30 17:44         ` Tomas Ebenlendr
2004-10-01 15:09         ` Yoshinori K. Okuji
2004-10-01 15:36           ` chaac
2004-10-01 21:56           ` Tomas Ebenlendr
2004-10-06  8:43             ` Yoshinori K. Okuji [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200410061043.09605.okuji@enbug.org \
    --to=okuji@enbug.org \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.