From: Peter Stuge <peter@stuge.se>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] Some good words for Gentoo embedded?
Date: Thu, 9 Dec 2010 22:42:33 +0100 [thread overview]
Message-ID: <20101209214233.7164.qmail@stuge.se> (raw)
In-Reply-To: <AANLkTi=J=1rvh7PqvH-24UUY1Q6whd_amXhcFm7AZ19M@mail.gmail.com>
Kfir Lavi wrote:
> What will be the major points I need to make in order to convert
> their minds from Ubuntu to Gentoo embedded?
It depends. Maybe Ubuntu would actually be a fine choice for the
customer.
> "Why Gentoo?" for people that don't understand Linux, but are
> educated and very experienced in software.
Key words are configurability (security, size, speed benefits),
repeatability (archive all sources and the build tools to recreate
from scratch forever), being source based (easy to stay close to
upstream, noone else makes arbitrary decisions on versions, easy to
also collect all licensing information), unparalleled simplicity and
power in the packaging system (ebuilds are vamped up sh scripts) and
excellent documentation of the same (pms-3.pdf).
Some of the above are significant advantages for some customers, and
major headaches for others. I would suggest that Gentoo will require
more "positive QA" to determine that the finished system behaves as
desired, while something based on Ubuntu requires more "negative QA"
to check if the Ubuntu system still works even if stripped down.
Gentoo also requires being able to make decisions. This means having
an ear to the upstream tracks. For someone who is not interested in
this it is much more comfortable to rely on Canonical's ears to the
tracks, albeit that means giving up much choice.
This is the selling point as a consultant - if you are skilled and
experienced with the open source community, perhaps even a
contributor in one or more projects, then you have a strong case as
being an open source expert.
If that also means that you are experienced enough to appreciate the
versatility of Gentoo, and able to compare it with the Ubuntu way,
then it should be easy to motivate your preference of Gentoo.
Of course, maybe your customer does not want to become, or depend on,
an open source expert - which may still be valid - in which case I
would advise against Gentoo, but in fact also Linux at all.
If they are business people rather than software people then you
could motivate Gentoo with the fact that it allows you to accomplish
virtually any configuration and extension they would like to have in
the future very efficiently, while Ubuntu is generally restricted to
one particular way of doing things.
(And of course Ubuntu above can be replaced with any other binary
distribution.)
//Peter
next prev parent reply other threads:[~2010-12-09 22:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 20:18 [gentoo-embedded] Some good words for Gentoo embedded? Kfir Lavi
2010-12-09 21:42 ` Peter Stuge [this message]
2010-12-09 23:02 ` David Ford
2010-12-30 6:52 ` Enrico Weigelt
2010-12-30 7:17 ` Peter Stuge
2010-12-30 10:49 ` Enrico Weigelt
2010-12-21 14:58 ` Ed W
2010-12-21 16:20 ` Peter Stuge
2010-12-23 8:34 ` Kfir Lavi
2010-12-23 11:17 ` [gentoo-embedded] virtual server profile Arkadi Shishlov
2011-02-26 11:58 ` Ed W
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=20101209214233.7164.qmail@stuge.se \
--to=peter@stuge.se \
--cc=gentoo-embedded@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