From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Smith Subject: Re: AX25 and related software's future in Debian Date: Fri, 04 May 2012 11:32:34 -0700 Message-ID: <4FA420C2.2060308@danplanet.com> References: <20120504151424.GC24655@flying-gecko.net> <20120504165706.GD24655@flying-gecko.net> <20120504180621.GB6444@flying-gecko.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigFD56340064703B1B7D44E609" Return-path: In-Reply-To: <20120504180621.GB6444@flying-gecko.net> Sender: linux-hams-owner@vger.kernel.org List-ID: To: Patrick Ouellette Cc: Bill Vodall , linux-hams@vger.kernel.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigFD56340064703B1B7D44E609 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable > Not seeing anything particularly well suited to ax25 networks there, > or anything particularly unique in general. Not sure I'd agree there. If whatever you're running AX.25 on is suitable for HTTP, then Node.js would be of potential use as well. I'd surely vote to avoid a "Conflicts: resolution" (pun intended). --=20 Dan Smith www.danplanet.com KK7DS --------------enigFD56340064703B1B7D44E609 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBAgAGBQJPpCDCAAoJEBeZxaMESjNVEccH/jt3HiQmx8lzGHIYYU7o3ITw N/iwOirp40c5fQXXWZYjIdUkYlKzhlXtG6iWY2Q8Ai0wOpciOgGS7CsEAm98yhad VXWxN1NYteU1R+k1JvRjZe+JCUt8qyaae+sdX/AMgeBtDBlXf8gPlASMctKvmECw Kiqe5QHOFhq39F79tdZ6gsNE1ychUYtrwm58Ajn2Ul/TRz9ua81rzwmrRDg3XPen 7zkus+wFqkm+aqRzlrGFoS0Sd8718FWJQlyCUr0pK1aDOT6psWXIRmMEuUM+HI5Q n+1kYE2y8ht6BIkbTLvlK7m2z/sP0nsmbQuvPKJl2JnC/XqLPzmkJ7ndm9lJEY4= =WDXu -----END PGP SIGNATURE----- --------------enigFD56340064703B1B7D44E609--