All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Schubert <bernd-schubert@web.de>
To: linux-kernel@vger.kernel.org
Subject: /dev/ entries change owner
Date: Fri, 6 Sep 2002 20:45:37 +0200	[thread overview]
Message-ID: <200209062045.37478.bernd-schubert@web.de> (raw)

Hi,

we (all adminitrators from our group) would like to know, why the owner of 
/dev/ entries are changed in 2.4.x kernels on accessing them.

We DON'T use devfs, so this can't be the reason.

For example if the user joerg (in this case also an admin :) )uses the 
soundcard, he magically owns all dsp-entries, though these were previously 
owned by root:

lrwxrwxrwx    1 root     root            9 Apr 12 18:35 /dev/dsp -> /dev/dsp0
crw-rw-rw-    1 joergb   user      14,   3 Apr 12 18:35 /dev/dsp0
crw-------    1 joergb   user      14,  19 Apr 12 18:35 /dev/dsp1
crw-------    1 joergb   user      14,  35 Apr 12 18:35 /dev/dsp2
crw-------    1 joergb   user      14,  51 Apr 12 18:35 /dev/dsp3

Or if the user sven (no admin, so no root rights so he has no possibility to 
affect this behaviour) uses the floppy drive:
 
brw-------    1 sven     user       2,   0 Sep 24  2001 /dev/fd0

Unfortunality this causes that no other user might use the floppy drive -- a 
desaster in a multi user environment (our group has over 40 members).

This seems to happen to lots of devices (another example are tty's) and it is 
distribution independent (I see it at home (Slackware) and at work (Suse)).


Any suggestions what I could do ???



Thanks in advance for your help,

Bernd

-- 
Bernd Schubert
Physikalisch Chemisches Institut
Abt. Theoretische Chemie
INF 229, 69120 Heidelberg
Tel.: 06221/54-5210
e-mail: 	bernd (dot) schubert (at) pci (dot) uni-heidelberg (dot) de 

             reply	other threads:[~2002-09-06 18:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-06 18:45 Bernd Schubert [this message]
2002-09-06 18:55 ` /dev/ entries change owner John Jasen

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=200209062045.37478.bernd-schubert@web.de \
    --to=bernd-schubert@web.de \
    --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.