Hi all,
I looked at the source code for schroot, and found that a mount command was
being forked/exec'd for every line in the fstab file. I was able to get ro
bind mounts working with two entries in the fstab file. Examples:
/sandboxes/rev3disks/platform /home/Platformnone
On Sat, Feb 22, 2014 at 11:42:11AM +0100, Ralf Jung wrote:
this would indeed be a great feature. It would also be interesting to be
able to make the chroot root mount (which is not controlled by the
fstab file) read-only.
I recall that there's a reason why ro,bind doesn't work directly--you
Hi,
I recall that there's a reason why ro,bind doesn't work
directly--you have to do two bind mounts to get it properly
read-only. Is that correct? What's the recommended sequence to make
this work properly? If we see ro and bind in the mount options,
we can probably special-case it; but
Hi,
this would indeed be a great feature. It would also be interesting to be
able to make the chroot root mount (which is not controlled by the
fstab file) read-only. Furthermore, there are additional interesting
flags that can be set for bind mounts, but only with a remount - think
of nosuid,
Package: schroot
Version: 1.4.21-1+b1
Severity: wishlist
Linux supports read-only bind-mounts, but they can only be made
read-only after bind-mounting, not during.
i.e.
mount --bind /foo /bar
mount -o remount,ro /bar
I hacked support for this into my schroot installation by running the
following
5 matches
Mail list logo
