From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: IEEE 1394 SBP-2 pseudo driver
Date: Mon, 08 Jan 2001 21:55:53 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-97899158825612@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-97897252601687@msgid-missing>
> > Wouldn't there be a problem if /sbin was mounted
> > on the device that was just unplugged?
>
> I suppose it would be.
I think Linus described that as a user error case ...
there are a LOT of ways you can break system startup.
For example, if "/sbin/init" or "/sbin/modprobe" went
away, similar bad things would happen.
I think Randy's got it right:
> The actual file name used for the hotplug program (script)
> is stored in /proc/sys/kernel/hotplug, so changing that
> during /sbin unplug/replug is also an option.
>
> Looks to me like /sbin is a good place for it according to
> FHS 2.1. FHS 2.2 is being updated now, but I don't see any
> changes in it to address hotplug.
> I doubt that FHS took hot unplug/plug into account.
Likely it should ... including conventions for how to extend
the basic /sbin/hotplug functionality. The convention
that's been discussed so far involves /etc/hotplug scripts;
a SCSI hotplug agent would be "/etc/hotplug/scsi.agent", and
could be updated independently from agents for USB, PCI,
and so forth.
- Dave
_______________________________________________
Linux-hotplug-devel mailing list
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2001-01-08 21:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 16:48 IEEE 1394 SBP-2 pseudo driver Dunlap, Randy
2001-01-08 18:31 ` Greg KH
2001-01-08 21:55 ` David Brownell [this message]
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-97899158825612@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).