[buildd-tools-devel] Bug#762597: Bug#762597: /var/lib/schroot/mounts should be in /var/run for --one-file-system

[Ian Jackson]

Roger Leigh writes ("Re: [buildd-tools-devel] Bug#762597: /var/lib/schroot/mounts should be in /var/run for --one-file-system"):
> Hmm, this is an interesting problem.  Your proposed solution would
> certainly provide a boundary to stop traversal, but I'm not sure it
> would help in all situations, since e.g. for file-based chroots we
> unpack them under /var/lib/schroot.  Putting the mounts themselves
> under /var/run should be safe enough though.

Yes, you're right, I hadn't properly considered file-based chroots.  I
don't know how to fix those.  But as you say, my proposal at least
won't hurt them.

> In recent years, I've put the chroot directories in btrfs subvolumes,
> where the subvolumes have a separate devid, and had that as a
> separate filesytem (don't trust it enough for the rootfs).  Currently
> implementing support for ZFS snapshots.

Right.

> I'll need to do some testing of this to make sure it doesn't
> break anything.  If you have any further thoughts or ideas, please
> do let me know!

Thanks for your attention!

Regards,
Ian.