Hi Gustavo,
On Mon, Oct 18, 2010 at 3:19 AM, gustavo panizzo
wrote:
>> > d) Create an user "udisks", add a PolicyKit rule to allow it to mount
>> > device files, use that for the init script (not even sure it's
>> > possible)
>> how would it leave the file permissions on the mounted filesystems
> > d) Create an user "udisks", add a PolicyKit rule to allow it to mount
> > device files, use that for the init script (not even sure it's
> > possible)
> how would it leave the file permissions on the mounted filesystems?
> Would them be readable/writable by local users?
i was referring to optio
On Sat, Oct 16, 2010 at 07:13:52PM -0300, Fernando Lemos wrote:
> Hello, mentors
disclaimer: i'm not a DD/DM
> I could make udisks-glue run as another user (say, nobody), but that
> would mean that the default config would not be able to mount devices.
> That's because PolicyKit will only allow ud
Hello, mentors
I'm looking for some advice on my ITP[1]. udisks-glue[2] is a
replacement to some of the functionality provided by halevt/ivman, but
it uses udisks instead of HAL (HAL is not actively maintained
anymore). So I'm trying to package it the same way halevt does it:
providing simple auto
4 matches
Mail list logo
