All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Schwaighofer <cs@tequila.co.jp>
To: Duncan Sands <baldrick@free.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: procfs permissions on 2.6.x
Date: Mon, 05 Jul 2004 17:14:02 +0900	[thread overview]
Message-ID: <40E90DCA.20107@tequila.co.jp> (raw)
In-Reply-To: <200407051005.29968.baldrick@free.fr>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Duncan Sands wrote:
|>Well perhaps I am on the wrong track but eg /proc/bus/usb/002/005 is my
|>digital camera and unless its either world rw or owned by me (user) I
|>can't get any pictures unless I make myself root.
|>
|>So yes, I would want to have chown/chmod in procfs ...
|
|
| Hi Clemens, that isn't procfs, it's usbfs.  It's been plonked (*) on
top of a procfs
| directory, but that doesn't matter.

total forgot about that :) Because if you don't compile the kernel with
usbfs you don't see it there ...

- --
Clemens Schwaighofer - IT Engineer & System Administration
==========================================================
TEQUILA\Japan, 6-17-2 Ginza Chuo-ku, Tokyo 104-8167, JAPAN
Tel: +81-(0)3-3545-7703            Fax: +81-(0)3-3545-7343
http://www.tequila.co.jp
==========================================================
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA6Q3KjBz/yQjBxz8RArACAKDNr+SXs20yVvWdWBYGsbpCAkMqwACgqO2S
srwaWJ2q6Wd0j5AOB4Y5UZM=
=kcN9
-----END PGP SIGNATURE-----

  reply	other threads:[~2004-07-05  8:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-03 20:22 procfs permissions on 2.6.x Herbert Poetzl
2004-07-03 20:25 ` Christoph Hellwig
2004-07-03 20:35   ` Andrew Morton
2004-07-03 21:04     ` Christoph Hellwig
2004-07-03 21:35       ` Andrew Morton
2004-07-04 21:35         ` viro
2004-07-04 21:55           ` Andrew Morton
2004-07-04 22:13             ` viro
2004-07-04 22:43               ` Andrew Morton
2004-07-06  3:31                 ` Andy Lutomirski
2004-07-05  1:50               ` Clemens Schwaighofer
2004-07-05  1:55                 ` viro
2004-07-05  8:05                 ` Duncan Sands
2004-07-05  8:14                   ` Clemens Schwaighofer [this message]
2004-07-04  1:27     ` bert hubert
     [not found] <2dZjc-7BP-15@gated-at.bofh.it>
     [not found] ` <2dZjf-7BP-27@gated-at.bofh.it>
     [not found]   ` <2dZsQ-7GF-23@gated-at.bofh.it>
     [not found]     ` <2dZVV-867-33@gated-at.bofh.it>
     [not found]       ` <2e0oZ-8lm-35@gated-at.bofh.it>
     [not found]         ` <2emSs-6R8-17@gated-at.bofh.it>
     [not found]           ` <2enbS-72q-19@gated-at.bofh.it>
     [not found]             ` <2env9-7li-9@gated-at.bofh.it>
2004-07-04 22:25               ` Andi Kleen
2004-07-04 22:37                 ` FabF
2004-07-04 23:30                   ` Paul Jackson

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=40E90DCA.20107@tequila.co.jp \
    --to=cs@tequila.co.jp \
    --cc=baldrick@free.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.