Following up with this Denys. Thanks, Dave
On 9/23/16, David Henderson <dhender...@digital-pipe.com> wrote: > Following up with this Denys. > > Thanks, > Dave > > > On 9/22/16, David Henderson <dhender...@digital-pipe.com> wrote: >> On 9/22/16, Denys Vlasenko <vda.li...@googlemail.com> wrote: >>> On Wed, Sep 21, 2016 at 2:57 PM, David Henderson >>> <dhender...@digital-pipe.com> wrote: >>>> On 9/20/16, Denys Vlasenko <vda.li...@googlemail.com> wrote: >>>>> On Tue, Sep 20, 2016 at 8:33 PM, David Henderson >>>>> <dhender...@digital-pipe.com> wrote: >>>>>>> General idea is described here: >>>>>>> https://busybox.net/~vda/no_ifup.txt >>>>>> >>>>>> Looked at it, wouldn't this be the same thing as scripts in >>>>>> /etc/network/if-*.d directories? >>>>> >>>>> It won't be the same, and the document explains why. >>>>> You did not understand it. >>>>> Example #1: the "ifup -a hangs at boot" case >>>>> Example #2: "ifup eth0" + pppd in parallel simultaneously upping ppp0. >>>>> What will be the default route in "ifup" world? >>>> >>>> So the only difference is to not pass the '-a' switch, but instead to >>>> pass the direct name of the adapter? >>> >>> No, I'm saying something rather different. >>> It is explained in the link. >>> >> >> I'm trying to understand what it is that you are saying. You keep >> referring me to the link, but if I don't understand it, I don't think >> I'm going to without further explanation. I'm currently working on >> the networking side of a project and am interested in knowing what >> you're talking about. >> >> Dave >> > _______________________________________________ busybox mailing list busybox@busybox.net http://lists.busybox.net/mailman/listinfo/busybox