Re: BK kernel workflow

From: Pavel Machek (pavel_at_ucw.cz)
Date: 11/01/04

  • Next message: David Jez: "Re: PCI & IRQ problems on TI Extensa 600CD"
    Date:	Mon, 1 Nov 2004 09:39:22 +0100
    To: Larry McVoy <lm@work.bitmover.com>, Ram?n Rey Vicente <ramon.rey@hispalinux.es>, Xavier Bestel <xavier.bestel@free.fr>, James Bruce <bruce@andrew.cmu.edu>, Linus Torvalds <torvalds@osdl.org>, Roman Zippel <zippel@linux-m68k.org>, Andrea Arcangeli <andrea@novell.com>, Linux Kernel <linux-kernel@vger.kernel.org>
    
    

    Hi!

    > > > In Spain, reverse engineering is allowed for interoperability.
    > >
    > > And in lots of other places. Which has been mentioned in this and other
    > > instances of this discussion for the last 5 years. And the response is
    > > that BK already gives you documented ways to interoperate, extensively
    > > documented, in fact. You can get data and/or metadata into and out of
    > > BK from the command line. You could create your own network protocol,
    > > client, and server using the documented interfaces that BK has. You
    > > could create your own CVS2BK tool, your own BK2CVS tool, etc., all
    > > using documented interfaces.

    Okay, statement here seems to be "it is technically possible to write
    BK2something using documented interfaces", problem is just that nobody
    but Halle Berry is allowed to do the work. So Larry claims that he's
    not doing lock-in because you can export that data. Only catch is that
    you are not legally permitted to do that with free version, and Larry
    is not going to sell commercial version to you if you do something
    like this. So we have unique lockin at legal level, instead of
    technical one.

    If I misunderstood this, Larry please clarify.
                                                                    Pavel

    -- 
    People were complaining that M$ turns users into beta-testers...
    ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
    -
    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/
    

  • Next message: David Jez: "Re: PCI & IRQ problems on TI Extensa 600CD"

    Relevant Pages

    • Re: [RFC] Linux Kernel Subversion Howto
      ... they are not specific to Bitmover. ... It's not Larry choosing not to have you do the work, ... Written proposal describing in detail the commands you want added to bk ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Scaling noise
      ... Larry was possibly referring to IRIX scaling to 1024 CPUs, ... It appears that SGI is working to scale the Altix to 128 CPUs on Linux. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Kernel SCM saga..
      ... >bkcvs or bkweb and it's the most crucial information to make the bk data ... Larry was previously very clear about this that he ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Stop the Linux kernel madness
      ... > you do the right thing like Fedora or Redhat and ship the proper KBUILD environment ... To quote from your previous mail: ... That doesn't really like documented interfaces to me. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: x86, ARM, PARISC, PPC, MIPS and Sparc folks please run this
      ... >> I mean in the same group of threads with the same struct mm, ... > Larry means that it's perfectly normal for libc to map the same file ... Practical tests indicate that the vast majority of applications do not ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)