| |
DL6RAI > UNIX 01.03.96 01:12l 99 Lines 4083 Bytes #999 (0) @ WW
BID : T26DB0AAB01C
Read: GUEST
Subj: CLX version 2.03 released!
Path: DB0AAB
Sent: 960229/2210z @:DB0AAB.#BAY.DEU.EU [Muenchen/Fachhochschule] bcm1.37f
From: DL6RAI @ DB0AAB.#BAY.DEU.EU (Ben)
To : UNIX @ WW
Hello friends,
A new version of CLX was released today. It was uploaded to
gonzo.rrze.uni-erlangen.de in the evening of February 29, 1996.
I hope the archive maintainers will soon find the time to move
the files to the appropriate directories so you will find the
following files:
upd_203.tgz (1812702 Bytes)
install.txt (11317 Bytes)
README_2.03 (3273 Bytes)
gonzo.rrze.uni-erlangen.de:/pds/freeware/hamradio/packet/packclus/clx
ftp.funet.fi:/pub/ham/unix/Linux/cluster
The new version contains bug fixes and corrections to the documentation.
Here are some details:
!!! We have now decided to go for differential updates
!!! which means that you just download the clx_200.tgz
!!! and then update it with this file. The new upd_203.tgz
!!! will contain all of the intermediate updates 2.01
!!! and 2.02.
As development is mostly within the binaries, it seemed reasonable to
do this. If you have a 2.01 or 2.02 installation you can just unpack the
update and it will not destroy anything (I hope so - you better have a
backup).
*** CHANGES ***
Only minor changes and bug fixes this time. We intended to come up
with a new feature which we call the "User Mode Protocol". However,
a major problem was discovered with one new program and it was too
late to fix it. So you will have to wait for this probably until the
next release.
- Hop counter for WWV telegrams may be set from the ~/config/clx_par
file. Using the keyword `wwv' (analogous to `dx', `ann', `user' and
`node').
- ~/bin/net_usr can not be used from another computer. Use the -h option
to specify the host where clx actually runs. Also a new ~/bin/clxsh is
provided for WAMPES. If WAMPES and clx are running on different hosts,
you must also specify w_host in the configuration file ~/config/clx_par.
- minor bug in conference mode fixed. Users are now deleted from the
conference when the AX.25 connection is lost. Also when no conference
name is specified, the conference will be named after the call of your
node.
- You can now start sending the message content right after the SEND
command. Also you can now start sending messages after entering the command
for TALK MODE. As several processes are doing their job here, they
had to be synchronized. You can now exit TALK mode with "ctrl-Z",
or "/exit".
- New command SHOW/STATION. New command SET/LOCATION. You can enter
geographical coordinates or Maidenhead QTH locator. The data will
be converted to degrees and minutes internally. SET/NAME and SET/QTH
now understands 8-bit characters.
- QRZ DX access now works with the new CD (Volume 6). The data format
was changed. CLX understands both.
- New program ~/bin/clxd (in fact a perl script) to make CLX access
available via `telnet'. See :
- ~/tools/us_adm was extended so that you now can add and delete users
to the database. They do not have to login before you may change
anything - you can go right ahead after the installation.
- Some silly problem fixed with ~/bin/clx checking if the callsigns
specified with axattach and the node call were identical. This test
lead to numerous people complaining that it would not work sometimes
giving strange responses. The problem is that when axattach is sleeping
it is shown as "(axattach)" in the ps table - without arguments. So there
was no way to find out with which callsign axattach was started. I have
now simply eliminated this test. You are on your own here. If the
two calls don't match, clx will not run and there is no warning - sorry!
- If you can print postscript, there is a file ~/doc/misc/clx.ps which
shows how the clx software is structured. Take a look at it, you will
be shocked!
---------------------------------------------------------------------
PROGRAMMERS WANTED
We are trying to find some people to help us with several programming
tasks (this is what they call `outsourcing', right?). Can you write
C code and are willing to join us? Please let us know!
---------------------------------------------------------------------
73 Ben
Read previous mail | Read next mail
| |
