Utilizing a Linux LiveCD, it's simple to "rescue" a given Linux box that has had it's root password changed or forgotten. Of course, this also creates a security risk in business-critical machines. If an employee were to use this on a business server to gain root access, the business would be in some form of trouble (provided the IT Department doesn't know what they're doing).

...At this point you should have a 32 bit environment setup with synaptic setup. When you run synaptic32 from your main environment it will chroot execute it and all installations will be made to your 32 bit environment. If you want to be able to easily launch 32 bit chroot apps from your 64 bit environment symlink the app name to /usr/local/bin/do_dchroot.

Installing Apache in a chroot jail does not make Apache itself any more secure. Rather, it serves to restrict the access of Apache and its child processes to a small subset of the filesystem. The advantage in chrooting a process is not in preventing a breakin, but rather in containing a potential threat.

Before deciding whether you need to chroot your Web server you should consider the advantages and disadvantages of such a setup.

One way - they say - is to install the ia32-libs, but I wanted to be all clean about it and use the arguably harder ‘chroot' method. This way, one can achiev a modular, easily upgradeble system. Both 64- and 32- bit apps and separated from each other, and all users can - compeletly transparently - call the 32-bit apps from within their 64-bit text consoles and DEs.