From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hotunplug
Date: Fri, 25 May 2001 14:19:11 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-99080083809712@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-99057879015003@msgid-missing>
> + # 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.
Yes. Though ... shouldn't the directory be configurable?
A default of /var/run/usb would be fine; the existing
machinery in /etc/sysconfig/usb should be able to change
such defaults.
And there are bootstrap issues too ... if this is run through
the /etc/rc.d/init.d/hotplug script, "/var/run/usb" won't be
readonly, but perhaps existing scripts should be run and then
removed (for crash recovery, with some appropriate ACTION
set in the environment during hotplug startup).
> If David doesn't object, I'll add this patch to cvs (without the above
> change, but with the .spec file changed.)
I'll not object, though as Miles noted there may be interesting
races on unplugging that don't get seen very often ... also, the
README directions for manual install should get updated.
- Dave
_______________________________________________
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
next prev parent reply other threads:[~2001-05-25 14:19 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 ` Hotunplug Greg KH
2001-05-25 14:19 ` David Brownell [this message]
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-99080083809712@msgid-missing \
--to=david-b@pacbell.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).