On Thu, 2006-02-02 at 10:13 -0700, Alex Williamson wrote: > Your best bet is probably an ia32 chroot, that way you have all the > apps and library issues will take care of themselves. Trying to satisfy > all the library requirements for big apps like this will just make a > mess of your filesystem. Also note that ia32 binary support is a > compatibility feature, not a performance feature of ia64. Yeah. In other words, "It's dog slow." From what I've read, a good software emulator/IA32->64 JIT outperforms the IA32 compatibility silicon (but still isn't what you'd call fast), and the next versions of IA64 won't include IA32 hardware support at all. If you need to run a lot of 32-bit i386 applications, I recommend using a real Xeon or Opteron server. If it's just a few apps that aren't performance critical, the chroot should work well enough. An annoying thing about chroots though, is that if its running Gnome or KDE apps, they tend to launch a pile of daemons doing duplicate work. You can do some wacky stuff with mount --bind to get the same /tmp and $HOME directories mounted inside the chroot, but then you can end up with mixed 32-bit/64-bit Gnome daemons running, and if anybody relies on the system byte ordering or word size in the socket communications, oh my, the pain. Maybe someone else has a good link explaining the best ways to get GUI apps running in a chroot? -- Zan Lynx <zlynx@acm.org>
Attachment:
signature.asc
Description: This is a digitally signed message part