On Tue, 30 Jan 2007 18:22:56 +1100 Russell Butler <[EMAIL PROTECTED]> dijo:
> Sorry for more noise/bandwidth but I think > http://alioth.debian.org/docman/view.php/30192/21/debian-amd64-howto.html > > was the clincher for me. OOo even rates a mention. Thanks for the suggestion. Been there, done that, wearing the t-shirt. Also, that link is rather old; there are much easier ways to install a 32-bit chroot environment today. If you have 64-bit Ubuntu you can just install it with Synaptic. And then all you need is to learn how to run the Synaptic in the 32-bit chroot environment. Everything you install with the chroot Synaptic will install programs inside the chroot environment. I installed a 32-bit chroot all the way back in Ubuntu Hoary in order to get a few things to run. After upgrading to Dapper I was thrilled to find that I could get everything running that I needed without the chroot environment. In my experience chroot was a major PITA. For example, I was running Firefox in chroot, but when I took my laptop to the university it needed to change to a different DNS server. The wireless connector was in the 64-bit world, but Firefox was in the 32-bit world. I had to symlink the config file for DNS servers from the 64-bit world to the 32-bit world, and manually run the command to update the link every time I moved from home to the university and again when I moved back. And that is just one example of the constant hassles I encountered with running things in a 32-bit chroot environment. Bear in mind that the whole original purpose of chroot was to create an isolated area that malware could not access. The fact that some people are now using it to create a 32-bit version of the operating system within the 64-bit OS doesn't change the fact that communicating between the "real" 64-bit OS and the 32-bit chroot environment requires constant manual efforts. I'll pass on the 32-bit chroot option. Yes, I really, really need drag and drop to work. But considering that out of hundreds of thousands of 64-bit OOo users I am one of maybe 50 or 100 worldwide who are experiencing this problem, I am convinced that I can fix it. Right now I am betting that it is a library that is buggy or needs to be reinstalled. If I keep poking at things I'm sure I'll find it eventually, especially if people here keep offering suggestions. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
