Difference between revisions of "Talk:Udev"

From ArchWiki
Jump to: navigation, search
(remove the "automounting usb devices" udev rules ?)
m (udevadm invocation)
(40 intermediate revisions by 10 users not shown)
Line 7: Line 7:
 
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)
 
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)
  
== Possible to Auto Mount Optical Discs? ==
+
== Extract the UDisks into new article ==
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)
+
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)
  
: 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)
+
:: Agreed 100%. [[User:Sambul13|Sambul13]] 09.40, 03 September 2012 (UTC)
  
== Wrong command ==
+
== About udev rules ==
 
+
udevadm info -a -n [device name]
It's not really wrong, just uselessly complex.
+
and
 
  udevadm info -a -p $(udevadm info -q path -n [device name])
 
  udevadm info -a -p $(udevadm info -q path -n [device name])
we are querying a path-based info, passing as parameter a name-based info query. We can obtain the same results with this much more rational command
+
gives the same output but the latter is recommended by some [[User:Khampf|Khampf]] ([[User talk:Khampf|talk]]) 20:57, 5 February 2013 (UTC)
udevadm info -a -n [device name]
+
This is not the only place in the web where I found this strange thing. :/
+
--[[User:4javier|4javier]] 07:14, 24 September 2010 (EDT)
+
 
+
== Obsolete information? ==
+
 
+
Today (Dec 5 2010) I've been following the instruction in the wiki, I've found that udiskie isn't required to autoload CDs/DVSs without HAL, udisks works perfectly without it... only need to explicitly add dbus daemon loading to my rc.conf --[[User:RkG|RkG]] 02:42, 5 December 2010 (EST)
+
 
+
:are you using a DE? udiskie is intended for people without one [[User:Thestinger|thestinger]] 02:54, 5 December 2010 (EST)
+
 
+
::I'm using just a window manager (Xmonad, init-3 level), but installed Gnome also for other members of my family. But really I'm not in a Gnome session :-? --[[User:RkG|RkG]] 00:59, 6 December 2010 (EST)
+
 
+
:::do you use a file manager? pcmanfm and nautilus will both use udev and mount the disks automatically [[User:Thestinger|thestinger]] 13:47, 6 December 2010 (EST)
+
 
+
::::Yes, I'm using pcmanfm... maybe this should be reflected in the wiki as is a very easy option to control removable devices, inside xorg and with any window manager without having to mess with udev rules. Additionally I spawn a command at the begin of my sessions to automount a external 3.5' USB drive permanently plugged to my computer (udisks --mount /dev/sdXX) This "automount" integrates well with pcmanfm, and requires no additional utilities. (Also for pcmanfm compatibility, I need to start my session with "exec ck-launch-session dbus-launch --sh-syntax --exit-with-session $WM") --[[User:RkG|RkG]] 02:17, 7 December 2010 (EST)
+
 
+
== SD cards don't cleanly umount ==
+
 
+
...because the rule as given creates a link: RUN+="/bin/ln -s /media/sd-%k /mnt/sd-%k" which is not deleted on removal. --[[User:Ideopath72|Ideopath72]] 08:44, 18 December 2010 (EST)
+
 
+
== How to match devices like /dev/sdb42 ==
+
 
+
https://bbs.archlinux.org/viewtopic.php?pid=882211#p882211
+
 
+
I'm not and udev guru, but why sometimes it's
+
KERNEL!="sd[a-z][0-9]"
+
and in other examples
+
KERNEL!="sd[a-z]*"
+
?
+
 
+
Why not put
+
KERNEL!="sd[a-z][0-9]*"
+
everywhere?
+
 
+
[[User:Karol|Karol]] 10:11, 23 January 2011 (EST)
+
 
+
:Some devices do not have any partitions, so you also want to match /dev/sdb for example that contains the filesystem in such a case. KERNEL!="sd[a-z]*" is the only expression that works for these ones. [[User:Xduugu|Xduugu]] 09:24, 5 February 2011 (EST)
+
::I actually have such device - it's one of my mp3 players; the other one shows up as sdb1. I couldn't figure out how to make it work until I figured out it's not regexp (where '*' means 'zero or more', so "sd[a-z][0-9]*" would work even for 'sdb'), but a globbing pattern. [[User:Karol|Karol]] 09:49, 5 February 2011 (EST)
+
:::Hey, that is a very nice tip, thanks! We should incorporate this information in the article somehow, I tried to change the pattern like it were a regex, and was very puzzled it didn't work. -- [[User:Nic|Nic]] 11:22, 5 November 2011 (EDT)
+
 
+
== Worth Mentioning? ==
+
In the section on how to prevent wireless and ethernet network devices from switching names would it be worth mentioning that the hardware addresses can also be obtained from ifconfig? It seems a slightly more obvious way of doing it to me.
+
:[http://www.archlinux.org/news/deprecation-of-net-tools/ net-tools (the package that provides ifconfig) was deprecated in favor of iproute2] so probably [https://wiki.archlinux.org/index.php/Requests#net-tools_-.3E_iproute2 that's why it doesn't mention ifconfig].
+
:Please sign the edits you make on the discussion pages. -- [[User:Karol|Karol]] 20:59, 15 July 2011 (EDT)
+
::However, running: {{bc|$ ip addr}} will also give you the MAC address ({{ic|link/ether xx:xx:xx:xx:xx:xx}}) [[User:Axanon|Axanon]] 16:40, 25 March 2012 (EDT)
+
 
+
== remove the "automounting usb devices" udev rules ? ==
+
considering [https://bbs.archlinux.org/viewtopic.php?id=143023 this discussion], I think the whole section should be removed. We shouldn't suggest to people to use this, there are [[Udev#Automounting_UDisks_Wrappers|Udisks Wrappers]] for this. Any objections? [[User:65kid|65kid]] ([[User talk:65kid|talk]]) 11:06, 10 June 2012 (UTC)
+

Revision as of 20:57, 5 February 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.

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. --thayer 16:40, 5 May 2010 (EDT)

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)