From 9da737f6aa9fa7735e74d261bb2d2b745e273219 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Wed, 26 Feb 2014 17:12:57 +0100 Subject: hurd/settrans/discussion: settrans --chroot. --- hurd/translator/mtab/discussion.mdwn | 15 --------------- 1 file changed, 15 deletions(-) (limited to 'hurd/translator/mtab') 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]]. and I saw that this also aplies to remap.sh *while yep, they're basically the same - btw, I somehow feel settrans is being abused for chroot and - friends, there is no translator setting involved - chroot, the command? or the settrans option? - I don't understand what you are pointing at - the settrans option being used by fakeroot, remap and (most - likely) our chroot - our chroot is just a file_reparent call - fakeroot and remap do start a translator - yes, but it is not being bound to a node, which is (how I - understand it) what settrans does - the point being that if settrans is being invoked with --chroot, - it does something completely different (see the big if (chroot) {...} - blocks) - to a point that it might be better of in a separate command - Mmm, indeed, a lot of the options don't make sense for chroot ## IRC, freenode, #hurd, 2013-09-06 -- cgit v1.2.3