linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hotunplug
Date: Fri, 25 May 2001 04:46:39 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-99077007926102@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-99057879015003@msgid-missing>

On Tue, May 22, 2001 at 05:44:45PM -0700, Stephen Williams wrote:
> 
> I've made a go at implementing support for hot unplug in the hotplug
> scripts. What I have done is calculated a path to a "remover" program
> that is passed as the REMOVE environment variable to the existing add
> scripts. If the add script wants to make something happen when the
> device is removed, it writes something to the remover and marks it
> executable.

I like the idea of this, but the following lines make me nervous:

 
+    # Create a directory to hold remover programs. Close it up so
+    # that only hotplug scripts can write to this directory.
+    mkdir /var/run/usb
+    chmod 0700 /var/run/usb
+

Things like this should be done by the installer of the package, so as
to allow different distros handle this properly.

Also, the creation of directories should be done only once, not every
time.

If David doesn't object, I'll add this patch to cvs (without the above
change, but with the .spec file changed.)

thanks,

greg k-h

_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  reply	other threads:[~2001-05-25  4:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-23  0:44 Hotunplug Stephen Williams
2001-05-25  4:46 ` Greg KH [this message]
2001-05-25 14:19 ` Hotunplug David Brownell
2001-05-25 14:53 ` Hotunplug Stephen Williams

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-99077007926102@msgid-missing \
    --to=greg@kroah.com \
    --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).