Re: Where is FreeBSD going? <the never-ending thread>

From: Narvi (narvi_at_haldjas.folklore.ee)
Date: 01/09/04

  • Next message: Tim Kientzle: "Re: tar's unusual argument handling"
    Date: Sat, 10 Jan 2004 00:09:37 +0200 (EET)
    To: Matt Freitag <mpf@inodes.us>
    
    

    On Fri, 9 Jan 2004, Matt Freitag wrote:

    > Narvi wrote:
    >
    > >>"M. Warner Losh" <imp@bsdimp.com> writes:
    > >>
    > >>
    > >>
    > >>>Whatever. I've consulted lawyers on this who assure me that it is
    > >>>legal. You've admitted to not knowing US Copyright law and are aguing
    > >>>emotion, which is why I didn't reply to the rest of your message.
    > >>>
    > >>>
    > >>
    > >It is not clear that there is a way - as things stand - to get to a point
    > >where this wouldnot be the case. In appears very doubtful there is such a
    > >way unless you can get to get everybody whose code has been ever commited
    > >to send in a real written on paper copyright transfer, the chances of
    > >which are essentialy 0, even should you be able to trace down all
    > >involved.
    > >
    > >
    > So there are cases of code by authors being committed into the codebase
    > without their knowledge/consent? This would be a problem. If code is
    > being committed against license, I definitely see an issue here.

    Consider code merges from Net/OpenBSD. There is no explicit permission
    involved nor needed.

    > However, If you /GIVE/ your IP to the FreeBSD community, it's no longer
    > yours. Either way, apparently you'll never make everyone happy, even as

    Well... See, this is the place where people go wrong. Nobody is *GIVING*
    their IP or code to anybody (and this includes the original sources from
    Berkeley), they are simply licencing it. And unsuprisingly enough, there
    is a difference - a big one - between two two. Whetever one needs to be
    concerned about that is yet againan altogether different matter.

    The same would by the way apply even if all of FreeBSD was GPL licenced.

    > hundreds (or thousands) of people give away their time to produce
    > something at no cost to you, there's still always going to be someone
    > complaining. (We refer to this as a sense of entitlement - Many people
    > have this, and it's an unfortunate growing fad all over.) If you don't
    > want your code in FreeBSD, don't submit it. Anyone going to pursue some
    > indictments against Coyote Point Systems? Since their load-balancing
    > hardware runs FreeBSD, and I don't believe (I'm unsure, but from the
    > info I've gotten, it doesn't sound like it.) that they give you any of
    > the source with your purchase of their hardware, Hmm....
    >

    There is no scenario at all under which they would have to give you their
    code. None at all.

    > -mpf
    >
    > +---- - -
    > | Resistance is futile, assimilation into the FreeBSD community is
    > inevitable.
    >
    >

    _______________________________________________
    freebsd-hackers@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
    To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"


  • Next message: Tim Kientzle: "Re: tar's unusual argument handling"

    Relevant Pages

    • Re: Is FreeBSD ready for desktop (Mozilla Flash)
      ... A number of hardware vendors ... > happen to be using a hardware/software combination blessed by Macromedia. ... >> layer for running the Linux version of the plugin exists. ... copies of FreeBSD running on i386 than on any of the other hardware ...
      (comp.unix.bsd.freebsd.misc)
    • RE: Anthonys drive issues.Re: ssh password delay
      ... The dmesg you sent indicated that the 2 disks were negotiating at ... > possible cause in the universe before blaming it on FreeBSD. ... to take the risk of it being hardware, ... believe is that it's a bug in the FreeBSD driver. ...
      (freebsd-questions)
    • Re: Quality of FreeBSD
      ... And wouldn't mind to wait longer for real production quality ... on the hardware you know ... and FreeBSD users to do some of the testing. ... This change will help shake out software bugs relating to ...
      (freebsd-stable)
    • Re: FreeBSD and hardware??
      ... Installing on laptop type hardware is a tricky proposition: ... FreeBSD project already has a very good world-wide on-line distribution ... Driver support really is the kicker in all of this. ... Apple MacOSX doesn't ...
      (freebsd-questions)
    • Re: i give up
      ... The list of supported hardware is often written in terms ... I've installed ethernet cards named "compex" to PCs and they worked well ... compatible with FreeBSD. ... nVidia sucks for use on Unix platforms. ...
      (freebsd-current)