| |
VE4KLM > WW 17.09.26 18:00l 89 Lines 3307 Bytes #999 (0) @ WW
BID : C2DHG_VE4KLM
Subj: test setup [ full info, not the internet link ]
Path: IZ3LSV<IK6IHL<IK7NXU<HB9ON<HB9ON<PI8ZTM<VE3CGR<VE3TOK<VE3MCH<VE4KLM
Sent: 260917/1331z @:VE4KLM.#WPG.MB.CAN.NOAM [Winnipeg] $:C2DHG_VE4KLM
Create a JNOS 2.0 test environment
mkdir /jnos
cd /jnos
wget https://www.langelaar.net/jnos2/live/mercnos.tar.gz --no-check-certificate
mkdir rte
cd rte
tar xvzf ../mercnos.tar.gz
# replace my callsign with your callsign, no SSID, just the callsign
find . -type f -exec sed -i 's/ve4klm/yourcall/g' {} \;
Compile JNOS 2.0 binaries and install into test environment
cd /jnos
rsync -av www.langelaar.net::official/2.0q .
cd 2.0q
./configure
make
mv jnos ../rte
mv jnospwmgr ../rte
Compile Mercury V2 on the same linux box hosting JNOS 2.0
cd /jnos
wget https://github.com/Rhizomatica/mercury/archive/refs/heads/mercuryv2.zip --no-check-certificate
unzip mercuryv2.zip
cd mercury-mercuryv2
make clean
make
make install
Run Mercury Software and configure/run with a browser
bring up another terminal
cd /jnos/mercury_mercuryv2
mercury
bring up a web browser and visit localhost:10000
set your sound cards, and your PTT configuraton, apply all changes
leave the browser running, it's your waterfall and monitor now
* the browser creates the mercury.ini when you apply changes,
so there is no need to hand edit the file .. I did not ...
Run JNOS 2.0
bring up another terminal
cd /jnos/rte
./jnos
you are now in the JNOS program. If everything goes correctly, your
browser will go into a connected state, and the system is ready for
incoming and outgoing calls. Simple eh ? Well, not quite :]
Making outgoing calls and 'kicking a forward with remote station
From the JNOS console, you can connect to another Mercury V2 station :
c vara k7ek
and have a keyboard interaction with Gary's BBS
The test environment is setup so you can also forward with Gary, but you
should arrange with him first if you want to do this. I'm already setup,
so the important files to note when forwarding with a remote system :
rte/spool/forward.bbs
rte/spool/rewrite
From the JNOS console, I can then 'kick' his station to forward :
mbox ki k7ek [ will attempt forward only if I have messages for him ]
mbox ki K7ek [ will force a forward, even if I have nothing for him,
but it will check if he has something for me ]
To send a message to Gary, I would just go into the BBS and 'SP k7ek', or
use my thunderbird client interfaced to JNOS and email k7ek@k7ek
If you have other stations you want to forward with, then add them
to forward.bbs and make sure there are rewrite rules for them, just
like what is setup for k7ek (Gary) ...
Closing comments
This write up makes a few assumptions, sorry, but it's the most point form
and brief explanation I can come up with. You will have to figure it out on
your own. I just hope this base infrastructure is enough of a start for you
to experiment with. JNOS took me years to figure out, and yet still baffles
me at times. I am a developer, with minimal SYSOP skills, and certainly not
a NET103 or BBS operations expert like many out there. This is the physical
configuration that I have been using to test the Mercury V2 software these
past weeks, and it's worked quite well for me, Gary and myself have passed
a decent amount of emails over the past week using Mercury V2 ...
* last updated on Monday Night, September 14, 2026 ...
Read previous mail | Read next mail
| |
