Re: hotplug and ifup
Sorry, I've been busy with several businesses.
I know hotplug has many bugs, so I'll try to tackle them in this weekend.
At Sun, 23 Feb 2003 13:13:36 +1000,
Anthony Towns wrote:
>
> On Sun, Feb 23, 2003 at 11:55:52AM +1100, Herbert Xu wrote:
> > Anthony Towns <aj@azure.humbug.org.au> wrote:
> > > what should happen, and how should it happen? Should:
> > hotplug should tell ifup that it is calling it, perhaps by using
> > a special option. Then ifup can decide what the policy is.
>
> ifup can't be called before S39ifupdown has been run, which is the
> problem here.
Hmm, then should I fix at least hotplug should be activated
after S39ifupdown? Maybe I should support blacklist (Bug#180521).
> That aside, hotplug could quite easily call "ifup eth0=hotplug"; allowing
> you to have "mapping hotplug" to handle any further details.
Ok, I'll do this.
I'm considering to modify hotplug to use run-parts mechanism (Bug#180017)
which could also solve other bugs such as Bug#148590.
Regards,
Fumitoshi UKAI
Reply to: