From: Warner Losh <email@example.com> To: John Cowan <firstname.lastname@example.org> Cc: COFF <email@example.com>, firstname.lastname@example.org Subject: Re: [COFF] [TUHS] ksh88 source code? Date: Thu, 23 Dec 2021 10:33:29 -0700 [thread overview] Message-ID: <CANCZdfoggLNW=ip0Po8d07arpLr6urJKVsn7zy9H4XHDm46NQA@mail.gmail.com> (raw) In-Reply-To: <CAD2gp_QnMdNo6pYvAOvPKr58DPmnYfxMr7GDdUtEabU9bqnpjQ@mail.gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 2272 bytes --] On Thu, Dec 23, 2021 at 9:14 AM John Cowan <email@example.com> wrote: > -tuhs +coff > > On Wed, Dec 22, 2021 at 1:30 AM <firstname.lastname@example.org> wrote: > > >> As a vendor or distributor, you would care. Anyone doing an OS or other >> software distribution (think the BSDs, of course; > > > There is no legal reason why the BSDs can't distribute GPLed software; > indeed, they did so for many years. Their objection is purely ideological. > However, not all of our downstreams could, however. So it's also a practical consideration. Also, some left over anger from the early days when BSD software would sometimes have the copyrights removed and be GPL'd. Thankfully, all the old cases of that were resolved years ago. Anyone selling a hardware device with embedded >> software (think switches/routers; think IOT devices; think consumer >> devices like DVRs; etc) needs to care. > > > Only if they are determined to infringe. Obeying the GPL's rules (most > often for BusyBox) is straightforward, and the vast majority of infringers > (per the FSF's legal team) are not aware that they have done anything wrong > and are willing to comply once notified, which cures the defect (much less > of a penalty than for most infringements). The ex-infringers do not seem > to consider this a serious competitive disadvantage. GPL licensors are > generous sharers, but you have to be willing to share yourself. > Except it's easier to just use software where there's not a compliance issue. Regardless of the altruism of the GPL licensors, easier is a competitive advantage. It's taken about 15 years from the initial busy-box suits for supply chains to catch up with the proper provenance so that downstreams know they are getting the proper sources. GPL (or similar "virally" >> licensed) software carries legal implications for anyone selling or >> distributing products that contain such software; and this can be a >> motivation to use software with less-restrictive license terms. > > > Only to the victims of FUD. Reusing source code is one thing: repackaging > programs is another. > Having been on the other side of this (a GPL shakedown that was improper), I'd say it's more than just FUD. The GPL is cool and all, but it isn't all roses and sunshine. Warner [-- Attachment #1.2: Type: text/html, Size: 4135 bytes --] [-- Attachment #2: Type: text/plain, Size: 141 bytes --] _______________________________________________ COFF mailing list COFF@minnie.tuhs.org https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
next prev parent reply other threads:[~2021-12-23 17:33 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20201222224306.GA28478@minnie.tuhs.org> [not found] ` <202012230546.0BN5kDwe028815@sdf.org> [not found] ` <CAGkfwV+kabBZZT=q9_mA9LtHPZ3xC0C2VybTW2bLFiYkJ2email@example.com> [not found] ` <firstname.lastname@example.org> [not found] ` <20211221162139.GP24180@mcvoy.com> [not found] ` <CANCZdfoJY86j0XpLMNx27GbY_mooBpiE=Vt5gX13x9zg4rVsJA@mail.gmail.com> [not found] ` <email@example.com> [not found] ` <alpine.LRH.firstname.lastname@example.org> 2021-12-23 16:14 ` John Cowan 2021-12-23 17:33 ` Warner Losh [this message] 2021-12-23 17:44 ` Larry McVoy 2021-12-23 18:18 ` John Cowan 2021-12-24 3:46 Rudi Blom [not found] <5D8BA976A496FD8E3AEFB6C9153250F0.email@example.com> 2021-12-22 14:51 ` Adam Thornton
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CANCZdfoggLNW=ip0Po8d07arpLr6urJKVsn7zy9H4XHDm46NQA@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [COFF] [TUHS] ksh88 source code?' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).