[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[no subject]



You can do what others do.  Have an internal battery that will provide
enough power to shut down the device.

> Thanks.
> ----- Original Message -----
> From: "Christopher Fowler" <cfowler at outpostsentinel.com>
> To: "Atlanta Linux Enthusiasts" <ale at ale.org>
> Sent: Monday, July 11, 2005 5:05 PM
> Subject: Re: [ale] Best FS to use when doing unclean shutdowns?
> 
> 
> > On Mon, 2005-07-11 at 17:00 -0400, James P. Kinney III wrote:
> > > Ah, HA! A basic dumb kiosk box.
> > >
> > > Make the basic boot section RO (/, /boot, /bin, /sbin). Make the
> /var
> > > a
> > > skeleton that gets populated by a rc.local script.
> > >
> > > Put the data collection part on a separate partition. Change the
> boot
> > > scripts so it is NOT automatically loaded. Force a file-system auto-
> > > repair check on every boot before mounting. Use EXT3 (easy to
> install
> > > from RedHat and derivatives) or ReiserFS (Mandrake and SUSE) (Debian
> > > and
> > > Slackware come with both). Use hdparm to setup no write buffering on
> > > the
> > > partition. Use a cron job that runs every minute to perform a "sync"
> > > to
> > > keep everything flushed.
> > >
> > > Use a second cron job to keep a mirror of the "live" partition as a
> > > backup. In the event the fsck fails for any reason, use the backup
> > > partition to overwrite it with.
> > >
> > > Rewire the power switch to only perform a soft-off, controlled power
> > > down and reset.
> > >
> >
> > I like this idea.  You can also reformat the FS storage if it gets
> > beyond repair.  It all depends on how valuable the data is.  If the
> > reason for HDD is because there is so much data but losing it is not a
> > problem then you could reformat on failure to clean and mount.
> 
> 
> 
> Visit us at the 28th Annual BAI Retail Delivery Conference & Expo, November 15-18, 2005 - Orlando FL!
> 
> 
> This email and any files transmitted with it are solely intended for the use of the
> addressee(s) and may contain information that is confidential and privileged. If 
> you receive this email in error, please advise us by return email immediately. 
> Please also disregard the contents of the email, delete it and destroy any copies 
> immediately. 
> 
> _______________________________________________
> Ale mailing list
> Ale at ale.org
&gt; <a  rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale";>http://www.ale.org/mailman/listinfo/ale</a>



</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<ul><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><a name="00178" href="msg00178.html">[ale] Best FS to use when doing unclean shutdowns?</a></strong>
<ul><li><em>From:</em> dragon at atlantacon.org (Dustin Schwacke)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00169" href="msg00169.html">[ale] Best FS to use when doing unclean shutdowns?</a></strong>
<ul><li><em>From:</em> CMorlan at filink.com (Claudia Morlan)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00173.html">[ale] Best FS to use when doing unclean shutdowns?</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00175.html">[ale] Best FS to use when doing unclean shutdowns?</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00169.html">[ale] Best FS to use when doing unclean shutdowns?</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00178.html">[ale] Best FS to use when doing unclean shutdowns?</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00174"><strong>Date</strong></a></li>
<li><a href="threads.html#00174"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>