Hi linuxers,
Now the new AWZNode Homepage is at:
http://www.elecomsolutions.com/noze/software/awznode/
It's under construction, but downloading and support are
avalaible!
For support and informations, send an email to:
[EMAIL PROT
ort"?
The name of my port is "radio1" but the network device is named "scc0".
- Original Message -
From: Hamish Moffatt <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, July 07, 2000 7:30 AM
Subject: Re: Fw: NEW aprsd Linux APRS Server ready to download
>
> Modified version with Linux socket support available from
> http://aprs.cloud.net.au/aprsd.shtml
D]>
> To: "TAPR APRS Special Interest Group" <[EMAIL PROTECTED]>
> Sent: Thursday, July 06, 2000 11:10 AM
> Subject: [aprssig] NEW aprsd Linux APRS Server ready to download
>
>
> >
> > aprsd 2.1.2 is available for download at:
> >
> > http:/
FYI.
Bob N2KGO
- Original Message -
From: "Dale Heatherington" <[EMAIL PROTECTED]>
To: "TAPR APRS Special Interest Group" <[EMAIL PROTECTED]>
Sent: Thursday, July 06, 2000 11:10 AM
Subject: [aprssig] NEW aprsd Linux APRS Server ready to download
At 08:36 02/06/2000 -0400, Chuck Gelm wrote:
>I'm getting a blank screen at
>http://windowsupdate.microsoft.com
I think (based on my experience) that page didnot respond to browser other
than Microsoft Internet Explorer since there is a script to identify
installed MS Windows on your computer a
?
I'm getting a blank screen at
http://windowsupdate.microsoft.com
?
Chuck
Wahyu Kelik C wrote:
> But you can upgrade your windows (visit http://windowsupdate.microsoft.com)
> to find out what your Windows need for running well. My experience with
> Microsoft Windows 98 (SE) is still running (wi
- Original Message -
From: "Tomi Manninen OH2BNS" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 02, 2000 7:01 PM
Subject: Re: New install of linux
> On Fri, 2 Jun 2000, Shane Deering wrote:
>
> > I might leave RH 6.2 for a while or
On Fri, 2 Jun 2000, Shane Deering wrote:
> I might leave RH 6.2 for a while or make an extra partition for it and have
> it as a boot option while working with 6.1.
I wouldn't do that. I'd just go with RH6.2 and apply all the updates (that
is what you should do anyway with any distribution). App
- Original Message -
From: "Wahyu Kelik C" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 02, 2000 1:59 AM
Subject: Re: New install of linux
> At 00:27 01/06/2000 +1000, Shane Deering wrote:
> >It will look something like -
> >hda1 w
At 00:27 01/06/2000 +1000, Shane Deering wrote:
>It will look something like -
>hda1 windows
>hda2 (or 5) linux /
>hda3 (or 6) linux swap partition
>hdb1 linux /boot
>
>Q1/ Am I on the right track with the partitions?
Yes, you're right with the partitions.
Or You can share your Windows swap parti
- Original Message -
From: "Paulo Goncalves" <[EMAIL PROTECTED]>
To: "Shane Deering" <[EMAIL PROTECTED]>
Sent: Thursday, June 01, 2000 7:07 PM
Subject: Re: New install of linux
>
>
> On Thu, 1 Jun 2000, Shane Deering wrote:
>
> >
- Original Message -
From: "Geoff Blake" <[EMAIL PROTECTED]>
To: "Shane Deering" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, June 01, 2000 3:18 AM
Subject: Re: New install of linux
> On Thu, 1 Jun 2000, Shane Deering wrote:
&
On Thu, 1 Jun 2000, Shane Deering wrote:
> Hello people,
> All going well, I hope to install linux (redhat 6.1) onto my good
> computer. I've been playing with linux on a p100 with 16 meg of
> ram and it's been a real struggle to get all the ax25 stuff and
> everything else I want running without
Hello people,
All going well, I hope to install linux (redhat 6.1) onto my good
computer. I've been playing with linux on a p100 with 16 meg of
ram and it's been a real struggle to get all the ax25 stuff and
everything else I want running without it (almost) grinding to a halt.
I want to put linu
On Sun, 14 May 2000, Stewart Wilkinson wrote:
> Gerd wrote:
> > >
> > > Do you have a case where this leads to actual problems so we can see if
> > > something needs to be fixed?
> >
> > Yes, I am aware of such a case. You run into problems when a
> > user enters a node on L2, goes out on L2 aga
Gerd wrote:
>
> Hello Tomi, hello all,
>
> > LinuxNode only inverts the callsign if the user is coming in via a L2
> > connection and going out again on a L2 connection and on the _same_port_.
> > In all other cases users callsign-ssid is left untouched. When I coded
> > this I tried to think of
Hello Tomi, hello all,
> LinuxNode only inverts the callsign if the user is coming in via a L2
> connection and going out again on a L2 connection and on the _same_port_.
> In all other cases users callsign-ssid is left untouched. When I coded
> this I tried to think of all the possible cases a
On Fri, May 12, 2000 at 01:28:29PM +, Wilbert Knol wrote:
> The 4U1VIC entries aren't duplicates. One of them (the IAURU Headquarters
> entity) has the asterisk in front of it, indicating it is a separate entity *only*
>in
> CQWW contests. It is not a DXCC entity, and outside CQWW contests
Well, the SQL version of CTY.DAT loads perfectly and I wind up with the two
tables (country and prefix).
The ampersand continuation is indeed not used in CTY.DAT, but I notice it is
used in CQWW.CTY. However, CTY.DAT is the better one to use since it
contains all the info in one file.
The 4
On 09-May-2000 Hamish Moffatt wrote:
> Here's the schema (SQL, more generic this time):
>
> drop table country;
> create table country (
> prefix varchar(10) PRIMARY KEY,
> name varchar(26),
> timezone int2
> );
>
> drop table prefix;
> create table prefix (
On Tue, May 09, 2000 at 10:33:07PM -0400, Steve Dimse K4HG wrote:
> On 5/9/00 9:15 PM Wilbert Knol ([EMAIL PROTECTED]) wrote:
>
> >Hmmm. Somebody on some oddball IOTA island could still have a perfectly
> >ordinary callsign. You can't map prefix <-> IOTA, I think. Any award experts
> >amongs us
On 5/9/00 9:15 PM Wilbert Knol ([EMAIL PROTECTED]) wrote:
>Hmmm. Somebody on some oddball IOTA island could still have a perfectly
>ordinary callsign. You can't map prefix <-> IOTA, I think. Any award experts
>amongs us?
>
No, you can't. I live in NA-62, nothing special about my call...
Steve
> That's correct. I think a map of prefix->IOTA would be the most useful.
> That same information could be included in the existing prefix table.
Hmmm. Somebody on some oddball IOTA island could still have a perfectly
ordinary callsign. You can't map prefix <-> IOTA, I think. Any award experts
On Tue, May 09, 2000 at 04:58:40PM +0200, Ivo Simicevic wrote:
> On Tue, May 09, 2000 at 10:56:36PM +1000, Hamish Moffatt wrote:
> >
> > I would like to incorporate IOTA data. The challenge will be to
> > be able to import it into an already-populated database. Perhaps
> > it might be simpler to
> 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 t
On Tue, May 09, 2000 at 10:56:36PM +1000, Hamish Moffatt wrote:
>
> I would like to incorporate IOTA data. The challenge will be to
> be able to import it into an already-populated database. Perhaps
> it might be simpler to use a separate set of tables. More work
> at lookup time, though.
>
If
OK I've been working on the DXCC database again. The CTY.DAT format
is quite good and the web site seems to encourage other people to use
it, so I decided it would be OK.
Their format does allow lat/long, zones and continent to be overriden
on a per-prefix basis, with multiple prefixes per entit
you spend most of your spare time on this stuff while the download
> counter reaches the "100" mark. I really need more feedback.
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
L you have a tree structure -- and it is an open standard, even
a good one. XML support for perl, python, etc exist and only those who
_do_ understand XML will edit that thing by hand.
> Because I do not have the time to maintain everything on my own.
You don't have to. We will see wh
octet in an AX.25 frame is part of the destination
address, thus it has to be in [0-9A-Z ] shifted by one. If you
receive a frame beginning with it it's likely the new DDI, if you
receive one with a value of 0-31 it is almost certainly the old
interface. Of course only with a certain probability
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
On Tue, 2 May 2000, Kjell Jarl wrote:
> bpq can be set up to give welcome text to the node call as well, usually
> set off though. Some thenet nodes also gives welcome texts, debending on
> the set up, also over long distance (already established link level).
Ok, maybe I shouldn't have stressed
bpq can be set up to give welcome text to the node call as well, usually
set off though. Some thenet nodes also gives welcome texts, debending on
the set up, also over long distance (already established link level).
Depending on the program used, it has to be taken into account when
provideng the
Hi Tomi,
Thanks, I think this explains to me. I have not noticed any problems
though, and my users have not said anything - about not getting in at
least.
I have seen that welcome message, some time ago, but the connection has
went through. I cannot easilly test this as I almost all the time has
s
Howdy, Richard:
This doesn't answer your question, but...
It is really a 'remainder' rather than a decrement.
:-|
Outbound SSID = (15 minus inboundSSID)
-0 yields -15
-1 yields -14
-2 yields -13
...
-15 yields -0
Richard Bown wrote:
> While on the subject of SSID's being used, and while there i
On Tue, 2 May 2000, Richard Bown wrote:
> While on the subject of SSID's being used, and while there is plenty of
> responses.
> Has there been a fix in this release to decrement the SSID of a either a L2
> or L3 connection to the node, i.e. I login as g8jvm on someone else's
> system then do a
While on the subject of SSID's being used, and while there is plenty of
responses.
Has there been a fix in this release to decrement the SSID of a either a L2
or L3 connection to the node, i.e. I login as g8jvm on someone else's
system then do an outgoing L2 connection to another
station what I
9
> CTNODE:N8PS-2} Connected to DAYLAN-9
> Welcome to NC8Q's Packet Switch in Dayton
> Type ? for list of available commands.New I message 4/6/97"
>
> I think that the two lines above is my welcome message. I use BPQ.
Try doing the same connecting to
o NC8Q's Packet Switch in Dayton
Type ? for list of available commands. New I message 4/6/97"
I think that the two lines above is my welcome message. I use BPQ.
?
Chuck nc8q
> Ever wondered why node software like BPQ and TheNet never send a welcome
> message...? :-) (A
On Mon, 1 May 2000, Kjell Jarl wrote:
> I do the same, have both netrom and port call the same, and letting node
> respond to ax.25 user connects to the same SSID.
> It seems to work, and makes it obviuos for users what to connect to.
> Maybe some one could elaborate on why not to do it?
If you
On Sun, 30 Apr 2000, Charles E. Gelm wrote:
> I thought Naylor & Manninen said that it is 'dirty' code to allow
> L3 & L2 connect requests to the same CALLSIGN-SSID.
> I thought this couldn't be done in linux.
Nope. Never said that. It would be 'dirty' to add that kind of hackery to
Linux which
Hi!
I do the same, have both netrom and port call the same, and letting node
respond to ax.25 user connects to the same SSID.
It seems to work, and makes it obviuos for users what to connect to.
Maybe some one could elaborate on why not to do it?
73/Kjell
> The paragraph below is what I thought c
Chuck Gelm wrote:
> It seems that there is a lot of configuration to be done
> and a lot of useless CALLSIGN-SSID assignments.
>
> The paragraph below is what I thought could not be done:
> Have the node ALIAS:CALLSIGN-SSID respond to an AX.25 connect.
I think there are two crucial points:
Fir
Hi, John:
I thought Naylor & Manninen said that it is 'dirty' code to allow
L3 & L2 connect requests to the same CALLSIGN-SSID.
I thought this couldn't be done in linux.
Thanks a bunch. I'll give linux another look see.
It seems that there is a lot of configuration to be done
and a lot of usel
in 145.61 MHz and will check
> my heard list and node list in a few minutes to see if I can figure out what
> CALLSIGN-SSID would be accepting AX.25 circuits.
>
> Result after about one hour:
> The only CALLSIGN-SSID heard was W8APR-0.
> (OBTW, you have mail.)
>
> If you hadn&#x
that you are answering my question (1.) with a 'yes', but I am not
> > sure.
> >
> > I've read all my new mail today and see no answer regarding making
> > the 'AX.25 accepting CALLSIGN-SSID' manifest.
> >
> > I think an ALIAS-* can be
> Hi, John:
>
> Thanks.
>
> I think that you are answering my question (1.) with a 'yes', but I am not
> sure.
>
> I've read all my new mail today and see no answer regarding making
> the 'AX.25 accepting CALLSIGN-SSID' manifest.
>
Hi, John:
Thanks.
I think that you are answering my question (1.) with a 'yes', but I am not
sure.
I've read all my new mail today and see no answer regarding making
the 'AX.25 accepting CALLSIGN-SSID' manifest.
I think an ALIAS-* can be configured though and t
Hi, Richard:
Let me redefine my use of the word 'intuitive';
perhaps I could use 'overt', 'obvious', 'manifest', 'immediately evident',
(one of my favorites) 'intuitively obvious to the casual observer'.
I want the CALLSIGN-SSID that is accepting AX.25 circuits to the BBS to be
'made known' to
On Thu, 27 Apr 2000, Charles E. Gelm wrote about, Re: Question, was; [ANNOUNCE]
new-AX.25 for 2.2.14 Rel. 5:
> Hi, Richard et allia:
>
> I probably didn't give enough information in my original post.
>
> I am assuming that everyone in 'linux-hams' is familiar
Hi Chuck --
I think that you can configure Linux AX.25 to do what you want.
The secret is that although you do need to assign a unique call/SSID to
each physical port, those calls do not have to be used by the application
or its users. If I recall correctly, you can configure so that the only
p
Hi, Richard et allia:
I probably didn't give enough information in my original post.
I am assuming that everyone in 'linux-hams' is familiar with
'NetRom', 'TheNet' and 'BPQ node' application. I use packet BBS
software authored by AA4RE. A mention is made to the node function
in the MSYS BBS p
> I'm not sure that pre-built packages would be a good thing. Jens may
> disagree but I believe these new things are to try out and debug rather
> than just install and play.
Nope, I agree completely. As long as there´s no real documentation for this
time to build RPMs/DEBs/whateve
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
On Fri, 21 Apr 2000, Chuck Gelm wrote about, Re: [ANNOUNCE] new-AX.25 for 2.2.14
Rel. 5:
> Howdy, Y'all:
>
> Does AX.25 for linux still require a unique CALLSIGN-SSID
> for each packet radio port?
Normally speaking here in EU land, its required that one uses a callsign to
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 reall
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 discu
PGP message
want to get to Y.
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.
On Wed, Apr 26, 2000 at 11:17:52PM +0200, Jens D
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 a
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 backwar
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
his "channel-access thing" affects more than low-level
driver interfaces. It affects the whole LAPB state machine structure. That´s
why Mat´s (mostly) rewrite was the right thing (tm) to do.
Finally, we are doing this for fun and education, aren´t we?
> > Some developers talk, some ac
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, j
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 t
ility issues are not that important.
I wasn't talking about compatibility issues (which are important also of
course) or which implementation is better. I was talking about attitudes.
(Actually the new-ax25 stuff looks very nice, I do believe it's better in
many ways and I'm sad
ack to those of us who have written the
> old code!
Some developers talk, some actually develop something .. :)
(just my opinion about new-ax25 discussion ..
don't take personaly (anyone))
And well.. if you want to give feedback .. just do it now!
This is why new versions are released, don
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 scr
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
e and
> > there are some nasty bugs I nailed down I decided commit the
> > release now.
> > It consists of
> >
> > - the kernel patch
> > - new libax25 (in fact this did not change but I renamed it
> > for consistency issues)
> > - new ax25-tools
&g
ailed down I decided commit the
> release now.
> It consists of
>
> - the kernel patch
> - new libax25 (in fact this did not change but I renamed it
> for consistency issues)
> - new ax25-tools
> - new ax25-apps
Urgh, are they backwards compatible? In other words will these n
ED]>
Date: Sunday, April 23, 2000 1:28 PM
Subject: [ANNOUNCE] new-AX.25 for 2.2.14 Rel. 5
>Hi all,
>
>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
patch
- new libax25 (in fact this did not change but I renamed it
for consistency issues)
- new ax25-tools
- new ax25-apps
Get the packages from
http://dl0td.afthd.tu-darmstadt.de/~dg1kjd/linux-ax25/index.html
http://dl0td.rmn.de.ampr.org/~dg1kjd/linux-ax25/index.html
Changes:
- Fixed LAPB state
On Thu, 13 Apr 2000, you wrote:
> Hi,
>
> I am using REDHAT 6.1 Linux installation with kernel 2.2.12-20.
> I downloaded and compiled OK the kernel 2.2.14 but I am having
> problem installing the new kernel. Can someone point me the steps
> to install a new kernel in REDHAT 6.
On Thu, 13 Apr 2000, Jose Ng Lee wrote about, new kernel installation:
> Hi,
>
> I am using REDHAT 6.1 Linux installation with kernel 2.2.12-20.
> I downloaded and compiled OK the kernel 2.2.14 but I am having
> problem installing the new kernel. Can someone point me the steps
Hi,
I am using REDHAT 6.1 Linux installation with kernel 2.2.12-20.
I downloaded and compiled OK the kernel 2.2.14 but I am having
problem installing the new kernel. Can someone point me the steps
to install a new kernel in REDHAT 6.1? I try changing the lilo.conf to
the new vmlinuz and using
On Sat, 1 Apr 2000, Barrett, Peter G wrote:
> > VIRUS WARNING
[snip]
And of course, it makes you inardinately attractive to members of the
opposite sex!
Te He
Geoff
--
Geoff Blakegeoff @ palaemon . co . uk linux 2.0.36
Chelmsford g8gnz @ g8gnz . ampr .
MAN
I just knew it. Bate the bull and he will come charging.
We just got through a whole series of exchanges where
wounded Linux supporters educated the universe to the fact
that Linux was virus proof.
Ya, okay, what else is new?
I ended up reading more email about the wonders of Linux
NEXT TIME YOU TAKE DRUGS, TAKE THOSE YOUR PSYCHIATRISTS PRESCRIBES !
"Barrett, Peter G" wrote:
>
> > VIRUS WARNING
> >
> > If you receive an e-mail entitled "crazy times" DELETE IT IMMEDIATELY AND
> > DO NOT OPEN IT!!! Apparently this one is pretty nasty. It will not only
> > erase everything on
> VIRUS WARNING
>
> If you receive an e-mail entitled "crazy times" DELETE IT IMMEDIATELY AND
> DO NOT OPEN IT!!! Apparently this one is pretty nasty. It will not only
> erase everything on your hard drive, but it will also delete everything on
> disks within 20 metres of your computer. It demag
I'm running Twpsk on my linux mandrake 2.2.14 kernel...lovin it!
Works slick...like trout!
- Original Message -
From: Geoff Bagley <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, March 16, 2000 2:46 AM
Subject: DSP and new modes.
>
> I wonder whethe
rch 18, 2000 5:32 PM
Subject: RE: DSP and new modes.
>Does anyone know where you can buy the Motorola EVM56002DSP?
>
>Thanks,
>Mike (KE4RNB)
>
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]]On Behalf Of Geoff Bagley
>Sent: Thursday,
Does anyone know where you can buy the Motorola EVM56002DSP?
Thanks,
Mike (KE4RNB)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Geoff Bagley
Sent: Thursday, March 16, 2000 1:47 AM
To: [EMAIL PROTECTED]
Subject: DSP and new modes.
I wonder whether
I wonder whether any hams on this list are using LINUX to drive the
Motorola EVM56002DSP, or have implemented any modern (DSP-based) modes
such as PSK31 ?
73
--
Geoff Bagley
G3FHL +?
Hi Jens,
sorry, took a while to respond. I haven't found the time to actually
test it, but I've skimmed over the patch. As far as I can see it
looks fine, but I've some remarks.
- Have you seen the solution for ax25_info in 2.3.x? That way it's
possible to easily remove support for the old str
Hi all,
a little bit later than promised it is finally there...
You can get the patch and the tools from the same place
as usual:
http://www.afthd.tu-darmstadt.de/~dg1kjd/linux-ax25/index.html
This release introduces some new features:
- DAMA slave code
- _All_ devices should be functional
Hi folks,
this is the next try to start declaring parts of the existing API for
AX.25 sockets obsolete. The following patch:
- issues a warning if someone uses struct sockaddr_ax25 for
bind(), connect() and sendmsg()
- issues a warning if someone uses old struct full_sockaddr_ax25 with
place
> > Binding to interfaces has an API already (see the IP space)
> > SO_BINDTODEVICE
>
> Can you point me to an example how that works from the application point
> of view? How does setting this option interact with bind(), for example?
> The good news: it looks as if the comment in front of ax25
Hi Alan,
thank you for the reply.
> 1003.1g says the user is entitled to use any buffer size they like and
> get half a sockaddr back. Going the other way (eg connect) we are quite
> in the right to require the full sockaddr.
Don't worry, I wasn't going to touch ax25_getname() and ax25_recvmsg(
gt; >
> > - Original Message -
> > From: Chuck Gelm <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: 02 March 2000 19:49
> > Subject: Re: NEW-AX.25: Starting to clean up socket API
> >
> > > Howdy, Y'all:
>
Howdy, Jean-Paul:
Interesting. I had no idea. Around here we use clones of 'NET/ROM'.
G8BPQ, THENET/X1J, MSYS, and such. I know of no flex, rose, or fpac
within 100 kilometers. :-|
73, Chuck nc8q
Jean-Paul ROUBELAT wrote:
>
> From: Chuck Gelm <[EMAIL PROTECTED]>
>
> > Howdy, Y'all:
> >
>
> - Original Message -
> From: Chuck Gelm <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: 02 March 2000 19:49
> Subject: Re: NEW-AX.25: Starting to clean up socket API
>
> > Howdy, Y'all:
> >
> > IMHO, digipeating is obsolete.
> the existing API for AX.25 sockets is a bit too liberal concerning
> the size of the sockaddr structure. It makes the code hard to read
> (thus difficult to maintain) and almost impossible to implement
> alternative ideas. In fact, we have three different structures to
> choose from:
1003.1g sa
- Original Message -
From: Chuck Gelm <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: 02 March 2000 19:49
Subject: Re: NEW-AX.25: Starting to clean up socket API
> Howdy, Y'all:
>
> IMHO, digipeating is obsolete.
Is it? Then how will APRS systems work t
From: Chuck Gelm <[EMAIL PROTECTED]>
> Howdy, Y'all:
>
> IMHO, digipeating is obsolete.
Digipeating is maybe obsolete but digipeater fields are not. They are mainly
used for routing information within networks (flex, rose, fpac, etc...)
>
> 73, Chuck nc8q
>
>
> Joerg Reuter wrote:
> >
> > Hi fo
Howdy, Y'all:
IMHO, digipeating is obsolete.
73, Chuck nc8q
Joerg Reuter wrote:
>
> Hi folks,
>
> the existing API for AX.25 sockets is a bit too liberal concerning
> the size of the sockaddr structure. It makes the code hard to read
> (thus difficult to maintain) and almost impossible to im
1 - 100 of 414 matches
Mail list logo
