root/current/website/trunk/english/index.wml

#use wml::emdebian::mainpage title="The Universal Embedded Operating System"
#use wml::emdebian::recent_list
# #include "$(ENGLISHDIR)/releases/info"

<h1>emdebian.org - home of the Embedded Debian Project</h1>

<hr />

<p>Welcome to Emdebian.org. The Embedded Debian Project is making Debian 
GNU/Linux a mainstream choice for embedded projects.</p>

<p>Debian's multiarchitecture support, vendor independence, social
contract and huge software base make it an attractive choice for all
sorts of systems, but the main distribution is very much aimed at systems
with at least desktop resources (big hard discs, plenty of memory).
Embedded Debian tries to strip Debian down to be a much smaller system
whilst keeping all the good things.</p>

<h2>Getting started with Emdebian</h2>

<h3>Why use Emdebian rather than Debian?</h3>
<p>The most obvious reason is installation sizes. Debian simply cannot fit
onto some devices that could run GNU/Linux. Other machines can accommodate
a typical Debian installation but would have little available space for
user data etc. and adding more storage is impossible or impractical. See
more on the <a href="emdebian/flavours.html">available flavours of Emdebian</a>.
Generally, if the machine can be easily extended with an extra internal
hard drive or by replacing the existing hard drive with a larger one, there
is no particular reason to look at Emdebian for that machine. Embedded devices
typically have no such way of adding more storage, at least not internally.
</p>

<h3>What about low resource machines?</h3>
<p>Emdebian is based on Debian and therefore uses Debian packages. Some
Emdebian installations can make lower demands on the machine hardware
but this would be because the Emdebian installation is based on packages
already in Debian that are intended for such purposes. Using the same
packages with a Debian installation is likely to be little different to
the same packages with an Emdebian installation. Therefore, an old PC with
a reasonably large hard drive (or a capacity to use a modern multi-gigabyte
hard drive) is not likely to benefit from Emdebian. However, a low resource
embedded device without the capacity for adding more internal storage
<b>would</b> benefit greatly from an Emdebian installation. If there are
other packages that would suit low resource machines, Emdebian developers
are often willing to assist in getting the packages into Debian and thereby,
Emdebian.
</p>

<p>See the <a href="docs.html">documentation</a> for more information.</p>

<h2>What does Emdebian provide?</h2>

<ul>
<li><p><a href="crosstools.html">Toolchains</a></p>
<p>Prebuilt toolchains to build for arm, ia64, m68k, mips, mipsel,
powerpc and sparc using gcc-3.3, gcc-3.4, gcc-4.0, gcc-4.1 and gcc-4.2.
Packages are also available for  gcc-4.1 and gcc-4.2 to build arm on
powerpc.</p>
</li>
<li><p><a href="packages/index.html">Smaller packages</a></p>
<ul><li>
<h4><a href="packages/">Emdebian Crush</a> - the smallest Emdebian installations</h4>
<p>Busybox based root filesystem and packages to support the G Palmtop
Environment based on GTK+2 or any workable package selection in-between.
Kernels and kernel modules are not provided directly but support exists
to add custom kernels to the installation tarballs. 
<b>Packages are heavily modified</b> and cross-built - functional
changes exist between Emdebian Crush and standard Debian. Emdebian 
Crush 1.0 (based on Debian 5.0 &quot;Lenny&quot;) will only be available
for ARM - adding more architectures in non-trivial. Subsequent releases
will migrate to armel instead of ARM and include i386, mips and mipsel.
Powerpc support can be considered, if there is sufficient interest.</p>
<p>Installations of Emdebian Crush require significant user involvement,
images will not generally be available for direct download. Instead,
each installation is customised from the available package set using the
scripts in the <tt>emdebian-rootfs</tt> package and possibly a few
custom packages cross-built using scripts in the <tt>emdebian-tools</tt>
package.</p></li>
<li><p><a href="emdebian/rootfs.html">Root filesystem for ARM</a> - based
on busybox and removing "Essential" Debian packages like perl.</p>
</li><li>
<h4><a href="grip/">Emdebian Grip</a> - an intermediate installation</h4>
<p>Complete repositories of packages for various architectures, based on
coreutils and perl. Support for standard Debian tools like debootstrap
and debian-installer. Few (if any) functional changes compared to Debian.
Support is expected for i386, amd64, powerpc, arm, armel, mips and mipsel.
</p>
<p>Installations of Emdebian Grip will work with standard Debian tools
like debootstrap, debian-installer and maybe debian-live - as long as
the device has enough space to generate such systems.</p>
<p>(The delays to Debian Lenny mean that Emdebian is looking at whether
it is possible to release Emdebian Grip alongside Lenny.)</p>
</li>
</ul></li>
<ul>
<li><p><a href="tools.html">Cross building tools</a></p>
<p>Debian packages continually updated for cross-building using the
Emdebian toolchains. Include support for installing toolchains, patching
Debian source packages, cross building binary packages and generating
the root filesystem from a repository of binary packages.</p>
</li></ul>
</li>
</ul>

<p>Embedded Debian is currently very much a work-in-progress: plenty of
people are already using Debian in their devices and systems, but there
is huge potential to make doing this easier. We already have tools,
toolchains and a root  filesystem, but more work is needed to have full
distributions ready to build or download. Anyone with an interest in
this area is very welcome to <a href="help.html">help</a>.</p>

<hr />

<h2>News</h2>

<p><:= get_recent_list('News/$(CUR_YEAR)', '6', '$(ENGLISHDIR)', '', '\d+\w*' ) :></p>

<p>For older news items see the <a href="$(HOME)/News/">News Page</a>.
The best way to keep up-to-date is to subscribe to the <a
href="support.html#mailinglist">debian-embedded mailing list</a>.</p>