[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m1vcotigyb.fsf@fess.ebiederm.org>
Date: Mon, 02 Jan 2012 19:49:00 -0800
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Stanislav Kinsbursky <skinsbursky@...allels.com>
Cc: "Trond.Myklebust\@netapp.com" <Trond.Myklebust@...app.com>,
"linux-nfs\@vger.kernel.org" <linux-nfs@...r.kernel.org>,
Pavel Emelianov <xemul@...allels.com>,
"neilb\@suse.de" <neilb@...e.de>,
"netdev\@vger.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
James Bottomley <jbottomley@...allels.com>,
"bfields\@fieldses.org" <bfields@...ldses.org>,
"davem\@davemloft.net" <davem@...emloft.net>,
"devel\@openvz.org" <devel@...nvz.org>
Subject: Re: [PATCH 01/11] SYSCTL: export root and set handling routines
Stanislav Kinsbursky <skinsbursky@...allels.com> writes:
> 19.12.2011 20:37, Eric W. Biederman пишет:
>> Stanislav Kinsbursky<skinsbursky@...allels.com> writes:
>>
>> Doing that independently of the rest of the sysctls is pretty horrible
>> and confusing to users. What I am planning might suit your needs and
>> 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/<pid>/sys
directory that reflects the sysctls for a given process.
Eric
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists