From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Advice for 64-bit n00b?
Date: Wed, 3 Mar 2010 17:04:45 +0000 [thread overview]
Message-ID: <0E02BFD1-8446-460C-A620-1C2AE57D33A4@stellar.eclipse.co.uk> (raw)
In-Reply-To: <008DDC13-5883-4155-A996-64325EFCAA77@stellar.eclipse.co.uk>
On 3 Mar 2010, at 15:29, Stroller wrote:
> ...
> I have started following the Gentoo Linux AMD64 Handbook, because
> the Quick Install Guide is described as "x86". Having untarred the
> stage I am surprised to find a lib32 directory. I thought
> compatibility with 32-bit binaries was optional. Or am I
> misunderstanding? This is going to be a headless server & I can't
> think that it'll need any binary packages - possibly the management
> utility for the RAID controller will be distributed as a binary, I'm
> not sure yet (the hardware RAID key was missing when I got this
> machine ☹)
Further to Alan's reply, I've proceeded a little further.
I'm onto section 2.3: Changing profiles, where it says:
"If you want to have a pure 64-bit environment, with no 32-bit
applications or libraries, you should use a non-multilib profile."
See my comments in the quoted above. It shouldn't be too expensive to
enable the RAID in this machine (which is on the mainboard, but
requires a little hardware PCB "key" to be fitted). That's a Dell
PERC4, which AFAICT is a rebadged LSI megaraid.
This post [1] http://tinyurl.com/3dzcl9 referrs to the management
utility thus: "MegaCLI comes as a RPM containing only a single
statically linked 32-bit Linux binary", however `eix mega` suggests
there may be alternatives, such as `megactl` [2]
My immediate thought when reading the handbook was that it's "best"
and "cleanest" and "more right" to only have 64-bit libraries on a 64-
bit system, but this need for the RAID management utility is making me
wonder if that would be cutting off my nose to spite my face.
Thoughts?
Stroller.
[1] http://www.kaltenbrunner.cc/blog/index.php?/archives/4-LSIlogic-MegaRAID-SAS-and-the-self-explaining-CLI.html
[2] http://sourceforge.net/projects/megactl/
next prev parent reply other threads:[~2010-03-03 17:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 15:29 [gentoo-user] Advice for 64-bit n00b? Stroller
2010-03-03 15:32 ` Alan McKinnon
2010-03-03 17:04 ` Stroller [this message]
2010-03-03 20:04 ` Alan McKinnon
2010-03-03 22:50 ` Mick
2010-03-03 22:56 ` Volker Armin Hemmann
2010-03-04 6:44 ` Graham Murray
2010-03-04 7:19 ` [gentoo-user] " Nikos Chantziaras
2010-03-04 8:16 ` Volker Armin Hemmann
2010-03-04 8:56 ` Stroller
2010-03-04 9:15 ` Volker Armin Hemmann
2010-03-04 12:02 ` Mick
2010-03-05 1:52 ` Walter Dnes
2010-03-04 7:23 ` [gentoo-user] " Zeerak Mustafa Waseem
2010-03-04 7:30 ` Alan McKinnon
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=0E02BFD1-8446-460C-A620-1C2AE57D33A4@stellar.eclipse.co.uk \
--to=stroller@stellar.eclipse.co.uk \
--cc=gentoo-user@lists.gentoo.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