From: Richard Wallman <r_wallman@yahoo.co.uk>
To: linux-8086@vger.kernel.org
Subject: Re: Elks testing
Date: Fri, 6 Dec 2002 22:47:23 +0000 (GMT) [thread overview]
Message-ID: <200212062247.gB6MlIAw024765@eddie.loc> (raw)
In-Reply-To: <20021205133648.J51701-100000@agora.rdrop.com>
I've been working on a shell to add to the source (there's something
wrong with the sash license, wasn't there?) and also a
compress/decompress program (first part of a system installer).
Perhaps a separate TODO: for applications should be created?
ELKS would *really* become useful when it has full Ethernet support -
the use of an old computer as a router/firewall would make ELKS very
popular. There's already a HTTP server, and if there's socket support
then an SMTP server and POP3 server would be next.
I'm going to be getting an SSD for my Psion 3c soon, so I'll
(hopefully) be able help with the SIBO port as well. :)
--
Richard Wallman
http://www.murkygoth.uklinux.net/elks
next prev parent reply other threads:[~2002-12-06 22:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-26 8:32 Elks Distribution Edition (EDE) - Update Neil Holmes
2002-12-05 21:43 ` Elks testing Dan Olson
2002-12-06 11:59 ` Pat Gilliland
2002-12-06 22:47 ` Richard Wallman [this message]
2002-12-07 2:28 ` Dan Olson
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=200212062247.gB6MlIAw024765@eddie.loc \
--to=r_wallman@yahoo.co.uk \
--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