GNOME != Fedora [LWN.net]

GNOME != Fedora

Posted Nov 6, 2011 23:38 UTC (Sun) by raven667 (subscriber, #5198)
In reply to: GNOME != Fedora by Wol
Parent article: Rawhide gets GNOME Shell for all display types

There is a good reason that doesn't work. Device Notifications are only sent to the user on the local console attached to the machine, not to remote users. There is no way to reliably and consistently handle notifications or access to devices in the remote user case, what would the system do when there are multiple remote users? Even if there is only one user logged in remotely, the first of N remote users shouldn't behave differently, that would be very weird in a multiuser environment

to post comments

GNOME != Fedora

Posted Nov 6, 2011 23:59 UTC (Sun) by dlang (guest, #313) [Link] (1 responses)

what do you do if there are multiple remote users? you notify them all of course.

sending notifications to all users, local or remote is something that has been done for decades on unix systems.

GNOME != Fedora

Posted Nov 7, 2011 16:22 UTC (Mon) by raven667 (subscriber, #5198) [Link]

Many if not most of the hardware access that is appropriate for a local console user, to network, audio, and storage devices is not appropriate for remote users. The OP was asking why they couldn't change local device settings when logged in remotely. There are certainly cases where we want to send a notice to all logged in users but for many of the desktop notifications related to local hardware you probably don't want to broadcast them to all users and you probably don't want all users to have automatically privileged read/write access when plugging in a removable drive for example. It's a much simpler default policy to just draw a line between local console users and remote.