From: Damien Gardner Jnr <rendrag@rendrag.net>
To: Patrick Ouellette <pat@flying-gecko.net>
Cc: Dan Smith <dsmith@danplanet.com>,
linux-hams@vger.kernel.org, debian-hams@lists.debian.org,
ralf@linux-mips.org, ax25@x-berg.in-berlin.de
Subject: Re: AX25 and related software's future in Debian
Date: Sat, 05 May 2012 08:52:17 +1000 [thread overview]
Message-ID: <4FA45DA1.8090602@rendrag.net> (raw)
In-Reply-To: <20120504151424.GC24655@flying-gecko.net>
On 5/05/2012 1:14 AM, Patrick Ouellette wrote:
> Dan,
>
> Playing Devil's advocate - the argument has been put forth in the
> "other discussion" that according to popcon (the Debian popularity
> contest), node has 81 installs, and 17 reporting as "active" while the
> nodejs package has 720 installs with 163 reporting as "active." So their
> conclusion is the node package is only used by a small community.
>
Does anyone actually USE popcon though? I dunno about you, but I have
~400 debian boxes in use around my clients, and NONE are participating
in popularity contest.. - Having the server info + installed packages
sent off to some off-site location is a security risk, and a stumbling
block on the way to PCI Compliance. That and it just seems
microsoft-style creepy!
I don't think you can honestly expect to use popcon as a valid indicator
to the ax25 packages' install base.. - Much like you couldn't expect it
to be valid for snort, acidbase, or other tools used in a secure
environment? (Which a ham radio node needs to be, to maintain the
separation of ham-tcpip and public-tcpip networks).
Regards,
Damien
--
Damien Gardner Jnr
VK2TDG. Dip EE. GradIEAust
rendrag@rendrag.net - http://www.rendrag.net/
--
We rode on the winds of the rising storm,
We ran to the sounds of thunder.
We danced among the lightning bolts,
and tore the world asunder
next prev parent reply other threads:[~2012-05-04 22:52 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 1:32 AX25 and related software's future in Debian Patrick Ouellette
2012-05-04 1:46 ` Dave Platt
2012-05-04 2:10 ` Patrick Ouellette
2012-05-04 1:53 ` Kamal Mostafa
2012-05-04 2:03 ` Charles Suprin
2012-05-04 2:17 ` Patrick Ouellette
2012-05-04 2:20 ` Alejandro Santos
2012-05-04 5:20 ` Kim, VK5FJ
2012-05-04 14:34 ` Patrick Ouellette
2012-05-04 14:06 ` Dan Smith
2012-05-04 15:14 ` Patrick Ouellette
2012-05-04 15:35 ` Dan Smith
2012-05-04 16:28 ` Steve Kostecke
2012-05-04 16:57 ` Patrick Ouellette
2012-05-04 17:50 ` Bill Vodall
2012-05-04 18:06 ` Patrick Ouellette
2012-05-04 18:32 ` Dan Smith
2012-05-04 18:49 ` Patrick Ouellette
2012-05-04 19:01 ` Dan Smith
2012-05-04 19:31 ` Patrick Ouellette
2012-05-04 22:52 ` Damien Gardner Jnr [this message]
[not found] ` <CAPSBm51zYFpfPa0Rqvjemv4KGh-NQfFmFTcW07B8KzpTK_E8bw@mail.gmail.com>
2012-05-05 3:00 ` Kris Kirby
2012-05-05 13:33 ` Thomas Osterried
2012-05-23 18:15 ` Wesley J. Landaker
2012-05-23 20:38 ` Nate Bargmann
2012-05-23 22:48 ` Damien Gardner Jnr
2012-05-24 12:18 ` C.J. Adams-Collier
2012-05-24 12:33 ` IT1 Stuart Blake Tener, USNR
2012-05-24 23:05 ` Marius Petrescu
2012-05-24 23:29 ` IT1 Stuart Blake Tener, USNR
2012-05-25 0:02 ` Marius Petrescu
2012-05-25 0:04 ` Marius Petrescu
2012-05-25 0:56 ` Bob Nielsen
2012-05-25 1:46 ` Nate Bargmann
[not found] <S1754044Ab2EQTsl/20120517194841Z+66@vger.kernel.org>
2012-05-17 20:03 ` Charles Boling (AD7UF)
2012-05-17 20:25 ` John Goerzen
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=4FA45DA1.8090602@rendrag.net \
--to=rendrag@rendrag.net \
--cc=ax25@x-berg.in-berlin.de \
--cc=debian-hams@lists.debian.org \
--cc=dsmith@danplanet.com \
--cc=linux-hams@vger.kernel.org \
--cc=pat@flying-gecko.net \
--cc=ralf@linux-mips.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.