astlinux-devel — The AstLinux development environment, compilation, etc

[Astlinux-devel] Announcing AstLinux Release: 1.5.11

[Lonnie A. <li...@lo...>]

Announcing AstLinux Release: 1.5.11

More Info: AstLinux Project
https://www.astlinux-project.org/

New Documentation Topics:
Protectli VP2430 Intel N150 Fanless Appliance [1]
Qotom Q10922H6 Intel N100 Fanless Appliance [2]
MeLE QuieterDL Intel N100 Fanless Mini PC [3]

AstLinux 1.5.11 Highlights:
* Asterisk Versions: 16.30.0, 18.26.2, 20.14.1
* Linux Kernel 5.10.238-cip61, security and bug fixes
* RUNNIX, version bump to runnix-0.6.23
* OpenSSL, version 1.1.1w, security fix: CVE-2024-13176
* OpenSSH, version 8.4p1, security fix: CVE-2025-32728
* libcurl (curl) version bump to 8.14.1
* libmad, version 0.15.1b, security fixes: CVE-2017-8372, CVE-2017-8373, CVE-2017-8374
* libxml2, version 2.11.9, many (7) security fixes
* chrony, version bump to 4.7
* keepalived, version bump to 2.3.4
* Monit, version bump to 5.35.2
* msmtp, version bump to 1.8.30
* mtr, version bump to 0.96
* php, version 7.2.34, add security fix: GHSA-wg4p-4hqh-c3g9
* screen, version 5.0.1, many (5) security fixes
* smartctl (smartmontools), version bump to 7.5, drivedb.h snapshot 2025-04-27
* sox, version 14.4.2, many (23) security fixes
* sqlite, version bump to 3.50.2
* stunnel, version bump to 5.75
* sudo, version 1.8.32, backport security fix: CVE-2025-32462
* unbound, version bump to 1.23.0
* WireGuard, wireguard-tools, version bump to 1.0.20250521
* ca-certificates, update trusted root certificates 2025-05-20
* mac2vendor, oui.txt database snapshot 2025-07-14
* Asterisk '16se' (stable edition) version 16.30.0 is the last Asterisk 16.x "Legacy" version, built --without-pjproject and --without-dahdi
* Package upgrades providing important security and bug fixes

Full ChangeLog:
https://raw.githubusercontent.com/astlinux-project/astlinux/1.5.11/docs/ChangeLog.txt

All users are encouraged to upgrade, read the ChangeLog for the details.

AstLinux Team

[1] https://doc.astlinux-project.org/userdoc:board_protectli_vp2430
[2] https://doc.astlinux-project.org/userdoc:board_qotom_q10922h6
[3] https://doc.astlinux-project.org/userdoc:board_mele_quieterdl

Re: [Astlinux-devel] Remote access of devices behind Astlinux

[David K. <da...@ke...>]

Unless you need to update packages on an installed system, without
refreshing the whole image, then I think Buildroot would be a great place
to start.  I think (but could be wrong) buildroot does not have a package
manager to allow updates to existing systems.  Instead you select all the
packages you want during build time, and the install image is created...
just like Astlinux.

There is a lot of documentation at Buildroot including recommendations on
how to layout and add your own custom packages which would not be part of
Buildroot itself... for example, all Astlinux custom web interfaces could
be added as a custom package on your own fork of Buildroot.  If you follow
the design recommendations in the documentation then it should fit in
fairly easily to the build environment.

Of course I say this without having tried it myself.  If it was me, I would
start by trying to get a very simple Buildroot image to build, install and
boot.  Step two would then be to select all the packages I expect to
need... build, install and boot that.  Step three would be to add custom
packages like a user interface.

I'd love to have a go at this, but unfortunately I simply don't have the
time.

David

On Sun, Jul 13, 2025 at 7:46 PM Michael Knill <
mic...@ip...> wrote:

> Thanks Lonnie/Christopher
>
>
>
> Yes we are now at the stage where our company has no choice but to roll
> our own and we are actively seeking to develop (and/or buy) the skills
> required to do so.
>
> So Im certainly interested in recommendations for doing so.
>
>
>
> Regards
>
> Michael Knill
>
>
>
>
>
> *From: *Lonnie Abelbeck <li...@lo...>
> *Date: *Sunday, 13 July 2025 at 11:36 pm
> *To: *AstLinux Developers Mailing List <
> ast...@li...>
> *Subject: *Re: [Astlinux-devel] Remote access of devices behind Astlinux
>
> Hi Michael,
>
> Christopher (Cadillac Kid) has good info for you.
>
> If I were in your shoes Michael, rolling your own solution from either a
> Debian base or the latest Buildroot seems much better than trying to start
> with the very old Buildroot snapshot AstLinux is based on.  While we have
> maintained the old Buildroot by backporting from upstream over time, this
> is a lot to learn and understand if you are just getting started with
> building custom images.
>
> Lonnie
>
>
> > On Jul 12, 2025, at 7:06 AM, The Cadillac Kid via Astlinux-devel <
> ast...@li...> wrote:
> >
> > we use VPN access for many of our sites..  (granted we rolled our own
> starting about 15 years ago).. we run Mikrotik Hex lites (or other
> variants) in front of our asterisk servers and set up VPN access for
> RMATS..  sites which they wont give us a public IP, we hae a site-to-site
> connection where we can log in to our NOC and remotely access devices on
> the system..  we had issues using straight proxy as grandstream gateways
> werent happy with the oroxy, their web GUI does some wierd stuff.
> >
> > we had broken away from the "one box does it all" setup that astlinux
> provides as we started doing larger sites and asking our systems to do more
> and more.. thus why the MT out front. we have several 3000+ line systems
> out there.. which are also handling communications for hotel PMS, cost
> accounting, etc..
> >
> > On Friday, July 11, 2025 at 10:13:55 PM EDT, Michael Knill <
> mic...@ip...> wrote:
> >
> >
> > Hi All
> >
> > I currently connect to devices behind Astlinux (mainly IP Phones) using
> SSH Tunnelling. This works well but is clunky and not easily scalable (I am
> looking at SSH Certificate Authentication which will be an improvement).
> > I really only need to connect to a directly accessible IP Phone via
> Astlinux using HTTP/S via some proxy mechanism.
> > Does anyone have any ideas? Note that it does not necessarily need to be
> existing Astlinux functionality as we are experimenting with rolling our
> own.
> >
> > Thanks so much.
> >
> > Regards
> >
> > Michael Knill
> > Managing Director
> >
> > D: +61 2 6189 1360
> > P: +61 2 6140 4656
> > E: mic...@ip...
> > W: ipcsolutions.com.au
> >
> >  <image001.png>Smarter Business Communications
> >
> > _______________________________________________
> > Astlinux-devel mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> > <image001.png>_______________________________________________
> > Astlinux-devel mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>
>
>
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>

Re: [Astlinux-devel] Remote access of devices behind Astlinux

[Michael K. <mic...@ip...>]

Thanks Lonnie/Christopher

Yes we are now at the stage where our company has no choice but to roll our own and we are actively seeking to develop (and/or buy) the skills required to do so.
So Im certainly interested in recommendations for doing so.

Regards
Michael Knill


From: Lonnie Abelbeck <li...@lo...>
Date: Sunday, 13 July 2025 at 11:36 pm
To: AstLinux Developers Mailing List <ast...@li...>
Subject: Re: [Astlinux-devel] Remote access of devices behind Astlinux
Hi Michael,

Christopher (Cadillac Kid) has good info for you.

If I were in your shoes Michael, rolling your own solution from either a Debian base or the latest Buildroot seems much better than trying to start with the very old Buildroot snapshot AstLinux is based on.  While we have maintained the old Buildroot by backporting from upstream over time, this is a lot to learn and understand if you are just getting started with building custom images.

Lonnie


> On Jul 12, 2025, at 7:06 AM, The Cadillac Kid via Astlinux-devel <ast...@li...> wrote:
>
> we use VPN access for many of our sites..  (granted we rolled our own starting about 15 years ago).. we run Mikrotik Hex lites (or other variants) in front of our asterisk servers and set up VPN access for RMATS..  sites which they wont give us a public IP, we hae a site-to-site connection where we can log in to our NOC and remotely access devices on the system..  we had issues using straight proxy as grandstream gateways werent happy with the oroxy, their web GUI does some wierd stuff.
>
> we had broken away from the "one box does it all" setup that astlinux provides as we started doing larger sites and asking our systems to do more and more.. thus why the MT out front. we have several 3000+ line systems out there.. which are also handling communications for hotel PMS, cost accounting, etc..
>
> On Friday, July 11, 2025 at 10:13:55 PM EDT, Michael Knill <mic...@ip...> wrote:
>
>
> Hi All
>
> I currently connect to devices behind Astlinux (mainly IP Phones) using SSH Tunnelling. This works well but is clunky and not easily scalable (I am looking at SSH Certificate Authentication which will be an improvement).
> I really only need to connect to a directly accessible IP Phone via Astlinux using HTTP/S via some proxy mechanism.
> Does anyone have any ideas? Note that it does not necessarily need to be existing Astlinux functionality as we are experimenting with rolling our own.
>
> Thanks so much.
>
> Regards
>
> Michael Knill
> Managing Director
>
> D: +61 2 6189 1360
> P: +61 2 6140 4656
> E: mic...@ip...
> W: ipcsolutions.com.au
>
>  <image001.png>Smarter Business Communications
>
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> <image001.png>_______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel



_______________________________________________
Astlinux-devel mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-devel

Re: [Astlinux-devel] Remote access of devices behind Astlinux

[David K. <da...@ke...>]

Lonnie,
  And this begs the question... what would it take to rebase Astlinux on
top of current buildroot.  I mean, really, *how hard can it be?*

Excuse me while I duck to avoid incoming projectiles.

David

On Sun, Jul 13, 2025 at 10:05 AM Lonnie Abelbeck <li...@lo...>
wrote:

> Hi Michael,
>
> Christopher (Cadillac Kid) has good info for you.
>
> If I were in your shoes Michael, rolling your own solution from either a
> Debian base or the latest Buildroot seems much better than trying to start
> with the very old Buildroot snapshot AstLinux is based on.  While we have
> maintained the old Buildroot by backporting from upstream over time, this
> is a lot to learn and understand if you are just getting started with
> building custom images.
>
> Lonnie
>
>
> > On Jul 12, 2025, at 7:06 AM, The Cadillac Kid via Astlinux-devel <
> ast...@li...> wrote:
> >
> > we use VPN access for many of our sites..  (granted we rolled our own
> starting about 15 years ago).. we run Mikrotik Hex lites (or other
> variants) in front of our asterisk servers and set up VPN access for
> RMATS..  sites which they wont give us a public IP, we hae a site-to-site
> connection where we can log in to our NOC and remotely access devices on
> the system..  we had issues using straight proxy as grandstream gateways
> werent happy with the oroxy, their web GUI does some wierd stuff.
> >
> > we had broken away from the "one box does it all" setup that astlinux
> provides as we started doing larger sites and asking our systems to do more
> and more.. thus why the MT out front. we have several 3000+ line systems
> out there.. which are also handling communications for hotel PMS, cost
> accounting, etc..
> >
> > On Friday, July 11, 2025 at 10:13:55 PM EDT, Michael Knill <
> mic...@ip...> wrote:
> >
> >
> > Hi All
> >
> > I currently connect to devices behind Astlinux (mainly IP Phones) using
> SSH Tunnelling. This works well but is clunky and not easily scalable (I am
> looking at SSH Certificate Authentication which will be an improvement).
> > I really only need to connect to a directly accessible IP Phone via
> Astlinux using HTTP/S via some proxy mechanism.
> > Does anyone have any ideas? Note that it does not necessarily need to be
> existing Astlinux functionality as we are experimenting with rolling our
> own.
> >
> > Thanks so much.
> >
> > Regards
> >
> > Michael Knill
> > Managing Director
> >
> > D: +61 2 6189 1360
> > P: +61 2 6140 4656
> > E: mic...@ip...
> > W: ipcsolutions.com.au
> >
> >  <image001.png>Smarter Business Communications
> >
> > _______________________________________________
> > Astlinux-devel mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> > <image001.png>_______________________________________________
> > Astlinux-devel mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>
>
>
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>

Re: [Astlinux-devel] Remote access of devices behind Astlinux

[Lonnie A. <li...@lo...>]

Hi Michael,

Christopher (Cadillac Kid) has good info for you.

If I were in your shoes Michael, rolling your own solution from either a Debian base or the latest Buildroot seems much better than trying to start with the very old Buildroot snapshot AstLinux is based on.  While we have maintained the old Buildroot by backporting from upstream over time, this is a lot to learn and understand if you are just getting started with building custom images.

Lonnie


> On Jul 12, 2025, at 7:06 AM, The Cadillac Kid via Astlinux-devel <ast...@li...> wrote:
> 
> we use VPN access for many of our sites..  (granted we rolled our own starting about 15 years ago).. we run Mikrotik Hex lites (or other variants) in front of our asterisk servers and set up VPN access for RMATS..  sites which they wont give us a public IP, we hae a site-to-site connection where we can log in to our NOC and remotely access devices on the system..  we had issues using straight proxy as grandstream gateways werent happy with the oroxy, their web GUI does some wierd stuff. 
> 
> we had broken away from the "one box does it all" setup that astlinux provides as we started doing larger sites and asking our systems to do more and more.. thus why the MT out front. we have several 3000+ line systems out there.. which are also handling communications for hotel PMS, cost accounting, etc.. 
> 
> On Friday, July 11, 2025 at 10:13:55 PM EDT, Michael Knill <mic...@ip...> wrote: 
> 
> 
> Hi All
>  
> I currently connect to devices behind Astlinux (mainly IP Phones) using SSH Tunnelling. This works well but is clunky and not easily scalable (I am looking at SSH Certificate Authentication which will be an improvement).
> I really only need to connect to a directly accessible IP Phone via Astlinux using HTTP/S via some proxy mechanism.
> Does anyone have any ideas? Note that it does not necessarily need to be existing Astlinux functionality as we are experimenting with rolling our own.
>  
> Thanks so much.
>  
> Regards
>  
> Michael Knill
> Managing Director
>  
> D: +61 2 6189 1360
> P: +61 2 6140 4656
> E: mic...@ip...
> W: ipcsolutions.com.au
>  
>  <image001.png>Smarter Business Communications
>  
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> <image001.png>_______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel

Re: [Astlinux-devel] Remote access of devices behind Astlinux

[The C. K. <eld...@ya...>]

 we use VPN access for many of our sites..  (granted we rolled our own starting about 15 years ago).. we run Mikrotik Hex lites (or other variants) in front of our asterisk servers and set up VPN access for RMATS..  sites which they wont give us a public IP, we hae a site-to-site connection where we can log in to our NOC and remotely access devices on the system..  we had issues using straight proxy as grandstream gateways werent happy with the oroxy, their web GUI does some wierd stuff. 
we had broken away from the "one box does it all" setup that astlinux provides as we started doing larger sites and asking our systems to do more and more.. thus why the MT out front. we have several 3000+ line systems out there.. which are also handling communications for hotel PMS, cost accounting, etc.. 
    On Friday, July 11, 2025 at 10:13:55 PM EDT, Michael Knill <mic...@ip...> wrote:  
 
  
Hi All
 
  
 
I currently connect to devices behind Astlinux (mainly IP Phones) using SSH Tunnelling. This works well but is clunky and not easily scalable (I am looking at SSH Certificate Authentication which will be an improvement).
 
I really only need to connect to a directly accessible IP Phone via Astlinux using HTTP/S via some proxy mechanism.
 
Does anyone have any ideas? Note that it does not necessarily need to be existing Astlinux functionality as we are experimenting with rolling our own.
 
  
 
Thanks so much.
 
  
 
Regards
 
 
 
Michael Knill
 
Managing Director
 
 
 
D: +61 2 6189 1360
 
P: +61 2 6140 4656
 
E: mic...@ip...
 
W: ipcsolutions.com.au
 
 
 
 
 
Smarter Business Communications
 
  
 _______________________________________________
Astlinux-devel mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-devel
  

[Astlinux-devel] Remote access of devices behind Astlinux

[Michael K. <mic...@ip...>]

Hi All

I currently connect to devices behind Astlinux (mainly IP Phones) using SSH Tunnelling. This works well but is clunky and not easily scalable (I am looking at SSH Certificate Authentication which will be an improvement).
I really only need to connect to a directly accessible IP Phone via Astlinux using HTTP/S via some proxy mechanism.
Does anyone have any ideas? Note that it does not necessarily need to be existing Astlinux functionality as we are experimenting with rolling our own.

Thanks so much.

Regards

Michael Knill
Managing Director

D: +61 2 6189 1360<tel:+61261891360>
P: +61 2 6140 4656<tel:+61261404656>
E: mic...@ip...<mailto:mic...@ip...>
W: ipcsolutions.com.au<https://ipcsolutions.com.au/>

 [Icon  Description automatically generated]
Smarter Business Communications

Re: [Astlinux-devel] Console in a VM

[David K. <da...@ke...>]

Lonnie,
  I do have a different machine h/w specified... I selected Q35 because it
is considered a more modern environment.  That may have something to do
with it, I will test (with a sandbox this time!!!!) and let you know.

>From Google's AI...

*In QEMU, the Q35 machine type is generally preferred over i440fx for
modern use cases, especially when dealing with PCIe devices and advanced
features like GPU passthrough. While i440fx is an older, more compatible
option for some legacy systems, Q35 offers better support for newer
hardware and virtualization technologies. *


Regards,
David




On Mon, Jul 7, 2025 at 9:51 AM Lonnie Abelbeck <li...@lo...>
wrote:

> Hi David,
>
> I spent some time testing with Proxmox, and it works as I remembered.
>
> I ran the AstLinux ISO installer under Legacy BIOS, performed a setup
> under Legacy BIOS, and then switched to UEFI BIOS.  All worked as
> expected.  Switched between Legacy and UEFI a couple times for good
> measure, no issues.
>
> I'm using Proxmox Virtual Environment 8.1.11
>
> Note: I always get a warning when booing via UEFI:
> --
> WARN: no efidisk configured! Using temporary efivars disk.
> TASK WARNINGS: 1
> --
>
> Hardware:
>
>
> Possibly you have a different "Machine" specified?  That can affect
> booting.
>
> Just for giggles, I also tested an AstLinux VM under "UTM" [1] on a M2 Mac
> Mini, I can toggle between UEFI enabled and not enabled without issues.
>
> Lonnie
>
> [1] https://doc.astlinux-project.org/userdoc:guest_vm_utm
>
>
>
> > On Jul 6, 2025, at 8:09 PM, Lonnie Abelbeck <li...@lo...>
> wrote:
> >
> > David, sorry to hear that.  I know I have switched back and forth
> between Legacy and UEFI BIOS in the past in Proxmox.
> >
> > The ISO installer must be done via Legacy and switch later to UEFI if
> desired, which I have done.
> >
> > Very surprised to hear your results.
> >
> > Lonnie
> >
> >
> >> On Jul 6, 2025, at 7:44 PM, David Kerr <da...@ke...> wrote:
> >>
> >> Lonnie,
> >>  I have been traveling for a couple of weeks so just got around to
> trying this.  I did a shutdown -h in astlinux, changed proxmox settings for
> the VM to use UEFI, restarted the VM and bad things happened.  First,
> opening the console just displayed a message that Guest has not initialized
> the display (yet) and it just stuck like that.  Worse, I could not ssh
> in... and it never responded to pings.  So I shutdown the VM again from
> proxmox, changed the bios back to the SeaBIOS, and rebooted.  And it
> failed... console reported that it could not find a bootable disk, it tried
> to boot from the network.
> >>
> >> Fortunately I have proxmox doing a daily backup/snapshot of the VM and
> I was able to restore that and get going again.
> >>
> >> I have a feeling that a fresh install with UEFI right from the start
> may be required?
> >>
> >> David.
> >>
> >>
> >>
> >> On Fri, Jun 20, 2025 at 7:15 AM Lonnie Abelbeck <
> li...@lo...> wrote:
> >>> Is it safe to switch an existing installed VM to UEFI and just reboot?
> >>
> >> "poweroff" AstLinux in the VM, switch the VM to "BIOS: UEFI", then
> Start the VM.
> >>
> >> I have an AstLinux VM with UEFI enabled mostly for testing.  I almost
> always use SSH when interacting.
> >>
> >> Also, I seem to recall Proxmox issues a warning about temporary efi
> vars or some such ... you can ignore that.
> >>
> >> Lonnie
> >>
> >>
> >>
> >>> On Jun 19, 2025, at 10:38 PM, David Kerr <da...@ke...> wrote:
> >>>
> >>> Thanks Lonnie,
> >>> Looks like I was wrong on the color, I do get that.  But I would like
> to have a higher resolution.  So, if I use UEFI bios then I should get
> that?  I've always installed Astlinux with the default SeaBIOS (on
> Proxmox).  Is it safe to switch an existing installed VM to UEFI and just
> reboot?
> >>>
> >>> David
> >>>
> >>> <image.png>
> >>>
> >>> On Thu, Jun 19, 2025 at 9:06 PM Lonnie Abelbeck <
> li...@lo...> wrote:
> >>> Hi David,
> >>>
> >>> The VNC console has been color whenever I use it.  Not sure how that
> could be B/W.
> >>>
> >>> Note that if you use UEFI the screen will be higher resolution, for
> example [1].
> >>>
> >>> Though it has always seemed to be a fixed window size, just a lower
> resolution with Legacy BIOS.
> >>>
> >>> Lonnie
> >>>
> >>> [1]
> >>>
> >>>
> >>>
> >>>
> >>>> On Jun 19, 2025, at 5:09 PM, David Kerr <Da...@Ke...> wrote:
> >>>>
> >>>> Running Astlinux in a VM and using VNC (Proxmox) console, the text
> display is a very confined 80x24 and black-and-white.  Every other
> text-based VM that I fire up, I can resize the VNC window and the number of
> rows/columns expands, and text colors are shown.
> >>>>
> >>>> Is it possible to have Astlinux do the same?
> >>>>
> >>>> Thanks
> >>>> David
> >>>> _______________________________________________
> >>>> Astlinux-devel mailing list
> >>>> Ast...@li...
> >>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> >>>
> >>> _______________________________________________
> >>> Astlinux-devel mailing list
> >>> Ast...@li...
> >>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> >>> _______________________________________________
> >>> Astlinux-devel mailing list
> >>> Ast...@li...
> >>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> >>
> >>
> >>
> >> _______________________________________________
> >> Astlinux-devel mailing list
> >> Ast...@li...
> >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> >> _______________________________________________
> >> Astlinux-devel mailing list
> >> Ast...@li...
> >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> >
> >
> >
> > _______________________________________________
> > Astlinux-devel mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>

Re: [Astlinux-devel] Console in a VM

[Lonnie A. <li...@lo...>]

Hi David,

I spent some time testing with Proxmox, and it works as I remembered.

I ran the AstLinux ISO installer under Legacy BIOS, performed a setup under Legacy BIOS, and then switched to UEFI BIOS.  All worked as expected.  Switched between Legacy and UEFI a couple times for good measure, no issues.

I'm using Proxmox Virtual Environment 8.1.11

Note: I always get a warning when booing via UEFI:
--
WARN: no efidisk configured! Using temporary efivars disk.
TASK WARNINGS: 1
--

Hardware:

Re: [Astlinux-devel] Console in a VM

[Lonnie A. <li...@lo...>]

David, sorry to hear that.  I know I have switched back and forth between Legacy and UEFI BIOS in the past in Proxmox.

The ISO installer must be done via Legacy and switch later to UEFI if desired, which I have done.

Very surprised to hear your results.

Lonnie


> On Jul 6, 2025, at 7:44 PM, David Kerr <da...@ke...> wrote:
> 
> Lonnie,
>   I have been traveling for a couple of weeks so just got around to trying this.  I did a shutdown -h in astlinux, changed proxmox settings for the VM to use UEFI, restarted the VM and bad things happened.  First, opening the console just displayed a message that Guest has not initialized the display (yet) and it just stuck like that.  Worse, I could not ssh in... and it never responded to pings.  So I shutdown the VM again from proxmox, changed the bios back to the SeaBIOS, and rebooted.  And it failed... console reported that it could not find a bootable disk, it tried to boot from the network.
> 
> Fortunately I have proxmox doing a daily backup/snapshot of the VM and I was able to restore that and get going again.
> 
> I have a feeling that a fresh install with UEFI right from the start may be required?
> 
> David.
> 
> 
> 
> On Fri, Jun 20, 2025 at 7:15 AM Lonnie Abelbeck <li...@lo...> wrote:
> > Is it safe to switch an existing installed VM to UEFI and just reboot?
> 
> "poweroff" AstLinux in the VM, switch the VM to "BIOS: UEFI", then Start the VM.
> 
> I have an AstLinux VM with UEFI enabled mostly for testing.  I almost always use SSH when interacting.
> 
> Also, I seem to recall Proxmox issues a warning about temporary efi vars or some such ... you can ignore that.
> 
> Lonnie
> 
> 
> 
> > On Jun 19, 2025, at 10:38 PM, David Kerr <da...@ke...> wrote:
> > 
> > Thanks Lonnie,
> > Looks like I was wrong on the color, I do get that.  But I would like to have a higher resolution.  So, if I use UEFI bios then I should get that?  I've always installed Astlinux with the default SeaBIOS (on Proxmox).  Is it safe to switch an existing installed VM to UEFI and just reboot?
> > 
> > David
> > 
> > <image.png>
> > 
> > On Thu, Jun 19, 2025 at 9:06 PM Lonnie Abelbeck <li...@lo...> wrote:
> > Hi David,
> > 
> > The VNC console has been color whenever I use it.  Not sure how that could be B/W.
> > 
> > Note that if you use UEFI the screen will be higher resolution, for example [1].
> > 
> > Though it has always seemed to be a fixed window size, just a lower resolution with Legacy BIOS.
> > 
> > Lonnie
> > 
> > [1]
> > 
> > 
> > 
> > 
> > > On Jun 19, 2025, at 5:09 PM, David Kerr <Da...@Ke...> wrote:
> > > 
> > > Running Astlinux in a VM and using VNC (Proxmox) console, the text display is a very confined 80x24 and black-and-white.  Every other text-based VM that I fire up, I can resize the VNC window and the number of rows/columns expands, and text colors are shown.
> > > 
> > > Is it possible to have Astlinux do the same?
> > > 
> > > Thanks
> > > David
> > > _______________________________________________
> > > Astlinux-devel mailing list
> > > Ast...@li...
> > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> > 
> > _______________________________________________
> > Astlinux-devel mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> > _______________________________________________
> > Astlinux-devel mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> 
> 
> 
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel

Re: [Astlinux-devel] Console in a VM

[David K. <da...@ke...>]

Lonnie,
  I have been traveling for a couple of weeks so just got around to trying
this.  I did a shutdown -h in astlinux, changed proxmox settings for the VM
to use UEFI, restarted the VM and bad things happened.  First, opening the
console just displayed a message that *Guest has not initialized the
display (yet)* and it just stuck like that.  Worse, I could not ssh in...
and it never responded to pings.  So I shutdown the VM again from proxmox,
changed the bios back to the SeaBIOS, and rebooted.  And it failed...
console reported that it could not find a bootable disk, it tried to boot
from the network.

Fortunately I have proxmox doing a daily backup/snapshot of the VM and I
was able to restore that and get going again.

I have a feeling that a fresh install with UEFI right from the start may be
required?

David.



On Fri, Jun 20, 2025 at 7:15 AM Lonnie Abelbeck <li...@lo...>
wrote:

> > Is it safe to switch an existing installed VM to UEFI and just reboot?
>
> "poweroff" AstLinux in the VM, switch the VM to "BIOS: UEFI", then Start
> the VM.
>
> I have an AstLinux VM with UEFI enabled mostly for testing.  I almost
> always use SSH when interacting.
>
> Also, I seem to recall Proxmox issues a warning about temporary efi vars
> or some such ... you can ignore that.
>
> Lonnie
>
>
>
> > On Jun 19, 2025, at 10:38 PM, David Kerr <da...@ke...> wrote:
> >
> > Thanks Lonnie,
> > Looks like I was wrong on the color, I do get that.  But I would like to
> have a higher resolution.  So, if I use UEFI bios then I should get that?
> I've always installed Astlinux with the default SeaBIOS (on Proxmox).  Is
> it safe to switch an existing installed VM to UEFI and just reboot?
> >
> > David
> >
> > <image.png>
> >
> > On Thu, Jun 19, 2025 at 9:06 PM Lonnie Abelbeck <
> li...@lo...> wrote:
> > Hi David,
> >
> > The VNC console has been color whenever I use it.  Not sure how that
> could be B/W.
> >
> > Note that if you use UEFI the screen will be higher resolution, for
> example [1].
> >
> > Though it has always seemed to be a fixed window size, just a lower
> resolution with Legacy BIOS.
> >
> > Lonnie
> >
> > [1]
> >
> >
> >
> >
> > > On Jun 19, 2025, at 5:09 PM, David Kerr <Da...@Ke...> wrote:
> > >
> > > Running Astlinux in a VM and using VNC (Proxmox) console, the text
> display is a very confined 80x24 and black-and-white.  Every other
> text-based VM that I fire up, I can resize the VNC window and the number of
> rows/columns expands, and text colors are shown.
> > >
> > > Is it possible to have Astlinux do the same?
> > >
> > > Thanks
> > > David
> > > _______________________________________________
> > > Astlinux-devel mailing list
> > > Ast...@li...
> > > https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> >
> > _______________________________________________
> > Astlinux-devel mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> > _______________________________________________
> > Astlinux-devel mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>
>
>
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>

Re: [Astlinux-devel] Mail API

[Michael K. <mic...@ip...>]

Thanks all.

Regards
Michael Knill


From: David Kerr <da...@ke...>
Date: Sunday, 6 July 2025 at 1:41 am
To: AstLinux Developers Mailing List <ast...@li...>
Subject: Re: [Astlinux-devel] Mail API
One of the enhancements I made in my fork was to add a system-notify script.  This lets me consolidate into one place all "outbound" notifications which could be Email, Pushover, SMS, whatever.  This adding/changing how a notification is sent can be done in one place.  I updated all services that had their own Email notification code to use this instead.

https://github.com/dkerr64/astlinux/blob/master/project/astlinux/target_skeleton/usr/sbin/system-notify

And in my rc.conf (for example)...

SYSTEM_NOTIFY da...@ke...<mailto:da...@ke...>
SYSTEM_NOTIFY_FROM pb...@ke...<mailto:pb...@ke...>
PUSHOVER_APP_TOKEN atuwaxxxxxxxxxxxxxxob2jce
PUSHOVER_USER_KEY uknjvgxxxxxxxxxxxxxxxgnuec5
PUSHOVER_API https://api.pushover.net/1/messages.json
PUSHOVER_IP 104.20.42.236
SMS_CMD /mnt/kd/bin/LB1120
SMS_URL 192.168.5.1
SMS_PW ExxxxxxxC
SMS_TO +1203xxxxx92
NOTIFY_PUSHOVER_UPSMON yes
NOTIFY_PUSHOVER_WANFAILOVER yes
NOTIFY_PUSHOVER_ACME yes
NOTIFY_PUSHOVER_SSHD yes

So, with my fork, a change to use Mailgun can be done in one place, and all services would use.

David


On Sat, Jul 5, 2025 at 11:16 AM Lonnie Abelbeck <li...@lo...<mailto:li...@lo...>> wrote:
Hi Michael,

I have heard good things about Mailgun, but have not personally used it.

When using the Mailgun SMTP Relay, is there only one auth credential per account, or could every unique API key auth the SMTP Relay?

Possibly different users in Mailgun would need to be created for multiple SMTP Relay credentials.


> ... we have also left the SMTP email for applications that are not using the API.
> My question is which ones they could be. The only one I have identified is ‘safe asterisk’ but just wondering if there are any others?

There are quite a few services that use sendmail (via msmtp), in AstLinux [1] the scripts sendmail.sh, msmtpqueue.sh, testmail.sh call 'msmtp'.

A dev could create an 'api-smtp' shell script, alternative to 'msmtp', that takes input like sendmail, produces error codes like sendmail, but uses 'curl' and  Mailgun APIs to send the message.

Lonnie

[1] https://github.com/astlinux-project/astlinux/tree/master/package/msmtp




> On Jul 5, 2025, at 1:24 AM, Michael Knill <mic...@ip...<mailto:mic...@ip...>> wrote:
>
> Hi Devs
>  We are currently using Mailgun for sending mail from Astlinux which works great but I am quite concerned about having the same credentials on all my systems. This is actually an issue for a number of our integrations which is why we are moving to the Azure API Manager in our next release.
>  Although this will be fine for applications using the current Mailgun API e.g. voicemail, we have also left the SMTP email for applications that are not using the API.
> My question is which ones they could be. The only one I have identified is ‘safe asterisk’ but just wondering if there are any others?
>  Regards
>  Michael Knill
> Managing Director
>  D: +61 2 6189 1360
> P: +61 2 6140 4656
> E: mic...@ip...<mailto:mic...@ip...>
> W: ipcsolutions.com.au<http://ipcsolutions.com.au>
>   <image001.png>Smarter Business Communications
>  _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...<mailto:Ast...@li...>
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel




_______________________________________________
Astlinux-devel mailing list
Ast...@li...<mailto:Ast...@li...>
https://lists.sourceforge.net/lists/listinfo/astlinux-devel

Re: [Astlinux-devel] Mail API

[David K. <da...@ke...>]

One of the enhancements I made in my fork was to add a system-notify
script.  This lets me consolidate into one place all "outbound"
notifications which could be Email, Pushover, SMS, whatever.  This
adding/changing how a notification is sent can be done in one place.  I
updated all services that had their own Email notification code to use this
instead.

https://github.com/dkerr64/astlinux/blob/master/project/astlinux/target_skeleton/usr/sbin/system-notify

And in my rc.conf (for example)...

SYSTEM_NOTIFY da...@ke...
SYSTEM_NOTIFY_FROM pb...@ke...
PUSHOVER_APP_TOKEN atuwaxxxxxxxxxxxxxxob2jce
PUSHOVER_USER_KEY uknjvgxxxxxxxxxxxxxxxgnuec5
PUSHOVER_API https://api.pushover.net/1/messages.json
PUSHOVER_IP 104.20.42.236
SMS_CMD /mnt/kd/bin/LB1120
SMS_URL 192.168.5.1
SMS_PW ExxxxxxxC
SMS_TO +1203xxxxx92
NOTIFY_PUSHOVER_UPSMON yes
NOTIFY_PUSHOVER_WANFAILOVER yes
NOTIFY_PUSHOVER_ACME yes
NOTIFY_PUSHOVER_SSHD yes

So, with my fork, a change to use Mailgun can be done in one place, and all
services would use.

David


On Sat, Jul 5, 2025 at 11:16 AM Lonnie Abelbeck <li...@lo...>
wrote:

> Hi Michael,
>
> I have heard good things about Mailgun, but have not personally used it.
>
> When using the Mailgun SMTP Relay, is there only one auth credential per
> account, or could every unique API key auth the SMTP Relay?
>
> Possibly different users in Mailgun would need to be created for multiple
> SMTP Relay credentials.
>
>
> > ... we have also left the SMTP email for applications that are not using
> the API.
> > My question is which ones they could be. The only one I have identified
> is ‘safe asterisk’ but just wondering if there are any others?
>
> There are quite a few services that use sendmail (via msmtp), in AstLinux
> [1] the scripts sendmail.sh, msmtpqueue.sh, testmail.sh call 'msmtp'.
>
> A dev could create an 'api-smtp' shell script, alternative to 'msmtp',
> that takes input like sendmail, produces error codes like sendmail, but
> uses 'curl' and  Mailgun APIs to send the message.
>
> Lonnie
>
> [1] https://github.com/astlinux-project/astlinux/tree/master/package/msmtp
>
>
>
>
> > On Jul 5, 2025, at 1:24 AM, Michael Knill <
> mic...@ip...> wrote:
> >
> > Hi Devs
> >  We are currently using Mailgun for sending mail from Astlinux which
> works great but I am quite concerned about having the same credentials on
> all my systems. This is actually an issue for a number of our integrations
> which is why we are moving to the Azure API Manager in our next release.
> >  Although this will be fine for applications using the current Mailgun
> API e.g. voicemail, we have also left the SMTP email for applications that
> are not using the API.
> > My question is which ones they could be. The only one I have identified
> is ‘safe asterisk’ but just wondering if there are any others?
> >  Regards
> >  Michael Knill
> > Managing Director
> >  D: +61 2 6189 1360
> > P: +61 2 6140 4656
> > E: mic...@ip...
> > W: ipcsolutions.com.au
> >   <image001.png>Smarter Business Communications
> >  _______________________________________________
> > Astlinux-devel mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>
>
>
>
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>

Re: [Astlinux-devel] Mail API

[Lonnie A. <li...@lo...>]

Hi Michael,

I have heard good things about Mailgun, but have not personally used it.

When using the Mailgun SMTP Relay, is there only one auth credential per account, or could every unique API key auth the SMTP Relay?

Possibly different users in Mailgun would need to be created for multiple SMTP Relay credentials.


> ... we have also left the SMTP email for applications that are not using the API.
> My question is which ones they could be. The only one I have identified is ‘safe asterisk’ but just wondering if there are any others?

There are quite a few services that use sendmail (via msmtp), in AstLinux [1] the scripts sendmail.sh, msmtpqueue.sh, testmail.sh call 'msmtp'.

A dev could create an 'api-smtp' shell script, alternative to 'msmtp', that takes input like sendmail, produces error codes like sendmail, but uses 'curl' and  Mailgun APIs to send the message.

Lonnie

[1] https://github.com/astlinux-project/astlinux/tree/master/package/msmtp




> On Jul 5, 2025, at 1:24 AM, Michael Knill <mic...@ip...> wrote:
> 
> Hi Devs
>  We are currently using Mailgun for sending mail from Astlinux which works great but I am quite concerned about having the same credentials on all my systems. This is actually an issue for a number of our integrations which is why we are moving to the Azure API Manager in our next release.
>  Although this will be fine for applications using the current Mailgun API e.g. voicemail, we have also left the SMTP email for applications that are not using the API.
> My question is which ones they could be. The only one I have identified is ‘safe asterisk’ but just wondering if there are any others?
>  Regards
>  Michael Knill
> Managing Director
>  D: +61 2 6189 1360
> P: +61 2 6140 4656
> E: mic...@ip...
> W: ipcsolutions.com.au
>   <image001.png>Smarter Business Communications
>  _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel

[Astlinux-devel] Mail API

[Michael K. <mic...@ip...>]

Hi Devs

We are currently using Mailgun for sending mail from Astlinux which works great but I am quite concerned about having the same credentials on all my systems. This is actually an issue for a number of our integrations which is why we are moving to the Azure API Manager in our next release.

Although this will be fine for applications using the current Mailgun API e.g. voicemail, we have also left the SMTP email for applications that are not using the API.
My question is which ones they could be. The only one I have identified is ‘safe asterisk’ but just wondering if there are any others?

Regards

Michael Knill
Managing Director

D: +61 2 6189 1360<tel:+61261891360>
P: +61 2 6140 4656<tel:+61261404656>
E: mic...@ip...<mailto:mic...@ip...>
W: ipcsolutions.com.au<https://ipcsolutions.com.au/>

 [Icon  Description automatically generated]
Smarter Business Communications

Re: [Astlinux-devel] Errors with custom build

[Michael K. <mic...@ip...>]

Thanks David. Will give that a try.

Regards
Michael Knill


From: David Kerr <da...@ke...>
Date: Saturday, 5 July 2025 at 1:21 pm
To: AstLinux Developers Mailing List <ast...@li...>
Subject: Re: [Astlinux-devel] Errors with custom build
Michael,
  Try running the build a second time.  The log shows that the .sha1 file for nmap is not being downloaded.  This is a checksum used to validate that the component build file downloaded without any corruption.  But if the file is already downloaded (which it will be on a second run) then the build process does not look for a .sha1 file or do the checksum (it is assumed to be okay).  Now-a-days download corruption is extremely unlikely, so you should be good.

I have been doing a custom build of Astlinux for years, and am able to keep up-to-date by merging the changes Lonnie makes into my build every few months.  Occasionally I run into a problem like this.

David

On Fri, Jul 4, 2025 at 10:46 PM Michael Knill <mic...@ip...<mailto:mic...@ip...>> wrote:
Hi Devs

Its been a long time coming and we have been able to hang out for a good while but we are at the stage that we are going to need to build our own image.
The main trigger for this is our desire to take our system to the next level with a completely redesigned portal for direct access by customers and partners.
This will entail the updating of PHP, overlaying the incredibly stable and low footprint Astlinux core which we have no desire to move from.

In our first steps we have attempted to build our own AstLinux image by closely following this guide: https://doc.astlinux-project.org/devdoc:documentation.
The “First Build” seemed to work fine, however, once we got to the “Custom Build” the build failed (log attached). The only additional packages selected were nmap and sipp.

Here are the specs of our build system (hosted on Vultr):
•         OS: Debian 12 x64
•         vCPU/s: 2 vCPUs
•         RAM: 2048.00 MB

Thanks so much for your help.

This is a new and exciting journey for us moving forward and Im expecting lots of hurdles but also expecting amazing outcomes.

Regards
Michael Knill

_______________________________________________
Astlinux-devel mailing list
Ast...@li...<mailto:Ast...@li...>
https://lists.sourceforge.net/lists/listinfo/astlinux-devel

Re: [Astlinux-devel] Errors with custom build

[David K. <da...@ke...>]

Michael,
  Try running the build a second time.  The log shows that the .sha1 file
for nmap is not being downloaded.  This is a checksum used to validate that
the component build file downloaded without any corruption.  But if the
file is already downloaded (which it will be on a second run) then the
build process does not look for a .sha1 file or do the checksum (it is
assumed to be okay).  Now-a-days download corruption is extremely unlikely,
so you should be good.

I have been doing a custom build of Astlinux for years, and am able to keep
up-to-date by merging the changes Lonnie makes into my build every few
months.  Occasionally I run into a problem like this.

David

On Fri, Jul 4, 2025 at 10:46 PM Michael Knill <
mic...@ip...> wrote:

> Hi Devs
>
>
>
> Its been a long time coming and we have been able to hang out for a good
> while but we are at the stage that we are going to need to build our own
> image.
>
> The main trigger for this is our desire to take our system to the next
> level with a completely redesigned portal for direct access by customers
> and partners.
>
> This will entail the updating of PHP, overlaying the incredibly stable and
> low footprint Astlinux core which we have no desire to move from.
>
>
>
> In our first steps we have attempted to build our own AstLinux image by
> closely following this guide:
> https://doc.astlinux-project.org/devdoc:documentation.
>
> The “First Build” seemed to work fine, however, once we got to the “Custom
> Build” the build failed (log attached). The only additional packages
> selected were *nmap* and *sipp*.
>
>
>
> Here are the specs of our build system (hosted on Vultr):
>
> ·         OS: Debian 12 x64
>
> ·         vCPU/s: 2 vCPUs
>
> ·         RAM: 2048.00 MB
>
>
>
> Thanks so much for your help.
>
>
>
> This is a new and exciting journey for us moving forward and Im expecting
> lots of hurdles but also expecting amazing outcomes.
>
>
>
> Regards
>
> Michael Knill
>
>
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>

[Astlinux-devel] Errors with custom build

[Michael K. <mic...@ip...>]

Hi Devs

Its been a long time coming and we have been able to hang out for a good while but we are at the stage that we are going to need to build our own image.
The main trigger for this is our desire to take our system to the next level with a completely redesigned portal for direct access by customers and partners.
This will entail the updating of PHP, overlaying the incredibly stable and low footprint Astlinux core which we have no desire to move from.

In our first steps we have attempted to build our own AstLinux image by closely following this guide: https://doc.astlinux-project.org/devdoc:documentation.
The “First Build” seemed to work fine, however, once we got to the “Custom Build” the build failed (log attached). The only additional packages selected were nmap and sipp.

Here are the specs of our build system (hosted on Vultr):
·         OS: Debian 12 x64
·         vCPU/s: 2 vCPUs
·         RAM: 2048.00 MB

Thanks so much for your help.

This is a new and exciting journey for us moving forward and Im expecting lots of hurdles but also expecting amazing outcomes.

Regards
Michael Knill

Re: [Astlinux-devel] Console in a VM

[Lonnie A. <li...@lo...>]

> Is it safe to switch an existing installed VM to UEFI and just reboot?

"poweroff" AstLinux in the VM, switch the VM to "BIOS: UEFI", then Start the VM.

I have an AstLinux VM with UEFI enabled mostly for testing.  I almost always use SSH when interacting.

Also, I seem to recall Proxmox issues a warning about temporary efi vars or some such ... you can ignore that.

Lonnie



> On Jun 19, 2025, at 10:38 PM, David Kerr <da...@ke...> wrote:
> 
> Thanks Lonnie,
> Looks like I was wrong on the color, I do get that.  But I would like to have a higher resolution.  So, if I use UEFI bios then I should get that?  I've always installed Astlinux with the default SeaBIOS (on Proxmox).  Is it safe to switch an existing installed VM to UEFI and just reboot?
> 
> David
> 
> <image.png>
> 
> On Thu, Jun 19, 2025 at 9:06 PM Lonnie Abelbeck <li...@lo...> wrote:
> Hi David,
> 
> The VNC console has been color whenever I use it.  Not sure how that could be B/W.
> 
> Note that if you use UEFI the screen will be higher resolution, for example [1].
> 
> Though it has always seemed to be a fixed window size, just a lower resolution with Legacy BIOS.
> 
> Lonnie
> 
> [1]
> 
> 
> 
> 
> > On Jun 19, 2025, at 5:09 PM, David Kerr <Da...@Ke...> wrote:
> > 
> > Running Astlinux in a VM and using VNC (Proxmox) console, the text display is a very confined 80x24 and black-and-white.  Every other text-based VM that I fire up, I can resize the VNC window and the number of rows/columns expands, and text colors are shown.
> > 
> > Is it possible to have Astlinux do the same?
> > 
> > Thanks
> > David
> > _______________________________________________
> > Astlinux-devel mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> 
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel

Re: [Astlinux-devel] Console in a VM

[David K. <da...@ke...>]

Thanks Lonnie,
Looks like I was wrong on the color, I do get that.  But I would like to
have a higher resolution.  So, if I use UEFI bios then I should get that?
I've always installed Astlinux with the default SeaBIOS (on Proxmox).  Is
it safe to switch an existing installed VM to UEFI and just reboot?

David

[image: image.png]

On Thu, Jun 19, 2025 at 9:06 PM Lonnie Abelbeck <li...@lo...>
wrote:

> Hi David,
>
> The VNC console has been color whenever I use it.  Not sure how that could
> be B/W.
>
> Note that if you use UEFI the screen will be higher resolution, for
> example [1].
>
> Though it has always seemed to be a fixed window size, just a lower
> resolution with Legacy BIOS.
>
> Lonnie
>
> [1]
>
>
>
>
> > On Jun 19, 2025, at 5:09 PM, David Kerr <Da...@Ke...> wrote:
> >
> > Running Astlinux in a VM and using VNC (Proxmox) console, the text
> display is a very confined 80x24 and black-and-white.  Every other
> text-based VM that I fire up, I can resize the VNC window and the number of
> rows/columns expands, and text colors are shown.
> >
> > Is it possible to have Astlinux do the same?
> >
> > Thanks
> > David
> > _______________________________________________
> > Astlinux-devel mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>

Re: [Astlinux-devel] Console in a VM

[Lonnie A. <li...@lo...>]

Hi David,

The VNC console has been color whenever I use it.  Not sure how that could be B/W.

Note that if you use UEFI the screen will be higher resolution, for example [1].

Though it has always seemed to be a fixed window size, just a lower resolution with Legacy BIOS.

Lonnie

[1]

[Astlinux-devel] Console in a VM

[David K. <da...@ke...>]

Running Astlinux in a VM and using VNC (Proxmox) console, the text display
is a very confined 80x24 and black-and-white.  Every other text-based VM
that I fire up, I can resize the VNC window and the number of rows/columns
expands, and text colors are shown.

Is it possible to have Astlinux do the same?

Thanks
David

Re: [Astlinux-devel] Problems compiling nice editor

[David K. <da...@ke...>]

Thanks Lonnie.   Build underway again.

David

On Sun, Jun 15, 2025 at 1:47 PM Lonnie Abelbeck <li...@lo...>
wrote:

> Hi David,
>
> Thanks for the info.
>
> Yes, the https://ne.di.unimi.it URL now forwards to the github site [2],
> not the autoconf download.
>
> I made a commit [1] to use our  ne-3.3.4.tar.gz copy, and the next release
> we can use the github tag.
>
> Thanks David!
>
> Lonnie
>
> [1]
> https://github.com/astlinux-project/astlinux/commit/fead6b59f4de4a350030615cdcf3ed92b5aa1b6c
>
> [2]
> --
> $ curl -LI https://ne.di.unimi.it/
> HTTP/1.1 302 Found
> Date: Sun, 15 Jun 2025 17:32:55 GMT
> Server: Apache/2.4.62 (Fedora Linux) OpenSSL/3.2.2 mod_jk/1.2.48
> Location: http://github.com/vigna/ne/
> Content-Type: text/html; charset=iso-8859-1
>
> HTTP/1.1 301 Moved Permanently
> Content-Length: 0
> Location: https://github.com/vigna/ne/
>
> HTTP/2 200  date: Sun, 15 Jun 2025 17:32:55 GMT
> content-type: text/html; charset=utf-8
> vary: X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame,
> X-Requested-With,Accept-Encoding, Accept, X-Requested-With
> etag: W/"f2c215b4cca5b2f293019cf300168950"
> ...
> --
>
>
>
> > On Jun 15, 2025, at 10:35 AM, David Kerr <Da...@Ke...> wrote:
> >
> > Trying to build astlinux today and I am getting this error...
> >
> > >>> ne 3.3.4 Extracting
> > gzip -d -c /home/david/github/astlinux/dl/ne-3.3.4.tar.gz | tar
> --strip-components=1 -C /home/david/github/astlinux/output/build/ne-3.3.4
> -xf -
> >
> > gzip: /home/david/github/astlinux/dl/ne-3.3.4.tar.gz: not in gzip format
> > tar: This does not look like a tar archive
> > tar: Exiting with failure status due to previous errors
> > make: *** [package/Makefile.package.in:248:
> /home/david/github/astlinux/output/build/ne-3.3.4/.stamp_extracted] Error 2
> >
> > and...
> >
> > [0.707s] 1  david@Astlinux-dev:~/github/astlinux$ ls -la
> /home/david/github/astlinux/dl/ne-*
> > -rw-rw-r-- 1 david david 284094 Jun 15 11:21
> /home/david/github/astlinux/dl/ne-3.3.4.tar.gz
> > -rw-rw-r-- 1 david david     61 Mar 24 11:13
> /home/david/github/astlinux/dl/ne-3.3.4.tar.gz.sha1
> >
> > Anyone else seeing this?  Suggestions?
> >
> > Thanks
> > David
> > _______________________________________________
> > Astlinux-devel mailing list
> > Ast...@li...
> > https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>
>
>
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel
>

Re: [Astlinux-devel] Problems compiling nice editor

[Lonnie A. <li...@lo...>]

Hi David,

Thanks for the info.

Yes, the https://ne.di.unimi.it URL now forwards to the github site [2], not the autoconf download.

I made a commit [1] to use our  ne-3.3.4.tar.gz copy, and the next release we can use the github tag.

Thanks David!

Lonnie

[1] https://github.com/astlinux-project/astlinux/commit/fead6b59f4de4a350030615cdcf3ed92b5aa1b6c

[2]
--
$ curl -LI https://ne.di.unimi.it/
HTTP/1.1 302 Found
Date: Sun, 15 Jun 2025 17:32:55 GMT
Server: Apache/2.4.62 (Fedora Linux) OpenSSL/3.2.2 mod_jk/1.2.48
Location: http://github.com/vigna/ne/
Content-Type: text/html; charset=iso-8859-1

HTTP/1.1 301 Moved Permanently
Content-Length: 0
Location: https://github.com/vigna/ne/

HTTP/2 200  date: Sun, 15 Jun 2025 17:32:55 GMT
content-type: text/html; charset=utf-8
vary: X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame, X-Requested-With,Accept-Encoding, Accept, X-Requested-With
etag: W/"f2c215b4cca5b2f293019cf300168950"
...
--



> On Jun 15, 2025, at 10:35 AM, David Kerr <Da...@Ke...> wrote:
> 
> Trying to build astlinux today and I am getting this error...
> 
> >>> ne 3.3.4 Extracting
> gzip -d -c /home/david/github/astlinux/dl/ne-3.3.4.tar.gz | tar --strip-components=1 -C /home/david/github/astlinux/output/build/ne-3.3.4  -xf -
> 
> gzip: /home/david/github/astlinux/dl/ne-3.3.4.tar.gz: not in gzip format
> tar: This does not look like a tar archive
> tar: Exiting with failure status due to previous errors
> make: *** [package/Makefile.package.in:248: /home/david/github/astlinux/output/build/ne-3.3.4/.stamp_extracted] Error 2
> 
> and...
> 
> [0.707s] 1  david@Astlinux-dev:~/github/astlinux$ ls -la /home/david/github/astlinux/dl/ne-*
> -rw-rw-r-- 1 david david 284094 Jun 15 11:21 /home/david/github/astlinux/dl/ne-3.3.4.tar.gz
> -rw-rw-r-- 1 david david     61 Mar 24 11:13 /home/david/github/astlinux/dl/ne-3.3.4.tar.gz.sha1
> 
> Anyone else seeing this?  Suggestions?
> 
> Thanks
> David
> _______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel

[Astlinux-devel] Problems compiling nice editor

[David K. <da...@ke...>]

Trying to build astlinux today and I am getting this error...

>>> ne 3.3.4 Extracting
gzip -d -c /home/david/github/astlinux/dl/ne-3.3.4.tar.gz | tar
--strip-components=1 -C /home/david/github/astlinux/output/build/ne-3.3.4
 -xf -

gzip: /home/david/github/astlinux/dl/ne-3.3.4.tar.gz: not in gzip format
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
make: *** [package/Makefile.package.in:248:
/home/david/github/astlinux/output/build/ne-3.3.4/.stamp_extracted] Error 2

and...

[0.707s] 1  david@Astlinux-dev:~/github/astlinux$ ls -la
/home/david/github/astlinux/dl/ne-*
-rw-rw-r-- 1 david david 284094 Jun 15 11:21
/home/david/github/astlinux/dl/ne-3.3.4.tar.gz
-rw-rw-r-- 1 david david     61 Mar 24 11:13
/home/david/github/astlinux/dl/ne-3.3.4.tar.gz.sha1

Anyone else seeing this?  Suggestions?

Thanks
David