Difference between revisions of "Talk:Udev"

From ArchWiki
Jump to: navigation, search
(udevadm invocation: new section)
m (umask fails to apply to vfat/ntfs partitions: rm old, unrelated question; fstab#Writing to FAT32 as Normal User mentions it now)
(4 intermediate revisions by 3 users not shown)
Line 2: Line 2:
 
In the udev rules for usbtiny, there are 2 rules listed.  Howver, adding the second one to my udev rules resulted in me not an "rc=-1" communication error when I tried to use my usbtiny.  When I commented out this rule:
 
In the udev rules for usbtiny, there are 2 rules listed.  Howver, adding the second one to my udev rules resulted in me not an "rc=-1" communication error when I tried to use my usbtiny.  When I commented out this rule:
 
  "SBSYSTEMS=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="0479", GROUP="users", MODE="0666"
 
  "SBSYSTEMS=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="0479", GROUP="users", MODE="0666"
everything worked fine. Not sure what the root of the issue is, but this rule makes the usbtiny programer unusable.
+
everything worked fine. Not sure what the root of the issue is, but this rule makes the usbtiny programer unusable. -- [[User:Ssalenik|Ssalenik]] ([[User talk:Ssalenik|talk]]) 04:09, 6 March 2012‎
 
+
== umask fails to apply to vfat/ntfs partitions ==
+
Has anyone else found that umask settings do not apply as they should?  Setting umask to 002 or 0002 results in all files having the executable bit enabled. However, if I manually set the fmask/dmask values (ex: fmask=113,dmask=002) it works fine. --[[User:Thayer|thayer]] 16:40, 5 May 2010 (EDT)
+
  
 
== Extract the UDisks into new article ==
 
== Extract the UDisks into new article ==
Line 12: Line 9:
  
 
:: Agreed 100%. [[User:Sambul13|Sambul13]] 09.40, 03 September 2012 (UTC)
 
:: Agreed 100%. [[User:Sambul13|Sambul13]] 09.40, 03 September 2012 (UTC)
 
== udevadm invocation ==
 
  
 
== About udev rules ==
 
== About udev rules ==
Line 20: Line 15:
 
  udevadm info -a -p $(udevadm info -q path -n [device name])
 
  udevadm info -a -p $(udevadm info -q path -n [device name])
 
gives the same output but the latter is recommended by some [[User:Khampf|Khampf]] ([[User talk:Khampf|talk]]) 20:57, 5 February 2013 (UTC)
 
gives the same output but the latter is recommended by some [[User:Khampf|Khampf]] ([[User talk:Khampf|talk]]) 20:57, 5 February 2013 (UTC)
 +
 +
== Use of 'uaccess' instead of GROUP and MODE? ==
 +
 +
Bug [https://bugs.archlinux.org/task/35602 openobex - relies on non-existing group plugdev, conflict with systemd] made me rethink the rules I have been using for [[Logitech_Unifying_Receiver]].
 +
 +
Currently, the following rule is taught to the user:
 +
 +
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1781", ATTRS{idProduct}=="0c9f", GROUP="users", MODE="0666"
 +
What about changing it to:
 +
 +
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1781", ATTRS{idProduct}=="0c9f", TAG+="uaccess"
 +
 +
As a developer note, Ubuntu versions before 13.04 Raring needs {{ic|<nowiki>TAG+="udev-acl"</nowiki>}} instead of uaccess. For compatibility with modern and legacy systems:
 +
 +
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1781", ATTRS{idProduct}=="0c9f", TAG+="uaccess", TAG+="udev-acl"
 +
 +
References:
 +
* http://cgit.freedesktop.org/systemd/systemd/tree/src/login/70-uaccess.rules
 +
[[User:Lekensteyn|Lekensteyn]] ([[User talk:Lekensteyn|talk]]) 10:16, 6 June 2013 (UTC)

Revision as of 10:20, 20 August 2013

usbtiny extra udev rule?

In the udev rules for usbtiny, there are 2 rules listed. Howver, adding the second one to my udev rules resulted in me not an "rc=-1" communication error when I tried to use my usbtiny. When I commented out this rule:

"SBSYSTEMS=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="0479", GROUP="users", MODE="0666"

everything worked fine. Not sure what the root of the issue is, but this rule makes the usbtiny programer unusable. -- Ssalenik (talk) 04:09, 6 March 2012‎

Extract the UDisks into new article

As UDev is more generic than just disk mounting subsystem, I propose to extract the UDisks part into its own page to keep things simple and clear. Lux (talk) 19:32, 27 July 2012 (UTC)

Agreed 100%. Sambul13 09.40, 03 September 2012 (UTC)

About udev rules

udevadm info -a -n [device name]

and

udevadm info -a -p $(udevadm info -q path -n [device name])

gives the same output but the latter is recommended by some Khampf (talk) 20:57, 5 February 2013 (UTC)

Use of 'uaccess' instead of GROUP and MODE?

Bug openobex - relies on non-existing group plugdev, conflict with systemd made me rethink the rules I have been using for Logitech_Unifying_Receiver.

Currently, the following rule is taught to the user:

SUBSYSTEMS=="usb", ATTRS{idVendor}=="1781", ATTRS{idProduct}=="0c9f", GROUP="users", MODE="0666"

What about changing it to:

SUBSYSTEMS=="usb", ATTRS{idVendor}=="1781", ATTRS{idProduct}=="0c9f", TAG+="uaccess"

As a developer note, Ubuntu versions before 13.04 Raring needs TAG+="udev-acl" instead of uaccess. For compatibility with modern and legacy systems:

SUBSYSTEMS=="usb", ATTRS{idVendor}=="1781", ATTRS{idProduct}=="0c9f", TAG+="uaccess", TAG+="udev-acl"

References:

Lekensteyn (talk) 10:16, 6 June 2013 (UTC)