On Fri, Apr 16, 2010 at 05:41, David Seikel wrote:
> On Thu, 15 Apr 2010 19:02:01 +0200 Thomas Gstädtner
> wrote:
>
>> On Thu, Apr 15, 2010 at 15:29, William Keaney
>> wrote:
>>
>> So you will still be able to hotplug as user, no problems there at
>> all.
>
> Computers don't usually authenticate
On Thu, 15 Apr 2010 19:02:01 +0200 Thomas Gstädtner
wrote:
> On Thu, Apr 15, 2010 at 15:29, William Keaney
> wrote:
>
> So you will still be able to hotplug as user, no problems there at
> all.
Computers don't usually authenticate the random human, cat, or robot
that actually physically plugs
On Thu, Apr 15, 2010 at 15:29, William Keaney wrote:
> On Wed, Apr 14, 2010 at 11:46 PM, wrote:
>
>> udisks only allows mounting of drives that are in fstab as of now, so
>> it seems like this might be the case. Then again, there are still a
>> few things missing from it so it may just destroy y
On Wed, Apr 14, 2010 at 11:46 PM, wrote:
> udisks only allows mounting of drives that are in fstab as of now, so
> it seems like this might be the case. Then again, there are still a
> few things missing from it so it may just destroy your hopes and dreams
> like hal did :)
>
I actually find thi
On Thu, Apr 15, 2010 at 05:46, wrote:
> udisks only allows mounting of drives that are in fstab as of now, so
> it seems like this might be the case. Then again, there are still a
> few things missing from it so it may just destroy your hopes and dreams
> like hal did :)
>
> I've just finished t
udisks only allows mounting of drives that are in fstab as of now, so
it seems like this might be the case. Then again, there are still a
few things missing from it so it may just destroy your hopes and dreams
like hal did :)
I've just finished the first version of e-udev and it seems to be
worki
On Wed, 14 Apr 2010 12:49:25 -0400 Michael Blumenkrantz
wrote:
> I'm going to be attempting to write a new backend for e_dbus to use
> the new udisks/upower framework which is succeeding hal. Some
> questions I've been mulling over while I've been doing it:
/me hopes that unlike hal, this new s
Hi,
I'm going to be attempting to write a new backend for e_dbus to use the
new udisks/upower framework which is succeeding hal. Some questions
I've been mulling over while I've been doing it:
Should I be migrating all the hal/udev calls to some kind of e_dbus_*
call system so that it will be tr
