From: Richard Freeman <rich0@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] gentoo embedded "reference accounts"?
Date: Sat, 29 May 2010 16:06:19 -0400 [thread overview]
Message-ID: <4C0173BB.4040907@gentoo.org> (raw)
In-Reply-To: <20100529105425.7a8727c3@angelstorm>
On 05/29/2010 01:54 PM, Joshua Saddler wrote:
>
> D-Link routers, for example, run (or used to run) Gentoo. SRI's solar
> probe, RAISE, ran Gentoo. The Misa Digital Guitar, just entering mass
> production, runs Gentoo. There are many more places where Gentoo's
> been used in various devices and production environments, so the PR,
> GMN, and GWN archives are your friends, as well as searching Google
> for Gentoo success stories.
When I think about pros/cons for Gentoo vs something else here are a few
thoughts (some of which you may have already had):
Linux in general isn't the only OS used in embedded apps - there are
other options like vxware/etc, which probably should be at least
considered as well. Advantages of linux in general would be familiarity
and a very wide range of features. A more purpose-driven OS might have
the advantage of better realtime support and stability, as well as
better vendor support (embedded is all that they do).
If you're going to run linux, then I'd consider Gentoo well up there -
granted I'd strip out a lot of it before deploying it. Gentoo has most
of the flexibility of linux from scratch, but is FAR more maintainable
if you plan to keep it updated. The fact that you can mix and match
just about any version of any library/etc is a big plus - it gives you
more control over what you put on your device. On the other hand, some
other distros might give you better long-term-support if you're willing
to live with the library versions they pick and how they build
everything. If your device goes on a network then it may need security
patching, and that is generally safer if you have a vendor who will
backport security fixes for 5+ years. Something like RHEL has
certifications/etc and more formal support, so you can hire people who
probably know what they're doing.
Like anything you have to consider all the pros/cons. If I were
building something on my own dime in an embedded space I'd probably
strongly consider Gentoo.
Of course, if you do use Gentoo unless you have a ton of storage you're
going to want to strip out the toolchain, portage, etc. You would use
gentoo to maintain a development image, and then any time you want to
you could copy that and then trim it way down (you could probably script
this).
Just some random thoughts.
Rich
next prev parent reply other threads:[~2010-05-29 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinZSmnIJ_eUc4yENvlDY92JWE0Q-n-gDvlcAZSV@mail.gmail.com>
2010-05-29 5:47 ` [gentoo-dev] gentoo embedded "reference accounts"? spinugio
2010-05-29 17:54 ` Joshua Saddler
2010-05-29 20:06 ` Richard Freeman [this message]
2010-05-29 20:28 ` Mike Frysinger
2010-05-29 20:58 ` Marc Arens
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C0173BB.4040907@gentoo.org \
--to=rich0@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox