linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mangus <ml@deprecated.it>
To: linux-hotplug@vger.kernel.org
Subject: Re: rules and RUN key
Date: Wed, 23 Nov 2005 18:44:19 +0000	[thread overview]
Message-ID: <200511231944.24482.ml@deprecated.it> (raw)
In-Reply-To: <200511230001.45163.ml@deprecated.it>

[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]

Alle 00:18, mercoledì 23 novembre 2005, Kay Sievers ha scritto:
> On Wed, Nov 23, 2005 at 12:01:29AM +0100, Mangus wrote:
> > Hi all, I'm trying to study the RUN key of udev rules, but I really don't
> > understand why this rule doesn't work..
> >
> > BUS=="usb", SYSFS{product}="Sony DSC", KERNEL="sda1", ACTION=="add",
> > SYMLINK+="digitalcamera", RUN="/opt/kde/bin/digikam"
>
> You don't want to run root level programs from udev to show up in your
> desktop session. This also can't work, cause digikam has no X display.
>
yeah, that's right, my fault , thanks

> Usually a process in your user session subscribes to device events from
> HAL and starts applications as the logged-in user.
>
> Kay
ok, but the RUN key is intended to run external script as root, isn't it?
like modprobe commands or whethever
so why this rule don't execute the command?
BUS=="usb", SYSFS{product}=="Sony DSC", KERNEL=="sda1", ACTION=="add", 
SYMLINK+="digitalcamera", RUN+="/sbin/modprobe fuse"

fuse module for example is not loaded
is my version of udev too old?
it's udev64 

thanks

-- 
Fede
Be cool - get Slack.
--

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2005-11-23 18:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-22 23:01 rules and RUN key Mangus
2005-11-22 23:18 ` Kay Sievers
2005-11-23 11:26 ` Harald Hoyer
2005-11-23 18:44 ` Mangus [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200511231944.24482.ml@deprecated.it \
    --to=ml@deprecated.it \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).