On 1 August 2014 21:32:54 CEST, Neil Bothwick <n...@digimed.co.uk> wrote: >On Fri, 01 Aug 2014 14:07:08 +0100, Peter Humphrey wrote: > >> I run a couple of chroots on this box to build packages for other >boxes >> on the LAN. So far, I haven't worked out what I should >> populate /etc/mtab with in each chroot. Is it enough to "grep >> ext4 /etc/mtab > /mnt/chroot/etc/mtab"? That catches all the physical >> partitions, but I imagine I need to add some /proc, /sys and /dev >> entries as well, but is there a simple formula for doing this? > >Do you need anything in mtab in the chroot? I've been using chroots to >build packages for slower machines for years and /etc/mtab has always >been empty or non-existent, with no problems. df gets the hump when run >inside the chroot, but the package building works fine.
You don't need anything in mtab. I've been building packages for multiple machines for years. Never had any issues using them to update the rest. Only have issues with fetch restricted files blocking the use of a fully automated system. -- Joost -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
