public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Olson <dano@agora.rdrop.com>
To: Richard Wallman <r_wallman@yahoo.co.uk>
Cc: linux-8086@vger.kernel.org
Subject: Re: Elks testing
Date: Fri, 6 Dec 2002 18:28:25 -0800 (PST)	[thread overview]
Message-ID: <20021206182552.J45648-100000@agora.rdrop.com> (raw)
In-Reply-To: <200212062247.gB6MlIAw024765@eddie.loc>

Sounds like a great idea.  For the time being, I'm going to use ELKS as a
terminal I think, but I would love support for a 3C503 (or another adaptor
if nobody wants to use a 3com card).  I'm sure there are odd Linux things
I'm used to having that would be handy too, as I think of them, I'll make
a list.

	Dan

> 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
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


      reply	other threads:[~2002-12-07  2:28 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
2002-12-07  2:28     ` Dan Olson [this message]

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=20021206182552.J45648-100000@agora.rdrop.com \
    --to=dano@agora.rdrop.com \
    --cc=linux-8086@vger.kernel.org \
    --cc=r_wallman@yahoo.co.uk \
    /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