From: Michiel de Bruijne <m.debruijne@hccnet.nl>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Gentoo could become certified for IBM Server Hardware
Date: Wed, 4 May 2005 18:17:53 +0200 [thread overview]
Message-ID: <200505041817.53353.m.debruijne@hccnet.nl> (raw)
In-Reply-To: <OF92174C11.03A4919D-ONC1256FF7.002EBF08-42256FF7.00314550@inside.allianz.de>
On Wednesday 04 May 2005 11:03, daniel.kerwin@allianz.de wrote:
> Hello,
>
> i just returned from a meeting with IBM which was about getting
> support for Gentoo Linux (hardware and software). The people from IBM
> told me that it's possible for Gentoo to become officially supported
> on IBM server hardware (xSeries, pSeries and zSeries).
>
> They told me about their hardware offerings to the Debian Project so
> that they could certify their distribution. I think this is a great
> chance for gentoo to become more common for productive use.
>
> Is there a general interrest in doing this and how can this start?
Interest; yes, believe that it will happen in the (forseeable) future;
absolutely not.
The biggest showstopper is that needs to be fixed first is lack of
predictability:
- Gentoo is extremely customizable (USE-flags, compiler settings, etc.). To
achieve predictability all those customizable options need to be locked.
- moving Portage-tree; if I install a system today, it wont be the same as a
system I installed one month ago.
- no standard method of installation; supported OS's are basically clicking
next, next, finish. Installation is done, system is identical. With Gentoo
you get a lot of choices for a single component (e.g. vanilla-sources vs.
gentoo-sources, vixie-cron vs. dcron, etc.). A default needs to be defined.
Second showstopper is lack of (LSB-)certification;
Like it or not, the typical managers in this world say if product x isn't
y-certified we wont use/support it. Gentoo needs a profile for a
LSB-compliant system.
There are more items that needs to be resolved before it's even possible to
talk about official support. Good news is that with the current
"Gentoo-framework" it's possible to fix both problems for example by creating
a profile, lock everything in this profile and make sure old ebuilds are not
removed during a sync. Other options are also possible (e.g. creating a
separate tree). See GLEP 19 for more details. The only problem is lack of
interest/time/priority from the developers/community.
If you want support from a company as big as IBM, you need to start smaller
(e.g. NX, MySQL, Open-Xchange). If these companies are willing to support
their products on Gentoo, then maybe bigger companies will follow.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-05-04 16:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 9:03 [gentoo-dev] Gentoo could become certified for IBM Server Hardware daniel.kerwin
2005-05-04 9:09 ` Donnie Berkholz
2005-05-04 9:17 ` Antwort: " daniel.kerwin
2005-05-04 10:21 ` José Alberto Suárez López
2005-05-04 10:37 ` [gentoo-dev] Re: Antwort: " Duncan
2005-05-04 10:15 ` [gentoo-dev] " Michael Cummings
2005-05-04 10:32 ` Fernando J. Pereda
2005-05-04 10:36 ` Antwort: " daniel.kerwin
2005-05-04 13:32 ` Omkhar Arasaratnam
2005-05-04 13:50 ` M. Edward (Ed) Borasky
2005-05-04 14:08 ` Omkhar Arasaratnam
2005-05-04 14:24 ` Michael Cummings
2005-05-04 14:18 ` Brett Curtis
2005-05-04 14:39 ` M. Edward (Ed) Borasky
2005-05-04 15:36 ` Brett Curtis
2005-05-04 14:12 ` Antwort: " daniel.kerwin
2005-05-04 14:28 ` Omkhar Arasaratnam
2005-05-04 14:35 ` M. Edward (Ed) Borasky
2005-05-04 13:47 ` Daniel Ostrow
2005-05-04 14:09 ` Mike Frysinger
2005-05-04 16:17 ` Michiel de Bruijne [this message]
2005-05-04 16:26 ` Ciaran McCreesh
2005-05-04 16:46 ` Lance Albertson
2005-05-04 16:55 ` Ciaran McCreesh
2005-05-04 20:28 ` Ryan
2005-05-04 22:31 ` David Krider
2005-05-04 23:14 ` Ciaran McCreesh
2005-05-05 1:28 ` Michiel de Bruijne
2005-05-05 14:11 ` Ciaran McCreesh
2005-05-09 20:27 ` Paul de Vrieze
2005-05-05 1:33 ` Chris Gianelloni
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=200505041817.53353.m.debruijne@hccnet.nl \
--to=m.debruijne@hccnet.nl \
--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