From: Wolfgang Grandegger <wolfgang.grandegger@bluewin.ch>
To: jdweyer@rockwellcollins.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: /dev/vme Permissions for users other than root...
Date: Wed, 23 Jan 2002 19:43:13 +0100 [thread overview]
Message-ID: <3C4F0441.8070905@bluewin.ch> (raw)
In-Reply-To: OFEA27A9BB.3CE5E820-ON86256B49.007E0567@collins.rockwell.com
Hi JoAnna,
I think the following code fragments in the ioctl function of the VME driver
simply prevent normal users from doing "bad" things:
/* Is this the right capability to use ? Everybody seems
to use
* CAPS_SYS_ADMIN as a default to replace suser().
*/
error = -EPERM;
if (!capable(CAP_SYS_ADMIN)) break;
Hope it helps,
Wolfgang.
jdweyer@rockwellcollins.com wrote:
>(disregard prior email; subject was not included)
>
>Greetings,
>
>We are using Linux version 2.2.12 with Gabriel Paubert's patches for the
>Motorola MVME2600 platform. I have
>my application working opening /dev/vme and then doing ioctl calls to set
>the attributes. It works
>fine only when I am root. When another user tries to run the application,
>the ioctl (not the open) fails.
>I have changed the permissions of /dev/vme to rw for all (ugo) and have
>even gone as far as
>changing ownership and group to the user's instead of root, but to no
>avail. The permissions
>of /dev/vme are crwxrwxrwx. I realize the execute (x) permission is
>ineffective, but I'm trying everything.
>
>Do you have any ideas of what to try?
>
>Thanks for any help you can provide,
>
>JoAnna Weyer
>
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-01-23 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-22 22:57 /dev/vme Permissions for users other than root jdweyer
2002-01-23 8:32 ` Didier Kryn
2002-01-23 18:43 ` Wolfgang Grandegger [this message]
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=3C4F0441.8070905@bluewin.ch \
--to=wolfgang.grandegger@bluewin.ch \
--cc=jdweyer@rockwellcollins.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).