Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 7 Oct 2002 13:37:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 7 Oct 2002 13:37:30 -0400 Received: from bitmover.com ([192.132.92.2]:7854 "EHLO mail.bitmover.com") by vger.kernel.org with ESMTP id ; Mon, 7 Oct 2002 13:37:29 -0400 Date: Mon, 7 Oct 2002 10:43:03 -0700 From: Larry McVoy To: Craig Dickson Cc: linux-kernel@vger.kernel.org Subject: Re: New BK License Problem? Message-ID: <20021007104303.Q14596@work.bitmover.com> Mail-Followup-To: Larry McVoy , Craig Dickson , linux-kernel@vger.kernel.org References: <20021007171812.GB13653@linux700.localnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20021007171812.GB13653@linux700.localnet>; from crdic@pacbell.net on Mon, Oct 07, 2002 at 10:18:12AM -0700 X-MailScanner: Found to be clean Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2485 Lines: 45 On Mon, Oct 07, 2002 at 10:18:12AM -0700, Craig Dickson wrote: > 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." Yup. Don't know what to do about it other than stay in charge. If it weren't for interactions like this with the community, I could make a compelling case that giving away the software and maintaining the status quo is in the best interests of BitMover. As it stands right now, we do it only because I insist on it and I own more stock than anyone else. My goal is to arrive at some sort of reasonable point, put this flamage behind us, and live happily ever after. We definitely derive benefit from having the kernel in BK. It stresses it, the kernel team has hard problems that we have no choice but to fix, the product is better and continues to get better because of it. The fact that it works with what you guys do to it validates the product, that's an important thing for us. The so-called PR value is definitely offset by the negative PR value we get from things like this weekend. I think I could make that go away simply by unsubscribing from the kernel list. That's not very realistic, I like being on the list. Another way to make it go away is hire Chris Mason and get him to do for me what he did for Hans. Hans and I share some of that shoot-yourself-in-the-foot behaviour. When Hans got Chris and Chris became the defacto interface to the outside world I believe that was a turning point for the acceptance of resierfs. Sometimes we are our own worst enemies. So I need a Chris for BitMover. -- --- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm - 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/