From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Nms0l-0003s9-Kv for garchives@archives.gentoo.org; Wed, 03 Mar 2010 17:05:28 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 32EC5E0E3E; Wed, 3 Mar 2010 17:05:02 +0000 (UTC) Received: from smtpout.karoo.kcom.com (smtpout.karoo.kcom.com [212.50.160.34]) by pigeon.gentoo.org (Postfix) with ESMTP id E7C6CE0E3E for ; Wed, 3 Mar 2010 17:05:01 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.49,574,1262563200"; d="scan'208";a="171773045" Received: from unknown (HELO compaq.stroller.uk.eu.org) ([213.152.39.90]) by smtpout.karoo.kcom.com with ESMTP; 03 Mar 2010 17:04:47 +0000 Received: from funf.stroller.uk.eu.org (funf.stroller.uk.eu.org [192.168.1.71]) by compaq.stroller.uk.eu.org (Postfix) with ESMTP id D4C1934080 for ; Wed, 3 Mar 2010 17:04:43 +0000 (GMT) Message-Id: <0E02BFD1-8446-460C-A620-1C2AE57D33A4@stellar.eclipse.co.uk> From: Stroller To: gentoo-user@lists.gentoo.org In-Reply-To: <008DDC13-5883-4155-A996-64325EFCAA77@stellar.eclipse.co.uk> Content-Type: text/plain; charset=UTF-8; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 (Apple Message framework v936) Subject: Re: [gentoo-user] Advice for 64-bit n00b? Date: Wed, 3 Mar 2010 17:04:45 +0000 References: <008DDC13-5883-4155-A996-64325EFCAA77@stellar.eclipse.co.uk> X-Mailer: Apple Mail (2.936) X-Archives-Salt: 35d52cea-5f6a-4f11-8d1c-a16431162821 X-Archives-Hash: 05b5fe97265e4942ba0b13935d27300d On 3 Mar 2010, at 15:29, Stroller wrote: > ... > I have started following the Gentoo Linux AMD64 Handbook, because =20 > the Quick Install Guide is described as "x86". Having untarred the =20 > stage I am surprised to find a lib32 directory. I thought =20 > compatibility with 32-bit binaries was optional. Or am I =20 > misunderstanding? This is going to be a headless server & I can't =20 > think that it'll need any binary packages - possibly the management =20= > utility for the RAID controller will be distributed as a binary, I'm =20= > not sure yet (the hardware RAID key was missing when I got this =20 > machine =E2=98=B9) 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 =20 applications or libraries, you should use a non-multilib profile." See my comments in the quoted above. It shouldn't be too expensive to =20= enable the RAID in this machine (which is on the mainboard, but =20 requires a little hardware PCB "key" to be fitted). That's a Dell =20 PERC4, which AFAICT is a rebadged LSI megaraid. This post [1] http://tinyurl.com/3dzcl9 referrs to the management =20 utility thus: "MegaCLI comes as a RPM containing only a single =20 statically linked 32-bit Linux binary", however `eix mega` suggests =20 there may be alternatives, such as `megactl` [2] My immediate thought when reading the handbook was that it's "best" =20 and "cleanest" and "more right" to only have 64-bit libraries on a 64-=20= bit system, but this need for the RAID management utility is making me =20= 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-S= AS-and-the-self-explaining-CLI.html [2] http://sourceforge.net/projects/megactl/