public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: "I'm in Void" <list1@benka.com>
To: linux-8086@vger.kernel.org
Subject: Re: Future of ELKS
Date: Thu, 20 May 2004 05:39:17 +0200	[thread overview]
Message-ID: <200405200539.17155.list1@benka.com> (raw)
In-Reply-To: <1084985870.3062.23.camel@talena.hsol.net>

Hi all,

onsdagen den 19 maj 2004 22.55 skrev Miguel Bolanos:
> Good day to all,
> 
> The project seems to be finally awaking from a very long period of
> inactivity, this can be reflected not only by the traffic on the mailing
> list, but on the amount of people hanging around at the irc channel and
> the quality of the discussions over there.
> 
> 
> - A possibility of using gcc to create 8086 binaries might be a
> possibility with a patch created by our irc friend boto. If the tests of
> this are successful we will enable elkscmd to let the users decide if
> they which to use gcc-8086 or our current bcc :)

This would be a major lift imho. Even if elks is 'never' even gona be a subset 
of linux, and that is not a major aspect for me at least as the 8088 in 
itself is cool to have good programs for, the idea to shift more to linux 
side is appealing.
I have also thought in the areas of netbsd kernels, to let it work in a subset 
environment. All this might come if the gcc-8088 compiler seams stable for 
it.


> 
> Anyways thats all for now. Hope to hear back from all.
> best wishes
> 
> Mike

/Benka
-- 
"I love Saturday morning cartoons, what classic humour!  This is what
entertainment is all about ... Idiots, explosives and falling anvils."
		-- Calvin and Hobbes, Bill Watterson


  reply	other threads:[~2004-05-20  3:39 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-19 20:55 Future of ELKS Miguel Bolanos
2004-05-20  3:39 ` I'm in Void [this message]
2004-05-20 14:47   ` Miguel Bolanos
2004-05-20 11:42 ` Javier Sedano
2004-05-20 15:15   ` Miguel Bolanos
2004-05-20 15:37     ` Eduardo Pereira Habkost
2004-05-20 16:06       ` Andrey Romanenko
2004-05-21  5:51         ` Dan Olson
2004-05-20 17:30       ` Javier Sedano
2004-05-21  8:32         ` Gábor Lénárt
2004-05-21 14:15           ` Jody
2004-05-24  9:29             ` Gábor Lénárt
2004-05-24 18:20               ` Alan Cox
2004-05-20 23:43       ` David Given
2004-05-21  1:04         ` Stefan de Konink
2004-05-21  3:39           ` Chad Page
2004-05-29 16:58             ` Gregg C Levine
2004-05-21  5:55         ` Dan Olson
2004-05-21  6:08         ` Jody
2004-05-21 13:24         ` Eduardo Pereira Habkost
2004-05-21 16:30           ` David Given
2004-05-21 16:59             ` Michael McConnell
2004-05-22 12:12               ` David Given
2004-05-22 17:29                 ` Chad Page
2004-05-21 18:38             ` Jody
2004-05-22  8:53               ` jb1
2004-05-22 17:00                 ` Chad Page
2004-05-24  9:42               ` Gábor Lénárt
2004-05-20 16:54     ` Javier Sedano
2004-05-21  5:50     ` Dan Olson
2004-05-21  9:08       ` Arnaldo Carvalho de Melo
2004-05-21 10:24         ` Alan Cox
2004-05-24 12:20         ` Gábor Lénárt
  -- strict thread matches above, loose matches on Subject: below --
2004-05-20 13:40 Pat Gilliland
2004-05-21 17:53 ` Miguel Bolanos
2004-05-20 20:18 Tommy McCabe
2004-05-24 13:17 BODRATO Stefano

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=200405200539.17155.list1@benka.com \
    --to=list1@benka.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