From: Sam Vilain <sam@vilain.net>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, dev@sw.ru, herbert@13thfloor.at,
devel@openvz.org, ebiederm@xmission.com, xemul@sw.ru,
haveblue@us.ibm.com, clg@fr.ibm.com, serue@us.ibm.com
Subject: Re: [PATCH] namespaces: uts_ns: make information visible via /proc/PID/uts directory
Date: Tue, 23 May 2006 09:31:26 +1200 [thread overview]
Message-ID: <44722DAE.3020205@vilain.net> (raw)
In-Reply-To: <20060522010414.6dfb4f71.akpm@osdl.org>
Andrew Morton wrote:
>Sam Vilain <sam@vilain.net> wrote:
>
>
>>Export the UTS information to a per-process directory /proc/PID/uts,
>> that has individual nodes for hostname, ostype, etc - similar to
>> those in /proc/sys/kernel
>>
>>
>umm, why?
>
>
Er, for the same reason we have /proc/PID/mounts ?
>> This duplicates the approach used for /proc/PID/attr, which involves a
>> lot of duplication of similar functions. Much room for maintenance
>> optimisation of both implementations remains.
>> fs/proc/base.c | 236 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>
>ouch.
>
>
Also yow. Refer above gross understatement.
Sam.
next prev parent reply other threads:[~2006-05-22 21:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 5:24 [PATCH] namespaces: uts_ns: make information visible via /proc/PID/uts directory Sam Vilain
2006-05-22 8:04 ` Andrew Morton
2006-05-22 21:31 ` Sam Vilain [this message]
2006-05-22 11:45 ` Alan Cox
2006-05-22 23:07 ` Sam Vilain
2006-05-22 23:10 ` Sam Vilain
2006-05-22 23:49 ` Sam Vilain
2006-05-22 14:03 ` Herbert Poetzl
2006-05-22 16:39 ` Eric W. Biederman
2006-05-22 23:18 ` Sam Vilain
-- strict thread matches above, loose matches on Subject: below --
2006-05-22 5:23 Sam Vilain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44722DAE.3020205@vilain.net \
--to=sam@vilain.net \
--cc=akpm@osdl.org \
--cc=clg@fr.ibm.com \
--cc=dev@sw.ru \
--cc=devel@openvz.org \
--cc=ebiederm@xmission.com \
--cc=haveblue@us.ibm.com \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
--cc=serue@us.ibm.com \
--cc=xemul@sw.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox