Re: Instead of chroot for i386
On Fri, 11 Mar 2005 11:26:02 -0700, Bob Proulx wrote: /emul/ia32-linux/usr/lib in my ldconfig, and running openoffice works fine without having to chroot or anything. Running it outside the chroot needs a symlink. See this thread. http://lists.debian.org/debian-ia64/2003/03/msg00012.html But it works fine with the symlink in place. Thanks a lot, Bob! That's a very insightful post -- just what I was hoping to achieve... save me tons of trials and errors. How about david's tip on 'no-need-symlinks'? ,- | If you use /emul/ia32-linux/ instead of /woody-ia32, you don't need | any of this symlink magic. For x86 apps, the kernel will | automatically check for a file in /emul/ia32-linux before trying to | open it starting from root. (Details are in my book on page 464.) | `- Do you have new updates on that? Have you run a strace to verify? thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Instead of chroot for i386
Alexander Rapp wrote: Tong wrote: Say my i386 Debian Sarge is mounted on /os/deb32. Then, having configured the ldconfig, just launch ooffice (or any other tools not available in amd64 yet) as /os/deb32/usr/bin/ooffice -- no bind mount, no dchroot, no various sym-links. Running ooffice outside the chroot should work fine. It's the same principle as the ia32-libs package. I have ia32-libs (which isn't even a full chroot) installed and /emul/ia32-linux/lib and /emul/ia32-linux/usr/lib in my ldconfig, and running openoffice works fine without having to chroot or anything. Running it outside the chroot needs a symlink. See this thread. http://lists.debian.org/debian-ia64/2003/03/msg00012.html But it works fine with the symlink in place. Bob signature.asc Description: Digital signature
Re: Instead of chroot for i386
Tong wrote: Well, I was thinking to abolish the chroot entirely. Say my i386 Debian Sarge is mounted on /os/deb32. Then, having configured the ldconfig, just launch ooffice (or any other tools not available in amd64 yet) as /os/deb32/usr/bin/ooffice -- no bind mount, no dchroot, no various sym-links. theoretically, should it work? Running ooffice outside the chroot should work fine. It's the same principle as the ia32-libs package. I have ia32-libs (which isn't even a full chroot) installed and /emul/ia32-linux/lib and /emul/ia32-linux/usr/lib in my ldconfig, and running openoffice works fine without having to chroot or anything. -- Alexander Rapp -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Instead of chroot for i386
Well, that's really encouraging, thanks a lot for the post! On Sun, 06 Mar 2005 12:15:05 +0300, Alexander Rapp wrote: Tong wrote: Well, I was thinking to abolish the chroot entirely. Say my i386 Debian Sarge is mounted on /os/deb32. Then, having configured the ldconfig, just launch ooffice (or any other tools not available in amd64 yet) as /os/deb32/usr/bin/ooffice -- no bind mount, no dchroot, no various sym-links. theoretically, should it work? Running ooffice outside the chroot should work fine. It's the same principle as the ia32-libs package. I have ia32-libs (which isn't even a full chroot) installed and /emul/ia32-linux/lib and /emul/ia32-linux/usr/lib in my ldconfig, and running openoffice works fine without having to chroot or anything. -- Alexander Rapp -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Instead of chroot for i386
Tong wrote: My understand that the solo reason for the i386 chroot to exist is to avoid messing up 64bit and 32bit libraries. Is that so? Nope, it's because debian's packaging system isn't intelligent enough to handle two architectures in the same installation. Linux can handle 32 and 64-bit libraries side by side at the same time just fine. I'm running an i386 Debian Sarge perfectly well, and I have sufficient spare partitions to test AMD64 Sarge. In this case, is it ok just to append my i386 tool paths to the PATH and add i386 library paths to ldconfig? If you want, but I'd mount the whole tree and use it as a chroot. For other reasons, you're going to want to bind mount certain portions of your 64bit install into the 32bit one or vice-versa, depending on which one is master. To me, theoretically it should work, and it is much much simpler than doing a brand new i386 chroot install. I don't think so. The chroot'd install is really a slave install and doesn't need to be a full, bootable debian install (nor do you really want it to be), Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Instead of chroot for i386
The quick answer: It doesn't matter whether the i386 is inside, outside, or next to the amd64 chroot. I've got them next to each other, just for symmetry. Tong wrote: My understand that the solo reason for the i386 chroot to exist is to avoid messing up 64bit and 32bit libraries. Is that so? Yes. Well, mostly. I'm running an i386 Debian Sarge perfectly well, and I have sufficient spare partitions to test AMD64 Sarge. In this case, is it ok just to append my i386 tool paths to the PATH and add i386 library paths to ldconfig? Sure. The easy way to do that is to mount your i386 filesystem tree inside the amd64 filesystem tree and refer to it as a chroot thereafter. To me, theoretically it should work, and it is much much simpler than doing a brand new i386 chroot install. Nonono ... Whatever you do, don't do another install if you've got a working one. Since nobody says so, I guess I might be missing something here. Please comment. Thanks Nope. Most people these days have amd64 as their first installation. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Instead of chroot for i386
Thanks for the reply, wow, that IS fast. On Sat, 05 Mar 2005 13:30:52 -0800, Alex Perry wrote: I'm running an i386 Debian Sarge perfectly well, and I have sufficient spare partitions to test AMD64 Sarge. In this case, is it ok just to append my i386 tool paths to the PATH and add i386 library paths to ldconfig? Sure. The easy way to do that is to mount your i386 filesystem tree inside the amd64 filesystem tree and refer to it as a chroot thereafter. Well, I was thinking to abolish the chroot entirely. Say my i386 Debian Sarge is mounted on /os/deb32. Then, having configured the ldconfig, just launch ooffice (or any other tools not available in amd64 yet) as /os/deb32/usr/bin/ooffice -- no bind mount, no dchroot, no various sym-links. theoretically, should it work? thank -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Instead of chroot for i386
Tong [EMAIL PROTECTED] writes: Hi, My understand that the solo reason for the i386 chroot to exist is to avoid messing up 64bit and 32bit libraries. Is that so? The reason for a chroot is so you can run apt-get and dpkg. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Instead of chroot for i386
On Sat, 05 Mar 2005 23:21:35 +0100, Goswin von Brederlow wrote: My understand that the solo reason for the i386 chroot to exist is to avoid messing up 64bit and 32bit libraries. Is that so? The reason for a chroot is so you can run apt-get and dpkg. Can I chroot into my existing system and run apt-get without any bad side-effects? How about running ooffice outside chroot? please answer in the previous thread. thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Instead of chroot for i386
Tong [EMAIL PROTECTED] writes: On Sat, 05 Mar 2005 23:21:35 +0100, Goswin von Brederlow wrote: My understand that the solo reason for the i386 chroot to exist is to avoid messing up 64bit and 32bit libraries. Is that so? The reason for a chroot is so you can run apt-get and dpkg. Can I chroot into my existing system and run apt-get without any bad side-effects? If it has proc mounted. How about running ooffice outside chroot? please answer in the previous thread. doubtfull. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
