From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NAfjC-0001BQ-NH for garchives@archives.gentoo.org; Wed, 18 Nov 2009 08:17:27 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8CEBBE0ACC; Wed, 18 Nov 2009 08:17:12 +0000 (UTC) Received: from mail-pz0-f174.google.com (mail-pz0-f174.google.com [209.85.222.174]) by pigeon.gentoo.org (Postfix) with ESMTP id 4B8CBE0ACC for ; Wed, 18 Nov 2009 08:17:12 +0000 (UTC) Received: by pzk4 with SMTP id 4so609119pzk.32 for ; Wed, 18 Nov 2009 00:17:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=P+1N7fKRZk5Gj2vaX8vaCQAQsrg5JgvBiwtDe5Lvf1Y=; b=FfTQ/hv3mynrohMXXLha9IqBAe0OMQz89fBwczafHPIRwsEVR0JF6XpWPW/prz9J4H yA9YtRKk/FNSSf87kdrJ5u97obLSxFxFs0ScBweojYoz6M6HitQtHWRwjQfi4OIJ9lqF w6lJ51HAsVkLboebqP5k7kRmSLfQsYhcm1Ibg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=r/HtH3QdUmv0nJGoNh3+u9NKCh10o/t0p5mvhxNeEcFckZpXuvcVjYJBCU56dah3l7 zzE/Ilr80hEQJMtwC4vvJZ18nwkq9kCWN61SpstGphdtVpCRsTyYWtWwIAsOQuj2jZmg aPr09gIR16OUpuJWBd+J+/EIM61xYxsiqmxzs= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.142.4.11 with SMTP id 11mr1283119wfd.86.1258532231882; Wed, 18 Nov 2009 00:17:11 -0800 (PST) In-Reply-To: <4B03602F.4010705@myfairpoint.net> References: <4B03602F.4010705@myfairpoint.net> Date: Wed, 18 Nov 2009 17:17:11 +0900 Message-ID: <3ac129340911180017x6bad487ev8cd05be18c9242e7@mail.gmail.com> Subject: Re: [gentoo-user] USB auto mounting From: daid kahl To: gentoo-user@lists.gentoo.org Content-Type: multipart/mixed; boundary=00504502b8699ea8420478a0ded3 X-Archives-Salt: 5268efd1-8b6c-4173-9a01-5df6adaf7577 X-Archives-Hash: b499882b26adc06f9b543ec6d6106dcb --00504502b8699ea8420478a0ded3 Content-Type: text/plain; charset=ISO-8859-1 > Using Windowmaker with Thunar as a file manager, with the volume manager > in place and that plugin is enabled. > > For some reason Thunar is now not seeing any USB device when plugged > in. I am not sure when this stopped working. > > My USB devices of keyboard, trackball, and webcam are working fine. > If I "lsusb" I can see the flash drive listed when inserted. > > I have tried re-emerging various items hoping that it would bring it > back to life. Obviously no luck since I am posting. > > Would anyone have any ideas on a possible cause and cure? I'm also using xfce & thunar, but I've not setup any auto-mounting yet. So, I don't have any wisdom on the ground of getting back your old functionality. However, there is a reasonable alternative solution that might be more elegant, and also not dependent on your desktop, which is to use udev. Generally speaking, for my approach here, this isn't good for automounting any random device. However, for your standard devices, you can do things like collecting the usb serial number. The upside of this (and the reason I use it), is that for your standard USB storage devices, you can mount each one uniquely to any specified mount point. This is useful for things like backup to USB harddisk that you want mounted to the same point for, in my case, rsnapshot. (This is otherwise more difficult, since automounting without serial ID will just take the first usb drive connected and mount it somewhere in /media usually.) My usb camera is also mounted in such a manner, so that will also work. I assume a keyboard could be done likewise. In case this route is of interest, I will syndicate parts of a post I made to the list in October: To get the serial of a device, for this example, the device node /dev/sdb (which might be a USB key considered as a SATA drive here): # udevadm info -a -p $(udevadm info -q path -n /dev/sdb) | grep ATTRS{serial} You might get more than one return on this command. Us the first serial, and it is also the one without colons or periods, just numbers and letters. I include my own configuration files. The .rules config files should go into /etc/udev/rules.d and the scripts should be made executable and go under /etc/udev/scripts/ For a harddrive, then, you can make the directory in /mnt and put it into fstab /dev/cyclops /mnt/cyclops ext3 rw,users 0 0 The system will complain on boot that it can't find the drive if it's not attached, but it won't do any harm as it's just a warning. PLEASE NOTE: For udev rules, each *new line* is considered as a *new rule*, thus for the same device, make sure there are no carriage returns. This could happen if you were Googling your hardware for udev rules and copy-pasting the udev rules from a web-browser (as not all sites will properly handle the carriage returns). Hope this helps, even if it is an alternative solution and doesn't tell you what happened to your system or why. ~daid --00504502b8699ea8420478a0ded3 Content-Type: application/octet-stream; name="10-local.rules" Content-Disposition: attachment; filename="10-local.rules" Content-Transfer-Encoding: base64 X-Attachment-Id: f_g25tcxi90 IyBpU2lnaHQKIFNVQlNZU1RFTT09InZpZGVvNGxpbnV4IiwgRFJJVkVSUz09InVzYiIsIEFUVFJT e3Byb2R1Y3R9PT0iQnVpbHQtaW4gaVNpZ2h0IiwgQVRUUlN7bWFudWZhY3R1cmVyfT09Ik1pY3Jv biIsIFNZTUxJTksrPSJ2NGwvaXNpZ2h0IgojIGV4dGVybmFsIFVTQiwgU2VhZ2F0ZSBGcmVlQWdl bnQgR08gYWthIGN5Y2xvcHMKIFNVQlNZU1RFTVM9PSJ1c2IiLCBEUklWRVJTPT0idXNiIiwgQVRU UlN7c2VyaWFsfT09IiAgICAgICAgICAgIDVMWjJYUUo1IiwgU1lNTElOSys9ImN5Y2xvcHMiIEFD VElPTj09ImFkZCIsIFJVTis9Ii9ldGMvdWRldi9zY3JpcHRzL21vdW50X2N5Y2xvcHMuc2giCiMg ZXh0ZXJuYWwgVVNCLCBLaW5nc3RvbiAyR0IgZmxhc2ggdGh1bWJkcml2ZSBha2EgYmVsbGUKIFNV QlNZU1RFTVM9PSJ1c2IiLCBEUklWRVJTPT0idXNiIiwgQVRUUlN7c2VyaWFsfT09IjAyMDAwMDAw MDAwMjZBIiwgU1lNTElOSys9ImJlbGxlIiBBQ1RJT049PSJhZGQiLCBSVU4rPSIvZXRjL3VkZXYv c2NyaXB0cy9tb3VudF9iZWxsZS5zaCIK --00504502b8699ea8420478a0ded3 Content-Type: application/octet-stream; name="isight.rules" Content-Disposition: attachment; filename="isight.rules" Content-Transfer-Encoding: base64 X-Attachment-Id: f_g25tfj8a1 QUNUSU9OPT0iYWRkIiwgU1lTRlN7aWRWZW5kb3J9PT0iMDVhYyIsIFNZU0ZTe2lkUHJvZHVjdH09 PSI4NTAxIiwgUlVOKz0iL3Vzci9saWIvdWRldi9pZnQtbG9hZCAtYiAwMDEgLWQgMDA0IC0tZmly bXdhcmUgL2xpYi9maXJtd2FyZS9pc2lnaHQuZnciIAo= --00504502b8699ea8420478a0ded3 Content-Type: application/x-sh; name="mount_cyclops.sh" Content-Disposition: attachment; filename="mount_cyclops.sh" Content-Transfer-Encoding: base64 X-Attachment-Id: f_g25tg01s2 IyEvYmluL2Jhc2gKI21vdW50IFNlYWdhdGUgRnJlZUFnZW50IEdvIHdpdGggc2VyaWFsIDVMWjJY UUo1IHRvIC9tbnQvY3ljbG9wcyBvbiBBQ1RJT049J2FkZCcKbW91bnQgLXQgZXh0MyAvZGV2L2N5 Y2xvcHMgL21udC9jeWNsb3BzCmNob3duIHJvb3Q6dXNlcnMgL21udC9jeWNsb3BzCmNobW9kIDc3 NSAvbW50L2N5Y2xvcHMK --00504502b8699ea8420478a0ded3--