From: Michael Hofmann <michael.hofmann-@gmx.net>
To: linux-8086@vger.kernel.org
Subject: Re: Compiling Trouble etc
Date: Fri, 3 Jan 2003 22:46:40 +0100 [thread overview]
Message-ID: <200301032246.40368.michael.hofmann-@gmx.net> (raw)
Neil,
thank you for your response.
> I have only included a selection of binaries in EDE. I would be interested
> to know more on what binaries you are missing in case they should be in that
> selection.
I haven't really been missing certain binaries, I just wanted to see all there
is to play and get a feel of how far ELKS has evolved.
Now wait, what I actually have been missing was "ln". One of the first things
I did (lacking ln) was writing a small script called "free" that does nothing
but call "meminfo". I guess I don't understand why it's called "meminfo" in
the first place.
Unfortunately ln (now that I found it) doesn't work on my system, just like
some other commands.
Outside of images.zip, are there any applications available for ELKS besides
e3 (which sadly also doesn't work for me)?
> As far as the other elkscmd binaries are concerned, I am working
> on the "package install" aspect of EDE at present. I will be packing any
> binaries not already included in there.
That sounds like a good idea, I'm looking forward to your next version.
Thank you for the work you have done,
Michael
--
Press any key to continue or any other key to quit!
Promoting Penguin Power. Web home: http://www.qsl.net/dc1rn
next reply other threads:[~2003-01-03 21:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 21:46 Michael Hofmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-03 19:15 Compiling Trouble etc Neil Holmes
2003-01-01 22:53 Michael Hofmann
2003-01-01 16:03 Michael Hofmann
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=200301032246.40368.michael.hofmann-@gmx.net \
--to=michael.hofmann-@gmx.net \
--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