On Sat, 28 Jan 2012, Samuli Suominen wrote:
This is definitely not an improvement and should be reverted. The
suid root is also needed to elevate cdrecord's scheduling priority.
Missed that piece of code and reverted then. Any chance you could be
more specific?
cdrecord calls mlock(2),
On Sat, 28 Jan 2012 03:07:45 +0200
Samuli Suominen ssuomi...@gentoo.org wrote:
On 01/28/2012 02:41 AM, Mike Frysinger wrote:
On Friday 27 January 2012 19:18:07 Samuli Suominen wrote:
On 01/28/2012 02:14 AM, Mike Frysinger wrote:
along these lines, why is cdrtools set*id ? if we have a
On 01/28/2012 10:32 AM, Michał Górny wrote:
On Sat, 28 Jan 2012 03:07:45 +0200
Samuli Suominenssuomi...@gentoo.org wrote:
On 01/28/2012 02:41 AM, Mike Frysinger wrote:
On Friday 27 January 2012 19:18:07 Samuli Suominen wrote:
On 01/28/2012 02:14 AM, Mike Frysinger wrote:
along these lines,
On 01/28/2012 02:14 AM, Mike Frysinger wrote:
hmm, i wonder why mount.nfs is set*id. if we require everyone to use `mount`,
there's no need for `mount.nfs` to be set*id. someone want to point out
something obvious that i'm missing before i adjust the nfs-utils package ?
along these lines, why
On Friday 27 January 2012 19:18:07 Samuli Suominen wrote:
On 01/28/2012 02:14 AM, Mike Frysinger wrote:
along these lines, why is cdrtools set*id ? if we have a cdrom group,
and we assign our cdroms/dvdroms to that group, then we already have
access control in place and can skip the
On 01/28/2012 02:41 AM, Mike Frysinger wrote:
On Friday 27 January 2012 19:18:07 Samuli Suominen wrote:
On 01/28/2012 02:14 AM, Mike Frysinger wrote:
along these lines, why is cdrtools set*id ? if we have a cdrom group,
and we assign our cdroms/dvdroms to that group, then we already have
Mike Frysinger schrieb:
along these lines, why is cdrtools set*id ? if we have a cdrom group, and
we assign our cdroms/dvdroms to that group, then we already have access
control in place and can skip the set*id.
-mike
From the manpage, In order to be able to use the SCSI transport
subsystem
On Friday 27 January 2012 20:07:45 Samuli Suominen wrote:
On 01/28/2012 02:41 AM, Mike Frysinger wrote:
On Friday 27 January 2012 19:18:07 Samuli Suominen wrote:
On 01/28/2012 02:14 AM, Mike Frysinger wrote:
along these lines, why is cdrtools set*id ? if we have a cdrom
group, and we
On 01/28/2012 03:49 AM, Mike Frysinger wrote:
On Friday 27 January 2012 20:07:45 Samuli Suominen wrote:
On 01/28/2012 02:41 AM, Mike Frysinger wrote:
On Friday 27 January 2012 19:18:07 Samuli Suominen wrote:
On 01/28/2012 02:14 AM, Mike Frysinger wrote:
along these lines, why is cdrtools
On Friday 27 January 2012 20:28:04 Chí-Thanh Christopher Nguyễn wrote:
Mike Frysinger schrieb:
along these lines, why is cdrtools set*id ? if we have a cdrom group,
and we assign our cdroms/dvdroms to that group, then we already have
access control in place and can skip the set*id.
From
On Friday 27 January 2012 20:49:49 Samuli Suominen wrote:
and people have multiple times tried to convince the cdrtools author to
change this, but without success.
the author can be, well, ...
sure, i'm not expecting him to be anything resembling reasonable. but if we
can reduce set*id
On Sat, 28 Jan 2012, Samuli Suominen wrote:
i've improved the situation _a bit_:
+*cdrtools-3.01_alpha06-r1 (28 Jan 2012)
+
+ 28 Jan 2012; Samuli Suominen ssuomi...@gentoo.org
+ +cdrtools-3.01_alpha06-r1.ebuild:
+ Change cdda2wav, cdrecord, readcd and rscsi from suid root to sgid
On 01/28/2012 08:28 AM, Ulrich Mueller wrote:
On Sat, 28 Jan 2012, Samuli Suominen wrote:
i've improved the situation _a bit_:
+*cdrtools-3.01_alpha06-r1 (28 Jan 2012)
+
+ 28 Jan 2012; Samuli Suominenssuomi...@gentoo.org
+ +cdrtools-3.01_alpha06-r1.ebuild:
+ Change cdda2wav, cdrecord,
13 matches
Mail list logo
