public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Mario Frasca <mfrasca@zonnet.nl>
To: ELKS <linux-8086@vger.kernel.org>
Subject: Re: Regarding the Future of ELKS
Date: Sun, 6 May 2007 00:25:00 +0200	[thread overview]
Message-ID: <20070505222500.GB21971@localhost.localdomain> (raw)
In-Reply-To: <463CD3EB.6020506@nc.rr.com>

On 2007-0505 14:58:51, Jody wrote:
> I can see many compelling reasons to drop ELKS entirely or
> shift it away from the 80(2)86-oriented platform [...]

> 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!

hi Jody,
hi list,

I have done something in the past with ELKS, worked on ls and the init
procedure, I think...  

in the end, ELKS did not result 'usable' for me, all I wanted to use there
was an editor, but I did not manage to find nor port/compile anything.
I tried during a few weeks, then gave up.  without an editor, I would not
know what to do with a PC.  at the time I tried to use an old Amstrad
(V30 based, 8086 compatible), just for the fun of it, and also because
it had a very nice keyboard.  the system is still there, still working,
but still without an editor.

What other alternatives can I go?

- buy a better laptop, 386 based, and use linux?  minix?  freebsd?
- use dos...
- use an other operating system (which one?)
- port a minimal editor to ELKS...

but these are the alternatives to my problem, which is "running
something on an old 8086 that would allow me to edit text"...

I am sure that ELKS can be defined 'usable' in other ways, this is just
my own interpretation.

looking on the elks website, I miss something, or it's too late and I
can't find it.  it states why (create a linux-like kernel), but then this
is not the whole story, is it?  we do want to use the kernel.  maybe we
could use the sourceforge tracker to keep track of what has to be done.
in the website I would also put more and more explicit links to the
tracker, so that also the occasional browser WILL check it...

ciao,
Mario

-- 
Never, under any circumstances, take a sleeping pill 
and a laxative on the same night. 

  parent reply	other threads:[~2007-05-05 22:25 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 [this message]
2007-05-06  9:23 ` Hans
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=20070505222500.GB21971@localhost.localdomain \
    --to=mfrasca@zonnet.nl \
    --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