From owner-freebsd-questions@freebsd.org Sat Mar 11 12:07:58 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 130EFD08D20 for ; Sat, 11 Mar 2017 12:07:58 +0000 (UTC) (envelope-from d@l.ynx.fr) Received: from mailer.daserv.fr (daserv.fr [91.121.223.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D55CB195F for ; Sat, 11 Mar 2017 12:07:56 +0000 (UTC) (envelope-from d@l.ynx.fr) Received: from mailpile.local (mailpile.ynx.fr [192.168.1.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mailer.daserv.fr (Postfix) with ESMTPS id A39A9441; Sat, 11 Mar 2017 11:49:48 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ynx.fr; s=YNX_KEY; t=1489229388; bh=QS377kbZQApB3acs82aHrpJSOUBiFyZ8a91i30tYkBM=; h=Subject:From:To:Date; b=W/rW+tHH5nVaj7RunlB3B9qZjeSaFNVjpsWKPBzsYQx/g6SDbAMU18/DuFkOo95wc CznPEmiOcX8ny/eMh3Coy43cse/gbG/I9zIeC5YOOkve90QtHXyplfVXH89gAXpseg s+OJmwg3R+Wm1zNOJJ6DfIDjrEuRMeFJZj1Hr4L0= MIME-Version: 1.0 Subject: Jail limited user cannot access host mountpoint although jail root can From: DaLynX To: freebsd-questions User-Agent: Mailpile Message-Id: Date: Sat, 11 Mar 2017 02:59:47 -0000 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Mar 2017 12:07:58 -0000 Hello, I am trying to make my setup work with jails and got stuck in the following situation: - Host is mounting a fuse filesystem (because I couldn't make it work directly inside the jail - although the /dev/fuse device was accessible) in the jail's chroot. - From root@host, everything looks fine. - root@jail, too, can access the mounted filesystem, read files, no problem. - limited@jail can see the mountpoints but cannot access them in any way (no cd, no ls...) although the file permissions look okay (it's all 755, and for some reason limited is the owner of all mountpoints). What could have gone wrong? I tried playing around with vfs.usermount on the host or enforce_statfs on the jail but it makes no difference. Any pointers would be greatly appreciated. Kind regards, DaLynX From owner-freebsd-questions@freebsd.org Sat Mar 11 13:23:22 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 27CAFD07971 for ; Sat, 11 Mar 2017 13:23:22 +0000 (UTC) (envelope-from lists@bertram-scharpf.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.126.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 805E222A for ; Sat, 11 Mar 2017 13:23:20 +0000 (UTC) (envelope-from lists@bertram-scharpf.de) Received: from becker.bs.l ([85.180.8.195]) by mrelayeu.kundenserver.de (mreue005 [212.227.15.129]) with ESMTPSA (Nemesis) id 0LkUcJ-1cEisw48hX-00cO8W for ; Sat, 11 Mar 2017 14:23:18 +0100 Received: from bsch by becker.bs.l with local (Exim 4.88 (FreeBSD)) (envelope-from ) id 1cmgzN-0004Xz-Ho for freebsd-questions@freebsd.org; Sat, 11 Mar 2017 14:23:17 +0100 Date: Sat, 11 Mar 2017 14:23:17 +0100 From: Bertram Scharpf To: freebsd-questions@freebsd.org Subject: The challenging Ports design Message-ID: <20170311132317.GA17391@becker.bs.l> Mail-Followup-To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.7.2 (2016-11-26) Sender: Bertram Scharpf X-Provags-ID: V03:K0:UNaYmIVNTcYOVzbex//PiBZZdPBWGpgkT+7MzrNQnG/YaDtSH2C +ihV0o15VGXfIpPJkFE03TIm1qsNFUfRzjTk8QuuQHu7cqFwV3+zTuq9ZTqhIc40UpSwLAN pziJgGJWsSA9E0JY/tSv2LZzHQVIXkb56U9/eaJ4pP+hdDB4OsI/i7cbTffwDmhcLhaDP3h 8pi3Qtc4RNAWdLT8TmSPA== X-UI-Out-Filterresults: notjunk:1;V01:K0:prrqA1B29Fc=:3Reh3dXNsRnYyhXRNo8v8n 0KwuGKIuoH/P4tGwGsa6uXfWhS2/cG8DNNKzwDMzKM/D7lNZBV8A1nIAVVmPSir4OA2dsZnh1 gKGnVR4h2bsbs/XZkVopFwmFI2x1aXGLyTrU29wu6LIctgDvwZhjE9EdNT0cu100SmUwhgIge DKPQkJy5FFTZxOsGBpwISkzFTt5wMKZVRUregbcPdfiR2mvOnuICiFDLrZLnU+d1eSqePH+cl QwlNZNnoMlxK1X1ZTQetdYBM6GMZ+CXH2vFWzpJ0SaVWkM1AXd7i1Ic2k8H1fxQ/7ZoTy95D7 Q+qp7vgIXZCpr11653QRcpmo0qIErPPyZ5cxpOsd3jXHGML8tAx8m03BNlz1UB3+nfw0+mh4U W9GQ4xjW6ZMjMz3dsmIdSK+lKcRIbUfjuKm2enxES6dFzYFt8aNLmVZ3zM209XQryqylmwuug FDKGFmMbTmTGE5XJ5XzyPfWWtXTZm0w/4GlDPTDaWxoUWvDzqE3V/wVuH9hvDK70crQOztmOP alKvMO7CfSL1E4Cv5nAL8D04tSW8VBGItt1Fy5XxxBs++BZH7mDsJJiM1jezR/oZtRlJpVrB3 sfSy7/+7uTAci7Oq78QTm7saJnJ6jsUzlwwY5/L+dOxHmUJK04j7UU0h7LUvbnHhn/43s6XEz tMlFH3s2evugc3LrxBJZzmcUF3ymYMHllgQNcXMRPcqiH8Dk3aabvjzrcE3gQldemu1o= X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Mar 2017 13:23:22 -0000 Hi, # cd /usr/ports/devel/fossil # make install [...] Error: Unknown option --without-tcl Try: 'configure --help' for options ===> Script "configure" failed unexpectedly. Please report the problem to [...] The problem is that Fossil uses "autosetup", an "automake" replacement that has no "--without-XXX" options. You cannot switch that off in /usr/ports/Mk/bsd.options.mk, line 566. In this context the word "unexpectedly" is quite venturesome. Bertram -- Bertram Scharpf Stuttgart, Deutschland/Germany http://www.bertram-scharpf.de