All of lore.kernel.org
 help / color / mirror / Atom feed
From: adrian15 <adrian15sgd@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Grub2 LUA API?
Date: Sat, 22 Aug 2009 20:57:55 +0200	[thread overview]
Message-ID: <4A903FB3.5070302@gmail.com> (raw)

Hi,

	I have been playing a bit with osdetect.lua file. I have seen many 
calls to grub.addmenu, grub.file_exist and so on.

	I am now interested in making a table where to store all the uuid 
associated to each one of the kernel that I find (I mean kernel's 
filesystem's uuid).

	As long as I suppose there is no documentation written about it I would 
like to know where should I look into the grub2 source code in order to 
know which grub.WHATEVER calls I can make, what are their 
arguments/options , their outputs and so on.

	So where should I look into in the source code?

	Thank you very much!

adrian15
-- 
Support free software. Donate to Super Grub Disk. Apoya el software 
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/index.php?pid=10




             reply	other threads:[~2009-08-22 19:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-22 18:57 adrian15 [this message]
2009-08-22 19:31 ` Grub2 LUA API? Bean
2009-08-23 15:25   ` adrian15

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=4A903FB3.5070302@gmail.com \
    --to=adrian15sgd@gmail.com \
    --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.