Quoting Joey Hess (jo...@debian.org):
> user-setup-apply is run in finish-install, so it can check if systemd is
> installed or not.
Interesting suggestion, yes.
>
> The only downsides I see:
>
> * Still need to add the groups in non-systemd installations, eg freebsd,
> so this will be an po
user-setup-apply is run in finish-install, so it can check if systemd is
installed or not.
The only downsides I see:
* Still need to add the groups in non-systemd installations, eg freebsd,
so this will be an point of difference that will need testing.
* If a user chooses to remove systemd afte
Quoting Steve McIntyre (st...@einval.com):
> On Mon, Aug 18, 2014 at 03:24:50PM +0200, Floris wrote:
> >>which is fine.
> >>
> >>But what if people decide to later not use logind/systemd? In what
> >>does it hurt that the first created user is *also* adde
On Mon, Aug 18, 2014 at 05:20:19PM +0200, Floris wrote:
>
> how about users who will login remotely? They also have full access to
> all the audio devices, even when they don't able to hear the music,
> because the speaker is on the other side of the world.
Remote login might be from a computer t
Op Mon, 18 Aug 2014 15:52:34 +0200 schreef Steve McIntyre
:
On Mon, Aug 18, 2014 at 03:24:50PM +0200, Floris wrote:
which is fine.
But what if people decide to later not use logind/systemd? In what
does it hurt that the first created user is *also* added to the audio
group?
When a
On Mon, Aug 18, 2014 at 10:22:16AM -0400, Lennart Sorensen wrote:
> That sure sounds likely.
>
> Perhaps there can be a README.multiseat in the systemd package that
> explains what changes to make for such a setup.
>
> Just because systemd is default doesn't mean everything else should
> stop wor
On Mon, Aug 18, 2014 at 02:52:34PM +0100, Steve McIntyre wrote:
> And if we ignore the multi-seat stuff (which is going to be used by a
> *tiny* minority of users) there is no down-side.
>
> There are still likely going to be vastly more non-systemd users than
> multi-seat users.
That sure sounds
On Mon, Aug 18, 2014 at 03:24:50PM +0200, Floris wrote:
>>which is fine.
>>
>>But what if people decide to later not use logind/systemd? In what
>>does it hurt that the first created user is *also* added to the audio
>>group?
>
>When a user is added to the
which is fine.
But what if people decide to later not use logind/systemd? In what
does it hurt that the first created user is *also* added to the audio
group?
When a user is added to the audio group. He will always see all sound
devices,
even when logind tries to hide the device from the
ice.
> group::rw-
> mask::rw-
> other::---
>
> So the user is able to control the device.
which is fine.
But what if people decide to later not use logind/systemd? In what
does it hurt that the first created user is *also* added to the audio
group?
signature.asc
Description: Digital signature
Adding the first user to group audio shouldn't break any ACL management
that is done by systemd-logind.
logind hide/ show the audio device from the user trough the ACL.
The audio group will always show all audio devices.
I think these two settings are conflicting.
floris
--
To UNSUBS
Op Sun, 17 Aug 2014 17:07:02 +0200 schreef Lennart Sorensen
:
On Fri, Aug 15, 2014 at 11:54:17PM +0200, Floris wrote:
Can you explain what would break? Pulseaudio doesn't need/ works
without the audio group.
The pulseaudio mailing list [1] explains:
I tend to have to kill pulseaudio t
On Fri, Aug 15, 2014 at 11:54:17PM +0200, Floris wrote:
> Can you explain what would break? Pulseaudio doesn't need/ works
> without the audio group.
> The pulseaudio mailing list [1] explains:
I tend to have to kill pulseaudio to get sound working.
If my user isn't in the aud
Adding the first user to group audio shouldn't break any ACL management
that is done by systemd-logind.
It just means, the first user *always* has access to the audio device,
no matter if his session is marked active for he is logged in locally.
So he get's access even when e.g. logged in remotel
with systemd as the default init system. systemd/ logind sets the right
permissions for the sound devices [1], so I think it is unnecessary to
add
somebody to the audio group. (And missing all the "fancy stuff" systemd
brings to us.)
I don't think you have explained why having
Op Sun, 17 Aug 2014 00:45:15 +0200 schreef Cyril Brulebois
:
Floris (2014-08-17):
Op Sat, 16 Aug 2014 08:55:27 +0200 schreef Christian PERRIER
:
>
>In short, yes, the first created user (the only one created by D-I) is
>added to the "audio" group, among a few others.
&
Floris (2014-08-17):
> Op Sat, 16 Aug 2014 08:55:27 +0200 schreef Christian PERRIER
> :
>
> >
> >In short, yes, the first created user (the only one created by D-I) is
> >added to the "audio" group, among a few others.
> >
> >
>
> with s
Op Sat, 16 Aug 2014 08:55:27 +0200 schreef Christian PERRIER
:
In short, yes, the first created user (the only one created by D-I) is
added to the "audio" group, among a few others.
with systemd as the default init system. systemd/ logind sets the right
permissions for the sou
(no Cc: to answers, please)
Quoting Floris (jkflo...@dds.nl):
> Dear Debian installation system Maintainers,
>
> I was wondering if a user is still automatically added to the audio group?
> Because it will break a systemd-pulseaudio-multiseat setup.
From user-setup code (in user
Op Fri, 15 Aug 2014 21:35:09 +0200 schreef Lennart Sorensen
:
On Fri, Aug 15, 2014 at 08:59:37PM +0200, Floris wrote:
Dear Debian installation system Maintainers,
I was wondering if a user is still automatically added to the audio
group?
Because it will break a systemd-pulseaudio
On Fri, Aug 15, 2014 at 08:59:37PM +0200, Floris wrote:
> Dear Debian installation system Maintainers,
>
> I was wondering if a user is still automatically added to the audio group?
> Because it will break a systemd-pulseaudio-multiseat setup.
I thought it was still done.
And not do
Dear Debian installation system Maintainers,
I was wondering if a user is still automatically added to the audio group?
Because it will break a systemd-pulseaudio-multiseat setup.
Thanks,
floris
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubs
22 matches
Mail list logo
