Mailinglist Archive: opensuse (4054 mails)

[Roger Oberholtzer <roger@xxxxxx>]

On Wed, 2006-01-18 at 21:09 +0100, Carlos E. R. wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> The Wednesday 2006-01-18 at 10:04 +0800, Peter Sutter wrote:
> 
> > To burn the dvd, growisofs needs physical access to the dvd burner, 
> > which is /dev/hda, and the permissions of /dev/hda change from 666 
> > root:disks  to 600 root:disks after a crash. 
> 
> Did you read my email (Monday)?
> 
> In file /etc/logindevperm:
> 
> :0 0600 /dev/cdrom:/dev/cdrom1:/dev/cdrom2:/dev/cdrom3

How does logindevperms relate to udev and HAL? I would guess that if a
device is already present when you log in, logindevperms will replace
any udev/HAL settings. If the device gets inserted while logged in, the
udev/HAL settings are used and not logindevperms.

Joy. Another piece of the puzzle.

And, what happens if someone logs in after you while you are logged in?
login runs as root, so there is nothing stopping it from claiming the
device for the new login. Meaning that any changes made by the first
person would be set to logindevperms when the second person logs in.

I guess the first item on each logindevperms line allows a bit of
control over this. But I would happy to fully understand the interaction
with udev/HAL. The default logindevperms explains why you only get the
device settings when you log in as the first GUI login on the console,
as only that is defined in the default SUSE logindevperms.

Anyway, thanks for the pointer to logindevperms. It is now on the radar.
Too bad it still does not explain why /dev/ttyS0 is set to rw access
only for the current login. I have not traced who does that.

--
Roger Oberholtzer