From mboxrd@z Thu Jan 1 00:00:00 1970 From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman) Subject: Re: [PATCH 01/11] SYSCTL: export root and set handling routines Date: Mon, 02 Jan 2012 19:49:00 -0800 Message-ID: References: <20111214103602.3991.20990.stgit@localhost6.localdomain6> <20111214104449.3991.61989.stgit@localhost6.localdomain6> <4EEEFC54.10700@parallels.com> <4EEF2C9A.8000403@parallels.com> <4EEF7364.8000407@parallels.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: "Trond.Myklebust\@netapp.com" , "linux-nfs\@vger.kernel.org" , Pavel Emelianov , "neilb\@suse.de" , "netdev\@vger.kernel.org" , "linux-kernel\@vger.kernel.org" , James Bottomley , "bfields\@fieldses.org" , "davem\@davemloft.net" , "devel\@openvz.org" To: Stanislav Kinsbursky Return-path: In-Reply-To: <4EEF7364.8000407-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org> (Stanislav Kinsbursky's message of "Mon, 19 Dec 2011 21:24:52 +0400") Sender: linux-nfs-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: netdev.vger.kernel.org Stanislav Kinsbursky writes: > 19.12.2011 20:37, Eric W. Biederman =D0=BF=D0=B8=D1=88=D0=B5=D1=82: >> Stanislav Kinsbursky writes: >> >> Doing that independently of the rest of the sysctls is pretty horrib= le >> and confusing to users. What I am planning might suit your needs a= nd >> if not we need to talk some more about how to get the vfs to do >> something reasonable. >> > > Ok, Eric. Would be glad to discuss your sysctls plans. > But actually you already know my needs: I would like to make sysctls = work in the > way like sysfs does: i.e. content of files depends on mount maker - > not viewer. What drives the desire to have sysctls depend on the mount maker? Especially what drives that desire not to have it have a /proc//sy= s directory that reflects the sysctls for a given process. Eric -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html