[PATCH] AUTHORS: Add myself to AUTHORS

2016-09-20 Thread Linus Walleij
Instead of complaining that my authorship of the rewrite of the mdev to use /sys/dev is totally gone from the git history I bravely take credit by adding myself to the AUTHORS file instead, he he. Signed-off-by: Linus Walleij --- AUTHORS | 4 1 file changed, 4

Re: additional ifupdown problems

2016-09-20 Thread Martin Townsend
Hi Dave, On Tue, Sep 20, 2016 at 4:40 PM, David Henderson wrote: > That's what my research has yielded as well, however, it doesn't > appear that /var/run/ifstate is getting written to. I check the > ownership/permissions of the file: > > root:root 644 > > I since

Re: ifupdown problem

2016-09-20 Thread Denys Vlasenko
On Tue, Sep 20, 2016 at 8:33 PM, David Henderson 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

Re: additional ifupdown problems

2016-09-20 Thread David Henderson
Additionally, I have tried to remove the /var/run/ifstate file before running 'ifup' - same failed result. What exact file is the following line referring to? ip: RTNETLINK answers: File exists Thanks, Dave On 9/20/16, David Henderson wrote: > Aside from

Re: additional ifupdown problems

2016-09-20 Thread David Henderson
Aside from ownership/permissions, can anyone think of why 'ifup' does not write to this file? Regression on BB code perhaps? Can any confirm theirs actuallys writes to this file? Thanks, Dave On 9/20/16, David Henderson wrote: > That's what my research has

Re: ifupdown scripts

2016-09-20 Thread David Henderson
Does BB require certain permissions or ownership of the scripts/directories for this to get called? Dave On 9/20/16, David Henderson wrote: > Hey Martin, thanks for your help! I tried renaming the file as you > requested, but it is still not being called. I did

Re: ifupdown problem

2016-09-20 Thread David Henderson
On 9/20/16, Denys Vlasenko wrote: > On Tue, Sep 20, 2016 at 5:44 PM, Martin Townsend > wrote: +++ busybox-1.24.1/networking/ifupdown.c 2016-09-06 13:39:59.288380571 +0100 @@ -501,7 +501,7 @@ { int result; # if

Re: ifupdown problem

2016-09-20 Thread Denys Vlasenko
On Tue, Sep 20, 2016 at 5:44 PM, Martin Townsend wrote: >>> +++ busybox-1.24.1/networking/ifupdown.c 2016-09-06 13:39:59.288380571 +0100 >>> @@ -501,7 +501,7 @@ >>> { >>> int result; >>> # if ENABLE_FEATURE_IFUPDOWN_IP >>> - result = execute("ip addr flush dev

Re: dhcp with /etc/network/interfaces

2016-09-20 Thread David Henderson
Thanks for your help with this too Denys. Answers are inline... On 9/20/16, Denys Vlasenko wrote: > On Tue, Sep 20, 2016 at 5:31 PM, David Henderson > wrote: >> Hey Martin, thanks again for your help! So I had to bring back >>

Re: ifupdown problem

2016-09-20 Thread Martin Townsend
Hi Denys, On Tue, Sep 20, 2016 at 4:34 PM, Denys Vlasenko wrote: > On Tue, Sep 6, 2016 at 3:11 PM, Martin Townsend > wrote: >> Hi, >> >> I'm using busybox with ENABLE_FEATURE_IFUPDOWN_IP and when using >> ifdown with a virtual interface it

Re: dhcp with /etc/network/interfaces

2016-09-20 Thread David Henderson
Yes, I'm interested to know if those parameters can be set, or if I can just use the scripts in the if-*.d directories instead of the build-in call BB is making to the DHCP (to prevent duplicate calls to that server - one from BB, one from my scripts). Thanks, Dave On 9/20/16, Martin Townsend

Re: additional ifupdown problems

2016-09-20 Thread David Henderson
That's what my research has yielded as well, however, it doesn't appear that /var/run/ifstate is getting written to. I check the ownership/permissions of the file: root:root 644 I since changed it to mimic yours and attempted an 'ifup' again - no luck, same message. I then tried adding the

Re: ifupdown problem

2016-09-20 Thread Denys Vlasenko
On Tue, Sep 6, 2016 at 3:11 PM, Martin Townsend wrote: > Hi, > > I'm using busybox with ENABLE_FEATURE_IFUPDOWN_IP and when using > ifdown with a virtual interface it takes down the primary interface as > well. For our board we setup eth0:0 on a 10.10.10.x/29 network and

Re: dhcp with /etc/network/interfaces

2016-09-20 Thread David Henderson
Hey Martin, thanks again for your help! So I had to bring back 'sneaker-net' to get strace on the machine via flash drive (after locating one), but it is now on the machine! I could not see anything in the 'ps' output (and it is the GNU version) regarding what was being called for contacting a

Re: ifupdown scripts

2016-09-20 Thread David Henderson
Hey Martin, thanks for your help! I tried renaming the file as you requested, but it is still not being called. I did just submit a new post regarding additional problems with ifup/down. Perhaps something in there can help with a resolution here - in short running an 'ifup -v eth0' doesn't

Re: dhcp with /etc/network/interfaces

2016-09-20 Thread Martin Townsend
Hi David, I've had a quick look through the ifupdown code what DHCP binary gets called and with what parameters is specific to how you've configured busybox. If you have the full version of ps you may be able to see the full command line using ps aux. Maybe the busybox version will show this

Re: ifupdown scripts

2016-09-20 Thread Martin Townsend
Hi David, Does it work if you drop the .conf? /etc/network/if-up.d/000_resolv -Martin On Mon, Sep 19, 2016 at 9:59 PM, David Henderson wrote: > Good afternoon all! I have been continuing to work with the > networking in BB and have added a single script >

Re: ifupdown scripts

2016-09-20 Thread David Henderson
And with this. Thanks, Dave On 9/19/16, David Henderson wrote: > Good afternoon all! I have been continuing to work with the > networking in BB and have added a single script > '/etc/network/if-up.d/000_resolv.conf' that does not seem to be called > when 'ifup -a'

Re: dhcp with /etc/network/interfaces

2016-09-20 Thread David Henderson
Good morning all, I was just following up with this. Thanks, Dave On 9/19/16, David Henderson wrote: > Plus that would only answer part of the original question. Any input > on that second part? > > Thanks, > Dave > > > On 9/19/16, David Henderson