[arm-allstar] Can somebody please update the RPI update status timing

[Doug Crompton]

The web page has been updated.
73 Doug
WA3DSP
http://www.crompton.com/hamradio


From: k8it at cac.net
To: arm-allstar at hamvoip.org
Date: Wed, 30 Sep 2015 11:44:00 -0400
Subject: [arm-allstar] Can somebody please update the RPI update status	timing








I know that family commitments etc.  have delayed the release of the 
RPI updates including the tail echo buffer issue, but could somebody please 
update the current target release date? Doug's website seems to be out of date. 
THANKS
 
 
Thanks
73 Neil Sablatzky  K8IT
Allstar Node 41838 
KITLINK
Allstar Node 42087 KITLINK HUB
IRLP Node exp0068
Echolink 
K8IT-L
WIRES-X K8IT 11479 Room 21479




From: Doug Crompton 
Sent: Thursday, September 10, 2015 1:56 PM
To: ARM Allstar 
Subject: Re: [arm-allstar] fsck on PI image


Bernie,

 There are a number of ways to 
shutdown the Pi. Already in the code is the ability to shutdown with a GPIO push 
button. You just have to add the button and activate it in the allstar.env file. 
A howto is on the web page.

There are also functions in rpt.conf that are 
commented out that allow dtmf asterisk restart, linux reboot, and system halt. 
You could uncomment them and possibly change the dtmf codes.

As far a 
power down problems without shutting down properly I have never seen a problem 
with the RPi2 image but of course it is always a good idea to shutdown properly. 
It does not take much to run the RPI2 for hours of power failure. A 400 watt UPS 
would run it all day.

The image is ext4 and does the same things it would 
do on any other OS.

https://wiki.archlinux.org/index.php/Fsck

I don't think 
it is anything you have to really worry about as long as you take a few 
precautions and of course always have an image backup on hand. They are easy to 
make with the backup scripts.

73 Doug
WA3DSP
http://www.crompton.com/hamradio



> From: bmcintosh at paceprofessional.co.uk
> To: 
arm-allstar at hamvoip.org
> Date: Thu, 10 Sep 2015 17:13:53 +0100
> 
Subject: [arm-allstar] fsck on PI image
> 
> 
> Hi,
> 

> I recently put together a remote base using Baofeng UV5R and Doug's 
PI
> image. One of the problems that I have had with using Pis in a 
shared
> environment is folk switching them off without shutting them down 
properly.
> I normally rig up a push switch that makes the PI do a clean 
shutdown for
> you when you don't have a terminal handy to do it via 
SSH.
> (http://www.feednet.org.uk/powerdownpi.htm )
> 
> I 
also usually enable non-interactive use of fsck on reboot to cope with
> 
those cases where a clean shutdown hasn't been made. This is to avoid 
those
> circumtances where the machine won't allow you to go further 
without logging
> in as root, but you can't login as root because SSH 
hasn't started yet. 
> 
> I'm not familiar with Arch Linux - can 
someone advise how to ensure that if
> the OS runs fsck on a reboot, that 
it completes without any intervention ?
> Or perhaps this is already done 
with Doug's image ?
> 
> Thanks !
> 
> Bernie
> 
GM4WZG
> 
> 
> 
_______________________________________________
> 
> arm-allstar 
mailing list
> arm-allstar at hamvoip.org
> 
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> 
> 
Visit the BBB and RPi2 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 web page - http://hamvoip.org 






No virus found in this 
message.
Checked by AVG - www.avg.com
Version: 2015.0.6125 / Virus 
Database: 4409/10609 - Release Date: 09/09/15

_______________________________________________

arm-allstar mailing list
arm-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar

Visit the BBB and RPi2 web page - http://hamvoip.org 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150930/bc3b8c09/attachment.html>