From: Dan Armak <danarmak@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] New local use flag for arts: artswrappersuid
Date: Sat, 17 May 2003 10:48:42 +0300 [thread overview]
Message-ID: <200305171048.50798.danarmak@gentoo.org> (raw)
In-Reply-To: <1053127124.11920.16.camel@nosferatu.lan>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 1135 bytes --]
On Saturday 17 May 2003 02:18, Martin Schlemmer wrote:
> On Sat, 2003-05-17 at 00:43, Dan Armak wrote:
> > Hello everyone,
> >
> > I'm adding a new local use flag for kde-base/arts: artswrappersuid. It
> > sets artswrapper suid root, which allows artsd (kde's sound server) to
> > run with realtime priority and avoid skips and clicks, but it's a
> > security hazard, so it's off by default.
>
> Dan, isn't this something that the admin should set for himself ?
> I mean, just adding a USE flag for that, even when local do sound
> a bit excessive ....
Well, isn't whoever emerges KDE (and thus has root perms) the admin of the
box? So now he can do USE=artswrappersuid instead of running chmod +s
manually. The important difference is that you can set the use flag once in
make.conf and forget about it. In my experience, after emerging a new kde I
usually forget to do the chmod manually, start the new kde, get a warning
about no realtime permissions, chmod and restart.
--
Dan Armak
Gentoo Linux developer (KDE)
Matan, Israel
Public GPG key: http://cvs.gentoo.org/~danarmak/danarmak-gpg-public.key
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-05-17 7:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-16 22:43 [gentoo-dev] New local use flag for arts: artswrappersuid Dan Armak
2003-05-16 23:18 ` Martin Schlemmer
2003-05-17 7:48 ` Dan Armak [this message]
2003-05-17 13:48 ` Grant Goodyear
2003-05-17 16:50 ` Martin Schlemmer
2003-05-17 18:49 ` Dan Armak
2003-05-17 19:47 ` torbenh
2003-05-20 9:27 ` Václav Hůla
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=200305171048.50798.danarmak@gentoo.org \
--to=danarmak@gentoo.org \
--cc=gentoo-dev@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox