From: Cathryn Mataga <cathryn@junglevision.com>
To: linux-hams <linux-hams@vger.kernel.org>
Subject: Re: Netrom on kernel version 3.9.6-200
Date: Fri, 05 Jul 2013 22:42:03 -0700 [thread overview]
Message-ID: <51D7AE2B.3070408@junglevision.com> (raw)
In-Reply-To: <51D7AC41.6060606@junglevision.com>
On 7/5/2013 10:33 PM, Cathryn Mataga wrote:
> On 7/5/2013 9:43 PM, Cathryn Mataga wrote:
>> On 7/5/2013 9:19 PM, Cathryn Mataga wrote:
>>> Hmm, is netrom known to work? I'm on 3.9.6-200, and I'm getting
>>> weird results with netrom.
>>>
>
> Wait, wait, this is definitely a Fedora issue and not a kernel issue.
> Because I copied in nrattach that I compiled myself and it started
> correctly. (I don't think it's a 'old versions of libax25 lying
> around issue' but I haven't completely ruled that out yet.)
Wait a minute. Someone has been mucking about with nrattach.c . They
removed the the code that actually connects the netrom port. Bahh..
#ifdef notdef
if (!startiface(dev, hp))
return 1;
#endif
next prev parent reply other threads:[~2013-07-06 5:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-06 4:19 Netrom on kernel version 3.9.6-200 Cathryn Mataga
2013-07-06 4:43 ` Cathryn Mataga
2013-07-06 5:33 ` Cathryn Mataga
2013-07-06 5:42 ` Cathryn Mataga [this message]
2013-07-06 17:24 ` David Ranch
2013-07-06 18:32 ` Cathryn Mataga
2013-07-06 20:28 ` Thomas Osterried
2013-07-07 5:49 ` Cathryn Mataga
2013-07-07 6:08 ` Netrom: Quality issue Cathryn Mataga
2013-07-07 16:59 ` David Ranch
2013-07-07 18:45 ` Cathryn Mataga
2013-07-08 3:40 ` David Ranch
2013-07-08 3:49 ` Cathryn Mataga
2013-07-08 7:48 ` Thomas Osterried
2013-07-08 13:24 ` Cathryn Mataga
[not found] <20130708115635.A4B233700A5@n1uro.ampr.org>
[not found] ` <51DABEDA.8020905@junglevision.com>
[not found] ` <1373314487.13641.19.camel@n1uro.ampr.org>
2013-07-09 4:37 ` Netrom on kernel version 3.9.6-200 Cathryn Mataga
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=51D7AE2B.3070408@junglevision.com \
--to=cathryn@junglevision.com \
--cc=linux-hams@vger.kernel.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.