Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 23, 2013
An "enum" for Python 3
An unexpected perf feature
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
Debian does not "require" chroots to run 32-bit packages. It's an option that the Debian developers seem to prefer, but they certainly don't force anybody to do things that way.
Debian on AMD64
Posted Dec 9, 2004 21:47 UTC (Thu) by anton (guest, #25547)
So around January the pure64 port that was not intended to support the
i386 architecture gained impetus. And of course there you have to use
tricks or chroot to run i386 (32-bit) binaries.
Technically, the difference is that other distributions put the 64-bit
libraries in /lib64 and 32-bit libraries in /lib , while Debian pure64
puts the 64-bit libraries in /lib. Now if you want to install a
32-bit library on pure64, it will likely collide with the 64-bit
library in the same place. That's why Debian users would consider
that dirty, and recommend using a chrooted 32-bit environment instead.
As for me, I bought an Athlon64 a little over a year ago, and wanted
to install Debian. After failing to install biarch (I deserved that,
I wanted to cut corners:-), I saw that Debian was headed in the pure64
direction, decided that I wanted to run 32-bit binaries without
chroot, and installed Fedora Core 1 in March, and have been pretty
happy with that since.
Posted Dec 12, 2004 3:08 UTC (Sun) by interalia (subscriber, #26615)
http://raw.no/debian/amd64-multiarch-3 (current multiarch proposal)
http://www.linuxbase.org/~taggart/multiarch.html (description of what the filesystem layout would look like)
http://lists.debian.org/debian-amd64/2004/07/msg00175.html (biarch vs multiarch)
http://lists.debian.org/debian-amd64/2004/05/msg00285.html (another succinct but informative thread about pure64/biarch/multiarch)
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds