hurd/settrans/discussion: settrans --chroot.

3 files changed, 36 insertions, 16 deletions

diff --git a/hurd/settrans/discussion.mdwn b/hurd/settrans/discussion.mdwn
index 74f1c8f5..aff7562a 100644
--- a/hurd/settrans/discussion.mdwn
+++ b/hurd/settrans/discussion.mdwn
@@ -1,4 +1,5 @@
-[[!meta copyright="Copyright © 2011, 2012 Free Software Foundation, Inc."]]
+[[!meta copyright="Copyright © 2011, 2012, 2013, 2014 Free Software Foundation,
+Inc."]]
 
 [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
 id="license" text="Permission is granted to copy, distribute and/or modify this
@@ -10,6 +11,8 @@ License|/fdl]]."]]"""]]
 
 [[!tag open_issue_documentation open_issue_hurd]]
 
+[[!toc]]
+
 
 # IRC, freenode, #hurd, 2011-06-01
 
@@ -37,3 +40,29 @@ License|/fdl]]."]]"""]]
     <antrik> braunr: well, the fact that a translator is unset by setting it to
       nothing is unclear in general, not only for passive translator. I agree
       that pointing this out should make things much more clear in general...
+
+
+<a name="chroot">
+# `--chroot`
+</a>
+
+## IRC, freenode, #hurd, 2013-08-29
+
+    <teythoon> btw, I somehow feel settrans is being abused for chroot and
+      friends, there is no translator setting involved
+    <youpi> chroot, the command? or the settrans option?
+    <youpi> I don't understand what you are pointing at
+    <teythoon> the settrans option being used by fakeroot, remap and (most
+      likely) our chroot
+    <youpi> our chroot is just a file_reparent call
+    <youpi> fakeroot and remap do start a translator
+
+[[virtualization/remap_root_translator]], [[virtualization/fakeroot]].
+
+    <teythoon> yes, but it is not being bound to a node, which is (how I
+      understand it) what settrans does
+    <teythoon> the point being that if settrans is being invoked with --chroot,
+      it does something completely different (see the big if (chroot) {...}
+      blocks)
+    <teythoon> to a point that it might be better of in a separate command
+    <youpi> Mmm, indeed, a lot of the options don't make sense for chroot
diff --git a/hurd/translator/mtab/discussion.mdwn b/hurd/translator/mtab/discussion.mdwn
index bac32906..d663d4c5 100644
--- a/hurd/translator/mtab/discussion.mdwn
+++ b/hurd/translator/mtab/discussion.mdwn
@@ -1870,21 +1870,6 @@ In context of [[open_issues/mig_portable_rpc_declarations]].
     <teythoon> and I saw that this also aplies to remap.sh
     <teythoon> *while
     <youpi> yep, they're basically the same
-    <teythoon> btw, I somehow feel settrans is being abused for chroot and
-      friends, there is no translator setting involved
-    <youpi> chroot, the command? or the settrans option?
-    <youpi> I don't understand what you are pointing at
-    <teythoon> the settrans option being used by fakeroot, remap and (most
-      likely) our chroot
-    <youpi> our chroot is just a file_reparent call
-    <youpi> fakeroot and remap do start a translator
-    <teythoon> yes, but it is not being bound to a node, which is (how I
-      understand it) what settrans does
-    <teythoon> the point being that if settrans is being invoked with --chroot,
-      it does something completely different (see the big if (chroot) {...}
-      blocks)
-    <teythoon> to a point that it might be better of in a separate command
-    <youpi> Mmm, indeed, a lot of the options don't make sense for chroot
 
 
 ## IRC, freenode, #hurd, 2013-09-06
diff --git a/open_issues/virtualization/fakeroot.mdwn b/open_issues/virtualization/fakeroot.mdwn
index 7856e299..8901e1c3 100644
--- a/open_issues/virtualization/fakeroot.mdwn
+++ b/open_issues/virtualization/fakeroot.mdwn
@@ -301,6 +301,9 @@ License|/fdl]]."]]"""]]
     <braunr> i might want to return to it later
     <teythoon_> ah
     <teythoon_> ok, so you are not using settrans --chroot
+
+[[hurd/settrans/discussion#chroot]].
+
     <braunr> or maybe i'm confusing the fakeroot translator and fakeroot-hurd
     <braunr> 10:48 < braunr> you may not want to chroot inside
     <braunr> yes
@@ -754,6 +757,9 @@ License|/fdl]]."]]"""]]
     <braunr> could it simply be that the check on np->references should be
       moved above the assertion ?
     <teythoon> braunr: it is not bound to any node, check settrans --chroot
+
+[[hurd/settrans/discussion#chroot]].
+
     <braunr> oh right
     <braunr> teythoon: ok i mean
     <braunr> does it shadow / ?