From: Jody Bruchon <jody@jodybruchon.com>
To: Stefan Pietzonke <jay-t@gmx.net>
Cc: ELKS <linux-8086@vger.kernel.org>
Subject: Re: Help test recent Dev86 changes against ELKS
Date: Tue, 1 Dec 2015 14:37:35 -0500 [thread overview]
Message-ID: <565DF6FF.8050603@jodybruchon.com> (raw)
In-Reply-To: <565DF1C6.3000105@gmx.net>
On 2015-12-01 14:15, Stefan Pietzonke wrote:
> Hi Jody,
> I made a successfull ELKS build with the lkundrak/dev86.
> I booted an image in bochs. Seems to work. I did only a quick test.
>
> I had to copy as86_encap from dev86/as to /usr/bin manually to make it
> work.
Thanks for that. I've merged upstream Dev86 into my fork now. My fork
still has the as86_encap where it needs to be, so anyone reading this
should be able to pull Dev86 from me and build ELKS as usual.
If anyone runs into problems, let me know immediately so I can fix them!
-Jody
prev parent reply other threads:[~2015-12-01 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 11:52 Help test recent Dev86 changes against ELKS Jody Bruchon
[not found] ` <565DF1C6.3000105@gmx.net>
2015-12-01 19:37 ` Jody Bruchon [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=565DF6FF.8050603@jodybruchon.com \
--to=jody@jodybruchon.com \
--cc=jay-t@gmx.net \
--cc=linux-8086@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).