if this happens then you just check the code out of the kernel as of the
last version prior to the one that makes this change.
if this happens then we are worse off then we are now, but not worse off
then we were before useing BK (diff+patch still work remember)
David Lang
On Mon, 7 Oct 2002, Craig Dickson wrote:
> Date: Mon, 7 Oct 2002 10:18:12 -0700
> From: Craig Dickson <crdic@pacbell.net>
> To: linux-kernel@vger.kernel.org
> Subject: Re: New BK License Problem?
>
> Larry McVoy wrote:
>
> > It always was and always will be a feature that it is easy to get in
> > and get *out* of BK. We may be pains in the butt on the license front
> > but once you are using BK, if you have to get the data out, BK makes
> > that as pleasant as can possibly be made.
>
> This is all very well, but is this not something that might change if
> someone else were to come into control of the company? It isn't hard to
> imagine some future BitMover CEO with a more Microsoft-like mentality
> looking at the product and thinking, "This 'ease of getting data out'
> has to go -- we need to make it less convenient for our customers to
> defect."
>
> It is a general problem with power that you have to worry not just about
> whether those who currently wield it will abuse it, but also their
> successors.
>
> Craig
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Oct 07 2002 - 22:00:59 EST