On Wed, Apr 4, 2012 at 2:32 AM, justin wrote:
> 2.
> suid it (bad in my view)
> 3.
> file capabilities (can this be done with portage)
>
iotop is a python script, so these were not really options anyway.
Unless you wrote a wrapper in C or something. :)
On 04/04/12 14:56, Greg KH wrote:
> On Wed, Apr 04, 2012 at 08:32:41AM +0200, justin wrote:
>> Hi,
>>
>> after this change
>>
>> https://github.com/torvalds/linux/commit/1a51410abe7d0ee4b1d112780f46df87d3621043
>>
>> iotop cannot be used as user anymore.
>> Any suggestions how to proceed?
>>
>> Th
On Wed, Apr 04, 2012 at 08:32:41AM +0200, justin wrote:
> Hi,
>
> after this change
>
> https://github.com/torvalds/linux/commit/1a51410abe7d0ee4b1d112780f46df87d3621043
>
> iotop cannot be used as user anymore.
> Any suggestions how to proceed?
>
> The solution I see are
>
> 1.
> Leave it to
On Wed, 04 Apr 2012 08:32:41 +0200
justin wrote:
> 3.
> file capabilities (can this be done with portage)
It can't. We've had discussions about caps before, and I imagine it
would get into EAPI 5 without objections if you can come up with a spec
that describes how it should work (bear in mind tha
2012/4/4 Chí-Thanh Christopher Nguyễn :
> justin schrieb:
>> iotop cannot be used as user anymore.
>> Any suggestions how to proceed?
>>
>> Leave it to root (Fedora and Suses way)
>> suid it (bad in my view)
>
> I suggest to have a suid USE flag (disabled by default) so the user can
> choose betwee
justin schrieb:
> iotop cannot be used as user anymore.
> Any suggestions how to proceed?
>
> Leave it to root (Fedora and Suses way)
> suid it (bad in my view)
I suggest to have a suid USE flag (disabled by default) so the user can
choose between the two. Maybe advertise this change in an elog me
Il 04/04/2012 08:43, "Paweł Hajdan, Jr." ha scritto:
On 4/4/12 8:32 AM, justin wrote:
1.
Leave it to root (Fedora and Suses way)
I think that's the best option, at least for now.
2.
suid it (bad in my view)
Agreed, that'd be very bad, any crashing bug in it could become a
privilege escalatio
On 4/4/12 8:32 AM, justin wrote:
> 1.
> Leave it to root (Fedora and Suses way)
I think that's the best option, at least for now.
> 2.
> suid it (bad in my view)
Agreed, that'd be very bad, any crashing bug in it could become a
privilege escalation problem.
> 3.
> file capabilities (can this be
Hi,
after this change
https://github.com/torvalds/linux/commit/1a51410abe7d0ee4b1d112780f46df87d3621043
iotop cannot be used as user anymore.
Any suggestions how to proceed?
The solution I see are
1.
Leave it to root (Fedora and Suses way)
2.
suid it (bad in my view)
3.
file capabilities (can
