On Thu, Mar 29, 2007 at 10:53:47PM +0300, Eddy Petrișor wrote: > >> The only case where the init script worked was when I enabled the > >> interface from NM and *then* it worked, even if I logged out of the > >> X session. This would work until NM disables/deconfigures(/whatever > >> is appropriate term would be according to NM) the card, when the > >> init script, again, has no effect.
> > Ok, still not sure what it means for this to not work. NM provides no hooks > > that prevent ifupdown from doing its job. > For more information about the issues, see the attached (beautified) script. Uh, putting your comments on the process *in-line as shell comments* is very difficult to read; you also show three tests but only show the contents of /etc/network/interfaces in two of them, which I find confusing. It would be a lot clearer if you would summarize your findings. It is certainly the case that /etc/init.d/networking should have no effect on interfaces that are not marked 'auto'. For interfaces that are marked 'auto', it should have an affect, and in my tests appears to do so. The fact that it is possible in the NM applet to *override* the status of an interface sounds to me like a feature, not a bug. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
