On Tue, 2005-08-23 at 10:00 +0200, Marco d'Itri wrote:
Right, it's not used but it's checked.
But then there is still /etc/hotplug.d/default/default.hotplug, which if
present will create all kinds of troubles.
Let me get one more thing straight before we move on ...
What's the sequence of
On Aug 24, Ben Armstrong [EMAIL PROTECTED] wrote:
1. kernel hotplug subsystem detects an event
2. kernel dispatches the event handling using the program named
in /proc/sys/kernel/hotplug (default is /sbin/hotplug) passing it any
necessary argument(s) to hotplug
3. /sbin/hotplug dispatches
On Wed, 2005-08-24 at 16:30 +0200, Marco d'Itri wrote:
On udev systems events are received by udevd, either using udevsend or
(when the kernel input subsystem will be fixed) a netlink socket.
/sbin/hotplug does not enter in the picture at all.
Then the default udev configuration will run the
On Aug 24, Ben Armstrong [EMAIL PROTECTED] wrote:
This is not strictly needed, but I cannot avoid it until udev will
become mandatory to have hotplug support (is there a consensus on this?).
Could udev be modified to not run the hotplug.d handlers
if /sbin/hotplug is missing? (Or is that
On Aug 23, Ben Armstrong [EMAIL PROTECTED] wrote:
script, it should be written to exit if the appropriate binary isn't
found.
The appropriate binary is a conffile as well.
Now, that's not strictly true, is it? /etc/init.d/hotplug
invokes /sbin/hotplug, which almost entirely consists of
Em Seg, 2005-08-22 às 01:32 +0200, Marco d'Itri escreveu:
The (still not uploaded) coldplug package conflicts+depends+provides
hotplug. The issue is that since all the important parts of hotplug are
conffiles they are not deleted when the package is removed, and this
is bad (as in the system
On Aug 23, Gustavo Noronha Silva [EMAIL PROTECTED] wrote:
The (still not uploaded) coldplug package conflicts+depends+provides
hotplug. The issue is that since all the important parts of hotplug are
conffiles they are not deleted when the package is removed, and this
is bad (as in the
On Tue, 2005-08-23 at 19:15 +0200, Marco d'Itri wrote:
Think hotplug events loop.
So, a hotplug event could load and run code (which happen to be in conf
files, and therefore cannot be diverted) in the old hotplug package.
The problem you're facing, it seems, is that while code should be
On Tue, Aug 23, 2005 at 02:09:48PM -0300, Gustavo Noronha Silva wrote:
Em Seg, 2005-08-22 às 01:32 +0200, Marco d'Itri escreveu:
The (still not uploaded) coldplug package conflicts+depends+provides
hotplug. The issue is that since all the important parts of hotplug are
conffiles they are
On Aug 23, Ben Armstrong [EMAIL PROTECTED] wrote:
So, a hotplug event could load and run code (which happen to be in conf
files, and therefore cannot be diverted) in the old hotplug package.
The problem you're facing, it seems, is that while code should be
divertable, conf files aren't, but
On Tue, 2005-08-23 at 19:50 +0200, Marco d'Itri wrote:
The init file does, but /etc/hotplug.d/default/default.hotplug does not.
Why is this file a conffile? I didn't see any obviously configurable
parts in it. If it were either wholly be moved elsewhere (/sbin) or the
guts of it moved
On Aug 23, Ben Armstrong [EMAIL PROTECTED] wrote:
On Tue, 2005-08-23 at 19:50 +0200, Marco d'Itri wrote:
The init file does, but /etc/hotplug.d/default/default.hotplug does not.
Why is this file a conffile? I didn't see any obviously configurable
Historical reasons? It does not really
Em Ter, 2005-08-23 às 11:11 -0700, Steve Langasek escreveu:
If you do that, how do you ensure that these two cases are both handled
sanely?:
- after installing the coldplug package, the admin purges the hotplug
package, and later reinstalls it (removing coldplug)
- after installing the
On Mon, 2005-08-22 at 01:32 +0200, Marco d'Itri wrote:
The (still not uploaded) coldplug package conflicts+depends+provides
hotplug. The issue is that since all the important parts of hotplug are
conffiles they are not deleted when the package is removed, and this
is bad (as in the system will
On Aug 22, Ben Armstrong [EMAIL PROTECTED] wrote:
The (still not uploaded) coldplug package conflicts+depends+provides
hotplug.
Aren't you missing replaces?
Yes, what I actually meant was conflicts+replaces+provides.
My original question still stands:
Is there anything else I can do, other
On Mon, 2005-08-22 at 21:41 +0200, Marco d'Itri wrote:
On Aug 22, Ben Armstrong [EMAIL PROTECTED] wrote:
The (still not uploaded) coldplug package conflicts+depends+provides
hotplug.
Aren't you missing replaces?
Yes, what I actually meant was conflicts+replaces+provides.
My original
On Aug 22, Ben Armstrong [EMAIL PROTECTED] wrote:
Which conf files blow things up? The reason I ask is, if it's an init
Just about all of them. Almost all files in the package are conffiles.
script, it should be written to exit if the appropriate binary isn't
found.
The appropriate binary is
On Mon, 2005-08-22 at 23:18 +0200, Marco d'Itri wrote:
On Aug 22, Ben Armstrong [EMAIL PROTECTED] wrote:
Which conf files blow things up? The reason I ask is, if it's an init
Just about all of them. Almost all files in the package are conffiles.
script, it should be written to exit if
The (still not uploaded) coldplug package conflicts+depends+provides
hotplug. The issue is that since all the important parts of hotplug are
conffiles they are not deleted when the package is removed, and this
is bad (as in the system will probably not boot bad).
Does a way to force purging the
19 matches
Mail list logo
