From: LM <lmemsm@gmail.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: Re: Cleaning up elkscmd and adding help text - Questions
Date: Sat, 28 Mar 2015 11:35:48 -0400 [thread overview]
Message-ID: <CAFipMOFVf_kJ43h+s94WdWWLj9CPOi4EnE51XQKaaBiDu9h3TQ@mail.gmail.com> (raw)
In-Reply-To: <20150327221912.60093649@www.etchedpixels.co.uk>
On 3/27/15, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> Busybox is in relative terms huge - even some of the busybox utilities
> split standalone are oversized compared with other implementations.
Have you looked at other utility collections like Heirloom and Toybox?
I read that Toybox is being developed by a former developer of
Busybox and that he is very interested in efficiency. Would be very
curious how his idea of efficiency translates to a system like Elks.
I do know portability is not one of his areas of interest.
Also, it may be too basic, but sbase has an interesting take on some
utilities. There's also pdclib as another alternative to uclibc.
It's not as complete, but there are some interesting optimizations
like with strstr using the railgun algorithm.
I found it interesting comparing the Fusix version of ls with the
Minix version. Liked the removal of the large array to track
user/group.
Sincerely,
Laura
http://www.distasis.com/cpp
next prev parent reply other threads:[~2015-03-28 15:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 8:19 Cleaning up elkscmd and adding help text - Questions Nils Stec
2015-03-27 13:19 ` Jody Bruchon
2015-03-27 14:10 ` Alan Cox
2015-03-27 16:17 ` Jody Bruchon
2015-03-27 18:19 ` MFLD
2015-03-27 18:26 ` Jody Bruchon
2015-03-27 18:52 ` MFLD
2015-03-27 22:19 ` Alan Cox
2015-03-28 15:35 ` LM [this message]
2015-03-27 18:41 ` Alan Cox
2015-03-27 17:59 ` Nils Stec
2015-03-27 18:31 ` Alan Cox
2015-03-27 13:54 ` 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=CAFipMOFVf_kJ43h+s94WdWWLj9CPOi4EnE51XQKaaBiDu9h3TQ@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).