ifupdown 0.8.5 ifupdown2

Started by paxmark2, 2016/01/05, 01:27:48

Previous topic - Next topic

paxmark2

I go weeks without my internet not cutting out, but occasionally my connman networked Indian Summer will not be come up at boot or more recently, for about a week, intermittent cutout of my internet, which has stopped.  The openvpn running under tmux from alt-F1 tty1 was not affected, it would start right back up after  ifdown wlan0 ifup wlan0 or systemctl stop then start connman.  I copied some logs via journalctl, but never filed a question.  I was not sure if it was connman, ifupdown or both or something else.  And I have not been troubled with it in a Sparky (testing) 32 bit atom laptop with LXQT also via Siduction repo. So, I delay but watch.   


I delay dist-upgrading  for 24 hours whenever I see systemd (or apt or dpkg), etc.  I read the changelog of ifupdown 0.8.5 when I saw the upgrade because of my prior suspicions and


Quote[/size]Move ifupdown related files from the systemd and udev packages to this package. Closes: #809171[size=78%]
grabbed my attention.  A day went by. 


So I was not surprised when attempting to dist-upgrade that I saw Debian bug 809773 flagged.  i delay some more.  I am naive, but I think 809773 might take a bit to fix.  Naive but patient. 


Questions I have
1.  Will ifupdown have a future in sid and systemd or is it to be swallowed up eventually
2.  How does the very young ifupdown2 fit into the future, if at all.  I did find the man page in the Cumulus git.   


I am in no rush, just curious. 
Mark



paxmark2

Maybe bad form, but I am replying to myself.


Bug 809171 has been downgraded, and bug 810114 has surfaced, both having to do with the moving of hotplug functions from udev 228-3 to ifupdown 0.8.6    Having the phrase allow-hotplug in /etc/network/interfaces can cause out of order problems. 


In re. Question 2 above
I asked at #CumulusNetworks about their ifupdown2 which is listed as a replacement for ifupdown in testing and sid if it was an option.  I received no reply over a few hours.  I tested it in a Debian 32 bit testing system with lxqt and connman and ifupdown2 1.0~git20151029-1 failed.  Getting back to ifupdown was easily done.  It seems like every few seasons someone decides to rewrite ifupdown into python - and then it lies dormant and languishes. 


peace out,