From owner-freebsd-hackers@freebsd.org Tue Mar 13 22:31:45 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 127A1F56574 for ; Tue, 13 Mar 2018 22:31:45 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A5DBE79B14 for ; Tue, 13 Mar 2018 22:31:44 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: by mail-qt0-x22c.google.com with SMTP id n12so1461155qtl.5 for ; Tue, 13 Mar 2018 15:31:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=longcount-org.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=v8yUVC6KtnLMjvci0EGZ3W8roNcdZEpPtVkzHVBMS8k=; b=VCwqfTWNHL4WegMllH3LyTBNjVEBXcm/qQcohMuZsFwcaMsizVrxbmYPe5CkAbTDQ2 jkQ0Ca3ZlBLx539eCCmEaAUvCAIhaGKCqiSCBLWgP+mtt9cbaGuc2Er5mCef0VrUr+gD 7+bD82x/fLp4ziLj0Pb3zC5/09CbfrnH1YhcA1i/+bIhhlk2ubxh51BWphjb/inyD9DZ tad5KeWo0U4eAThlyIhnQuocA12lDLtoxmnDNPYlirYeruQsZbDCF51POJhdXYrAQohl ngwiBzIbtSVPukKzeGznbDDECsno3isYvyITg2t18LFaABwn4VOh82gh1tjOa5BsVScP Ov7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=v8yUVC6KtnLMjvci0EGZ3W8roNcdZEpPtVkzHVBMS8k=; b=DwLoSg6qRe/de1IbKvAGgh6Y+L/a1ZISAs8JtzQvEZCC0MWz1UegH29sznsuGHhhk6 hs0OQgb3gwRacOODTCEpN2hpv4iV46jf2D1XFWzumTsM3GelNReYMg8aSDK3VDOClnDG Ea6mR7WypHF/vZS7heonOAaINBBbZPyfIPNlsg8S1NZPQsy6GNSODHxkzeDfEpzhGIiK bT6SS2l3sE3Us7R3SzbVuUU050tPuKdqNQK2D51+z98SUikKn4gFiLCcsoUxIGZFONv9 D8cKs3W+bjnYHr0RuofpWxBJ51af+5T/dtUWjgP6RtiWjQZzsRJys5rcyJMQrXByj/O+ tdtw== X-Gm-Message-State: AElRT7GWrUFruKOBm/03VoiMFsy4fISB0RpOKaiuUbndzPriYkp+CcPP 7kKd2i/hzffwcaIy/0AjcmVhwVJHEsI= X-Google-Smtp-Source: AG47ELvBOo2facIuKw1A3Lg0Y37UHjOXaMrPNgItHTS7mPPpUdHRwdHKN3yu2j8xG8gHHeH2cMkOYw== X-Received: by 10.200.36.189 with SMTP id s58mr3757938qts.0.1520980303660; Tue, 13 Mar 2018 15:31:43 -0700 (PDT) Received: from ?IPv6:2600:1017:b81e:56ea:9c09:d36e:402c:9f78? ([2600:1017:b81e:56ea:9c09:d36e:402c:9f78]) by smtp.gmail.com with ESMTPSA id 21sm603001qkk.10.2018.03.13.15.31.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 13 Mar 2018 15:31:42 -0700 (PDT) Mime-Version: 1.0 (1.0) Subject: Re: GSoC Idea: per-process filesystem namespaces for FreeBSD From: Mark Saad X-Mailer: iPhone Mail (15D100) In-Reply-To: Date: Tue, 13 Mar 2018 18:31:41 -0400 Cc: Kristoffer Eriksson , Theron , Warner Losh Message-Id: References: <201803132055.aa28780@berenice.pkmab.se> To: "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Mar 2018 22:31:45 -0000 > On Mar 13, 2018, at 5:43 PM, Warner Losh wrote: >=20 >> On Tue, Mar 13, 2018 at 1:55 PM, Kristoffer Eriksson wrote= : >>=20 >>=20 >>> On 13 Mar 2018 12:53:18, Theron wrote: >>> For those unfamiliar with Plan9, here is a rough explanation of the >>> namespace feature: unlike in Unix, where all processes share the same >>> virtual filesystem, each process instead has its own view of the >>> filesystem according to what has been mounted ... >>=20 >> What if I mount a new /etc with a passwd file where root has no >> password, and then run "su"? >>=20 >> (How does Plan9 handle that?) >>=20 >=20 > Plan9 handles that by having a daemon that does user authentication. It's > actually more complicated than that, but the machine owner has control ove= r > who can do what. For this to work in FreeBSD, either we'd need to disallow= > the 'file' type for passwd, or we'd have to do something sensible with > setuid programs. Well, maybe not 'or' but 'and' since the security of > setuid programs depends on the security of the filesystem.... Plan 9 > doesn't have these complications, so it can offer a user malleable > filesystem without security risk. >=20 > Warner A kind of related task; FreeBSD could benefit from : Fixing and improving u= nionfs / nullfs. There are some weird issues with the current unionfs and wh= ile it works in many cases there are some edge cases where the comments are s= omething like =E2=80=9C FreeBSD needs a proper stacking vfs ...=E2=80=9D t= he examples I can think of ; imagine you have a jail , chroot or even a Pxe b= ooted system where you want a a read only null mount from the hosts /bin to t= he targets /bin . Now expand that to most of the base system and the mount t= mpfs=E2=80=99s for /tep /var/log etc. most of that works but try to unmount= it in the wrong order or thrash a unionfs with lots of writes ,on top of a t= mpfs and things break .=20 So to be clear the project would be to better document the various uses of u= nionfs and nullfs that work , for the ones that do not diving into the stack= ing vfs and seeing if it could be implemented and if it would help .=20 Alternatively making FreeBSD multiboot compliant would rock . This would all= ow FreeBSD to natively boot from ipxe or syslinux derivates; thus allowing y= ou to boot a working FreeBSD install via a kernel and mfsroot image off a we= b server . http://netbsd.gw.com/cgi-bin/man-cgi?multiboot+8+NetBSD-current http://ipxe.org/ --- Mark Saad | nonesuch@longcount.org > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"=