Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 6 Oct 2002 12:25:22 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 6 Oct 2002 12:25:22 -0400 Received: from almesberger.net ([63.105.73.239]:3347 "EHLO host.almesberger.net") by vger.kernel.org with ESMTP id ; Sun, 6 Oct 2002 12:25:19 -0400 Date: Sun, 6 Oct 2002 13:30:44 -0300 From: Werner Almesberger To: Ingo Molnar Cc: Larry McVoy , linux-kernel@vger.kernel.org Subject: Re: New BK License Problem? Message-ID: <20021006133044.A14894@almesberger.net> References: <20021006075627.I9032@work.bitmover.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ; from mingo@elte.hu on Sun, Oct 06, 2002 at 05:22:33PM +0200 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1054 Lines: 26 [ Ccs trimmed ] Ingo Molnar wrote: > just wondering where the boundary line is. Eg. if i started working on a > versioned filesystem today, i'd not be allowed to use BK. I just have to > keep stuff like that in mind when using BK. Worse yet, assuming you work for a sufficiently large company, your license is void if or as soon as anybody works in that company's name on something BKS (or any legal successor of them *) considers as competition. (* I'm not a lawyer, but I'm not sure if GPLing BK in the last moment before, say, bankruptcy, would really work.) - Werner -- _________________________________________________________________________ / Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net / /_http://www.almesberger.net/____________________________________________/ - 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/