On Thu, 2005-02-17 at 15:17 +0100, Guus Sliepen wrote: > The ifrename package does not > contain an init script (I don't think anyone knows which priority it > should have)
You can create one at S:S40ifrename. This was requested and discussed in #243382. In that thread, J.T. said at one point that the ifrename call should come after the setting up of ipv4 kernel parameters, which happens in S:S40networking. However, I later discussed this with Md and he convinced me that there was no reason to insist on this sequence of events. It should be fine to do ifrename just before S:S40networking. > nor hook scripts for any other package. Adding a hotplug hook script is complicated by the fact that the name of the interface is passed to /etc/hotplug.d/net/*.hotplug scripts in the INTERFACE environment variable. It won't do for ifrename to install a hook script at /etc/hotplug.d/net/000ifrename.hotplug and for ifplugd.hotplug and waproamd.hotplug to get called with the original interface name in INTERFACE. Either * hotplug should run ifrename and call ifplugd.hotplug and waproamd.hotplug with INTERFACE set to the new name or else * ifplugd.hotplug and waproamd.hotplug should each call ifrename for the interface named in INTERFACE and then should start ifplugd/waproamd with the new interface name. -- Thomas Hood <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
