21 Mar
2005
21 Mar
'05
7:36 p.m.
jjbenham(a)chicagoguitar.com (Jeremiah Benham) writes:
On Mon, Mar 21, 2005 at 10:11:48AM -0800, Noah Roberts
wrote:
Not really. You usually solve this issue by either creating a 64-bit
chroot in a 32-bit base system or a 32-bit chroot in a 64-bit base
system. These chroots can be very useful since some apps just don't
work in 64-bit mode yet. We are using this method at work to make
32-bit commercial apps run on our 64-bit x84_64 machines, and it
works very well. I wouldn't call it confusing. Its actually very logical
as soon as you start to grasp the chroot concept.
--
CYa,
Mario | Debian Developer <URL:http://debian.org/>
.''`. | Get my public key via finger mlang(a)db.debian.org
: :' : | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44
`. `'
`-
I have an amd64 running in 64 bit mode. There
honestly isn't much
reason to get a 64 if you are going to run in 32 bit mode...They are
way more expensive than the 32 bit counterparts and don't offer enough
extra in 32 bit mode.
I also considered going to 64 bit. What flavor of linux are you using? I
know you can't run 32 bit and 64 bit applications on the same machine.
That is unless you have both the 32 bit and 64 bit libc installed. That
seems confusing as if you are just asking for trouble.