Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Christopher Waid <chris@thinkpenguin.com>
Cc: make-wifi-fast@lists.bufferbloat.net,
	cerowrt-devel@lists.bufferbloat.net,
	fcc@lists.prplfoundation.org
Subject: Re: [Cerowrt-devel] [FCC] some comments from elsewhere on the lockdown
Date: Wed, 30 Sep 2015 16:51:36 -0400	[thread overview]
Message-ID: <21167.1443646296@turing-police.cc.vt.edu> (raw)
In-Reply-To: <c4cfac093cff8fefa8cd763dab8f04a0@thinkpenguin.com>

[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]

On Wed, 30 Sep 2015 16:11:38 -0400, Christopher Waid said:

> > Apparently, they were of the opinion that the mere fact that I might
> > die of a heart attack a year after distributing something doesn't
> > excuse me from complying.)
>
> I don't know if it does excuse you from complying, but I say good luck
> to the person trying to get it enforced.

They could quite possibly hassle the executor of my estate if they were
sufficiently determined.

But given that abandonware (both software and hardware) is a big chunk
of the problem, we really *do* need to address the problem of companies
that can't provide patches because they've gone under.  Possibly a
requirement that they open-source the hardware/software if possible?
(That's another can-o-worms - consider that a big chunk of why NVidia
doesn't open-source their proprietary graphics drivers is because there's
a lot of OpenGL-related patents and trade secrets that Microsoft bought when
there was the big fire sale when SGI got out of the graphics market - so
it's quite possible that a vendor *can't* open-source it when they go
under due to licensing issues...)

[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]

  parent reply	other threads:[~2015-09-30 20:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 19:49 [Cerowrt-devel] " Dave Taht
2015-09-25 20:16 ` David P. Reed
2015-09-25 21:40   ` Dave Taht
2015-09-26  1:08     ` David P. Reed
2015-09-30 19:56     ` Valdis.Kletnieks
     [not found]       ` <c4cfac093cff8fefa8cd763dab8f04a0@thinkpenguin.com>
2015-09-30 20:51         ` Valdis.Kletnieks [this message]
2015-10-01 10:33           ` [Cerowrt-devel] [FCC] " David P. Reed
2015-10-01 11:15             ` Dave Taht
2015-10-02 14:22               ` [Cerowrt-devel] Editorial questions for response to the FCC Rich Brown
2015-10-02 20:21                 ` dpreed
2015-09-26  9:46 ` [Cerowrt-devel] some comments from elsewhere on the lockdown Laurent GUERBY

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=21167.1443646296@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=chris@thinkpenguin.com \
    --cc=fcc@lists.prplfoundation.org \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox