public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Boyd Stephen Smith Jr." <bss03@volumehost.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] chroot: cannot run command `bin/bash': Exec format error
Date: Wed, 22 Feb 2006 17:42:36 -0600	[thread overview]
Message-ID: <200602221742.36605.bss03@volumehost.com> (raw)
In-Reply-To: <200602230003.33868.bo.andresen@gmail.com>

On Wednesday 22 February 2006 17:03, Bo Andresen <bo.andresen@gmail.com> 
wrote about '[gentoo-user] chroot: cannot run command `bin/bash': Exec 
format error':
> I have just purchased a new computer with a AMD Semphron 2800+ 64 bit
> processor. I am installing it following the gentoo handbook of the amd64
> architecture - only I am using the x86 minimal livecd (2005-r1) and the
> stage3-amd64-2005.1-r1.tar.bz2 tarball. Shouldn that be a problem?

Definitely a problem.

> livecd gentoo # chroot /mnt/gentoo bin/bash
> chroot: cannot run command `bin/bash': Exec format error

Your 32-but kernel can't run the 64-bit bash.  You'll have to use a 64-bit 
kernel (or as 32-bit stage3, and then gradually recompile)

> I did use LVM2 for partitioning but other than that I have followed the
> handbook very throughly. I hope someone has a solution.  Please feel
> free to ask for any information that may be helpful.

If you have a little bit of free space, do a 32-bit install to a separate 
LV.  No need to really do a full install, just enough so you can compile a 
64-bit kernel and install and configure your bootloader to load the 64-bit 
kernel.

That should be as easy as lvcreate, format, mount, extract 32-bit stage3, 
cp over /etc/resolv.conf, chroot, emerge <your_favorite>-sources, 
cd /usr/src/<whatever>, zcat /proc/config.gz > .config, make oldconfig, 
make, emerge grub, mount /boot, grub-install, make install, umount boot, 
shutdown -r now.

(Maybe a few steps I'm missing, and I don't mess with (e)lilo.)

-- 
Boyd Stephen Smith Jr.
bss03@volumehost.com
ICQ: 514984 YM/AIM: DaTwinkDaddy
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2006-02-22 23:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-22 23:03 [gentoo-user] chroot: cannot run command `bin/bash': Exec format error Bo Andresen
2006-02-22 23:14 ` John Jolet
2006-02-22 23:28   ` [gentoo-user] " Mick
2006-02-22 23:41     ` Bo Andresen
2006-02-22 23:18 ` [gentoo-user] " Boris Fersing
2006-02-22 23:42 ` Boyd Stephen Smith Jr. [this message]
2006-02-22 23:51   ` Bo Andresen
2006-02-23 21:31   ` Bo Andresen
2006-02-23 21:40     ` Boyd Stephen Smith Jr.
2006-02-23 21:56       ` Bo Andresen
2006-02-23 22:33         ` Boyd Stephen Smith Jr.
2006-02-23 23:25           ` Bo Andresen
2006-02-23 23:52             ` Boyd Stephen Smith Jr.
2006-02-24  0:12               ` Bo Andresen
2006-02-24  0:16                 ` Bo Andresen
2006-02-24  0:32                   ` Boyd Stephen Smith Jr.
2006-02-24  0:56                     ` Boyd Stephen Smith Jr.
2006-02-24  1:07                       ` Bo Andresen
2006-02-24  5:18                         ` Boyd Stephen Smith Jr.
2006-02-24 12:56                           ` [gentoo-user] chroot: cannot run command `bin/bash': Exec format error [SOLVED] Bo Andresen
2006-02-24 21:07                             ` Boyd Stephen Smith Jr.

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=200602221742.36605.bss03@volumehost.com \
    --to=bss03@volumehost.com \
    --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