public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <iod00d@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Installing kernel 2.6.6 on hp zx6000 (fwd)
Date: Wed, 26 May 2004 03:23:31 +0000	[thread overview]
Message-ID: <20040526032331.GK7616@cup.hp.com> (raw)
In-Reply-To: <Pine.GSO.4.58.0405251608490.28567@tokyo.cc.gatech.edu>

On Tue, May 25, 2004 at 04:09:19PM -0400, Younggyun Koh wrote:
> i'm trying to run linux kernel 2.6.6 on hp itanium2 machine - zx6000,
> which is running Redhat advanced server 2.1AW...
> and i got some questions..
> 
> 1. has anyone succeeded with the same condition?

HP formally only tests the original kernels delivered with the OS.
You should just try it if you no longer need formal support from HP.

Nearly all of the folks I know doing 2.6 linux kernel developement are
either using RHEL 3.0, a future release of SLES, or (most likely) Debian.

> 2. nfs-utils currently installed is version 0.3.3. the minimum requirement
> for 2.6.6 is 1.0.5, but i was told from the system management guy that
> installing 1.0.5 might cause serious problems... is it true?

Can you post details?

Sorry - since I run debian "testing" release, I'm not exposed to this kind
of problems. I expect the RHEL update service would avoid them too.
But one wouldn't get a 2.6 kernel yet with that either.

> 3. i got the link error when i build the kernel
> 
> bash-2.05$ make CROSS_COMPILE=/opt/gcc-3.3.3/usr/local/bin/

Can you add "V=1" parameter so we can see the commands?

thanks,
grant

  parent reply	other threads:[~2004-05-26  3:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-25 20:09 Installing kernel 2.6.6 on hp zx6000 (fwd) Younggyun Koh
2004-05-25 20:19 ` Matthew Wilcox
2004-05-26  2:15 ` Younggyun Koh
2004-05-26  3:23 ` Grant Grundler [this message]
2004-05-26 12:46 ` Younggyun Koh
2004-05-26 14:28 ` H. J. Lu
2004-05-26 15:08 ` Grant Grundler
2004-05-27  0:44 ` Younggyun Koh

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=20040526032331.GK7616@cup.hp.com \
    --to=iod00d@hp.com \
    --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