From: Grant Grundler <grundler@cup.hp.com>
To: Sandy Harris <sandy@storm.ca>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Host for 712/60 compiles
Date: Sun, 19 Nov 2000 23:05:26 -0800 [thread overview]
Message-ID: <200011200705.XAA18181@milano.cup.hp.com> (raw)
In-Reply-To: Your message of "Fri, 17 Nov 2000 22:54:58 PST." <3A15FD92.DEB522FE@storm.ca>
Sandy Harris wrote:
> A couple of us have 16 diskless 712/60s which we want to use for distributed
> processing on easily parallelized tasks like factoring and perhaps crypto
> cracking. A few questions arise.
>
> Is PARISC Linux far enough along to be useful for that? We need no monitor or
> console (except perhaps for initial debugging), no devices except ethernet,
> and expect to run only one process per machine, but we need stability.
It's not rock solid. On 712's, it should be pretty good though.
> We'll need a host for cross-compiling. We have a 256 meg 715/100 with HP/UX
> which we expect to use as the host for booting, handing out chunks of work,
> storing results, etc. Should we compile there under HP/UX or would we get
> better tools on one of our Intel Linux boxes?
I don't think anyone has tried to cross-compile parisc-linux on an HPUX
host in quite a while.
> Or is PARISC Linux far enough along we should put it on the 715 and get
> native compilation?
AFAIK, all of the debian packages on the ISO image are built natively.
But using a dual P700 linux box would be alot faster. :^)
grant
Grant Grundler
Unix Systems Enablement Lab
+1.408.447.7253
prev parent reply other threads:[~2000-11-20 7:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-18 3:54 [parisc-linux] Host for 712/60 compiles Sandy Harris
2000-11-20 7:05 ` Grant Grundler [this message]
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=200011200705.XAA18181@milano.cup.hp.com \
--to=grundler@cup.hp.com \
--cc=parisc-linux@thepuffingroup.com \
--cc=sandy@storm.ca \
/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