On Thu, 2019-07-25 at 21:23 -0500, Martin McCormick wrote: > Tixy <t...@yxit.co.uk> writes: > > I've used 'schroot' in the past for this sort of thing, let's you > > configure what to mount and I believe either defaults or has > > examples > > for the common things you're likely to need like /dev and /proc. I > > don't remember the details as it's been quite some years since I > > used > > it. > Thanks for this information. I have installed schroot > as this seems to be the missing link I didn't know about. > > I knew one had to have all the resources turned on so to > speak and it looks like schroot makes getting it right in this > century much more likely.
This may, or may not, be useful to the sort of work you do, but I also used it to run a Debian install for a different CPU, in my case an Arm Debian install running on my x86 PC. I found that getting a PC to emulate an Arm CPU was a lot quicker and more convenient than doing it on the Arm single board computers I had. In such a setup, whilst the PC is having to do lot's of extra works to emulate Arm instructions for running user code, you are still using the PC's kernel, so disk i/o is likely an order of magnitude or more faster, and you have available all the PC's RAM, which is probably a lot more than the ARM board's. If I remember correct, getting such a setup working was quite straight forward. To be able to run foreign binaries I think you just need to install package qemu-user-static and it's recommendation binfmt-support, and after a quick google just now [1], there is probably an emulation binary from that which needs copying into the Arm chroot. [1] https://wiki.debian.org/RaspberryPi/qemu-user-static -- Tixy