Re: chroot and ia32libs combined
On Wed, 2006-09-06 at 13:45 -0500, Seb wrote:
> On Mon, 04 Sep 2006 23:38:41 -0500, Owen Heisler wrote:
> > In that HOWTO, _I_ would skip 1.3, 1.4, and 1.5. The only changes I
> > make to the real system is to /etc/fstab.
>
> Yes, this is what I really felt like doing, since I had the ia32-libs
> package. So I went ahead and skipped those instructions and added this to
> fstab:
>
> ,-----[ tail -n 5 /etc/fstab ]
> |
> | # Chroot mounts
> | /home /var/chroot/sid-ia32/home none bind 0 0
> | /tmp /var/chroot/sid-ia32/tmp none bind 0 0
> | proc /var/chroot/sid-ia32/proc proc defaults 0 0
> `-----
>
> Installed firefox, mplayer, w32codecs, realplayer (last 3 from
> Marillat's repos). I haven't tested mplayer yet, but realplayer has quite
> jumpy video (not smooth), which got me thinking about the /dev mount. Any
> further ideas on that welcome.
Sorry, I can't help you there. Perhaps someone else...
> Another question that nobody seems to mention in the various how-tos is
> what happens if you have say both the same 64-bit app in the main system
> and 32-bit app in the chroot? Because /home is mounted in both systems,
> each version will be messing with each other's config stuff, won't it?
> Say things like ~/.mozilla would change and probably get messed up by
> changes made by each version of firefox. How is that handled?
I have the Etch version of Firefox installed on the 64-bit side, and the
Sid version of Firefox installed in the chroot. I use the 64-bit one
except for when I want to be able to use Flash, then I run the 32-bit
one. Every time I switch, it runs the extension compatibility wizard.
Luckily, the versions are very close, so nothing is ever changed (else
it would just disable certain extensions, I think). So I guess it isn't
"handled"; the apps just do as they would across version changes.
Reply to: