Difference between revisions of "Talk:Udev"

From ArchWiki
Jump to: navigation, search
m (Possible to Auto Mount Optical Discs?: Close.)
(Undo revision 353462 by Kynikos (talk) changed my mind)
 
(20 intermediate revisions by 8 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 ==
+
== About udev rules ==
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)
+
  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 [[User:Khampf|Khampf]] ([[User talk:Khampf|talk]]) 20:57, 5 February 2013 (UTC)
  
== <s> Possible to Auto Mount Optical Discs? </s> ==
+
== Use of 'uaccess' instead of GROUP and MODE? ==
Is there a way to auto mount CD and DVDs with Udev? --[[User:Matthewbauer|Matthewbauer]] 23:12, 30 May 2010 (EDT)
+
  
: I think I hacked up a way and added to the page. --[[User:Matthewbauer|Matthewbauer]] 00:16, 31 May 2010 (EDT)
+
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]].
  
: With that rule udev will take a lot longer to "process events" during boot. (+-10s more than without it) --[[User:vieira|Vieira]] 02:20, 26 June 2010 (GMT)
+
Currently, the following rule is taught to the user:
:: These rules are removed. Should be handled by udisk/udisk2. -- [[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 04:34, 13 December 2012 (UTC)
+
  
== Extract the UDisks into new article ==
+
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1781", ATTRS{idProduct}=="0c9f", GROUP="users", MODE="0666"
 +
What about changing it to:
  
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. [[User:Lux|Lux]] ([[User talk:Lux|talk]]) 19:32, 27 July 2012 (UTC)
+
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1781", ATTRS{idProduct}=="0c9f", TAG+="uaccess"
  
:: Agreed 100%. [[User:Sambul13|Sambul13]] 09.40, 03 September 2012 (UTC)
+
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)
 +
 
 +
== Printers ==
 +
 
 +
[[Udev#Printers]]:
 +
 
 +
If you use multiple printers, /dev/lp[0-9] devices will be assigned randomly on boot, which will break e.g. CUPS configuration.
 +
 
 +
I don't use multiple printers, but doesn't {{Pkg|system-config-printer}} handle this automatically? If so, a tip could be added. --[[User:Alad|Alad]] ([[User talk:Alad|talk]]) 08:38, 28 June 2014 (UTC)
 +
 
 +
:It might, unfortunately its {{Pkg|gtk3}} dependency discouraged me from even trying... -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 09:01, 28 June 2014 (UTC)

Latest revision as of 02:40, 27 December 2014

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‎

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)

Printers

Udev#Printers:

If you use multiple printers, /dev/lp[0-9] devices will be assigned randomly on boot, which will break e.g. CUPS configuration.

I don't use multiple printers, but doesn't system-config-printer handle this automatically? If so, a tip could be added. --Alad (talk) 08:38, 28 June 2014 (UTC)

It might, unfortunately its gtk3 dependency discouraged me from even trying... -- Lahwaacz (talk) 09:01, 28 June 2014 (UTC)