Re: Instructions for g2_link 4.00 install on AlmaLinux
Rob et al - Many thanks
?
- whilst i started to follow the recipe, being new to this i could not find 'my scripts'? when i got to this point
?
# Copy the scripts to the my_scripts directory
cp /root/alma_temp/myscripts/* /root/my_scripts
?
Hope you can give me a pointer / wget link
?
73
?
?Murray G6JYB
|
Re: Instructions for g2_link 4.00 install on AlmaLinux
So happy to see this! I've been helping resuscitate the VE2RM gateway (a ways south and east of VY1RDS ...). I've got everything working under AL9 / G3.2 and have been waiting for "g2_link" (needs a new name). I was even able to re-import the user database from the left-for-dead former gateway system after I got it up and running. Unfortunately, our 70-cm RF module (only one we have - ID-RP4000V) is deaf. Sure, I can hit it using my ID-51+ from the bottom of the tower, but not from much further away. OK, it's not *quite* that bad, but I can hit the co-located 70-cm FM repeater from home ~20 km away on that same HT. Not full quieting, but still. Not so with the D-STAR repeater. But the network park works great! ANYWAY, I look forward to attempting to follow your recipe and will feed back any observations I have. Thank you! 73, Peter On Fri, Sep 6, 2024 at 12:17?PM Robert Gillis via groups.io <robert@...> wrote:
Hi g2_link admins,
As you have seen by some recent posts of mine, I have been working on getting g2_link working alongside of the new dplus G3 version 3.2 on an AlmaLinux install. I think I worked out all the kinks and I documented the install by creating the attached "recipe". These instructions should work for other admins as well assuming they have a working dplus G3 version 3.2 system running on AlmaLinux. Please note:
My attached instructions does not document the multiple options for dashboards, it just documents what I used on VY1RDS.
I do not used the supplied "my_scripts" or "cron" that was on va3uv's website, I used slightly modified versions as described in the next bullet point.
For the specific bits that are different than previous installs (some described below), I created a new tar file and place it on my website for download. This is included in the attached documentation. These files include:
modified crontab entries, disabled by default except the update_gwys one.
systemd services for use in AlmaLinux
slightly modified "my_scripts", and additional specific scripts I created for email notifications when new users register (work in progress, but mostly works), as well as a backup script that backups up g2_link config, dplus, and ircddb3 (if installed)
some customizations used on the vy1rds dashboard
patch file for g2_lh, to stop it from crashing (as per my last email, I still need to investigate why the condition comes up that was causing it to crash to begin with)
Please feel free to pick my work apart, reuse any or all of it, and/or re-incorporate any bits and pieces of this recipe or my tar file in official documentation for g2_link (assuming it actually works on other gateway installs--it should).
I will be following this recipe on a backup gateway I will be building shortly, so if I notice any errors at that time I will update and resend. Feedback welcome.
Enjoy,
Rob, VY1RDS
-- Peter Laws | VE[23]UWY / N5UWY | plaws0 gmail com | Travel by Train!
|
Re: Instructions for g2_link 4.00 install on AlmaLinux
I should really create a signature block, my call is not VY1RDS, its VY1RG, and I am one of the admins for the VY1RDS d-star repeater, which is managed and operated by the Yukon Amateur Radio Association (https://yara.ca)?
Rob, VY1RG (not VY1RDS).
toggle quoted message
Show quoted text
Hi g2_link admins,
As you have seen by some recent posts of mine, I have been working on getting g2_link working alongside of the new dplus G3 version 3.2 on an AlmaLinux install. I think I worked out all the kinks and I documented the install by creating the attached "recipe".?
These instructions should work for other admins as well assuming they have a working dplus G3 version 3.2 system running on AlmaLinux. Please note:
-
-
My attached instructions does not document the multiple options for dashboards, it just documents what I used on VY1RDS.
-
I do not used the supplied "my_scripts" or "cron" that was on va3uv's website, I used slightly modified versions as described in the next bullet point.
-
For the specific bits that are different than previous installs (some described below), I created a new tar file and place it on my website for download.? This is included in the attached documentation. These files include:
-
modified crontab entries, disabled by default except the update_gwys one.?
-
systemd services for use in AlmaLinux
-
slightly modified "my_scripts", and additional specific scripts I created for email notifications when new users register (work in progress, but mostly works), as well as a backup script that backups up g2_link config, dplus, and
ircddb3 (if installed)
-
some customizations used on the vy1rds dashboard
-
patch file for g2_lh, to stop it from crashing (as per my last email, I still need to investigate why the condition comes up that was causing it to crash to begin with)
Please feel free to pick my work apart, reuse any or all of it, and/or re-incorporate any bits and pieces of this recipe or my tar file in official documentation for g2_link? (assuming it actually works on other gateway installs--it should).
I will be following this recipe on a backup gateway I will be building shortly, so if I notice any errors at that time I will update and resend.? Feedback welcome.
Enjoy,
Rob, VY1RDS
|
Instructions for g2_link 4.00 install on AlmaLinux
Hi g2_link admins,
As you have seen by some recent posts of mine, I have been working on getting g2_link working alongside of the new dplus G3 version 3.2 on an AlmaLinux install. I think I worked out all the kinks and I documented the install by creating the attached "recipe".?
These instructions should work for other admins as well assuming they have a working dplus G3 version 3.2 system running on AlmaLinux. Please note:
-
-
My attached instructions does not document the multiple options for dashboards, it just documents what I used on VY1RDS.
-
I do not used the supplied "my_scripts" or "cron" that was on va3uv's website, I used slightly modified versions as described in the next bullet point.
-
For the specific bits that are different than previous installs (some described below), I created a new tar file and place it on my website for download.? This is included in the attached documentation. These files include:
-
modified crontab entries, disabled by default except the update_gwys one.?
-
systemd services for use in AlmaLinux
-
slightly modified "my_scripts", and additional specific scripts I created for email notifications when new users register (work in progress, but mostly works), as well as a backup script that backups up g2_link config, dplus, and
ircddb3 (if installed)
-
some customizations used on the vy1rds dashboard
-
patch file for g2_lh, to stop it from crashing (as per my last email, I still need to investigate why the condition comes up that was causing it to crash to begin with)
Please feel free to pick my work apart, reuse any or all of it, and/or re-incorporate any bits and pieces of this recipe or my tar file in official documentation for g2_link? (assuming it actually works on other gateway installs--it should).
I will be following this recipe on a backup gateway I will be building shortly, so if I notice any errors at that time I will update and resend.? Feedback welcome.
Enjoy,
Rob, VY1RDS
|
Re: g2_link + AlmaLinux - almost there! - challenge with g2_lh
Hi Rich,
Based on the log output, I am using g2_link 4.00 binaries, which I sourced from . However.... I did find some time today to do some debugging.? With a little help from my old friend gdb, I was able to find the condition that causes this segmentation fault in g2_lh, and I coded a simple handler
to handle the condition (instead of letting it crash when this condition is met—which in turn also keeps g2_link
up). The system has been steady ever since I applied my patch to g2_lh and I even just had a short QSO with KA8SCP via my repeater / g2_link. While I will still need to do some more debugging to understand why this condition is happening in the first place,
I am happy with the patch I created for g2_lh.
I will go though my documentation that I created while going through this exercise tonight to clean it up a bit,?and if time permits, I will send it out to this group for feedback / incorporation into other sources/official documentation.
Live dashboard of upgraded system here: .? I still have a bit of customization to do on the registration page, etc., but fully operational.
Rob
toggle quoted message
Show quoted text
what is the source of your g2-link and what is the version number?
rich
On 9/5/24 11:05 AM, Robert Gillis via groups.io wrote:
Hi There,
so close....
I have been working away getting g2_link running on AlmaLinux alongside DPlus G3 version 3.2, and am getting pretty close. I have g2_link and dtmf_reader converted to systemd services, and have them both running successfully (wahoo). However, it seems I am
running into one last hurdle and I am hoping someone with a bit more recent Linux development experience can help me out with. This is something I can tinker with in my spare time, but I don't have much spare time lately.? If there are any C++ / Linux development
guru's out there that have experience I have no doubt they can figure it out much quicker than I can.
The issue I am running into is that the g2_lh program (which is executed frequently to build the dashboard) will sometimes crash, causing g2_link to crash as described below.? I have the systemd service I created to restart the service when it crashes, but
of course if there was a pre-established link it drops and will need to be reestablished.
Here are the details of what is happening:
sometimes, when g2_lh executes, it crashes it core-dumps with the following (from /var/messages):
Sep ?5 09:30:02 vy1rds-gw2 kernel: g2_lh[126886]: segfault at 448001 ip 00007f18eb159755 sp 00007ffc613cd4a8 error 4 in libc.so.6[7f18eb028000+175000] likely on CPU 0 (core 0, socket 0)
Sep ?5 09:30:02 vy1rds-gw2 kernel: Code: 0f b6 44 07 e0 29 c8 c5 f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 83 fa 01 76 7b 89 f8 09 f0 25 ff 0f 00 00 3d e0 0f 00 00 7f 2b <c5> fe 6f 16 c5 ed 74 17 c5 ? ? ? ? ?fd d7 c2 ff c0 c4 e2 68 f5 d0 0f 85 d2
Sep ?5 09:30:02 vy1rds-gw2 systemd[1]: Started Process Core Dump (PID 127638/UID 0).
Sep ?5 09:30:02 vy1rds-gw2 systemd-coredump[127639]: Resource limits disable core dumping for process 126886 (g2_lh).
Sep ?5 09:30:02 vy1rds-gw2 systemd-coredump[127639]: Process 126886 (g2_lh) of user 0 dumped core.
Shortly after, g2_link crashes (from /var/messages)
Sep ?5 09:30:52 vy1rds-gw2 kernel: g2_link[126542]: segfault at ae15ae9a ip 00000000f7ca84a3 sp 00000000fffc2d0c error 4 in libstdc++.so.6.0.29[f7c78000+123000] likely on CPU 2 (core 0, socket 0)
Sep ?5 09:30:52 vy1rds-gw2 kernel: Code: 66 90 66 90 66 90 90 f3 0f 1e fb 8b 54 24 04 8b 42 0c 85 c0 74 11 90 89 c2 8b 40 08 85 c0 75 f7 89 d0 c3 8d 74 26 00 8b 42 04 <3b> 50 0c 75 1b 8d b4 26 00 ? ? ? ? ?00 00 00 90 89 c2 8b 40 04 39 50 0c 74
Sep ?5 09:30:52 vy1rds-gw2 systemd[1]: Started Process Core Dump (PID 127773/UID 0).
Sep ?5 09:30:52 vy1rds-gw2 systemd-coredump[127774]: Resource limits disable core dumping for process 126542 (g2_link).
Sep ?5 09:30:52 vy1rds-gw2 systemd-coredump[127774]: Process 126542 (g2_link) of user 0 dumped core.
In /var/log/g2_link, this is the error that happens right before the g2_link segfault:
??????090524 at 09:30:52:call=1NFO ? ? timeout, removing 10.0.0.2, users=0
It seems to me, that g2_lh is crashing, which then has the cascading effect into g2_link. While I have the c code for g2_lh which I can try to debug as time permits, I do not have the code for g2_link, so I cant look into that side.
It has been a long?time since I analyzed core dumps, but I am willing to try. If anyone wants to see the core dumps to analyze, I will happily enable core dumping for these services and send them over for their analysis.
Rob, VY1RG
|
Re: g2_link + AlmaLinux - almost there! - challenge with g2_lh
i've not seen this before but that message is emitted from send_heartbeat() here:
static void send_heartbeat()
{
?? inbound_type::iterator pos;
?? inbound *inbound_ptr;
?? bool removed = false;
?? for (pos = inbound_list.begin(); pos != inbound_list.end(); pos++)
?? {
????? inbound_ptr = (inbound *)pos->second;
????? sendto(ref_g2_sock,(char *)REF_ACK,3,0,
???????????? (struct sockaddr *)&(inbound_ptr->sin),
???????????? sizeof(struct sockaddr_in));
????? if (inbound_ptr->countdown >= 0)
???????? inbound_ptr->countdown --;
????? if (inbound_ptr->countdown < 0)
????? {
???????? removed = true;
???????? traceit("call=%s timeout, removing %s, users=%d\n",
???????????????? inbound_ptr->call,
???????????????? pos->first.c_str(),
???????????????? inbound_list.size() - 1);
???????? free(pos->second);
???????? pos->second = NULL;
???????? inbound_list.erase(pos);
????? }
?? }
?? if (removed)
????? print_status_file();
}
toggle quoted message
Show quoted text
On 9/5/24 11:05 AM, Robert Gillis via groups.io wrote: timeout, removing
|
Re: g2_link + AlmaLinux - almost there! - challenge with g2_lh
what is the source of your g2-link and what is the version
number?
rich
On 9/5/24 11:05 AM, Robert Gillis via
groups.io wrote:
toggle quoted message
Show quoted text
Hi There,
so close....
I have been working away getting g2_link running on AlmaLinux
alongside DPlus G3 version 3.2, and am getting pretty close. I
have g2_link and dtmf_reader converted to systemd services, and
have them both running successfully (wahoo). However, it seems I
am running into one last hurdle and I am hoping someone with a
bit more recent Linux development experience can help me out
with. This is something I can tinker with in my spare time, but
I don't have much spare time lately.? If there are any C++ /
Linux development guru's out there that have experience I have
no doubt they can figure it out much quicker than I can.
The issue I am running into is that the g2_lh program (which is
executed frequently to build the dashboard) will sometimes
crash, causing g2_link to crash as described below.? I have the
systemd service I created to restart the service when it
crashes, but of course if there was a pre-established link it
drops and will need to be reestablished.
Here are the details of what is happening:
sometimes, when g2_lh executes, it crashes it core-dumps
with the following (from /var/messages):
Sep ?5 09:30:02 vy1rds-gw2 kernel: g2_lh[126886]: segfault at
448001 ip 00007f18eb159755 sp 00007ffc613cd4a8 error 4 in
libc.so.6[7f18eb028000+175000] likely on CPU 0 (core 0, socket
0)
Sep ?5 09:30:02 vy1rds-gw2 kernel: Code: 0f b6 44 07 e0 29 c8 c5
f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 83 fa 01 76 7b 89 f8 09
f0 25 ff 0f 00 00 3d e0 0f 00 00 7f 2b <c5> fe 6f 16 c5 ed
74 17 c5 ? ? ? ? ?fd d7 c2 ff c0 c4 e2 68 f5 d0 0f 85 d2
Sep ?5 09:30:02 vy1rds-gw2 systemd[1]: Started Process Core Dump
(PID 127638/UID 0).
Sep ?5 09:30:02 vy1rds-gw2 systemd-coredump[127639]: Resource
limits disable core dumping for process 126886 (g2_lh).
Sep ?5 09:30:02 vy1rds-gw2 systemd-coredump[127639]: Process
126886 (g2_lh) of user 0 dumped core.
Shortly after, g2_link crashes (from /var/messages)
Sep ?5 09:30:52 vy1rds-gw2 kernel: g2_link[126542]: segfault at
ae15ae9a ip 00000000f7ca84a3 sp 00000000fffc2d0c error 4 in
libstdc++.so.6.0.29[f7c78000+123000] likely on CPU 2 (core 0,
socket 0)
Sep ?5 09:30:52 vy1rds-gw2 kernel: Code: 66 90 66 90 66 90 90 f3
0f 1e fb 8b 54 24 04 8b 42 0c 85 c0 74 11 90 89 c2 8b 40 08 85
c0 75 f7 89 d0 c3 8d 74 26 00 8b 42 04 <3b> 50 0c 75 1b 8d
b4 26 00 ? ? ? ? ?00 00 00 90 89 c2 8b 40 04 39 50 0c 74
Sep ?5 09:30:52 vy1rds-gw2 systemd[1]: Started Process Core Dump
(PID 127773/UID 0).
Sep ?5 09:30:52 vy1rds-gw2 systemd-coredump[127774]: Resource
limits disable core dumping for process 126542 (g2_link).
Sep ?5 09:30:52 vy1rds-gw2 systemd-coredump[127774]: Process
126542 (g2_link) of user 0 dumped core.
In /var/log/g2_link, this is the error that happens right before
the g2_link segfault:
??????090524 at 09:30:52:call=1NFO ? ? timeout, removing
10.0.0.2, users=0
It seems to me, that g2_lh is crashing, which then has the
cascading effect into g2_link. While I have the c code for g2_lh
which I can try to debug as time permits, I do not have the code
for g2_link, so I cant look into that side.
It has been a long?time since I analyzed core dumps, but
I am willing to try. If anyone wants to see the core dumps to
analyze, I will happily enable core dumping for these services
and send them over for their analysis.
Rob, VY1RG
|
g2_link + AlmaLinux - almost there! - challenge with g2_lh
Hi There,
so close....
I have been working away getting g2_link running on AlmaLinux alongside DPlus G3 version 3.2, and am getting pretty close. I have g2_link and dtmf_reader converted to systemd services, and have them both running successfully (wahoo). However, it seems I am
running into one last hurdle and I am hoping someone with a bit more recent Linux development experience can help me out with. This is something I can tinker with in my spare time, but I don't have much spare time lately.? If there are any C++ / Linux development
guru's out there that have experience I have no doubt they can figure it out much quicker than I can.
The issue I am running into is that the g2_lh program (which is executed frequently to build the dashboard) will sometimes crash, causing g2_link to crash as described below.? I have the systemd service I created to restart the service when it crashes, but
of course if there was a pre-established link it drops and will need to be reestablished.
Here are the details of what is happening:
sometimes, when g2_lh executes, it crashes it core-dumps with the following (from /var/messages):
Sep ?5 09:30:02 vy1rds-gw2 kernel: g2_lh[126886]: segfault at 448001 ip 00007f18eb159755 sp 00007ffc613cd4a8 error 4 in libc.so.6[7f18eb028000+175000] likely on CPU 0 (core 0, socket 0)
Sep ?5 09:30:02 vy1rds-gw2 kernel: Code: 0f b6 44 07 e0 29 c8 c5 f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 83 fa 01 76 7b 89 f8 09 f0 25 ff 0f 00 00 3d e0 0f 00 00 7f 2b <c5> fe 6f 16 c5 ed 74 17 c5 ? ? ? ? ?fd d7 c2 ff c0 c4 e2 68 f5 d0 0f 85 d2
Sep ?5 09:30:02 vy1rds-gw2 systemd[1]: Started Process Core Dump (PID 127638/UID 0).
Sep ?5 09:30:02 vy1rds-gw2 systemd-coredump[127639]: Resource limits disable core dumping for process 126886 (g2_lh).
Sep ?5 09:30:02 vy1rds-gw2 systemd-coredump[127639]: Process 126886 (g2_lh) of user 0 dumped core.
Sep ?5 09:30:02 vy1rds-gw2 systemd[1]: systemd-coredump@...: Deactivated successfully.
Shortly after, g2_link crashes (from /var/messages)
Sep ?5 09:30:52 vy1rds-gw2 kernel: g2_link[126542]: segfault at ae15ae9a ip 00000000f7ca84a3 sp 00000000fffc2d0c error 4 in libstdc++.so.6.0.29[f7c78000+123000] likely on CPU 2 (core 0, socket 0)
Sep ?5 09:30:52 vy1rds-gw2 kernel: Code: 66 90 66 90 66 90 90 f3 0f 1e fb 8b 54 24 04 8b 42 0c 85 c0 74 11 90 89 c2 8b 40 08 85 c0 75 f7 89 d0 c3 8d 74 26 00 8b 42 04 <3b> 50 0c 75 1b 8d b4 26 00 ? ? ? ? ?00 00 00 90 89 c2 8b 40 04 39 50 0c 74
Sep ?5 09:30:52 vy1rds-gw2 systemd[1]: Started Process Core Dump (PID 127773/UID 0).
Sep ?5 09:30:52 vy1rds-gw2 systemd-coredump[127774]: Resource limits disable core dumping for process 126542 (g2_link).
Sep ?5 09:30:52 vy1rds-gw2 systemd-coredump[127774]: Process 126542 (g2_link) of user 0 dumped core.
Sep ?5 09:30:52 vy1rds-gw2 systemd[1]: systemd-coredump@...: Deactivated successfully.
In /var/log/g2_link, this is the error that happens right before the g2_link segfault:
??????090524 at 09:30:52:call=1NFO ? ? timeout, removing 10.0.0.2, users=0
It seems to me, that g2_lh is crashing, which then has the cascading effect into g2_link. While I have the c code for g2_lh which I can try to debug as time permits, I do not have the code for g2_link, so I cant look into that side.
It has been a long?time since I analyzed core dumps, but I am willing to try. If anyone wants to see the core dumps to analyze, I will happily enable core dumping for these services and send them over for their analysis.
Rob, VY1RG
|
Re: g2_link and alma - success
That is great news Rob. I only had some old CPU based machines here that Alma 9 would not load on. So I had started to manually edit the script… minor items. The one potential issue was Alma did not have an init.d directory so the startup piece was one issue to be addressed. Ramesh and I discussed the overall package and thought it would be fine… since Alma is pretty much CentOS anyways.
Nice job and thanks for the notice.
Has anyone addressed the g2_link startup piece? Or had any success like Rob?
toggle quoted message
Show quoted text
On Aug 30, 2024, at 1:45?AM, Robert Gillis <robert@...> wrote:
?
Hi There,
I haven't seen too much out there about people successfully installing g2_link alongside a new AlmaLinux install, but I wanted to share that I?successfully upgraded our local repeater (VY1RDS) this evening to AlmaLinux, the latest iCom gateway/dplus software,
ircddb addon--and, just now, I had a working g2_link manually running with it as well I verified quickly by linking/unlinking to XRF reflectors, and verified I was getting though to the reflector.? I used the same binary package that I was using on CentOS.??
Over the next week, I plan to convert the services from the old format to systemd, and make things automatic (again, I was just running the g2_link manually this evening with a few script modifications) as well as make sure I can get the FreeStar dashboard
up and running, etc.? I hope to have this all done before mid-September, but if I do not get around to it (that day job of mine and kids sure do take up a lot of my time), I will put this work on pause until early October as I am away the last two weeks of
September with no communications.
Before I work on converting the services over / documenting everything that I did to get g2_link working (which didn't involve too much modification) I wanted to verify that no one else has already done / shared this?? Based on my preliminary searching, I have
not found anything along these lines.
Rob, VY1RG
--
Terry Stader - KA8SCP
D-STAR Gateway & Reflector Admin
|
g2_link and alma - success
Hi There,
I haven't seen too much out there about people successfully installing g2_link alongside a new AlmaLinux install, but I wanted to share that I?successfully upgraded our local repeater (VY1RDS) this evening to AlmaLinux, the latest iCom gateway/dplus software,
ircddb addon--and, just now, I had a working g2_link manually running with it as well I verified quickly by linking/unlinking to XRF reflectors, and verified I was getting though to the reflector.? I used the same binary package that I was using on CentOS.??
Over the next week, I plan to convert the services from the old format to systemd, and make things automatic (again, I was just running the g2_link manually this evening with a few script modifications) as well as make sure I can get the FreeStar dashboard
up and running, etc.? I hope to have this all done before mid-September, but if I do not get around to it (that day job of mine and kids sure do take up a lot of my time), I will put this work on pause until early October as I am away the last two weeks of
September with no communications.
Before I work on converting the services over / documenting everything that I did to get g2_link working (which didn't involve too much modification) I wanted to verify that no one else has already done / shared this?? Based on my preliminary searching, I have
not found anything along these lines.
Rob, VY1RG
|
yes. but it will take me a while to get it together. i have to
get alma on a server first. Also, I must determine whether I can
share src or a binary since long ago I agreed to not distribute
the src.
One challenge I have mentioned is "what is the current official
src"? Is my v4 (aside from my changes) the same as other v4 out
there? (I think not.) and what are these 4.1 and 4.2 src?
Maybe it is time to create an "official" src....
rich
On 7/1/24 5:54 AM, Terry M. Stader via
groups.io wrote:
toggle quoted message
Show quoted text
Can you share your changes with the group?
Terry
i have supported g2-link ver 4 and I have some zips of
4.1 and 4.2 that appear to come from other than Ramesh.
Years ago Ramesh provided me with some 3.x versions which
I still have.
As you can see here
I show modified g2-lh and g2-link v 4.0p meaning "painter"
version, which is modified from the v4.0
The problem we all have is that there were many versions
that a number of folks modified that there isn't a clear
lineage OR which is the latest and has fixes.
I'm getting ready to put alma and G3.2 on our 3 systems
and likely a 4th I help with locally. I'm not sure where I
will start with g2-link but likely it is what I'm
currently running (4.0p) and see what works.
rich
On 6/30/24 5:27 PM, Terry M.
Stader via groups.io wrote:
I have a couple of local hams that are going to assist the
transition from Centos to AlmaLinux… so helpfully we will
get some helpful assistance. I have 4 or 5 gateways we can
test with.
Scott Lawson asked that the original dextra code not
be available publicly… so I can’t really push it out to
GitHub, etc.
Terry
?
That makes you Project Manager! ??
People move on, interests change,
ain’t no thing.? Software authors owe us exactly
$0.00.?
Thank you for taking up the torch. I
have a new Alma G3.2 and am happy to help test.?
Peter
I’ve
worked with Ramesh and we have determined that
g2_link will compile with the components
provided in the archive provided in the
documentation. I am working on modifying the
install documentation for g2_link in an Alma
environment.
When I return from vacation I’ll try and
update the install steps.
I’ve also updated some if the zip files to
accommodate both G3 for Centos and Alma.
Terry
Terry M Stader KA8SCP
> On Jun 29, 2024, at 12:54?PM, Peter Laws
<plaws0@...>
wrote:
> ?So ... VA3UV.? Has he given up the
G2_link project?
>
> If yes, then where does that leave us?? I
do note that it's G2_link
> and not G3_link, so if the "G" relates to
the Icom bits, now G3.2,
> does this mean it's pretty old?
>
> I don't have the software (I know - I
haven't asked The Right Guy -
> it's fine) so don't know what it consists
of.? If it's scripts, we can
> probably make do.? If it's binaries and
we have no source ...
>
> Peter
>
> --
> Peter Laws | VE[23]UWY / N5UWY | plaws0
gmail com | Travel by Train!
>
>
>
--
Terry Stader - KA8SCP
D-STAR Gateway & Reflector Admin
--
Terry Stader - KA8SCP
D-STAR Gateway & Reflector Admin
--
Terry Stader - KA8SCP
D-STAR Gateway & Reflector Admin
|
Can you share your changes with the group?
Terry
toggle quoted message
Show quoted text
On Jun 30, 2024, at 7:35?PM, Rich Painter <painterengr@...> wrote
i have supported g2-link ver 4 and I have some zips of 4.1 and
4.2 that appear to come from other than Ramesh.
Years ago Ramesh provided me with some 3.x versions which I still
have.
As you can see here I show
modified g2-lh and g2-link v 4.0p meaning "painter" version, which
is modified from the v4.0
The problem we all have is that there were many versions that a
number of folks modified that there isn't a clear lineage OR which
is the latest and has fixes.
I'm getting ready to put alma and G3.2 on our 3 systems and
likely a 4th I help with locally. I'm not sure where I will start
with g2-link but likely it is what I'm currently running (4.0p)
and see what works.
rich
On 6/30/24 5:27 PM, Terry M. Stader via
groups.io wrote:
I have a couple of local hams that are going to assist the
transition from Centos to AlmaLinux… so helpfully we will get some
helpful assistance. I have 4 or 5 gateways we can test with.
Scott Lawson asked that the original dextra code not be
available publicly… so I can’t really push it out to GitHub,
etc.
Terry
?
That makes you Project Manager! ??
People move on, interests change, ain’t no
thing.? Software authors owe us exactly $0.00.?
Thank you for taking up the torch. I have a
new Alma G3.2 and am happy to help test.?
Peter
I’ve
worked with Ramesh and we have determined that g2_link
will compile with the components provided in the
archive provided in the documentation. I am working on
modifying the install documentation for g2_link in an
Alma environment.
When I return from vacation I’ll try and update the
install steps.
I’ve also updated some if the zip files to accommodate
both G3 for Centos and Alma.
Terry
Terry M Stader KA8SCP
> On Jun 29, 2024, at 12:54?PM, Peter Laws <plaws0@...>
wrote:
> ?So ... VA3UV.? Has he given up the G2_link
project?
>
> If yes, then where does that leave us?? I do note
that it's G2_link
> and not G3_link, so if the "G" relates to the
Icom bits, now G3.2,
> does this mean it's pretty old?
>
> I don't have the software (I know - I haven't
asked The Right Guy -
> it's fine) so don't know what it consists of.? If
it's scripts, we can
> probably make do.? If it's binaries and we have
no source ...
>
> Peter
>
> --
> Peter Laws | VE[23]UWY / N5UWY | plaws0 gmail com
| Travel by Train!
>
>
>
--
Terry Stader - KA8SCP
D-STAR Gateway & Reflector Admin
--
Terry Stader - KA8SCP
D-STAR Gateway & Reflector Admin
--
Terry Stader - KA8SCP
D-STAR Gateway & Reflector Admin
|
i have supported g2-link ver 4 and I have some zips of 4.1 and
4.2 that appear to come from other than Ramesh.
Years ago Ramesh provided me with some 3.x versions which I still
have.
As you can see here I show
modified g2-lh and g2-link v 4.0p meaning "painter" version, which
is modified from the v4.0
The problem we all have is that there were many versions that a
number of folks modified that there isn't a clear lineage OR which
is the latest and has fixes.
I'm getting ready to put alma and G3.2 on our 3 systems and
likely a 4th I help with locally. I'm not sure where I will start
with g2-link but likely it is what I'm currently running (4.0p)
and see what works.
rich
On 6/30/24 5:27 PM, Terry M. Stader via
groups.io wrote:
toggle quoted message
Show quoted text
I have a couple of local hams that are going to assist the
transition from Centos to AlmaLinux… so helpfully we will get some
helpful assistance. I have 4 or 5 gateways we can test with.
Scott Lawson asked that the original dextra code not be
available publicly… so I can’t really push it out to GitHub,
etc.
Terry
?
That makes you Project Manager! ??
People move on, interests change, ain’t no
thing.? Software authors owe us exactly $0.00.?
Thank you for taking up the torch. I have a
new Alma G3.2 and am happy to help test.?
Peter
I’ve
worked with Ramesh and we have determined that g2_link
will compile with the components provided in the
archive provided in the documentation. I am working on
modifying the install documentation for g2_link in an
Alma environment.
When I return from vacation I’ll try and update the
install steps.
I’ve also updated some if the zip files to accommodate
both G3 for Centos and Alma.
Terry
Terry M Stader KA8SCP
> On Jun 29, 2024, at 12:54?PM, Peter Laws <plaws0@...>
wrote:
> ?So ... VA3UV.? Has he given up the G2_link
project?
>
> If yes, then where does that leave us?? I do note
that it's G2_link
> and not G3_link, so if the "G" relates to the
Icom bits, now G3.2,
> does this mean it's pretty old?
>
> I don't have the software (I know - I haven't
asked The Right Guy -
> it's fine) so don't know what it consists of.? If
it's scripts, we can
> probably make do.? If it's binaries and we have
no source ...
>
> Peter
>
> --
> Peter Laws | VE[23]UWY / N5UWY | plaws0 gmail com
| Travel by Train!
>
>
>
--
Terry Stader - KA8SCP
D-STAR Gateway & Reflector Admin
--
Terry Stader - KA8SCP
D-STAR Gateway & Reflector Admin
|
I have a couple of local hams that are going to assist the transition from Centos to AlmaLinux… so helpfully we will get some helpful assistance. I have 4 or 5 gateways we can test with.
Scott Lawson asked that the original dextra code not be available publicly… so I can’t really push it out to GitHub, etc.
toggle quoted message
Show quoted text
On Jun 30, 2024, at 1:06?PM, Peter Laws <plaws0@...> wrote:
? That makes you Project Manager! ??
People move on, interests change, ain’t no thing.? Software authors owe us exactly $0.00.?
Thank you for taking up the torch. I have a new Alma G3.2 and am happy to help test.?
I’ve worked with Ramesh and we have determined that g2_link will compile with the components provided in the archive provided in the documentation. I am working on modifying the install documentation for g2_link in an Alma environment.
When I return from vacation I’ll try and update the install steps.
I’ve also updated some if the zip files to accommodate both G3 for Centos and Alma.
Terry
Terry M Stader KA8SCP
> On Jun 29, 2024, at 12:54?PM, Peter Laws <plaws0@...> wrote:
> ?So ... VA3UV.? Has he given up the G2_link project?
>
> If yes, then where does that leave us?? I do note that it's G2_link
> and not G3_link, so if the "G" relates to the Icom bits, now G3.2,
> does this mean it's pretty old?
>
> I don't have the software (I know - I haven't asked The Right Guy -
> it's fine) so don't know what it consists of.? If it's scripts, we can
> probably make do.? If it's binaries and we have no source ...
>
> Peter
>
> --
> Peter Laws | VE[23]UWY / N5UWY | plaws0 gmail com | Travel by Train!
>
>
>
--
Terry Stader - KA8SCP
D-STAR Gateway & Reflector Admin
--
Terry Stader - KA8SCP
D-STAR Gateway & Reflector Admin
|
That makes you Project Manager! ??
People move on, interests change, ain’t no thing.? Software authors owe us exactly $0.00.?
Thank you for taking up the torch. I have a new Alma G3.2 and am happy to help test.?
I’ve worked with Ramesh and we have determined that g2_link will compile with the components provided in the archive provided in the documentation. I am working on modifying the install documentation for g2_link in an Alma environment.
When I return from vacation I’ll try and update the install steps.
I’ve also updated some if the zip files to accommodate both G3 for Centos and Alma.
Terry
Terry M Stader KA8SCP
> On Jun 29, 2024, at 12:54?PM, Peter Laws <plaws0@...> wrote:
> ?So ... VA3UV.? Has he given up the G2_link project?
>
> If yes, then where does that leave us?? I do note that it's G2_link
> and not G3_link, so if the "G" relates to the Icom bits, now G3.2,
> does this mean it's pretty old?
>
> I don't have the software (I know - I haven't asked The Right Guy -
> it's fine) so don't know what it consists of.? If it's scripts, we can
> probably make do.? If it's binaries and we have no source ...
>
> Peter
>
> --
> Peter Laws | VE[23]UWY / N5UWY | plaws0 gmail com | Travel by Train!
>
>
>
--
Terry Stader - KA8SCP
D-STAR Gateway & Reflector Admin
|
?I’ve worked with Ramesh and we have determined that g2_link will compile with the components provided in the archive provided in the documentation. I am working on modifying the install documentation for g2_link in an Alma environment.
When I return from vacation I’ll try and update the install steps.
I’ve also updated some if the zip files to accommodate both G3 for Centos and Alma.
Terry
Terry M Stader KA8SCP
toggle quoted message
Show quoted text
On Jun 29, 2024, at 12:54?PM, Peter Laws <plaws0@...> wrote:
?So ... VA3UV. Has he given up the G2_link project?
If yes, then where does that leave us? I do note that it's G2_link
and not G3_link, so if the "G" relates to the Icom bits, now G3.2,
does this mean it's pretty old?
I don't have the software (I know - I haven't asked The Right Guy -
it's fine) so don't know what it consists of. If it's scripts, we can
probably make do. If it's binaries and we have no source ...
Peter
--
Peter Laws | VE[23]UWY / N5UWY | plaws0 gmail com | Travel by Train!
--
Terry Stader - KA8SCP
D-STAR Gateway & Reflector Admin
|
So ... VA3UV. Has he given up the G2_link project?
If yes, then where does that leave us? I do note that it's G2_link
and not G3_link, so if the "G" relates to the Icom bits, now G3.2,
does this mean it's pretty old?
I don't have the software (I know - I haven't asked The Right Guy -
it's fine) so don't know what it consists of. If it's scripts, we can
probably make do. If it's binaries and we have no source ...
Peter
--
Peter Laws | VE[23]UWY / N5UWY | plaws0 gmail com | Travel by Train!
|
The red button is discard, the green button is send. *sigh* And again ...
Why would you look at Oracle's distribution vs Alma? Are you certain that they are "RHEL compatible" enough that the instructions on offer for Alma 9 would "just work"? Or would you spend hours and hours tracking down some obscure difference?
Anyway, not a fan of systemd, but as a user (and mostly-former admin), I don't get a say. I hate the gratuitous changes over the years in how things work. I do want to keep moving forward but for goodness's sake, include config converters and commands that look like the "old way" while doing the new thing (and telling you where to find more info). Some new stuff *is* better, but if you have been running ifconfig for *decades* and now it's "ip", at least make ifconfig say "hey, greybeard, run 'ip a' instead next time (here is the info)"
But no. Not how the kids do it these days.
ANYWAY, systemd uses ASCII files like the /etc/init.d stuff but just rearranges everything. Here is the example for the ircDDB addon I put on our G3.2/Alma 9 system the other day.
[root@dstar-gw etc]# more /usr/lib/systemd/system-preset/51-ircddbd3.preset /usr/lib/systemd/system/ircddbd3.service
::::::::::::::
/usr/lib/systemd/system-preset/51-ircddbd3.preset
::::::::::::::
enable ircddbd3.service
::::::::::::::
/usr/lib/systemd/system/ircddbd3.service
::::::::::::::
[Unit]
Description=ircDDB java program
After=network.target
[Service]
Type=simple
ExecStart=/usr/share/ircddbd3/ircddbd3.sh
User=ircddb
Group=ircddb
Restart=always
RestartSec=30
[Install]
WantedBy=multi-user.target
|
On Thu, Jun 27, 2024 at 11:01?PM Terry M. Stader via groups.io <ka8scp@...> wrote:
Did anyone come up with a AlmaLinux version of the init.d “service” file for g2_link?
Is there not a compatibility shim that allows systemctl to understand the older files? -- Peter Laws | VE[23]UWY / N5UWY | plaws0 gmail com | Travel by Train!
|
Did anyone come up with a AlmaLinux version of the init.d “service” file for g2_link?
Terry
--
Terry Stader - KA8SCP
D-STAR Gateway & Reflector Admin
|
Peter Laws
Rich Painter
Terry M. Stader