From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: porting info
Date: Tue, 01 Nov 2011 20:43:42 +0100 [thread overview]
Message-ID: <4EB04BEE.8080500@gmail.com> (raw)
In-Reply-To: <15425.439.683-28710-676871465-1319806058@seznam.cz>
[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]
On 28.10.2011 14:47, Dominik Táborský wrote:
> Hi,
>
> I am considering porting Grub2 to HelenOS system, which does not prefer any standard API and instead has its own.
>
> On the IRC channel a guy told me I need to port just grub-probe and grub-setup (please correct me if wrong). I am looking for some information, overview or something that would help me understand how things work inside GRUB2.
>
> Primarily I'd like to know what should be ported (files and stuff) and a bit of guidance (like "don't try to fix that [...]").
>
> Any help would be much appreciated.
>
BTW I've just checked. GRUB2 is able to load HelenOS just fine (I used
legacy_configfile). So porting is limited to compiling it under HelenOS.
bdsh is obviously not enough to hold our build system or scripts. For
the required dependencies see INSTALL. In case of more questions you can
ask here.
> Thanks in advance
>
> Dominik
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2011-11-01 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 12:47 porting info Dominik Táborský
2011-10-28 13:47 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-11-01 19:43 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2011-11-01 20:38 ` Dominik Táborský
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=4EB04BEE.8080500@gmail.com \
--to=phcoder@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.