| 1 |
On Fri, 01 Aug 2014 14:07:08 +0100, Peter Humphrey wrote: |
| 2 |
|
| 3 |
> I run a couple of chroots on this box to build packages for other boxes |
| 4 |
> on the LAN. So far, I haven't worked out what I should |
| 5 |
> populate /etc/mtab with in each chroot. Is it enough to "grep |
| 6 |
> ext4 /etc/mtab > /mnt/chroot/etc/mtab"? That catches all the physical |
| 7 |
> partitions, but I imagine I need to add some /proc, /sys and /dev |
| 8 |
> entries as well, but is there a simple formula for doing this? |
| 9 |
|
| 10 |
Do you need anything in mtab in the chroot? I've been using chroots to |
| 11 |
build packages for slower machines for years and /etc/mtab has always |
| 12 |
been empty or non-existent, with no problems. df gets the hump when run |
| 13 |
inside the chroot, but the package building works fine. |
| 14 |
|
| 15 |
|
| 16 |
-- |
| 17 |
Neil Bothwick |
| 18 |
|
| 19 |
Every morning is the dawn of a new error... |
Archives