From: Dan Olson <dano@agora.rdrop.com>
To: linux-8086@vger.kernel.org
Subject: Re: problems with putting an rtlinux kernel on a 686 on a PC104 board
Date: Wed, 4 Dec 2002 11:50:50 -0800 (PST) [thread overview]
Message-ID: <20021204114900.U43261-100000@agora.rdrop.com> (raw)
In-Reply-To: <001501c29bc1$c831b750$182fa8c0@2fkft.com>
> BTW, does the use of Linux for military purposes make the open source
> development community legitimate targets? I indeed do think so. Commercial
> sw licences specifically prohibite critical applications (nuclear
> powerplants, life support and the like) which conveniently covers military
> use, so they are not agreeing to that. Linus should better look out for
> the bearded man with thin face...
You really think so? I would think the community would be a little too
far removed, like the auto maker who made the car that the suicide bomber
drove or something. It's an interesting point though.
Dan
prev parent reply other threads:[~2002-12-04 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 23:38 problems with putting an rtlinux kernel on a 686 on a PC104 board Sonal Bhushan
2002-12-04 18:20 ` Feher Tamas
2002-12-04 19:50 ` Dan Olson [this message]
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=20021204114900.U43261-100000@agora.rdrop.com \
--to=dano@agora.rdrop.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