Which Directory Service do you use for your network?
None NIS LDAP LDAP + Kerberos Samba Active Directory eDirectory other ( 735 votes ~ 14 comments )
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 Using proprietary i386 apps on an amd64 system:
#4 Re: Using proprietary i386 apps on an amd64 system Posted by dkg (216.254.xx.xx) on Fri 15 Jun 2007 at 06:41 Yes, thanks for your article, neofpo! I was actually about to travel down the chroot route before i figured out the ia32-libs approach for a client. I figured i'd write up this approach before i forgot it ;) I think one of the reasons that the proprietary software world hasn't picked up 64-bit computing as fast is that porting is hard, and there aren't many folks who do it well. In particular, it's a field of software engineering where it helps to have free and open communication between very different groups of specialists (specialists on the software being ported, specialists on the original architecture, and specialists on the target architecture). Since the free software world already does free and open communication quite well (and has tons of experience with porting), we've had a leg up on the proprietary world for this transition. Intel actually did develop a 64-bit arch (the Itanium architecture, or ia64), but it was released earlier (when there was less need); it was more expensive; and i think it was not as backward-compatible as the amd64 chips (though i'm not sure on the details). It has been rejected/ignored even more egregiously than amd64 has been. Of course, you can still run debian on ia64. ia32-libs appears to be built for it as well, but i've never tried it.
I think one of the reasons that the proprietary software world hasn't picked up 64-bit computing as fast is that porting is hard, and there aren't many folks who do it well. In particular, it's a field of software engineering where it helps to have free and open communication between very different groups of specialists (specialists on the software being ported, specialists on the original architecture, and specialists on the target architecture). Since the free software world already does free and open communication quite well (and has tons of experience with porting), we've had a leg up on the proprietary world for this transition.
Intel actually did develop a 64-bit arch (the Itanium architecture, or ia64), but it was released earlier (when there was less need); it was more expensive; and i think it was not as backward-compatible as the amd64 chips (though i'm not sure on the details). It has been rejected/ignored even more egregiously than amd64 has been.
Of course, you can still run debian on ia64. ia32-libs appears to be built for it as well, but i've never tried it.
Posting Format:
Inappropriate comments will be removed.
Some help on entry formatting is available
Username:
Password:
[ Advanced Login ]
Register Account
