<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><font style="" color="#000000" face="Tahoma,sans-serif">The web page has been updated.<br id="FontBreak"></font><br><b><font style="font-size:16pt;" size="4">73 Doug</font><font style="font-size:16pt;" size="4"><br></font><font style="font-size:16pt;" size="4">WA3DSP</font><font style="font-size:16pt;" size="4"><br></font><font style="font-size:16pt;" size="4">http://www.crompton.com/hamradio</font></b><font style="font-size:16pt;" size="4"><br></font><br><br><div><hr id="stopSpelling">From: k8it@cac.net<br>To: arm-allstar@hamvoip.org<br>Date: Wed, 30 Sep 2015 11:44:00 -0400<br>Subject: [arm-allstar] Can somebody please update the RPI update status timing<br><br>
<style><!--
.ExternalClass .ecxhmmessage P {
padding:0px;
}
.ExternalClass body.ecxhmmessage {
font-size:12pt;
font-family:Calibri;
}
--></style>
<div>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</div>
<div> </div>
<div> </div>
<div>Thanks<br>73 Neil Sablatzky K8IT<br>Allstar Node 41838
KITLINK<br>Allstar Node 42087 KITLINK HUB<br>IRLP Node exp0068<br>Echolink
K8IT-L<br>WIRES-X K8IT 11479 Room 21479</div>
<div style="FONT:10pt Tahoma;">
<div><br></div>
<div style="BACKGROUND:#f5f5f5;">
<div style=""><b>From:</b> <a title="mailto:doug@crompton.com CTRL + Click to follow link" href="mailto:doug@crompton.com">Doug Crompton</a> </div>
<div><b>Sent:</b> Thursday, September 10, 2015 1:56 PM</div>
<div><b>To:</b> <a title="arm-allstar@hamvoip.org" href="mailto:arm-allstar@hamvoip.org">ARM Allstar</a> </div>
<div><b>Subject:</b> Re: [arm-allstar] fsck on PI image</div></div></div>
<div><br></div>
<div dir="ltr"><font color="#000000" face="Tahoma,sans-serif">Bernie,<br><br> 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.<br><br>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.<br><br>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.<br><br>The image is ext4 and does the same things it would
do on any other OS.<br><br><a href="https://wiki.archlinux.org/index.php/Fsck" target="_blank">https://wiki.archlinux.org/index.php/Fsck</a><br><br>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.<br></font><br><b><font style="FONT-SIZE:16pt;" size="4">73 Doug</font><font style="FONT-SIZE:16pt;" size="4"><br></font><font style="FONT-SIZE:16pt;" size="4">WA3DSP</font><font style="FONT-SIZE:16pt;" size="4"><br></font><font style="FONT-SIZE:16pt;" size="4">http://www.crompton.com/hamradio</font></b><font style="FONT-SIZE:16pt;" size="4"><br></font><br><br>
<div>> From: bmcintosh@paceprofessional.co.uk<br>> To:
arm-allstar@hamvoip.org<br>> Date: Thu, 10 Sep 2015 17:13:53 +0100<br>>
Subject: [arm-allstar] fsck on PI image<br>> <br>> <br>> Hi,<br>>
<br>> I recently put together a remote base using Baofeng UV5R and Doug's
PI<br>> image. One of the problems that I have had with using Pis in a
shared<br>> environment is folk switching them off without shutting them down
properly.<br>> I normally rig up a push switch that makes the PI do a clean
shutdown for<br>> you when you don't have a terminal handy to do it via
SSH.<br>> (http://www.feednet.org.uk/powerdownpi.htm )<br>> <br>> I
also usually enable non-interactive use of fsck on reboot to cope with<br>>
those cases where a clean shutdown hasn't been made. This is to avoid
those<br>> circumtances where the machine won't allow you to go further
without logging<br>> in as root, but you can't login as root because SSH
hasn't started yet. <br>> <br>> I'm not familiar with Arch Linux - can
someone advise how to ensure that if<br>> the OS runs fsck on a reboot, that
it completes without any intervention ?<br>> Or perhaps this is already done
with Doug's image ?<br>> <br>> Thanks !<br>> <br>> Bernie<br>>
GM4WZG<br>> <br>> <br>>
_______________________________________________<br>> <br>> arm-allstar
mailing list<br>> arm-allstar@hamvoip.org<br>>
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar<br>> <br>>
Visit the BBB and RPi2 web page - http://hamvoip.org<br>> <br></div></div>
<BR><hr>
<BR>_______________________________________________<br><br>arm-allstar
mailing
list<br>arm-allstar@hamvoip.org<br>http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar<br><br>Visit
the BBB and RPi2 web page - http://hamvoip.org
<BR><hr>
<BR><a target="_blank"></a>
<p align="left">No virus found in this
message.<br>Checked by AVG - <a href="http://www.avg.com" target="_blank">www.avg.com</a><br>Version: 2015.0.6125 / Virus
Database: 4409/10609 - Release Date: 09/09/15</p>
<br>_______________________________________________
arm-allstar mailing list
arm-allstar@hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
Visit the BBB and RPi2 web page - http://hamvoip.org</div> </div></body>
</html>