hurd/settrans/discussion: settrans --chroot.

1 files changed, 0 insertions, 15 deletions

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