Re: [gentoo-user] chroot complain not able to find file/directory when it's actually there
On Sunday 04 January 2009 06:41:31 Zhang Weiwu wrote: Hello. Sorry for stupid newbie question: # cp /bin/sh /usr/local/bin/sh # chroot /usr/local /bin/sh chroot: cannot run command `/bin/sh': No such file or directory In theory it should work, right? This is the first time I run chroot not for rescuing a broken system (which means /dev/ and /proc/ are not mounted in chroot jail). However I guess /dev/ and /proc/ doesn't have to be mounted to run chroot. I am sure this is not because the executable is dynamically linked to a file outside of the chroot jail, because I also tried to run executables compiled with USE=static What could be the reason (for complaining an existing file No such file)? Thanks in advance. Using coreutils-6.10-r2 on ibook/ppc Do this: a...@nazgul ~ $ ls -al /bin/sh lrwxrwxrwx 1 root root 4 Nov 24 09:58 /bin/sh - bash sh is a symlink to bash. You do not have bash inside your chroot, and that is the file that is not being found. You must also run ldd on bash, see all the libs it links to and copy those as well into the chroot -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] chroot problem
On Sunday 01 June 2008 20:10:22 Neil Bothwick wrote: On Sun, 1 Jun 2008 18:51:02 +0100, Peter Humphrey wrote: * Is there a way to find out what USE flags a package has been compiled with when it's not the current system but a rescue system mounted temporarily in it? Anyone? Look in var/db/pkg/cate-gory/pkgname-version/USE Thanks Neil. -- Rgds Peter -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] chroot problem
2008/5/29 Peter Humphrey [EMAIL PROTECTED]: I have no problem chrooting into a system on the hard disk if I've booted from an installation CD, but every time I try it after booting from another HD partition I get e.g. this: # chroot /mnt/rescue /bin/bash chroot: cannot run command `/bin/bash': Permission denied Are you using SELinux or anything similar? If so (or you aren't sure), what do the following commands (as root) say: id -Z ls -alZR /mnt/rescue If not then try strace'ing the chroot call, like so: strace -etrace=chroot,chdir,execve chroot /mnt/rescue /bin/bash That will show whether it is the chroot call itself that is failing or the attempt to run bash afterwards. Cheers, Duane. -- I never could learn to drink that blood and call it wine - Bob Dylan -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] chroot problem
On Saturday 31 May 2008 21:09:52 Alexander Meinke wrote: However, I think this problem is [neither] mount nor bash related. Try # mount -tproc proc /mnt/rescue/proc # mount -obind /dev /mnt/rescue/dev # chroot /mnt/rescue /bin/bash That's almost exactly what I did. To be certain, I tried it with the full paths you suggest, but of course I got the same result. Especially check the permissions of /mnt/rescue/bin/bash and /bin/bash. They should be at least 0755. As I said the first time, the permissions are the same on both, thus: # ls -l bin/bash -rwxr-xr-x 1 root root 772120 2008-05-29 17:29 bin/bash # ls -l /mnt/rescue/bin/bash -rwxr-xr-x 1 root root 772120 2008-05-29 17:29 /mnt/rescue/bin/bash As they're the same size, I assume they're the same version - but they could have been compiled with different USE flags. I'll look into that. [Later: on remerging bash in the main system the flags look perfectly innocent, and I can't imagine having set them differently on the rescue system; but I will look next time I boot the rescue system*.] ... rebuild the package that include 'chroot' so that right permissions are set for the program and its libs. The permissions are right already, but I'll do that anyway. I hope this helps in any way and excuse me for that bad English. I've no difficulty following you :-) Thanks also to the others who've helped. Wolf's idea wouldn't help me because I want a separate system that will boot even if the main one won't. It's on a different physical disk as well. * Is there a way to find out what USE flags a package has been compiled with when it's not the current system but a rescue system mounted temporarily in it? Anyone? -- Rgds Peter -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] chroot problem
On Sun, 1 Jun 2008 18:51:02 +0100, Peter Humphrey wrote: * Is there a way to find out what USE flags a package has been compiled with when it's not the current system but a rescue system mounted temporarily in it? Anyone? Look in var/db/pkg/cate-gory/pkgname-version/USE -- Neil Bothwick Does the name Pavlov ring a bell? signature.asc Description: PGP signature
Re: [gentoo-user] chroot problem
On Thursday 29 May 2008 10:50:59 [EMAIL PROTECTED] wrote: Wolf Canis [EMAIL PROTECTED] Only for verification, have you under /mnt/rescue /bin/bash? Or with other words have this /mnt/rescue/bin/bash? And with the appropriate permissions? Yes, I said so the first time. W. Canis Just in case, you'll also need proper permissions for /mnt/rescue/lib and libraries inside there. Bash dinamically loads libraries, so the user running it must have execution perms over invoked libraries. That puzzled me for two weeks till I finally fixed it last saturday :-P No, that isn't it either. I'm doing everything as root, as one would when installing or repairing the system. I never have got chrooting working as an ordinary user. I installed both the rescue system and the main system from the current installation CD, whichever that was - 2007.1, I think. In each case, I continued the installation to build the system I wanted: KDE on the main system and only a few tools on the rescue system. I didn't mess about with essential system components like bash. Is it possible that chrooting from one bash version to another is my problem? I think they're the same, and it'll take me some time to check. Or maybe the problem is in the chroot function in the system I'm leaving. -- Rgds Peter -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] chroot problem
On Thursday 29 May 2008 10:28:40 Dirk Heinrichs wrote: Am Donnerstag, 29. Mai 2008 schrieb ext Peter Humphrey: What am I doing wrong? Just a wild guess: /mnt/rescue mounted with noexec? No, that isn't it. -- Rgds Peter -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] chroot problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter Humphrey wrote: [...] # cd /mnt/rescue # mount -tproc proc proc # mount -obind /dev dev I mean that the mount commands should be: # mount -tproc proc /mnt/rescue/proc # mount -obind /dev /mnt/rescue/dev I just build a mini chroot environment. My working directory is /root. I create under /root a directory x. The contents under x is: # ls -R x: bin dev lib proc x/bin: bash x/dev: x/lib: ld-linux.so.2 libc.so.6 libdl.so.2 libncurses.so.5 x/proc: Then my mount commands: # mount -tproc proc x/proc # mount -obind /dev x/dev Then chroot: # chroot /root/x /bin/bash wolf-di6400 0(0) 10:38 AM / # Hope that helps. W. Canis -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkhBKyMACgkQKT9zBKF0twWttgCffzjUSQZAxNBZcAwf9avjvZYa YDoAn1Rw5y18equ4b+27hAhCnboyfF0x =Um4X -END PGP SIGNATURE- -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] chroot problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wolf Canis wrote: Peter Humphrey wrote: [...] # cd /mnt/rescue # mount -tproc proc proc # mount -obind /dev dev I mean that the mount commands should be: # mount -tproc proc /mnt/rescue/proc # mount -obind /dev /mnt/rescue/dev Ooops, I overlooked your cd command. Therefore the mount command is of course correct. :-[ W. Canis -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkhBSZgACgkQKT9zBKF0twXnmgCeKd9BcrcinpSFZYlYHH6JkYmJ TAUAnjVNmHArsqLbx3nclUPDhIZqQzbW =nt4b -END PGP SIGNATURE- -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] chroot problem
Wolf Canis wrote:
# mount -tproc proc /mnt/rescue/proc
# mount -obind /dev /mnt/rescue/dev
Ooops, I overlooked your cd command. Therefore the
mount command is of course correct. :-[
Hi,
I think this is, although the 'cd' command is executed, necessary as the mount
command looks at /etc/fstab and if e.g. 'proc' is specified at command line
mount uses information from fstab.
However, I think this problem is whether mount nor bash related. Try
# mount -tproc proc /mnt/rescue/proc
# mount -obind /dev /mnt/rescue/dev
# chroot /mnt/rescue /bin/bash
Especially check the permissions of /mnt/rescue/bin/bash and /bin/bash. They
should be at least 0755. In case of there are several permission problems last
time on my system ('up-to-date-system', no ~*) rebuild the package that include
'chroot' so that right permissions are set for the program and its libs.
I hope this helps in any way and excuse me for that bad English.
Regards,
acm.
signature.asc
Description: OpenPGP digital signature
Re: [gentoo-user] chroot problem
Peter Humphrey schrieb: I have no problem chrooting into a system on the hard disk if I've booted from an installation CD, but every time I try it after booting from another HD partition I get e.g. this: # chroot /mnt/rescue /bin/bash chroot: cannot run command `/bin/bash': Permission denied Ls shows the same permissions in each case, and I always make sure to: # cd /mnt/rescue # mount -tproc proc proc # mount -obind /dev dev ...first. What am I doing wrong? # cd /mnt/rescue # mount -t proc proc proc # mount -o bind /dev dev You forgot some spaces! signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] chroot problem
Am Donnerstag, 29. Mai 2008 schrieb ext Peter Humphrey: I have no problem chrooting into a system on the hard disk if I've booted from an installation CD, but every time I try it after booting from another HD partition I get e.g. this: # chroot /mnt/rescue /bin/bash chroot: cannot run command `/bin/bash': Permission denied Ls shows the same permissions in each case, and I always make sure to: # cd /mnt/rescue # mount -tproc proc proc # mount -obind /dev dev ...first. What am I doing wrong? Just a wild guess: /mnt/rescue mounted with noexec? Bye... Dirk -- Dirk Heinrichs | Tel: +49 (0)162 234 3408 Configuration Manager | Fax: +49 (0)211 47068 111 Capgemini Deutschland | Mail: [EMAIL PROTECTED] Wanheimerstraße 68 | Web: http://www.capgemini.com D-40468 Düsseldorf | ICQ#: 110037733 GPG Public Key C2E467BB | Keyserver: wwwkeys.pgp.net signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] chroot problem
Dirk Heinrichs schrieb: Am Donnerstag, 29. Mai 2008 schrieb ext Justin: # cd /mnt/rescue # mount -tproc proc proc # mount -obind /dev dev ...first. What am I doing wrong? # cd /mnt/rescue # mount -t proc proc proc # mount -o bind /dev dev You forgot some spaces! They're irrelevant. Bye... Dirk Really? I didn't know that, thanks! signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] chroot problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter Humphrey wrote: I have no problem chrooting into a system on the hard disk if I've booted from an installation CD, but every time I try it after booting from another HD partition I get e.g. this: # chroot /mnt/rescue /bin/bash chroot: cannot run command `/bin/bash': Permission denied Ls shows the same permissions in each case, and I always make sure to: # cd /mnt/rescue # mount -tproc proc proc # mount -obind /dev dev ...first. What am I doing wrong? Only for verification, have you under /mnt/rescue /bin/bash? Or with other words have this /mnt/rescue/bin/bash? And with the appropriate permissions? W. Canis -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkg+eZ0ACgkQKT9zBKF0twWTtwCdHIkXGHwaas50Zy2leKo5g6iU gP8AnRuiWCgemE/GFja4RaduEfcWp/9g =hplz -END PGP SIGNATURE- -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] chroot problem
Wolf Canis [EMAIL PROTECTED] 29/05/2008 11:38 Por favor, responda a gentoo-user Para: gentoo-user@lists.gentoo.org cc: Asunto: Re: [gentoo-user] chroot problem -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter Humphrey wrote: I have no problem chrooting into a system on the hard disk if I've booted from an installation CD, but every time I try it after booting from another HD partition I get e.g. this: # chroot /mnt/rescue /bin/bash chroot: cannot run command `/bin/bash': Permission denied Ls shows the same permissions in each case, and I always make sure to: # cd /mnt/rescue # mount -tproc proc proc # mount -obind /dev dev ...first. What am I doing wrong? Only for verification, have you under /mnt/rescue /bin/bash? Or with other words have this /mnt/rescue/bin/bash? And with the appropriate permissions? W. Canis -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkg+eZ0ACgkQKT9zBKF0twWTtwCdHIkXGHwaas50Zy2leKo5g6iU gP8AnRuiWCgemE/GFja4RaduEfcWp/9g =hplz -END PGP SIGNATURE- -- gentoo-user@lists.gentoo.org mailing list ** Just in case, you'll also need proper permissions for /mnt/rescue/lib and libraries inside there. Bash dinamically loads libraries, so the user running it must have execution perms over invoked libraries. That puzzled me for two weeks till I finally fixed it last saturday :-P HTH, Abraham -- gentoo-user@lists.gentoo.org mailing list
Re: [gentoo-user] chroot problem
Am Donnerstag, 29. Mai 2008 schrieb ext Justin: # cd /mnt/rescue # mount -tproc proc proc # mount -obind /dev dev ...first. What am I doing wrong? # cd /mnt/rescue # mount -t proc proc proc # mount -o bind /dev dev You forgot some spaces! They're irrelevant. Bye... Dirk -- Dirk Heinrichs | Tel: +49 (0)162 234 3408 Configuration Manager | Fax: +49 (0)211 47068 111 Capgemini Deutschland | Mail: [EMAIL PROTECTED] Wanheimerstraße 68 | Web: http://www.capgemini.com D-40468 Düsseldorf | ICQ#: 110037733 GPG Public Key C2E467BB | Keyserver: wwwkeys.pgp.net signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] Chroot question
Anthony E. Caudel wrote: I have an AMD64 chip and have separate Gentoo x86 and x86_64 distros. Gentoo has a 32Bit Chroot Guide for Gentoo/AMD64 but this guide only discusses setting up a separate 32bit environment within the 64bit Gentoo. I was wondering if it could be used, suitably modified, to chroot from my x86_64 bit distro to my x86 distro. Will it mess up one or the other? Tony You should be fine as long as you ignore the installation steps. Just make sure you have the proper options in the 64 bit kernel and use the proper chroot command. PaulNM -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Chroot question
On Tue, 20 Nov 2007 21:33:15 -0600 Anthony E. Caudel [EMAIL PROTECTED] wrote: I have an AMD64 chip and have separate Gentoo x86 and x86_64 distros. Gentoo has a 32Bit Chroot Guide for Gentoo/AMD64 but this guide only discusses setting up a separate 32bit environment within the 64bit Gentoo. I was wondering if it could be used, suitably modified, to chroot from my x86_64 bit distro to my x86 distro. Will it mess up one or the other? No, they won't effect each other, but isn't this generally how a multi-lib system is done? I read a howto years ago but got bored halfway through, and since I didn't need it anyway, I gave up. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Chroot question
Dan Farrell wrote: On Tue, 20 Nov 2007 21:33:15 -0600 Anthony E. Caudel [EMAIL PROTECTED] wrote: I have an AMD64 chip and have separate Gentoo x86 and x86_64 distros. Gentoo has a 32Bit Chroot Guide for Gentoo/AMD64 but this guide only discusses setting up a separate 32bit environment within the 64bit Gentoo. I was wondering if it could be used, suitably modified, to chroot from my x86_64 bit distro to my x86 distro. Will it mess up one or the other? No, they won't effect each other, but isn't this generally how a multi-lib system is done? I read a howto years ago but got bored halfway through, and since I didn't need it anyway, I gave up. Good point. I don't know the difference between chroot'ing and multilib (well, I know the difference but I don't the advantages/disadvantages of each). The reason I want to be able to chroot is that I want to be able run make menuconfig in each distro in order to view, side-by-side the configuration of the kernels. The x86 distro is my production distro but I want to configure and tune the x86_64 kernel to be as close to the x86 kernel as possible. Tony -- Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Chroot to new environment complains about kernel
Bertram Scharpf wrote: I try to chroot to a brand new environment, freshly unpacked from stage 3: kyle # chroot /mnt/hdb/ /bin/bash FATAL: kernel too old kyle # uname -a Linux kyle 2.6.8-3-686 #1 Tue Dec 5 21:26:38 UTC 2006 i686 2.6.8? That's old. Why not upgrade the kernel to 2.6.16-r13? You're trying to chroot from another Gentoo system, right? Benno -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Chroot to new environment complains about kernel
On 12/14/06, Bertram Scharpf [EMAIL PROTECTED] wrote: Hi, I try to chroot to a brand new environment, freshly unpacked from stage 3: kyle # chroot /mnt/hdb/ /bin/bash FATAL: kernel too old kyle # uname -a Linux kyle 2.6.8-3-686 #1 Tue Dec 5 21:26:38 UTC 2006 i686 GNU/Linux After that, I unpacked stage 1. The boostrap worked fine until during compilation of glibc a command .././scripts/mkinstalldirs stoped with (yes!): FATAL: kernel too old. An strace of the chroot command ends with the uname function call yielding the above results and returning 0. Then, the message is output and exit is called. Google did not give me any hints. Thanks in advance for any hints. Bertram -- Bertram Scharpf Stuttgart, Deutschland/Germany http://www.bertram-scharpf.de -- gentoo-user@gentoo.org mailing list This happens when you try to chroot to a system that has a much newer kernel than the one you're running. The solution is to use a newer gentoo boot cd. -- - Mark Shields
Re: [gentoo-user] Chroot to new environment complains about kernel
On Friday 15 December 2006 01:54, Bertram Scharpf wrote: Hi, I try to chroot to a brand new environment, freshly unpacked from stage 3: kyle # chroot /mnt/hdb/ /bin/bash FATAL: kernel too old kyle # uname -a Linux kyle 2.6.8-3-686 #1 Tue Dec 5 21:26:38 UTC 2006 i686 GNU/Linux After that, I unpacked stage 1. The boostrap worked fine until during compilation of glibc a command .././scripts/mkinstalldirs stoped with (yes!): FATAL: kernel too old. An strace of the chroot command ends with the uname function call yielding the above results and returning 0. Then, the message is output and exit is called. Google did not give me any hints. It means your running kernel is too old for the version of glibc in your chroot. Either upgrade your kernel or downgrade glibc in the chroot. You can probably do the latter by downloading an older stage3 e.g. 2006.0 (or possibly 2005.x...). -- Bo Andresen pgpd2fzBKzxCy.pgp Description: PGP signature
Re: [gentoo-user] chroot to gentoo amd64
On 9/20/06, Bo Ørsted Andresen [EMAIL PROTECTED] wrote: On Thursday 21 September 2006 05:06, Drew wrote: You need a 64 bit kernel with CONFIG_IA32_EMUL enabled. Uh no. A 32bit chroot can be run on a 64bit kernel with IA32_EMUL enabled however a 64bit chroot can *NOT* be run from a 32bit kernel. Err..., which differs from what I stated exactly how?? how can i chroot to gentoo amd64 from 32 bit Linux ?? It sounds like he wants to chroot into an 64bit environment from an existing 32bit environment. You can't execute 64bit code inside a 32bit chroot because the underlying kernel is still 32bit, and hence can't understand the 64bit code. Short of building a 64bit kernel (your suggestion) there's no way to execute 64bit code from inside a 32bit system. And if he's going to go to the trouble of building a 64bit kernel just for this chroot (assuming his hardware supports 64bit which I am assuming it does), he might as well migrate fully from the 32bit kernel he has and take full advantage of a 64bit one. -Drew -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] chroot to gentoo amd64
On 9/20/06, S. M. Ibrahim (Lavlu) [EMAIL PROTECTED] wrote: how can i chroot to gentoo amd64 from 32 bit Linux ?? You would be trying to run 64 bit programs on a 32 bit operation system? That doesn't sound like it will work too well ;) If you need to chroot, use a 64 bit live cd (unless you can pull off some funky emulation stuff - no clue.) Good luck! -- Neil Isaac [EMAIL PROTECTED] -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] chroot to gentoo amd64
On Wednesday 20 September 2006 22:07, S. M. Ibrahim (Lavlu) wrote: how can i chroot to gentoo amd64 from 32 bit Linux ?? You need a 64 bit kernel with CONFIG_IA32_EMUL enabled. See [1] for more details... [1] http://groups.google.com/group/linux.gentoo.user/browse_frm/thread/e4629ea8751a9ab4/815dbc64722b7d49%23815dbc64722b7d49 -- Bo Andresen pgpnSVXrDGXkl.pgp Description: PGP signature
Re: [gentoo-user] chroot to gentoo amd64
You need a 64 bit kernel with CONFIG_IA32_EMUL enabled. Uh no. A 32bit chroot can be run on a 64bit kernel with IA32_EMUL enabled however a 64bit chroot can *NOT* be run from a 32bit kernel. -Drew -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] chroot to gentoo amd64
On Thursday 21 September 2006 05:06, Drew wrote: You need a 64 bit kernel with CONFIG_IA32_EMUL enabled. Uh no. A 32bit chroot can be run on a 64bit kernel with IA32_EMUL enabled however a 64bit chroot can *NOT* be run from a 32bit kernel. Err..., which differs from what I stated exactly how?? -- Bo Andresen pgpuNj9fz72ci.pgp Description: PGP signature
Re: [gentoo-user] chroot: cannot run command `/bin/bash'
moriah ~ # ldd /bin/bash linux-gate.so.1 = (0xe000) libncurses.so.5 = /lib/libncurses.so.5 (0xb7f28000) libdl.so.2 = /lib/libdl.so.2 (0xb7f23000) libc.so.6 = /lib/libc.so.6 (0xb7dec000) /lib/ld-linux.so.2 (0xb7f84000) moriah ~ # equery belongs /lib/libc.so.6 [ Searching for file(s) /lib/libc.so.6 in *... ] sys-libs/glibc-2.3.6-r4 (/lib/libc.so.6 - libc-2.3.6.so) moriah ~ so bash needs glibc! Your best bet would be to locate a glibc bin package (from the livecd?)and untar it in / of your system, then it should work enough to rebuild properly. You could just copy in the missing libs as you discover them, but thats probably going to be worse :( BillK On Sat, 2006-07-22 at 13:45 +0200, oskar kapala wrote: Hi, I unmerged glibc, I know it's stupid, by I did it. I know how to solve the problem, but sth is wrong with chroot: -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] chroot: cannot run command `/bin/bash'
Hi oskar, on Saturday, 2006-07-22 at 13:45:01, you wrote: chroot: cannot run command `/bin/bash': No such file or directory of course file is present, executable, and I'm doing it as su... You should be fine if ou follow William's instructions. The reason for this is the error the linker returns to execve(2): | ENOENT The file filename or a script or ELF interpreter does not |exist, or a shared library needed for file or inter- |preter cannot be found. cheers! Matthias -- I prefer encrypted and signed messages. KeyID: FAC37665 Fingerprint: 8C16 3F0A A6FC DF0D 19B0 8DEF 48D9 1700 FAC3 7665 pgp0WRxjmucrQ.pgp Description: PGP signature
Re: [gentoo-user] chroot
El Wed, 29 Mar 2006 01:55:43 -0500 Walter Dnes dijo: Hi! That's not necessary. I regularly... - start off with a basic text-console-only install - and then I fire up emerge gimp before heading off to work By the time I get home from work, Portage has pulled in and built the approximately 40 packages necessary to get a basic X GUI running with TWM and has built Gimp. rpm-hell... what's that??? Portage rocks!!! The basic X support doesn't show up in /var/lib/portage/world. It's installed as dependancy for various applications. Another cute trick is to emerge bbkeys without first emerge blackbox. blackbox doesn't show up in world either. It's a dependancy for bbkeys. [m3000][root][~] grep -c ^. /var/lib/portage/world 54 ...yes folks, only 54 entries in world for a full-featured desktop with a whole bunch of apps. Like I said, all the dependancies end up as dependancies. Maybe I don't understand the benefits of your action, but what advantages do you get doing so? I always do a emerge -uD world, so package and its dependency... I do not care if dependency it's in world or not... Please, could you please explain a little more your post? I'm intrigued... Cheers! -- Arnau Bria http://blog.emergetux.net Por regla general, las chicas malas suelen ser las que están más buenas. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] chroot
On Wed, 29 Mar 2006 01:55:43 -0500 Walter Dnes [EMAIL PROTECTED] wrote: That's not necessary. I regularly... - start off with a basic text-console-only install - and then I fire up emerge gimp before heading off to work I need those apps installed so I can get mail and serve my personal web site. By the time I get home from work, Portage has pulled in and built the approximately 40 packages necessary to get a basic X GUI running with TWM and has built Gimp. rpm-hell... what's that??? Portage rocks!!! I like that idea. Though it doesn't always work. For example, last night I did an emerge -vb gnome and woke up to find that it died only 30 minutes into the build. I was expecting to have a full gnome desktop today, but I am still building now. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] chroot
On Wed, 29 Mar 2006 12:05:35 -0500, JimD wrote: I like that idea. Though it doesn't always work. For example, last night I did an emerge -vb gnome and woke up to find that it died only 30 minutes into the build. I was expecting to have a full gnome desktop today, but I am still building now. Why not do a Stage 3 install then emerge GRP GNOME packages? You can have a full desktop system running in around an hour. You can customise your USE flags and compile to suit once the system is running and in use. -- Neil Bothwick Photons have mass? I didn't know they were catholic! signature.asc Description: PGP signature
Re: [gentoo-user] chroot
On Wed, Mar 29, 2006 at 03:44:02PM +0200, Arnau Bria Ram??rez wrote Maybe I don't understand the benefits of your action, but what advantages do you get doing so? I always do a emerge -uD world, so package and its dependency... I do not care if dependency it's in world or not... Please, could you please explain a little more your post? I'm intrigued... What I said was, when doing the install... - start off with a basic text-console-only install - and then I fire up emerge gimp before heading off to work It's not necessary to figure out what dependancies are required. Portage will do it for you. You do not need to waste time figuring out how to build X or parts of GNOME or KDE separately. Of course, if you want the GNOME or KDE desktop, then you'll have to install it explicitly. I run with Blackbox. Only the necessary parts of GNOME and KDE are pulled in and built. -- Walter Dnes [EMAIL PROTECTED] In linux /sbin/init is Job #1 My musings on technology and security at http://tech_sec.blog.ca -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] chroot
On Monday 27 March 2006 23:21, Boyd Stephen Smith Jr. wrote: Boyd Stephen Smith Jr. [EMAIL PROTECTED] wrote: Yes, that's an option to, although with more than ~768K of ram it's not ideal. Maybe not ideal (especially on 64-bit processors) it is more than possible to address a lot of memory (damn I forget the numbers, I think 64G). Why is that? I thought 32-bit should have no problems addressing 2GB? Yes you can. It will be slower than native 48-bit address modes from 64-bit processors, but not a large overhead at all (and the code mostly stays in cache). You will need to select 3G/1G split to access the full 2GB you have in your system. I have 1.5G and have to use 2G/2G to address all of mine. Plus, with a 64-bit kernel, it'll have access to the 64-bit specific registers. :) That is a much larger benefit than most people give it credit for. Almost double the registers! -- Zac Slade [EMAIL PROTECTED] ICQ:1415282 YM:krakrjak AIM:ttyp99 -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] chroot
On Mon, Mar 27, 2006 at 06:14:32PM -0500, JimD wrote Is is safe to continue to build in a chroot? The handbook say to boot into my new gentoo system. However, I would like to continue to build in the chroot (from another Gentoo 2006.0) until I have X, Fluxbox, Firefox, Postfix, Apache, Mysql and Courier built. This way I will have the minimal I need in a system and can take my time to build Gnome and everyhing else. That's not necessary. I regularly... - start off with a basic text-console-only install - and then I fire up emerge gimp before heading off to work By the time I get home from work, Portage has pulled in and built the approximately 40 packages necessary to get a basic X GUI running with TWM and has built Gimp. rpm-hell... what's that??? Portage rocks!!! The basic X support doesn't show up in /var/lib/portage/world. It's installed as dependancy for various applications. Another cute trick is to emerge bbkeys without first emerge blackbox. blackbox doesn't show up in world either. It's a dependancy for bbkeys. [m3000][root][~] grep -c ^. /var/lib/portage/world 54 ...yes folks, only 54 entries in world for a full-featured desktop with a whole bunch of apps. Like I said, all the dependancies end up as dependancies. -- Walter Dnes [EMAIL PROTECTED] In linux /sbin/init is Job #1 My musings on technology and security at http://tech_sec.blog.ca -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] chroot
Walter Dnes wrote: That's not necessary. I regularly... - start off with a basic text-console-only install - and then I fire up emerge gimp before heading off to work By the time I get home from work, Portage has pulled in and built the approximately 40 packages necessary to get a basic X GUI running with TWM and has built Gimp. rpm-hell... what's that??? Portage rocks!!! The basic X support doesn't show up in /var/lib/portage/world. It's installed as dependancy for various applications. Another cute trick is to emerge bbkeys without first emerge blackbox. blackbox doesn't show up in world either. It's a dependancy for bbkeys. [m3000][root][~] grep -c ^. /var/lib/portage/world 54 ...yes folks, only 54 entries in world for a full-featured desktop with a whole bunch of apps. Like I said, all the dependancies end up as dependancies. Always more than one way to skin a cat. O_O LOL How much thought did you put into that? Dale :-) -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] chroot
On Monday 27 March 2006 17:14, JimD [EMAIL PROTECTED] wrote about '[gentoo-user] chroot': Is is safe to continue to build in a chroot? The handbook say to boot into my new gentoo system. However, I would like to continue to build in the chroot (from another Gentoo 2006.0) until I have X, Fluxbox, Firefox, Postfix, Apache, Mysql and Courier built. This way I will have the minimal I need in a system and can take my time to build Gnome and everyhing else. The only risk I can think of is trying to load kernel modules built against the kernel source in the chroot into the kernel that was loaded off of the livecd. That's not really a risk anyway; it should just fail cleanly. No well-behaving program should try and escape your chroot, so I'm gonna say it's generally safe. There /could/ be issues if you booted from a livecd that has a different CHOST than you are building the system for, but if you are doing something that crazy, I'd hope you'd tell us in your initial email. -- If there's one thing we've established over the years, it's that the vast majority of our users don't have the slightest clue what's best for them in terms of package stability. -- Gentoo Developer Ciaran McCreesh pgptO2hd7PGP9.pgp Description: PGP signature
Re: [gentoo-user] chroot
On Mon, 27 Mar 2006 18:16:31 -0600 Boyd Stephen Smith Jr. [EMAIL PROTECTED] wrote: There /could/ be issues if you booted from a livecd that has a different CHOST than you are building the system for, but if you are doing something that crazy, I'd hope you'd tell us in your initial email. ^ Errr... I actually was going to build an x86 version under my amd64 Gentoo. I was planing on having them on different partitions for testing. Right now I am running Gentoo amd64 though I see some issues with not being able to run some crap proprietary software that is binary only and needs to load binary only 32-bit modules into the kernel. So I was going to have two Gentoo's installed to boot into. One 64-bit and one 32-bit. If I found 32-bit to be just as nice as 64-bit, I was planning on just switching to that. I extracted an i686 stage3 tarball into /mnt/gentoo and I was going to build from there in chroot. Once the initial build is done I was going to stay in chroot and build X, fluxbox and a few other apps I need to be running. Jim -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] chroot
On Monday 27 March 2006 18:30, JimD [EMAIL PROTECTED] wrote about 'Re: [gentoo-user] chroot': On Mon, 27 Mar 2006 18:16:31 -0600 Boyd Stephen Smith Jr. [EMAIL PROTECTED] wrote: There /could/ be issues if you booted from a livecd that has a different CHOST than you are building the system for, but if you are doing something that crazy, I'd hope you'd tell us in your initial email. ^ Errr... I actually was going to build an x86 version under my amd64 Gentoo. I was planing on having them on different partitions for testing. That's fine, but make sure you use linux32 chroot /path/to/chroot /chroot/shell -- that'll fix up your CHOST. How much RAM do you have? 4G, you might just go with a full 32-bit userland and only a 64-bit kernel. -- If there's one thing we've established over the years, it's that the vast majority of our users don't have the slightest clue what's best for them in terms of package stability. -- Gentoo Developer Ciaran McCreesh pgpM2I3tSinGf.pgp Description: PGP signature
Re: [gentoo-user] chroot
On Mon, 27 Mar 2006 18:55:46 -0600 Boyd Stephen Smith Jr. [EMAIL PROTECTED] wrote: How much RAM do you have? 4G, you might just go with a full 32-bit userland and only a 64-bit kernel. I have 2G. Couldn't I do 32-bit userland and 32-bit kernel? The reason for a 32-bit kernel is because I need to compile the Nortel VPN client and it is binary only crap and has 32-bit only binary modules. Well, the code actually uses a module wrapper which I can compile 64-bit but then it barfs trying to link with the 32-bit only modules provided. I have not found any other way to connect to my works VPN than with the Nortel VPN client and even that is tough to get to work. Out of curiosity, how would I do a 32-bit userland with 64-bit kernel? Would I just change CHOST to x86_64 when I compile the kernel? Jim -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] chroot
On Monday 27 March 2006 19:20, JimD [EMAIL PROTECTED] wrote about 'Re: [gentoo-user] chroot': On Mon, 27 Mar 2006 18:55:46 -0600 Boyd Stephen Smith Jr. [EMAIL PROTECTED] wrote: How much RAM do you have? 4G, you might just go with a full 32-bit userland and only a 64-bit kernel. I have 2G. Couldn't I do 32-bit userland and 32-bit kernel? Yes, that's an option to, although with more than ~768K of ram it's not ideal. The reason for a 32-bit kernel is because I need to compile the Nortel VPN client and it is binary only crap and has 32-bit only binary modules. Well, that'll force a 32-bit kernel; do none of the open-source solutions for VPN-ing work? Have you tried them? I was able to get VPN-ing to a Cisco router working even when I was told it just wouldn't work. Out of curiosity, how would I do a 32-bit userland with 64-bit kernel? Would I just change CHOST to x86_64 when I compile the kernel? emerge crossdev crossdev -s2 -t x86_64 make ARCH=x86_64 CROSS_COMPILE=x86_64-pc-linux-gnu- -- If there's one thing we've established over the years, it's that the vast majority of our users don't have the slightest clue what's best for them in terms of package stability. -- Gentoo Developer Ciaran McCreesh pgpA8DOcNVatc.pgp Description: PGP signature
Re: [gentoo-user] chroot
On Monday 27 March 2006 20:43, JimD [EMAIL PROTECTED] wrote about 'Re: [gentoo-user] chroot': On Mon, 27 Mar 2006 19:56:22 -0600 Boyd Stephen Smith Jr. [EMAIL PROTECTED] wrote: Yes, that's an option to, although with more than ~768K of ram it's not ideal. Why is that? I thought 32-bit should have no problems addressing 2GB? I'm not sure about the exact technical reasons, but basically, if you want more than 1G total visible you have to introduce the kernel BIGMEM or HUGEMEM modes; both of which add a software component to each memory access, from what I understand. Without them (and no other kernel hacking) your get a 768m/256m user/kernel split; With BIGMEM this moves up to a 3m/1m user/kernel split; With HUGEMEM I'm not sure if there's a split at all, but it slower than using the hw available in your x86_64 chipset. Using the native, flat 40- or 48-bit addressing of 64-bit mode is much more efficient than any of the kernel hackery that takes place above 768M. Plus, with a 64-bit kernel, it'll have access to the 64-bit specific registers. :) -- If there's one thing we've established over the years, it's that the vast majority of our users don't have the slightest clue what's best for them in terms of package stability. -- Gentoo Developer Ciaran McCreesh pgpqz5bVdxCQZ.pgp Description: PGP signature
Re: [gentoo-user] chroot: cannot run command `bin/bash': Exec format error [SOLVED]
On Friday 24 February 2006 06:56, Bo Andresen [EMAIL PROTECTED] wrote about 'Re: [gentoo-user] chroot: cannot run command `bin/bash': Exec format error [SOLVED]': Actually I guess I could just download the the amd64 livecd, mount it, copy its kernel to the harddrive (already did emerge coldplug) and boot on it. I did, however, find this very interesting so I do wish to compile a 64-bit kernel and see what it takes. Well, when you are already running a 64-bit kernel and have a native gcc, you won't have to use the ARCH and CROSS_COMPILE magic. It just works. The whole process was also enlightening to me. I've never cross-compiled a kernel, but now I know how to have my dual-Opteron box compile the kernel for my Linksys router or my friend's hppa box. make ARCH=x86_64 CROSS_COMPILE=x86_64-pc-linux-gnu- (menuconfig, all, modules_install, etc.) At first when typing make ARCH=x86_64 CROSS_COMPILE=x86_64-pc-linux-gnu- it told me it could not find these files: arch/x86_64/kernel/asm-offsets.c:12:21: asm/pda.h: No such file or directory arch/x86_64/kernel/asm-offsets.c:16:22: asm/ia32.h: No such file or directory [...] make[1]: *** [arch/x86_64/kernel/asm-offsets.s] Error 1 make: *** [prepare0] Error 2 # ls -ld include/asm lrwxrwxrwx 1 root root 10 Feb 24 14:27 include/asm - asm-386 I solved this by: # ln -sfn include/asm-x86_64 include/asm I think this could also be solved with a 'make mrproper'. make install didn't work either Weird. This all did solve the problems. The resulting kernel does indeed boot and it does make it possible to chroot into a 64 bit environment. :D Thanks a lot. This has been very educating. Very good! I'm glad we solved your problem. -- Boyd Stephen Smith Jr. [EMAIL PROTECTED] ICQ: 514984 YM/AIM: DaTwinkDaddy -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] chroot: cannot run command `bin/bash': Exec format error
On Thursday 23 February 2006 00:42, Boyd Stephen Smith Jr. wrote: 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) Will a 64 bit kernel be able to run a 32 bit bash? In order to get a 64 bit kernel a have to set CFLAGS=-march=k8 and set the processor type to K8 in the kernel configuration, right? -- Bo Andresen -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] chroot: cannot run command `bin/bash': Exec format error
On Thursday 23 February 2006 15:31, Bo Andresen [EMAIL PROTECTED] wrote about 'Re: [gentoo-user] chroot: cannot run command `bin/bash': Exec format error': On Thursday 23 February 2006 00:42, Boyd Stephen Smith Jr. wrote: 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) Will a 64 bit kernel be able to run a 32 bit bash? A 64-bit kernel will run 32-bit binaries fine... Um, there may be a needed kernel option though... CONFIG_IA32_EMUL? Anyone? In order to get a 64 bit kernel a have to set CFLAGS=-march=k8 Your CFLAGS in make.conf don't affect your kernel, normally. I don't use genkernel maybe it does some crazy magic like that. and set the processor type to K8 in the kernel configuration, right? Just setting the proper processor type should build your kernel as 64-bit. -- Boyd Stephen Smith Jr. [EMAIL PROTECTED] ICQ: 514984 YM/AIM: DaTwinkDaddy -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] chroot: cannot run command `bin/bash': Exec format error
On Thursday 23 February 2006 22:40, Boyd Stephen Smith Jr. wrote: On Thursday 23 February 2006 15:31, Bo Andresen [EMAIL PROTECTED] wrote about 'Re: [gentoo-user] chroot: cannot run command `bin/bash': Exec format error': On Thursday 23 February 2006 00:42, Boyd Stephen Smith Jr. wrote: livecd gentoo # chroot /mnt/gentoo bin/bash chroot: cannot run command `bin/bash': Exec format error [SNIP] Will a 64 bit kernel be able to run a 32 bit bash? A 64-bit kernel will run 32-bit binaries fine... Um, there may be a needed kernel option though... CONFIG_IA32_EMUL? Anyone? I cannot seem to find any such kernel config option. In order to get a 64 bit kernel a have to set CFLAGS=-march=k8 Your CFLAGS in make.conf don't affect your kernel, normally. Didn't really think so either. It's just that I still get the Exec format error when I try to chroot. Is there a way to very that I really am running a 64 kernel? I don't use genkernel maybe it does some crazy magic like that. I don't either. and set the processor type to K8 in the kernel configuration, right? Just setting the proper processor type should build your kernel as 64-bit. Did do that. Thanks for your replies.. -- Bo Andresen -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] chroot: cannot run command `bin/bash': Exec format error
On Thursday 23 February 2006 15:56, Bo Andresen [EMAIL PROTECTED] wrote about 'Re: [gentoo-user] chroot: cannot run command `bin/bash': Exec format error': Will a 64 bit kernel be able to run a 32 bit bash? A 64-bit kernel will run 32-bit binaries fine... Um, there may be a needed kernel option though... CONFIG_IA32_EMUL? Anyone? I cannot seem to find any such kernel config option. I think these are relevant: $ zgrep -i ia32 /proc/config.gz CONFIG_IA32_EMULATION=y CONFIG_IA32_AOUT=y In order to get a 64 bit kernel a have to set CFLAGS=-march=k8 Your CFLAGS in make.conf don't affect your kernel, normally. Didn't really think so either. It's just that I still get the Exec format error when I try to chroot. Is there a way to very that I really am running a 64 kernel? I believe this tells you: $ uname -m x86_64 and set the processor type to K8 in the kernel configuration, right? Just setting the proper processor type should build your kernel as 64-bit. Did do that. The only thing I can't think of at this point is something from the gentoo cross compile howto from vapier that may or may not apply: If you want to cross compile a kernel, do this: make ARCH=hppa CROSS_COMPILE=hppa2.0-unknown-linux-gnu- So, you may want to configure, make, and install your kernel like: make ARCH=x86_64 menuconfig make ARCH=x86_64 make ARCH=x86_64 install (You don't need a CROSS_COMPILE prefix since gcc should work fine.) -- Boyd Stephen Smith Jr. [EMAIL PROTECTED] ICQ: 514984 YM/AIM: DaTwinkDaddy -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] chroot: cannot run command `bin/bash': Exec format error
On Thursday 23 February 2006 23:33, Boyd Stephen Smith Jr. wrote: On Thursday 23 February 2006 15:56, Bo Andresen [EMAIL PROTECTED] A 64-bit kernel will run 32-bit binaries fine... Um, there may be a needed kernel option though... CONFIG_IA32_EMUL? Anyone? I cannot seem to find any such kernel config option. I think these are relevant: $ zgrep -i ia32 /proc/config.gz CONFIG_IA32_EMULATION=y CONFIG_IA32_AOUT=y I cannot find those options. ~ # zcat /proc/config.gz | grep -i '32\|k8' CONFIG_X86_32=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_MK8=y # CONFIG_SCSI_QLA2322 is not set # CONFIG_SCSI_NSP32 is not set # CONFIG_PCNET32 is not set # CONFIG_USB_SERIAL_MCT_U232 is not set # CONFIG_NLS_CODEPAGE_932 is not set CONFIG_CRYPTO_CRC32C=m CONFIG_CRC32=y CONFIG_LIBCRC32C=m I notice CONFIG_X86_32=y but cannot figure out where to change that in make menuconfig. Typing /X86_32 just gives this as a search result: Symbol: X86_32 [=y] Is there a way to verify that I really am running a 64 kernel? I believe this tells you: $ uname -m x86_64 ~ # uname -m i686 So, you may want to configure, make, and install your kernel like: make ARCH=x86_64 menuconfig make ARCH=x86_64 make ARCH=x86_64 install (You don't need a CROSS_COMPILE prefix since gcc should work fine.) Should I ignore all these warnings? # make ARCH=x86_64 menuconfig scripts/kconfig/mconf arch/x86_64/Kconfig # # using defaults found in .config # .config:90:warning: trying to assign nonexistent symbol X86_ELAN .config:91:warning: trying to assign nonexistent symbol X86_VOYAGER .config:93:warning: trying to assign nonexistent symbol X86_SUMMIT .config:94:warning: trying to assign nonexistent symbol X86_BIGSMP .config:96:warning: trying to assign nonexistent symbol X86_GENERICARCH .config:97:warning: trying to assign nonexistent symbol X86_ES7000 .config:98:warning: trying to assign nonexistent symbol M386 .config:99:warning: trying to assign nonexistent symbol M486 .config:100:warning: trying to assign nonexistent symbol M586 .config:101:warning: trying to assign nonexistent symbol M586TSC .config:102:warning: trying to assign nonexistent symbol M586MMX .config:103:warning: trying to assign nonexistent symbol M686 .config:104:warning: trying to assign nonexistent symbol MPENTIUMII .config:105:warning: trying to assign nonexistent symbol MPENTIUMIII .config:106:warning: trying to assign nonexistent symbol MPENTIUMM .config:107:warning: trying to assign nonexistent symbol MPENTIUM4 .config:108:warning: trying to assign nonexistent symbol MK6 .config:109:warning: trying to assign nonexistent symbol MK7 .config:111:warning: trying to assign nonexistent symbol MCRUSOE .config:112:warning: trying to assign nonexistent symbol MEFFICEON .config:113:warning: trying to assign nonexistent symbol MWINCHIPC6 .config:114:warning: trying to assign nonexistent symbol MWINCHIP2 .config:115:warning: trying to assign nonexistent symbol MWINCHIP3D .config:116:warning: trying to assign nonexistent symbol MGEODEGX1 .config:117:warning: trying to assign nonexistent symbol MCYRIXIII .config:118:warning: trying to assign nonexistent symbol MVIAC3_2 .config:119:warning: trying to assign nonexistent symbol X86_GENERIC .config:121:warning: trying to assign nonexistent symbol X86_XADD .config:125:warning: trying to assign nonexistent symbol X86_WP_WORKS_OK .config:126:warning: trying to assign nonexistent symbol X86_INVLPG .config:127:warning: trying to assign nonexistent symbol X86_BSWAP .config:128:warning: trying to assign nonexistent symbol X86_POPAD_OK .config:129:warning: trying to assign nonexistent symbol X86_CMPXCHG64 .config:131:warning: trying to assign nonexistent symbol X86_INTEL_USERCOPY .config:132:warning: trying to assign nonexistent symbol X86_USE_PPRO_CHECKSUM .config:140:warning: trying to assign nonexistent symbol X86_UP_APIC .config:141:warning: trying to assign nonexistent symbol X86_UP_IOAPIC .config:145:warning: trying to assign nonexistent symbol X86_MCE_NONFATAL .config:146:warning: trying to assign nonexistent symbol X86_MCE_P4THERMAL .config:147:warning: trying to assign nonexistent symbol TOSHIBA .config:148:warning: trying to assign nonexistent symbol I8K .config:149:warning: trying to assign nonexistent symbol X86_REBOOTFIXUPS .config:160:warning: trying to assign nonexistent symbol NOHIGHMEM .config:161:warning: trying to assign nonexistent symbol HIGHMEM4G .config:174:warning: trying to assign nonexistent symbol REGPARM .config:220:warning: trying to assign nonexistent symbol APM .config:231:warning: trying to assign nonexistent symbol PCI_GOBIOS .config:232:warning: trying to assign nonexistent symbol PCI_GOMMCONFIG .config:233:warning: trying to assign nonexistent symbol PCI_GODIRECT .config:234:warning: trying to assign nonexistent symbol PCI_GOANY .config:1405:warning: trying to assign nonexistent symbol X86_FIND_SMP_CONFIG .config:1406:warning: trying to assign nonexistent symbol X86_MPPARSE .config:1459:warning: trying
Re: [gentoo-user] chroot: cannot run command `bin/bash': Exec format error
On Friday 24 February 2006 01:12, Bo Andresen wrote: On Friday 24 February 2006 00:52, Boyd Stephen Smith Jr. wrote: So, it's starting from your i686 config, and trying to use it to assign as many symbols as possible to the new x86_64 kernel. Some of the symbols just won't exist. When you 'make ARCH=x86_64 menuconfig', can you find the IA32 configuration options? Indeed I can. Thanks. :) Unfortunately, however, it doesn't compile.. :( # make ARCH=x86_64 CHK include/linux/version.h SPLIT include/linux/autoconf.h - include/config/* CC arch/x86_64/kernel/asm-offsets.s cc1: error: code model `kernel' not supported in the 32 bit mode make[1]: *** [arch/x86_64/kernel/asm-offsets.s] Error 1 make: *** [prepare0] Error 2 Going to bed now. Will look at it tomorrow. -- Bo Andresen -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] chroot: cannot run command `bin/bash': Exec format error
On Thursday 23 February 2006 18:16, Bo Andresen [EMAIL PROTECTED] wrote about 'Re: [gentoo-user] chroot: cannot run command `bin/bash': Exec format error': On Friday 24 February 2006 01:12, Bo Andresen wrote: On Friday 24 February 2006 00:52, Boyd Stephen Smith Jr. wrote: When you 'make ARCH=x86_64 menuconfig', can you find the IA32 configuration options? Indeed I can. Thanks. :) Unfortunately, however, it doesn't compile.. :( # make ARCH=x86_64 CHK include/linux/version.h SPLIT include/linux/autoconf.h - include/config/* CC arch/x86_64/kernel/asm-offsets.s cc1: error: code model `kernel' not supported in the 32 bit mode make[1]: *** [arch/x86_64/kernel/asm-offsets.s] Error 1 make: *** [prepare0] Error 2 Going to bed now. Will look at it tomorrow. Oy, oy, oy. No wonder my friends would rather fsck with the amd64 live cd (that panics on boot unless the BIOS settings are /really/ special) than start off in 32-bit land. Anyway, I think what you probably need to do is append -m64 to your CFLAGS. Try: make ARCH=x86_64 CFLAGS=-m64 I'll go fiddle a bit, too. I'm already running a 64-bit userland, but I have an i686 cross-compiler installed, maybe I can iron out think kinks in the process for ya. -- Boyd Stephen Smith Jr. [EMAIL PROTECTED] ICQ: 514984 YM/AIM: DaTwinkDaddy -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] chroot: cannot run command `bin/bash': Exec format error
On Thursday 23 February 2006 18:32, Boyd Stephen Smith Jr. [EMAIL PROTECTED] wrote about 'Re: [gentoo-user] chroot: cannot run command `bin/bash': Exec format error': Try: make ARCH=x86_64 CFLAGS=-m64 Nah, don't. It won't help, the kernel's Makefile doesn't pay attention to CFLAGS, it sets up it's own based on your .config. While I didn't get the same error as you, I see definite I'm trying to compile 64-bit assembly into 32-bit binaries-style errors when compiling with: make ARCH=x86_64 CROSS_COMPILE=i686-pc-linux-gnu- make ARCH=x86_64 CROSS_COMPILE=i686-pc-linux-gnu- CFLAGS=-m32 make ARCH=x86_64 CROSS_COMPILE=i686-pc-linux-gnu- CFLAGS=-m64 and make ARCH=x86_64 CROSS_COMPILE=i686-pc-linux-gnu- CC=gcc -m32 However, I /was/ able to convince the kernel to build with make ARCH=x86_64 CROSS_COMPILE=i686-pc-linux-gnu- CC=gcc -m64 although I didn't see if that would boot. So, why don't you give it a go with: make ARCH=x86_64 CC=gcc -m64 menuconfig make ARCH=x86_64 CC=gcc -m64 make ARCH=x86_64 CC=gcc -m64 modules_install make ARCH=x86_64 CC=gcc -m64 install and let me know how it goes. -- Boyd Stephen Smith Jr. [EMAIL PROTECTED] ICQ: 514984 YM/AIM: DaTwinkDaddy -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] chroot: cannot run command `bin/bash': Exec format error
On Friday 24 February 2006 01:56, Boyd Stephen Smith Jr. wrote: So, why don't you give it a go with: make ARCH=x86_64 CC=gcc -m64 menuconfig make ARCH=x86_64 CC=gcc -m64 make ARCH=x86_64 CC=gcc -m64 modules_install make ARCH=x86_64 CC=gcc -m64 install and let me know how it goes. linux # make ARCH=x86_64 CC=gcc -m64 clean CLEAN .tmp_versions # make ARCH=x86_64 CC=gcc -m64 menuconfig HOSTCC scripts/basic/fixdep HOSTCC scripts/basic/split-include HOSTCC scripts/basic/docproc HOSTCC scripts/kconfig/conf.o HOSTCC scripts/kconfig/kxgettext.o HOSTCC scripts/kconfig/mconf.o HOSTCC scripts/kconfig/zconf.tab.o HOSTLD scripts/kconfig/mconf HOSTCC scripts/lxdialog/checklist.o HOSTCC scripts/lxdialog/inputbox.o HOSTCC scripts/lxdialog/lxdialog.o HOSTCC scripts/lxdialog/menubox.o HOSTCC scripts/lxdialog/msgbox.o HOSTCC scripts/lxdialog/textbox.o HOSTCC scripts/lxdialog/util.o HOSTCC scripts/lxdialog/yesno.o HOSTLD scripts/lxdialog/lxdialog scripts/kconfig/mconf arch/x86_64/Kconfig # # using defaults found in .config # *** End of Linux kernel configuration. *** Execute 'make' to build the kernel or try 'make help'. via linux # make ARCH=x86_64 CC=gcc -m64 CHK include/linux/version.h UPD include/linux/version.h SPLIT include/linux/autoconf.h - include/config/* CC arch/x86_64/kernel/asm-offsets.s cc1: error: code model `kernel' not supported in the 32 bit mode cc1: sorry, unimplemented: 64-bit mode not compiled in make[1]: *** [arch/x86_64/kernel/asm-offsets.s] Error 1 make: *** [prepare0] Error 2 # gcc --version gcc (GCC) 3.3.5-20050130 (Gentoo 3.3.5.20050130-r1, ssp-3.3.5.20050130-1, pie-8.7.7.1) Copyright (C) 2003 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -- Bo Andresen -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] chroot: cannot run command `bin/bash': Exec format error
On 2/22/06 5:03 PM, Bo Andresen [EMAIL PROTECTED] wrote: Hi 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? When I get to step 6a (chrooting) http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=1chap=6#doc_cha p1 I get the following error: livecd gentoo # chroot /mnt/gentoo bin/bash chroot: cannot run command `bin/bash': Exec format error I've seen that when chrooting into 64-bit environment from a 32-bit kernel. You cannot boot from the x86 minimal and use an amd64 stage file. You need the amd64 boot cd. 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. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] chroot: cannot run command `bin/bash': Exec format error
2006/2/23, Bo Andresen [EMAIL PROTECTED]: Hi Hi, 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? When I get to step 6a (chrooting) http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=1chap=6#doc_chap1 I get the following error: livecd gentoo # chroot /mnt/gentoo bin/bash chroot: cannot run command `bin/bash': Exec format error You'll have to boot on a 64bits liveCD if you want to chroot into a 64bits environment. Regards, Boris. -- Bo Andresen -- gentoo-user@gentoo.org mailing list -- Quiconque me parle de Dieu en veut à ma bourse ou à ma liberté. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] chroot: cannot run command `bin/bash': Exec format error
On Wednesday 22 February 2006 17:03, Bo Andresen [EMAIL PROTECTED] 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. [EMAIL PROTECTED] ICQ: 514984 YM/AIM: DaTwinkDaddy -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] chroot: cannot run command `bin/bash': Exec format error
On Thursday 23 February 2006 00:42, Boyd Stephen Smith Jr. wrote: 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) Thanks for explaining that. 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. Is that all it takes? I'll definitely try that then. Thanks again. -- Bo Andresen -- gentoo-user@gentoo.org mailing list
