All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fumitoshi UKAI <ukai@debian.or.jp>
To: linux-hotplug@vger.kernel.org
Subject: Re: REMOVER support without usbdevfs
Date: Tue, 08 Jan 2002 17:47:32 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-101051216220317@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-101042462122011@msgid-missing>

At Mon, 07 Jan 2002 10:18:22 -0800,
David Brownell wrote:
> 
> Looks right to me.  Please submit a patch to fix this bug.

I just committed a following patch to cvs repository. Is this ok?

Index: usb.agent
=================================RCS file: /cvsroot/linux-hotplug/admin/etc/hotplug/usb.agent,v
retrieving revision 1.15
diff -u -u -r1.15 usb.agent
--- usb.agent	2001/09/07 15:57:39	1.15
+++ usb.agent	2002/01/08 17:43:42
@@ -281,7 +281,11 @@
 # declare a REMOVER name that the add action can use to create a
 # remover, or that the remove action can use to execute a remover.
 #
-declare -rx REMOVER=/var/run/usb/`echo $DEVICE | sed -e 's;/;%;g'`
+if [ "$DEVICE" = "" ]; then
+  declare -rx REMOVER=/var/run/usb/`echo "$INTERFACE/$PRODUCT/$TYPE" | sed -e 's;/;%;g'`
+else
+  declare -rx REMOVER=/var/run/usb/`echo $DEVICE | sed -e 's;/;%;g'`
+fi
 
 #
 # What to do with this USB hotplug event?


Regards,
Fumitoshi UKAI

> ----- Original Message ----- 
> From: "Fumitoshi UKAI" <ukai@debian.or.jp>
> To: <linux-hotplug-devel@lists.sourceforge.net>
> Sent: Monday, January 07, 2002 9:28 AM
> Subject: REMOVER support without usbdevfs
> 
> 
> > Hi,
> > 
> > I've receive the following bug reports: http://bugs.debian.org/128121
> > 
> > > In /etc/hotplug/usb.agent REMOVER is made from the contens of DEVICE
> > > which is empty if usbdevfs is not present, i.e. REMOVER will be set
> > > to /var/run/usb/ instead of /var/run/usb/somefile.
> > 
> > > Thus program relying on REMOVER to install a remover script will
> > > fail to do so.
> > 
> > > I've circumvented this by checking whether DEVICE is empty and then
> > > generating REMOVER from INTERFACE PRODUCT and TYPE. note however
> > > that DEVICE may not be set to anything, since hotplug.functions
> > > takes it as an indicator whether usbdevfs is present or not.
> > 
> > So is there any problem like this?
> > 
> > if [ "$DEVICE" = "" ]; then
> >  declare -rx REMOVER=/var/run/usb/`echo "$INTERFACE/$PRODUCT/$TYPE" | sed -e 's;/;%;g'`
> > else
> >  declare -rx REMOVER=/var/run/usb/`echo $DEVICE | sed -e 's;/;%;g'`
> > fi
> > 
> > Regards,
> > Fumitoshi UKAI
> > 
> > _______________________________________________
> > 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
> 
> 

_______________________________________________
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

  parent reply	other threads:[~2002-01-08 17:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-07 17:28 REMOVER support without usbdevfs Fumitoshi UKAI
2002-01-07 18:18 ` David Brownell
2002-01-08 17:47 ` Fumitoshi UKAI [this message]
2002-01-08 18:17 ` David Brownell

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=marc-linux-hotplug-101051216220317@msgid-missing \
    --to=ukai@debian.or.jp \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.