From: "Hans" <hans64@ht-lab.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: Re: Regarding the Future of ELKS
Date: Sun, 6 May 2007 10:23:23 +0100 [thread overview]
Message-ID: <005401c78fc0$35f3a040$6502a8c0@dionysus> (raw)
In-Reply-To: 463CD3EB.6020506@nc.rr.com
Hi Jody,
I am sure there is still live in ELKS but unless it is picked up by a very
enthusiastic experienced hacker with lots of spare time and experience I
think ELKS will remain a dormant project (like so many of sourceforge).
Unfortunately my hardware is not PC/XT compatible which means that I need to
understand all the nitty gritty stuff. When I looked at the source code I
quickly came to realise that this is an un-doable project for me. This was
not helped by a custom C compiler and non-flexible development environment
so in the end I gave up and became one of the many(?) low-active lurkers on
this list :-)
I will remain subscribed to this list and hope that one day ELKS will burst
into life with a vengeance :-)
Hans
www.ht-lab.com
----- Original Message -----
From: "Jody" <jbruchon@nc.rr.com>
To: "ELKS" <linux-8086@vger.kernel.org>
Sent: Saturday, May 05, 2007 7:58 PM
Subject: Regarding the Future of ELKS
> Hello everyone. This is Jody, the current maintainer of the ELKS project.
> I wanted to ask for everyone's opinion on what the future of ELKS should
> be.
>
> I can see many compelling reasons to drop ELKS entirely or shift it away
> from the 80(2)86-oriented platform, including the following:
>
> * No one works on ELKS. Really. I'm no C programmer, and apparently all
> the ones that COULD work on it have moved on to "bigger better things" in
> their lives.
>
> * 8086/80286 cores are being dropped in favor of other platforms,
> including ARM, 386EX, Coldfire, etc. While embedded Linux covers a lot of
> that territory, there is certainly some room for discussion of changing
> ELKS to be more portable and pushing it to those platforms. The minimalist
> approach to the ELKS kernel would make it far smaller than Linux and it
> could potentially compete with the likes of other smaller operating
> systems used in embedded applications, such as VxWorks.
>
> * ELKS has not developed to a very "usable" stage yet. There are a
> hundred different ways the project could go, but the original stated goals
> are quickly showing that they are not it. Lack of interest in the project
> and limited ability to reuse the code are clear signs that something must
> change.
>
> To those of you who are still subscribed to this list: what do you think
> should be done? I look forward to hearing your answers!
>
> ~Jody
> -
> 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
>
next prev parent reply other threads:[~2007-05-06 9:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-05 18:58 Regarding the Future of ELKS Jody
2007-05-05 22:10 ` Royce Williams
2007-05-05 22:14 ` NOTICE REGARDING SENDING MAIL TO THE ELKS LIST Jody
2007-05-06 10:08 ` Regarding the Future of ELKS Gábor Lénárt
2007-05-06 12:54 ` David Given
2007-05-06 13:46 ` Alan Cox
2007-05-06 17:13 ` David Given
2007-05-06 18:37 ` Alan Cox
2007-05-05 22:25 ` Mario Frasca
2007-05-06 9:23 ` Hans [this message]
2007-05-06 17:46 ` Luis A. Montes
2007-05-07 12:19 ` Mario Urban
-- strict thread matches above, loose matches on Subject: below --
2007-05-07 18:12 chriscureau
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='005401c78fc0$35f3a040$6502a8c0@dionysus' \
--to=hans64@ht-lab.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