On Thu, January 26, 2012 2:52 am, Ralf Madorf wrote:
> If you lock the door, you could run into trouble, if the studio catches
> fire and btw. it's a safe bet that somebody will knock at the door. The
I thought of that after.
> A balancing act regarding to the realtime group issue isn't worse t
On Wed, 2012-01-25 at 17:52 -0800, Len Ovens wrote:
> On Tue, January 24, 2012 8:37 pm, David Henningsson wrote:
>
> > One of the advantages of Linux is that the line between "single user
> > system" and "multi user system" is blurry. E g, I could run a web server
> > or other service on the same
On Tue, January 24, 2012 8:37 pm, David Henningsson wrote:
> One of the advantages of Linux is that the line between "single user
> system" and "multi user system" is blurry. E g, I could run a web server
> or other service on the same machine as I use for audio production. This
> is great, it sa
On 2012-01-25 05:37, David Henningsson wrote:
If Ubuntu Studio wants to be insecure in that sense, I guess that would
be okay (to me personally, I can't speak for Ubuntu's security team),
but I would definitely not have it in the Ubuntu by default.
It is not audio group (or whatever it may be
On 01/24/2012 04:15 PM, Ralf Madorf wrote:
On Tue, 2012-01-24 at 09:48 +0100, David Henningsson wrote:
Or possibly one could add some kind of script that would give RT prio to
the current logged in user (and remove it if the user logs out)?
So you assume that there never will be more than one
On Tue, 2012-01-24 at 09:48 +0100, David Henningsson wrote:
> Or possibly one could add some kind of script that would give RT prio to
> the current logged in user (and remove it if the user logs out)?
So you assume that there never will be more than one user be logged in?
There's no need to remo
On 2012-01-24 10:51, Kaj Ailomaa wrote:
On 2012-01-24 09:48, David Henningsson wrote:
Is there an "Ubuntu Studio Controls" application still around? If so,
that might be the right place to aid with this.
Or possibly one could add some kind of script that would give RT prio to
the current logged
On 2012-01-24 09:48, David Henningsson wrote:
Is there an "Ubuntu Studio Controls" application still around? If so,
that might be the right place to aid with this.
Or possibly one could add some kind of script that would give RT prio to
the current logged in user (and remove it if the user logs
On 01/23/2012 09:12 AM, Kaj Ailomaa wrote:
On 2012-01-22 21:08, David Henningsson wrote:
On 01/21/2012 06:41 PM, Len Ovens wrote:
There was some discussion on the IRC channel that got me thinking about
this. Ubuntu's standard position on use of the audio group is here:
https://wiki.ubuntu.com/A
On 2012-01-22 21:08, David Henningsson wrote:
On 01/21/2012 06:41 PM, Len Ovens wrote:
There was some discussion on the IRC channel that got me thinking about
this. Ubuntu's standard position on use of the audio group is here:
https://wiki.ubuntu.com/Audio/TheAudioGroup
After having cleaned th
On 01/21/2012 06:41 PM, Len Ovens wrote:
There was some discussion on the IRC channel that got me thinking about
this. Ubuntu's standard position on use of the audio group is here:
https://wiki.ubuntu.com/Audio/TheAudioGroup
After having cleaned that page up a bit (something strange was recentl
On Sun, January 22, 2012 5:17 am, Ralf Madorf wrote:
> Hi Kaj :)
>
> I'll continue top posting ;).
>
> To be honest, I can't see any disadvantage to set every user to the
> group audio, but I might have miss something.
>
> Why do we have a group "audio"? Perhaps there's a valid reason not to
> set
On Sat, January 21, 2012 7:04 pm, Kaj Ailomaa wrote:
>> Having the option of administrating groups will of course always remain,
>> but from my point of view, a distro like UbuntuStudio should have audio
>> group as a default group for both the desktop and administrator users.
>> Not having that
I'm going to ask around. I've sent a mail to the multimedia package mail
list for Debian.
Where would be the best place to adress this?
Don't know how fast such a change would find it's way over to Ubuntu
repo. jackd2 1.9.8 is now in Debian unstable, I believe.
If it is achievable to solve this
Hi Kaj :)
I'll continue top posting ;).
To be honest, I can't see any disadvantage to set every user to the
group audio, but I might have miss something.
Why do we have a group "audio"? Perhaps there's a valid reason not to
set every user to the group audio. I don't know.
Regards,
Ralf
On Sun
Only an admin is allowed to install programs, and if the admin would be
given a choice to include users to audio group during installation of a
package (you can always answer no), than what is the problem? You'll
have to do it anyway if you are intending to get realtime privilege
(though many w
On Sun, 2012-01-22 at 03:58 +0100, Kaj Ailomaa wrote:
> My point in bringing up this problem with audio group was that new users
> (who wouldn't know about audio group) shouldn't have to create a new
> user and find that the new user cannot use audio applications in realtime.
> Having the option
And sorry for not bringing up the problem with what implications audio
group presents to the system.
But, it seems to me whatever problems it presents, those are totally
unavoidable for audio users.
If adding the user to audio group is checked during installation of some
package it should be eno
My point in bringing up this problem with audio group was that new users
(who wouldn't know about audio group) shouldn't have to create a new
user and find that the new user cannot use audio applications in realtime.
Having the option of administrating groups will of course always remain,
but fr
On Sat, January 21, 2012 10:41 am, Ralf Madorf wrote:
> On Sat, 2012-01-21 at 09:41 -0800, Len Ovens wrote:
>> The installing user is both admin and sound engineer
>
> IIRC only the first user is admin, any additional user isn't!
The GUI user creator allows creating more admin accounts. It in fac
On Sat, 2012-01-21 at 09:41 -0800, Len Ovens wrote:
> The installing user is both admin and sound engineer
IIRC only the first user is admin, any additional user isn't!
--
Ubuntu-Studio-devel mailing list
Ubuntu-Studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubu
On Sat, 2012-01-21 at 19:31 +0100, Ralf Madorf wrote:
> On Sat, 2012-01-21 at 09:41 -0800, Len Ovens wrote:
> > Does any of this make sense? Or am I crazy?
>
> Hahaha, neither or nor. You aren't an idiot, but it anyway isn't ideal.
> Sessions should be usable on different distros, since I'm switch
On Sat, 2012-01-21 at 09:41 -0800, Len Ovens wrote:
> Does any of this make sense? Or am I crazy?
Hahaha, neither or nor. You aren't an idiot, but it anyway isn't ideal.
Sessions should be usable on different distros, since I'm switching
between distros, I prefer to have distros as similar/equal a
On Sat, January 21, 2012 9:41 am, Len Ovens wrote:
> My thought is that at install there would be an extra user created called
> project. No password needed. This would create /home/project.
Just5 to clarify. "No password needed" means "not able to log in" not the
same as guest...
--
Len Oven
There was some discussion on the IRC channel that got me thinking about
this. Ubuntu's standard position on use of the audio group is here:
https://wiki.ubuntu.com/Audio/TheAudioGroup
While this does not apply to UbuntuStudio, there are some side effects of
using the audio group in any case. Curre
25 matches
Mail list logo
