On Sun, Sep 02, 2012 at 06:54:12PM +1000, Adam Baxter wrote:
> Permissions could probably be maintained by a dotfile somewhere in the
> chroot, then a git hook to restore permissions when needed.
With schroot 1.6, we have a "custom" chroot type and user-definable
keys which would enable anyone who
Permissions could probably be maintained by a dotfile somewhere in the
chroot, then a git hook to restore permissions when needed.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
I forgot that Git does not store permissions apart from the owner's
+x bit, and thus, a Git-managed chroot will not have any
ug+s,o+t bits set, nor will it restore groups. /home and /tmp appear
to be alright, but that's because they're bind-mounted.
[EMAIL PROTECTED]:~$ ls /etc/shadow -l
-rw-r--r-
Package: schroot
Version: 1.1.6-1
Severity: wishlist
Please find attached the files 05git and a diff to 00check, which
together should enable Git to be used as chroot backend. The
rationale is that
- Git is itself a filesystem, really.
- Because it snapshots the tree, it gives the same functional
4 matches
Mail list logo