summaryrefslogtreecommitdiff
path: root/doc/todo
diff options
context:
space:
mode:
Diffstat (limited to 'doc/todo')
-rw-r--r--doc/todo/etckeeper/comment_2_69484bfac40de156a4b877f27aa69eca._comment14
-rw-r--r--doc/todo/etckeeper/comment_3_5f62128bdb550de475d22abb35730949._comment7
-rw-r--r--doc/todo/removable_drive_partitioning_and_install.mdwn40
3 files changed, 61 insertions, 0 deletions
diff --git a/doc/todo/etckeeper/comment_2_69484bfac40de156a4b877f27aa69eca._comment b/doc/todo/etckeeper/comment_2_69484bfac40de156a4b877f27aa69eca._comment
new file mode 100644
index 00000000..dfb9f9df
--- /dev/null
+++ b/doc/todo/etckeeper/comment_2_69484bfac40de156a4b877f27aa69eca._comment
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="stappers@eb96885816da287c29f6f699999434d532149234"
+ nickname="stappers"
+ avatar="http://cdn.libravatar.org/avatar/bf33450acf6fc2a17a8b4e6fc7749c65"
+ subject="why still on todo list"
+ date="2017-12-27T23:00:58Z"
+ content="""
+the 'all needed apt.installed[\"etckeeper\"]' seems to me that the etckeeper is available.
+
+Why is this still on the todo list?
+
+What kind of patches are wanted??
+
+"""]]
diff --git a/doc/todo/etckeeper/comment_3_5f62128bdb550de475d22abb35730949._comment b/doc/todo/etckeeper/comment_3_5f62128bdb550de475d22abb35730949._comment
new file mode 100644
index 00000000..7d2f8d43
--- /dev/null
+++ b/doc/todo/etckeeper/comment_3_5f62128bdb550de475d22abb35730949._comment
@@ -0,0 +1,7 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 3"""
+ date="2017-12-27T23:35:16Z"
+ content="""
+Yeah, just been waiting to hear back from the issue submitter.
+"""]]
diff --git a/doc/todo/removable_drive_partitioning_and_install.mdwn b/doc/todo/removable_drive_partitioning_and_install.mdwn
new file mode 100644
index 00000000..891c3b92
--- /dev/null
+++ b/doc/todo/removable_drive_partitioning_and_install.mdwn
@@ -0,0 +1,40 @@
+I want to be able to temporarily plug in the root drive of another host
+to my laptop and run propellor to re-image the drive with the properties of
+the host it belongs to. This is especially useful when the drive is too
+large to make a DiskImage on my laptop.
+
+Open design questions:
+
+* How to uniquely identify which removable drive belongs to which Host?
+ Could use partition uuids for updating an already imaged drive, but not
+ for the initial build.
+
+ /dev/disk/by-id/ seems a good way to go. Eg for a USB drive I have,
+ "/dev/disk/by-id/usb-LaCie_iamaKey_37637172f536ba-0:0" probably uniquely
+ identifies it, at least as long as the manufacturer is not reusing serial
+ numbers.
+
+ One problem with /dev/disk/by-id/ is, if a removable drive is attached
+ on a different bus (ie, a SATA drive might be connected via SATA or a USB
+ dock), it won't appear the same there.
+
+ Could instead use eg `udevadm info --query=all -n /dev/sdb`, which
+ breaks out `ID_SERIAL`. However, this would be harder for the user to
+ look up. Or, could parse the /dev/disk/by-id/ name, excluding the bus
+ part of it.
+
+ Question: When using microsd card adapter, does the serial number pass
+ through so different microsds can be distinguished?
+ > Checked this, and two microsd card adapters from different
+ > manufacturers with different microsd cards have the same by-id.
+ > Those must have no serial number..
+
+* Should an already imaged drive be updated incrementally or re-imaged?
+ Seems both cases would be useful, the former especially for incrementally
+ configuring it, the latter to bring it up from a clean state.
+ If it defaults to updating, the user could force a re-image by deleting
+ the partitions from the drive manually.
+
+secret-project has some code for /target which might be reusable here.
+
+--[[Joey]]