From: Stephen Samuel <samuel@bcgreen.com>
To: Thunder from the hill <thunder@ngforever.de>
Cc: Florian Weimer <Weimer@CERT.Uni-Stuttgart.DE>,
linux-kernel@vger.kernel.org
Subject: Re: SSSCA Hits the Senate
Date: Mon, 25 Mar 2002 18:44:33 -0800 [thread overview]
Message-ID: <3C9FE091.5000702@bcgreen.com> (raw)
In-Reply-To: <200203251522.JAA62284@tomcat.admin.navo.hpc.mil> <001b01c1d417$7ec599a0$0100007f@localdomain.wni.com.wirelessnetworksinc.com> <87zo0wnup5.fsf@CERT.Uni-Stuttgart.DE> <3C9FBE96.1010502@ngforever.de>
But how are you going to compile your FIRST kernel?? At some point
you'll need a compiler, and they'll insist that the limitations go into
that first compiler that someone gets.
Thunder from the hill wrote:
> Florian Weimer wrote:
>
>> "Herman Oosthuysen" <Herman@WirelessNetworksInc.com> writes:
>>
>>
>>> The obvious solution is to continue the way Richard Stallman envisaged:
>>> ***Distribute all code in source form only - no binary distributions.***
>>>
>>> This way, the source files are protected under freedom of speech
>>> rules and
>>> the originator of the work is safe.
>>
>>
>>
>> Unfortunately, this works only in the U.S. Other countries which will
>> follow the US leadership in consumer suppression regulate free speech
>> to make it conforming to law.
>>
>> I agree, though, that source-only distribution avoids many problems
>> and is preferable.
>>
> But not all the people out there are skilled enough to install a source
> distribution. Also, binary installations may go faster, and the youth of
> today tends to not having time...
> So there are still problems with it. If one day computers are all so
> fast like the one who compiled a kernel in 7.56 seconds, and we have a
> nice API for compiling, it might be great idea, but it might happen that
> someone else will claim to have had the idea. This certainly won't be me.
>
> Thunder
--
Stephen Samuel +1(604)876-0426 samuel@bcgreen.com
http://www.bcgreen.com/~samuel/
Powerful committed communication, reaching through fear, uncertainty and
doubt to touch the jewel within each person and bring it to life.
next prev parent reply other threads:[~2002-03-26 2:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-25 15:22 SSSCA Hits the Senate Jesse Pollard
2002-03-25 16:06 ` Ron Pagani / San Francisco / San Jose, CA
2002-03-25 16:09 ` Herman Oosthuysen
2002-03-25 22:33 ` Florian Weimer
2002-03-26 0:19 ` Thunder from the hill
2002-03-26 2:44 ` Stephen Samuel [this message]
2002-03-26 12:18 ` Thunder from the hill
2002-03-26 20:32 ` CBDTPA (Re: SSSCA Hits the Senate) son of SSSCA Andre Hedrick
2002-03-25 17:34 ` SSSCA Hits the Senate Itai Nahshon
2002-03-25 18:17 ` Alan Cox
2002-03-25 19:37 ` Herman Oosthuysen
2002-03-25 20:37 ` Rik van Riel
2002-03-25 21:24 ` Herman Oosthuysen
2002-03-25 22:43 ` Itai Nahshon
2002-03-26 0:25 ` Thunder from the hill
2002-03-25 21:29 ` Matthew D. Pitts
2002-03-26 20:30 ` Matt Reppert
2002-03-25 22:35 ` Florian Weimer
-- strict thread matches above, loose matches on Subject: below --
2002-03-25 20:58 Dieter Nützel
2002-03-25 21:33 ` Herman Oosthuysen
2002-03-25 17:50 Gabriel Sechan
2002-03-23 1:09 Paul G. Allen
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=3C9FE091.5000702@bcgreen.com \
--to=samuel@bcgreen.com \
--cc=Weimer@CERT.Uni-Stuttgart.DE \
--cc=linux-kernel@vger.kernel.org \
--cc=thunder@ngforever.de \
/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