linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Chris Ridd <Chris.Ridd@MessagingDirect.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: More commercial interest in Linux PPC
Date: Fri, 23 Jul 1999 09:01:46 +0100	[thread overview]
Message-ID: <15687.932716906@MessagingDirect.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 137 bytes --]

I don't know if anyone's interested in this announcement, but I guess 
it al least shows people don't just assume Linux == Intel.

Chris

[-- Attachment #2: Type: message/rfc822, Size: 2515 bytes --]

From: Mark Gavin <mgavin_list@digapp.com>
To: Acrobat Talk <acrobat@blueworld.com>
Subject: PDF Server based applications on Linux
Date: Thu, 22 Jul 1999 18:02:23 -0400
Message-ID: <v04020a05b3bd44bc4a3f@[38.164.135.200]>


We are in the process of porting our existing server based applications
(FDFMerge, StampPDF Batch and AppendPDF) to Linux.  We intend to support
Red Hat Linux 6.0 running on Intel Pentium processors.

We are debating whether to support other processors running Linux.  For
example:

	Dec Alpha	Compaq
	Sun Sparc	Sun Microsystems
	Cobalt MIPS	Cobalt Networks
	PowerPC		IBM or Apple

We would appreciate feedback from people who are currently running Linux or
who expect to be running Linux in the near future.

This question is not really relevant to the list and I would appreciate any
feedback be sent to me directly at mailto:mgavin@digapp.com.

Thank you.


Mark Gavin
Vice President, Software Development
Digital Applications, Inc.
215 East Providence Road
Aldan, PA 19018-4129
(610) 284-4006
http://www.digapp.com


-----------------------------------------------------------------------
To Unsubscribe: <mailto:acrobat-off@blueworld.com>
Archives : <http://listsearch.blueworld.com/acrobattalksearch.lasso>

                 reply	other threads:[~1999-07-23  8:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=15687.932716906@MessagingDirect.com \
    --to=chris.ridd@messagingdirect.com \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).