From: Tritech - Jody <jody@nctritech.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: Fixed full5 and cleaned up HD image script
Date: Mon, 27 Feb 2017 08:45:41 -0500 [thread overview]
Message-ID: <9e6b20c3-0541-f9b7-d393-299c5ebbdc30@nctritech.com> (raw)
Just wanted to let everyone know about the new code push. I dropped the
m4 and yacc commands from the default program set to make full5 building
work again. I also improved Georg's hard drive script to add more error
checking and flexibility and to get rid of the byte0x01 file that I
noticed. Changes tested with QEMU to make sure the HD boot works.
-Jody
reply other threads:[~2017-02-27 13:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=9e6b20c3-0541-f9b7-d393-299c5ebbdc30@nctritech.com \
--to=jody@nctritech.com \
--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).