linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Rick Ewing" <rick@ewing.org>
To: someguy <someguy@rakis.net>, linuxppc-dev@lists.linuxppc.org
Subject: Re: IBM providing Linux for RS6000
Date: Thu, 18 Feb 1999 20:19:57 -0600	[thread overview]
Message-ID: <36CCCA4D.674C653F@ewing.org> (raw)
In-Reply-To: 199902182152.QAA20060@ns2.gis.net


Published reports already say that IBM has been talking to the LinuxPPC guys
for a little while and will likely use their product for a demo an upcoming
trade show.  For IBM, if these guys are producing a good port, why reinvent
the wheel on an OS with little revenue potential? (In IBM's terms of dollars)

Rick Ewing


someguy wrote:

> >Will the fact that IBM is going to be providing it's own version going to
> >have any effects on the linuxppc development efforts?
> >
> >If so, will it be positive or negative?
>
> I thought IBM talked to J. Haas about getting LinuxPPC on the IBMs?
>
> justin


[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

  parent reply	other threads:[~1999-02-19  2:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-18 21:51 IBM providing Linux for RS6000 someguy
1999-02-18  3:22 ` sean o'malley
1999-02-19 17:18   ` RedHat ppc dist. [was: IBM providing Linux for RS6000] Gedanken
1999-02-19  2:19 ` Rick Ewing [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-02-18 19:26 IBM providing Linux for RS6000 Greg Stovall
1999-02-18 20:50 ` David Edelsohn
1999-02-19  1:11 ` Jason Haas
1999-02-19  3:25 ` Cort Dougan

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=36CCCA4D.674C653F@ewing.org \
    --to=rick@ewing.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=someguy@rakis.net \
    /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;
as well as URLs for NNTP newsgroup(s).