From: Jeremy Fox <jerfox@Stanford.EDU>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Basic Advice Needed
Date: Mon, 01 Apr 2002 07:24:19 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905350@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905348@msgid-missing>
On Sun, Mar 31, 2002 at 07:30:16PM -0800, Randolph Chung wrote:
> That is hard to believe, but in any case, you can get Debian isos at:
> http://www.debian.org/ports/ia64/
Thanks for the link. RedHat ia64 seems to be open source as long as
you are willling to open your wallet for $495. Seriously you can
download the individual files but not isos and the seller wasn't able
to make bootable CDs properly. I went to the RedHat ia64 list and I
see some anguish but no success stories.
> Dunno about "high memory", but the Debian ia64 build daemon builds on the
> order of 100-150 packages of various complexity every day and it's been
> running for over 100 days. It's a HP i2000 with 2G of RAM
The seller claims it's stable with only 2 GB of RAM, but when he ups
it to 5 GB with SuSE 7.1 the machine crashes every hour or so. If this
is a software problem it's not good because the whole point of using a
64-bit machine is to address more than 2 GB with one process.
--
------------------------
Jeremy T. Fox
jerfox@stanford.edu
next prev parent reply other threads:[~2002-04-01 7:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-01 3:20 [Linux-ia64] Basic Advice Needed Jeremy Fox
2002-04-01 3:30 ` Randolph Chung
2002-04-01 7:24 ` Jeremy Fox [this message]
2002-04-01 14:42 ` Van Maren, Kevin
2002-04-01 15:25 ` n0ano
2002-04-01 16:17 ` Andreas Schwab
2002-04-01 23:18 ` Jeremy Fox
2002-04-02 7:52 ` Andreas Schwab
2002-04-02 8:29 ` Gwenole Beauchesne
2002-04-02 15:14 ` Van Maren, Kevin
2002-04-03 0:17 ` Jeremy Fox
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=marc-linux-ia64-105590701905350@msgid-missing \
--to=jerfox@stanford.edu \
--cc=linux-ia64@vger.kernel.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