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

[Astlinux-devel] Announcing AstLinux Release: 1.3.0

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

Announcing AstLinux Release: 1.3.0

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

AstLinux 1.3.0 Highlights:
• Major upgrade to Linux Kernel 3.16.44, including the RUNNIX bootloader
• The default serial baud rate is now 115200 instead of the previous 19200
• New firewall "net-prefix-translation" plugin, provides NPTv6 (Network Prefix Translation) for IPv6
• Updated firewall "traffic-shaper" plugin, use fq_codel (Fair Queueing CoDel) for both 'htb' and 'hfsc' types
• New command "acme-client" to generate Let's Encrypt certificates using the ACME protocol
• Added support for VMware Tools, vmw_pvscsi and virtio-scsi disk drivers (genx86_64-vm)
• Web Interface enhancements and package upgrades providing important security and bug fixes

Full ChangeLog:
http://svn.code.sf.net/p/astlinux/code/tags/1.3.0/docs/ChangeLog.txt

All users are encouraged to upgrade.

AstLinux Team

Re: [Astlinux-devel] To github, or not to github, that is the question

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

On Aug 13, 2017, at 12:24 PM, David Kerr <Da...@Ke...> wrote:

> Devs,
>   For a while now I have been pondering whether to advocate for moving Astlinux source control from Sourceforge to Github.  The reason is the power of collaborative development brought by Github (forks, pull requests, etc.) which will make it much easier to manage updates to AstLinux.
> 
> The problem of course is that our development processes and scripts are pretty tied to SVN, and GIT is a "different way of doing things"
> 
> But I thought I would run a test and see what happens.  So this weekend I used one of the migration tools (svn2git) and copied the entire AstLinux source over to github... branches, tags, commit history and all.  And I asked Lonnie to go kick the tires.
> 
> Github supports SVN as a client, so I was then able to svn checkout Astlinux and successfully ran a clean build.  This is critical because for at least some transition period Astlinux will still assume SVN in its build environment -- but over time it is possible we could change that.
> 
> But.  And of course there is always a but.  We have run into an issue.  For some reason the revision number is out-of-sync.  So for example on Sourceforge astlinux branch 1.0 is at 8481, the exact equivalent on Github thinks it is at revision 8467.  We're not sure why.
> 
> Also, Github assumes that the current dev code base is in "master" branch.  Sourceforge equivalent is "trunk" and that is migrated cleanly.  But, another but, Astlinux on Sourceforge is using Branches/1.0 as the current dev code base and trunk is wildly out of date.  That needs to get resolved either on Sourceforge prior to importing to Github, or after importing.
> 
> Actions:
> 1) Please respond with your thoughts.  Do you see a problem if we move to GitHub?
> 2) Is there a reason "trunk" is so out-of date?  Is it okay if we merge branches/1.0 into that on Sourceforge or is it better to leave Sourceforge in the state it is (as a permanent record) and do the merge once we are on GitHub.
> 3) There are a lot of branches.  We should clean these up... delete anything not needed.  Again decision to be made as to whether to do this on Sourceforge prior to migration, or do the cleanup on Github. Please identify any branches that you think should NOT be deleted.
> 
> Feel free to take a look and kick the tires at https://github.com/dkerr64/astlinux but note that when we pull the trigger we will host it at https://github.com/astlinux-project so any changes made in my github account will get lost.
> 
> Personally I vote to do the migration. With 1.3 just tagged, now might be a good time.
> 
> Thanks
> David

I'm old and don't like change, but GitHub is a dream to work on compared to Sourceforge.  For what we do SVN is far easier to use than git, but per David's proof-of-concept the SVN wrapper around GitHub's git seems to work.  Regardless I would expect some problems, most likely fixable.  I think we figured out the revision number sync issue, seems to work after a fresh SVN commit.

I also worry about Sourceforge's future.  Though we would keep our mailing lists on Sourceforge as GitHub has no equivalent.  GitHub "Issues" are not the same.

I'm on the fence here, what we have works and any transition has pitfalls.  Darrick what do you think ?


If we did this ...
Before the transition we should remove all the old unused branches, keep 0.4 to 0.7 and rename 1.0 to trunk.

Darrick, what is your GitHub username "dhartman" I presume ?  Off-list I would need your associated GitHub account email address.

Lonnie

[Astlinux-devel] To github, or not to github, that is the question

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

Devs,
  For a while now I have been pondering whether to advocate for moving
Astlinux source control from Sourceforge to Github.  The reason is the
power of collaborative development brought by Github (forks, pull requests,
etc.) which will make it much easier to manage updates to AstLinux.

The problem of course is that our development processes and scripts are
pretty tied to SVN, and GIT is a "different way of doing things"

But I thought I would run a test and see what happens.  So this weekend I
used one of the migration tools (svn2git) and copied the entire AstLinux
source over to github... branches, tags, commit history and all.  And I
asked Lonnie to go kick the tires.

Github supports SVN as a client, so I was then able to svn checkout
Astlinux and successfully ran a clean build.  This is critical because for
at least some transition period Astlinux will still assume SVN in its build
environment -- but over time it is possible we could change that.

But.  And of course there is always a but.  We have run into an issue.  For
some reason the revision number is out-of-sync.  So for example on
Sourceforge astlinux branch 1.0 is at 8481, the exact equivalent on Github
thinks it is at revision 8467.  We're not sure why.

Also, Github assumes that the current dev code base is in "master" branch.
Sourceforge equivalent is "trunk" and that is migrated cleanly.  But,
another but, Astlinux on Sourceforge is using Branches/1.0 as the current
dev code base and trunk is wildly out of date.  That needs to get resolved
either on Sourceforge prior to importing to Github, or after importing.

Actions:
1) Please respond with your thoughts.  Do you see a problem if we move to
GitHub?
2) Is there a reason "trunk" is so out-of date?  Is it okay if we merge
branches/1.0 into that on Sourceforge or is it better to leave Sourceforge
in the state it is (as a permanent record) and do the merge once we are on
GitHub.
3) There are a lot of branches.  We should clean these up... delete
anything not needed.  Again decision to be made as to whether to do this on
Sourceforge prior to migration, or do the cleanup on Github. Please
identify any branches that you think should NOT be deleted.

Feel free to take a look and kick the tires at
https://github.com/dkerr64/astlinux but note that when we pull the trigger
we will host it at https://github.com/astlinux-project so any changes made
in my github account will get lost.

Personally I vote to do the migration. With 1.3 just tagged, now might be a
good time.

Thanks
David

[Astlinux-devel] Ready for AstLinux 1.3.0 ?

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

Hi Devs,

The AstLinux team is considering whether now (next 1-2 weeks) is the time to release AstLinux 1.3.0.

Any issues found with the pre-release versions ?

Any features we should add to 1.3.0 ?

Current AstLinux 1.3.0 ChangeLog
http://svn.code.sf.net/p/astlinux/code/branches/1.0/docs/ChangeLog.txt

Lonnie

[Astlinux-devel] arnofw r8460-8465 SVN builds

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

Hi Devs,

This note only applies to those of you who build custom images from the SVN, in particular with revision 8460 or later to 8465.

If you have built an image with revision 8460 through 8465, within your build system do the following:
--
rm dl/arno-iptables-firewall_2.0.2.tar.gz*

make arnofw-clean
make arnofw-dirclean
make arnofw
--

The upstream "arno-iptables-firewall_2.0.2.tar.gz" file changed and associated .sha1 file.

Any images created with revision 8460-8465 are functionally identical except for a few stray "dot-files" were unnecessarily included in the /usr/share/arno-iptables-firewall/ path.

Sorry for any inconvenience.

Lonnie

[Astlinux-devel] AstLinux Pre-Release: astlinux-1.0-8453

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

Announcing Pre-Release Version: astlinux-1.0-8453

Significant update with Linux 3.16 kernel, will eventually become the new AstLinux 1.3 series.

The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own.

-- acme-client, new command to generate Let's Encrypt certificates using the ACME protocol.
http://doc.astlinux-project.org/userdoc:tt_acme_certificates

-- genx86_64-vm board type
http://doc.astlinux-project.org/userdoc:guest_vm_vmware_vsphere
1) Add support for VMware Tools (open-vm-tools 10.1.5)
2) Add support for virtio-scsi as a bootable disk driver, also added to RUNNIX
3) Add support for vmw_pvscsi as a bootable disk driver, also added to RUNNIX
Note: If you want to test with the "astlinux-1.0-8453-genx86_64-vm.iso" email me privately.

-- DAHDI version bump to 2.10.2

-- DHCPv6 with Prefix Delegation
http://doc.astlinux-project.org/userdoc:tt-dhcpv6-prefix-delegation
Note: If you previously enabled DHCPv6 in the Network tab -> Connection Type, see IPv6 Autoconfig: "Assign GUA Prefix" reference.

-- IPv6 ULA / NPTv6 Configuration
http://doc.astlinux-project.org/userdoc:tt_ipv6_ula_nptv6_config

-- Traffic Shaper how uses fq_codel (Fair Queueing CoDel) for both 'htb' and 'hfsc' types.  Give 'hfsc' a try.

-- The default serial baud rate is now 115200 instead of the previous 19200.  Upgrading RUNNIX will default to 115200.

These pre-release images are for those who would like to take advantage of the AstLinux development before the next official release, as well as providing testing for the project.

The "AstLinux Pre-Release ChangeLog" and "Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ...

AstLinux Project -> Development
http://www.astlinux-project.org/dev.html

While these images are considered 'stable', the lack of testing will not make these images suitable for critical production systems.

If you should come across an issue, please report back here.

AstLinux Team

[Astlinux-devel] AstLinux Pre-Release: astlinux-1.0-8413

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

Announcing Pre-Release Version: astlinux-1.0-8413

Significant update with Linux 3.16 kernel, will eventually become the new AstLinux 1.3 series.

The AstLinux Team is regularly upgrading packages containing security and bug fixes as well as adding new features of our own.

-- genx86_64-vm board type
1) Add support for VMware Tools (open-vm-tools 10.1.5)
2) Add support for virtio-scsi as a bootable disk driver, also added to RUNNIX
3) Add support for vmw_pvscsi as a bootable disk driver, also added to RUNNIX
Note: If you want to test with the "astlinux-1.0-8413-genx86_64-vm.iso" email me privately.

-- DAHDI version bump to 2.10.2

-- Asterisk 13.16.0 missing ari.conf crash has been patched and fixed. (Noted by David Kerr with previous pre-release)

-- DHCPv6 with Prefix Delegation
http://doc.astlinux-project.org/userdoc:tt-dhcpv6-prefix-delegation
Note: If you previously enabled DHCPv6 in the Network tab -> Connection Type, see IPv6 Autoconfig: "Assign GUA Prefix" reference.

-- IPv6 ULA / NPTv6 Configuration
http://doc.astlinux-project.org/userdoc:tt_ipv6_ula_nptv6_config

-- Traffic Shaper how uses fq_codel (Fair Queueing CoDel) for both 'htb' and 'hfsc' types.  Give 'hfsc' a try.

-- The default serial baud rate is now 115200 instead of the previous 19200.  Upgrading RUNNIX will default to 115200.

These pre-release images are for those who would like to take advantage of the AstLinux development before the next official release, as well as providing testing for the project.

The "AstLinux Pre-Release ChangeLog" and "Repository URL" entries can be found under the "Development" tab of the AstLinux Project web site ...

AstLinux Project -> Development
http://www.astlinux-project.org/dev.html

While these images are considered 'stable', the lack of testing will not make these images suitable for critical production systems.

If you should come across an issue, please report back here.

AstLinux Team

Re: [Astlinux-devel] Dahdi driver 2.8.0.x on 3.16 kernel, issues?

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

On Jun 18, 2017, at 5:48 PM, Luigi Porto <ope...@gm...> wrote:
> 2017-06-18 22:22 GMT+02:00 Lonnie Abelbeck <li...@lo...>:
> 
> Luigi, let us know if the patch solves your issue.
> 
> Possibly with the kernel bump to 3.16 we should bump DAHDI linux/tools to 2.10.2, which includes that patch.
> 
> Lonnie
> 
> 
> Hello Lonnie, 
> 
> Thank you for the reply, yes, it works.. no more warn messages
> 
> I renamed the patch in dahdi-linux-2.8-Fix-failure-to-read-write-on-kernel-3.16-v2.patch, placed in packages/dahdi-linux/
> 
> :-)

Hi Luigi,

I just committed Revision: 8401
--
dahdi-linux version bump to 2.10.2, dahdi-tools version bump to 2.10.2.  Also mount /dev/shm on tmpfs so the dahdi_cfg command works
--
This includes your "dahdi-linux-2.8-Fix-failure-to-read-write-on-kernel-3.16-v2.patch" natively.

You need to do a clean build ...
--
## start clean
rm -rf output/

svn up

## Remove your patch
rm package/dahdi-linux/dahdi-linux-2.8-Fix-failure-to-read-write-on-kernel-3.16-v2.patch

## build
./scripts/build
--

I hope you have time to test this, any feedback is much appreciated.

Thanks Luigi !

Lonnie

Re: [Astlinux-devel] Dahdi driver 2.8.0.x on 3.16 kernel, issues?

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

On Jun 18, 2017, at 5:48 PM, Luigi Porto <ope...@gm...> wrote:

> 
> 
> 2017-06-18 22:22 GMT+02:00 Lonnie Abelbeck <li...@lo...>:
> 
> Luigi, let us know if the patch solves your issue.
> 
> Possibly with the kernel bump to 3.16 we should bump DAHDI linux/tools to 2.10.2, which includes that patch.
> 
> Lonnie
> 
> 
> Hello Lonnie, 
> 
> Thank you for the reply, yes, it works.. no more warn messages
> 
> I renamed the patch in dahdi-linux-2.8-Fix-failure-to-read-write-on-kernel-3.16-v2.patch, placed in packages/dahdi-linux/
> 
> :-)

OK thanks.  Also I've been working on a version bump to DAHDI 2.10.2, it builds but needs more testing.

When you see a commit to DAHDI 2.10.2 you can "svn up" and remove your patch and that should also work.

Lonnie

Re: [Astlinux-devel] Dahdi driver 2.8.0.x on 3.16 kernel, issues?

[Luigi P. <ope...@gm...>]

2017-06-18 22:22 GMT+02:00 Lonnie Abelbeck <li...@lo...>:

>
> Luigi, let us know if the patch solves your issue.
>
> Possibly with the kernel bump to 3.16 we should bump DAHDI linux/tools to
> 2.10.2, which includes that patch.
>
> Lonnie
>
>
Hello Lonnie,

Thank you for the reply, yes, it works.. no more warn messages

I renamed the patch in
dahdi-linux-2.8-Fix-failure-to-read-write-on-kernel-3.16-v2.patch, placed
in packages/dahdi-linux/

:-)

-- 
#musk from calabria.ninux.org - CS

@openmusk

Re: [Astlinux-devel] Dahdi driver 2.8.0.x on 3.16 kernel, issues?

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

On Jun 18, 2017, at 2:20 PM, Luigi Porto <ope...@gm...> wrote:

> Hello,
> 
> I have an Alix + Openvox A400M (1FXS1FXO), after compiling my Astlinux version I noticed that when I enable Dahdi drivers there is a flood of:
> 
> Jun 18 19:09:31 pbx local0.warn asterisk[422]: WARNING[520]: chan_dahdi.c:11653
> in do_monitor: Read failed with -1: Invalid argument
> 
> in /var/log/messages and asterisk -rvvvvv
> 
> 
> This behavior is very similar to: 
> 
> https://issues.asterisk.org/jira/browse/DAHLIN-340
> 
> I'm currently trying to recompile with the patch..


Luigi, let us know if the patch solves your issue.

Possibly with the kernel bump to 3.16 we should bump DAHDI linux/tools to 2.10.2, which includes that patch.

Lonnie

[Astlinux-devel] Dahdi driver 2.8.0.x on 3.16 kernel, issues?

[Luigi P. <ope...@gm...>]

Hello,

I have an Alix + Openvox A400M (1FXS1FXO), after compiling my Astlinux
version I noticed that when I enable Dahdi drivers there is a flood of:

Jun 18 19:09:31 pbx local0.warn asterisk[422]: WARNING[520]:
> chan_dahdi.c:11653
> in do_monitor: Read failed with -1: Invalid argument
>

in /var/log/messages and asterisk -rvvvvv


This behavior is very similar to:

https://issues.asterisk.org/jira/browse/DAHLIN-340

I'm currently trying to recompile with the patch..

-- 
#musk from calabria.ninux.org - CS

@openmusk

Re: [Astlinux-devel] Custom build for ALIX in r8400

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

On Jun 17, 2017, at 1:06 PM, Luigi Porto <ope...@gm...> wrote:

> 
> 
> 2017-06-17 18:20 GMT+02:00 Lonnie Abelbeck <li...@lo...>:
> 
> Alternatively, since you are building your own images, without needing to do a clean rebuild ...
> --
> make runnix-clean
> make runnix-dirclean
> --
> 
> Then in the file "boot/runnix/runnix.mk" change:
> --
> RUNNIX_VERSION = 0.5-8385
> -- to --
> RUNNIX_VERSION = 0.4-8057
> --
> 
> --
> make runnix
> ./scripts/build alix
> ./scripts/astlinux-makeimage -z 256 256 0
> --
> 
> You should now have a .img.gz with runnix-0.4-8057 .
> 
> 
> I can confirm, it works!
> 
> Thank you so much
> Luigi Porto

Excellent, thanks for reporting.

Lonnie

Re: [Astlinux-devel] Custom build for ALIX in r8400

[Luigi P. <ope...@gm...>]

2017-06-17 18:20 GMT+02:00 Lonnie Abelbeck <li...@lo...>:

>
> Alternatively, since you are building your own images, without needing to
> do a clean rebuild ...
> --
> make runnix-clean
> make runnix-dirclean
> --
>
> Then in the file "boot/runnix/runnix.mk" change:
> --
> RUNNIX_VERSION = 0.5-8385
> -- to --
> RUNNIX_VERSION = 0.4-8057
> --
>
> --
> make runnix
> ./scripts/build alix
> ./scripts/astlinux-makeimage -z 256 256 0
> --
>
> You should now have a .img.gz with runnix-0.4-8057 .
>
>
I can confirm, it works!

Thank you so much
Luigi Porto

-- 
#musk from calabria.ninux.org - CS

@openmusk

Re: [Astlinux-devel] Custom build for ALIX in r8400

[Luigi P. <ope...@gm...>]

2017-06-17 18:20 GMT+02:00 Lonnie Abelbeck <li...@lo...>:

> Hi Luigi,
>
> Using the latest SVN, the "project/astlinux/geni586/linux-smp.config" has
> a non-PAE kernel.  RUNNIX 0.4 has a non-PAE kernel.
>
> Though the new 0.5 RUNNIX has a PAE kernel, and that is the problem you
> are seeing since you created a .img image containing the RUNNIX 0.5
> bootloader.
>
> My best advice is to start with 1.2.10 and use the .img for initial
> installs (extract from the .iso if you need) then upgrade the ".run" image
> (via upgrade-run-image or System tab) using your latest SVN build.
>
> BTW, I have a net5501 running the latest SVN just fine.
>
> Alternatively, since you are building your own images, without needing to
> do a clean rebuild ...
> --
> make runnix-clean
> make runnix-dirclean
> --
>
> Then in the file "boot/runnix/runnix.mk" change:
> --
> RUNNIX_VERSION = 0.5-8385
> -- to --
> RUNNIX_VERSION = 0.4-8057
> --
>
> --
> make runnix
> ./scripts/build alix
> ./scripts/astlinux-makeimage -z 256 256 0
> --
>
> You should now have a .img.gz with runnix-0.4-8057 .
>
> Let me know how it goes.
>
> Lonnie
>
>
> On Jun 17, 2017, at 10:50 AM, Luigi Porto <ope...@gm...> wrote:
>
> > Hello,
> >
> > Reading the last changelog I've noticed:
> >
> > "net5501" and "alix" board types have reached end-of-life. AstLinux
> 1.2.10 was the last supported version.
> > A custom build can still be used to generate 'run' images for "net5501"
> and "alix" board types.
> >
> >
> > So I tried to build for my Alix following what is written in:
> > https://doc.astlinux-project.org/devdoc:documentation > Paragraph
> "custom build"
> >
> > Apparently everything ok. I flash my CF but at the first boot I read via
> serial:
> >
> > boot:
> > Loading runnix...............................................
> > Loading runnix.img...............................................ready.
> > This kernel requires the following features not present on the CPU:
> > pae
> > Unable to boot - please use a kernel appropriate for your CPU.
> >
> > Reading in devdoc:documentation :
> > Of special note, there are three kernel configurations supported.
> >
> > For 32-bit non-SMP kernel builds: (boards with i586 single-core
> processors)
> >
> > project/astlinux/geni586/linux.config
> > For 32-bit SMP kernel builds: (boards with i586 multi-core processors)
> >
> > project/astlinux/geni586/linux-smp.config
> > For 64-bit SMP kernel builds: (boards with x86_64 multi-core processors)
> >
> > project/astlinux/genx86_64/linux-smp.config
> >
> > linux.config (1st kernel conf) is missed in astlinux/geni586/.. How can
> i build NON-PAE for my Alix?
> >
> > Thanks for your time
> >
> > Kind regards,
> > Luigi Porto
> > --
> > #musk from calabria.ninux.org - CS
> >
> > @openmusk
>
>
Oh, perfect! Thank you Lonnie!
I'll test both methods and release feedbacks :-)

-- 
#musk from calabria.ninux.org - CS

@openmusk

Re: [Astlinux-devel] Custom build for ALIX in r8400

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

Hi Luigi,

Using the latest SVN, the "project/astlinux/geni586/linux-smp.config" has a non-PAE kernel.  RUNNIX 0.4 has a non-PAE kernel.

Though the new 0.5 RUNNIX has a PAE kernel, and that is the problem you are seeing since you created a .img image containing the RUNNIX 0.5 bootloader.

My best advice is to start with 1.2.10 and use the .img for initial installs (extract from the .iso if you need) then upgrade the ".run" image (via upgrade-run-image or System tab) using your latest SVN build.

BTW, I have a net5501 running the latest SVN just fine.

Alternatively, since you are building your own images, without needing to do a clean rebuild ...
--
make runnix-clean
make runnix-dirclean
--

Then in the file "boot/runnix/runnix.mk" change:
--
RUNNIX_VERSION = 0.5-8385
-- to --
RUNNIX_VERSION = 0.4-8057
--

--
make runnix
./scripts/build alix
./scripts/astlinux-makeimage -z 256 256 0
--

You should now have a .img.gz with runnix-0.4-8057 .

Let me know how it goes.

Lonnie 


On Jun 17, 2017, at 10:50 AM, Luigi Porto <ope...@gm...> wrote:

> Hello,
> 
> Reading the last changelog I've noticed:
> 
> "net5501" and "alix" board types have reached end-of-life. AstLinux 1.2.10 was the last supported version.
> A custom build can still be used to generate 'run' images for "net5501" and "alix" board types.
> 
> 
> So I tried to build for my Alix following what is written in:
> https://doc.astlinux-project.org/devdoc:documentation > Paragraph "custom build"
> 
> Apparently everything ok. I flash my CF but at the first boot I read via serial:
> 
> boot:
> Loading runnix...............................................
> Loading runnix.img...............................................ready.
> This kernel requires the following features not present on the CPU:
> pae
> Unable to boot - please use a kernel appropriate for your CPU.
> 
> Reading in devdoc:documentation :
> Of special note, there are three kernel configurations supported.
> 
> For 32-bit non-SMP kernel builds: (boards with i586 single-core processors)
> 
> project/astlinux/geni586/linux.config
> For 32-bit SMP kernel builds: (boards with i586 multi-core processors)
> 
> project/astlinux/geni586/linux-smp.config
> For 64-bit SMP kernel builds: (boards with x86_64 multi-core processors)
> 
> project/astlinux/genx86_64/linux-smp.config
> 
> linux.config (1st kernel conf) is missed in astlinux/geni586/.. How can i build NON-PAE for my Alix?
> 
> Thanks for your time
> 
> Kind regards,
> Luigi Porto
> -- 
> #musk from calabria.ninux.org - CS
> 
> @openmusk
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel

[Astlinux-devel] Custom build for ALIX in r8400

[Luigi P. <ope...@gm...>]

Hello,

Reading the last changelog I've noticed:

"net5501" and "alix" board types have reached end-of-life. AstLinux 1.2.10
was the last supported version.
A custom build can still be used to generate 'run' images for "net5501" and
"alix" board types.



So I tried to build for my Alix following what is written in:
https://doc.astlinux-project.org/devdoc:documentation > Paragraph "custom
build"

Apparently everything ok. I flash my CF but at the first boot I read via
serial:

boot:
> Loading runnix...............................................
> Loading runnix.img...............................................ready.
> This kernel requires the following features not present on the CPU:
> pae
> Unable to boot - please use a kernel appropriate for your CPU.
>

Reading in devdoc:documentation :

> Of special note, there are three kernel configurations supported.
>
> For 32-bit non-SMP kernel builds: (boards with i586 single-core
> processors)
>
> project/astlinux/geni586/linux.config
>
> For 32-bit SMP kernel builds: (boards with i586 multi-core processors)
>
> project/astlinux/geni586/linux-smp.config
>
> For 64-bit SMP kernel builds: (boards with x86_64 multi-core processors)
>
project/astlinux/genx86_64/linux-smp.config


linux.config (1st kernel conf) is missed in astlinux/geni586/.. How
can i build NON-PAE for my Alix?

Thanks for your time

Kind regards,
Luigi Porto

-- 
#musk from calabria.ninux.org - CS

@openmusk

Re: [Astlinux-devel] Custom MoH

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

Thanks Lonnie. I will add one.

No same here and I only add royalty free or customer created media.

Regards
Michael Knill

-----Original Message-----
From: Lonnie Abelbeck <li...@lo...>
Reply-To: AstLinux Developers Mailing List <ast...@li...>
Date: Tuesday, 13 June 2017 at 7:39 am
To: AstLinux Developers Mailing List <ast...@li...>
Subject: Re: [Astlinux-devel] Custom MoH

Hi Michael,

No, there is no "custom-moh" standard directory.

Here in the US, "music" lawyers are always trolling for copyright infringement, including MoH services.  So I would be careful using anything other than the standard Digium provided MoH, unless you created the music :-)

Possibly Australia is better in this regard.

Lonnie


On Jun 12, 2017, at 4:23 PM, Michael Knill <mic...@ip...> wrote:

> Hi devs
>  
> Just wondering if there are any /mnt/kd directories for custom MoH. I know there is a custom-sounds so this is why I am asking.
> Its easy to point to a separate directory but it would be good to know what is available.
>  
> Regards
> Michael Knill
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Astlinux-devel mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-devel

Re: [Astlinux-devel] Custom MoH

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

Hi Michael,

No, there is no "custom-moh" standard directory.

Here in the US, "music" lawyers are always trolling for copyright infringement, including MoH services.  So I would be careful using anything other than the standard Digium provided MoH, unless you created the music :-)

Possibly Australia is better in this regard.

Lonnie


On Jun 12, 2017, at 4:23 PM, Michael Knill <mic...@ip...> wrote:

> Hi devs
>  
> Just wondering if there are any /mnt/kd directories for custom MoH. I know there is a custom-sounds so this is why I am asking.
> Its easy to point to a separate directory but it would be good to know what is available.
>  
> Regards
> Michael Knill
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
> Astlinux-devel mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-devel

[Astlinux-devel] Custom MoH

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

Hi devs

Just wondering if there are any /mnt/kd directories for custom MoH. I know there is a custom-sounds so this is why I am asking.
Its easy to point to a separate directory but it would be good to know what is available.

Regards
Michael Knill

Re: [Astlinux-devel] Astlinux Asterisk SIP Monitor

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

Ah cool Lonnie thanks that's better than rebooting the system.

Regards
Michael Knill

-----Original Message-----
From: Lonnie Abelbeck <li...@lo...>
Reply-To: AstLinux Developers Mailing List <ast...@li...>
Date: Saturday, 10 June 2017 at 9:24 pm
To: AstLinux Developers Mailing List <ast...@li...>
Subject: Re: [Astlinux-devel] Astlinux Asterisk SIP Monitor

Michael,

"Restart Asterisk" will also restart asterisk-sip-monitor-ctrl, but I understand what you are asking.

Lonnie


On Jun 10, 2017, at 12:16 AM, Michael Knill <mic...@ip...> wrote:

> Feature request:
>  
> ‘asterisk-sip-monitor-ctrl restart’ from network tab Reboot/Restart dropdown for when I set up a new trunk or peer that I want to monitor.
>  
> Regards
> Michael Knill
>  
> From: Michael Knill <mic...@ip...>
> Reply-To: AstLinux Developers Mailing List <ast...@li...>
> Date: Saturday, 10 June 2017 at 10:29 am
> To: AstLinux Developers Mailing List <ast...@li...>
> Subject: Re: [Astlinux-devel] Astlinux Asterisk SIP Monitor
>  
> Ok sorry I should have put more effort into looking. I found the script.
>  
> Regards
> Michael Knill
>  
> From: IPC Solutions Accounts <acc...@ip...>
> Date: Saturday, 10 June 2017 at 10:21 am
> To: AstLinux Developers Mailing List <ast...@li...>
> Subject: Astlinux Asterisk SIP Monitor
>  
> Hi devs
>  
> Sorry for my ignorance but I would like to know how the Asterisk SIP Monitor works.
> Is it possible to add monitored trunks without having to reboot?
> How hard would it be to write a script that looked at all the SIP Trunks configured and added them to the SIP monitor?
> Should I just use Monit?
>  
> Thanks all. Sorry for the large number of emails lately. Im putting lots of time into my new release ready for a big marketing push to get lots of systems out there.
>  
> Regards
> Michael Knill


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Astlinux-devel mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-devel

[Astlinux-devel] Switching Images between genx86_64 and genx86_64-vm

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

Hi Devs,

We added a new WiKi entry to the developer's section:

Switching Images between genx86_64 and genx86_64-vm
https://doc.astlinux-project.org/devdoc:devdoc_switch_genx86_64_and_vm

"This may be particularly useful with VMware installations that were originally deployed with the bare-metal genx86_64 (Video console) image, and with new features of AstLinux 1.3 you may want to switch to the VM-centric genx86_64-vm (Video console) image."

Would there be any practical reason to switch to genx86_64-vm for VirtualBox guests ?

Lonnie

Re: [Astlinux-devel] Astlinux Asterisk SIP Monitor

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

Michael,

"Restart Asterisk" will also restart asterisk-sip-monitor-ctrl, but I understand what you are asking.

Lonnie


On Jun 10, 2017, at 12:16 AM, Michael Knill <mic...@ip...> wrote:

> Feature request:
>  
> ‘asterisk-sip-monitor-ctrl restart’ from network tab Reboot/Restart dropdown for when I set up a new trunk or peer that I want to monitor.
>  
> Regards
> Michael Knill
>  
> From: Michael Knill <mic...@ip...>
> Reply-To: AstLinux Developers Mailing List <ast...@li...>
> Date: Saturday, 10 June 2017 at 10:29 am
> To: AstLinux Developers Mailing List <ast...@li...>
> Subject: Re: [Astlinux-devel] Astlinux Asterisk SIP Monitor
>  
> Ok sorry I should have put more effort into looking. I found the script.
>  
> Regards
> Michael Knill
>  
> From: IPC Solutions Accounts <acc...@ip...>
> Date: Saturday, 10 June 2017 at 10:21 am
> To: AstLinux Developers Mailing List <ast...@li...>
> Subject: Astlinux Asterisk SIP Monitor
>  
> Hi devs
>  
> Sorry for my ignorance but I would like to know how the Asterisk SIP Monitor works.
> Is it possible to add monitored trunks without having to reboot?
> How hard would it be to write a script that looked at all the SIP Trunks configured and added them to the SIP monitor?
> Should I just use Monit?
>  
> Thanks all. Sorry for the large number of emails lately. Im putting lots of time into my new release ready for a big marketing push to get lots of systems out there.
>  
> Regards
> Michael Knill

Re: [Astlinux-devel] Astlinux Asterisk SIP Monitor

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

Feature request:

‘asterisk-sip-monitor-ctrl restart’ from network tab Reboot/Restart dropdown for when I set up a new trunk or peer that I want to monitor.

Regards
Michael Knill

From: Michael Knill <mic...@ip...>
Reply-To: AstLinux Developers Mailing List <ast...@li...>
Date: Saturday, 10 June 2017 at 10:29 am
To: AstLinux Developers Mailing List <ast...@li...>
Subject: Re: [Astlinux-devel] Astlinux Asterisk SIP Monitor

Ok sorry I should have put more effort into looking. I found the script.

Regards
Michael Knill

From: IPC Solutions Accounts <acc...@ip...>
Date: Saturday, 10 June 2017 at 10:21 am
To: AstLinux Developers Mailing List <ast...@li...>
Subject: Astlinux Asterisk SIP Monitor

Hi devs

Sorry for my ignorance but I would like to know how the Asterisk SIP Monitor works.
Is it possible to add monitored trunks without having to reboot?
How hard would it be to write a script that looked at all the SIP Trunks configured and added them to the SIP monitor?
Should I just use Monit?

Thanks all. Sorry for the large number of emails lately. Im putting lots of time into my new release ready for a big marketing push to get lots of systems out there.

Regards
Michael Knill

Re: [Astlinux-devel] Astlinux Asterisk SIP Monitor

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

Ok sorry I should have put more effort into looking. I found the script.

Regards
Michael Knill

From: IPC Solutions Accounts <acc...@ip...>
Date: Saturday, 10 June 2017 at 10:21 am
To: AstLinux Developers Mailing List <ast...@li...>
Subject: Astlinux Asterisk SIP Monitor

Hi devs

Sorry for my ignorance but I would like to know how the Asterisk SIP Monitor works.
Is it possible to add monitored trunks without having to reboot?
How hard would it be to write a script that looked at all the SIP Trunks configured and added them to the SIP monitor?
Should I just use Monit?

Thanks all. Sorry for the large number of emails lately. Im putting lots of time into my new release ready for a big marketing push to get lots of systems out there.

Regards
Michael Knill