1 |
On Sun, 20 Dec 2009 14:30:57 +0000 (UTC), Duncan <1i5t5.duncan@×××.net> |
2 |
wrote: |
3 |
> Just in case anybody ever wondered, there's nothing stopping someone |
4 |
from |
5 |
> doing the 32-bit chroot (as in the gentoo/amd64 documentation) on a |
6 |
> no-multilib system. In fact, it's a cleaner way to do it, since the two |
7 |
|
8 |
> systems will be fully separated, no 32-bit stuff on the 64-bit side, and |
9 |
|
10 |
> no 64-bit stuff on the 32-bit side, plus no generic 32-bit binary-only |
11 |
> emul-linux-x86 libs to worry about. |
12 |
|
13 |
It's all about options. I find it cleaner to pursue the true multilib (as |
14 |
implemented in the multilib overlay) than to have to OSes just to run a few |
15 |
apps. That feels like having a Windows installation just to run a couple of |
16 |
games: hackish at best. But, as said, it's just a matter of opinions. |
17 |
There's no absolute best option, it depends on your tastes. This way you |
18 |
can get things like true DRM working no matter what kind of binary you are |
19 |
using. |
20 |
|
21 |
> The one caveat is to make sure you have the kernel set to handle 32-bit |
22 |
> also (in menuconfig, under executable file formats, ia32 emulation), but |
23 |
|
24 |
> that's needed for grub-static anyway, I believe, so no big deal there. |
25 |
|
26 |
However you don't need that for grub. You can install grub to your MBR |
27 |
from a livecd and then forget about it. Unlike lilo, grub doesn't need to |
28 |
be reinstalled each time you add a new kernel to your menu. |
29 |
|
30 |
-- |
31 |
Jesús Guerrero |