[arm-allstar] Easier way to effect HamVoip updates?
Bryan St Clair
bryan at k6cbr.us
Wed Mar 7 14:16:09 EST 2018
Perhaps a weekly update check script to see if updates are available,
followed by an email to the node owner that an update is waiting would be a
fist step to getting people to update quicker. Even a message of 'multiple
updates' waiting to give urgency. This would be for manual updates via ssh.
Last, an option the owner has to enable for auto updates. With the warning
of the risks of power interruptions or locked processes.
Completed updates could generate and email notifying the node owner of
completion. (Manual or Automatic update) The email could be an option
enabled feature as well.
Just ideas....
Bryan
On Mar 7, 2018 10:52, Doug Crompton via arm-allstar <arm-allstar at hamvoip.org>
wrote:
> Don,
>
> The whole idea of the updates as you know is so that one could update over
> the Internet and not have to image or re-image SD cards. We will be
> updating the static image at hamvoip.org soon and this will at least put
> new users close to the latest updates.
>
> Dave and I have had this discussion many times. It has always been and I
> think will remain our idea to not force updates but on the other hand we
> are concerned that not everyone is updating. The updating process is very
> important and will become even more important as time goes on with even
> more significant changes in the code.
>
> Yes, there could be a DTMF update but the problem with that is the feedback
> to the user. It is important when doing updates to wait for it to complete.
> It is also important that there is no power interruption during the
> process. I suppose it could be done via DTMF with a modified script and
> some voice feedback. I will talk to Dave and maybe we can come up with some
> ideas on how to make it more accessible and also still reliable.
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
>
>
>
> On Wed, Mar 7, 2018 at 1:33 PM, "Don Backstrom - AA7AU via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> >
> > Doug/David:
> >
> > As always, thank you very much for your continuing work on, and
> > support for, HamVoip and our little community!
> >
> > I notice that several of the nodes which I've helped with and/or
> > use are not necessarily being regularly updated with the latest on-line
> > updates from HamVoip.
> >
> > I think, in part, this is due to the fact that apparently one
> > needs to be either logged in with 1) a direct console session, or 2) a
> > remote SSH session -- and thereby use option #1 from your menu system to
> > effect the check/update.
> >
> > This can be problematic for some users for various reasons. There
> > is also the old "don't fix it if it ain't broke" axiom, which
> unfortunately
> > most folks don't realize does NOT APPLY here.
> >
> > Can you recommend a way to setup a script which is run from a
> > [complex?] DTMF trigger? I understand that this approach would have
> > pros/cons in theory of use, but is it possible to implement safely on a
> > technical level? How about just a check "is there an update available"
> > query with yes/no audio reply triggered by a DTMF code?
> >
> > If not (or even if so), would it be possible to run such a script
> > under the new/improved Supermon with its newly improved security?
> >
> > Making the update process more accessible to all would be a very
> > good thing, IMO.
> >
> > Thanks again,
> >
> > - Don - AA7AU
> > _______________________________________________
> >
> > arm-allstar mailing list
> > arm-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> >
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
More information about the arm-allstar
mailing list