From: Kfir Lavi <lavi.kfir@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] Some good words for Gentoo embedded?
Date: Thu, 23 Dec 2010 10:34:25 +0200 [thread overview]
Message-ID: <AANLkTik=qhWdXkhEyjO+24JMw8rM2CN0wBow9=3ms2JX@mail.gmail.com> (raw)
In-Reply-To: <20101221162012.27392.qmail@stuge.se>
[-- Attachment #1: Type: text/plain, Size: 2428 bytes --]
On Tue, Dec 21, 2010 at 6:20 PM, Peter Stuge <peter@stuge.se> wrote:
> Ed W wrote:
> >> "Why Gentoo?"
> >
> > I like gentoo for situations where:
> > - Skilled developer available
> > - Customisable solution is desired
> > - Tightly controlled deployment environment
> > - Repeatable build environment required
> >
> > I think gentoo is far less acceptable if there isn't a skilled developer
> > available to help maintain and develop it... Probably that's my main
> > suggestion on how to size your project?
> >
> > However, if that developer/administrator is available, then Gentoo is a
> > marvellous solution for quickly building few MB custom solution, or a
> 60MB
> > virtual server base installation, or whatever other customised
> environment
> > you desire?
>
> This is very perceptive, and excellent advice!
>
> I believe firmly in "owning the problem" and for that, Gentoo is a
> very good fit. I know many who fiercly resist owning any problem
> whatsoever, and they do fine anyway (even better than me) and for
> them obviously Gentoo is not at all a goo fit because they would have
> to make lots of decisions they do not want to.
>
> Abstracting a little; the more requirements there are, the more
> likely it is that without Gentoo, it would be neccessary to start
> re-inventing various bits and pieces that Gentoo already offer.
>
> Sometimes requirements come only later, when a production process has
> already been established, and can not comfortably be replaced. That's
> a bad situation to be in. It will be painful no matter what, but
> often people choose the lengthy pain that means sticking with the old
> "distribution" living with a less-than-useful environment and
> reinventing tools and processes, instead of ripping off the band-aid
> and making a switch to Gentoo or something else that fits the
> project.
>
>
> //Peter
>
> Well, switching to Gentoo, is really not probable.
People don't understand Linux, and if they do, usually they know the big
distros.
If they search for embedded distro, Gentoo will not be on the list.
You need to come from Gentoo to understand it's capabilities.
If I start to roll an embedded environment with Gentoo, this will lit
some developers to check the system, because they need to use it.
It seems that when time goes by, and we grow older, we are reluctant to
do the change. Thats includes me too ;-) I have hard time letting Gentoo
off :-)
Regards,
Kfir
[-- Attachment #2: Type: text/html, Size: 3040 bytes --]
next prev parent reply other threads:[~2010-12-23 9:06 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
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 [this message]
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='AANLkTik=qhWdXkhEyjO+24JMw8rM2CN0wBow9=3ms2JX@mail.gmail.com' \
--to=lavi.kfir@gmail.com \
--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