From: corey@lod.com (Corey Lindsly)
Subject: [TUHS] Questions for TUHS great minds
Date: Wed, 11 Jan 2017 09:01:12 -0800 (PST) [thread overview]
Message-ID: <20170111170112.6D81840FC@lod.com> (raw)
In-Reply-To: <608e82b3a875c499f5e63e776886337a@xs4all.nl>
>
> On 2017-01-11 17:25, Ron Natalie wrote:
> > Somewhere I have an etherkiller (unfortunately it is non functional).
>
> FTFY
>
I don't think so. RJ-11? More like a telephone killer, or home
firestarter.
--corey
next prev parent reply other threads:[~2017-01-11 17:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 2:33 Robert Swierczek
2017-01-11 16:25 ` Ron Natalie
2017-01-11 16:50 ` Jacob Goense
2017-01-11 17:01 ` Corey Lindsly [this message]
2017-01-11 17:54 ` Marc Rochkind
2017-01-11 20:32 ` Jacob Goense
2017-01-11 18:34 ` Steve Johnson
2017-01-11 19:46 ` Steffen Nurpmeso
2017-01-17 13:09 ` Tim Bradshaw
2017-01-17 13:36 ` Michael Kjörling
2017-01-17 19:55 ` Steve Johnson
2017-02-01 23:32 ` Erik E. Fair
2017-01-17 14:27 Nelson H. F. Beebe
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=20170111170112.6D81840FC@lod.com \
--to=corey@lod.com \
/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;
as well as URLs for NNTP newsgroup(s).