You are not currently logged in. If you do not have a user account then please consider creating one and logging in before you post your comment. This will allow you to track replies to your comment, and take part in the site much more freely.

To add your comment, fill in all the boxes below and then preview it to make sure you're happy with the way that it looks.

This is the comment you were replying to, attached to the article Multi-arch installation: x86 and amd64:

#5 Re: Multi-arch installation: x86 and amd64 Posted by undefined (192.91.xx.xx) on Wed 16 May 2007 at 22:38 maybe grimoire didn't choose the right word with "filesystem", maybe "namespace" would have been better, but his intended meaning was conveyed (at least to me), and he is correct: your approach requires multiple filesystem namespaces. you have to essentially maintain two distinct systems with dchroot as the gatekeeper between the two. a true multiarch solution will not require that. as you have admitted, that's problematic as most applications, menu entries, etc do not expect to call dchroot to exec an application. and to access amd64 applications from the ia32 chroot, can you not install dchroot in the ia32 chroot and specify the amd64 chroot as /amd64? for userland virtualization (which is what you are doing in your oracle example) i use vserver.

Inappropriate comments will be removed.

Username:

Password:

[ Advanced Login ]

Register Account