public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Olson <dano@agora.rdrop.com>
To: "jerryc@innerpeace.org" <jerryc@innerpeace.org>
Cc: linux-8086@vger.kernel.org
Subject: Re: New Member VERY hot on 8086's
Date: Mon, 13 Jan 2003 11:43:39 -0800 (PST)	[thread overview]
Message-ID: <20030113113444.A48585-100000@agora.rdrop.com> (raw)
In-Reply-To: <3E21D8FC.1050305@innerpeace.org>

> We have over 100 free self-help programs and want to make them available
> for old 8086's for jails, halfway houses, shelters, rehab centers, and
> many other places where you wouldn't want to put more expensive computers.

That sounds like an interesting project.

> We probably only need a subset of ELKS (or Minix, or FreeDOS, or
> whatever we end up using). We mostly want to echo text to an 80 x 25
> text screen.

I assume everything is local to that computer then?  No serial terminals
off of a main computer or anything like that.  If that's the case, then I
guess you'd just need to make sure that whatever interface you choose is
supported (script, C, PERL, etc).

 We don't need to print or access any ports. We don't need
> mouse support (mice would probably disappear in these placements,
> anyway, and they're just something else to break). We looked at the
> Minix utilities and libraries, and they do much more than we need.

When you mentioned being concerned with hardware damage, is that true of
software too?  I mean, do you need a sort-of "security", not to totally
lock people out of places they shouldn't be, but to at least make it such
that someone with a little computer skill can't trash the system.  I
remember in school floppys were ofter stolen, and in DOS it's easy to type
"format c:".  I *think* ELKS would at least make it a little tougher to
destroy data on a fixed drive.

> These machines will be set up as dedicated Inner Peace machines, so
> other functions will not be needed. As you know, there are literally
> warehouses full of 8086's all over the world. Many of them end up in
> landfills because people do not know what to do with them. We have a
> good use for them if we can get it working.

I almost hate to ask this, but aren't 386s adn 486s just as easly found
for free?  I don't know, I just can't see someone keeping 8086s in
spendy warehouse space for this length of time.  Or do they come from
schools or places that are upgrading to those free 486s?

> We did plan to do this project with FreeDOS, but feel that using ELKS or
> Minix would help in the promotion of linux, and would rather go that route.

I can't fault you there :)

> P.S. Here's the link for the original project. We'll be converting it to
> innerpeace4elks soon, if that's how we end up going.

Let us know what you end up doing.

	Dan

  parent reply	other threads:[~2003-01-13 19:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-12 21:07 New Member VERY hot on 8086's jerryc
2003-01-12 23:28 ` Alan Cox
     [not found]   ` <3E2220A6.7050500@innerpeace.org>
     [not found]     ` <1042470345.18624.17.camel@irongate.swansea.linux.org.uk>
2003-01-14  4:27       ` jerryc
2003-01-13 19:43 ` Dan Olson [this message]
2003-01-14  4:15   ` jerryc

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=20030113113444.A48585-100000@agora.rdrop.com \
    --to=dano@agora.rdrop.com \
    --cc=jerryc@innerpeace.org \
    --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