initscripts, branch 10.10

10.10

2021-08-26T09:57:28+00:00

Translated using Weblate (Friulian) (#381)

2021-07-10T15:45:37+00:00

Translated using Weblate (Friulian)

Co-authored-by: Fabio Tomat

Translations update from Weblate (#378)

2021-07-03T12:54:23+00:00

* Translated using Weblate (Portuguese (Brazil))
* Translated using Weblate (Swedish)

Co-authored-by: Gustavo Costa 
Co-authored-by: Anders Jonsson

added veth support

2021-06-24T10:11:04+00:00

ifup-eth: add a new PERSISTENT_DHCLIENT_IPV6 option for IPv6 dhclient daemon

2021-06-24T10:07:01+00:00

In 76226a34 ("ifup-eth: apply PERSISTENT_DHCLIENT to IPv6 dhclient daemon"),
one PERSISTENT_DHCLIENT option works for both IPv4 and IPv6, so the IPv4
and IPv6 settings are consistent. However, the user settings for IPv4 and IPv6
are limited.

For example, users try to adopt both IPv4 and IPv6 protocol. DHCPv6 servers
may be not stable as DHCP servers, thus the expectation for obtaining IPv6
address is lower than IPv4 address. For users, IPv4 address must be
obtained for the basic communication. So the PERSISTENT_DHCLIENT option is
set to be "yes | 1" for IPv4 address. However, the network service may be
stuck until it fails due to missing DHCPv6 servers, and the remaining devices also
cannot obtain both IPv4 and IPv6 addresses. The problem is very serious for users.

Here, I add a new PERSISTENT_DHCLIENT_IPV6 option only for IPv6 dhclient daemon,
so users can set IPv4 and IPv6 separately.

Fixes: 76226a3 ("ifup-eth: apply PERSISTENT_DHCLIENT to IPv6 dhclient daemon")
Signed-off-by: Zhiqiang Liu

ifdown removes veth pair if both peers are down

2021-06-24T10:07:01+00:00

rename_device: also support dracut-style kernel cmdline configuration

2021-06-16T07:34:12+00:00

There are 2 cases where this might be useful.
* On machines with initrd build without dracut-network, you can now
  still use ifname option
* On older kernels where double renaming was allowed, normal system
  replaced the name set by initrd.

spec: Mark network-scripts as deprecated

2021-06-03T10:51:55+00:00

The network-scripts package is legacy and deprecated, so nobody should depend on this!
If ifcfg-style configuration is still desired, NetworkManager can do this.
Thus, mark this as deprecated to ensure people know to not depend on it.

Reference: https://docs.fedoraproject.org/en-US/packaging-guidelines/deprecating-packages/

spec: Initscripts now requires chkconfig (#374)

2021-05-31T14:18:03+00:00

As a easy way to get full legacy system V support.

Translations update from Weblate (#371)

2021-05-31T14:15:54+00:00

* Translated using Weblate (Spanish)

Currently translated at 88.6% (140 of 158 strings)

Co-authored-by: Emilio Herrera 
Translate-URL: https://translate.fedoraproject.org/projects/fedora-sysv/initscripts/es/
Translation: fedora-sysv/initscripts

* Added translation using Weblate (Sinhala)

Co-authored-by: Hela Basa 

* Translated using Weblate (Finnish)

Currently translated at 100.0% (158 of 158 strings)

Co-authored-by: Ricky Tigg 
Translate-URL: https://translate.fedoraproject.org/projects/fedora-sysv/initscripts/fi/
Translation: fedora-sysv/initscripts

* Translated using Weblate (Korean)

Currently translated at 100.0% (158 of 158 strings)

Translated using Weblate (Korean)

Currently translated at 82.9% (131 of 158 strings)

Co-authored-by: simmon 
Translate-URL: https://translate.fedoraproject.org/projects/fedora-sysv/initscripts/ko/
Translation: fedora-sysv/initscripts

Co-authored-by: Emilio Herrera 
Co-authored-by: Hela Basa 
Co-authored-by: Ricky Tigg 
Co-authored-by: simmon