Page 3 of 3 FirstFirst 123
Results 21 to 27 of 27

Thread: Writing udev Rules

  1. #21
    Join Date
    Jul 2007
    Location
    Murcia, Spain
    Beans
    33
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: Writing udev Rules

    Running Lucid 64 bits (profile info was outdated)

  2. #22
    Join Date
    Mar 2009
    Beans
    927
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Writing udev Rules

    Sorry people, but I've given up on this how-to and udev in general. I can't even get the 'Hello World!' test to work anymore.

  3. #23
    Join Date
    Jun 2006
    Beans
    106
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: Writing udev Rules

    Thanks for the guide. Really cool.
    I am now able to have my ext drive automatically start xmms2d (using xmms2-launcher fyi).

    Only problem I could see was this line:
    Code:
    drive_uuid=`drive_uuid=`blkid -c /dev/null -o value -s UUID /dev/${drive_kernel}``
    Issnt the double assignment kinda redundant? IIRC it also threw an error on my system.

  4. #24
    Join Date
    Mar 2009
    Beans
    927
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Writing udev Rules

    Quote Originally Posted by TheTank View Post
    Thanks for the guide. Really cool.
    I am now able to have my ext drive automatically start xmms2d (using xmms2-launcher fyi).

    Only problem I could see was this line:
    Code:
    drive_uuid=`drive_uuid=`blkid -c /dev/null -o value -s UUID /dev/${drive_kernel}``
    Issnt the double assignment kinda redundant? IIRC it also threw an error on my system.
    Glad the guide was helpful, thanks for reporting that problem - yes, I think it is indeed majorly erroneous so I've changed it to:
    Code:
    drive_uuid=$(`blkid -c /dev/null -o value -s UUID /dev/${drive_kernel})

  5. #25
    Join Date
    Jun 2006
    Beans
    106
    Distro
    Ubuntu 11.04 Natty Narwhal

    Re: Writing udev Rules

    Small correction: I thought it was starting xmms2d, but that is not the case. But that seems to be more of an issue with launching stuff from the script then with the udev rules.

    Again, thanks!

  6. #26
    Join Date
    May 2012
    Beans
    1

    Re: Writing udev Rules

    I have a question related with this thread. I´m new with linus, so I hope that you can help me and I apologize if my question is stupid or here is not the right place to do it

    I'm writing a new udev for the usb devices. I will only that one in Qt developed program started when the usb is connected.

    I write the USB script and the 91-local.rules and it worked.

    When I modify my USB file to exec my program:

    $/opt/program/# ./SH_Update

    My program works, but I get the next warning:

    (process:4022): GConf-WARNING**: Client failed to connect to the D-BUS daemon: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply time out expired, or the network connection was broken.

    When I connect the USB stick, the program SH_Update doesn't work.

    Have you any Ideas??

    Best

  7. #27
    Join Date
    Mar 2006
    Beans
    90

    Re: Writing udev Rules

    I have the problem that it will first start the script and after finishing the script it will mount my device. When I use SUBSYSTEM==”block”, my device is mounting perfectly, but my script will never start. How can I solve this?

    Smika

Page 3 of 3 FirstFirst 123

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •