Rapsberry Pi OS “firstboot” configures all of that during, well, firstboot. The imaging process writes the customizations to the vfat partition where /boot lives in various places. Those are then applied as the system starts. You can’t unpack/inspect the ext4 root system for proper configuration until after the firstboot process.
1 Like
OK, ya I’m punting here. But I’m using the web admin portal and then terminal and the menu , then expert config menu and then trying to edit in there. I have also tried using putty and get the file to open and edit but never able to save.
First off, it would be good to know which editor you selected. Since you have been using asl-menu and the expert config menu you should have been asked which editor you would like to use (with the default being nano). You can get back to this menu using “sudo select-editor”.
Assuming that you are using “nano” you will see a legend at the bottom of the screen. When you see sequences like “^X” that means control-X (hold down the control key and type “X”). To save a file you would use “^O” (control-O) to “Write Out” the file. That should bring up a “File Name to Write:” line just above the legend with the name of the file you are editing being displayed. Since you want to write the same file you can simply hit the Return/Enter key. That should have saved the file with any updates you made. If you are finished with the file then you would use “^X” (control-X) to “Exit”.
I hope this helped.
Chip,
Thank you so much for saying that.
You say “Let us know what you think”, so I think ASL would be much improved if it were open-source with compilable code. Introducing a Linux OS to others is difficult for you, but there are many node operators who live daily with Unix/Linux.
Yeah, that’s a todo. I recall an outside contributor posted a docker compose yaml.
For ASL3? I know several attempts were made to containerise previous versions, but all failed. From memory, DAHDI was the main issue. If there is a Dockerfile and yaml for ASL3 that works, I’d be happy to have a play.
ASL3 is a huge improvement and that significant effort is much appreciated.
Where can I set static IPs?
What’s the best way to turn on/off WLAN access?
Thanks again,
Tom / K5TRA
It’s theoretically possible to run it in Docker and Podman. It requires some setup for the
/deventries and exposing the kernel models needed to the docker. What we really need is a container wizard to help with the project - would make some of these kinds of features go much faster.
In my case, I don’t need audio devices, as the system in question is a hub (actually multiple hubs). My container foo isn’t quite up to exposing kernel modules yet. 
I’ll need someone else to do that side of things. 
Most OS settings are done with Cockpit, IP address included.
I’m not sure I’m following what you are trying to say here. All of AllStarLink v3 IS open source code. Look above and I posted the links to all of the various GitHub repositories that contain the code and how to raise issues with the different compents. One can also build their own system and install ASL3 on it without the Pi appliance elements. It’s all documented in the manual.
1 Like
There is always someone who doesn’t know all the facts and is quick to complain!
1 Like
It seems “make” doesn’t compile included code, but downloads and installs it. It’s also of concern here that there is no “uninstall” option in Makefile.
It seems “make” doesn’t compile included code, but downloads and installs it.
I am not sure which “make” you are referring to but, yes, the build process does include a few downloads (most importantly, we need the asterisk source code). The build steps pull together the various pieces (asterisk, app_rpt), apply a few needed patches, and then you have a directory with all of the bits to compile. Is this a bit complicated? Yes. Do we have our reasons for doing things this way. Yup.
It’s also of concern here that there is no “uninstall” option in Makefile.
Umm, the asterisk source code’s top-level Makefile HAS an “uninstall” option.
Amazing update. Hard to believe they kept it under wraps.
I got it set up on a new node fast- but when installing AllScan ran into a problem that looks like the AllScan updater does not run on x64bit. I have not seen any info in ASL guides, wiki, AllScan info, etc saying the OS must be x32bit. Am I dead in the water and must start over with x32bit ISO? Thx.
Hello guys can you use dvswitch with the new asl3.
Is installation different compared to previous asl.
thanks Brett VK4BDE
AllScan is supported on ASL3 by its author: https://github.com/davidgsd/AllScan?tab=readme-ov-file#release-notes.
ASL3 does not support 32-bit operating systems.
1 Like
Hello all,
Thanks for the amazing update, kudo’s to all who contributed to this, really nice work! One thing I ran into on the otherwise very smooth setup is the connpgm (and discpgm) programs. However I put these options into the rpt.conf file, template section or general part I cannot seem to get this to work. Even just a simple touch of a file in /tmp doesn’t seem to get executed. Have I missed something in the extensive (again kudo’s) documentation about changes to this option for ASL3?
Thanks,
73, Max
I just configured a simple connpgm (and discpgm) and all worked … for me. So, let’s start with the simple things like making sure your pgm’s are executable (chmod +x …) and have been tested independently. Also, you need to remember that the asterisk process is no longer running as “root”. Any files that you are reading/writing need to be accessible to the “asterisk” user.
Oh, wait, maybe this is NOT working. Investigating
… and it looks like you have found a real bug. I will file a GitHub issue and we’ll see if we can get that fixed.
… and a fix is coming. Just give us some time to turn the cranks and push out an update.
What aspect of “dvswitch” are you asking about? If you mean DVSwitch Mobile, yes it works fine and there will be some configuration differences.
Congrats to the team! I know this was a huge project to tackle and great to see it out in the wild! I plan on upgrading my nodes over the next few weeks!
Keep up the good work!
Jim, K6JWN
1 Like