public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] DevFS support for /dev/cpu/X/(cpuid|msr)
Date: Wed, 9 Jan 2002 14:28:37 +1100	[thread overview]
Message-ID: <20020109142837.3ee52fe0.rusty@rustcorp.com.au> (raw)
In-Reply-To: <a1gcme$18t$1@cesium.transmeta.com>
In-Reply-To: <20020106181749.A714@butterlicious.bodgit-n-scarper.com> <20020108201451.088f7f99.rusty@rustcorp.com.au> <a1f9j9$5i9$1@cesium.transmeta.com> <20020109120108.39bcf7ad.rusty@rustcorp.com.au> <a1gcme$18t$1@cesium.transmeta.com>

On 8 Jan 2002 19:16:30 -0800
"H. Peter Anvin" <hpa@zytor.com> wrote:
> So you chown an entry, then a module is unloaded and reloaded, now
> what happens?

Sorry, was responding to the second sentence, not the first:

> However, procfs has no permission control
> system set up, unlike /dev.  This is inherent; adjusting sysctls is a
> root-only function and cannot be made otherwise.

In practice, my /proc/sys perms are four bits: ALL READ, ALL WRITE, ROOT READ, ROOT WRITE.

Hope that helps,
Rusty.
-- 
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  reply	other threads:[~2002-01-09  5:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-06 18:17 [PATCH] DevFS support for /dev/cpu/X/(cpuid|msr) Matt Dainty
2002-01-06 19:34 ` Richard Gooch
2002-01-06 20:43   ` Matt Dainty
2002-01-06 21:08     ` H. Peter Anvin
2002-01-06 21:11       ` Richard Gooch
2002-01-06 21:12         ` H. Peter Anvin
2002-01-06 21:06   ` H. Peter Anvin
2002-01-06 21:08     ` Richard Gooch
2002-01-06 21:10       ` H. Peter Anvin
2002-01-06 21:36         ` Russell King
2002-01-07  0:44           ` H. Peter Anvin
2002-01-07  1:31         ` Richard Gooch
2002-01-07  1:32           ` H. Peter Anvin
2002-01-07  1:40             ` Richard Gooch
2002-01-07  1:44               ` H. Peter Anvin
2002-01-08 11:13               ` Matt Dainty
2002-01-08  9:14                 ` Rusty Russell
2002-01-08 12:02                   ` Matt Dainty
2002-01-08 17:35                     ` Richard Gooch
2002-01-08 17:17                   ` H. Peter Anvin
2002-01-09  1:01                     ` Rusty Russell
2002-01-09  3:16                       ` H. Peter Anvin
2002-01-09  3:28                         ` Rusty Russell [this message]
2002-01-09  3:30                         ` Richard Gooch
2002-01-09  3:47                           ` H. Peter Anvin
2002-01-09  5:41                             ` Richard Gooch
  -- strict thread matches above, loose matches on Subject: below --
2002-02-18 10:50 Ishan Jayawardena
2002-02-18 18:25 ` Richard Gooch

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=20020109142837.3ee52fe0.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    /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