From: LM <lmemsm@gmail.com>
To: linux-8086@vger.kernel.org
Subject: core utilities
Date: Thu, 8 Aug 2013 07:16:42 -0400 [thread overview]
Message-ID: <CAFipMOFRtS1o7+LB_j8NeZWO9FXYAYG5HBOfxb1qu6FEGYobbA@mail.gmail.com> (raw)
I've been looking at the source code for some of the Minix utilities
that replace the standard GNU coreutils. I noticed several Minix
based utilities in the Elks (elkscmd) source tree. I also noticed
Minix itself seems to be switching to using BSD based utilities and is
no longer using many of these programs. Am curious about the pros and
cons of using the Minix code versus the NetBSD/FreeBSD code for basic
utilities. Anyone have any opinions?
Am also curious if there's been any progress on the BusyElks project
and how things are going with it.
Don't know if anyone's interested, but I've been experimenting with a
modified version of PicoBSD's msh and attempting to add enough bash
features to it to be able to run scripts I have for building various
applications. It's still in the works, but I'm making some progress.
Sincerely,
Laura
http://www.distasis.com/cpp
reply other threads:[~2013-08-08 11:16 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=CAFipMOFRtS1o7+LB_j8NeZWO9FXYAYG5HBOfxb1qu6FEGYobbA@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).