<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:dc="https://purl.org/dc/elements/1.1/" xmlns:content="https://purl.org/rss/1.0/modules/content/" xmlns:foaf="https://xmlns.com/foaf/0.1/" xmlns:og="https://ogp.me/ns#" xmlns:rdfs="https://www.w3.org/2000/01/rdf-schema#" xmlns:schema="https://schema.org/" xmlns:sioc="https://rdfs.org/sioc/ns#" xmlns:sioct="https://rdfs.org/sioc/types#" xmlns:skos="https://www.w3.org/2004/02/skos/core#" xmlns:xsd="https://www.w3.org/2001/XMLSchema#" version="2.0" xml:base="https://www.linuxjournal.com/tag/tiny-core-linux">
  <channel>
    <title>Tiny Core Linux</title>
    <link>https://www.linuxjournal.com/tag/tiny-core-linux</link>
    <description/>
    <language>en</language>
    
    <item>
  <title>Practical Tiny Core in the Fire Service</title>
  <link>https://www.linuxjournal.com/content/practical-tiny-core-fire-service</link>
  <description>  &lt;div data-history-node-id="1338424" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-field-node-image field--type-image field--label-hidden field--item"&gt;  &lt;img src="https://www.linuxjournal.com/sites/default/files/nodeimage/story/11658f8.jpg" width="550" height="413" alt="" typeof="foaf:Image" class="img-responsive" /&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/wilfredo-crespo" lang="" about="https://www.linuxjournal.com/users/wilfredo-crespo" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Wilfredo Crespo&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;
I'm sure many of you have at least heard of Tiny Core Linux—legends
of how small it is, how little it takes it to run a system with it
and even now how it's been ported to run on Raspberry Pi. It's an esoteric
minimalist distribution. There was a very good &lt;a href="https://www.linuxjournal.com/article/11023"&gt;September 2011 write up&lt;/a&gt; about it
in &lt;em&gt;Linux Journal&lt;/em&gt; by Joey Bernard. 
&lt;/p&gt;

&lt;p&gt;
I came to Tiny Core Linux after a protracted quest
to find a good solution to a problem I've had. I am a Firefighter
and EMT with the Bushkill Fire Company in Pennsylvania. Being an
all-volunteer fire department while also being the primary service provider for
our entire coverage area poses some unique challenges. When a dispatch
comes through, fire engines and rescue apparatuses are expected to get
out the door and on the road, quick.
&lt;/p&gt;

&lt;p&gt;
Part of the logistical acrobatics that we perform every call is figuring
out who is even coming. Different personnel bring different skills,
skill levels, responsibilities and capabilities. Some are specialists in
operating particular and specialized pieces of equipment, while others
may bring specific types of know-how in techniques. Depending on the
call, officers like to know who they have arriving as they plan out the
best approach to tackle the given emergency. It's nice to know, down
right imperative to know, that your best vehicle extrication technicians
are responding to a motor vehicle accident involving two cars with a
possible entrapment.
&lt;/p&gt;

&lt;p&gt;
Technology has been at the forefront of this ongoing struggle in
emergency services to solve a plethora of problems. A few companies have
released Web apps designed for the fire service to tackle the "who's
coming" 
problem. These systems consist of a Web page that acts as a dashboard and
is displayed in the station. Each responder dials a number that registers
his or her name as responding to the call. Officers then can assess what
their man power is like and decide quickly whether they need more resources,
simply by looking up at the monitor in the station. These apps do more than
that, 
but this is the crux of what they are designed for.
&lt;/p&gt;

&lt;p&gt;
It sounds fantastic, and indeed it is an enormous help and resource. Being
the go-to IT guy at my firehouse, I had fallen in the enviable position
of making this system work for us. The trivial solution is, of course,
just to fire up Windows with IE and let the monitor sit there—in fact,
the vendor suggested this to me. I suppose when you're trying to sell
something as easy to use, that's what you do. That solution, needless
to say, was unsatisfactory. From a budgetary standpoint, I was encouraged
to keep costs down. The first decision and the easiest decision was to use
Linux. I just shaved off the cost of the Windows license.
&lt;/p&gt;

&lt;p&gt;
The initial requirements and constraints became as follows:
&lt;/p&gt;

&lt;ol&gt;&lt;li&gt;
&lt;p&gt;
Have a low-power computer to run the Web browser—the smaller the better.
&lt;/p&gt;&lt;/li&gt;&lt;/ol&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/practical-tiny-core-fire-service" hreflang="und"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Wed, 24 Sep 2014 21:14:32 +0000</pubDate>
    <dc:creator>Wilfredo Crespo</dc:creator>
    <guid isPermaLink="false">1338424 at https://www.linuxjournal.com</guid>
    </item>

  </channel>
</rss>
