From: Ian Pilcher <i.pilcher@comcast.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Is anybody paying attention?
Date: Thu, 11 Nov 2004 21:00:16 +0000 [thread overview]
Message-ID: <cn0jt1$9r4$1@sea.gmane.org> (raw)
In-Reply-To: <cn09g1$9no$1@sea.gmane.org>
Ian Pilcher wrote:
> Come on people! This is causing a lot of pain for people who want USB
> devices to "just work". If changing the "readlink -f" call to just
> "readlink" isn't the right answer, then someone speak up. Otherwise,
> fix it!
>
An update, changing 'readlink -f' to simply 'readlink' definitely
doesn't work. Replacing it with 'echo' *seems* to work for me. I don't
feel comfortable sending in a patch to do this, because I don't under-
stand what side-effects it might have.
To ask again, I'm proposing to change the line in /etc/hotplug/usb.agent
that reads:
REMOVER=/var/run/usb/$(readlink -f $SYSFS/$DEVPATH | sed -e 's;/;%;g')
to:
REMOVER=/var/run/usb/$(echo -n $SYSFS/$DEVPATH | sed -e 's;/;%;g')
This gives REMOVER a consistent value for both add and insert events
(even when the sysfs device is already gone during the remove event).
--
====================================
Ian Pilcher i.pilcher@comcast.net
====================================
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id\x12065&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-11-11 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-11 18:02 Is anybody paying attention? Ian Pilcher
2004-11-11 19:20 ` the flying pig brigade
2004-11-11 21:00 ` Ian Pilcher [this message]
2004-11-12 2:06 ` Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='cn0jt1$9r4$1@sea.gmane.org' \
--to=i.pilcher@comcast.net \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).