Contents

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:

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)

Possible to Auto Mount Optical Discs?

Is there a way to auto mount CD and DVDs with Udev? --Matthewbauer 23:12, 30 May 2010 (EDT)

I think I hacked up a way and added to the page. --Matthewbauer 00:16, 31 May 2010 (EDT)

With that rule udev will take a lot longer to "process events" during boot. (+-10s more than without it) --Vieira 02:20, 26 June 2010 (GMT)

remove the "automounting usb devices" udev rules ?

considering this discussion, I think the whole section should be removed. We shouldn't suggest to people to use this, there are Udisks Wrappers for this. Any objections? 65kid (talk) 11:06, 10 June 2012 (UTC)

+ 1 for me. Normal user should never touch these. However, you'd better leave a link or two about how to write udev rules manully. -- Fengchao (talk) 06:08, 12 June 2012 (UTC)

BTW: As of systemd 185-1, the deleted scripts were broken for NTFS partitions, yielding only "Transport endpoint is not connected". They still worked with classic initscripts, though. -- Misc (talk) 13:29, 20 June 2012 (UTC)

I'll disagree. udisks{1,2} needs PolKit, which I doubt is ever needed for normal setup and almost always is a PITA in configuration by itself. It is needed, though, for big and fat DE such as KDE, Gnome or even XFCE. But not for "home brew" environments. Neither who uses those big DE are going to write udev rules by themselves nor they are to install udisks and wrappers (as KDE, Gnome or XFCE brings their own automounting). As you removed the tips, you deprived those who wants their own setup of valuable information. The discussion you mention just reveals lack of the documentation and examples on UDev rules. ANd you propose just hide the KISS way and expose wrappers and bloatware of PolKit and UDisks. Lux (talk) 18:56, 27 July 2012 (UTC)

I'm with Lux. I spent a while searching for these rules and was sad to see them gone. Maybe a separate wiki page with a link from here? Jaredcasper (talk) 07:04, 30 July 2012 (UTC)

udev rules were never meant to be used for stuff like this, it was an ugly and broken hack. For example the umount rules didn't make any sense because the device was already gone when the rule matched, so there was nothing to unmount. And polkit/udisks is neither bloatware nor hard to configure. It is a single process running in the background and doesn't need any configuration whatsoever as long as you have a proper ConsoleKit session set up (but I guess ConsoleKit is bloatware too...). If you seriously think that these ugly and hacky udev rules are "more KISS" than udisks, I personally can't take you seriously, sorry. 65kid (talk) 09:41, 30 July 2012 (UTC)

I agree with Lux. Numerous users of Plug computers wouldn't install Udisks etc. And Udisks topic should be separated to a new article and only referenced by a link in this complex enough for a novice by itself Udev topic. Unmounting detached devices 'after the fact' in udev-automount rules does make sense to drop handles to now empty folders where they were mounted. If udev can't delete the folder, it remains shared by Samba and users with rw access to then mounted drive can write files to it, which then be replaced by content of the remounted drive. So its data loss threat to leave these folders accessible. Sambul13 09.40, 03 September 2012 (UTC)

Now that systemd is the standard Arch init/session manager, consolekit is no longer required and polkit is built with systemd support this section, and the rules herein, just confuse the issue. They should be scrapped and the entire section rewritten to emphasize (finally) how simple it is to get auto {u}mounting to work Jasonwryan (talk) 20:11, 31 October 2012 (UTC)