Re: Sequence of rc.* during boot
TuxaneMedia <[email protected]>
| Newsgroups | gmane.linux.slackware |
|---|---|
| Organization | burro-net |
| Message-ID | <[email protected]> |
Am 28.09.2012 20:32, schrieb Rich Shepard: > On Fri, 28 Sep 2012, Evan Hisey wrote: > >> The rc.* file has the execution order for that run level > > Evan > > That's the answer. Since there's no listing for rc.wireless or > rc.ifplugd > I still don't know if the order in which they're invoked is part of the > problem of the Ethernet interface staying up in the kernel when > there's no > cable attached. > > Thanks, > > Rich > > > _______________________________________________ > slackware mailing list > [email protected] > https://mailman.lug.org.uk/mailman/listinfo/slackware Hi rich, rc.wireless get's called in rc.init1 around line 129. As far as I know, there is no rc.ifplugd in stock Slackware. About your network problem I wrote a longer answer (I accidently never send) because I feel you are a bit on the wrong track as it's quite normal that an exixting interface *ALWAYS* stays visible, if the cable is plugged in or not. (from ifconfig for example) If you like I can send what I wrote, - I thought it had been solved already Jens -- TuxaneMedia / SARL Burro-net 7 Place du Pont F-66400 Céret T:: +33 4 68 82 73 20 @:: [email protected] Web:: http://www.burro-net.com PGP:: http://www.tuxane.com/pub/jenspub.asc TVA:: FR20503676124 SIRET:: 503 676 124 000 20