[App_rpt-users] BeagleBone Black Allstar Official Release

Thu Jun 26 22:37:25 UTC 2014

Personally, I didn't see anything in Jim's email that could be
characterized as "naysaying" or negative in any way. I took it as a very
polite email simply clarifying the status of the work from an official
Allstar point of view. What I find disappointing is the negative and
disrespectful sounding reactions to Jim's email.

73's,

Keith
KF7DRV
Allstar: 2541 (currently down while relocating)

On Thu, Jun 26, 2014 at 3:03 PM, David McGough <kb4fxc at inttek.net> wrote:

>
> Hi Jim and everyone,
>
> I think Doug probably meant "officially released" since we've had several
> beta-test releases over the last 6 weeks or so.
>
> I'm unfortunately not surprised by your comments, but, am disappointed.
> As the father of the AllStar project, you should be grinning from ear to
> ear that your baby has grown to the point that other developers are
> helping to build *your* network without requiring any of your time.
>
> I, for one, hope this isn't another fork in the road. I hope it's just
> another step in the evolution of this already fantastic radio/repeater
> control and VoIP solution you envisioned.
>
> As a software developer and project manager with decades of experience,
> one thing I've had to painfully learn is that everybody has there own
> vision for how a piece of software or a system should function. You can't
> stifle this creativity. Rather, you have to embrace it and direct it. If
> the system works reliably, inter-operates (with AllStar) compatibly and is
> being (pro)actively supported, then you smile and say: Good job guys! We
> need this feature next! Or, how about finding a solution for that issue???
>
>
> This shouldn't be a competition. Lets work for a common goal.
>
>
> 73, David KB4FXC
>
>
>
>
> On Thu, 26 Jun 2014, Jim Duuuude wrote:
>
> > It has quite sadly become painfully necessary to "Officially" and
> publicly state that
> > this release is *NOT* an "Official" Allstar release. It has not been
> sanctioned by
> > me or the Allstar network. It is something that this person is doing
> completely independently.
> >
> > I am not in any way trying to infer that there is anything "right" or
> "wrong", or anything else
> > about it, merely that is in an independent operation and I/we are not in
> any way responsible
> > for its contents and/or use.
> >
> > Jim WB6NIL
> >
> >
> > From: doug at crompton.com
> > To: app_rpt-users at ohnosec.org
> > Date: Thu, 26 Jun 2014 01:02:00 -0400
> > Subject: [App_rpt-users] BeagleBone Black Allstar Official Release
> >
> >
>
>
> Hello and welcome to the first public release of Allstar on the BeagleBone
> Black. This represents months of trial and error testing which first
> started with the Raspberry Pi back at the beginning of the year and was
> finally successful on the BBB platform. We have had several beta versions
> out now for over two months with many testers and we had very good reports.
> There is more to be done but this is a working system that will allow many
> to get rid of their energy consuming PC's with constantly running hard
> drives and have an Allstar system that fits in the palm of your hand.
> >
> > The web page I have created gives very detailed instructions on how to
> download, install, and configure your BBB for use with Allstar. The web
> page is:
> >
> > hamvoip.org
> >
> > There you will find a link to download the image and also to join the
> arm-allstar email list. Please try to address questions specific to the BBB
> and Allstar to the arm-allstar list and not the apt-rpt list.
> >
> > While the code is the current Acid release there are many differences in
> how things are done on the BBB and the OS we are using, Arch Linux, is much
> different than Centos or Debian. Please refer to the web page for detailed
> info on some of the differences. We also recommend that you NOT use the
> nodesetup routine that is offered on the standard Acid release. In many
> ways this is faulty and often more trouble than it is worth. For that
> reason we have renamed nodesteup on the image and made it non-executable.
> Besides what is described on the web page there is a very detailed how-to
> describing first time setup of the config files. We encourage you to edit
> the existing config files rather than wholesale copying your existing
> configs on top of the examples. There is a little learning involved but in
> the long run it is good to know how things work by configuring the files on
> your own.
> >
> > We also encourage you to make image backups once you have your system
> configured. This will avoid having to recreate your configuration should a
> failure of some kind occur. While we have not seen any problems with power
> failures and as far as we know not one SD card has ever failed running
> Allstar there is always a first time and better safe than sorry.
> >
> > This release does not have the backup/restore scripts that we promised
> but they will be available soon. Basically what they will do is copy
> /etc/asterisk and all directories under it in entirety into a tar file and
> then you would use winscp or a similar file copy program to transfer the
> tar file to another computer. This would allow you to make updates of the
> image when new code is released in the future without losing your former
> configuration. For now you can do this manually. See the howto on the web
> page for instructions on doing image and directory backups. It is not hard
> to do and well worth the piece of mind.
> >
> > Have fun and I hope you enjoy your new BBB Allstar node. There will be
> many more features and upgrades available in the future all of which will
> be announced on the arm-allstar email list. There are already plenty of
> experienced users on the list that can help you with any problems you might
> have.
> >
> > 73 Doug, WA3DSP
> >
> >
>
> > _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>
> To unsubscribe from this list please visit
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down
> to the bottom of the page. Enter your email address and press the
> "Unsubscribe or edit options button"
> You do not need a password to unsubscribe, you can do it via email
> confirmation. If you have trouble unsubscribing, please send a message to
> the list detailing the problem.
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>
> To unsubscribe from this list please visit
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down
> to the bottom of the page. Enter your email address and press the
> "Unsubscribe or edit options button"
> You do not need a password to unsubscribe, you can do it via email
> confirmation. If you have trouble unsubscribing, please send a message to
> the list detailing the problem.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20140626/4db0119c/attachment.html>