From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jody Bruchon <jody@jodybruchon.com>
Cc: ELKS <linux-8086@vger.kernel.org>
Subject: Re: Cleaning up elkscmd and adding help text...any volunteers?
Date: Wed, 18 Mar 2015 13:24:38 +0000 [thread overview]
Message-ID: <20150318132438.3b9a5bac@www.etchedpixels.co.uk> (raw)
In-Reply-To: <550972F6.5000309@jodybruchon.com>
> We especially need help text because GNU and/or BusyBox commands is what
> anyone trying ELKS will currently be used to. Users won't know how to
> use the commands if they don't explain themselves. One example is how
> the 'dd' ELKS command doesn't support 'conv=' or 'oflag=' while the
> other two do.
You may also want to look at the V7 and 2.11 BSD releases. The encumbered
Unix licensed bits were freed up by Caldera before they went evil and it
contains a lot of useful stuff although some of it contains PDP11-isms
and a few other traps for the unwary.
Also while I remember, as FUZIX uses some of the same code I've got
ansified versions of certain critical v7 apps done (wumpus, backgammon,
arithmetic, and fish) 8)
I also got a bug report that the C strlen() implementation in BCC libc is
wrong (it returns a number 1 too large). Not checked the 8086 asm version.
Alan
next prev parent reply other threads:[~2015-03-18 13:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 12:43 Cleaning up elkscmd and adding help text...any volunteers? Jody Bruchon
2015-03-18 13:24 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-18 20:52 Juan Perez-Sanchez
2015-03-19 13:41 LM
2015-03-19 14:07 ` Alan Cox
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=20150318132438.3b9a5bac@www.etchedpixels.co.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jody@jodybruchon.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).