public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Omkhar Arasaratnam <omkhar@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: Antwort: Re: Antwort: Re: [gentoo-dev] Gentoo could become certified for IBM Server Hardware
Date: Wed, 04 May 2005 10:28:27 -0400	[thread overview]
Message-ID: <4278DC0B.9030604@gentoo.org> (raw)
In-Reply-To: <OFDE4B6240.F956C62D-ONC1256FF7.004DAD05-42256FF7.004D9379@inside.allianz.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
daniel.kerwin@allianz.de wrote:

> Well i also was very surprised to become this offering from IBM. I
> tried this for a long time with very less success :(
>
> All i can say is that i talked to IBM's Senior IT Architct for
> Principal Linux Services and he told me that theres a chance to do
> this. Of cause he didn't said something about a gurantee that IBM
> really would do so. But anyway i think it's definitively worth
> trying.
>
Ah now I understand. You've been speaking to the Global Services
(consulting side) people. I don't doubt that IBM would love to engage
with Gentoo for SERVICES (ie manage your server, or develop a protien
folding cluster and install it for you). However, you will not see IBM
preloading, or releasing kernel modules for gentoo-sources.

I'm not trying to be a roadblock here, infact I know many of the
people in the Open Source Community of Practice at IBM, so please let
me know where you would like this to go.

- --
Omkhar Arasaratnam - Gentoo PPC64 Developer
omkhar@gentoo.org - http://dev.gentoo.org/~omkhar
Gentoo Linux / PPC64 Linux: http://ppc64.gentoo.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
 
iD8DBQFCeNwL9msUWjh2lHURAqd5AJwN2/kWNj3+OKmEjkTTzwwtfuJx0QCeN0s7
xh+VcqAc4HcOf27dZm7vxWk=
=k7vh
-----END PGP SIGNATURE-----


-- 
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2005-05-04 14:28 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 [this message]
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
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=4278DC0B.9030604@gentoo.org \
    --to=omkhar@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