On 03/05/2013 03:34 PM, Ivan Lezhnjov Jr. wrote:
That was directly in response to commit commentary.
You might want to see these to understand where I'm coming from:
http://lists.freedesktop.org/archives/devkit-devel/2013-February/001354.html
And there was also another message like mine approxi
On 03/05/2013 05:28 AM, Phillip Susi wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/04/2013 11:18 PM, Michael Biebl wrote:
http://cgit.freedesktop.org/udisks/commit/?id=6ae6c19ad981801d08f3f5b59c0301ed3fe8b7b4
I guess this is not quite what you are asking for, but get's
close.
N
On 05/09/2012 01:08 PM, Christopher Chittleborough wrote:
> On Sun, May 6, 2012, at 12:57 PM, Stef Bon wrote:
>> Hi,
>>
>> when enumerating and monitoring devices from udev, I would like to program
>> whether the device (block, when a disk) there are partitions or not p
Hi,
when enumerating and monitoring devices from udev, I would like to program
whether the device (block, when a disk) there are partitions or not present.
Howto do this? Is this possible in udev or do I have to use udisks(2)??
Stef
___
devkit-devel
On 01/24/2012 06:22 PM, David Zeuthen wrote:
> Hey,
>
> I spun the release on Friday but didn't get around to do the
> announcement until now, sorry. Anyway, here's the first release of
> udisks2! Not a lot to say expect that it's a complete rewrite of the
> udisks1 codebase with a more modern, int
Hi,
I'm looking for a good way to program the open (with or without media)
and close the tray
of a cdrom.
It looks like there is no single command to do that.
eject /dev/sr0
works when door is closed, simular to
udisks --eject /dev/sr0
(eventual media is not mounted)
but when door is open
The only other relevant var is SUBSYSTEM=bdi.
Thanks in advance,
Stef Bon
___
devkit-devel mailing list
devkit-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/devkit-devel
lot for you answers!
Stef Bon
Voorburg
the Netherlands
___
devkit-devel mailing list
devkit-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/devkit-devel
On 10/04/2010 06:41 PM, Kay Sievers wrote:
On Mon, Oct 4, 2010 at 17:42, Kay Sievers wrote:
On Mon, Oct 4, 2010 at 17:30, Stef Bon wrote:
To be sure, the command
udisk --poll-for-media /dev/sr0
results in:
:> ps aux | grep udisks | grep -v grep
root 2792 0.0 0.0 14408 3
On 10/04/2010 05:13 PM, Kay Sievers wrote:
On Mon, Oct 4, 2010 at 17:05, Stef Bon wrote:
But still stays why not:
udisks --poll-for-removeable-media
in stead of
udisks --poll-for-media /dev/sr0
That's a one-shot command, not a switch to enable something in the
daemon that keeps po
On 10/04/2010 04:31 PM, Kay Sievers wrote:
On Mon, Oct 4, 2010 at 16:14, Stef Bon wrote:
On 10/04/2010 03:03 PM, David Zeuthen wrote:
I see also a difference in the way udev handles cdroms. cdroms inserted or
ejected are reported as change, while an inserted usb stick is reported as
adding
On 10/04/2010 03:03 PM, David Zeuthen wrote:
Hi,
For the record, the docs are located here
http://hal.freedesktop.org/docs/udisks/
Also note that the ABI of the udisks(1) binary isn't considered
stable. The D-Bus ABI has some stability gurantees, see the README
file.
Thanks a lot for your
ndles
everything correct right, so why does udisks bother?
Stef Bon
Voorburg
___
devkit-devel mailing list
devkit-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/devkit-devel
Hello,
I've been trying to get the following issue earlier, like here:
http://lists.freedesktop.org/archives/devkit-devel/2009-October/000457.html
HAL (and maybe udiks, I do not know, I haven't tried it yet) mounts
devices at /media, with the user using the
computer as the owner of everything
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/De
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
er mountpath
> # choice 2 : the mount part is done by root, or udev
> # so we only do stuff at post-mount time
> DeviceMounted=mirage %device_mount_paths
>
What;s this mirage thing??
Please note that not everybody has the same skills as you when
answering... make your emails a little
chine (and with multiseat this is possible), and you don't
want that!
The only sollution is per-user rules.
I do not understand your goal exactly, and the reason that you want
per-user rules is maybe
another I want it.
Stef Bon
gibbo...@gmail.com wrote:
> Hi,
> I attempted to do wh
Kay Sievers wrote:
> On Fri, May 29, 2009 at 15:31, Stef Bon wrote:
>
>
>> Is there some other way to tell the new devkit for disks not to ignore
>> the disk, but not to mount it
>>
>
> The policy is in your user session, not at the system level, just li
ntroduces other problems by the way, when working in an multi user
environment like multihead.
But what do you think?
Stef Bon
___
devkit-devel mailing list
devkit-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/devkit-devel
Well, if any user has USB disks mounted somewhere in his/her
homedirectory, the desktopenvironment should use this mountpoint in
stead of the general mountpoint at /media.
Anyone understands what I mean?
Stef Bon
Stef Bon wrote:
>
>
> the same device is mounted at two places:
&
d with the
desktopenvironment, for user2
only the second. And what about inactive sessions?
Looking forward to your reaction,
Stef Bon
___
devkit-devel mailing list
devkit-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/devkit-devel
22 matches
Mail list logo
