[opensuse-packaging] How to give the program access to RTC of Alsa Timer?
How to give a program access to /dev/rtc or alsa timer without starting it as root? I made a package with an application which requires this but I do not want to set up it such a way that an ordinary user could not use it. What preparations should I do in the install-time to get it work for any user? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Sat, 8 Jan 2011 21:50:12 +0300, Ilya Chernykh
How to give a program access to /dev/rtc or alsa timer without starting it as root?
I made a package with an application which requires this but I do not want to set up it such a way that an ordinary user could not use it. What preparations should I do in the install-time to get it work for any user?
You should probably also ask on opensuse-security. Philipp -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 01/08/2011 08:50 PM, Ilya Chernykh wrote:
How to give a program access to /dev/rtc or alsa timer without starting it as root?
I made a package with an application which requires this but I do not want to set up it such a way that an ordinary user could not use it. What preparations should I do in the install-time to get it work for any user?
When you find an answer please pass it on to me, I want jack to run in real time when first installed. As pointed out to you, this is considered a security risk. Thanks Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 01/09/2011 03:45 AM, Dave Plater wrote:
On 01/08/2011 08:50 PM, Ilya Chernykh wrote:
How to give a program access to /dev/rtc or alsa timer without starting it as root?
I made a package with an application which requires this but I do not want to set up it such a way that an ordinary user could not use it. What preparations should I do in the install-time to get it work for any user?
When you find an answer please pass it on to me, I want jack to run in real time when first installed. As pointed out to you, this is considered a security risk. Thanks Dave P
Indirectly related, but an interesting read on Jack and kernel settings: http://lwn.net/Articles/420407/ HTH, Peter -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 01/11/2011 11:30 AM, Peter Linnell wrote:
Indirectly related, but an interesting read on Jack and kernel settings: http://lwn.net/Articles/420407/
HTH, Peter
Thanks, it's good to know that a solution for jack is being worked on by the libcgroup people and I know what to look for in case of a problem. Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Hello, when i put the mouse on the section Build Status Reload Status the 'broken' status says 'conflict in file patches.rpmify.tar.bz2' How can the error be fixed? The details can be found at https://build.opensuse.org/package/show?package=kernel-reiser4&project=home%3Adoiggl Any help appreciated. Thanks Glenn The patches.rpmify.tar.bz2 was constructed with these results: # tar -cvf patches.rpmify.tar patches.rpmify patches.rpmify/ patches.rpmify/qla4xx-missing-readq-definition patches.rpmify/easycap-fixes patches.rpmify/rpm-kernel-config patches.rpmify/tioca-fix-assignment-from-incompatible-pointer-warnings patches.rpmify/reiser4-for-2.6.36.patch patches.rpmify/cloneconfig.diff patches.rpmify/ia64-mca-fix-cast-from-integer-to-pointer-warning patches.rpmify/split-package patches.rpmify/buildhost patches.rpmify/reiser4-fix-entd_flush.patch patches.rpmify/firmware-path # bzip2 patches.rpmify.tar # ls patches.rpmify.tar.bz2 patches.rpmify.tar.bz2 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 01/11/2011 11:30 AM, Peter Linnell wrote:
Indirectly related, but an interesting read on Jack and kernel settings: http://lwn.net/Articles/420407/
HTH, Peter -- Having read the subject of this thread again, I think the op actually needs to synchronize with alsa and isn't looking for RT privileges. Having read through the comments in the article you posted the link for, I can now understand that the old school "linux the server" commenters can't see the other "linux the PC" crowds concept at all due to confusion over the use of the word "server" in the jack sense combined with the use of the phrase "real time". I wonder what would need to be done to prove that jack's real time privileges couldn't be used for a denial of service attack or if in fact they could? I posted a long comment in reply to two parties that couldn't communicate well enough to understand each other and then noticed the dates on the comments, the newest one was 22 Dec. so probably nobody will see it. This link gets to my comment : http://lwn.net/Articles/422497/
Regards Dave P -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (5)
-
Dave Plater -
doiggl＠velocitynet.com.au -
Ilya Chernykh -
Peter Linnell -
Philipp Thomas