public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Jody Bruchon <jody@jodybruchon.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: Re: Some questions on ELKS web sites
Date: Sun, 22 Mar 2015 11:31:41 -0400	[thread overview]
Message-ID: <550EE05D.9020706@jodybruchon.com> (raw)
In-Reply-To: <550EB379.1060400@gmail.com>

On 3/22/2015 8:20 AM, MFLD wrote:
> Then, I would ask maybe a FAQ : what is the ELKS official web site today
> ? I see mainly a SourceForge page (http://elks.sourceforge.net/) and a
> GitHub page (https://github.com/jbruchon/elks). What is the right one ?

The GitHub page is the current official site. I haven't touched 
SourceForge in aeons. The old site is mainly there for historical 
purposes; I've decided that until ELKS is a little further along in 
development, there's no point in trying to maintain an informational 
website for it. The info should be in the ELKS documentation/README 
first and on a website second.

I'd like to see some Ethernet card support in ELKS and that's where I 
personally draw the line; these days, everything is "connected" and SLIP 
is difficult to set up and requires a second computer. Everything in 
ELKS is designed solely to use SLIP and the ktcp program. Once we can 
connect to the Internet properly, we can port or write a text-mode web 
browser. I think that's when it will become more interesting to people 
in general and will justify having a new website.

Of course, I welcome the thoughts of others in this regard. These are 
just what I've contemplated in my spare time.

-Jody

  reply	other threads:[~2015-03-22 15:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <550EB2A1.5050706@gmail.com>
2015-03-22 12:20 ` Some questions on ELKS web sites MFLD
2015-03-22 15:31   ` Jody Bruchon [this message]
2015-03-22 15:38     ` Royce Williams

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=550EE05D.9020706@jodybruchon.com \
    --to=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