initscripts/network-scripts, branch 10.00.2 Mageia fork of Fedora's Init Scripts ifup-post: fix incorrect condition for RESOLV_MODS 2019-06-06T08:32:53+00:00 David Kaspar [Dee'Kej] dkaspar@redhat.com 2018-08-20T12:31:56+00:00 1d4ffa5559de4cf3fdfcc2e69467fc74426cd78c This was causing the /etc/resolv.conf file to be always updated when RESOLV_MODS was not set... Before the commit 5d6156454bf8f6dab4a5fdd7e1bf6 we were not updating the /etc/resolv.conf file if the RESOLV_MODS was empty. See https://bugzilla.redhat.com/show_bug.cgi?id=1610411 for more info. 
  This was causing the /etc/resolv.conf file to be always updated when
  RESOLV_MODS was not set...

  Before the commit 5d6156454bf8f6dab4a5fdd7e1bf6 we were not updating
  the /etc/resolv.conf file if the RESOLV_MODS was empty.

  See https://bugzilla.redhat.com/show_bug.cgi?id=1610411 for more info.
network/ifup/ifdown: deprecations warnings redirected to stderr 2018-08-06T11:05:14+00:00 David Kaspar [Dee'Kej] dkaspar@redhat.com 2018-08-06T09:15:47+00:00 b163b3a66dc3684181f219f424e2dd81eff691f6 






network/ifup/ifdown: allow disabling of deprecation warnings
2018-08-03T11:06:43+00:00

David Kaspar [Dee'Kej]
dkaspar@redhat.com

2018-08-02T13:05:17+00:00

335a6a84f618515c6902d374e391a301d0f43f6c

  ... by checking existence of /etc/sysconfig/disable-deprecation-warnings





  ... by checking existence of /etc/sysconfig/disable-deprecation-warnings







network/ifup/ifdown: deprecation warnings for 'network-scripts' added
2018-08-03T11:03:15+00:00

David Kaspar [Dee'Kej]
dkaspar@redhat.com

2018-08-01T15:41:08+00:00

285473ae10611849129eb16050ea6d6b8d84388d

  In case of 'network' service these warnings are displayed only once,
  to not spam unnecessarily user's journalctl if they have many NICs.





  In case of 'network' service these warnings are displayed only once,
  to not spam unnecessarily user's journalctl if they have many NICs.







network-scripts: Add previously dropped error checking
2018-06-14T14:27:36+00:00

Phil Sutter
psutter@redhat.com

2018-06-12T11:54:15+00:00

88b3ac3840cc993901f971a2a99046881d9e46c4

When converting from brctl to ip-link, the call to exit in case bridge
adding failed was dropped by accident.





When converting from brctl to ip-link, the call to exit in case bridge
adding failed was dropped by accident.







network-scripts: Replace brctl with ip-link
2018-06-14T14:27:36+00:00

Phil Sutter
psutter@redhat.com

2018-06-11T14:58:20+00:00

bf40c2768d6b6614cc0f1b4fb68ca011489e89d3

Since ip-link has full support for Linux bridges (and slave ports), use
that instead of the deprecated brctl from bridge-utils.





Since ip-link has full support for Linux bridges (and slave ports), use
that instead of the deprecated brctl from bridge-utils.







network-scripts: setting of firewall ZONE fixed
2018-06-07T12:04:50+00:00

David Kaspar [Dee'Kej]
dkaspar@redhat.com

2018-06-06T17:19:11+00:00

12a83d3ef4244d354cba541ce8d3f0ded9773c89

  For currently unknown reason the dbus-send calls will fail to set the
  firewall zone for the given interface if we omit the --print-reply
  option...

  This looks like some kind of race-condition in dbus-send, since the
  --print-reply makes the call synchronous and slower.

  Hopefully this is only a temporary workaround until DBus is fixed.

  Resolves: #1586284





  For currently unknown reason the dbus-send calls will fail to set the
  firewall zone for the given interface if we omit the --print-reply
  option...

  This looks like some kind of race-condition in dbus-send, since the
  --print-reply makes the call synchronous and slower.

  Hopefully this is only a temporary workaround until DBus is fixed.

  Resolves: #1586284







ifdown-post: artifact whitespace removed from the DBus call
2018-06-07T12:04:50+00:00

David Kaspar [Dee'Kej]
dkaspar@redhat.com

2018-06-06T17:09:36+00:00

8659ca9ef9c1b0826799ea8da217c886ff0c26b5

  This was causing the DBus call to fail, and we didn't catch it before
  since we were forwarding everything into /dev/null...

  Related: RHBZ#1586284





  This was causing the DBus call to fail, and we didn't catch it before
  since we were forwarding everything into /dev/null...

  Related: RHBZ#1586284







netreport functionality dropped
2018-05-30T12:33:04+00:00

David Kaspar [Dee'Kej]
dkaspar@redhat.com

2018-05-24T14:06:03+00:00

9b2dbe00100d4e1077404b9d781f35adad979467

  This concept is quite outdated, and not sane to use at all.





  This concept is quite outdated, and not sane to use at all.







Repository scheme updated to new layout
2018-05-30T10:32:22+00:00

David Kaspar [Dee'Kej]
dkaspar@redhat.com

2018-05-25T18:01:54+00:00

a145ddda284570e57413e37f025c3657205e17d8

  NOTE: This commit just moves files around, without actually fixing the
        Makefiles and specfile. See follow up commits which resolve this.





  NOTE: This commit just moves files around, without actually fixing the
        Makefiles and specfile. See follow up commits which resolve this.