[App_rpt-users] Arch Linux version of allstar has been stable for 2 weeks now....

[Anthony Percy]

Hi Tim,
As you can see I bascially put everything that I had on the git hub!!!
Arch Linux can be tricky as its in a constant state of flux. I have assumed
a certain level of developer understanding but will produce a live cd when
I get some time.

Before you compile, make sure you do a pacman -Syy followed by pacman -Su
when its finished.
Check by rebooting with no errors..
The allstar compile process I roughly follow from memory is ;
I can document this properly if required...

1. Load the dependencies via the pacman -S. I have updated the github
README with the ones I use.. They may be some extras in there as well...:-)
2. First Install the ztdummy kernel driver. Go to the <your
root>/allstar/ast-1.4.23-pre/trunk/zaptel dir in the asterisk dir and run
configure. Then run make and make install. If you get complaints about the
kernel source not being avaiable make sure you  "pacmaned" the kernel
headers.. and done the pacman -Syy and -Su process
3. Reboot and do modprobe ztdummy. Check for zaptel /dev/zap devices.. If
not there look for zaptel.rules in udev dirs.
4. Then look in main allstar dir ( <your
root>/allstar/ast-1.4.23-pre/trunk/) readme and run make install_usbradio
.You will get errors at the end due to flash card stuff but ignore these...
5. Then you should have a compiled allstar system.
6. Check asterisk will run by running asterisk -vvvc. You will get lots of
not found errros but if it runs and stops its ok. At least it is now
compiled.
7. Add your allstar config files to the </etc/asterisk/> dir and then
restart as above...

This is what i do when I am playing around with allstar...

Regards
Anthony, VK2ACP



On Sat, Jan 19, 2013 at 11:51 PM, Tim Sawyer <tim.sawyer at mac.com> wrote:

> I'd never messed with Arch Linux so I took a look at it. Looked
> interesting so I installed it on a Parallels VM just for testing, I have no
> intention of running asterisk on a VM. It went pretty well considering the
> complexity and the unique approach from my long time favorite, Red
> Hat/Enterprise Linux/Fedora/CentOS. I build a LAMP stack just because
> that's whats I used to do for a living. I'm impressed, it's fast and lean.
>
> Anyway, to my point. I looked at your github. Looks like you duplicated a
> lot of the stuff on SVN including the RTCM firmware and programmer. So it's
> not clear to me how to approach an app_rpt install. I appreciate any
> pointers you might feel like send our way. And thanks for bringing Arch
> Linux to us.
> --
> Tim
> :wq
>
> On Jan 16, 2013, at 10:10 PM, Anthony Percy <anthcp at gmail.com> wrote:
>
> Hi all,
> Just an update, the Arch Linux version of allstar has been stable for 2
> weeks now on the repeater VK2RCZ.
> If you are happy to compile the allstar code, I have updated
> my modified version to https://github.com/anthcp/Arch-allstar.
> You may still have to fine tune the makefiles like add a symlink for the
> ar library but it does show the code changes....
> We will make a  Live CD in the future sometime....
>
> Regards
>
> Anthony, VK2ACP
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20130120/350bb813/attachment.html>