> As a SysOp and an User I think if the YAM driver was ported to work with
> this new AX.25 package, many persons would be tempted to try it out.
> That's because it is a modem widely used.
> I would like to test it at home but I only have 1 Baycom and 2 YAMs.
Ummm... does that mean that the
On Wed, 26 Apr 2000, Jens David wrote:
> I definetely do not think I know the answers to everything. In fact I love
> to say "I know that I know nothing". I´m studying ee, not cs, so there are
> surely a lot people who have more knowledge and better ideas than me. That´s
> why I did that posting
[Still catching up on e-mail]
> This is surely an interesting idea as long as things are concerned
> which are not updated very frequently (i.e. not speed critical stuff).
> But all routing stuff should be done via netlink interface, shouldn´t it?
I'd like to be able to add and remove static rou
> > there is no prepending KISS command byte anymore. That's
> > annoying, but only affects very few tools: AFAIK only listen, net2kiss
> > and ax25rtd. The later will use the netlink interface, I don't know
>
> And some applications -- aprsdigi, aprsmon, aprsd at least.
Hmm, I don't know anythi
Tomi wrote:
> The original reason for axports was that interfaces could only be
> differentiated by the interface callsign. There was no way to tell the
> kernel to "open a connection through device ax0". It needed to be done
> by telling the kernel to "open a connection through the interface hav
Craig Small wrote:
> It sounds like you are re-writing an awful lot, that's fine too. If you
> are removing ioctls, let's add the new ones in leave the old ones there
> then remove the old ones. Look at what was done with ipchains/ipfwadm.
Of cause. Here the same rules apply as with the socket A
Howdy, Y'all:
Does AX.25 for linux still require a unique CALLSIGN-SSID
for each packet radio port?
Is there an AX25-HOWTO for a 2.2.x kernel ?
Chuck nc8q
a.k.a. Joe Packet
Richard Adams wrote:
> Gentelmen, we all know that everyone is free to change what he/she wants
> to, but once again
On Thu, 27 Apr 2000, Jens David wrote:
> > The later will use the netlink interface, I don't know
> > how to fix net2kiss for the new DDI, and listen can easily be tweaked
> > to work with all kernels.
>
> As I said, listen is already done, but net2kiss really puzzles me.
> Maybe AF_AX25, SOCK_D
On Wed, 26 Apr 2000, Jens David wrote:
> please calm down and let us deal with this on the facts. It was definetely
> not my intention to start another flamewar when I did that announcement.
Neither did I. Sorry if I seemed a little too exited earlier.
> Fact is, nobody else but Jan and Joerg c
Who said it does'nt matter, but someone said in a reply mail to linux-hams.
> > Some developers talk, some actually develop something .. :)
> > (just my opinion about new-ax25 discussion ..
> > don't take personaly (anyone))
Normally i dont get involved in discusiions about how development shoul
I thought I better first up say that I have not looked at the
implementation, is it better or not (though I totally agree that the way
things are done is suboptimal and would like to see sounthing like
iproute if ifup/ifdown scheme). My only problem is a migration
strategy. We are at X and we wa
Joerg Reuter wrote:
>
> Oh my, here we go again...
>
> > Of cause the new kernel needs new tools which will not work with
> > the old kernel.
>
> We need to differ between the tools, the applications and the library.
> My idea is to get rid of some programs altogether (axparms for example)
> an
Craig Small wrote:
>
> On Wed, Apr 26, 2000 at 11:57:00AM +0200, Jens David wrote:
> > Of cause the new kernel needs new tools which will not work with
> > the old kernel. That´s why I released seperate distributions. I
> > orginally wanted to keep the new tools backward compatible. I modified
>
On Wed, Apr 26, 2000 at 07:32:06PM +0200, Joerg Reuter wrote:
> We need to differ between the tools, the applications and the library.
> My idea is to get rid of some programs altogether (axparms for example)
> and provide the functionality through procfs. Some tools (those that
> use AF_PACKET to
Gentlemen,
please calm down and let us deal with this on the facts. It was definetely
not my intention to start another flamewar when I did that announcement.
Tomi Manninen wrote:
>
> On Wed, 26 Apr 2000, Jan Wasserbauer wrote:
>
> > I have to support Jens since I think nex-Ax25 support is muc
On Wed, Apr 26, 2000 at 09:47:25PM +1000, Craig Small wrote:
> On Wed, Apr 26, 2000 at 11:57:00AM +0200, Jens David wrote:
> > Of cause the new kernel needs new tools which will not work with
> > the old kernel. That´s why I released seperate distributions. I
>
> OK, just so I know when to expect
Oh my, here we go again...
> Of cause the new kernel needs new tools which will not work with
> the old kernel.
We need to differ between the tools, the applications and the library.
My idea is to get rid of some programs altogether (axparms for example)
and provide the functionality through pr
On Wed, 26 Apr 2000, Jan Wasserbauer wrote:
> I have to support Jens since I think nex-Ax25 support is much better (and
> what is done so far greatly proves that).
>
> Have in mind we're talking about Ax25 for 2.5/2.6 kernels .. (or patched
> 2.2/2.4 of course) so compatibility issues are not th
I have to support Jens since I think nex-Ax25 support is much better (and
what is done so far greatly proves that).
Have in mind we're talking about Ax25 for 2.5/2.6 kernels .. (or patched
2.2/2.4 of course) so compatibility issues are not that important.
On Wed, 26 Apr 2000, Tomi Manninen OH
On Wed, Apr 26, 2000 at 11:57:00AM +0200, Jens David wrote:
> Of cause the new kernel needs new tools which will not work with
> the old kernel. That´s why I released seperate distributions. I
> orginally wanted to keep the new tools backward compatible. I modified
> the autoconf scripts so that t
On Wed, 26 Apr 2000, Jens David wrote:
> My future plans are the following:
> I will mostly rework the complete packages. There is a lot of conceptionally
> wrong stuff in there like dependencies on the stupid axports file and
> /proc/*-Entries.
>
> Also, I will remerge ax25-tools and -apps (I d
Craig will there be RPM versions available, for us lazy people that use them
?
And Jens, I disagree with flexnet wheel !
-Original Message-
From: Jens David [mailto:[EMAIL PROTECTED]]
Sent: 26 April 2000 10:57
To: [EMAIL PROTECTED]
Subject: Re: [ANNOUNCE] new-AX.25 for 2.2.14 Rel. 5
Craig Small wrote:
>
> On Sun, Apr 23, 2000 at 01:16:23PM +0200, Jens David wrote:
> > I´m happy to announce the 5th attempt of DG2FEF/DG1KJD AX.25
> > for Linux 2.2.14. I originally intended to wait until 2.2.15,
> > but since it seems there are some delays on its release and
> > there are some
On Sun, Apr 23, 2000 at 01:16:23PM +0200, Jens David wrote:
> I´m happy to announce the 5th attempt of DG2FEF/DG1KJD AX.25
> for Linux 2.2.14. I originally intended to wait until 2.2.15,
> but since it seems there are some delays on its release and
> there are some nasty bugs I nailed down I decid
Dear Hams,
Reading this memo, i see a driver for PCISCC-4 card. Is this card in
production (yet?) , or is this beta ?
Anyone working with this card .?.
Regards,
PD1ACF
Ron Jochems
-Original Message-
From: Jens David <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date:
25 matches
Mail list logo
