summaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorRoger Leigh <rleigh@debian.org>2009-06-28 23:46:25 +0100
committerRoger Leigh <rleigh@debian.org>2009-06-28 23:46:25 +0100
commitd8ba8499cfee76c256356acb61b744395ea7c2da (patch)
tree93e0d1145061fdb148bf460fc55a409d2eddbab3 /TODO
parent47105b0d7d1df93de98dff1b5596fadc95dd43e1 (diff)
downloadschroot-d8ba8499cfee76c256356acb61b744395ea7c2da.tar.gz
[TODO] Add union items
Diffstat (limited to 'TODO')
-rw-r--r--TODO33
1 files changed, 33 insertions, 0 deletions
diff --git a/TODO b/TODO
index 2b3b4be3..f9995b24 100644
--- a/TODO
+++ b/TODO
@@ -79,6 +79,13 @@ fashion. expect might be useful for testing the PAM wrappers.
Note: how to deal with duplicated names in both namespaces for --all?
Maybe just list twice, first chroots and then sessions?
+Have separate namespaces for
+* chroots (for --all-chroots)
+* chroot aliases (for chroot commands)
+* source chroots (for --all-source-chroots)
+* source chroot aliases (for source chroot commands; add --source option)
+* sessions (for all session commands)
+
* Testcase for chroot-loopback
fs-union mounting simplifications
@@ -94,3 +101,29 @@ file: Set full unpack dir with session ID like LVM snapshot.
* Add a read-only mount option for union underlay (both for
devices and bind mounts).
+Security: Record user who created a session, and don't allow other
+users access (except root?).
+This might involve serialising the authentication state into the
+chroot object.
+
+Does a NULL ptr from clone_source get stored?
+
+Move chroot-specific session setup from sbuild::session for chroot
+vfunc.
+
+Union: Don't allow overlay/underlay to be user-specified? Or only
+allow underlay to be specified (but it's already specified in the
+chroot definition, so don't allow?).
+Note: Currently user settings are automatically overridden.
+
+Add directories under /var to man pages
+
+Add checks for unsupported features in setup scripts.
+
+Separate UUID support into support function
+
+Set session ID in chroot configuration in addition to name.
+This will allow the removal of chroot-specific session setup from
+sbuild::session. This also means the session ID is chroot-specific
+rather than session-specific, so won't be reused if using multiple
+chroots.