archive attached
On Wed, Oct 28, 2009 at 12:31:08AM +0100, gibbo...@gmail.com wrote:
[...]
devkit-disks-trigger.tar.gz
Description: Binary data
___
devkit-devel mailing list
devkit-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinf
Hi again,
I still keep my noise restricted to this thread.
typo in :
- DeviceKit-disks.7.html
DKD_PRESENTATION_NAME
The name to user for the device when presenting it to the user.
=>
The name to use for the device when presenting it to the user.
and trivial changes :
- Like device_file_by_path
Sorry, litlle type mistakes:
Stef Bon wrote:
I wrote
> after creating the directory in the "shadow" directory:
>
> mkdir -p $HOME/Workspace/Devices/USBstick
>
it should be:
after creating the directory in the "shadow" directory:
mkdir -p $HOME/.fuse/shadow/Devices/USBstick
Futher I wrote:
gibbo...@gmail.com wrote:
>>
> DKD handle several mountpaths (char **), so does my code (comma separated) :
> if one of specified path matches one the mountpath of the newly mounted device
> (which I recall, can be mounted by automounter, user, root, udev, ...)
> The the value of DeviceMounted is e
Hello,
On Wed, Oct 14, 2009 at 10:39:42AM +0200, Stef Bon wrote:
> Hello Raph,
>
> I'm sorry to say, but your email is too technical (complicated) for me.
> I'll go through your answer checking what you mean:
I'm really sorry, I was to quick to write, and wrote as if you wanted to
understand the
Hello Raph,
I'm sorry to say, but your email is too technical (complicated) for me.
I'll go through your answer checking what you mean:
gibbo...@gmail.com wrote:
> Hi Stef,
> From what I uinderstand, udev is to low-level.
>
Too low-level. For what??
> My 1st goal is to get all devices (known
Hi Stef,
>From what I uinderstand, udev is to low-level.
My 1st goal is to get all devices (known and unknown) automounted.
Then, to let a user spawn any action for any block device event
(added, removed, mounted, unmounted)
1) I have set all the rules for my known hardware in the fstab
so users h
Hello,
your idea of per-user udev subset is great. I've been working on a
construction
which makes access to network- and hardware resources available in a
directory
in your homedirectory and not a foreign place like /mnt or /media.
The latest construction is using the automounter and a fuse mo
attachment
dkd_actions.tar.gz
Description: Binary data
___
devkit-devel mailing list
devkit-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/devkit-devel
Hi,
I attempted to do what I wanted.
(just a POF, but I'm still without any advice
about the correct way to do)
So here comes 11k of noobish-bloated code which :
- parse some config files of this format (GKeyFile) :
[spec]
name=this_device
event=DeviceMounted
exec=echo ADDED docus >> /tmp/dk.log
On Sat, Oct 03, 2009 at 07:24:08AM +0100, Scott James Remnant wrote:
> On Tue, 2009-09-29 at 11:47 +0200, gibbo...@gmail.com wrote:
>
> > ** What I want : **
> > I want the ability for a simple user to set ANY action
> > automatically done according to device events ...
> > with the "state-of-art"
On Tue, 2009-09-29 at 11:47 +0200, gibbo...@gmail.com wrote:
> ** What I want : **
> I want the ability for a simple user to set ANY action
> automatically done according to device events ...
> with the "state-of-art" way to think the device events.
>
This is a major goal of Upstart: http://upsta
As no answer has (yet) been given,
I would like to rewrite differently my
thoughts :
I want to give a simple user the ability the do
something when a block subsystem event happens.
1) with udev it means using libudev and rewriting a udev subset
2) with hal it means "hook"ing a helper in a policy
Hello,
I'm new to this list, a bit curious about udev and the upper
layers. I have some questions, not too dumb I wish.
- re-expliciting to understand myself -
** What I want : **
I want the ability for a simple user to set ANY action
automatically done according to device events ...
with
14 matches
Mail list logo
