From: Alan Carvalho de Assis <acassis@gmail.com>
To: Jody Bruchon <jody@jodybruchon.com>
Cc: linux-8086@vger.kernel.org
Subject: Re: ELKS disk images updated
Date: Sun, 19 Feb 2012 21:12:41 -0200 [thread overview]
Message-ID: <CAG4Y6eQ_dZr_3L6_XPh7ZOR55G27aGsfmvNg+HmOjVHTOpwy6Q@mail.gmail.com> (raw)
In-Reply-To: <4F414614.3010609@jodybruchon.com>
On 2/19/12, Jody Bruchon <jody@jodybruchon.com> wrote:
snip
> I feel that a much better approach will be to take the
> separate sources we have now and combine them into an ELKS "BusyBox"
> instead. It would involve far less work since the tools work fine with
> ELKS already and are written in the C dialect required. I'll take
> another look and see what I could do to merge them together.
Yes, you are right, modifying existent programs source code to become
just a single binary like busybox will be easier than porting original
busybox to ELKS.
Do you think it is easy to port Linux applications to use Dev86 libc
or is it very inconsistent?
> sh is a copy of ash, not a symlink, unless you use the 360K root disk,
> where I symlinked it and was able to copy a few more useful tools such
> as "tr" because of the extra 50K I gained. I will correct that problem
> later; the other disks had free space whereas the 360K root disk was
> totally full. When I built new binaries with the latest Dev86 toolchain,
> all binaries shrunk, so I took advantage of this to further reduce the
> size of the system. The 360K disk is still completely full...but now it
> has more stuff! :-)
>
I noticed some commands are not working correctly, please try this one:
# cd /bin
# ls -l | more
I think the problem is on pipe (|) because "more file" is working.
Thank you very much!
Best Regards,
Alan
next prev parent reply other threads:[~2012-02-19 23:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F41458F.9030506@jodybruchon.com>
2012-02-19 18:57 ` ELKS disk images updated Jody Bruchon
2012-02-19 23:12 ` Alan Carvalho de Assis [this message]
2012-02-19 18:20 Alan Carvalho de Assis
-- strict thread matches above, loose matches on Subject: below --
2012-02-19 17:09 Jody Bruchon
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=CAG4Y6eQ_dZr_3L6_XPh7ZOR55G27aGsfmvNg+HmOjVHTOpwy6Q@mail.gmail.com \
--to=acassis@gmail.com \
--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).