From: LM <lmemsm@gmail.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: Re: Cleaning up elkscmd and adding help text...any volunteers?
Date: Thu, 19 Mar 2015 09:41:56 -0400 [thread overview]
Message-ID: <CAFipMOGLtd7DJLMbrP17wynT-V-g7+dHr_KsZZq9YErkAxUKYQ@mail.gmail.com> (raw)
I mentioned the man program in Elks on the musl wiki and some of the
developers that use musl seemed interested in it. One of them did
some modifications to it. You can find the modified version here:
https://github.com/rofl0r/hardcore-utils
Might be worth comparing to the current version in Elks to see if any
of the changes are worth using.
I've been working on my own version of various core utilities. Some
of them are based on the simple Minix utilities (which Elks uses in
some cases). Some of them are based on BSD or public domain code. A
few, I've written from scratch. They use ANSI prototypes not K&R in
most cases. My goal for this project is to make them as portable as I
can, so they'll work on POSIX systems or Windows or even DOS. I have
the following utilities:
based on Minix utilities:
cat
ls
du - with modifications for reusable functions for directory traversal
tr
xargs
find
based on obase utilities:
expr
original:
echo
mv
based on NetBSD utlities:
mktemp
tee
test
based on OpenBSD utiltiies:
patch
Others are also in the works and I'm still making improvements to
these when I can. I also have BSD versions of gzip, libintl and
libiconv. I've done some work on msh to try to add
internationalization support and minimize/remove the need to use fork.
I haven't officially released anything because everything's still
pretty much in flux. I'd be interested in sharing code or ideas for
improvements though. It would be nice to share some changes rather
than needing to duplicate effort.
Sincerely,
Laura
On Wed, Mar 18, 2015 at 8:43 AM, Jody Bruchon <jody@jodybruchon.com> wrote:
> I'm currently spending time cleaning up the elkscmd code base. There's a lot
> that needs to be done.
next reply other threads:[~2015-03-19 13:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 13:41 LM [this message]
2015-03-19 14:07 ` Cleaning up elkscmd and adding help text...any volunteers? Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2015-03-18 20:52 Juan Perez-Sanchez
2015-03-18 12:43 Jody Bruchon
2015-03-18 13:24 ` 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=CAFipMOGLtd7DJLMbrP17wynT-V-g7+dHr_KsZZq9YErkAxUKYQ@mail.gmail.com \
--to=lmemsm@gmail.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).