From: Roberto Peon <robertopeon@sportvision.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Hell.Surfers@cwctv.net, <nico@cam.org>,
<alan@lxorguk.ukuu.org.uk>, <pavel@suse.cz>, <drepper@redhat.com>,
<lm@bitmover.com>, <linux-kernel@vger.kernel.org>
Subject: Re: Re: New BK License Problem?
Date: Tue, 8 Oct 2002 11:30:44 -0700 [thread overview]
Message-ID: <200210081130.44639.robertopeon@sportvision.com> (raw)
In-Reply-To: <Pine.LNX.4.44L.0210081530220.1648-100000@duckman.distro.conectiva>
On Tuesday 08 October 2002 11:32 am, Rik van Riel wrote:
> On Tue, 8 Oct 2002, Roberto Peon wrote:
> > Good thing Linus was attached to the "Its amazing what you can do when
> > you don't know you can't do it" philosophy instead of the "If it could
> > have been done, it would have been done" POS philosophy.
>
> It all depends on how much risk you want to take and how
> much you have to lose.
>
> If all you can lose is some of your own time and energy
> there's nothing wrong with attempting something where
> everybody else has failed over the last 15 years.
>
> On the other hand, I wouldn't take that risk if I were
> running a business and had to make money to live...
I agree with this. The only thing I was disagreed with was your statement
which basically came down to:
If it could have been done, it would have been done.
Hell, the risks of starting up an open-source/service based company *are*
high, which is precisely why I won't try to start one up anytime in the
immediate future.
-Roberto JP
robertopeon@sportvision.com
next prev parent reply other threads:[~2002-10-08 18:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 21:12 Hell.Surfers
2002-10-07 21:19 ` Rik van Riel
2002-10-08 18:14 ` Roberto Peon
2002-10-08 18:32 ` Rik van Riel
2002-10-08 18:30 ` Roberto Peon [this message]
2002-10-08 19:16 ` Roberto Peon
2002-10-08 22:18 RE= " Hell.Surfers
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=200210081130.44639.robertopeon@sportvision.com \
--to=robertopeon@sportvision.com \
--cc=Hell.Surfers@cwctv.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=nico@cam.org \
--cc=pavel@suse.cz \
--cc=riel@conectiva.com.br \
/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
all inboxes | Powered by JetHome®